Went from small spike 100% to decreasing 100%

Pattern was as follows:
Thursday AM: https://turnipprophet.io/?prices=100.83.82..75...63.....&pattern=3
Thursday PM: https://turnipprophet.io/?prices=100.83.82..75...63.62....&pattern=3
Obviously changed from 100% small spike to 100% decreasing? Surely shouldn’t say 100% if it’s not sure. Not sure if prediction error or not.

With a Sunday price of 100, your first price on Monday (83) is out of the range of what should have been possible for the decreasing pattern (85-91). Either there's a bug with this project, or perhaps the new AC update affected what pattern/prices you're getting? The update was centered around balancing the bells economy. I haven't seen anything saying that turnips were affected, but it's possible.

Either there's a bug with this project, or perhaps the new AC update affected what pattern/prices you're getting? The update was centered around balancing the bells economy. I haven't seen anything saying that turnips were affected, but it's possible.

There's been no indication so far that the Turnip prices have been tweaked in any of the patches.

As far as these numbers go.. they start to fall appart already at your Monday PM price. A value of 83 on Monday AM is within range for a Small Spike, but an 82 on Monday PM is already out of range - the app applied a fudge factor of 1 here in case it was a floating point rounding issue, and caame up with a match for Small Spike again (but a fudged one).
Then we get into Tuesday - you don't have a Tuesday AM price (that's fine!) but the Tuesday PM price is within normal range for a Small Spike, again assuming we remove the 82 from Monday PM.
Finally we get into the next set of known numbers, the 63 on Thursday AM is within range of a normal Small Spike. However, the 62 on Thursday PM is back out of range, and a fudge factor of 2 was applied in order to find a possible fudged match in a Decreasing pattern.

So, there's all that, and of course more... For a Small Spike pattern, there can be anywhere bewteen 0 and 7 decreasing periods before the start of the spike. Based on your numbers, we can see that you had the max of seven, because of your Monday AM at 83 down to Thursday AM at 63. What that means is, for a Small Spike, you are guaranteed to hit the start of your spike by Thursday PM, however in your case the number went down again by 1, which means it's impossible to be a Small Spike.
What this all tells me is a couple things are possible.

A resident of your island did some time traveling, causing the calculations to be reset for the week.
The numbers you've entered aren't all from the same island
The numbers were entered slightly incorrectly
The game logic has been changed in a patch (but as previously stated there's been no indication of that so far)

One of those things (or possibly something else I'm not thinking of right now) must be true, and it appears you've been on a Decreasing pattern all week, despite to tool falsely reporting a Small Spike.
Now, all that being said.. the fact that the tool produced a Small Spike when that wasn't possible for you is concerning, and is an unfortunate side effect of the fudge factor that we account for... more thought/work needs to be done on the fudge factor, it seems.

@theRTC204 the level of detail you put into this is astounding - thanks for this tool.
I can confirm, without being that guy, that no time travelling happened, as only I know how to time travel and my girlfriend, bless her, doesn't want to at all anyway. It is entirely possible that the numbers are slightly incorrect, however, all I can do this time around is trust my partner to pass it on correctly.
Thanks for the detailed response. I look forward to this tool becoming more and more reliable!


public NavigationPathHolder for usage in cases where Custom UI is needed

When using a SwiftUI Button or any other programmatic way, it might be convinient to be able to access the NavigationPathHolder EnvironmentObject to manipulate the path directly in sub views.

Thanks for raising this PR @muellnes! I agree this is a useful addition, but so far I've resisted adding any APIs that aren't available in SwiftUI's equivalent, so that there won't be any barriers for package users to migrate back to vanilla SwiftUI when possible.
This functionality could be achieved from outside this library, e.g.:
class Navigator: ObservableObject {
  private let pathBinding: Binding<NBNavigationPath>

  var path: NBNavigationPath {
    get { pathBinding.wrappedValue }
    set { pathBinding.wrappedValue = newValue }
  }

  init(_ pathBinding: Binding<NBNavigationPath>) {
    self.pathBinding = pathBinding
  }
}

Where you create the NBNavigationStack you could then add .environmentObject(Navigator($path)), and on screens that want to use it  @EnvironmentObject var navigator: Navigator would give you access to its path. Something similar could be done if using an Array path rather than an NBNavigationPath, with the advantage that your navigator would be properly typed.

Hi @johnpatrickmorgan thank you for the quick response :) and the good suggestion.
I can absolutely understand your concerns, but if it is fine for you I would then change the PR to add your suggestion to the README?
Thanks,
Sascha

@muellnes Having thought about this a little more, I think you're right that the library should offer this functionality. I've made a PR #23 that builds this into the library and adds utility functions for pushing and popping.

Closed as the changes in https://github.com/johnpatrickmorgan/NavigationBackport/pull/23 cover not only this initial request, but even go further.
Thank you so much @johnpatrickmorgan

Thanks @muellnes - the new APIs are now available from v0.6.0.

Thank you so much @johnpatrickmorgan - I just upgraded our current project to the new version 👍


Allow to change webhook secret name via WEBHOOK_SECRET_NAME

It is next action in #1377

/ok-to-test

@hhk7734 Please join the list of contributors, so that we do not need the ok-to-test label any more.
This is an example: https://github.com/knative/community/pull/1264/files


The number of Jacobian matrix is the number of links in the robot minus 1

The base link does have Jacobian matrix?

Currently, the base link does not have a Jacobian matrix. We are working on integrating a faster kinematics library for Jacobian computation and the all 0 Jacobian matrix for the root link will be available in the next release.


Disable individual options

Is it possible to toggle the disabled state of individual options?
https://select2.github.io/examples.html#disabled

This is intended to work, but in fact not currently tested. Please give me some time to dig into this and add tests.
In case you need this feature right now, feel free to give me a helping hand ;)


doc: more example manifests

Useful to try out quickly things on kind, at least.
Signed-off-by: Francesco Romani<EMAIL_ADDRESS>

/lgtm


Reset password error - Uncaught Error: Match error: Expected string, got object

I'm getting the following error message when testing out the reset password
Uncaught Error: Match error: Expected string, got objectn @ 1b6d362a6b5cf33ccf07ab04bb45f2a3d5320a98.js:21e.resetPassword @ 1b6d362a6b5cf33ccf07ab04bb45f2a3d5320a98.js:72E.atPwdFormEvents.submit #at-pwd-form @ 1b6d362a6b5cf33ccf07ab04bb45f2a3d5320a98.js:212(anonymous function) @ 1b6d362a6b5cf33ccf07ab04bb45f2a3d5320a98.js:64e._withTemplateInstanceFunc @ 1b6d362a6b5cf33ccf07ab04bb45f2a3d5320a98.js:64(anonymous function) @ 1b6d362a6b5cf33ccf07ab04bb45f2a3d5320a98.js:64(anonymous function) @ 1b6d362a6b5cf33ccf07ab04bb45f2a3d5320a98.js:63c._withCurrentView @ 1b6d362a6b5cf33ccf07ab04bb45f2a3d5320a98.js:63(anonymous function) @ 1b6d362a6b5cf33ccf07ab04bb45f2a3d5320a98.js:63(anonymous function) @ 1b6d362a6b5cf33ccf07ab04bb45f2a3d5320a98.js:63ie.event.dispatch @ 1b6d362a6b5cf33ccf07ab04bb45f2a3d5320a98.js:50g.handle

A bit more of context, please?
...when do you get the error?
After doing what?

I land on the change password route, I fill in new password (twice) and click the button that's when I get the error

Lets try to debug this block of code in your browser (put a bearkpoint on the first line...).
And try to see what you get on this line for AccountsTemplates.paramToken and password...

Accounts.resetPassword requires two strings

You can see the issue here - https://xstaging.goplatfarm.com/#!forgot-password
<EMAIL_ADDRESS>

I'm having no luck debugging this, you can see the error here  - https://xstaging.goplatfarm.com/#!reset-password/lVAjYl5iqapjQipWFWMok85CPwWifUu7H8sziI9h3HS

I've just tried with your link...
...and it worked! :-)
I was able to see the Email sent! message for a couple of seconds then a redirect to /dashboard took place.
...I'd suggest to redirect to / thereafter, so to show the normal login form without the Must be logged in! error message.
AccountsTemplates.configureRoute('forgotPwd', {
    redirect: '/',
});

That's not the issue, it sends the reset password email but once you get the email click on the link, go to the change password page you can't change the password you get that error in the console

Attached gif, not sure how to make it any clearer

Sorry I got lost...

the problem is AccountsTemplates.paramToken is undefined!
if you head to https://useraccounts-bootstrap.meteor.com/reset-password/lVAjYl5iqapjQipWFWMok85CPwWifUu7H8sziI9h3HS open up browser's console and type AccountsTemplates.paramToken you'll see to token taken from the URL.
if instead you head to https://xstaging.goplatfarm.com/#!reset-password/lVAjYl5iqapjQipWFWMok85CPwWifUu7H8sziI9h3HS and do the same, you'll get undefined...

this must be a problem with the route path which is defined here as /reset-password/:paramToken.
The paramToken value is the picked up here.
...the curious thing is that Router.current().params.paramToken works fine in both cases...
Please try to debug this considering you're using appcache which changes the URLs...

I tried your settings with my changes within a local app, also adding appcache.
And everything seems to work for me...

Just tested your changes still not working you can test it  https://xstaging.goplatfarm.com/

Just tested it locally again still getting the same console error
Uncaught Error: Match error: Expected string, got object

When I test it by AccountsTemplates.paramToken I'm getting null

I'm thinking it might be better to use "Router.current().params.paramToken" as this seems to work on my end when I test.
I think something is causing a conflict with the URL not sure what it is maybe a package I checked all the routes I don't have reset-password router set anywhere.
Is there way for me to hardcode or set a workaround that would use "Router.current().params.paramToken"

Lets try this:

go to your app folder
mkdir packages && cd packages
git clone https://github.com/meteor-useraccounts/core.git
 cd..
put a console.log('setting paramToken to ' + this.params.paramToken); just before this line
put a console.log('clearing paramToken!!!'); just before this line
meteor
test the reset-password form...

I bet there's something with your IR configuration that causes the onStop callback to be called...

I did the following and run meteor add useraccounts:core and run meteor remove useraccounts:bootsstrap
But now I get -
Couldn't find a template named "fullPageAtForm" or "fullPageAtForm". Are you sure you defined it?
If I leave useraccounts:bootstrap I'm not seeing the console logs

I added the bootstrap package locally, and tested still getting the console log. It seems the error hits before the log.

