Update dependencies

This PR updates some dependencies, my main motivation in this is ruzstd removes syn from it's dependency tree and a bunch of proc-macro code generation speeding up compile times and making it so my project will only have syn 2 in it's dependencies and not syn 1 + 2 (once object updates and releases a new version).

Looks like MSRV would have to bump from 1.65 to 1.73 for ruzstd to pass the check - not sure on your MSRV policy :eyes:

We can exclude the compression feature from the MSRV test for now.

okay done :+1:


Only available for en-US as no HostsFileProvider.psd1 for other languages

It would be prefer if this resource is multilingual support.
Ex. We can use with this resource if we add ja-JP folder and HostsFileProvider.psd1

If you want to provide the translations, by all means.  :)

alright close then issue.


Utilize cardano-cli with marlowe-cli to create and submit transaction

Describe the feature you'd like
I would like to have an example of how to build a transaction with cardano-cli transaction build after creating the datum & redeemer with marlowe-cli contract.
Additional context / screenshots
This is the conversation I had with Brian W Bush on ask-marlowe : https://discord.com/channels/826816523368005654/936295815926927390/998628705469485148

1. Watch https://github.com/input-output-hk/marlowe-cardano/issues/186 to learn of progress on Babbage compatibility and tag it with 👍 to indicate your interest and having this prioritized.

2. Tomasz Rybarczyk is working on a branch that brings Babbage to key Marlowe components: see https://github.com/input-output-hk/marlowe-cardano/issues/186#issuecomment-1186816334.

3. Although it's somewhat tedious, it should be possible to use the low-level marlowe-cli commands like marlowe-cli contract and marlowe-cli role to create the script, datums, and redeemers for Marlowe transactions. Those can be bundled into a transaction using version 1.35.x of cardano-cli, which is compatible with Babbage. (This is how we ran Marlowe on chain last year before we had higher level support in marlowe-cli.) Please feel free to submit a github ticket requesting a detailed tutorial on how to do this: https://github.com/input-output-hk/marlowe-cardano/issues.

Thanks for your patience. 🙏

https://gist.github.com/bwbush/a49a093db2137deb3b0791876cc0bc43
Here is the answer of @bwbush on how to make the above request.


Adds Initial: Jest setup, testing utilities, tests

* Add /src/__tests__ directory

* Add Redux-Mock-Store dev dependency

* Add jest-setup.js file at project root

* Add tests for middleware, createOfflineStore, config, and batch

@jevakallio , Alright, I've got these updated to test the newest version of the code.  I have one test that I'm currently skipping because something isn't mocking correctly which is proving to be a little bit tricky to debug, so I figured I would just submit the PR now because I'm not sure how long it will take to figure it out.
As I said in my last PR, I just have a few tests in so far which a fairly straight forward unit tests, but if we get these to a point where you're happy with the direction and want to move forward. I'll finish off the unit tests and try to get in some full integration tests as well.
One thing you might notice is that some of the formatting is updated on a few of the non-test files.  That was a mistake initially because my editor auto-formats when I switch panes which I have set up to use Prettier.  I was initially going to pull out these changes, but I figured if using Prettier is the standard you want to use for formatting, it might make sense to leave the changes in for consistency.  That being said, I don't want to create any merge conflict headaches for anyone, so if need be, I can definitely revert them to the original formatting.

@fossage thank you, I will try to review this ASAP.
It looks like I have my prettier-atom plugin configured with a longer line length (110 char), and I agree with you that I should try to use the standard configuration as much as possible, so happy to accept these changes.

Some unit tests have been added so I'm going to close this, but feel free to add more.


Taylor/template details type

:tada: This PR is included in version 5.0.10 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Generic EntityTable

Merry Christmass! :-D
This is a first attempt at a generic "entitymanager". Applied to both the Brands and the Products views.
They both are functioning exactly the same like before, which can definitely still use some work as some features are not yet implemented. But at least you can do it now in one spot ;-)
Still thinking about the api and the naming... looking for feedback.
We'll probably have to add functionality/customization as we go... also probably split it up into more separate components... in the end I imagine it should be usable on the roles and users screen as well...
Look how nice and clean Brands.razor has become (even small enough to put it in one file in stead of with code behind) ;-)

Cool, I had a similar approach in a previous project where we made the Table Component Generic. The one challenge I saw is that, when the Table has to be customized (like adding a new button, or changing the color of a row based on some conditions, etc), the generic approach doesn't do very well.
For ex, the AuditLogs table cannot use this generic approach, right? What would be your suggestion?

Yeah, for now, I've taken the road of least resistance for implementing both products and brands... they are quite basic so the rowtemplate is not customizable, but in the end it should be... also the toolbarcontent, ...
That's also what I meant with "adding functionality/customization options as we go" and splitting it up in multiple smaller sub-components over time... For instance the search field, and the "reload" and "create" buttons... we should never have to copy that specific markup again (and have to change it everywhere if it needs to be changed)...

Roles has been done... (non server side filtering/sorting and extra actions button)

AuditLogs done...

Users done as well...
There's only one thing that isn't working (as far as I see), and that's the passwordVisibilityToggle...
Can't seem to figure out why ;-s

Ok, found the culprit... apparently have to explicitly do a StateHasChanged on the dialog... added a convenience method on the context for that (AddEditModalForceRender).
With that, I think it's ready for review ;-)

I think the control level validation is still not available? I am able to see it via login page as well, also via brand / product forms

BTW, the code looks very clean and minimal at the first glance. Will dig deep and let you know.

Can you clarify what you mean with control level validation? Is it the 400 result you're talking about?
For me it's working on the login page, also on the add new user screen (due to the 400 response I just added over on the api project). For products and brands, that 400 response will also have to be added.

Try to submit an entirely blank form. You should be able to reproduce the issue.

The DataAnnotations of the FshApi Client code get triggered but don't reflect back to the mud control.

I guess adding the NullHandling = Ignore property to the Serializer should fix this. That's for Server-side validation. But then again, we still have to figure out Local Validation. The DataAnnotationsValidator that you have added, what's its role?

Also, if NSWAG could read the fluentValidation Rules (of API), it should be able to generate better client code. And this should also fix the local validation I beleive.

Aaah, ok, now I see what you mean. The reason is the nullability... because on the RegisterRequest type on the server, the properties are annotated with the [Required] attribute, they apparently get generated with non nullable properties on the client.
I see they even get the same annotations applied. That's magnificent... (hadn't realized that before).
But somehow they don't get triggered... I'll have a look why...