I'm running a test before the error hits, at at_pwd_forms.js
before
return Accounts.resetPassword(AccountsTemplates.paramToken, password, function(error) {
I'm seeing that console.log(AccountsTemplates); has no object or paramToken or anything with hash

Been testing it some more it seems that the onRun in core.js (https://github.com/meteor-useraccounts/core/blob/98aa2a8471dfb25bbc70e38288ac427ea3e95a19/lib/core.js#L721)
is never being run, if I move / add  AccountsTemplates.paramToken = this.params.paramToken; to the onBefore hook it's fine and works. Still not sure why it's happing. Will do a pull request

Never mind can't create a pull request, it's not open. Here is a gist with the fix https://gist.github.com/almogdesign/15d770ee2873f2d525b2

Same issue as here - https://github.com/meteor-useraccounts/core/issues/410#issuecomment-107200253 onRun hook not firing

@splendido hi have you had a chance to check the onRun hook issue?

pushing out 1.11.1 right now, let me know if it works!
tnx!

Tested works perfect thanks for the great support


RQA trend results for certain orbits are empty

The RQA trend for the orbits 014, 036, 044, 045 seem to be empty on tile EU_E048N014T3 for 2019.
I am not sure, whether this is something that failed in my processing or whether the data is empty in the first place.
I should run countvalid on the data cubes and check whether this is also completely empty.
If that would be the case this is something that should be upstreamed to the EODC.

Maybe the threshold was very insensitive and didn't detect any change?

This is before applying the threshold on the trend significance and I would also expect then to get some value and not missings at all positions.


Windows processes are started with a lower process priority class

Description
Linux builds are spawned with normal niceness
Windows builds are spawned with BelowNormal process priority.
This causes issues in systems that expect it to be normal upon launch.
Platforms affected

[ ] Azure DevOps
[x] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[X] Windows Server 2019
[X] Windows Server 2022

Image version and build link
See repro: https://github.com/Cyberboss/actions_testbed/actions/runs/5159892878
Is it regression?
Unknown
Expected behavior
Processes run at Normal priority
Actual behavior
Processes run at BelowNormal priority
Repro steps
There's a repro workflow here: https://github.com/Cyberboss/actions_testbed/blob/main/.github/workflows/windows_process_priority_fail.yml
Results: https://github.com/Cyberboss/actions_testbed/actions/runs/5159892878
Workarounds
Processes seem to be able to change this, so they can fix it themselves. See https://github.com/tgstation/tgstation-server/commit/50c657ea32bfe76655599dd90f45f4af408ad050

░░░░░░░░░░░░▄▄
░░░░░░░░░░░█░░█
░░░░░░░░░░░█░░█
░░░░░░░░░░█░░░█
░░░░░░░░░█░░░░█
███████▄▄█░░░░░██████▄
▓▓▓▓▓▓█░░░░░░░░░░░░░░█
▓▓▓▓▓▓█░░░░ Github, ░░░░░█
▓▓▓▓▓▓█░░░░Fix This░░░░░█
▓▓▓▓▓▓█░░░░Please!░░░░░█
▓▓▓▓▓▓█░░░░░░░░░░░░░░█
▓▓▓▓▓▓█████░░░░░░░░░█
██████▀░░░░▀▀██████▀

Hi @Cyberboss,
We will check this behavior

Hey @Cyberboss. This behavior is caused by the way how runners provisioning works. Worker process itself runs with PriorityClass BelowNormal and this is unlikely to be changed.
If you need your process to run with higher priority you can either:

Set priority class for the current step using this command in the beginning of your script:[System.Diagnostics.Process]::GetCurrentProcess().PriorityClass = [System.Diagnostics.ProcessPriorityClass]::Normal

Set priority class for all the upcoming steps by changing class for Worker process:- name: Set Priority Class for Runner.Worker
  shell: powershell
  run: |
    (Get-Process -Name "Runner.Worker").PriorityClass = [System.Diagnostics.ProcessPriorityClass]::Normal

Well, I'm closing this issue. Feel free to reopen it or create a new one if you still have questions or experience other problems.


Add parser.load()

This does several important things:

Adds parser.load() and parser.load_many(), which parse from disk (they don't really take advantage of this for performance, but we can make it do so now).
Adds document::load(), which mirrors document::parse() and shortens examples nicely
Adds padded_string::load() to read from disk, for those who want to keep the corpus around
Makes padded_string::load() return error codes instead of throwing (uses the result pattern becoming pervasive across our API)
Deprecates get_corpus and replaces all examples
Documents padded_string and moves its implementation into include/simdjson/inline/padded_string.h

You'll notice the line count getting smaller in a lot of the get_corpus uses, because they had to do a lot work and weird swap()s to handle things with exceptions, and with padded_string::load() it can use the auto [p, error] pattern.
Along with the auto-allocation patch this builds on, this makes the simple case look like this:
document doc = document::load("jsonexamples/twitter.json");

Or this:
document::parser parser;
const document &doc = parser.load("jsonexamples/twitter.json");

As always, error chaining, and the choice of error codes vs. exceptions, are entirely within the user's choice.
Fixes #522.

I also went ahead and added error tests to test for IO_ERROR as well as CAPACITY, as well as error chaining. Error chaining (which is worth making pervasive IMO) lets you write several statements before checking the error--and still doesn't require exceptions. Sort of a middle ground when you are running without exceptions, allowing you not to check the error on every single operation:
    document::parser parser;
    auto [val, error] = parser.load(file)["foo"].as_uint64_t();
    if (error) { cerr << error << endl; exit(1); } // Will report file not found, invalid  JSON, nonexistent field "foo", or incorrect type for "foo"

I did not make error chaining work on document::load(), because I'm dreadfully frightened that C++ is going to free the document here (someone convince me otherwise!):
// Will the result of document::load() live through ["foo"] and .as_uint64_t()?
auto [val, error] = document::load(file)["foo"].as_uint64_t();

I did not make error chaining work on document::load(), because I'm dreadfully frightened that C++ is going to free the document here (someone convince me otherwise!):

Let me quote the reference:
"All temporary objects are destroyed as the last step in evaluating the full-expression that (lexically) contains the point where they were created, and if multiple temporary objects were created, they are destroyed in the order opposite to the order of creation. This is true even if that evaluation ends in throwing an exception."
So if a temporary value is created byte document.load when calling "document::load(file)["foo"].as_uint64_t()", it will get destroyed after the as_uint64_t called is finished.

In that case, it's probably not introducing any worse issues than we currently have. I'll add it before checkin.

Added the feature, and this test:
document::parser parser;
auto [val, error] = parser.load(NONEXISTENT_FILE)["foo"].as_uint64_t();
ASSERT_ERROR(error, IO_ERROR);


Fix browsersync

I believe the main issue was monkey-hot-loader, which I just removed since the original repo has been abandoned and the fork we were using didn't seem like it was likely to be maintained either.
Just read commit messages for other changes that were made.

We the people


Overkill on delete cascade + Project Custom SMTP

Describe the bug
Two things:

I feel like some on delete cascade constraint in the database are way too overkill. One example that occur to me, and was really confused about it, was the Status Page, when having a ProjectSMTP mail subscriber, and bu deleting that Project SMTP, instead of not having a mail subscriber in the status page, you just dont have a Status Page anymore
Project SMTP doesnt seem to override Global SMTP

To Reproduce

Setup yourself a Project Custom SMTP and a Global Custom SMTP that are both different. Invite someone to your team, and look which SMTP is used
Create a Status Page, Go to View this status Page > Subscriber Settings > Custom SMTP. Set your previously made Custom SMTP. Delete hat previous made SMTP

Expected behavior

For the invite team member, it should use the project SMTP instead of Global as it should override the Global
For the Status Page, deleting the Custom Project SMTP linked to the Subscriber Settings should just remove the SMTP from the status page. Not the entire page.

Deployment Type
Self Hosted OneUptime version 7.0.2666

This is fixed! I've also removed the cascade from other places as well. Please upgrade your cluster.


[snapshot] Add iPhone 11 series devices to reports_generator

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context

This pull request closes #15326 by adding support for iPhone 11 series to reports_generator.
Description
The problem (iPhone 11 series devices not showing up in HTML reports) was resolved with a straightforward extension of xcode_9_and_above_device_name_mappings.
Testing Steps
Can be easily tested by including iPhone 11 (Pro, Pro Max) in Snapfile, running fastlane snapshot and verifying they are now included in screenshots.html

@googlebot I signed it!

@googlebot I fixed it.

Yay, thanks for creating this PR @stephanmantler 🚀


Moon activity: css fix in chrome mobile version

Issue reference: #1576
Before fix:

After fix:

Kindly review it.
@llaske

Not pertinent. See comment on the issue.


fix: Use admin-cli to make admin calls to Keycloak

Description
The goal here is to use Keycloak ADMIN REST API to make admin calls like fetching users which were doing with the user's token at the moment. This is bad. Its better to use an admin token that the server creates at runtime when necessary.
Closes #30
Type of Change
Please delete options that are not relevant (including this descriptive text).

[x] 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 not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Added some tests locally.
Checklist: (Feel free to delete this section upon completion)

[ ] I have performed a self-review of my own code
[] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] My code follows the style guidelines of this project (I have run yarn lint)
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes (I have run yarn test)
[ ] My changes generate no new warnings
[ ] Any dependent changes have been merged and published in downstream modules

:tada: This PR is included in version 1.2.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[WebApplication] - Write unit tests for code writen thus far

As a car driver, I want the peace of mind that all code has been automatically tested so that I can relax while driving.

Commits 79725ce, and d84de52 has resolved this issue.


File history with VSTS API

Hi,
I'd like to use VSTS history feature that shows all renamings for a file. It works well in web GUI, but I can't make use of it through API.
I use the following API: https://docs.microsoft.com/en-us/rest/api/vsts/git/commits/get commits?view=vsts-rest-4.1. It works well when I query commits by a recent filename. If I try to query commits by filename existed in the past (e.g. before a renaming) VSTS returns "The item  could not be found in the repository".
In another words, how to reproduce: "git log --follow -- " with VSTS?
Might it be an error or it's just my misconception?

VSTS currently needs to resolve the path at the tip commit so we can get the exact casing for the path and canonicalize it (i.e. convert "a\b.txt" to "a/b.txt", unless there is actually an item named "a\b.txt").  The underlying file history algorithm is case-sensitive and assumes exact paths but humans are really bad at typing exact paths.
We could probably just fall back to using the path verbatim if it doesn't exist at tip.  I'll pass this on.
Note that this behavior isn't technically specific to renames or --follow.  core/official/upstream "git log" works for files deleted at tip even if you don't use --follow
mkdir del
cd del
git init
echo a > a.txt
git add .
git commit -m a.txt
git rm a.txt
git commit -m del
echo b > b.txt
git add .
git commit -m b.txt
git log -- a.txt <- shows history of a.txt even though its deleted
git log -- A.txt <- empty history (it's case sensitive, as I would expect, even w/ core.ignorecase=true)


HibernateDomainExporter and inheritance with composite-id

Modifications required to produce compilable code as described in https://github.com/querydsl/querydsl/issues/1459 .
The change did not break existing unit tests.

@vveloso Thanks for the PR! Could you also add a test case that fails without your fix?

Also could you use a more descriptive commit message?

I'm not sure what would be the best way to test this. I don't like to assert on text output, but it may well be what's required in this case. I'll take another look at the existing test cases to figure out how to go about building a new test case.

If you add your source that didn't compile at first (or at least the relevant parts) to the test sources, then it will be processed, if there is a regression it will not compile as before.
Does that sound like something that you can do?

@Shredder121, I hope that this is what you meant. If not, it still seems to work: if the change I made to EntitySerializer is removed the Java code generated by the unit test will not compile.

... if the change I made to EntitySerializer is removed the Java code generated by the unit test will not compile

That is exactly what I meant, then if (for some reason) the logic is changed in such a way that the code doesn't compile anymore we'll know about it.

All spaces in the right places (hopefully).

Sorry about the accidental close&reopen.
@timowest I hope that the latest commits address your concerns.

Looks good. Could you also provide a PR for the master branch?

To me it also looks good, so if the master counterpart could be created it is fine to merge.

@timowest I just created the PR for the master branch (#1509).

Looks good to me. Thanks for the PR @vveloso!


@export_category("") name Strings cause conflicts with like Class names and Autoloads

Godot version
4.1.1 Stable
System information
Windows 11, RTX 3070TI, Vulcan
Issue description
This may or may not be a bug, but definitely needs some kind of detection or warning build into the code if it is intentional or unavoidable.
After bashing my head against a wall today trying to figure out why a single specific script would not utilize referenced autoload function/methods and trying to figure out why it was the only script that would not recognize the autoload class, I realized that I had an organizational @export_category() at the top using the same name. Apparently this means that any future references to that same string will not properly reference the class or autoload.
Example:
Having an autoload script named "Debug" with a method "draw_cube()" in it.
Then in another script having a parameter organizer like such:
@export_category("Debug")
@export_range(0.0, 1.0) var debug_polyline_pos : float = 0.0

and then later attempting
Debug.draw_cube(Vector3.ZERO, Vector3.ZERO, 2.0, Color.PURPLE)

in that same script will result the inability for the game to recognize Debug as the autoload script and will not find the .draw_cube() method.
This may be expected/intentional behavior, but if that is the case this definitely needs to be outlined and/or flagged in the script-editor as a conflict.
Also as a side note, I love the fact the export_category("Debug") specifically has a little built-in easter-egg for using the term "Debug" so if there's anyway we can keep that around or maybe even expose the ability for users to control that little icon that would be pretty amazing!

Thank you for reporting, this has been reported previously and resolved in #78254, which has not been cherry picked yet

Duplicate of:

https://github.com/godotengine/godot/issues/67865
https://github.com/godotengine/godot/issues/73843


Ui border is 1 pixel too large, or is getting aliased.

Bevy version
Main, commit 0ec634763ec378193eeea0cc38909e7d7251b272
Relevant system information

Windows 11
Rust Nightly, 1.80.0 (8387315ab 2024-05-14)
Also tested on Rust Stable, 1.78.0 (9b00956e5 2024-04-29)

AdapterInfo { name: "NVIDIA GeForce RTX 2080 Ti", vendor: 4318, device: 7684, device_type: DiscreteGpu, driver: "NVIDIA", driver_info: "555.85", backend: Vulkan }

What you did
Create a NodeBundle with a 1 pixel wide border on all sides.
What went wrong
The border appears to be 1 pixel too large on all sides, or is getting aliased, causing it to blend into the node's background. I would expect a 1 pixel border to be exactly 1 pixel on the screen(see the 0.13.2 screenshot below).
This gist reproduces the issue on commit 0ec6347.
And this gist does not show the issue on 0.13.2.
Possible Fix
I'm not at all fluent with shader code, but while poking around in ui.wgsl, I found that on line 161, changing external_distance < internal_distance to external_distance > internal_distance fixes the issue. After doing that, the border appears exactly the same as the 0.13.2 screenshot below. I have no idea what the implications are for making that change, so it may very well break other things.
True scale:

Scaled up to highlight issue:

Expected(using bevy 0.13.2):

could you try before and after https://github.com/bevyengine/bevy/pull/12725?
commit before: debcf3fb1d0c8e0b259a3ea852eca7f702b7c21d
commit with that PR: 8da4fcb6167ced2aaa89cb92c4420d3be7eb0591

The issue still exists on both of those commits, with debcf3f looking slightly different.

#12500, commit e7a31d0 has this issue.
The commit before that PR, 7c7d1e8, does not.

looking into this rn. I think there's a bug with how the sdfs are calculated. Visualizing external_distance(left) and internal_distance(right).

We see a darker red around the external_distance. It being darker is saying that the outside pixel is half in and half out of the border, but it should be bright red saying that the outside pixel is fully part of the border.

getting close. left is the border distance and right is the fwidth(border_distance). The border_distance looks correct, but the fwidth(border_distance) looks weird, which is making artifacts in the final rendering.

looks like something weird is going on on the diagonals of the sdf

I think I got it. Will do a little more testing tomorrow and then open a pr.

Thanks for working on this issue! That looks much better, but there is still 1px of the border bleeding into the middle on some sides of some of those squares. It is visible only on the top right black/white square, the 2 green/orange, and the 2 purple/yellow squares. Is this an artifact caused by the screenshot?

Not an artifact. Here's a blown up screenshot.

For this I changed border_distance to be
let border_distance = select(external_distance, -internal_distance, internal_distance <= 0);

Which is more correct than it was before, but probably still a little wrong. I'll see if I can come up with a better formula.

Darn above formula is still pretty wrong. The red area should be darkening again in the below screenshot.

Using
    let border_distance = select(max(external_distance, -internal_distance), -internal_distance, internal_distance <= 0);

got me

just some single pixel artifacts left in the corners.


SendAsync() does not clean "To"

I have the need to send multiple emails with different templates to many recipients. I would expect something like:
foreach (var notification in emailNotifications)
{
    await _fluentEmail
        .To(notification.ToAddress)
        .Subject(notification.Subject)
        .UsingTemplate(template, notification)
        .SendAsync();
}

... To send one email to one person successively
What actually happens when this code is executed, is that the first recipient gets an email addressed to them, then the second gets sent to both the first and the second email, then it continues until the foreach ends
This caused an interesting situation where everyone got spammed down by emails this morning

Maybe a "SendAndClear()" method, would be appropriate

The email factory is the supported way to handle this calling FluentEmailFactory.Create() will give you a fresh email to send. I am considering throwing an exception when you try to send the same email twice.

@lukencode this is not really expected at all and you should really update your documentation with a HUGE red warning banner - this is EXTREMELY dangerous - (imagine password reset emails going out to multiple people?!?)!
TBH you should probably deprecate IFluentEmail and make FluentEmailFactory the standard as I do not understand why would ever want the OPs behaviour.


initial commit

Fixes #53
Description
Redesign the current version of CC’s platform toolkit webpage so that it looks clean and contemporary.
Other information
In the Figma file with my redesign, I did not include the content from the current version of the CC's platform toolkit page that I would not change much and that would be exactly the same design as the content I included.

@AndrejaP I cannot see the Figma file. Could you upload it somewhere else and post the link here? (I assumed that the design would be HTML/CSS when I specified the instructions as making a pull request).

@kgodey Oh sorry, I never pushed a Figma file to GitHub before. I will code it in HTML, CSS and Javascript and make another pull request when I'm done.

I don't mind just looking at the Figma design if you can send it to me another way.

Ah, ok. I committed a pdf file of the design to my forked repository. I am not sure if I should make a pull request again. I am currently coding the 10 FAQ. I don't mind coding this one too, if there is time.

I'd recommend focusing on your final application after one contribution.

Thanks a lot for the recommendation. I will try again next time, I feel I need to upgrade my skills to be able to contribute better. I gained some useful knowledge in the process.

 You are welcome to keep contributing as well, the recommendation for the final application was because the deadline is coming up soon. If you're not applying for Outreachy, we hope that you'll still stick around!

Thank you. I will!

Since the Outreachy application period is over, I'm going to close this PR.


is model ready when Fine-tuning in distributed case

When we finetune a model on a different task, only a part of vars in the model are restored from the pretrained task and others are left as initial values.
As many docs recommends(page1 page2), when training with a local graph, we restore the pretrained model after running the global init op(call restoring in "init_fn" if MonitoredSession or supervisor is included).
But in the distributed case, does global init op make "model_ready" returns true before the restoring-model called? other non-chief nodes will use the "not ready" values.

codes in "prepare_session" of "SessionManager". After " sess.run(init_op)", the "wait_for_session" nodes will get true for "_model_ready", but init_fn have not finished.
    if not is_loaded_from_checkpoint:
      if init_op is None and not init_fn and self._local_init_op is None:
        raise RuntimeError("Model is not initialized and no init_op or "
                           "init_fn or local_init_op was given")
      if init_op is not None:
        sess.run(init_op, feed_dict=init_feed_dict)
      if init_fn:
        init_fn(sess)

    local_init_success, msg = self._try_run_local_init_op(sess)
    if not local_init_success:
      raise RuntimeError(
          "Init operations did not make model ready for local_init.  "
          "Init op: %s, init fn: %s, error: %s" % (_maybe_name(init_op),
                                                   init_fn,
                                                   msg))

    is_ready, msg = self._model_ready(sess)
    if not is_ready:
      raise RuntimeError(
          "Init operations did not make model ready.  "
          "Init op: %s, init fn: %s, local_init_op: %s, error: %s" %
          (_maybe_name(init_op), init_fn, self._local_init_op, msg))
    return sess

This question is better asked on  StackOverflow since it is not a  bug or feature request. There is also a larger community that reads questions there. Thanks!

I'm wondering is this a bug


How to set paddingRight on slide container?

Hey there! I have a carousel where I'm trying to eliminate the paddingRight after the slides:

I tried specifying the contentContainerStyle with something like paddingRight: 20, like so:
<Carousel
	{...props}
	ref={c => {
		this._carousel = c;
	}}
	layout={"default"}
	renderItem={this._renderItem}
	sliderWidth={sliderWidth}
	itemWidth={itemWidth}
	loop={false}
	inactiveSlideScale={1}
	inactiveSlideOpacity={1}
	activeSlideAlignment={"start"}
	containerCustomStyle={{ paddingRight: 20 }}
/>

... but it looks like _getComponentStaticProps overrides any padding specified in the contentContainerStyle prop:
const contentContainerStyle = [
    contentContainerCustomStyle || {},
    vertical ? {
        paddingTop: this._getContainerInnerMargin(),
        paddingBottom: this._getContainerInnerMargin(true)
    } : {
        paddingLeft: this._getContainerInnerMargin(),
        paddingRight: this._getContainerInnerMargin(true)
    }
];

To try this out, I swapped paddingRight: this._getContainerInnerMargin(true) with paddingRight: 20, and achieved my ideal result:

I'm newer to React overall – is there any way I can get around this to manually specify the paddingRight value I'm hoping for? 😄
Thanks so much!

@tgmcguire Unfortunately, by doing so you might have messed with the inner logic of the carousel. Is onSnapToItem(index) still called with the proper index and at the right time?
If yes, then you're clearly onto something ;-)
If no, please see this comment and the follow-up discussion.

Closing as no further feedback has been provided.


Prevent non-validated users from appearinng in lists

Currently you can find non-validated users via search, or see them as followees.

We should fast lane this.


MMS - is automatic language detection a thing with MMS? The mms_infer.py requires a language input to work

What is your question?
How to auto-detect a language from the mms_infer.py?
Code
Running
python asr/infer/mms_infer.py --model mms1b_l1107.pt --audio output_audio.mp3
shows
the following arguments are required: --lang

i have same issue. If not automatic, is there at least a way I can give multiple language inputs, eg eng & hin.

We currently don't support automatic language detection given a speech. But you could use the LID to detect the language and put the predicted language code into inference script (but check if ASR support those languages or not from README table)

We currently don't support automatic language detection given a speech. But you could use the LID to detect the language and put the predicted language code into inference script (but check if ASR support those languages or not from README table)

Thanks for the comment @androstj , could you elaborate on what "use the LID" means?

LID is Language Identification. Check our readme section MMS LID


More descriptive identifiers in scenario unit tests

This is a readability improvement inspired by a conversation in #1734, in which it was suggested to use a better identifier name than x for use in assertions.
While not an exhaustive change, it is hopefully incremental change for the better.

Great, thanks!

Hi, can you have a look why this test is failing in https://travis-ci.com/ansible/molecule/jobs/179269177 ?
test/functional/docker/test_scenarios.py::test_command_side_effect[side_effect-docker-default] FAILED


On https://prod-preview.openshift.io/ the space homepage includes a description field for the space

The user is not given an opportunity to write text into the field.

@ldimaggi - is that one of your Spaces or someone else's? If it is your's, then you can edit it. Hover over the description field and a pencil will pop up. Just click inside to edit and click outside to save.
Users who did not create the Space cannot edit the Description.

Adam is correct!


Allow Appenders and Handlers to pass a zero length message to network

This change allows both Appenders (org.apache.log4j.Appender) and Handlers
(java.util.logging.Handler) to send zero length and null messages to
a remote destination. Previously both zero length and null messages were
pruned out in GelfMessage class.
Though pruning out empty messages makes sense in terms of saving (some)
network traffic, it's kind of counterintuitive for several reasons.
To begin with, those who are familiar with other implementations expect
to see an empty message to get passed along. E.g. o.a.l.ConsoleAppender,
o.a.l.FileAppender, j.u.l.ConsoleHandler, and j.u.l.FileHandler all
allow a zero length/null message to be passed on.
Additionally, an Appender/Handler implementation is not supposed to
prune out any messages, besides invalid ones which simply can not be
passed due to missing information. In this case an empty message is
not something that prevents it being sent, as long as other GELF
parameters are all right. If additional filtering is needed, that should
go in org.apache.log4j.Filter or java.util.logging.Filter implementation
respectively.
Finally, there is a use case for sending empty messages as well. Some
developer might want to do log.info(thisStringIGotPassed), and should
the string be empty, it'd be reasonable to expect an empty log entry
appear, instead of receiving an error "Could not send GELF message".
References:
https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Appender.html
https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/spi/Filter.html
https://docs.oracle.com/javase/7/docs/api/java/util/logging/Filter.html
https://docs.oracle.com/javase/7/docs/api/java/util/logging/Handler.html

Hi @samilaine,
I appreciate the effort you put in this pull request. It's a great example of how collaboration should be done!
Thank you.

Hi @samilaine,
Version 1.1.14 with your pull request released.
Thanks again for your help.
Anton

The pleasure was all mine. Thank you for putting Gelfj together.


Make advisoriesPath option configurable

In order to support a better offline experience, the advisoriesPath option
needs to be configurable so that the advisories.json file can be placed in
a directory that will persist across multiple runs (for CI purposes).

This works. Going to also add in --advisoriesPath support for cmd line usage.


Make the ObservedObjectParent public via the BaseSpatialObserver class

This change addresses #9907 by moving the implementation of the ObservedObjectParent property into the BaseSpatialObserver class. This avoids introducing a breaking interface change at the expense of requiring application code to cast to the base class if access to a specific observer's observation parent game object is desired.
Here is an example of how to acquire the object
IMixedRealityDataProviderAccess providerAccess = CoreServices.SpatialAwarenessSystem as IMixedRealityDataProviderAccess;
if (providerAccess == null) { return; }

List<GameObject> observationParents = new List<GameObject>();
foreach (IMixedRealitySpatialAwarenessObserver obs in
             providerAccess.GetDataProviders<IMixedRealitySpatialAwarenessObserver>())
{
    BaseSpatialObserver observer = obs as BaseSpatialObserver;
    if (observer == null) { continue; }

    observationParents.Add(observer.ObservedObjectParent);
}

Fixes #9907

/azp run

/azp run

/azp run


Add build task to copy StaticWebAssets.xml of module

Blazor needs the file <Module Assembly>.StaticWebAssets.xml from module to load the assets.
During build the file for the module itself is not copied to output directory of referencing apps.
This is ok in a "normal" web app, but as in Hosuto each module will use the module assembly name as application name (this is a requirement of razor and some other aspnetcore feature).
Current workaround is to copy the missing file from the module directory to all apps using the module. However it would be better when this could be automated with a build task.

Found a better way, that should work for most use cases.
See #26 how to add the static assets of host to Module. Will only work for Development Environment (like in default ASP.NET Core WebHostBuilder).


npm run build failed when importing a ckeiditor build file from the working dir.

build/
  ckeditor.js
  ckeditor.map.js
Main.jsx

Inside Main.jsx I import the build file import ClassicEditor from './build/ckeditor'
It works correctly, but when I run npm run build it throws an error, Attempted import error: './build/ckeditor' does not contain a default export (imported as 'ClassicEditor').
I think the problem is npm run build tries to build an already compiled file, ckeditor.js. So how to import compiled files without building it?

If it's a ES6 module, you could try dynamically importing it instead:
import(`./build/ckeditor.js`).then(ClassicEditor => {
  ...
});

Alternatively use the npm package @ckeditor/ckeditor5-build-classic

thanks @petetnt , this is a custom build which adds a mathtype plugin that @ckeditor5/ckeditor5-build-classic doesn't have.


Dap debug failed with: Adapter doesn't support chosen strategy

I use neotest-go and neotest-rust,  when I hove to the test function and run:
require("neotest").run.run({strategy = "dap"})
it prints:
Adapter doesn't support chosen strategy

I have setup dap already and it works with my main entry.

I have now the same issue with C#. Previously everything worked fine. Is the a problem of neotest or from neotest-dotnet or is it my config?

This is because neotest-dotnet changed its dap implementation, this should be fixed soon with recent changes to neotest.
See https://github.com/nvim-neotest/neotest/discussions/24#discussioncomment-5641606


sdf.plugin bolt diameter size calculation

Hi,
I'm a student and I'm trying to use MuJoCo for assembly nut-bolt with a ur5 manipulator.
I'm looking for some help with the  correct calculation of diameter size of the bolt and the nut,
how to calculate the outside diameter and inside diameter of the bolt?,
I would have a outside diameter=20mm, but after many attempts, i dont get the correct diameter. instead i get a size more than 20mm of diameter. It also happens with the nut.
i wonder if there is a formula  i ignore that helps to calculate  the exact input diameter.
regards

I would suggest to look at the code https://github.com/google-deepmind/mujoco/blob/main/plugin/sdf/nut.cc#L33 if you need and interactive visualization you can use https://www.shadertoy.com/view/XtffzX which is where I took the initial SDF from.


Questions about the sparsity

Hi, thanks for your great work!
I tried to visualize the sparsity for the models you mentioned in the paper, including other models like Qwen-moe, and have some questions.

GQA models generally have lower sparsity than MHA models, especially for Mistral-series and llama3.1. Have you verified the accuracy of duo-attention on those models, since I only find the results for Llama-2-7B-32K-Instruct and Llama-3-8B-Instruct-1048K.
The distribution of streaming heads here seems to disobey the insight from papers like pyramidkv, which found deeper layers have higher sparsity, cause most of streaming heads of GQA models are found in lower layers.

btw, I also noticed that Llama-3-8B-Instruct-1048K suffered obvious loss on some sub benchmarks of Longbench, for example, lsht and vcsum. But other sub benchmarks seem to be lossless, maybe use lower sparsity would recover the precision.

Thank you for your interest in our work and for applying it to additional models! Here are my responses to your questions:

Yes, I’ve tested DuoAttention on other GQA models like Mistral and Llama-3.1, and the findings are consistent with those from Llama-3-8B-Instruct-1048K.
If I understand correctly, PyramidKV relies on a human-designed heuristic to allocate the KV cache across layers, which is not necessarily the optimal strategy.
Indeed, DuoAttention shows more noticeable performance losses on some benchmarks. Reducing sparsity can help mitigate these losses.

Got it, thanks!


Missing JDK 17 packages from deb/rpm repos.

Some while ago the Adoptium (then AdoptOpenJDK) team published official DEB/RPM repos:
https://medium.com/adoptopenjdk/adoptopenjdk-rpm-and-deb-files-7003ba38144e
These work fine up to 16, but there are no packages for 17.

This is being worked on see installers repo issue 330


Suggestion for Multiplayer Games row -- Add "Edit Game" option next to "Host Game"

Add another CTA here:

Similar to what we have in the Community Games feed:

This might be good to add as otherwise teachers might think our platform is just encouraging playing.


Remove null pointer exception on isEqualTo for DateTimes

+1
I guess it would be nice to do the same for isIn and isNotIn.

Integrated, thanks.


tensorflow 2.9.1-gpu error kernel driver does not appear to be running on this host

Click to expand!
Issue Type
Build/Install
Source
binary
Tensorflow Version
2.9.1-gpu
Custom Code
No
OS Platform and Distribution
Ubuntu 18.04.1
Mobile device
n/a
Python version
3.8.10
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Tensorflow 2.9.1-gpu is installed from Dockerfile.

Why is the kernel driver missing in the host if the image is gpu support "tensorflow/tensorflow:2.9.1-gpu"?

Standalone code to reproduce the issue
tf-docker /app > python3
Python 3.8.10 (default, Jun 22 2022, 20:18:18)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

>>> import tensorflow as tf
2022-09-20 14:11:26.407642: I tensorflow/core/util/util.cc:169] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable `TF_ENABLE_ONEDNN_OPTS=0`.

>>> print("Num GPUs Available: ", len(tf.config.list_physical_devices('GPU')))
2022-09-20 14:11:47.727435: E tensorflow/stream_executor/cuda/cuda_driver.cc:271] failed call to cuInit: UNKNOWN ERROR (34)
2022-09-20 14:11:47.727516: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:156] kernel driver does not appear to be running on this host (mv-inference-5f7d446b77-kmsxn): /proc/driver/nvidia/version does not exist
Num GPUs Available:  0

>>> print(tf.__version__)
2.9.1

Relevant log output
No response

Hi @dcvtruong, You need to install CUDA and cuDNN to use GPU.
Install CUDA and cuDNN with conda.
conda install -c conda-forge cudatoolkit=11.2 cudnn=8.1.0
Configure the system paths. You can do it with following command everytime your start a new terminal after activating your conda environment.
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$CONDA_PREFIX/lib/
Thank you!

Hi @gadagashwini,
CUDA and CUDNN is installed.
tf-docker /app > nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2021 NVIDIA Corporation
Built on Sun_Feb_14_21:12:58_PST_2021
Cuda compilation tools, release 11.2, V11.2.152
Build cuda_11.2.r11.2/compiler.29618528_0

tf-docker /app > ldconfig -p | grep cudnn
	libcudnn_ops_train.so.8 (libc6,x86-64) => /lib/x86_64-linux-gnu/libcudnn_ops_train.so.8
	libcudnn_ops_infer.so.8 (libc6,x86-64) => /lib/x86_64-linux-gnu/libcudnn_ops_infer.so.8
	libcudnn_cnn_train.so.8 (libc6,x86-64) => /lib/x86_64-linux-gnu/libcudnn_cnn_train.so.8
	libcudnn_cnn_infer.so.8 (libc6,x86-64) => /lib/x86_64-linux-gnu/libcudnn_cnn_infer.so.8
	libcudnn_adv_train.so.8 (libc6,x86-64) => /lib/x86_64-linux-gnu/libcudnn_adv_train.so.8
	libcudnn_adv_infer.so.8 (libc6,x86-64) => /lib/x86_64-linux-gnu/libcudnn_adv_infer.so.8
	libcudnn.so.8 (libc6,x86-64) => /lib/x86_64-linux-gnu/libcudnn.so.8

Hi @dcvtruong, Make sure you have Nvidia docker.
For GPU support on Linux, install NVIDIA Docker support. Follow the steps mentioned on the Tensorflow site. Thank you!


Exif image orientation should be handled when stripping image metadata

When using mod_pagespeed to optimize images, the exif orientation data is not taken into account, and exif data is stripped, so the image rotation is wrong when reaching the browser.
mod_pagespeed should read exif orientation data, and eventually rotate the image before optimizing it.

Thanks for the report.
Note that it is possible to disable the meta data stripping, maybe that helps in the short term: https://www.modpagespeed.com/doc/reference-image-optimize#strip_image_meta_data

thank you @oschaaf, I didn't know that. still, having the image optimized and resized, while retaining the correct orientation would be very nice.

By disabling meta data stripping I was suggesting you could achieve resizing and most optimizations on offer (only excluding the meta data stripping), and keep the orientation correct as it will be around post-optimization in the exif data — or at least I hope so.

Yes it works. Metadata is retained and the css property image-orientation: from-image; works (in browsers that support it).
example: https://fcku.it/it.comp.console/thread/3694261

Cool, thanks for sharing that.
Let’s keep this issue open, to see if we can automagically make this work at some point.

Is there any update on this issue? We have WordPress sites that would benefit from the whole resize_images module but image rotation should should be applied to the image based on the exif data.

As far as I know no, no news about this.
But you can diable strip images metadata with:
Nginx pagespeed DisableFilters strip_images_meta_data
Apache ModPagespeedDisableFilters strip_image_meta_data


"Persons" component should OR the device trackers

Home Assistant release with the issue:

0.88.0
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):

Dedicated Docker container on Linux x86_84 host
Component/platform:

https://www.home-assistant.io/components/person/
Description of problem:
According to documentation, the Person components takes the last update from the connected device_trackers to determine the Person's state (home / not_home).
If have connected my phone and my laptop to the component and shutting down my laptop makes me considered being not_home, because the laptop's state update occured last.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
person:

Traceback (if applicable):

Additional information:

Sounds like it's working according to the docs. Is this a feature request?

You can already do that by putting them in a group. A simple or is mostly incorrect (one bad tracker can mess up everything). Except for WiFi and BT tracker, last-updated value is almost always right and should be used. With the last update approach, even if there is a bad tracker, it will be ignored.

more like feature request...
in this case, priorities should be applied
e.g
I have two dev trackers for person (me):

openwrt luci device scanner check if my phone is connected to home network
google maps track my phone too...but show location <> home

If first show home and second show away, the person should return home status,
even if the status of the second tracker was updated later.
person:
  - name: User
    id: user1
    device_trackers:
      - device_tracker.phone1
        priority: 1 #higher
      - device_tracker.google_maps_11223344
        priority: 2 #lower

Generally:

device with higher priority and home status always is returned first (without comparing with lower prority trackers)
if device with higher priority have status not_home
and device with lower priority <> home and <> not_home (zone name) then return zone name for person else return not_home as tracker with higher priority

with priority is possible OR function as @m0wlheld wrote (two devices with the same priority).
it is also possible to add per tracker expiration time...

Again., as @MartinHjelmare suggested, it is more of a feature request. Additional features will come to person over time. But, what you argued is exactly what I indicated earlier. BT/WiFi tracker are less reliable compared to GPS based trackers and should be used accordingly.
Having said that, please close this issue as this is not a place to discuss features.

as this is not a place to discuss features.

Where is this place instead?


Extend Consumer to support proxied connections

Extend Consumer to allow optional WebProxy parameter to be passed into constructor
Extend all HTTP Calls to support web proxies

As discussed with Mark, a slightly different approach will be used to resolve this issue. It will involve reading the proxy settings from the framework properties (either file or database) rather than passing the values through the Consumer calls. This Pull Request will therefore be closed and the changes highlighted will be implemented in a separate Pull Request.


SVG properties support for eslint-plugin

Is your feature request related to a problem? Please describe.
eslint-plugin should supports svg properties.
Describe a solution you'd like
const styles = stylex.create({
  circle: {
    cx: '50%',
    cy: '50%',
    strokeDasharray: '100',
    fill: 'transparent',
  },
  // ...
}

Describe alternatives you've considered
// eslint-disable

I'll add it to the list of missing properties in the ESLint plugin. Thanks.

@olivierpascal Not every SVG attribute can be applied using CSS. In your example, strokeDasharray and fill should work already, but cx and cy are intentionally not supported.
cx and cy attributes can be applied with CSS in the SVG 2.0 spec. However, this spec isn't consistently applied across browsers and supporting it officially would be harmful.
Outside of this, I'm adding any missing SVG property to the ESlint rule.


catch NULL geometries created in clean

One small change to avoid clean_geometry failing on smaller domains. Test written, test data in test/testthat/data, and all tests still pass.

Codecov Report

Merging #33 (1efccaa) into main (e669fcd) will increase coverage by 0.07%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #33      +/-   ##
==========================================
+ Coverage   90.27%   90.35%   +0.07%
==========================================
  Files          11       11
  Lines        1574     1576       +2
==========================================
+ Hits         1421     1424       +3
+ Misses        153      152       -1

Impacted Files
Coverage Δ

R/catchment_geometry.R
76.51% <100.00%> (+0.99%)
:arrow_up:

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 e669fcd...1efccaa. Read the comment docs.


application still thinks it's 1.3.0

Version tag wasn't bumped for 1.3.1
https://github.com/yitsushi/totp-cli/blob/0db55f84dcad8f02a31d122495bd4a97c453dab3/internal/info/app.go#L10

Thanks. It should have been moved already to be updated on build (with ldflags).


Use load_balanced_fqdn when setting up the cluster

Propogate load_balanced_fqdn to Ansible
Run an integration test with DNS records pointing to API server with AWS Route53

I will squash before merging


KAFKA-3227; Conservative update of Kafka dependencies

Patch version bumps for bouncy castle, minikdc, snappy, slf4j, scalatest and powermock. Notable fixes:

Snappy: fixes a resource leak
Bouncy castle: security fixes

Also update Gradle to 2.11 where the notable change is improved IDE integration.

@ijuma Thanks for keeping the dependencies up to date. I check for dependency updates for my gradle projects (and checked this patch) with the below addition to my gradle file. Think that would be useful to add in a patch? If not, its useful to copy & paste when reviewing dependencies.
buildscript {
  repositories {
    jcenter()
    mavenCentral()
  }
  dependencies {
    classpath 'com.github.ben-manes:gradle-versions-plugin:0.12.0'
  }
}

subprojects {
  apply plugin: 'com.github.ben-manes.versions'

  dependencyUpdates {
    revision="release"
    resolutionStrategy = {
      componentSelection { rules ->
        rules.all { ComponentSelection selection ->
          boolean rejected = ['snap', 'alpha', 'beta', 'rc', 'cr', 'm'].any { qualifier ->
            selection.candidate.version ==~ /(?i).*[.-]${qualifier}[.\d-]*/
          }
          if (rejected) {
            selection.reject('Release candidate')
          }
        }
      }
    }
  }
}

gradle dependencyUpdates

Thanks for the review @granthenke. I used something similar to your example to check the updates myself (although yours includes an additional rule that looks useful). I would personally find it useful, if that was included in the Kafka build.

@ijuma Looking at the dependencies output I think commons-collections 3.2.1 is still pulled in transitively. Looks like the Hadoop update didn't fix miniKdc.

@granthenke It looks like the hadoop project updated its commons-collections dependency to 3.2.2[1], but MiniKDC actually has no direct dependency on commons-collections, just a transitive one. So that commit didn't fix the issue in the end. Seems like we need #564 after all.
[1] https://github.com/apache/hadoop/commit/1752fece9ccef31f4f4ed111d278c97927fc2e21

@ijuma I can re-open it if you like. Its not a huge deal since its a test dependency.

Up to you @granthenke, I think rat also seems to have a dependency on common-collections.

@ijuma That reminds me. The build script depends on an old version of grgit due to 1.6 compatibility, now that we don't need that can we update here too? (and use standard syntax)
From:
classpath group: 'org.ajoberstar', name: 'grgit', version: '0.2.3'
To:
classpath "org.ajoberstar:grgit:1.5.0"

@granthenke Updated grgit.

LGTM

Review by @gwenshap or @ewencp

LGTM


Changing the statuschange behaviour to single messages per change

Hey guys,
in #68 @hedgehog90 proposed another status change event, that he called statuschange_single, that triggers a message about a single status change whenever one happens.
At the moment there's this big status change object that looks something like this, just populated with even more properties
{
  "mute": false,
  "duration": 320,
   "media-title": "somesong"
}

and if there's a change to one single of those properties, the statuschange event returns the whole object, which could possibly have like 50 properties.
Instead of introducing statuschange_single I'm rather leaning towards replacing the old one with the new behaviour, that would return something like this
{
   "property": "duration",
   "value": 400
}

Of course, this would break the API. But since we're doing a Version 2 here anyways, which means breaking the API is kind of okay, since people migrating from Version 1 to Version 2 will have to migrate their code anyways.
What do you guys think? @vankasteelj , @AxelTerizaki and @hedgehog90. You guys seem to be the most active user of this package.

The idea is that when anything changes, that event is triggered, right? I don't see any particular problem with that. It does change app code though as we now have to test which property got changed.
I don't mind the change. I haven't been following the whole discussion which led to it though, but I don't see any particular issue with it (apart from a slight code change)

Yes exactly, if property A changed (and was observerd of course), there will be a statuschangeevent for property A.

I don't see why we can't just retain the original statuschange event and have an extra event for singular property changes, as I've proposed.
It would avoid any problems with back-compatibility.
Also, I can imagine being confused by the change in behaviour when the name of the event is the same.

It's definitely possible @hedgehog90 , but it's pretty much for the reasons @AxelTerizaki stated, simple is better and having multiple ways of doing stuff just adds a layer of confusion.
There already is a migration guide, so it's just adding the changes to that.
Big Statusobject
Pros

Everything in one place, helps people to see properties they didn't know existed
If an app keeps track of the properties, updating could be as easy as    mpv.on('statuschange', (statusobj) => {
        state = statusobj;
   });

Cons

Even if only a single property changes, the whole object is sent. The user of the library has to check if every single property did change or not, by keeping track of the state and comparing it with the new state every time

Individual Messages
Pros

an event relevant to a certain property is only fired when that property did actually change
seems like it would keep the logic cleaner, for example it could look like this    mpv.on('statuschange', (prop, value) => {
        switch(prop) {
            case "duration":
                // code
                break;
        }
    });

possiblity to add more information to a single property, for example    {
        "property": "duration",
        "value": 300,
        "timestamp": "<unix timestamp of the change>",
        "somethingelse": "foo"
    }

Cons

API change
not every observed property in one place

Anything you guys want to add?
One possibility I see is using a rename to keep the old behaviour with a warning, that it is deprecated. By that I mean, for example, the new event would be called state or status or something. Then I see if I can add a message to an event, that it's deprecated and remove it from the documentation (not yet from the code). This gives people time to transition.

I'm in 2 minds about it now as well!
I'll let you decide whether to keep it as statuschange or to rename it, it's not a huge issue either way.
Also, good idea with the timestamp property.

I implemented this and removed the old behaviour. I think it's better now, allthough it breaks the module. While doing so I also changed the way observing properties works, it no longer requires IDs by the user


Incorrect PhantomJS version installed with Homebrew

When installing CasperJS view homebrew, it installs the latest PhantomJS version (2.0.0) but that doesn't seem to be supported. I was able to install via npm for now.
Brew formula:
https://github.com/Homebrew/homebrew/blob/master/Library/Formula/casperjs.rb

It's possible. More info about support PhantomJS 2.0.X https://github.com/n1k0/casperjs/pull/1137

I had the same issue

Someone should make a PR for the given brew formula to lock PhantomJS version in 1.9.x...

I'm waiting for PhantomJS 2.0 support....
But, sadly, I didn't see any progress for a long time about it.
So, I've made PR  https://github.com/Homebrew/homebrew/pull/38632 for the lock dependency for PhantomJS 1.9.8.
If CasperJS support PhantomJS 2.0.x, please send revert PR against Homebrew.

You did well, thanks.

Thanks to @DomT4's work https://github.com/Homebrew/homebrew/pull/38681, this issue would have been resolved.
Is there anything else that would prevent us from closing this deal?

Just needs to be confirmed via clean installation of brew install casperjs --devel

I confirmed clean installation of brew install casperjs --devel:

Homebrew has PhantomJS 2.0.0
Casper Formula has PhantomJS 1.8.2 resource by itself

It seems that incorrect PhantomJS dependency issue is resolved.
% brew info phantomjs
phantomjs: stable 2.0.0 (bottled), HEAD
http://www.phantomjs.org/
Not installed
From: https://github.com/Homebrew/homebrew/blob/master/Library/Formula/phantomjs.rb
% brew install casperjs --devel
==> Downloading https://github.com/n1k0/casperjs/archive/1.1-beta3.tar.gz
######################################################################## 100.0%
==> Downloading https://phantomjs.googlecode.com/files/phantomjs-1.8.2-macosx.zi
######################################################################## 100.0%
🍺  /usr/local/Cellar/casperjs/1.1-beta3: 363 files, 11M, built in 16 seconds
% casperjs --version
2015-04-20 21:13:53.406 phantomjs[90468:d13] *** WARNING: Method userSpaceScaleFactor in class NSView is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead.
1.1.0-beta3

And minimal script http://casperjs.readthedocs.org/en/latest/quickstart.html#a-minimal-scraping-script works well (but with a few warnings...):
% casperjs sample.js
2015-04-20 21:21:55.509 phantomjs[90986:d13] *** WARNING: Method userSpaceScaleFactor in class NSView is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead.
2015-04-20 21:21:56.992 phantomjs[90986:d13] CoreText performance note: Client called CTFontCreateWithName() using name "Palatino" and got font with PostScript name "Palatino-Roman". For best performance, only use PostScript names when calling this API.
2015-04-20 21:21:56.992 phantomjs[90986:d13] CoreText performance note: Set a breakpoint on CTFontLogSuboptimalRequest to debug.
CasperJS, a navigation scripting and testing utility for PhantomJS and SlimerJS
PhantomJS | PhantomJS

You should also be able to install Homebrew/homebrew's more recent PhantomJS and it shouldn't interfere with CasperJS. CasperJS now automatically prepends the $PATH variable with its own internal version of PhantomJS during runtime.

Ah, you mean that Homebrew users can install latest PhantomJS and develop version of CasperJS at same time?
If so, this issue is ideally solved.

If not so, we need work for solving this issue....

Yup. You should be able to brew install phantomjs and brew install casperjs and they should never conflict or cross each other.

Thanks. Your proposal fix is really awesome!

It should all be fixed, but if you hit anything else funky/odd, feel free to ping me on it :).

:)

So I want to use CasperJS 1.1-beta3, but with PhantomJS 2.0.
Supposedly Phantom JS versions < 1.9.7 on Mavericks OSX throw font warnings: https://github.com/ariya/phantomjs/issues/11418#issuecomment-35010263
I don't want the font warnings in my output.  However, since
brew install casperjs --devel by default installs and uses PhantomJS 1.8.2, I don't know how to use the new CasperJS 1.1 AND PhantomJS 2.0.
I've installed PhantomJS 2.0 first, and then installed CasperJS, but CasperJS always pulls in and uses PhantomJS 1.8.2.
Is it possible to upgrade the dependency for the 1.1 Beta to use Phantom 1.9.7 or higher?

Sorry, I didn't see this till now. Super-easily you can locally modify the launcher to whichever PhantomJS you want to use. In /usr/local/opt/casperjs/bin/* you'll find a script which is just an exec script - Just change the export PATH line to your desired PhantomJS and you're golden.


still more ImageName default tag fixes

Add some more information to build.py and change_from_in_df to make it easier to determine why a
parent image isn't found on a BaseMismatchError.
Fix exit_store_metadata to not crash if a parent image is None.

Not updating release notes draft because this is bugfix to an unreleased feature.


Support horizontal pod scaling for information discovery and health discovery