Ok, I see the problem. The AddEditModal is not working with a RegisterRequest, but rather with a UserDetailsDto (as that's the base entity of the whole "EntityTable")...
The CreateAsync method on the Users view uses mapster to map the UserDetailsDto to the RegisterRequest... I'll have a look if I can trigger the validation after that...
Otherwise I might have to introduce another (or rather 2) new TypeParameters for the registerrequest and updaterequest types...

NSwag doesn't read the fluentvalidations, but it does read the dataannotations apparently (that's what I didn't realize), and adds all those validations to the jsonschema supplied in the openapi spec.
There's a package apparently to also process fluentvalidations:
https://github.com/zymlabs/nswag-fluentvalidation
we'll have to check that out!

See #58

Also, i think it is necessary to copy over the fluentValidator rules to the wasm project as well, in case someone wants to add additional validation rules for entity creation and stuff.

So, instead of dataAnnotations validator we can make use of the local FluentValidator and remove the validation dependency with NSWAG's generated code.

Let's continue the chat here - https://github.com/fullstackhero/blazor-wasm-boilerplate/issues/59


RWops extras currently requires an update for SDL3

The migration document for SDL3 outlines some changes to the SDL_RWops read and write function signatures here.
Naturally, this means the custom RWops implementation example in (extras/physfsrwops.c) will need an update, since it passes functions that use the old signature.
With SDL3 still in a prerelease state, I would imagine it would be currently inadvisable to push any changes until that's solidified. That said, I figured I'd make a note of it here so that it's not forgotten...and because I don't know what I'm looking at yet, I'm not sure how to fix it myself.

Good call.
I think we're done making changes to this part of SDL3, so it's probably safe to update PhysicsFS, but we'll let it marinate a little longer, just in case.

I attempted to do this, not sure if this is the right approach but it works well enough for my simple use case https://github.com/icculus/physfs/pull/81


Fix quick open background panel style

Quick open result container tries to set the container stylebox override to QuickOpenBackgroundPanel which isn't defined in the editor theme. ~This adds the missing stylebox to make quick open look consistent with all other lists in editor~. Using Tree panel stylebox instead

Master
PR

Instead of copying tree panel, you can assign it directly in the dialog. There is no reason to have a type that's identical to existing one.
Also CC @stijn-h

Thanks!

Yeah, this is what it was supposed to look like. I intended to use this stylebox to remove padding on the sides of the dialog. I got it working in a hacky way, but ended up giving up on it because i couldnt figure it out and removed most theming, except this apparently. Thanks for fixing!


TPV positive regulation of cyclin dependent kinase

Has ancestry to "regulation of cytokinesis". This is definitely not always true.

Removed this link.


do not allow EnvironmentVariableAccess in Ruby files within config

The description of the cop states Do not access ENV directly after initialization.. However in some ways, the application is already initialized when we get to config/**/*.rb:

config_for(:service) is already available to read config from service.yml
Rails.application.credentials is already available to read application credentials / secrets

I think it could make sense to push people to move their config in either of these two places. If they want to access their config / secrets in a Ruby file, let's say, config/initializers/service.rb they can use credentials or config_for, no need to access ENV directly again.
Also see https://guides.rubyonrails.org/initialization.html.
I understand this is a bit nuanced, so if this is not desired, that's completely fine ✌

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[ ] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[ ] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.
[ ] If this is a new cop, consider making a corresponding update to the Rails Style Guide.

config/**/* seems to be too broad of a match. For example, in config/boot.rb, it appears that the Rails constant cannot yet be resolved. i.e., uninitialized constant Rails (NameError)

Hmmm... How about we limit the include to config/initializers? seems like boot.rb, environment.rb, application.rb have already run at that point and Rails has been loaded, see https://guides.rubyonrails.org/initialization.html#railties-lib-rails-application-rb. Would that be an option?

I have left two comments. Can you update these and squash the commits?

Updated, squashed, and added specs for the new cases 👍

Thanks!

I'm confused: With this rule enabled, how can a Rails app read env vars at all?
E.g., in my initializers, I ENV.fetch() env vars and create constants that I access throughout my app. This seems to be the safest way to do it.
A couple people (or maybe just one person?) has said that the Rails configuration lib can read env vars and check them at boot time. But no one has provided code showing this, so the rule was set disabled by default here. I'm skeptical: I couldn't find mention of this check-env-var-at-boot feature in the Guide.
In a nutshell, this rule seemed to be on shaky ground before this change. And now that all initializers are off-limits to ENV access under the rule, how should environment variables be access when enabled?

From the PR description:

However in some ways, the application is already initialized when we get to config/**/*.rb:

config_for(:service) is already available to read config from service.yml
Rails.application.credentials is already available to read application credentials / secrets

So what you can do is
# In config/slack.yml
default: &default
  client_id: <%= ENV["SLACK_CLIENT_ID"] %>
  client_secret: <%= ENV["SLACK_CLIENT_SECRET"] %>

# In application.rb
module MyApp
  class Application
    config.slack = config_for(:slack)
  end
end

# In rest of the app
Rails.application.config.slack.client_id

Similarly, secrets should be in credentials.yml [docs], so given
# In config/credentials.yml.enc
secret_key_base: 3b7cd72...
some_api_key: SOMEKEY
system:
  access_key_id: 1234AB

You can do
# In rest of the app
Rails.application.secrets.some_api_key
Rails.application.secrets.system.access_key_id

That way

Secrets are in credentials.yml.enc
Config is in config/*.yml

Direct ENV access only happens here and in config/*.rb since those files are excluded

Access to secrets happens via Rails.application.secrets or Rails.application.config

Hope that helps

Thanks @markokajzer. So if I understand it correctly, under this rule, ENV access can happen in the config/*.yml files.

I'm not sure I fully understand the argument about the app already being semi-initialized at the point it starts loading the initializers directory. The idea of that makes sense, but I'm not sure how we extend that logic to mean that the initializers are an inappropriate place to read from ENV.
My understanding is that the entire reason we say "don't mess with ENV post-initialization" is because missing configuration wouldn't be caught at boot (obviously bad). This is the exact reason I read directly from ENV from within initializers in the first place.

I'm willing to be wrong here, but I'm really not thrilled by the idea of adding an extra YML file

Unfortunately, that is literally the suggested approach from the Rails docs.
Rails changed this a couple of times throughout the versions and years, and other people from the community dislike the different configuration options for similar reasons. Here's an example from searls.

don't mess with ENV post-initialization

i don't think it was ever about "messing" with anything. after all it was just access to ENV. one could argue why the rule existed in the first place if accessing ENV is okay in some places 🤷
to me, this was about enforcing one way of doing this (now everything is pushed towards config/*.yml instead of spreading access to ENV around the place like it usually happens), and recommending the suggested approach from the Rails docs to developers. personally I think a linter should enforce things to be done in a certain, consistent way, just like formatter.
similarly, if our env variable is an actual secret, maybe we can put it in Rails credentials, where it will be encrypted and actually safe, in contrast to just having ENV which leaves it to the developer.
nevertheless, i'm just trying to explain some points here. I'm more then willing to take the L here and revert this. your feedback is heard 👍

I appreciate the extra thoughts & time, thanks @markokajzer. This certainly is far from a hill worth dying on as far as I'm concerned, and I think I am aligned on the idea that the linter should have an opinion on the correct way to do things like this, and I really can't argue with the idea that it's how the Rails guide wants you to do it.
The link you included is helpful as it's the same issue I'm having, and I also happen to be using standardrb, so looks like this won't be something I have to mess with configuration wise, either.
In the end, the discussion is what's important - if I could suggest anything extra, for what does appear to be an immediately-noticed change & resulting disagreement, maybe a small disclaimer in the Rubocop docs which has a very short rationalization for the choice? Even if it were just to explain that this is the "correct" way to do it as far as the Rails guides are concerned, and that enabling the cop by default is preferable to having no cop at all.
Cheers.


Fix scaffolding type mapper FixedLength bug

Fixes #14160 Superceeds #14162
ScafoldingTypeMapper should have been passing false when looking for the default mapping, since, non-fixed length is the default. (Compare this to Unicode, where we pass true because Unicode is the default.)
Also included is a fix for test, which wasn't Asserting for fixed length, as found by Smit.
Also fixed the code in RelationalTypeMappingInfo that was for some reason using parsed-length to drive the fixed-length flag, although this was a secondary issue.

/cc @roji


Icons on Squire demo page not displayed on IE

Icons on Squire demo page not displayed on IE:
http://neilj.github.io/Squire/

Works fine for me.

Yeh, this works for me too.


When 'required' is set to 'false' the input field always initializes to blank

When I pass in a value for current_date but also set required to be false I'm ending up with a date picker that has the initial value set to '', which lets the placeholder show up. I think it should set the initial value to be the formatted version of current_date.
I think this line is the culprit.
https://github.com/Baremetrics/calendar/blob/master/dev/js/Calendar.js#L776

524c55b363c2e0e56d7b3ba6be485dc3c043ac7d


Unimplemented RPC should return a non-empty message.

What version of gRPC and what language are you using?
1.14.1, C++
What operating system (Linux, Windows, …) and version?
N/A (Ubuntu 16.04.5 LTS)
What runtime / compiler are you using (e.g. python version or version of gcc)
N/A (gcc 7.3.0)
What did you do?
I implemented the gRPC Server Reflection Tutorial and used the gRPC command line tool, without implementing my service's single function.
syntax = "proto3";

package mykpg;

message CreateTableRequest {
}

message CreateTableReply {
}

service MyServer {
  rpc CreateTable (CreateTableRequest) returns (CreateTableReply);
}

...
struct MyServerImpl final : public mypgk::MyServer::Service {};

What did you expect to see?
I expected to see an error telling me that I didn't implement the function I called.
What did you see instead?
Rpc failed with status code 12, error message:

I had to find this via status_code_enum.h, and/or by guessing/counting on statuscodes.md.

I suggest gRPC replaces ::grpc::StatusCode::UNIMPLEMENTED, \"\") with ::grpc::StatusCode::UNIMPLEMENTED, \"UNIMPLEMENTED\") in cpp_generator.cc.
I can make a PR if the project is amenable (or someone else can).

A further and separate suggestion is to enhance the documentation on statuscodes.md to include the integer codes that the status code enums represent.

I am neither for or against this. Seems to me that a simple enum to string function would also do the job.


AsyncParsableCommand never runs. Only shows help text.

I'm using Swift 6.0, and Im trying to use adhere to to the AsyncParsableCommand protocol. However I'm noticing that no matter what, my program always returns the help text instead of actually running.
There's post here describing this issue as well. Seems like the compiler favors the sync run command over the async run command.
Here's my main file. Just trying to print a string right now.
import ArgumentParser

@main
struct PhpFlayer: AsyncParsableCommand {
    mutating func run() async throws {
        print("I'm working!")
    }
}

ArgumentParser version: main branch
Swift version: swift-driver version: 1.113 Apple Swift version 6.0 (swiftlang-<IP_ADDRESS>.6 clang-16<IP_ADDRESS>) Target: arm64-apple-macosx14.0.
Checklist

[x ] If possible, I've reproduced the issue using the main branch of this package
[x ] I've searched for existing GitHub issues

Steps to Reproduce

Create an empty project

mkdir MyCLI && cd MyCLI
swift package init --name MyCLI --type executable

Setup the entry file and add the argument parser package

Add the argument parser package  to Package.swift
rename Sources/main.swift to Sources/MyCLI.swift
setup the following main struct

import ArgumentParser

@main
struct MyCLI: AsyncParsableCommand {
    mutating func run() async throws {
        print("I'm working!")
    }
}

Run the program and see only help text show up instead of "I'm Working!"

Expected behavior
I'd expect when running swift run MyCLI that i would see "I'm working!" in the terminal.
Actual behavior
Right now this always displays the help text.

Same with Swift 5.10. Using ParsableCommand works just fine.

Have you tried removing mutating?

Yea. Same result unfortunately.

My code structured like the following works for me using Swift Argument Parser 1.5.0 on Swift 5.7.1 targeting macOS 10.15+. I do not have mutating anywhere in my code:
import ArgumentParser

@main
struct Command: AsyncParsableCommand {
    static let configuration = CommandConfiguration(
        abstract: "…",
        subcommands: [
            Sub.self
        ]
    )
}

extension Command {
    struct Sub: AsyncParsableCommand {
        func run() async throws {
            try await …
        }
    }
}

Works for command sub for me

i have the same issue, it never runs the run function, my code looks correct - have been stuck on this for hours now.


Swedish translations updated based on latest Pootle data

Jeffrey Schiller should make a sanity check since this is my first PR of these files :)

Hi Jeff,
Thanks for your help. Is the problem in the Pull request or elsewhere?
I will ask "my" users to give it a try on ai2-test.

@carlrobert http://ai2-test.appinventor.mit.edu is ready for you to test against. Let me know if all is well and I can merge this change into the master branch. Once this is done, we are planning a non-component release within a day or so that would include this change.
I made a few changes to your PR to make things work. Later today I'll put a Pull Request in against your repo that will let you see the changes that I made.

Looks good to me. OK to deploy on master.

MERGED!

Hi Jeff,
Two brief follow-up questions:

I can't seem to find any changes made to my pull request. Did the files work out as is?
For, as yet, non-localized strings, what is the procedure for getting them into Pootle? There a number of items that still need localization based on feedback from my reviewers.

I just added a Pull Request on your "fork" (PR #1) which outlines the
changes I made. You can close it when you like, it is just there for your
information.
I'll try to update the English in Pootle later this week (have a few
other things to get done first).

-Jeff
On Saturday, April 16, 2016, Robert Storlind<EMAIL_ADDRESS>wrote:

Hi Jeff,
Two brief follow-up questions:

I can't seem to find any changes made to my pull request. Did the files
work out as is?
For, as yet, non-localized strings, what is the procedure for getting
them into Pootle? There a number of items that still need localization
based on feedback from my reviewers.

—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/mit-cml/appinventor-sources/pull/743#issuecomment-210828885

--

Jeffrey I. Schiller
Information Systems and Technology – MIT App Inventor
Massachusetts Institute of Technology
77 Massachusetts Avenue  Room 32-386
Cambridge, MA 02139-4307
617.910.0259 - Voice
<EMAIL_ADDRESS>http://jis.qyv.name
http://appinventor.mit.edu


[Dojo] add dojo-core interfaces into their file + snake_case contracts

To follow your comment @tarrencev I've moved the interfaces into their respective file.
Also, as I saw your snake_casing initiative, I have done it too.
By the way, the snake_casing of the world and executor contracts has an impact on the dojo-lang and dojo-world.
Modifications were made accordingly + refacto into constants to allow future changes.
Let me know if it's wasn't planned, and I'll remove this snake_casing. :+1:

awesome thank you!


Stochastic Treatment TMLE

This is another valuable addition to TMLE (that I also need as part of a project I am working on). Essentially, this would allow more complex treatments than treat-all vs. treat-none, similar to custom treatments in the g-formula.
What it does is shift the probability of A distribution. However, the single-step convergence of TMLE is no longer valid. I would need to iteratively estimate Q* until it epsilon converges to 0. This should be easy enough. After convergence, follows the remainder of the TMLE procedure
Likely best if I make this separate from TMLE
Starting points;
https://github.com/tlverse/tmle3shift
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4117410/#SD1

General reminder to myself: stochastic treatment TMLE is no longer a one-step fit. There has to be an interative process of estimating Q* until convergence criteria is met. This means repeating the targeting step several times. while loop for this with either a convergence criteria or max_iters criteria should be the solution

Added as part of 0.8.2


ISSUE WITH uploadMetas.js FILE

Version

[X] Yes

General Question

[X] No

What happened?
When I run uploadMetas.js, it gives me this error. Please tell me how I can solve the problem.
What have you tried?
I've tried restarting the computer, and running the program multiple times.
Relevant log output
CATCH ERROR: TypeError: Cannot read properties of undefined (reading 'response')
Retrying
NOK: Failed to upload metadata to IPFS
Retrying
ERROR STATUS: 502
Retrying
CATCH ERROR: TypeError: Cannot read properties of undefined (reading 'response')
Retrying
ERROR STATUS: 502
Retrying
CATCH ERROR: TypeError: Cannot read properties of undefined (reading 'response')
Retrying
NOK: Failed to upload metadata to IPFS
Retrying
NOK: Failed to upload metadata to IPFS
Retrying
ERROR STATUS: 502
Retrying
CATCH ERROR: TypeError: Cannot read properties of undefined (reading 'response')
Retrying
ERROR STATUS: 502
Retrying
ERROR STATUS: 502
Retrying
NOK: Failed to upload metadata to IPFS
Retrying
CATCH ERROR: TypeError: Cannot read properties of undefined (reading 'response')
Retrying
CATCH ERROR: TypeError: Cannot read properties of undefined (reading 'response')
Retrying
ERROR STATUS: 429
Retrying
CATCH ERROR: TypeError: Cannot read properties of undefined (reading 'response')
Retrying
ERROR STATUS: 429
Retrying
CATCH ERROR: TypeError: Cannot read properties of undefined (reading 'response')
Retrying
NOK: Failed to upload metadata to IPFS
Retrying
NOK: Failed to upload metadata to IPFS
Retrying
NOK: Failed to upload metadata to IPFS
Retrying
NOK: Failed to upload metadata to IPFS
Retrying
NOK: Failed to upload metadata to IPFS
Retrying
NOK: Failed to upload metadata to IPFS
Retrying
ERROR STATUS: 502
Retrying
CATCH ERROR: TypeError: Cannot read properties of undefined (reading 'response')
Retrying
ERROR STATUS: 502
Retrying
CATCH ERROR: TypeError: Cannot read properties of undefined (reading 'response')
Retrying
NOK: Failed to upload metadata to IPFS
Retrying
ERROR STATUS: 502
Retrying
CATCH ERROR: TypeError: Cannot read properties of undefined (reading 'response')
Retrying

Protect your information

[X] I Agree

Do you fixed it??

I had the exact same problem for a couple days I found out my internet provider xfinity had a security that was blocking it so I went on my xfinity modem app amd turned of the security and it worked perfect, you probably just need to get your internet provider and look up how to turn off it's security

I have a similar issue, but before this. I encountered a TypeError and check in the meta data json, it is missing the "custom_field.edition" tag. So i added it, and run the script again and got this same error as you guys.

I have a similar issue, but before this. I encountered a TypeError and check in the meta data json, it is missing the "custom_field.edition" tag. So i added it, and run the script again and got this same error as you guys.

can you tell me where'd you add the tag


getInverterList v1 api isnt working anymore

Good morning,
Firstly thank you so much for writing this. I've just got my PV installed and was expecting to have to use solarman only to find I had an S3 stick. Your interface with the API is awesome.
I was playing with it last night and I've noticed your getInverterList call isnt working.
2024-02-27 09:59:51.962 DEBUG (MainThread) [custom_components.pyscript.eval] file.solis_control.solis_control: calling post("https://www.soliscloud.com:13333/v1/api/inverterList", {'data': '{"stationId":"XXXXXX"}', 'headers': {'Content-MD5': 'XXXXXXXX==', 'Content-Type': 'application/json', 'Date': 'Tue, 27 Feb 2024 09:59:51 GMT', 'Authorization': 'API XXXXXX='}})
2024-02-27 09:59:52.199 DEBUG (MainThread) [custom_components.pyscript.eval] file.solis_control.solis_control: calling json(, {})
2024-02-27 09:59:52.201 ERROR (MainThread) [custom_components.pyscript.file.solis_control.solis_control] Exception in <file.solis_control.solis_control> line 92:
for record in inverterList['data']['page']['records']:
Using Chrome tools I see the page is calling listV2 now.
https://www.soliscloud.com:15555/inverter/listV2
The response looks good
{
"success": true,
"code": "0",
"msg": "success",
"data": {
"page": {
"records": [
{
"id": "xxxxx",
I have tried to update the
INVERTER_URL= '/inverter/listV2'
and port 15555 but it didnt work.
response = await session.post("https://www.soliscloud.com:15555"+INVERTER_URL, data = body, headers = header)

2024-02-27 10:11:54.840 DEBUG (MainThread) [custom_components.pyscript.eval] file.solis_control.solis_control: calling post("https://www.soliscloud.com:15555/inverter/listV2", {'data'...
2024-02-27 10:11:54.945 ERROR (MainThread) [custom_components.pyscript.file.solis_control.solis_control] Exception in <file.solis_control.solis_control> line 93:
for record in inverterList['data']['page']['records']:
^
KeyError: 'data'
Are you already aware of this problem. If I manually configure the inverterId the rest of the script works. Is there any reason why you dont just pass it in as a config item unless you are expecting people to have more than 1 inverter? You can harvest the inverer Id from solis cloud.
https://www.soliscloud.com/#/station/inverter/inverterdetail?id=INVERTERID&stationId=xxxx

I am nut sure but think I get the same error since yesterday (29 feb) (my chinese is not so good)

Strange. I’ve commented your inverter def and just pass my inverter id
directly and that’s working fine. Oh well doesn’t matter, what I have works
fine and is one less api call so all good.
On Fri, 8 Mar 2024 at 08:57, stevegal @.***> wrote:

Still working fine for me. Check your configuration for password and api
key values in case you are getting rejected due to incorrect values in
either of those.
I haven't been able to get hold of any documentation for the other
versions of the api, but I suspect the v2 ones have a slightly different
authorization mechanism.
—
Reply to this email directly, view it on GitHub
https://github.com/stevegal/solis_control/issues/16#issuecomment-1985303243,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFMFL5EHXLO7C6JV24QX2MTYXF4PZAVCNFSM6AAAAABD33JSOKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBVGMYDGMRUGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

I have the same issue:
Exception in <file.solis_control.solis_control> line 92:
for record in inverterList['data']['page']['records']:
^
KeyError: 'data'
I have checked and re-checked the config.
I too have commented out the inverter def block - thanks aymsley.

I've now had a few people with this error. I was wondering if you could provide some debug for me as it's working fine with my inverter. can you log the response of your solis inverterList by adding log.warning(str(inverterList)) after line 90 where we make the post call and before I look for the inverterId in the response (line 92) and see if there is an error message there.
Thanks

can I close this issue?

Absolutely

see updated README for missing link as to where to find the plantId


Introduce an OpenSearch output plugin for Logstash

Requirement/Problem - what kind of business use case are you trying to solve?
Many people who use open source Elasticsearch use Logstash for data ingestion. People will want to continue to use their Logstash deployments as they transition to OpenSearch. To make that transition easier, it would be good to provide an specific OpenSearch output plugin for Logstash that is tested and guaranteed to work.
Proposal - what do you suggest to solve the problem or improve the existing situation?
We build an OpenSearch output plugin for open source Logstash 7.x. We should package this plugin with the most current version of Logstash available and provide a link to the installable binary. My proposal is to support the following:

OpenSearch 1.x
Elasticsearch OSS 7.x. This is to provide backwards compatibility for people still using older version of Elasticsearch OSS and enable them to run newer versions of Logstash such as 7.13.x
ODFE 1.x. This is for the same backwards compatibility reasons as Elasticsearch OSS.
(To be discussed) There are other output plugins like the Amazon ES one that just add auth. It would be nice to have this output plugin support a variety of authentication mechanisms so that there doesn't need to be a new output plugin just to add a new type of authentication.

This is https://github.com/opensearch-project/logstash-output-opensearch. Closing the issue.


Error when creating cloud scheduler

Hey there!
I did my best to avoid submitting a request but I wanted to reach out. The steps I've taken include deleting my first staging project and creating a new staging project just to make sure I didn't miss a step in the process.
I am getting two errors at the last stage of the script when it tries to create a cloud scheduler. See the errors below and the screenshot here https://d.pr/i/BrTjGp .
ERROR: (gcloud.app.create) The project [myproject-name] already contains an App Engine application in region [us-central].  You can deploy your application using `gcloud app deploy`.
ERROR: (gcloud.scheduler.jobs.create.http) argument --uri: Bad value []: Must be a valid HTTP or HTTPS URL.

I am using a brand new project to test out the script prior to installing on a production project.
I hope this is enough information to get started. Let me know if I should provide more details.
Thank you.

The latest updates fix this issue since the deploy script no longer creates the scheduler and users are instructed to use the Google Cloud UI.


add --no-babelrc option

Ref https://github.com/babel/babel.github.io/pull/898#discussion_r76549902 @loganfsmyth

But if I want to override this, is it possible ?

In the above case no. But then maybe we would say just use babel-cli then?

I personally found it surprising that babili would pick up .babelrc configs. From a user standpoint, the fact that it's implemented with Babel seems like it should be an implementation detail. If you want to use a .babelrc, it seems to me like you should use the babel cli instead.

👍


.progress() method for CallbackCounted

#396

Nice 👍  But I think count should stay the way it was as to not break anything. Please just make remaining save the total call amount and leave other things unchanged.

Is it possible, to break anything? count is a private field that's not accessable from anywhere except the class it contains as far as I know. Even from children.

Just to be sure and to keep changed to a minimum. There is no benefit of these changes, is there.

What about this? I'm placing count decreasement before the callback execution, otherwise .progress() returns a wrong value (that's > 0) before the callback very first execution.

I don't think that's good, now count values will be different. The original behavior must not be changed by this PR.

It seems fine now, please add some assertions for the callback before the first invocation.

add some assertions for the callback before the first invocation

Like the last two lines of code?

Missed that on phone 👍
Can you please fix the circleci build?
Check this: https://circleci.com/docs/2.0/oss/#build-pull-requests-from-forked-repositories
Fork builds are enabled on my side, seems like you have to follow the second note:

Note: If a user submits a pull request to your repository from a fork, but no pipeline is triggered, then the user most likely is following a project fork on their personal account rather than the project itself of CircleCi, causing the jobs to trigger under the user’s personal account and not the organization account. To resolve this issue, have the user unfollow their fork of the project on CircleCI and instead follow the source project. This will trigger their jobs to run under the organization when they submit pull requests.

Fixed?

I see, your fork isn't up to date with upstream, consider merging. Looks good now, thanks 👍


New Python Code

Well I have done DSA majorly in Python only so I thought I shall add a few codes in python directory of this repo so that I can stay in touch with GitHub. Please assign this issue to me @lovishprabhakar02 .
Things am gonna do:

Create a directory for python
Add files for python codes.

All yours! @cyberbuddy-manas , and sure, I will add cpp code in a while

@lovishprabhakar02 CPP folder is soon going to be added by @pacific-prashant and I shall wait for someone to add python issue so that other people get a better chance at this.


it needs bumpup versions for k8s.

In case of k8s environment, as it is mentioned in issue #221,
it needs to remove entries from ingress configmap while minifab cleanup operation.
unfortunately, under openshift v0.11.0, the above is impossible because of bugs in dependency libs.
to support the above feature, it requires to use latest kubernetes.core and cloud.common.
in short, the following bumpups are needed to fix issue 221.
# pip list
openshift            latest(>=0.12.0)

# ansible-gallaxy collection list
cloud.common         latest(>=2.0.3)
kubernetes.core      latest(>=2.0.2)
community.kubernetes latest(>=2.0.0)

opensift v0.12.0 can redirects k8s ops to kubernetes.core via latest community.kubernetes,
and kubernetes.core can involve latest cloud.common...
cf. when I bump up ansible to v4.1.0,
ansible 4.1.0 redirects k8s ops to kubernetes.core without community.kubernets nor openshift
but it may be risky to use ansible 4.x at this moment.

@litong01 the following is the minimum patch to archive bumpup. what dou you think? any suggestion?
diff --git a/Dockerfile b/Dockerfile
index 98017e2..5fd08ba 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -12,7 +12,8 @@ COPY . /home
 COPY plugins /usr/lib/python3.8/site-packages/ansible/plugins
 COPY pypatch /usr/lib/python3.8/site-packages/Crypto/Random/Fortuna
 RUN rm -rf /var/cache/apk/* && rm -rf /tmp/* && apk update && \
-    pip install openshift==0.11.2 requests google-auth && \
+    pip install openshift requests google-auth && \
+    ansible-galaxy collection install cloud.common kubernetes.core community.kubernetes && \
     dos2unix -q /home/main.sh /home/scripts/mainfuncs.sh \
     /usr/lib/python3.8/site-packages/ansible/plugins/callback/minifab.py && \
     apk del dos2unix && rm -rf /var/cache/apk/* && rm -rf /tmp/*

I do not mind using ansiblen4.x and newer openshift library. Since we package everything in a container, as long as the tests are successful, we should be ok. We test different versions at the gate(ci/cd)

That pictured showed how many fabric versions we test at the gate

@litong01 minimum patch for ansible 4.1.0 version is following.
when I tested with this ansible 4.1.0, I got error in plugins/callback/minifab.py. testing with '-f default' option seems ok.
to pass CI/CD test, fixing this callback feature is required. but I have no time to work with it.
Which version (2.x or 4.x)  you want?
ERROR! Unexpected Exception, this is probably a bug: cannot import name 'codeCodes' from 'ansible.utils.color' (/usr/lib/python3.8/site-packages/ansible/utils/color.py)

# because...
grep codeCodes /usr/lib/python3.8/site-packages/ansible/utils/color.py  | wc -l
0

pip list | grep ansible
ansible           4.1.0
ansible-core      2.11.2

# minimum patch for ansible 4.x

diff --git a/Dockerfile b/Dockerfile
index 98017e2..b03bbe5 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -4,15 +4,17 @@ LABEL<EMAIL_ADDRESS>
 ENV PYTHONUNBUFFERED=1

-RUN apk add --update py-pip bash ansible docker-cli openssl xxd dos2unix && \
+RUN apk add --update py-pip bash         docker-cli openssl xxd dos2unix py3-cryptography && \
     if [ ! -e /usr/bin/python ]; then ln -sf python3 /usr/bin/python ; fi && \
-    mkdir -p /usr/lib/python3.8/site-packages/Crypto/Random/Fortuna
+    mkdir -p /usr/lib/python3.8/site-packages/Crypto/Random/Fortuna \
+             /usr/lib/python3.8/site-packages/ansible/plugins

 COPY . /home
 COPY plugins /usr/lib/python3.8/site-packages/ansible/plugins
 COPY pypatch /usr/lib/python3.8/site-packages/Crypto/Random/Fortuna
 RUN rm -rf /var/cache/apk/* && rm -rf /tmp/* && apk update && \
-    pip install openshift==0.11.2 requests google-auth && \
+    pip install ansible kubernetes requests google-auth && \
+    ansible-galaxy collection install cloud.common kubernetes.core && \
     dos2unix -q /home/main.sh /home/scripts/mainfuncs.sh \
     /usr/lib/python3.8/site-packages/ansible/plugins/callback/minifab.py && \
     apk del dos2unix && rm -rf /var/cache/apk/* && rm -rf /tmp/*


ISPN-5367 Cache putMap/getAll usage of SegmentAwareMap/Set performance

investigation

Use standard map to prevent iteration over all entries multiple times

https://issues.jboss.org/browse/ISPN-5367

In my testing using https://gist.github.com/mcimbora/5c404d98a13b38bbecc4 and running master and the new version I saw about 10% performance increase when using 3-5 nodes.

Pushed, thanks


feat: add client credentials capabilities for ocm client

Summary
Makes it possible to use client credentials to authenticate OCM client.

/retest

Tested with Token, with Client Credentials, and without any connection details and all behavior is as expected.


improve bucket size aggregation limit

postpone bucket size aggregation limit for terms aggregation when converting to intermediate aggregation result
improve min_doc_count special use case 0, it loaded more texts from the
dict than segment_size limit
Note that we effectively check now that segment_size does not exceed the
bucket limit, since that's the number of bucket when converting into an intermediate bucket.
segment_size is 10 * size. So requests would fail with size 6500 for a bucket limit of 65000.
That behavior is probably good for Quickwit, since we pass intermediate results between nodes, so we should have the circuit breaker on the intermediate result level.
It's not great for use cases where we have many segments in a single index, since they could easily add up to hit the bucket limit, since the formula is now: #num_segments * segment_size < bucket limit (if all segments have enough results)
closes https://github.com/quickwit-oss/tantivy/issues/1822

Superseeded by https://github.com/quickwit-oss/tantivy/pull/1942


On orientation change there is gap for some of the list items .

any solution? I'm getting frustated for this

I too faced this issue and solved it by handling onConfigurationChanged(Configuration newConfig) event and resetting the adapter


Browsing latest APIM docs from docs.wso2.com gives a 404

Description:
Latest APIM docs link gives a 404. See below
https://github.com/wso2/docs-apim/assets/57770159/0bc060b3-f30a-4911-ab2f-2813835953d4
Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

Hi @wx-yz,
I have informed the marketing team and requested them to update the link on the documentation portal.
Mail: "Request to fix invalid link on the Documentation Dashboard"
Thanks & Kind Regards,
Dinithi

Closing the issue since it has been fixed now.


Migrate dart sass

This resolves #60 and migrates node-sass to dart-sass. This may also resolve #45

Hmm... I still can't get the Netlify build to succeed. I updated the dependencies, set it to use node v18, but am now running into issues building the Lamda. I'm not a Node developer, so not quite sure how to proceed
11:47:28 AM: Error: error:0308010C:digital envelope routines::unsupported
11:47:28 AM:     at new Hash (node:internal/crypto/hash:71:19)
11:47:28 AM:     at Object.createHash (node:crypto:133:10)
11:47:28 AM:     at module.exports (/opt/build/repo/node_modules/webpack/lib/util/createHash.js:135:53)
11:47:28 AM:     at NormalModule._initBuildHash (/opt/build/repo/node_modules/webpack/lib/NormalModule.js:417:16)
11:47:28 AM:     at handleParseError (/opt/build/repo/node_modules/webpack/lib/NormalModule.js:471:10)
11:47:28 AM:     at /opt/build/repo/node_modules/webpack/lib/NormalModule.js:503:5
11:47:28 AM:     at /opt/build/repo/node_modules/webpack/lib/NormalModule.js:358:12
11:47:28 AM:     at /opt/build/repo/node_modules/loader-runner/lib/LoaderRunner.js:373:3
11:47:28 AM:     at iterateNormalLoaders (/opt/build/repo/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
11:47:28 AM:     at iterateNormalLoaders (/opt/build/repo/node_modules/loader-runner/lib/LoaderRunner.js:221:10)
11:47:28 AM:     at /opt/build/repo/node_modules/loader-runner/lib/LoaderRunner.js:236:3
11:47:28 AM:     at context.callback (/opt/build/repo/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
11:47:28 AM:     at /opt/build/repo/node_modules/babel-loader/lib/index.js:44:71 {
11:47:28 AM:   opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
11:47:28 AM:   library: 'digital envelope routines',
11:47:28 AM:   reason: 'unsupported',
11:47:28 AM:   code: 'ERR_OSSL_EVP_UNSUPPORTED'

Node v14 seems to work great. v18 of node was failing with generating the Lamda. I'm not a Node developer, so 🤷♂.
Either way this seems to be working, does deployments, and is now updated.


How do I encrypt the credentials file using Python?

We use leased credentials in order to access our DBs.
I would like to generate the credentials-config.json dynamically, using Python.
It looks like you use the ContentEncrypter
https://github.com/dbeaver/dbeaver/blob/be7a12a3bf2c3dfd3122a9bdfcbd41d06b878900/plugins/org.jkiss.dbeaver.registry/src/org/jkiss/dbeaver/registry/DataSourceSerializerModern.java#L258 to encrypt the entire config file.
How would I obtain the local secret key?

Hi, @zzztimbo!
Did you solve this with python?
I'm trying to do this because I'm connecting to Google cloud databases and passwords expire after some time. And I'm trying to build a script to automate the generation of new passwords and update the dbveaver connection settings.
Thanks

Pretty much related: #9413


Incompatibility with Bootstrap?

Hello,
If you put the "zoomgallery" inside a bootstrap carousel and you click on an image, it opens correctly; however when closing, it doesnt return to its correct location. This is due to the class "item" needed in the bootstrap carousel. Any idea how to fix this?
Thank you in advance.

Hi @michelabikhalil sorry for never answering this, as you may notice this project died a long time ago.
I will archive this repository


GPII-1308:  Update to use smtp-server...

In working on the tests for the new user management module, I noticed a few shortcomings in our mail test module that made it harder to work with the standard test framework.  This pull request addresses those concerns.
See GPII-1308 for details.

As I have updated the code surrounding the duplicated addRequiredSequences, I wanted to comment here so that it wasn't missed.  I am proposing submitting a wrapper grade as part of Kettle itself.  I am happy to prepare a pull request, or to have you do it, or to put it somewhere else.  I just need your input.


Webpack & entrypoints.json

Hello,
I am using Webpack 5.0 and Webpack Encore from Symfony framework.
I noticed the generation of outgoing media stylesheets is done before Webpack setup its output directory.
So these media files get deleted, if put inside the same directory as Webpack output.
Additionally, there is no entrypoints.json. Would it be easy to do ?
For instance, I basically define an "app" entry and I get "app-mobile.css".
So at the moment the loading of this file is hardcoded, but I need to make it more dynamic.
Thank you for the hard work. This plugin is great for optimization !

Additionally, I just noticed that the outgoing css files does not relate to the entry defined in Webpack, but the basename of the extracted stylesheet.
e.g. ["app" => "path/to/my/app.test.css"]
Webpack is returning app.css, but here the plugin is returning app.test-mobile.css instead of app-mobile.css.
(At least I would expect that from Webpack point of view.)

I just found that media-query-pluging is better fit for Webpack. Thanks !


Add keywords to quickstarts JSON schema

Description
Now that keywords have been added to most packs, we want to verify that new PRs follow the correct syntax. This will be done via the JSON schema.
The correct form for keywords is:
keywords:
  - cloud computing
  - something else

AC

[ ] keywords are adding to the JSON schema as an array of strings
[ ] If the schema check fails, the output has enough information for the user to fix their issue
[x] Contributing doc is updated to include keywords

I documented keywords in this PR https://github.com/newrelic/newrelic-observability-packs/pull/192


Reddit NFL Streams.!! ways to watch NFL Week 10 Live FREE Streams Crackstreams

NFL fans have gotten a few extra hours of sleep the past few weeks, but it’s time for die-hards to wake up early again as the league heads over to Germany. The Giants and the Panthers will face off in Munich in the last overseas game of the year.
 Kansas City looks set to continue its undefeated stream, facing a beleaguered Broncos team. And the Detroit Lions will be in the spotlight Sunday night as they continue their very impressive seasons.
There are a variety of ways to take in the action. Here’s all you need to know about this week’s games.
Which NFL teams are playing this week? And what channels are airing the games?
As always, the home team is listed second.
Sunday, Nov 10
New York Giants vs. Carolina Panthers, 9:30 a.m. ET on NFL Network
New England Patriots vs. Chicago Bears, 1:00 p.m. ET on Fox
San Francisco 49ers vs. Tampa Bay Buccaneers, 1:00 p.m. ET on Fox
Denver Broncos vs. Kansas City Chiefs, 1:00 p.m. ET on CBS
Buffalo Bills vs. Indianapolis Colts, 1:00 p.m. ET on CBS
Pittsburgh Steelers vs. Washington Commanders, 1:00 p.m. ET on CBS
Minnesota Vikings vs. Jacksonville Jaguars, 1:00 p.m. ET on Fox
Atlanta Falcons vs. New Orleans Saints, 1:00 p.m. ET on Fox
Tennessee Titans vs. Los Angeles Chargers, 4:05 p.m. ET on Foc
New York Jets vs. Arizona Cardinals, 4:25 p.m. ET on CBS
Philadelphia Eagles vs. Dallas Cowboys, 4:25 p.m. ET on CBS
Detroit Lions vs. Houston Texans, 8:20 p.m. ET on NBC
Monday, Nov. 11
Miami Dolphins vs. Los Angeles Rams, 8:15 p.m. ET on ABC and ESPN
How can I watch NFL games for free—even if I am out of market?
The best way to watch any sort of network programming for free on a big screen is with a good HD antenna. To ensure you’re getting the most reliable signal, be sure to test the antenna in multiple locations in your home.
Can I stream 2024 NFL games live online if I don’t have a cable subscription?
Yes and there are a number of different options to do so.
Paramount+
CBS’s streaming service will give you a one-week free trial, followed by a $8 or $13 monthly charge. (An annual plan is as low as $30 right now.)
Peacock
NBC’s streaming service will give you access to several games, including all upcoming Sunday night matchups. It carries a $8 or $14 monthly charge—and the service has recently done away with its free trial. (The free version of Peacock does not include live sports.)
Disney+
Disney’s bundle of Disney+, Hulu and ESPN+ no longer has a free trial, so you’ll have to pay $17 per month for all three combined (or $30 per month for no ads on Hulu).
Including Live TV in the bundle bumps the price to $77 per month ($90 with no ads).
Hulu with Live TV
The free trial on this service lasts three days. Afterward, it will cost you $77 per month.
YouTubeTV
After a free trial, you can expect monthly charges of $73.
Sling TV
Dish Network’s Sling lower-tiered “Orange” plan will run you $40 per month. Adding the more comprehensive “Blue” plan bumps the cost to $55 per month. The seven-day free trial has disappeared, unfortunately.
DirecTV Stream
Formerly known as DirecTV Now, AT&T TVNow and AT&T TV, this oft-renamed streaming service will run you $80 per month and up after the free trial option. (The package that includes NFL Network will run you $99 per month.)
Fubo TV
This sports-focused cord-cutting service carries broadcast networks in most markets. There’s a seven-day free trial, followed by monthly charges of $80 and up, depending on the channels you choose.
Can I watch NFL games on Amazon?
Not for the Sunday or Monday games. Amazon, however, is the home of Thursday Night Football once again, with the exception of Thanksgiving (though it will air a game on Black Friday). The first matchup on Amazon this year will be the Washington Commanders facing the Philadelphia Eagles on Nov. 14.
Does the NFL offer any viewing packages to watch the games I want?
A trio, in fact.
NFL App
The NFL App will let you stream games that are being broadcast locally in your market on Sundays. If you want to watch an “out of market” game, you’ve got two choices.
NFL+
Watch live local and out of market games and (with the premium subscription) replays. You’re looking at a $50 charge per season. ($100 for premium.)
NFL Sunday Ticket
YouTube once again is the home for this channel.

ED
cxvxcv

Watch NFL Week 10 Live streams Online Free Form Anywhere
🏈NFL Live Link⤵
𝗟𝗶𝘃𝗲 𝐋𝐢𝐧𝐤📺 https://bit.ly/3CjjH1N
𝗟𝗶𝘃𝗲 𝐋𝐢𝐧𝐤📲 https://bit.ly/3CjjH1N
𝗟𝗶𝘃𝗲 𝐋𝐢𝐧𝐤🌍 https://bit.ly/3CjjH1N
live 🏈NFL streams online⬆

Watch NFL Week 10 Live streams Online Free Form Anywhere
🏈NFL Live Link⤵
𝗟𝗶𝘃𝗲 𝐋𝐢𝐧𝐤📺 https://bit.ly/3CjjH1N
𝗟𝗶𝘃𝗲 𝐋𝐢𝐧𝐤📲 https://bit.ly/3CjjH1N
𝗟𝗶𝘃𝗲 𝐋𝐢𝐧𝐤🌍 https://bit.ly/3CjjH1N
live 🏈NFL streams online⬆

Watch NFL Week 10 Live streams Online Free Form Anywhere
🏈NFL Live Link⤵
𝗟𝗶𝘃𝗲 𝐋𝐢𝐧𝐤📺 https://bit.ly/3CjjH1N
𝗟𝗶𝘃𝗲 𝐋𝐢𝐧𝐤📲 https://bit.ly/3CjjH1N
𝗟𝗶𝘃𝗲 𝐋𝐢𝐧𝐤🌍 https://bit.ly/3CjjH1N
live 🏈NFL streams online⬆

Watch NFL Week 10 Live streams Online Free Form Anywhere
🏈NFL Live Link⤵
𝗟𝗶𝘃𝗲 𝐋𝐢𝐧𝐤📺 https://bit.ly/3CjjH1N
𝗟𝗶𝘃𝗲 𝐋𝐢𝐧𝐤📲 https://bit.ly/3CjjH1N
𝗟𝗶𝘃𝗲 𝐋𝐢𝐧𝐤🌍 https://bit.ly/3CjjH1N
live 🏈NFL streams online⬆


Setter state "as" attribute is getting ignored

Describe the bug
The as parameter is getting ignored. In the following example the variable would be still stored under var.mykey instead of var.mydata.
- id: get
  type: getter
  variables:
  - key: mykey
    scope: namespace
    as: mydata

This is only the case if the variable does not exist. The result is that the variable is getting renamed if it exists otherwise not. That causes a problem if there is a switch checking if the value is null.

Issue title doesn't match example. Does this issue refer to getters, or setters?


Do we need CI checker on PR or push?

This CI checker can run some tests on different Linux distributions, even in MacOS. I notice that Github workflow supports MacOS.

buidling testing can be also included.


White lines flickering around edges during transitions

Version
Tell us which versions you are using:

react-native-router-flux v3.37.0
react-native v0.37.0

Expected behaviour
There would be no white lines flickering.
Actual behaviour
I'm aware of this as being an issue in other places (here and here) however all of the solutions are about styling the Navigator component which is something that isn't exposed with this plugin. I haven't been able to find anything specific to react-native-router-flux that applies a solution. I saw someone had made a commit on a fork which looks similar to the solutions I've read about elsewhere but didn't know if it had actually made it back into the build.
See this video for an example: https://www.dropbox.com/s/08vxhuka1svn10o/white-flickering-during-transitions.mov?dl=0
Steps to reproduce

Create an app with black backgrounds
2.Transition between scenes and notice the edges

I've been running into this too - super annoying. Going to see if I can come up with a decent solution.

I noticed these as well, but only on the iOS emulator. After building to an actual device, it didn't seem to be an issue.

I still am seeing it on real devices unfortunately.

Alright so it looks like if we simply add a transparent background to the NavigationCard component the white lines go away!
Example:
 <NavigationCard
      {...props}
      key={`card_${key}`}
      style={[animationStyle, style, { backgroundColor: 'transparent' }]}
      panHandlers={panHandlers}
      renderScene={this.renderScene}
    />

Source:
https://github.com/aksonov/react-native-router-flux/blob/master/src/DefaultRenderer.js#L253

@timkendall thanks for working on this! Want to make a PR?

@dwilt doing it now!

@timkendall  Even though I set background color as transparent still flickering occurs

const sceneConfig = {
cardStyle: {
backgroundColor: 'transparent'
}
}
<Scene key="root" {...sceneConfig}>
This worked for me for v4


Motion sensors not updating in Home assistant

Noticed recently motion sensors not triggering automations, found when inside EUFY security app if notifications for motion sensor are turned off then home assistant state is not updated
Steps to reproduce the behavior:

Open Eufy secruity application
click on "security" adjust "XX mode" disable motion sensors notification > save
attempt to trigger automation with notifications turned off
when notifications inside of eufy security app are turned off > HA does not change motion sensor state

yes, you have to go through README

Sorry what did I miss in the Readme section?

Old README:
**Create a separate account for HA integration as that account will be logged out automatically from mobile app when HA integration logged in. Do not forget to share your cameras with your new account (preferably with adming rights), enable motion notifications with full picture and enable push notifications. This integration depends on push notifications to catch any updates.**

New README:
**As we already called out earlier, add-on heavily relies on push notifications, so you must enable all kind of push notifications (motion detected, person detected, lock events, alarm events etc) in your mobile app. These notifications are not user based but device based so after enabling all these notifications, your main account will probably bloated with many push notifications. In android, there is a setting to disable specific notifications, please use it. **

Any future plans to change Push notifications for the HA trigger?

there is no option to get the states from sensors without enabling push notifications. do you have any idea in your mind?

No not at all, Sorry new just very curious!

Or let me put in a different way, there are 2 ways of getting data;

you can pull it from somewhere regularly. this is very consuming because you have to check it regularly and gets very demanding if you are looking for motion sensor. you have to pull every second maybe?
something can push it to you when it has changed. when a notification arrives to add-on, we can react on it and this is very light weight to achive.

I guess pulling it from home base directly in out of the question ?
as it seems to monitor state changes

I know for android you can go in and change the notifications on your phone so you don't get spammed for motion alerts on your phone


[FLINK-16829] Refactored Prometheus Metric Reporters to Use Constructor Initialization

What is the purpose of the change
Clean-up for the initialization of the two Prometheus Metric Reporters (PrometheusReporter and PrometheusPushGatewayReporter) by explicitly passing in arguments to the constructors as opposed to relying on resolving these values via the internal configuration properties.
Brief change log

Removed argument resolution against defaults from the open() functions and instead resolved those within the factories and passed them into the respective reporter instances (roughly modeled after the JmxReporter implementation)

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

@zentol
I through together what a draft of these changes might look like. It was roughly modeled after the JmxReporter implementation which seemed to do something similar (i.e. resolve the port and pass that into the constructor). Since I'm still familiarizing myself with the codebase, I tried to follow conventions that I had seen there (e.g. the use of the config suffix for the arguments passed into the constructor), which I wasn't crazy about but kept them in case that was a common convention that I was unaware of.
Any feedback or changes? I noticed that after running a mvn clean verify per the contribution guide that there were some test failures, but they didn't seem related to these changes (or potentially flaky tests). I have a larger Azure Pipelines build queued as well to run it in a separate environment.
Thanks!

@zentol
I'll be submitting another PR once this work is done, ran into some git issues and decided to scorch the earth in the interested of keeping things clean.


Japan Support

Does Azure Data Box Disk support in Japan East Region as written in the document?
The pricing page does not show the pricing for East Japan Region.
Also, according from Products available by region site, it say both Japan Region support Data Box Disk as in GA.
Which will cause conflict between the this document.
May I ask Actual Support Status for Japan Region.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 037a0a65-382e-b2c4-4bf9-b393dd1ece69
Version Independent ID: 28c0046d-44af-c91e-1c84-b6fcfcd51be4
Content: Microsoft Azure Data Box Disk overview
Content Source: articles/databox/data-box-disk-overview.md
Service: databox
Sub-service: disk
GitHub Login: @alkohli
Microsoft Alias: alkohli

https://azure.microsoft.com/en-us/global-infrastructure/services/?products=databox&regions=japan-east,japan-west
Adding resource

@KeiroKamioka0000, Thanks for the feedback!I have assigned the issue to the content author to investigate further and update the document as appropriate.

@KeiroKamioka0000 Yes. Data Box Disk is generally available in Japan.
I believe the pricing changes on the page are in progress. For now, you can refer to EU pricing and view it in the Japanese Yen to communicate to customer (the break up of pricing will be the same except there may/may not be slight changes only for the shipping costs).
Please let me know if this helps.


Request - Pull through Live data from Octopus Home Mini

I believe Octopus are now allowing access to the API data for live data from the Octopus Home Mini, would this be able to pull through to Home Assistant?

Hi @mark-summers. I tried looking at the APIs again yesterday but was still unable to retrieve current data. Do you know where you saw this?

Hi @BottlecapDave, I’m not sure if you have heard of the app Octo-Aid, but it tracks Octopus usage, he is managing to pull through the live data in the app now!

Unfortunately the app is not open source so I'm not sure what API they're using. They've possibly cracked/snooped the official app?
I've sent another message to Octopus Energy to see if they'll tell me. If not, I'll try emailing the app developer to see if they can help me out.

They are definitely using the API, he's pretty responsive as well so hopefully he will come back to you on it!

I just had a response from Octopus Energy

The team have informed me unfortunately not direct with Octopus, however if you want to link your Octo account to another app you can get your API key and more from your account and use it in another app.

So looks like I've have to see if the developer of the app is friendly enough to tell me their secrets. If I can find some contact information...

Might it be the requestConsumptionData mutation in the GraphQL API, with a suitably short and recent window?
If anyone has a Mini, and an app that is successfully querying its data, then might be worth a peek with Wireshark.

I may have found the endpoint. I'm currently testing the feature.

Just a quick update. I've got something up and running currently refreshing every minute. However I've seen a few instances where the API has fallen over at this rate and therefore the data doesn't quite match up the web dashboards., which isn't ideal.
I think I'm going to try and reduce the refresh rate, as the energy dashboard only supports seeing on an hourly basis, however I need to test if this has any other negative impacts (e.g. data being associated with the wrong time)

@BottlecapDave  happy to help test anything if you need it!

I've done a beta release of what I have so far, available at https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/releases/tag/octopus-home-mini-beta-1. I don't think this is available via HACS so might need to be installed manually. To get the sensors to appear, you need to edit your Octopus Energy account and tick "I have a Home Mini".
I've been seeing a few API gateway issues in my testing which has caused my numbers to be slightly off when compared to Octopus Energy. I think the numbers can also be effected by how Home Assistant buckets the data (when it's consumed/read vs when it's raised) in the energy dashboard so it might appear in the wrong hour block.

It feels like there ought to be a way to retrieve the data, that the Home Mini posts to Kraken, at a local level? I don't have mine yet (😞) so have no way to experiment. Does the Home Mini expose anything locally?
I'm assuming that the data it transmits will be encrypted, so proxying the post endpoint will not easily yield anything useful. I wonder whether the MCU inside has a debug port enabled.

@RobinXe There is a debug port and it looks like someone managed to get it into Home Assistant via raspberry pi (https://twitter.com/Incanus/status/1590825709114904576) - you could probably do something similar with an ESPHome. However it doesn't look like it's an official means ;)
I guess it's not in Octopus' interest to have it supply such a thing as the majority of their customers probably don't need it? Hopefully via a software update or v2 🤞

@BottlecapDave Oh nice! Good find! Thanks for that.
It looks like a nice little board in there, good to see they don't appear to have glued it together, and have included holes for standard headers!
I capitulated and have just ordered a Hildebrand Glow! 😜

I've done a beta release of what I have so far, available at https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/releases/tag/octopus-home-mini-beta-1. I don't think this is available via HACS so might need to be installed manually. To get the sensors to appear, you need to edit your Octopus Energy account and tick "I have a Home Mini".
I've been seeing a few API gateway issues in my testing which has caused my numbers to be slightly off when compared to Octopus Energy. I think the numbers can also be effected by how Home Assistant buckets the data (when it's consumed/read vs when it's raised) in the energy dashboard so it might appear in the wrong hour block.

I have downloaded the beta and all looks to be working fine, except it's not letting me add it to the energy dashboard as it is missing a statistic, am I doing something wrong?

Hmm that is odd, as I have it on my dashboard. Has this resolved itself? What is the exact error that is being displayed on the dashboard?

Ahh sorry, I was expecting to select Current Demand for the dashboard, I have since selected Current Consumption and it's working correctly now!

Looking forward to trying this, but our Mini is refusing to connect properly to the meter or Octopus at the mo. If it starts working I'll test the beta, but not holding out much hope as Octopus aren't responding to the support request 😒

Does the Octopus Mini beta include the latest 5.4.1 with fixes for the Tracker changes, I assume not yet?

Just pushed https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/releases/tag/octopus-home-mini-beta-2 which should include the 5.4.1 fixes

I use Node-Red rather than HA, would it be possible to have the API as been unable to find it.

Looking forward to trying this, but our Mini is refusing to connect properly to the meter or Octopus at the mo. If it starts working I'll test the beta, but not holding out much hope as Octopus aren't responding to the support request 😒

Update on this for anyone in the same boat, Octopus have reached out to say they have a known Bluetooth issue and hope to roll out a fix next week so hopefully I can test this then!
My solar/battery installer visited last week and saw the mini on the counter - he was very interested on behalf of customers he has for whom smart meters can't get a signal. Not sure if it is a robust enough solution (technically, security-wise and legally for actual metering though.

I spotted this a few days ago and informed them of the problem. The app doesn't ask for Bluetooth permission when using the Android version. set it up with an 'I' phone and it will work great.

This has now been included in the latest release (https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/releases/tag/v6.0.0). Please read the readme with instructions and caveats.


Add Santa Cruz

In this PR, we add a page for Santa Cruz, and we add a link to it in the "Towns" menu

Merging Zach's PR for Santa Cruz.


Kata main payload

Switch the CCv0 payload to the kata-deploy main version

Note: I've not replaced the enclave-cc payloads as they are created in a different way IIUC

Update operator and reqs-payload images to use latest tags

/test

hi @stevenhorsman , the changes you made look correct but we still need to fix at least one problem: not all runtimeClasses passed to the kata-deploy (samples/ccruntime/default/kustomization.yaml) are supported on main. At least kata-clh-tdx isn't as you can see on the error below when trying to install the operator:
~/operator/install/pre-install-payload
ccruntime.confidentialcontainers.org/ccruntime-sample created
ERROR: cc-operator-daemon-install pod is not running
DEBUG: Pod cc-operator-daemon-install-8gcdf
+ kubectl describe pods/cc-operator-daemon-install-8gcdf -n confidential-containers-system
Name:         cc-operator-daemon-install-8gcdf
Namespace:    confidential-containers-system
Priority:     0
Node:         myvm/<IP_ADDRESS>
Start Time:   Wed, 29 Nov 2023 20:06:16 +0000
Labels:       controller-revision-hash=54c88d84cf
              name=cc-operator-daemon-install
              pod-template-generation=1
Annotations:  <none>
Status:       Running
IP:           <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  DaemonSet/cc-operator-daemon-install
Containers:
  cc-runtime-install-pod:
    Container ID:  containerd://79da992890804f4adc73e35aaefa849cb4d615ac633636bb7d0fd35153a34f83
    Image:         quay.io/kata-containers/kata-deploy-ci:kata-containers-latest
    Image ID:      quay.io/kata-containers/kata-deploy-ci@sha256:538779d4e59d9a50b4fbee6252e8043ba30d909641cce751f70ba501bd7b613e
    Port:          <none>
    Host Port:     <none>
    Command:
      /opt/kata-artifacts/scripts/kata-deploy.sh
      install
    State:          Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Wed, 29 Nov 2023 20:16:00 +0000
      Finished:     Wed, 29 Nov 2023 20:16:01 +0000
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Wed, 29 Nov 2023 20:13:13 +0000
      Finished:     Wed, 29 Nov 2023 20:13:14 +0000
    Ready:          False
    Restart Count:  6
    Environment:
      NODE_NAME:                     (v1:spec.nodeName)
      DEBUG:                        false
      DEFAULT_SHIM:                 qemu
      CREATE_DEFAULT_RUNTIMECLASS:  true
      CREATE_RUNTIMECLASSES:        true
      SHIMS:                        clh clh-tdx qemu qemu-tdx qemu-sev qemu-snp
      SNAPSHOTTER:                  nydus
      INSTALL_OFFICIAL_CONTAINERD:  false
    Mounts:
      /etc/containerd/ from containerd-conf (rw)
      /etc/crio/ from crio-conf (rw)
      /opt/kata/ from kata-artifacts (rw)
      /usr/local/bin/ from local-bin (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-995wl (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  crio-conf:
    Type:          HostPath (bare host directory volume)
    Path:          /etc/crio/
    HostPathType:
  containerd-conf:
    Type:          HostPath (bare host directory volume)
    Path:          /etc/containerd/
    HostPathType:
  kata-artifacts:
    Type:          HostPath (bare host directory volume)
    Path:          /opt/kata/
    HostPathType:  DirectoryOrCreate
  local-bin:
    Type:          HostPath (bare host directory volume)
    Path:          /usr/local/bin/
    HostPathType:
  kube-api-access-995wl:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              node.kubernetes.io/worker=
Tolerations:                 node.kubernetes.io/disk-pressure:NoSchedule op=Exists
                             node.kubernetes.io/memory-pressure:NoSchedule op=Exists
                             node.kubernetes.io/not-ready:NoExecute op=Exists
                             node.kubernetes.io/pid-pressure:NoSchedule op=Exists
                             node.kubernetes.io/unreachable:NoExecute op=Exists
                             node.kubernetes.io/unschedulable:NoSchedule op=Exists
Events:
  Type     Reason     Age                    From               Message
  ----     ------     ----                   ----               -------
  Normal   Scheduled  9m56s                  default-scheduler  Successfully assigned confidential-containers-system/cc-operator-daemon-install-8gcdf to myvm
  Normal   Pulled     5m53s                  kubelet            Successfully pulled image "quay.io/kata-containers/kata-deploy-ci:kata-containers-latest" in 4m1.87092816s
  Normal   Pulled     5m49s                  kubelet            Successfully pulled image "quay.io/kata-containers/kata-deploy-ci:kata-containers-latest" in 986.334737ms
  Normal   Pulled     5m34s                  kubelet            Successfully pulled image "quay.io/kata-containers/kata-deploy-ci:kata-containers-latest" in 1.03330351s
  Normal   Pulled     5m6s                   kubelet            Successfully pulled image "quay.io/kata-containers/kata-deploy-ci:kata-containers-latest" in 1.082074027s
  Warning  BackOff    4m38s (x6 over 5m47s)  kubelet            Back-off restarting failed container
  Normal   Pulling    4m23s (x5 over 9m55s)  kubelet            Pulling image "quay.io/kata-containers/kata-deploy-ci:kata-containers-latest"
  Normal   Created    4m22s (x5 over 5m53s)  kubelet            Created container cc-runtime-install-pod
  Normal   Started    4m22s (x5 over 5m53s)  kubelet            Started container cc-runtime-install-pod
  Normal   Pulled     4m22s                  kubelet            Successfully pulled image "quay.io/kata-containers/kata-deploy-ci:kata-containers-latest" in 1.116094312s
+ kubectl logs pods/cc-operator-daemon-install-8gcdf -n confidential-containers-system
Environment variables passed to this script
* NODE_NAME: myvm
* DEBUG: false
* SHIMS: clh clh-tdx qemu qemu-tdx qemu-sev qemu-snp
* DEFAULT_SHIM: qemu
* CREATE_RUNTIMECLASSES: true
* CREATE_DEFAULT_RUNTIMECLASS: true
* ALLOWED_HYPERVISOR_ANNOTATIONS:
copying kata artifacts onto host
Creating the runtime classes
Creating the kata-clh runtime class
runtimeclass.node.k8s.io/kata-clh unchanged
Creating the kata-clh-tdx runtime class
error: the path "/opt/kata-artifacts/runtimeclasses/kata-clh-tdx.yaml" does not exist
+ set +x

Thanks, I'll have a think about it tomorrow

hi @stevenhorsman , the changes you made look correct but we still need to fix at least one problem: not all runtimeClasses passed to the kata-deploy (samples/ccruntime/default/kustomization.yaml) are supported on main. At least kata-clh-tdx isn't as you can see on the error below when trying to install the operator:

I'm not sure if it is formally documented anywhere, but @fidencio and I have discussed TDX with CLH before not being in main and the decision was that it's not coming over in the short-term, so I've added commits to drop references to it.

/test

/test

/test

"hey, let's switch to the main branch, it should be as easy as point to the other payload".... and here we are with 9 commits
@stevenhorsman is there any missing piece? Can I approve and merge when I get one more ack?

"hey, let's switch to the main branch, it should be as easy as point to the other payload".... and here we are with 9 commits

I'm just trying to break it down for ease of review (I've learnt from you and Fabiano !)

@stevenhorsman is there any missing piece? Can I approve and merge when I get one more ack?

Nothing missing that I know about

Hi @bpradipt ! do you have time to review this one? :D


Layout issue in main view

I can't see the things at the very top of the feed/profile I'm watching.
And everything seems to be shifted to the right.
In both images I'm scrolled to the top.
Running on MacOS Sierra 10.12.5
Main feed:

Profile:

Already fixed on master. please use the search functionality next time.

Cheers!
Might wan't to not close the issue until fixed in release for discoverability. Or have reasonable naming "rules" of PR's so that one can find the fix there.
Anyhow, sweet product! Nice that it is open source, maybe some contribution guidelines could help so you don't have to waste time on duplicate issues and the such!

Agree with @KHellkvist. It's still showing this for me (understandably), but I had to dig (a bit) to find this issue.


Ruby-command defaults to rbenv, but Bitrise is moving to/suggest asdf first

See https://github.com/bitrise-io/go-steputils/blob/v1.0.5/command/rubycommand/rubycommand.go#L69-L77
which prefers rbenv over asdf
However, https://discuss.bitrise.io/t/xcode-14-3-x-edge-stack-update-2023-06/22945 suggests using asdf over Rbenv
but if you do, the RubyCommand still finds rbenv and thinks it needs to use it. This causes steps, like cocoa pods-install (see https://github.com/bitrise-steplib/steps-cocoapods-install/blob/75dd45d47a09aecdec2f90738ebb78afc677a8dd/main.go#L368 ) to try and install Ruby again even if it's there from asdf

Hello @broksonic21,
Thanks for reporting, a fix is in progress (https://github.com/bitrise-io/go-steputils/pull/81).
Can you confirm that the problem you are seeing is an extra unnecessary installation time for Ruby? Can you share a build URL or part of the build log where this happens, so we can test the fix?

Yes, we installed a ruby version via asdf, but then the CocoaPods-install step tried to install it again (via rbenv) vs realizing the ruby version was installed and being used already.
I do suggest a slightly different check from your change - is there a reason you aren't checking for ruby version matching (for any reason) before going into the asdf/rbenv checking flow?
I am concerned on your change, as it will have the opposite intent if you do use rbenv -> as asdf will be checked first, it will try and install even if ruby is installed via rbenv first.
FYI: this wasn't just a timing issue - we saw build failures since rbenv failed to get the proper version due to a network issue.

closing older ticket of mine as the fix in #81 resolved it


Simple installation of Hephy wouldn't work. Client on Mac OS X and Cluster on AWS

I have been getting these error messages from a simple install of hephy. Would really appreciate if anyone could let me know how I came into receieving these errors (I was assuming these should be addressed by the installer itself?)
Error: validation failed: [secrets "minio-user" not found, secrets "deis-router-dhparam" not found, secrets "objectstorage-keyfile" not found, configmaps "dockerbuilder-config" not found, configmaps "slugbuilder-config" not found, configmaps "slugrunner-config" not found, serviceaccounts "deis-builder" not found, serviceaccounts "deis-controller" not found, serviceaccounts "deis-logger-fluentd" not found, serviceaccounts "deis-logger" not found, serviceaccounts "deis-monitor-telegraf" not found, serviceaccounts "deis-nsqd" not found, serviceaccounts "deis-registry" not found, serviceaccounts "deis-router" not found, serviceaccounts "deis-workflow-manager" not found, services "deis-builder" not found, services "deis-controller" not found, services "deis-logger" not found, services "deis-monitor-grafana" not found, services "deis-monitor-influxapi" not found, services "deis-monitor-influxui" not found, services "deis-nsqd" not found, services "deis-logger-redis" not found, services "deis-registry" not found, services "deis-router" not found, services "deis-workflow-manager" not found, daemonsets.extensions "deis-logger-fluentd" not found, daemonsets.extensions "deis-monitor-telegraf" not found, daemonsets.extensions "deis-registry-proxy" not found, deployments.extensions "deis-builder" not found, deployments.extensions "deis-controller" not found, deployments.extensions "deis-logger" not found, deployments.extensions "deis-monitor-grafana" not found, deployments.extensions "deis-monitor-influxdb" not found, deployments.extensions "deis-nsqd" not found, deployments.extensions "deis-logger-redis" not found, deployments.extensions "deis-registry" not found, deployments.extensions "deis-router" not found, deployments.extensions "deis-workflow-manager" not found]

What version of helm are you using to install hephy workflow? Any ideas @kingdonb ?

Kubernetes v 1.6.13
Helm 2.6.14
Kubectl 1.6.4
kops 1.16.0
AWS with image kope.io/k8s-1.6-debian-jessie-amd64-hvm-ebs-2018-08-17
Hephy 2.21.4
Would be great if you could teach me how to install (I'm kind of a newbie)
My guess is my tiller setup. But I'm not really sure what is the correct tiller configuration.

That's a pretty old k8s and helm version, which probably means if anything you should be in good shape for Workflow, and I've had enough issues with upgrades lately that I won't suggest a drastic all-at-once upgrade route...
The recommended version of Helm right now for Hephy v2.21.4 and lower is still 2, although I have had good luck with Helm 3. Kubernetes kubelet and kubectl must remain below v1.16.x (supported version is <= 1.15.x) for now, as we have not finalized our apps/v1 updates or extensions/v1beta1 API deprecations support required for newer versions of Kubernetes.
We have some issues with our documentation right now, sorry this is not posted anywhere more prominently. We should be able to support newer versions of Kubernetes soon. But if you start now, a test cluster with say https://github.com/weaveworks/wks-quickstart-firekube will come in with the right versions, v1.14.1 default, this is a great environment for testing without requiring a heavy investment in cloud resources, you can do a multi-node cluster as a trial all from docker containers on a Macbook pro, or KVM machines under a single node if your host OS is Linux.
Any Kubernetes with the right version requirements should work out of the box with the directions on web.teamhephy.com – legacy docs are available at docs.teamhephy.com which go into more detail about best practices and configuration for production. Glad to have you join us @jofell and I hope @felixbuenemann was able to help you this morning in our Slack community.
Is it too corny to celebrate I just happened to notice this:

...looks like you're our 100th customer? 🤣 🚀 We welcome kind of newbies and anyone else who works with Workflow, and if your experience is broken or positive we hope you will tell us more about it either way as time goes on, so we can support our community better.

Btw. I'm successfully running on Kubernetes 1.17 with the following Kube-Controller flags:
--runtime-config=extensions/v1beta1/daemonsets=true,extensions/v1beta1/deployments=true,extensions/v1beta1/replicasets=true,extensions/v1beta1/networkpolicies=true

This effectively re-enables the deprecated extensions on 1.16 and 1.17.
I have not verified if that still works on 1.18.

OK, don't celebrate yet, we have run down this issue and the finding is that Helm 2.16.x has an issue which prevents Workflow from being installed on even the older/correct versions of kubelet for Workflow v2.21.4,
[kube] 2020/03/28 14:43:34 get relation pod of object: deis/Service/deis-router
[kube] 2020/03/28 14:43:34 get relation pod of object: deis/DaemonSet/deis-registry-proxy
[kube] 2020/03/28 14:43:34 get relation pod of object: deis/DaemonSet/deis-logger-fluentd
[kube] 2020/03/28 14:43:34 get relation pod of object: deis/DaemonSet/deis-monitor-telegraf
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x14e314f]

goroutine 832 [running]:
k8s.io/helm/pkg/kube.getSelectorFromObject(0x1c01c40, 0xc00087a000, 0xc00087a000, 0x0)
	/go/src/k8s.io/helm/pkg/kube/client.go:924 +0x26f
k8s.io/helm/pkg/kube.(*Client).getSelectRelationPod(0xc00030a3a0, 0xc000238e00, 0xc000af8030, 0xc000b07770, 0x18, 0xc0000ea648)
	/go/src/k8s.io/helm/pkg/kube/client.go:1104 +0x195
k8s.io/helm/pkg/kube.(*Client).Get.func2(0xc000238e00, 0x0, 0x0)
	/go/src/k8s.io/helm/pkg/kube/client.go:366 +0xd1
k8s.io/helm/pkg/kube.batchPerform.func1(0xc00008f0e0, 0xc00079aea0, 0xc0003e0e10, 0xc000238e00)
	/go/src/k8s.io/helm/pkg/kube/client.go:752 +0x30
created by k8s.io/helm/pkg/kube.batchPerform
	/go/src/k8s.io/helm/pkg/kube/client.go:751 +0xb8

The latest version of Helm as of today is v2.16.5 and if your tiller is running that version, or perhaps any 2.16 version, it seems like you will get this error if you tail the tiller logs, or if you are just running helm client interactively it looks like this:
$ helm upgrade --install hephy hephy/workflow --namespace deis --set global.use_rbac=true
Release "hephy" has been upgraded.
Error: transport is closing

We backed down to a Helm version v2.15.2 and don't have this problem anymore, everything seems to come up ok, although the Helm 2.x series is probably not long for this world so that's not too helpful, I'm going to try to confirm that I am able to use Helm 3 to install Hephy, since I have not had issues with the latest Helm versions in the past. I have heard a lot of people saying that you need to keep around Helm 2 and Helm 3 both these days, I am not sure that's true.

It's definitely possible that all of these things are related by a single thread "issue with that specific combination of versions"
Thanks for letting us know about the workaround for enabling the deprecated versions, I can try this out on my 1.18 cluster next time.

All indications from my own testing point that Helm v3.1.2 (the latest version as of this writing) works fine with Hephy Workflow v2.21.4 (also the latest version as of today) on a Kubernetes cluster running v1.15.11. I could not say the same about Helm v2.16.4 and v2.16.5 which both seemed to bomb out in different ways when installing Workflow today.
Let's leave this issue report open until we can offer a better answer about what's going on with Helm v2.16.x, but I'm not too worried about it, as it doesn't seem to be an issue in the latest version of the modern-era Helm series releases, without tiller.
More urgent right now that we are able to support Kubelet control plane of v1.16.x and up, which is coming soon.

@jofell Since you figured it out, I think this issue can be closed. Maybe add a closing comment what the problem / solution was in case others run into the same problem.

Hi guys, great work and support. Really appreciate all the help.
Basically the kubernetes version sweet spot is using 1.15 and a working Helm version for it (2.14). But I'm happy you guys saw there's an issue here as well.
Hope to get help / help the project more in the future!

@kingdonb @felixbuenemann Thank you for helping with this issue ! @jofell let us know what else we can help with in the Slack channel. :+1:

@felixbuenemann Have you verified if this works with 1.18? From my experience it doesn't look like it does...

@dmcnaught No I haven't, I'm still on 1.17.

thanks @felixbuenemann


[refactor][query] Propagate RawTraces flag to  query service

Which problem is this PR solving?

Towards #6417

Description of the changes

This PR defines GetTraceParamaters and TraceQueryParameters inside package querysvc that are currently just wrappers around their package spanstore counterparts.
This is done so that additional parameters can be passed into the query service, like the RawTraces flag, without having to extend the parameters that are passed into the storage implementations.

How was this change tested?

CI

Checklist

[x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
[x] I have signed all commits
[x] I have added unit tests for the new functionality
[x] I have run lint and test steps successfully

for jaeger: make lint test
for jaeger-ui: npm run lint and npm run test

@yurishkuro I think there are two lines that are missing code coverage at the moment in the http_gateway.go. It should be taken care of in the next PR as I will add tests to all the handlers to ensure that the RawTraces flag is being respect but let me know if you prefer adding some boilerplate tests in this PR to get codecov up to 100%.


adds logic for stopping server and trigger only on command trigger

@arunkumars08 @jyasveer pls merge if it looks good. :)


container support

some games (such as PC games) have many files that are contained in a folder

Dduplicate of #21


Change color in the customization

This is the example code in guide.
  pprint.copy(
    additionalHandlers = {
      case value: Double =>  pprint.Tree.Literal(f"$value%1.5f") /* 5 digit precision */
    }
  )

Is it possible to change color in the customized handler?

This can already be customized via colorLiteral and colorApplyPrefix