Support scaling information discovery and health discovery pods to enable horizontal scaling.

Currently scaling information-discovery and health-discovery pods fails because the persistent volume claims can only mounted read write once:
Events:
  Type     Reason              Age   From                     Message
  ----     ------              ----  ----                     -------
  Normal   Scheduled           27s   default-scheduler        Successfully assigned default/health-discovery-68d59c9b5d-cllxz to ip-192-168-66-187.eu-central-1.compute.internal
  Warning  FailedAttachVolume  27s   attachdetach-controller  Multi-Attach error for volume "pvc-e9bc6287-9357-4df3-8fe3-1d56642870c6" Volume is already used by pod(s) health-discovery-68d59c9b5d-7b9lq

Persistent volumes with RMX are available to AWS EFS:
https://docs.aws.amazon.com/eks/latest/userguide/efs-csi.html


Move client creation integ tests to functional

This PR is moving a test class out of our integration tests and putting it in the functional directory where it belongs. We have a handful of tests in the code base that are getting missed on PRs and don't surface until after merge because they're misclassified as integration. This is the first step to get a common set moved over and will have follow up to migrate some of the other offenders.

Codecov Report

Merging #2129 into develop will decrease coverage by 0.08%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop    #2129      +/-   ##
===========================================
- Coverage    93.11%   93.03%   -0.09%
===========================================
  Files           60       60
  Lines        11114    10982     -132
===========================================
- Hits         10349    10217     -132
  Misses         765      765

Impacted Files
Coverage Δ

botocore/model.py
97.98% <0.00%> (-0.23%)
:arrow_down:

botocore/docs/bcdoc/restdoc.py
96.26% <0.00%> (-0.17%)
:arrow_down:

botocore/retries/bucket.py
98.48% <0.00%> (-0.09%)
:arrow_down:

botocore/validate.py
98.74% <0.00%> (-0.07%)
:arrow_down:

botocore/compat.py
95.32% <0.00%> (-0.06%)
:arrow_down:

botocore/loaders.py
99.24% <0.00%> (-0.04%)
:arrow_down:

botocore/docs/bcdoc/style.py
95.45% <0.00%> (-0.04%)
:arrow_down:

botocore/client.py
98.56% <0.00%> (-0.04%)
:arrow_down:

botocore/paginate.py
97.80% <0.00%> (-0.03%)
:arrow_down:

botocore/signers.py
98.09% <0.00%> (-0.03%)
:arrow_down:

... and 10 more

Continue to review full report at Codecov.

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


[Question] Why Channel doesn't have a feature to return all metadata?

When using Channel, I sometimes need to extract its metadata in JSON/Dictionary format. I can access the data using _metadata:
channel = Channel("channel_id")
channel.parseData()
print(channel._metadata)

But that's not a "public" feature, as it involves an insecure attribute _metadata. Should I write a function that extracts all channel's metadata securely?
P.S. As I want to contribute to this project in the future, maybe we can talk in Discord or somewhere else, if you're interested.

I will open a pull request with this feature after your answer.

I will open a pull request with this feature after your answer.

Thanks a lot.

PR is ready to be merged. Please update the docs as I don't have access to them.

Documentation has been updated.
https://ytsa.thecodeblog.net/en/latest/API reference.html#youtube_scraping_api.parser.channel.Channel.raw


run_train_val.sh: --pi: not found

Hi~Your work is very impressing. Sadly, I am stuck when trying to run the code, could you please help me?
When I try to run the run_train_val.sh, it ends up of failure as:
Traceback (most recent call last):
File "train_and_eval.py", line 25, in
model.optimize_parameters()
File "/home/yb/code/Distillation/structure_kd/networks/kd_model.py", line 168, in optimize_parameters
self.forward()
File "/home/yb/code/Distillation/structure_kd/networks/kd_model.py", line 122, in forward
self.preds_T = self.parallel_teacher.eval()(self.images, parallel=args.parallel)
File "/home/yb/anaconda3/envs/pt041/lib/python3.5/site-packages/torch/nn/modules/module.py", line 477, in call
result = self.forward(*input, **kwargs)
File "/home/yb/code/Distillation/structure_kd/utils/parallel.py", line 106, in forward
return super().forward(inputs, **kwargs)
File "/home/yb/anaconda3/envs/pt041/lib/python3.5/site-packages/torch/nn/parallel/data_parallel.py", line 121, in forward
return self.module(*inputs[0], **kwargs[0])
File "/home/yb/anaconda3/envs/pt041/lib/python3.5/site-packages/torch/nn/modules/module.py", line 477, in call
result = self.forward(*input, **kwargs)
File "/home/yb/code/Distillation/structure_kd/networks/pspnet_combine.py", line 177, in forward
x = self.relu1(self.bn1(self.conv1(x)))
File "/home/yb/anaconda3/envs/pt041/lib/python3.5/site-packages/torch/nn/modules/module.py", line 477, in call
result = self.forward(*input, **kwargs)
File "/home/yb/code/Distillation/structure_kd/libs/bn.py", line 184, in forward
self.activation, self.slope)
File "/home/yb/code/Distillation/structure_kd/libs/functions.py", line 218, in forward
x, x, ctx.eps)
File "/home/yb/code/Distillation/structure_kd/libs/functions.py", line 16, in _check
raise RuntimeError("CUDA Error encountered in {}".format(fn))
RuntimeError: CUDA Error encountered in <function CompiledLib.bn_forward_cuda at 0x7f270938d620>
run_train_val.sh: 19: run_train_val.sh: --pi: not found
I don't know how to fix it, would you kindly take a look? Thank you sooooo much~
By the way, my environment is PyTorch 0.4.1, python 3.5.6 and CUDA 9.0.

The --pi is a hyperparameter, which needs to be True.
Do you modify any code in the script?
This seems like the wrong format bug...

The --pi is a hyperparameter, which needs to be True.
Do you modify any code in the script?
This seems like the wrong format bug...

Thanks for your kind reply~ I found the error, I annotated --student-pretrain-model-imgnet when running run_train_val.sh. Thanks again~ღ


fix extact task id

keys -v didn't return taskid
It returned the name ECS cluster

@hilenko
Thanks for fix it!

Released as https://github.com/shufo/ecs-fargate-oneshot/releases/tag/v0.1.4.


GPIO test code tests/drivers/gpio/gpio_basic_api does not compile for microchip board mec15xxevb_assy6853

Describe the bug
Tried to compile the standalone gpio test code for microchip and it gives compilation error.
What have you tried to diagnose or workaround this issue?
Adding the line #define DT_ALIAS_GPIO_0_LABEL DT_MICROCHIP_XEC_GPIO_40081000_LABEL
in the file zephyr/tests/drivers/gpio/gpio_basic_api/src/test_gpio.h solves the issue. But this has to be added for all ports and in the proper way in the zephyr stack.
To Reproduce
Steps to reproduce the behavior:

Cd zephyrproject/zephyr/tests/drivers/gpio/gpio_basic_api/
West build -p -b mec15xxevb_assy6853 .
See error

Expected behavior
Should compile without errors and give the output binary.
Impact
Build should succeed. It affects gpio testing for microchip.
Screenshots or console output
In file included from ../src/test_callback_manage.c:15:
../src/test_gpio.h:22:2: error: #error Unsupported board
#error Unsupported board
^~~~~
../src/test_callback_manage.c: In function 'test_callback_add_remove':
../src/test_callback_manage.c:84:42: error: 'DEV_NAME' undeclared (first use in this function)
struct device *dev = device_get_binding(DEV_NAME);
^~~~~~~~
../src/test_callback_manage.c:84:42: note: each undeclared identifier is reported only once for each function it appears in
../src/test_callback_manage.c: In function 'test_callback_self_remove':
../src/test_callback_manage.c:126:42: error: 'DEV_NAME' undeclared (first use in this function)
struct device *dev = device_get_binding(DEV_NAME);
^~~~~~~~
../src/test_callback_manage.c: In function 'test_callback_enable_disable':
../src/test_callback_manage.c:171:42: error: 'DEV_NAME' undeclared (first use in this function)
struct device *dev = device_get_binding(DEV_NAME);
^~~~~~~~
ninja: build stopped: subcommand failed.
Environment (please complete the following information):

OS : Ubuntu LTS 18.04
Toolchain: Zephyr SDK : 0.10.3
Zephyr version: v2.1.0-1048-gdbdfd2995b2b

Additional context

There is an updated Zephyr SDK (0.11.1).
I'm not sure if this helps/relates to this, but there was recent activity on the GPIO API that may have impacted some users despite best efforts to ease the transition. Please see more information in the TOPIC-GPIO project page on that effort to convert to the new GPIO API: https://github.com/zephyrproject-rtos/zephyr/issues/20017. More specifically, https://github.com/zephyrproject-rtos/zephyr/pull/19555/commits/b3f835377d37d5909b22e7bc2fc8a30f6f1881d4

See #22639 which documents what needs to be done to build this test.

I have no problem building it at current master.
The git commit the bug pointed to was before the topic-gpio branch was merged into master. In the topic-gpio branch, an overlay was added for the mec15xxevb_assy6853 board (which is now in master).
Please try building again and see if it is still a problem on your side.

Yes the build issue for microchip is fixed with the latest master.
Closing the issue


Finished -> Passed/Failed

This changes the tooltip text from:

to "Failed Tuesday at 2:33 PM"
Which is important because at the moment, colour is the only way to differentiate the builds in the build graph… there's no icon or words to tell people what the difference between passed and failed graphs are.

You’ll need to update some snapshot tests! Let me know if you want help with that :smile:

@ticky thanks, just spotted that now! Pushed a fix


Redis cluster connection issue

Hi,
I was trying to establish a connection to redis cluster, using createCluster(). But was not able to. Following was the error returned :
ReplyError: NOAUTH Authentication required.
at parseError (/redis-parser/lib/parser.js:179:12)
at parseType (/redis-parser/lib/parser.js:302:14)
(Use node --trace-warnings ... to show where the warning was created)
(node:89375) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:89375) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Also, I have verified the connection string and there is no issue in terms of that. Here's the code snippet.
(async () => {
const cluster = createCluster({
rootNodes: [
{
url: 'redis://:CLUSTER_PASSWORD@CLUSTER_IP:CLUSTER_PORT'
}
]
});
cluster.on('error', (err) => console.log('Redis Cluster Error', err));
cluster.on('connect', () => {
    console.log("Redis client connected. RedisHost");
  });
await cluster.connect();

})();

specifying the password in the URL or a root node will only affect the connection to that specific node. In case you want to set the password for all the connections being created from a cluster instance - use the defaults option:
const cluster = createCluster({
  rootNodes: [{
    url: 'redis://CLUSTER_IP:CLUSTER_PORT'
  }]
}, {
  defaults: {
    password: 'CLUTSER_PASSWORD'
  }
});

Following the workaround above, I still get the NOAUTH error

start redis cluster at 7379, 7380, 7381

vim rediscluster.mjs

import { createCluster } from 'redis';

const cluster = createCluster({
  rootNodes: [{
      url: 'redis://default:cluster@localhost:7379'
  }]
}, {
  defaults: {
    username: 'default',
    password: 'cluster'
  }
});

cluster.on('error', (err) => console.log('Redis Cluster Error', err));

await cluster.connect();

await cluster.set('key', 'value');
const value = await cluster.get('key');
console.log("get key: %s", value);

await cluster.disconnect();

$ node --experimental-modules rediscluster.mjs
node:internal/process/esm_loader:79
    internalBinding('errors').triggerUncaughtException(
                              ^

[ErrorReply: NOAUTH Authentication required.]

Node.js v19.4.0

@yangbodong22011 I fixed the example above. This should work:
const cluster = createCluster({
  rootNodes: [{
      url: 'redis://default:cluster@localhost:7379'
  }],
  defaults: {
    username: 'default',
    password: 'cluster'
  }
});

@leibale thank you very much, it worked. my new code is:
import { createCluster } from 'redis';

const cluster = createCluster({
  rootNodes: [{
      url: 'redis://default:cluster@localhost:7379'
  }],
  defaults: {
      username: 'default',
      password: 'cluster'
 }
});

cluster.on('error', (err) => console.log('Redis Cluster Error', err));

await cluster.connect();

await cluster.set('key', 'value');
const value = await cluster.get('key');
console.log("get key: %s", value);

await cluster.disconnect();


[Beta 2.0.0] Version is too long for the craft_plugins table

The Craft plugins table only allows for varchar 15. The current 2.0.0 beta version is listed as '2.0.0 beta 1 (1.0.71)'.  This gets truncated on some systems but others it causes a MySQL errror.
Not sure what you'd do other than make sure the version isn't crazy long.

Didn't even think of that, but thanks for bringing that up. I've now reverted it as of the latest master.

No problem. Just wanted to bring it to your attention.


[docs] Fixed typo in BaseFileHelper::findFiles() docs [ci skip]

Q
A

Is bugfix?
no

New feature?
no

Breaks BC?
no

Tests pass?
no

Merged. Thanks!


Creating a custom Step without Next Button

I would like to create a custom Step component that has no next button, but is only used for some steps, which require user input in order to progress in the tour.
I read in other issues and the docs that you can use a Custom template, but I did not understand how I can create one and set it for a certain step as the template. Could you provide a little bit more detail on how to do that?

You can just create one custom template for all steps and then hide the button depending which step you are on:
<button
    mat-button
    class="next"
    *ngIf="tourService.hasNext(step) && step?.anchorId !== 'foo'"
    (click)="tourService.next()"
>
    {{step?.nextBtnTitle}} <mat-icon>chevron_right</mat-icon>
</button>

Thank you for your advice.

One thing that I had to do is use the default md-menu template instead of the default template of the README.md which is outdated I guess.
If you use the template from the Readme the close button is not styled properly. I wanted to create a Merge Request, but did not know which file I have to edit for the Readme.


Increment version for provisioning releases

Increment package version after release of Azure.Provisioning

API change check
API changes are not detected in this pull request.


WIP: OSS Project Pricing Page

This PR introduces an OSS Pricing page to pulumi.com. The intent is for someone to submit the form to get in contact with us about a free OSS license.
@susanev I think we will need to update the pricing page as well to merge this in. My assumption is that the pricing page is where we would link to this page from but interested to hear if you think there is a better place.

I'll hold off on reviewing this further for the 👍 from @aaronkao, as I think there are still some questions to be answered.

@zchase @aaronkao i still have a few concerns about this page...

the name of this project, is really similar to other names and im worried it wont be clear what this is in relation to the plans on the pricing page
we don't have a sku currently that has a 25 member limit, and unlimited stacks, will we need to create one for this or will things get turned on manually for folks who are accepted into this program?
for the URL can we name it the same as whatever the project ends up getting named?

@zchase for the linking from the pricing page, lets add a FAQ, something like ...
How can organizations that are not seeking a profit, and projects under an OSI-approved open source license use Pulumi for free?

that links to the page with the details.

@susanev I updated the URL to match better with the name of the page.

I think it will be fine to leave the title as-is for now, but leave the option to change it later if we hear confusion from customers.
Onboarding these folks will be a manual process for now, but essentially this the current Team PRO SKU w/ 100% discount. I believe we have already onboarding 1 customer with this plan, so it might exist in some capacity already?
Updated

Also if you don't mind, let's do the pricing page changes in a different PR. I think we will likely want to add an FAQ section and it would be to spend at least a little time thinking through exactly what we want to write and present on the /pricing page.

@zchase @aaronkao i still have a few concerns about this page...

the name of this project, is really similar to other names and im worried it wont be clear what this is in relation to the plans on the pricing page
we don't have a sku currently that has a 25 member limit, and unlimited stacks, will we need to create one for this or will things get turned on manually for folks who are accepted into this program?
for the URL can we name it the same as whatever the project ends up getting named?

@zchase @aaronkao i still have a few concerns about this page...

the name of this project, is really similar to other names and im worried it wont be clear what this is in relation to the plans on the pricing page
we don't have a sku currently that has a 25 member limit, and unlimited stacks, will we need to create one for this or will things get turned on manually for folks who are accepted into this program?
for the URL can we name it the same as whatever the project ends up getting named?

I agree the name may seem confusing, but there is no confusion that this is free stuff for OSS projects. We would probably just link to this at the very bottom of the /pricing page with a clear description. We could also call this "OSS Free Offer". Do you have any suggestions?
This is just the the maxed version of the current Pro plan - https://www.pulumi.com/pricing/
Yes, of course

oh for the free plan my concern is just the confusion between the free plan currently: community and this free plan.


App icon enhancements to config

Assume cmus-icon.png location from the config file

Expand home user constructions for the app_icon in the config. This is useful so there is no absolute paths 😄
Didn't use the validator, because there is no way to modify the value before it is called.

Great addition! That being said: I'm not the biggest fan of this approach because it accesses internal values of the _EditableConfig instance and because it forgoes the validation support that's integrated into Meh. I'll shortly push my take on this 🙂

Agreed. Your solution looks better!
Thanks for taking care of it quickly  👍


Fix Android gradle build script

As of 0.56, new RN project start declaring a few constants in gradle that libraries can query about.
Some library uses this technique so I'm porting it over here:

https://github.com/oblador/react-native-vector-icons/blob/master/android/build.gradle
https://github.com/oney/react-native-webrtc/pull/494/files

wow, incredibly late but here goes! thanks a bunch, excellent strategy to make it more portable 👍


change loglevel for websocket abnormal close from error to debug

abnormal close happens quite often in modern mobile browsers
this prevents spamming the logs with errors

Considering the refactoring #229 , the specific code for websocket has been removed so this PR cannot be merged.


197 version 007 updates

closes #197
contents of changes found in #197

For what is most certainly the last time, I will bypass standard operating procedure, but it is @stratfordCircle birthday celebration, so all is forgiven of me.


Not working...

import asyncio
from aiocfscrape import CloudflareScraper

async def test_open_page(url):
    async with CloudflareScraper() as session:
        async with session.get(url) as resp:
            print(resp.status)
            pass

if __name__ == '__main__':
    asyncio.run(test_open_page('https://www.banrep.gov.co/'))

> python -V
Python 3.9.10
> python test.py
403

I'm facing this too.
Not working for "help-txbiz.tv-tokyo.co.jp" while cloudscraper is still working
import cloudscraper
scraper = cloudscraper.create_scraper()
scraper.get(f"http://help-txbiz.tv-tokyo.co.jp")

Does not work for https://passport.mfa.gov.ua either. I suppose it needs updates per https://github.com/pavlodvornikov/aiocfscrape/issues/27#issuecomment-722376837.


arxiv files download by category/

fantastic work. Did you find a method for downloading arxiv files for only a specific topic e.g.: physics ?

I seem to recall a lack of helpful metadata in this regard. I just identified math papers based on the presence of  keywords.


Travis failure on CCPi-Framework

https://travis-ci.org/github/CCPPETMR/SIRF-SuperBuild/jobs/663096871#L1643
CMake Error: The source directory "/opt/SIRF-SuperBuild/sources/CCPi-Framework" does not appear to contain CMakeLists.txt.

There's also
https://travis-ci.org/github/CCPPETMR/SIRF-SuperBuild/jobs/663096871#L1516
CMake Warning at SuperBuild/External_CCPi-Regularisation-Toolkit.cmake:57 (message):
  CIL_VERSION

which implies that CIL_VERSION is empty in SuperBuild/External_CCPi-Regularisation-Toolkit.cmake, but that might be alright, in which case the warning needs to be deleted.
Possibly this error is another case of a broken update in CCPi code, #347

It seems that they put in a CMakeLists.txt between the last release 19.10 and now. Perhaps that's why they were just doing copies before, so my PR #359 will have broken it for older versions. Is that right @paskino ?
As it is, it seems to be broken one way or another. Either we use the old method and then the library won't be compiled so it fails. Or we use the PR I put in yesterday, in which the last stable release will fail as there is no CMakeLists.txt.
Would it be possible to do another release and then we could reference that?

If travis goes green (it did for the PR), then #362 should have fixed this.


Option not to re-download deleted, renamed or moved files that were downloaded from the Tumblr search and tagged pages

Hello, Johannes.
I noticed that the program seems to be ignoring or simply not using such a file-lists like * _files.tumblrtagsearch and * _files.tumblrsearch that are stored in Index folders, because when after end of crawling I use a duplicate search program to delete all duplicate images and the next day I run a new crawling to download new images added after the last crawl, then the program still continues to re-download deleted files. With regular blogs there is no such problem, the program does not download deleted files if index files are stored, which is very convenient for me. But this option does not apply to new functions of downloading images by tags and search keywords. I would like it to be implemented for these functions too. Thanks!

Can you append two pairs of blog files (so the _files and the non _files) of searches where that has actually happend? If they are too large, you can also send them to me via email.
In principle it shouldn't work different as for blog downloads since the downloader code is the exact same, just the scanning/detection of photos/videos is different. But I haven't have time to check it thoroughly though.
I probably also won't have time to fix anything, if it's in case broken, before next weekend.

Of course, here is the whole Index folder.
Index.zip

When I do a tumblr search, delete all the downloaded files (i.e. photos and videos) afterwards and re-queue the search, no (new) files are re-downloaded.
In your _files database is no duplicate either, so in principle it does work as it works for blogs. There is also no filename with a smaller image size of the same file in the _files database.
Thus, I think it works. For testing it more thoroughly I probably won't have time.

Did you actually fix your connection issues?
 If the download does not completely finish, TumblThree will not update the databases on the disk. Thus, if there is a stalled connection because of wonky wifi/internet and you remove duplicates between different blogs, the same files might be re-downloaded.
Since I've told you this already at least 4 times, I really hope it's not the same issue again.

If the download does not completely finish, TumblThree will not update the databases on the disk. Thus, if there is a stalled connection because of wonky wifi/internet and you remove duplicates between different blogs, the same files might be re-downloaded.

Yes, it seems that case. I've been testing more, on small searches with several hundred images. When the download completely completes and I delete the files, then the program does not download the deleted files. On large searches, it happens to me that the download stops or when the download is finished and I close the program, then the process still exists in the memory and I have to manually end it so the index files are not updated too. So the problem is on my side. Sorry for bothering you.

Possible duplicate of #116.


Sync for manual Chart releases

When a Chart release is manually handled (upgraded/installed/deleted), the cluster gets out of sync with the desired state prescribed through Custom Resources.
The implementation regularly polls the cluster to check whether only expected Chart releases are running, all of them and no others. The existing Chart releases are checked for changes from the desired state described by their respective Custom Resources. Diversion from the expected state leads to an upgrade install of the changed release.
Fixes #980

Remember to squash away review-response commits.

I mentioned it when I created the PR just to avoid this comment ;)