App name on TestFlight build without the spaces

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
After some time searching about fastlane I was able to upload my build to Testflight correctly. All is fine except the app name (the name the user sees, display name on Xcode, not bundle name or bundle id). The app name was suppose to be "Boring Name" (example), after uploading the build and downloading it the name displayed is "BoringNa..." (yeah, it doesn't even shows the complete name). Uploading via Xcode works fine.
What can I do? Anyone having the same issue?
Thanks!
Complete output when running fastlane, including the stack trace and command used

[INSERT OUTPUT HERE]

Environment
✅ fastlane environment ✅
Stack

Key
Value

OS
10.13.3

Ruby
2.3.3

Bundler?
false

Git
git version 2.14.3 (Apple Git-98)

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.13.3 (17D102)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib

OpenSSL Version
LibreSSL 2.2.7

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
9.2

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "2.86.0"

default_platform :ios

platform :ios do

  # 1
  desc "Creating a code signing certificate and provisioning profile"
  # 2
lane :testflight do
    cert
    sigh
    update_info_plist(
    plist_path: 'project/Info.plist'
    )
    gym(
    scheme: "project",
    export_method: "app-store",
    export_xcargs: "-allowProvisioningUpdates"
    )
    upload_to_testflight
    pilot(skip_waiting_for_build_processing: true)
end

  error do |lane, exception|
  # This block is called if there was an error running a lane.
  end

end

fastlane gems

Gem
Version
Update-Status

fastlane
2.87.0
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-update_provisioning_profile_specifier
1.3.0
✅ Up-To-Date

Loaded gems

Gem
Version

did_you_mean
1.0.0

slack-notifier
2.3.2

atomos
0.1.2

CFPropertyList
2.3.6

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.4

xcodeproj
1.5.7

rouge
2.0.7

xcpretty
0.2.8

terminal-notifier
1.8.0

unicode-display_width
1.3.0

terminal-table
1.8.0

plist
3.4.0

public_suffix
2.0.5

addressable
2.5.2

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.6.4

tty-cursor
0.5.0

tty-spinner
0.8.0

babosa
1.0.2

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.61.0

faraday
0.14.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.1

gh_inspector
1.1.3

mini_magick
4.5.1

multi_json
1.13.1

multi_xml
0.6.0

rubyzip
1.2.1

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.2.1

bundler
1.16.1

faraday_middleware
0.12.2

naturally
2.1.0

simctl
1.6.2

uber
0.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.1

mime-types-data
3.2016.0521

mime-types
3.1

little-plugger
1.1.4

logging
2.2.2

jwt
2.1.0

memoist
0.16.0

os
0.9.6

signet
0.8.1

googleauth
0.6.2

httpclient
2.8.3

google-api-client
0.13.6

io-console
0.4.5

libxml-ruby
2.9.0

json
2.1.0

fastlane-plugin-update_provisioning_profile_specifier
1.3.0

generated on: 2018-03-23

[INSERT OUTPUT HERE]

@stein-fabricio I see that you are replacing the info plist with update_info_plist. What are the contents of your plist at project/Info.plist?

@joshdholtz actually I did this
update_info_plist(     plist_path: 'unquOProject/Info.plist',     display_name: 'Boring name'     )
trying to explicit the desired name, but it didn't work either.

@stein-fabricio This seams to be a "feature" of iOS. If the name you are trying to display is too long for the, it will be smart to try to remove spaces and then add a "..." if it doesn't fit (see my example images below) This doesn't appear to be a fastlane problem (as I was able to replicate this just using Xcode) and I think the only real solution would be to choose a shorter name 😊
Just right

Too long

Closing this since this is expected behavior by iOS. Happy fastlaning 🚀


Add duckDB example

Showcases how to query file-written records obtained from a local benchmark run, both with an inlined context and a flattened one.
Contains a SQL query example with escaped dotted columns, which are necessary as we currently cannot specify the separator to use when writing files to disk using our FileIO.

I have not yet removed the DuckDBReporter, since it technically does more than what happens in this example, which is creating benchmark records from duckdb SQL queries.
I guess we are not in a hurry to remove the functionality though, so it can stay there without harming anyone. But as a reference on how to crunch/analyze records, this is an improvement over the duckDB reporter.


textSize in xml

Is it possible to set textSize in xml? I needed to adjust the size of the text so it matches with other widgets in my view, ex. TextInputEditText.
android:textSize="20sp"

The same solution that works for normal a Spinner should work for MaterialSpinner. Use a custom layout for your spinner_item (see this Stack Overflow answer for details).
Let me know if that doesn't work.

oh thanks for the link. This works and is the correct way.
Make a custom XML file for your spinner item.
spinner_item.xml:
Give your customized color and size to text in this file.
<?xml version="1.0" encoding="utf-8"?>

<TextView
    xmlns:android="http://schemas.android.com/apk/res/android"
    android:layout_width="match_parent"
    android:layout_height="wrap_content"
    android:textSize="20sp"
    android:gravity="left"
    android:textColor="#FF0000"
    android:padding="5dip"
    />

Now use this file to show your spinner items like:
ArrayAdapter<String> adapter = new ArrayAdapter<String>(this, R.layout.spinner_item,list);
You don't need to set the drop down resource. It will take spinner_item.xml only to show your items in spinner.


Errors running with coverage[toml]

I've had coverage and coveralls working fine in a GitHub Action. I recently changed where I keep coverage's config, from setup.cfg to .pyproject.toml, and installed coverage[toml].
But now when coveralls runs I get the errors below. Is there a way for it to work with coverage[toml] instead of vanilla coverage?
Run coveralls debug --service=github
[2](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:2)
  coveralls debug --service=github
[3](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:3)
  shell: /usr/bin/bash -e {0}
[4](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:4)
  env:
[5](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:5)
    pythonLocation: /opt/hostedtoolcache/Python/3.10.5/x64
[6](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:6)
    LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.10.5/x64/lib
[7](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:7)
    GITHUB_TOKEN: ***
[8](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:9)
Missing .coveralls.yml file. Using only env variables.
[9](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:10)
Testing coveralls-python...
[10](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:11)
Traceback (most recent call last):
[11](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:12)
  File "/opt/pipx_bin/coveralls", line 8, in <module>
[12](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:13)
    sys.exit(main())
[13](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:14)
  File "/opt/pipx/venvs/coveralls/lib/python3.8/site-packages/coveralls/cli.py", line 75, in main
[14](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:15)
    coverallz.wear(dry_run=True)
[15](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:16)
  File "/opt/pipx/venvs/coveralls/lib/python3.8/site-packages/coveralls/api.py", line 254, in wear
[16](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:17)
    json_string = self.create_report()
[17](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:18)
  File "/opt/pipx/venvs/coveralls/lib/python3.8/site-packages/coveralls/api.py", line 332, in create_report
[18](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:19)
    data = self.create_data()
[19](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:20)
  File "/opt/pipx/venvs/coveralls/lib/python3.8/site-packages/coveralls/api.py", line 386, in create_data
[20](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:21)
    self._data = {'source_files': self.get_coverage()}
[21](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:22)
  File "/opt/pipx/venvs/coveralls/lib/python3.8/site-packages/coveralls/api.py", line 400, in get_coverage
[22](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:23)
    workman = coverage.coverage(config_file=config_file)
[23](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:24)
  File "/opt/pipx/venvs/coveralls/lib/python3.8/site-packages/coverage/control.py", line 246, in __init__
[24](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:25)
    self.config = read_coverage_config(
[25](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:26)
  File "/opt/pipx/venvs/coveralls/lib/python3.8/site-packages/coverage/config.py", line 561, in read_coverage_config
[26](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:27)
    config_read = config.from_file(fname, warn, our_file=our_file)
[27](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:28)
  File "/opt/pipx/venvs/coveralls/lib/python3.8/site-packages/coverage/config.py", line 277, in from_file
[28](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:29)
    files_read = cp.read(filename)
[29](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:30)
  File "/opt/pipx/venvs/coveralls/lib/python3.8/site-packages/coverage/tomlconfig.py", line 66, in read
[30](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:31)
    raise ConfigError(msg.format(filename))
[31](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:32)
coverage.exceptions.ConfigError: Can't read 'pyproject.toml' without TOML support. Install with [toml] extra
[32](https://github.com/philgyford/django-hines/runs/7433522069?check_suite_focus=true#step:8:33)
Error: Process completed with exit code 1.

Can't seem to reproduce this, using dependencies coverage[toml] and coveralls. I'm just about to release a new coveralls version which has a bunch of cleanups; please try it out, and if you still see this issue go ahead and re-open the ticket. Please be sure to include all the relevant versions when you do so!


Feature: add generic properties accessor for complex runtypes

Closes #217. This is still a very draft, but it would work. Test cases are not yet sufficient almost certainly.

Coverage decreased (-0.07%) to 98.995% when pulling ee33f6f2621acbfb454dfa19f36e0d1d00732305 on yuhr:feat/properties into 6b62147695b0152babe7e71f221a19aa620ea77a on pelotom:master.


Rox-11939: Expose scanner monitoring

Description
A detailed explanation of the changes in your PR.
Feel free to remove this section if it is overkill for your PR, and the title of your PR is sufficiently descriptive.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why
you did not do so. Valid reasons include, for example, "CI is sufficient",
"No testable changes". Feel free to attach JSON snippets, curl commands,
screenshots.
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.

/test all

/retest

/retest

/retest

/test all

/retest

/retest

/retest

/retest

I'm curious how are we handling the fact there are 2 - 5 Scanners in a production deployment? I think this just looks at the metrics for the Scanner which is chosen by the Service, right?

Good point. I think it depends on how the Prometheus scrape is configured (see the different role types in https://prometheus.io/docs/prometheus/latest/configuration/configuration/#kubernetes_sd_config). Basically Prometheus either allows service discovery - then the scrape is routed to only one pod - or pod discovery, in which case all pods should be scraped. For the pod discovery role config the service definition should be unnecessary, but again I'm not sure it makes sense to allow individual configuration.

I'm curious how are we handling the fact there are 2 - 5 Scanners in a production deployment? I think this just looks at the metrics for the Scanner which is chosen by the Service, right?

Good point. I think it depends on how the Prometheus scrape is configured (see the different role types in https://prometheus.io/docs/prometheus/latest/configuration/configuration/#kubernetes_sd_config). Basically Prometheus either allows service discovery - then the scrape is routed to only one pod - or pod discovery, in which case all pods should be scraped. For the pod discovery role config the service definition should be unnecessary, but again I'm not sure it makes sense to allow individual configuration.

I think pod might work, but what is an even better choice here is endpoints. You can run kubectl -n stackrox get endpoints scanner -o yaml to see what the endpoints resource backing the scanner service looks like - it basically contains all possible (ip, port) combinations resulting from resolving the pod selector of the service to concrete pod IPs. IMHO, this is the best of all worlds, as:

You can select ports for scraping even if they don't show up in the containerPorts section of the pod spec, which might not always be complete. Rather than patching a missing containerPort into the deployment resource, a Service can be created as a new resource, not modifying any of the existing ones.
You do not miss any replicas, as can happen with the service sd role.
You still get the logical grouping imposed by the Service object (you can stitch that together with pods via labels, but with the endpoints sd role, you also get all the labels from the service sd role ("If the endpoints belong to a service, all labels of the role: service discovery are attached.")


[Answer from the stakeholders needed] How the revert to the default favicon and title button should be named?

As US #426 paragraph 9 says we should have a button for the admin user to revert to the default favicon and title if desired.
In the last meeting we had a dispute how the revert button should be named "Cancel", "Reset" or "Revert" and came to the conclusion that we should ask the client.

as it was discussed on our sync 19.07 we can close this clarification as N.A.


Proposal: expose downstream protocol and stream id as opt-in response headers

Title: Expose downstream protocol and stream id as opt-in response headers
Description:
We'd like this feature primarily to use as additional context in analytics data. While clients technically have this information already, few publicly-shipped HTTP stacks expose it, and none are consistent.
I have an implementation that exposes this from the http codecs and injects the headers in the http connection manager. @mattklein123  suggested header injection could also be done within the codec itself.
Open questions:
Most important: how do folks feel about this?
Where should the code live?
For http/1.* should we return a notional stream id (e.g. set it as 1 initially and increment if the connection is re-used)?
I feel confident about tackling the implementation, but wanted to get feedback before going further.

As long as this is opt-in on a config basis I don't have an objection to this. I guess loosely my preference would be to expose this from the codec at the interface layer, and for HTTP/1 just use an incrementing "stream" ID which would still give you info about where on the connection the request was started. So I think how you have likely coded it makes sense to me w/ the config at the HCM layer.
@alyssawilk what is your thinking here?

Incidentally, I have the headers tentatively named:
x-envoy-downstream-protocol
x-envoy-downstream-stream-id
Open to other options on that front as well, though.

We pass both around internally so this totally passes the 2+ users general purpose usefulness test :-)    +1 to  incremental stream id for HTTP/1 - for network latency analysis it's important to know the request was on a pre-warmed connection.
My question is how many of these reasonable headers we're going to have.  Internally we've got client protocol, number of requests on a connection, initial server vip, client certs, sever cert selected, initial connection security, ciphers, negotiation mechanism, rtt, srtt, bandwith, etc, etc, etc. for something like 30 fields total, most of which I think will be generally purpose useful and we'll add many of them upstream   Doing each of these as
x-envoy-client-rtt: #,
x-envoy-client-srtt: #
x-envoy-client-cert-hash: [hash]
etc
ends up adding enough bytes to add up to multiple rtts on non-warm connections.  To avoid this, we have a general purpose header the "frontline info header" where individual routes can opt in or out of specific fields via a mechanism similar to user defined headers.  So you end up with one
x-envoy-frontline-info-header: srtt=#;rtt=#;request=#;cert=hash;
and then there's utilities to pull the token you want from the one general purpose header.  It is a bit more work for upstream consumers to have to parse the tokens, but it's been well worth it to us.  I think we should consider if we want such a thing for Envoy - Google will definitely do so internally even if we have to one-off munge a bunch of upstream headers on the way out so we don't need upstream, it, but if other @envoyproxy/maintainers think it's worth the complexity vs bandwidth trade-off I'd be happy to have it upstream and start it here.

Thanks for the feedback, @mattklein123 and @alyssawilk !
@alyssawilk, you raise a good point about the other possible fields - in truth I had already been considering measuring rtts from envoy to the client at some point. A couple thoughts:
First, it seems like we could support both a "packed" format as well as an individual-header format fairly easily. All the plumbing to get at the information would be the same and configuration options could dictate which (if any) we inject. This appeals to me because it lets me defer on biting the complexity bullet of the packed format for now, but it seems totally reasonable that we support that in the not too distant future.
Second, I know we used protobufs for a "packed" tracing header format at one point. For a packed frontline-info header proto jumps out at me as appealing both because it possibly simplifies the work for clients to extract information from the header, and also because it gives us an external schema. The trade-off is of course that it does require a consumer of the header to speak proto and isn't human readable like the format you suggest above.
I don't have terribly strong feelings about this. All of the above seem workable.

I think based on previous discussion with @PiotrSikora, we're been persuaded against using proto/JSON for new headers that we're defining if we want these to be somewhat standard. I'm a proto partisan, but I buy the argument that if we want any headers we define to have wider adoption, we can't be dictating proto.

Yeah I think I would shy away from proto/JSON here and do a basic format. I agree on designing a packed header with all of this information.
Additionally, I would prefer that we configure the output of this header using the "extra debug" information configuration that @junr03 has been designing and is going to start working on. @goaway can you sync with @junr03 next week when he is back and add this to that document? I think that document also needs to go out for wider community review. Thank you!

Catching up on this now that I am back.

I'll follow up with @goaway to add this to the doc.
@alyssawilk is @vilobhmm the primary owner of the Reverse Proxy Response Propagation to downstreams doc you sent me? In my doc we mentioned that the work can be separate, but I want to make sure we are not duplicating effort, so I want to sync before we start working on this.
@mattklein123, other than resolving point 2 above (and adding that to my doc), I am happy to share with the wider community. Once I get a chance to sync with folks at google I will open up an issue to share the doc. Thoughts?

Yes please share the other doc whenever we can. Also, feel free to close/consolidate issues that are related to this topic and potentially duplicates.

summarizing discussions at the community meeting, we're lean towards using http parameterized lists
https://tools.ietf.org/html/draft-ietf-httpbis-header-structure-06#section-3.3
as fairly readable, semi-colon delimited and standards compliant.

re: fitting this into the richer response information design I have been working on.
@goaway and I met, and we agree that this feature fits in nicely into the proposed framework. However, given that I have not shared the document for community comment (and internally at Lyft it is unclear to me when we are going to schedule this work), it seems too vague to me to block adding this feature on that work.
So what we propose is the following: add this feature as an http conn man config option, and then once the richer response information framework is in place we can fold this feature into it (with a deprecation cycle of course).

Cool.  @junr03 what do you think of making the config for these 2 new options into their own sub-proto in the hcm?  I think both it'd be nice to keep the frontline-info-header options together, and it might make it easier to migrate when we have the rich info framework.

@alyssawilk yeah, which would make sense, but maybe we're biased towards the edge proxy case. The issue description mentions response headers, and there is already X-Forwarded-Proto in Envoy, which x-envoy-downstream-protocol in request headers would duplicate, so I want to make sure that we're all talking about the same thing, and not just assume that we do.

@PiotrSikora It's my understanding that X-Forwarded-Proto generally is only used to distinguish between TLS and plaintext connections (i.e. either http or https), whereas x-envoy-downstream-protocol is meant to provide the the HTTP-compatible protocol used for the downstream connection (i.e. http/1, http/2, quic, etc.). I am also specifically proposing a response header, though this doesn't preclude support as a forward-propagated request header.

Cool. @junr03 what do you think of making the config for these 2 new options into their own sub-proto in the hcm? I think both it'd be nice to keep the frontline-info-header options together, and it might make it easier to migrate when we have the rich info framework.

+1

I am also specifically proposing a response header, though this doesn't preclude support as a forward-propagated request header.

We are going to use a single header with delimiters, right?

@junr03 @htuch @alyssawilk should we coalesce this with #4283 ?

Sorry for the delay/inactivity - I still am working on this as a low priority change, but since we reached a general consensus here, I don't mind closing the issue or coalescing.


Use verbose_print for updating sudo cached credentials notice

https://github.com/ralish/bash-script-template/blob/ff628fcbe2e5fa6ddd4a96fdb013879a9ea75fe8/source.sh#L352

The rationale at the time was that it might not be obvious what credential you're being prompted for, but at least on the systems I just tested, the sudo password prompt is always prefixed with [sudo] so yes, that does make it a bit redundant.

Fixed in https://github.com/ralish/bash-script-template/commit/9ba36a646fe13779ddd2c009a1bdaae505e29649.


sidecar config with workload selector is not applied to root namespace

Bug Description
I am trying to setup the mTLS termination at sidecar using the sidecar API use case according to the newly introduced feature in istio 1.13 based on https://github.com/istio/istio/pull/36210  and came around the following limitation:
When installing the example mentioned here in istio-system namespace(instead of prod-us1 namespace as in the example), which is the default rootNamespace in my deployment, the workload selector in the sidecar configuration doesn’t become effective. This seems to be due to the specific behaviour of the sidecar API in rootNamespace, see Note 2 on https://istio.io/latest/docs/reference/config/networking/sidecar/
Note2
This means in the end, the entire use case becomes ‘invalid’ for the rootNamespace.
Is this limitation of sidecar API intentional? This makes the TLS termination at sidecar solution unusable for us.
The below code seems to be the relevant area which checks if rootNamespace sidecar config has a workloadSelector or not:
https://github.com/istio/istio/blob/master/pilot/pkg/model/push_context.go#L1637
Version
istioctl version : 1.14.1
kubectl version: 1.23.1

Additional Information
No response

cc @shriramsharma

PeerAuthentication policies have the same issue, when configuring a selector on the root namespace they stop working across all namespaces.

when configuring a selector on the root namespace they stop working across all namespaces.

WorkloadSelector is not supposed to apply to all namespaces. IIUC @kfaseela is saying its not working at all?

when configuring a selector on the root namespace they stop working across all namespaces.

WorkloadSelector is not supposed to apply to all namespaces. IIUC @kfaseela is saying its not working at all?

yes @howardjohn, looks like sidecar api with workloadSelector does not get effective in istio-system namespace at all. Something related seems to be present in the code comment here: https://github.com/istio/istio/blob/master/pilot/pkg/model/push_context.go#L1637
Any reason why such a restriction is present? Is this something that can be changed?

hey @howardjohn , the issue is not with the workloadSelector field.
I think what @kfaseela is trying to say is that currently the way it is coded here,  a sidecar config can only be applied to the root namespace if it does not contain the workloadSelector field.
Due to this restriction, they cannot use the TLS/mTLS termination feature on the sidecar proxy.
Can you please provide some historical context as to why this restriction was added?


add kubeconfig reference in ForeignCluster status for outgoing and incoming

Description
This PR adds a reference to Identity Secrets coming with Advertisements and PeeringRequests respectively in ForeignCluster > Status > Outgoing > IdentityRef and  ForeignCluster > Status > Incoming > IdentityRef
This will allow components that want to access these identities to not to have permissions on Advertisements and PeeringRequests

/rebase


Logs/Metrics within the Admin Portal to View Traffic to Proxy Hosts

Describe the solution you'd like
I would love to see an enhancement of the admin portal that is perhaps a "Monitor" section of the site. In that section, we could see number of requests that have gone to each host.
If you select a Host within this view, you could then get some high level details about each request (maybe have a way to configure verbosity / retention period).
Having this additional visibility into traffic to hosts could provide an immense amount of value.
Describe alternatives you've considered
Currently, I believe the other ways to get this data would be spinning up some sort of log aggregation service and building out rules and dashboards this way instead. It definitely can be done, but I think it would make this project even more useful if it was baked in.

I'd honestly settle for latency data being visible in the logs saved to disk by NPM, so that I can have a script scrape them once every minute (or even follow them) and dump them into Influx to further explore.

👍

👍

👍


Adding power support to travis job

Adding power support to travis job.
Signed-off-by<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build 1392

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

Totals

Change from base Build 1391:
0.0%

Covered Lines:
12587

Relevant Lines:
17851

💛  - Coveralls

Closing as missed adding signed-off by.


Error while populating event database

When running the command to populate the event database, I'm getting the following error:
npm run populate
><EMAIL_ADDRESS>populate
> babel-node scripts/populate.js

[1/2] - Fetching all schemas for event bus: inspection-flow...
(node:16385) UnhandledPromiseRejectionWarning: Error:
    at new ServiceException (/Users/xxxx/Development/event-bridge/eventbridge-canon/node_modules/@aws-sdk/smithy-client/dist-cjs/exceptions.js:6:9)
    at new SchemasServiceException (/Users/xxxx/Development/event-bridge/eventbridge-canon/node_modules/@aws-sdk/client-schemas/dist-cjs/models/SchemasServiceException.js:7:9)
    at deserializeAws_restJson1ListSchemasCommandError (/Users/xxxx/Development/event-bridge/eventbridge-canon/node_modules/@aws-sdk/client-schemas/dist-cjs/protocols/Aws_restJson1.js:2147:24)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at /Users/xxxx/Development/event-bridge/eventbridge-canon/node_modules/@aws-sdk/middleware-serde/dist-cjs/deserializerMiddleware.js:7:24
    at /Users/xxxx/Development/event-bridge/eventbridge-canon/node_modules/@aws-sdk/middleware-signing/dist-cjs/middleware.js:11:20
    at StandardRetryStrategy.retry (/Users/xxxx/Development/event-bridge/eventbridge-canon/node_modules/@aws-sdk/middleware-retry/dist-cjs/StandardRetryStrategy.js:51:46)
    at /Users/xxxx/Development/event-bridge/eventbridge-canon/node_modules/@aws-sdk/middleware-logger/dist-cjs/loggerMiddleware.js:6:22
(Use `node --trace-warnings ...` to show where the warning was created)
(node:16385) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 18)
(node:16385) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I've tried to use the schema registries that I have in my account, which both are default in their naming: aws.events and discovered-schemas.
I've tried using the credentials in ~/.aws/credentials with the default profile set for it. Then I also tried to put the credential variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and AWS_SESSION_TOKEN) in the .env file specifically. The error is the same in all cases.

@guyernest I encountered this exact stack trace and problem using SCHEMA_REGISTRY_NAME=discovered-schemas on a newly created eventbus.
My problem?
I had forgotten to enable schema discovery for my new eventbus! Once enabled I ensured I fired events at the same eventbus to the point that at least one event schema was discovered.
HTH,
Lorcan

It's also probably worth mentioning that I opted not to specify any credentials in the .env file in favour of using an AWS profile (I just happen to be using aws-vault but I'm sure a basic profile would also work).
$ aws-vault exec my-profile-name -- npm run populate

My .env file:
EVENT_BUS_NAME=my-eventbus-name
SCHEMA_REGISTRY_NAME=discovered-schemas
REGION="us-east-1"

AWS_ACCESS_KEY_ID=
AWS_SECRET_ACCESS_KEY=
AWS_SESSION_TOKEN=

Thanks @lorcanoeire for your help. The issue was eventually related to the credentials method. I tried to use the SSO login option, which is working well for most cases of AWS CLI, and it didn't work in this case. Once I've updated the temporary credentials in the ~/.aws/credentials file it worked. Thanks again for this great tool and support.

Hey @guyernest @lorcanoeire
Sorry for the late response, this issue managed to go through the net!
Sounds like you managed to fix the issue 🙏, yeah I need to update the docs and method to focus on moving away from ENV variables, so I will make a note of that!
If you have any ideas, or feedback for canon feel free to share!
Hope you enjoy the tool
Cheers,
Dave!


Convert and re-enable TimingModuleTest

Summary:
As part of the effort to Kotlin-fy React Native tests, I've converted TimingModuleTest to Kotlin.
I noticed the test suite was ignored and it was failing locally but managed to get all the tests to pass except one which I kept ignored.
Changelog:
[Internal] [Changed] - Convert TimingModuleTest to Kotlin
Test Plan:
Tests pass: ./gradlew :packages:react-native:ReactAndroid:test
Formatted with KtFmt

@cortinico FYI I've fixed the ignored test. Turns out its a simple case of ordering calls as the implementation expect.
When we call onHostResume.. it goes into this flow
  private void maybeSetChoreographerIdleCallback() {
    synchronized (mIdleCallbackGuard) {
      if (mSendIdleEvents) {
        setChoreographerIdleCallback();
      }
    }
  }

So if we don't set idle events before it then no callback will be set which means nothing is triggered for idle callbacks which results in the test failing.

@amrfarid140 That's awesome, thank you so much!


feat: Add test/build GH Actions workflow

This merge request is erroring out, but it's erroring out in a way that it should be – the Object.is comparison is comparing +0 against -0. Will be making a separate commit to resolve this.


added support for KL400 smart light strip

Hey, thanks for the contribution!
As I don't have this product, can I safely assume you have tested to make sure it works?
If so I think we can bring this in and release a new NuGet package too.

Yes I do, and this has worked great! In theory you can address each LED in
the light strip individually, and control the color of each separately, so
eventually I would like to enhance this to add that functionality. But for
the time being, this has worked great to address my immediate use case.
On Fri, Oct 21, 2022 at 10:45 AM Anthony Turner @.***>
wrote:

Hey, thanks for the contribution!
As I don't have this product, can I safely assume you have tested to make
sure it works?
If so I think we can bring this in and release a new NuGet package too.
—
Reply to this email directly, view it on GitHub
https://github.com/anthturner/TPLinkSmartDevices/pull/14#issuecomment-1287320413,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABN46FGNSTMFO3TZ43VYFDWELQDVANCNFSM6AAAAAARKVQ6RQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Note for future: I plan to release a new NuGet version shortly, but I want to put a tiny bit of time in to refactoring a couple pieces of this code that I cringe at when I browse this repo.
(Should be within the next week, though)

I don't have any docs on how to individually address LEDs, I just know that in the app, they have some presets with varying colors across the light strip, so I'm assuming it must be possible.


Fix missing error type in stream type's string representation

Purpose

$title

Fixes #21817
Approach

Include error type in toString() method

Error message - Before bug fix
incompatible types: expected 'stream<Student>', found 'stream<record {| anydata...; |}>'

Error message - After bug fix
incompatible types: expected 'stream<Student,(ballerina/sql:DatabaseError|ballerina/sql:ApplicationError)>', found 'stream<record {| anydata...; |},(ballerina/sql:DatabaseError|ballerina/sql:ApplicationError)>'

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

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

@@           Coverage Diff           @@
##           master   #22799   +/-   ##
=======================================
  Coverage   14.59%   14.59%
=======================================
  Files          51       51
  Lines        1411     1411
  Branches      219      219
=======================================
  Hits          206      206
  Misses       1189     1189
  Partials       16       16

Continue to review full report at Codecov.

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

@pcnfernando can we merge this please?
@lasinicl can you please send this fix to 1.2.x branch as well (include a test case if possible)?


'cut -c3- ~/.tmux.conf | sh -s _apply_configuration' returned 2

I have:
'cut -c3- ~/.tmux.conf | sh -s _apply_configuration' returned 2

Here is the log file associated to this command:
tmux.log

I don't what happened but the problem is magically solved - maybe related to a simple reboot

I'm still getting this issue.
'cut -c3- ~/.tmux.conf | sh -s _apply_configuration' returned 1
I'm running on a linux server via ssh

You obtained a 1, and me a 2. We don't have the same error. You can produce a tmux.log with:
cut -c3- ~/.tmux.conf | sh -sx _apply_configuration > tmux.log 2>&1

Had the same issue, I think it's related to what your default shell is - if you've changed it with chsh sometimes a reboot is needed for that to take effect, so your resolving comment makes sense if that was the case. Changing the line to the following worked for me (note sh changed to zsh):
cut -c3- ~/.tmux.conf | zsh -s _apply_configuration

Had the same issue, I think it's related to what your default shell is - if you've changed it with chsh sometimes a reboot is needed for that to take effect, so your resolving comment makes sense if that was the case. Changing the line to the following worked for me (note sh changed to zsh):
cut -c3- ~/.tmux.conf | zsh -s _apply_configuration


Check compatibility with new timestamp option in multimon

https://github.com/EliasOenal/multimon-ng/pull/68

the timestamp is injected before the protocol word, so stripping the ^ from regex is all that's needed - not able to test properly at this point, but resolving with that unless we get further reports. PR to follow


custom default filters for each tab

Example: I go to movies tab, set filter to watched and sort by release date. I see movies sorted and filtered as expected.
Question: is it possible to set default filter and sort for the tab?

It's not possible at the moment


Investigate “Delete User Data” functionality

Clicking the “Delete User Data” button may not work. This one:

Investigate, ensuring that the user is logged out after the button is clicked. A user should be able to log in and resume COINSTAC work.

More info: this doesn't work on windows do to how the OS handles files..... not sure on solution


[BEAM-10670][BEAM-11028][BEAM-10997] Cherrypick #13041 to 2.25.0: "[BEAM-10670][BEAM-11028][BEAM-10997] Ensure that UnboundedSourceAsSDFWrapperFn returns stop() when the UnboundedSource gets to BoundedWindow.TIMESTAMP_MAX_VALUE. Also close readers when they are done."

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @robinyqiu

CC: @iemejia


Add test cases for weather

This is for forecast

@houshengbo , I saw in blue whisk repo there already a Scala version.

Involved with username and password.


Motion_Detection_Active lets itself turn off but not on again

I agree to the following

[X] I have read the documentation right now
[X] I have read the FAQs right now
[X] I am aware of the latest release notes
[X] I am aware that an integration that was installed via HACS also needs to be updated via HACS
[X] The Backend (CCU/Homegear/...) is working as expected, devices are taught in and are controllable by its own UI.
[X] I am running the latest version of the custom_component (and Home Assistant)

The problem
I have an automation that controles my motionsensor and switches it of after specific conditions were met. I'm using the Motion_Detection_Active button for this but for some reason it turns it off but never on again.
I also noticed it throws me a warning in the logs when it doesn't turn it on again (included in the form).
I'm more than happy to admit I'm to stupid for the sensor, I just have no clue what to do further I've already reset the sensor once and it did the exact same thing...
I'm also running the sensor on batteries.
Thanks for the help in advance.
What version of HomematicIP (local) has the issue?
1.61.0
What was the last working version of HomematicIP (local)?
No response
What type of installation are you running?
Home Assistant OS
What type of installation are you running for your homematic backend?
RaspberryMatic HA-Addon
Which version of your homematic backend are you running?
<IP_ADDRESS>40420
What hardware are you running for your system?
Pi4
Which config details do you use

[ ] TLS
[ ] callback data (see)

Which interfaces do you use?

[X] Homematic IP
[ ] Homematic (Bidcos-RF)
[ ] Groups (Heating-Group)
[ ] BidCos-Wired (HM-Wired)

Diagnostics information (no logs here)
No response
Log file extract. Anything in the logs that might be useful for us? The log (Setting/System/Logs -> load full log) is the best source to support trouble shooting!
2024-05-24 20:06:42.481 WARNING (MainThread) [hahomematic.client] SET_VALUE failed with ClientException [XMLRPC Fault from backend: -1 Generic error]: XXXXXXXXXXXXXXXX:3, MOTION_DETECTION_ACTIVE, True

Additional information
No response

Thank you I will try some other thinks or maybe even resetting it again :)


Cable flicker bug

When the cable latches on to a planet, there is a flicker as it is reparented. This is probably because of the call_deferred being used because reparenting cannot be done in the _physics_process().

There is also a bug where harpoon reparenting in a zoom out zone triggers the zoom out again, even when the camera is already zoomed out. This is because when the player is removed from the scene tree, it leaves the zone, then reenters it when readded to the scene tree.

Fixed in https://github.com/dchiquito/small-regent/commit/61e414b3da9b494c63c74f636bcb5296fa44dd8f


Bump version to 7.0.0-rc1

Could wait that I test it via https://github.com/oasisprotocol/emerald-web3-gateway/issues/184 before doing a release


feat: upgrade to Angular 9

Updates tables to Angular 9.
We have to replace ng2-completer with @akveo/ng2-completer because original completer is published with two major issues (first issue, second issue).
@akveo/ng2-completer package is a<EMAIL_ADDRESS>package built with fixes from https://github.com/oferh/ng2-completer/pull/448.
BREAKING CHANGE:

ng2-completer dependency replaced by @akveo/ng2-completer. Read details in #1140.
We no longer have a direct dependency on tslib. Instead it is now
listed a peerDependency. This matches Angular framework.

ng2-completer dependency replaced by @akveo/ng2-completer. Read details in #1140.

let's add that this is a temporary measure and we have on current plans on supporting the completer library.


Error - JSON file 'data/in-network-rates-fee-for-service-sample.json' not found

I am unable to get the validator working. When I run the
cms-mrf-validator validate test-files/in-network-rates-fee-for-service-sample.json v1.0.0
command i get a JSON file 'data/in-network-rates-fee-for-service-sample.json' not found error. The file is present in the test_files folder. Not sure why the validator adds "data/" to the path.
At work, we have Docker CLI, but not Docker Desktop. Also, we are running the validator on a Linux (RHEL) machine.
At home, I was able to run the validator using Docker Desktop on a windows machine, without any issues.
Any ideas on how to resolve this issue?
thanks

Thank you for reporting this issue. The reason for the "data/" at the beginning of the path is because the path reported in this error message is produced inside the Docker container that is running the validator. As a result, the error message you receive is not as helpful as it could be. To make this easier to troubleshoot, the validator will be updated to check the path to the data file before sending the path to the Docker container.

Thank you for the quick response. After the update,  if the path to data file is a valid one (which it is), then I should expect to see a different error message from the validator?


Iterator return type not constraining typed arrays literals

Bug Report
🕗 Version & Regression Information
It has always been there. (tested with every Typescript version available in the playground since the support or typing for iterator return types)
⏯ Playground Link
👉 Reproduction link in playground
💻 Code
export type It = Iterator<[string, number], [string, number]>;

function *it(): It {
    yield ['', 0]; // this works ✔
    return ['', 0]; // this fails ❌
}

🙁 Actual behavior
The return statement does not constraint the array literal to the right type. Instead, it takes its... I dont know how to put it... its "natural" type ?
🙂 Expected behavior
Both yield & return statements should compile.
👉  Workaround:  Force the array to be correctly typed via return ['', 0] as const.

This looks to have been fixed in TypeScript 4.8 as a result of #49736.


native with angular its not working ...

In native with angular its not working ...
I tried the same coding but its not working

Can you provide a code sample? What error do you get?


Commands fail without internet connection because of version checking

From a validator trying to create a wallet on a box without internet:
It throws an error. “Could not check Vega wallet version updates:”
Because machine is offline
Specifically after issuing
vega wallet key generate —wallet “example”

We do have indeed the --no-version-check flag to avoid checking for a version. But should failing to check for the version stops you to execute the command you tried to? I'm not so sure, up to debate.

Tested OK on latest wallet
Muthus-MBP:vega muthupandianvadivelu$ vegawallet key generate --wallet TestConnWal4
✗ You are running an unreleased version of the Vega wallet (v0.11.0+dev). Use it at your own risk!

✗ couldn't check latest releases: couldn't get releases: couldn't deliver request: Get "https://api.github.com/repos/vegaprotocol/vegawallet/releases": dial tcp: lookup api.github.com on [::1]:53: read udp [::1]:61983->[::1]:53: read: connection refused

Enter passphrase:
Confirm passphrase:

✓ Wallet TestConnWal4 has been created at: /Users/muthupandianvadivelu/Library/Application Support/vega/wallets/TestConnWal4
✓ Key pair has been generated for wallet TestConnWal4 at: /Users/muthupandianvadivelu/Library/Application Support/vega/wallets/TestConnWal4
✓ Generating a key pair succeeded

With flag --no-version-check
Muthus-MBP:vega muthupandianvadivelu$ vegawallet --no-version-check key generate --wallet TestConnWal5
Enter passphrase:
Confirm passphrase:

✓ Wallet TestConnWal5 has been created at: /Users/muthupandianvadivelu/Library/Application Support/vega/wallets/TestConnWal5
✓ Key pair has been generated for wallet TestConnWal5 at: /Users/muthupandianvadivelu/Library/Application Support/vega/wallets/TestConnWal5
✓ Generating a key pair succeeded


Subtitles resolution tied to video resolution

On Linux, when playing low-res videos, subtitles are low-res too. When VLC window is opened, it's output seems to be automatic (as opposite to VLC Qt interface, where you can set output to "X11").
There is no option in the python-vlc API guide for setting  output, so it may be solved by creating an X window object first, then create a VLC instance in this window.

Fixed by passing command-line option for output module to VLC Instance constructor


chore(deps): update dependency actions/cache to v4.1.2

This PR contains the following updates:

Package
Update
Change

actions/cache
patch
v4.1.1 -> v4.1.2

Release Notes

actions/cache (actions/cache)
v4.1.2
Compare Source
What's Changed

Add Bun example by @idleberg in https://github.com/actions/cache/pull/1456
Revise isGhes logic by @jww3 in https://github.com/actions/cache/pull/1474
Bump braces from 3.0.2 to 3.0.3 by @dependabot in https://github.com/actions/cache/pull/1475
Add dependabot.yml to enable automatic dependency upgrades by @Link- in https://github.com/actions/cache/pull/1476
Bump actions/checkout from 3 to 4 by @dependabot in https://github.com/actions/cache/pull/1478
Bump actions/stale from 3 to 9 by @dependabot in https://github.com/actions/cache/pull/1479
Bump github/codeql-action from 2 to 3 by @dependabot in https://github.com/actions/cache/pull/1483
Bump actions/setup-node from 3 to 4 by @dependabot in https://github.com/actions/cache/pull/1481
Prepare 4.1.2 release by @Link- in https://github.com/actions/cache/pull/1477

New Contributors

@idleberg made their first contribution in https://github.com/actions/cache/pull/1456
@jww3 made their first contribution in https://github.com/actions/cache/pull/1474
@Link- made their first contribution in https://github.com/actions/cache/pull/1476

Full Changelog: https://github.com/actions/cache/compare/v4...v4.1.2

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


Debug tracking annotator

There are some issues with the lineage logic on dev now.

Fixed by #475


Restrict Boards to users/roles

Description
I would love the option to restrict boards to specific users and/or specific roles i.e. users with a "Normal" role would only be able to view boards that an admin has granted them permission to view. Admins/Owners should be able to see all boards, as it is now.
Priority
Low (Nice-to-have)

Duplicate of #1801 and #1668. Please search for duplicates before opening issues. Thank you


Bot State seems to be messed up. Dialog not working as expected

I am using SDK V3 version 3.15.3.  In my bot I am simulating a conversation flow using Dialogs. But instead of hitting the call back function mentioned in context.wait(), after hitting Message.Controller the control is going to StartAsync function in my root dialog and as a result the whole dialog flow is restarting from the beginning rather than proceeding to the function mentioned in the callback for context.wait(). This behavior is also quite random as in few cases ( specially when debugging locally) the bot is acting as expected.

Hi @sagnikm95
I'm sorry you've run into this issue.  We will address your duplicate question here: https://github.com/Microsoft/BotBuilder-V3/issues/127
In the future, please note: the Bot Framework Support team monitors both repositories, so there is no need to cross-post.


Authenticator Application continues to prompt for password after removed

Yubico Authenticator version: 5.0.5
Operating system and version: Windows 10
YubiKey model and version: v4, v5
Bug description summary: Application keeps prompting for password even though it was removed and reset.

Steps to reproduce

setup OATH with password
Use application - it will prompt for password
run ykman oath reset
run ykman and add new credentials
try to use Authenticator - still prompts for password

[Please explain what you did when the bug appeared, and if and how you have been
able to reproduce it.]
I have not tried to reproduce this, but notice it is prompting for password on other tokens.
Expected result
It should see that ykman show password as disabled and not prompt for password.
Actual results
[What actually happened?]
Other info
[Anything else you would like to add?]

Are you restarting the GUI at all between step 2 and 5?

Yes, several times.  Also tried deleting the json file in the .ykman folder.  Also restarting between keys.
RW

From: Dennis Fokin @.>
Sent: Thursday, July 15, 2021 7:29 AM
To: Yubico/yubioath-desktop @.>
Cc: Robert Wagner @.>; Author @.>
Subject: Re: [Yubico/yubioath-desktop] Authenticator Application continues to prompt for password after removed (#730)
Are you restarting the GUI at all between step 2 and 5?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Yubico/yubioath-desktop/issues/730#issuecomment-880619072, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUY3JQGIPV23SBV5MSMWM7TTX3BBXANCNFSM5ANJTOBA.

Have you been able to reproduce this on other computers?

I should be able to test later today.  I do think it may be localized to one computer that I entered the password on, but will try another.
RW

From: Dennis Fokin @.>
Sent: Thursday, July 15, 2021 9:12 AM
To: Yubico/yubioath-desktop @.>
Cc: Robert Wagner @.>; Author @.>
Subject: Re: [Yubico/yubioath-desktop] Authenticator Application continues to prompt for password after removed (#730)
Have you been able to reproduce this on other computers?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Yubico/yubioath-desktop/issues/730#issuecomment-880683288, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUY3JQAOW7PXTFJXIVZHOO3TX3NETANCNFSM5ANJTOBA.

Yes, please, do that and report back. I am not able to reproduce this issue.

Can you provide details on where the secrets are stored and the logic as to whether or not to prompt for the password?
If the software is supposed to look at the key and read that Password protection = enabled/disabled then this is not occurring.
If it is looking at some registry setting : https://github.com/Yubico/yubioath-desktop/issues/390
Enhancement: Add keyring support for storing device password
then I can review those settings.
C:\Program Files\Yubico\YubiKey Manager>ykman oath info
OATH version: 4.4.5
Password protection: disabled
Robert Wagner

From: Dennis Fokin @.>
Sent: Thursday, July 15, 2021 9:31 AM
To: Yubico/yubioath-desktop @.>
Cc: Robert Wagner @.>; Author @.>
Subject: Re: [Yubico/yubioath-desktop] Authenticator Application continues to prompt for password after removed (#730)
Yes, please, do that and report back. I am not able to reproduce this issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Yubico/yubioath-desktop/issues/730#issuecomment-880697075, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUY3JQFPLBFKPR7O3NGNB5LTX3PLDANCNFSM5ANJTOBA.

More Details... No prompt when using ykman, it does prompt when I use my own routines with yubikit library:
I am not sure why, but something I am doing forces it to prompt for password, but the yubikit library doesn't catch my error.
C:\WINDOWS\system32>ykman oath info
OATH version: 5.1.2
Password protection: disabled
                cred_data = CredentialData(
                            oathname_v,
                            OATH_TYPE.TOTP,
                            HASH_ALGORITHM.SHA1,
                            oathsecret_v,
                            digits_v,
                            totpperiod_v,
                            counter_v,
                            issuer_v,
                        )

                o = OathSession(connection)
                o.put_credential(cred_data, touch)

cred_data	CredentialData: CredentialData(name='RBuild', oath_type=<OATH_TYPE.TOTP: 32>, hash_algorithm=<HASH_ALGORITHM.SHA1: 1>, secret=b'\xa9\xa1\xa2\x1c\x83x\xe4\xff$\xe9{Q\xfa\xc3\x08\xc4\xb1\x97\x90\x8b', digits=6, period=60, counter=0, issuer='Azure')
counter	int: 0
digits	int: 6
hash_algorithm	HASH_ALGORITHM: HASH_ALGORITHM.SHA1
issuer	str: Azure
name	str: RBuild
oath_type	OATH_TYPE: OATH_TYPE.TOTP
period	int: 60
secret	bytes: b'\xa9\xa1\xa2\x1c\x83x\xe4\xff$\xe9{Q\xfa\xc3\x08\xc4\xb1\x97\x90\x8b'

Running with: oath accounts add -t --period 60 -i Azure RBuild VGQ2EHEDPDSP6JHJPNI7VQYIYSYZPEEL

This is a problem with writing the same credentials over and over again, even with a ykman oath reset. (issuer and name and secret)

ykman oath reset
---test yubi authenticator - no accounts listed
---close authenticator
ykman oath accounts add -t --period 60 -i Azure RBuild VGQ2EHEDPDSP6JHJPNI7VQYIYSYZPEEL
---Open authenticator  - prompted for password

Aha! I was now able to reproduce your issue with the command ykman oath accounts add -t --period 60 -i Azure RBuild VGQ2EHEDPDSP6JHJPNI7VQYIYSYZPEEL. Turns out it is the combination of the -t flag and a non-standard period that is giving us trouble. You probably noticed that when you started up authenticator the second time, it was waiting for something. It was actually waiting on a touch. This is not the expected behavior. We have identified the issue in ykman cli and we know what is causing it. Next release of ykman cli will have this fixed and is planned to be in Aug/Sept.

ykman cli 4.0.5 with a fix for this has now been released. A release of Yubico Authenticator will come at a later date, it has not been fully decided when yet.


Link-on-demand breaks with reserved names

The following code raises an AttributeError with 2.0.0 (tested on Python 3.5):
from addict import Dict
a = Dict()
a['keys']['x'] = 1

because this line uses __setattr__ instead of __setitem__.

It also breaks if the key isn't a string:
>>> Dict()[1].x = 1
TypeError: hasattr(): attribute name must be string


EXTREMELY Sorry for the new issue.

What is your question?
Quick question (before I close this). Why was the source code hidden for so long? There's no sensitive information or much reason not to. I just wanted to know why this wasn't already open sourced earlier. Especially since you technically supposed to since this was under the official fnf github.

After a response I'll probably stop making new issues.

The source code is hidden cuz we want to prevent potential leaks in future updates. I also noticed that a lot of my stuff is using really bad programming approaches that should not be used as samples. After the mod is canceled there is no reason to keep it a secret and I'm too tired to fix all the programming issues so I decided to open source it now as a signal of the end of the project.

Alr thx man. I'll leave this repo alone now.
Thank you and have a blessed day.


Make logs configurable via environment variables

Description:
It would be useful to make the logging behavior of the application configurable. Specifically, I would like to:

Change the verbosity of logs (e.g., INFO, DEBUG, ERROR).
Enable or disable JSON output for logs.
Pass custom log format strings.

All of these configurations should be adjustable via environment variables to provide more flexibility in different environments.
Suggested environment variables:

LOG_LEVEL: Set the logging verbosity level (e.g., INFO, DEBUG, ERROR).
LOG_FORMAT: Enable plain text or JSON logging output (plain or json).
LOG_FORMAT_STRING: Set the custom log format string.

@zakkg3 Could you take a look ? Thanks!


Unable to find hostfile

How to fix this
[runner.py:148:fetch_hostfile] Unable to find hostfile, will proceed with training with local resources only.
and if there is only 1 GPU, what should the hostfile be? Thanks.

How to fix this
[runner.py:148:fetch_hostfile] Unable to find hostfile, will proceed with training with local resources only.
and if there is only 1 GPU, what should the hostfile be? Thanks.

you donot need to set hostfile option unless there is a multi-nodes model。
you just remove hostfile option in your launch commands.

@starkhu, thanks for responding. We appreciate the community support.
@OliveS9, is this is still a problem or can this issue be closed?

Did you find solution? I have same problem

Hi, any updated solutions as I got the same problem.

i have same problem ...


Fix param comment and log message

There are some parameters missed in function's comment  and a wrong word in log message.
Please check them.
Thanks!
Signed-off-by: yuexiao-wang<EMAIL_ADDRESS>

@nir0s PTAL
Thanks!

Closed: As this PR is more than six months old without having been merged. Please reopen (and rebase if necessary) if it is still relevant.


Remove full mkl package dependency for blas=mkl

@piiswrong  HI, Pls review the changes. The purpose is to remove the annoying full mkl dependency when set blas=mkl.

So looks like we don't need USE_BLAS=MKL at all now?

USE_BLAS is mainly used by mshadow. I want to keep using it when mshadow use mkl func.


HorizontalPager not swiping pages with swipe gesture

1st off...i appreciate your Good work
i've been able to implement the next into buttons, but the default swipe gesture that comes with Horizontal pager seems not to be working, I'm currently working on it but maybe you can check it out...

The user swipe is disabled as of now because the zoom gesture was interfering with the swipe gesture. As of now I have decided to provide other modes to swipe through pages.
You can check HorizontalPager examples.
I will soon be writing a proper Readme. Thanks for using the library,happy to help :)

still the same after setting userScrollEnabled = true, took out the line (to let the default) and the swipe still don't work.

You have to remove the pinchToZoom modifier from the image


Update morph.textproto for Honk

https://github.com/EkType/Honk
Adjusting maximum value and remove seconds reference from description to accommodate to replace Honk’s STYL implementation with MORF.

@yanone making this PR a draft and filed the #151 issue to review the axis change.

Per https://github.com/googlefonts/axisregistry/issues/151#issuecomment-1731883456 I kindly reject this PR


Adding Debian fuse support

Hi, this PR adds Debian fuse mount support: https://torsion.org/borgmatic/docs/how-to/extract-a-backup/
Omit the --archive flag to mount all archives (lazy-loaded):
borgmatic mount --mount-point /mnt

Or use the "latest" value for the archive to mount the latest successful archive:
borgmatic mount --archive latest --mount-point /mnt

Shall we make this optional, since many people don't need this feature and/or have strong opinions about not wanting FUSE installed. Just my experience. 😄

Kudos for taking care of ALL the OSs. 😄
Let's run those tests and then merge it.

Hmm. Our tests don't try different parameters yet. So it won't test the FUSE option. Todo for me to add this later.


update insertion-sort codes

add markdown identifier to code language JavaScript and Java

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

@CleoAguiar Thank you for your contribution to the page! :+1:
We're happy to accept these changes, and look forward to future contributions. :memo:


ICE: getAst(VariableDeclNode) got cast(AstType)255

Expected behavior
Similar to #43 but now the a templated parameter is used instead.
Describe the bug
The error message is now:
vox.context:574: ICE: getAst(VariableDeclNode) got cast(AstType)255
Stack:
> test.vox:14:9: node.1164 type_check expr_call printa
  test.vox:13:13: node.1204 type_check stmt_block stmt_block
  test.vox:13:6: node.1073 type_check decl_function main
  test.vox:1:1: node.485 type_check decl_module test
vox.context.CompilationException@vox.context(574)
----------------
??:? [0x55835b29249c]
??:? [0x55835b273f6d]
??:? [0x55835b0c21bd]
??:? [0x55835b0c1d69]
??:? [0x55835b17da25]
??:? [0x55835b178736]
??:? [0x55835b17865a]
??:? [0x55835b178b7f]
??:? [0x55835b19c5df]
??:? [0x55835b24628f]
??:? [0x55835b24d508]
??:? [0x55835b273bfe]
??:? [0x55835b273a80]
??:? [0x55835b2738dd]
??:? [0x7fe1a7f9c30f]
??:? __libc_start_main [0x7fe1a7f9c3c0]
??:? [0x55835b1bfe2d]

To Reproduce
The function signature is now:
void printa[Args](Args... data) {
  sys_write(1, data[1].ptr, data[1].length);
  sys_write(1, data[2].ptr, data[2].length);
  sys_write(1, data[3].ptr, data[3].length);
}

Additional context

OS: Linux
Hash:<PHONE_NUMBER>269d6c5a6f3943dfe488668dd015a6

How did you instantiate printa?

Yes! For some reason, I had the feeling that you didn't had to create an instance to get the error but you do! Hence the following code can be used as a reference:
@extern(syscall, 60)
void exit(i32 exit_code);

void printa[Args](Args... data) {
  sys_write(1, data[1].ptr, data[1].length);
  sys_write(1, data[2].ptr, data[2].length);
  sys_write(1, data[3].ptr, data[3].length);
}

void main () {
  printa("Hello", ", ", "world!\n");
  exit(0);
}

The correct syntax would be
void printa[Args...](Args... data) {
  sys_write(1, data[1].ptr, data[1].length);
  sys_write(1, data[2].ptr, data[2].length);
  sys_write(1, data[3].ptr, data[3].length);
}

but I will fix the crash to give proper error message

Wait wait wait! I'm veeery confused here! Is the syntax you mentioned supposed to work? Is this what you mean be saying with the phrase "correct syntax"? I used the following code:
@extern(syscall, 60)
void exit(i32 exit_code);

@extern(syscall, 1)
void sys_write(u32 fd, void* ptr, u64 length);

void printa[Args...](Args... data) {
  sys_write(1, data[1].ptr, data[1].length);
  sys_write(1, data[2].ptr, data[2].length);
  sys_write(1, data[3].ptr, data[3].length);
}

void main () {
  printa("Hello", ", ", "world!\n");
  exit(0);
}

And it tries to compile for about 9 seconds and then I get the infamous segmentation fault (core dumped). Was this supposed to happen?
Also keep in mind that [Args...] and [Args] mean two different things. As the first one allows every instance of "Args" to be any type and the second forces every instance to be the same type so both of them should be supported right?

yes, template argument Args... matches 0 or more types and is supposed to be matched in runtime arguments with the same Args... args. I may change this syntax in the future though. Singular Args is a single type.
The hang is a bug, because compiler code atm missed a check for using runtime Args... without matching Args... template arg.

It still gives a segmentation fault when I'm trying to compile tho

I STARTING INDEXING WITH 1!? OMG I'm blind!!!!! Thankfully, I found a bug this way.
Yeah, starting with 0 makes it work and now! The out of index message is awesome! Simple and clean!
Thanks for allowing to index the variadic array like that! That's not only simple compare to the dirty and ugly solution we need to use in D but it will also not introduce any runtime cost.
Now, I only wait for been able to link with ".so" so I can convert my language's front end code from D to Vox.
However, I don't need linking with ".so" libraries to create a system library in Vox. I'll a little bit sick right now and I'm mostly in the bed so I will start working on it when I feel better. Thanks a lot for the quick replies and fixes!

In Vox it works exactly like in D btw

This works in D? Are you sure about that? I converted the code and I'm trying to compile and I get the following error message (using ldc2):
test.d(10): Error: template `test.printa` cannot deduce function from argument types `!()(string, string, string)`
test.d(3):        Candidate is: `printa(Args...)(Args data...)`

The code is:
import core.sys.linux.unistd;

void printa(Args...)(Args data...) {
  write(1, data[0].ptr, data[0].length);
  write(1, data[1].ptr, data[1].length);
  write(1, data[2].ptr, data[2].length);
}

extern (C) void main() {
  printa("Hello", ", ", "world!\n");
}

In D you don't need to use ... on runtime argument, so the code is:
import core.sys.linux.unistd;

void printa(Args...)(Args data) {
  write(1, data[0].ptr, data[0].length);
  write(1, data[1].ptr, data[1].length);
  write(1, data[2].ptr, data[2].length);
}

extern (C) void main() {
  printa("Hello", ", ", "world!\n");
}

https://dlang.org/spec/template.html#variadic-templates

That's cool! Indexing doesn't work as clean an nice as in Vox tho. Also, it requires Phobos to be linked which is a big no no!

Indexing doesn't work as clean an nice as in Vox tho

Not sure what you mean here without an example

Also, it requires Phobos to be linked which is a big no no!

same here

Actually you can define it yourself in one line:
alias AliasSeq(TList...) = TList;

and in Vox it barely exists yet.

Nice! Still it needs Phobos!


Mark all currently failing VPC specs as skipped

Until we have proper API mocks in place we should skip any tests which depend on having a live API Key

All checks have passed
1 successful check

:tada:

I'm working on getting the VPC to use VCR.


Async Stream-based JSON serialization

As mentioned in this issue thread: https://github.com/RSuter/NSwag/issues/1666
This PR also includes other changes that are orthogonal to the intended change of only enabling stream-based deserialization instead of always using an intermediate String instance.
This PR passes all JSON object deserialization work to a new method:
protected virtual async Task<...> ReadObjectResponseAsync<T>(HttpResponseMessage response, ...)

This method uses the Stream from HttpResponseMessage.ReadAsStreamAsync() and JsonTextReader to deserialize the expected object from the stream without using an intermediate String instance. This should result in reduced memory consumption, especially when dealing with large JSON object responses. Because the response is not buffered into a string it means that if an error is encountered the program cannot view the raw response body as a string.
If the DEBUG compilation symbol is defined then the method will instead read the response using an intermediate string (Passing the string from ReadAsStringAsync() into JsonConvert.DeserializeObject) and it will include that string in any raised exceptions.
I wonder if #if DEBUG could be replaced with #if STRING_DESERIALIZATION and adding #if DEBUG\r\n#define STRING_DESERIALIZATION\r\n#endif to the top of the file might be more flexible. I'll see what the project maintainers say.
Unfortunately Json.NET still does not offer an Async DeserializeObject<T> method. While JsonReader/JsonWriter do support async IO, they're only for reading and writing JSON tokens (JToken, JObject, JArray, etc) and not for whole-object deserialization/serialization. I was thinking that I could read the response asynchronously using JsonReader into a root JToken however it isn't feasible to then deserialize an object from a JToken - a quick look inside Json.NET revealed that deserialization uses a very different code-path entirely and doesn't use JToken as an intermediary. It doesn't look like this will be fixed in Json.NET given it's a long outstanding request (dating back to 2012) and Microsoft have announced their own forthcoming JSON serialization/deserialization library which they say will have an emphasis on performance.

Any new information about when it will be merged?
Thanks in advance

I cannot merge this PR as there are too many unrelated changes (e.g. change of full qualified types to using usings which do pollute the namespace with lots of types which might lead to name clashes/compile errors for some users), etc. please create/update the PR with only the stream-based JSON serialization feature for a review...

@Jehoel
Do you have plans on updating the PR with the changes that @RicoSuter suggested?

@RicoSuter @juanperezADD Sorry for the delay - I've rebased my changes to the latest master and restricted my changes to only the addition and use of ReadObjectResponseAsync<T>.

Btw: The new json serializers for .net core 3.0 do not use async, because for small payloads it is killing your performance, due to many context switches.

@SebastianStehle off-topic: but if Microsoft's JSON API will not support async reading from streams, what is their official guidance for deserializing large objects? Surely they could use some form of buffering?
I do wish the Async IO API in .NET included a way for sources to pass metadata like ideal buffer size to their sinks so synchronous parsers can read tokens from an async source, for example.

@Jehoel I think the guidance is to use another serializer ;) ... The System.Text.Json thing is optimized for Web Apis where you typically have small payloads of a few KB to MB

@RicoSuter are we good to merge? :)

Please review the PR. I've fixed the templates.

I just fixed a bug I overlooked earlier where objectBodyAsString was undefined. LGTM now. Thank you for accepting it! :D

I need to do more testing before i can merge (with actual running the client. Did anyone do that with a bigger api?

I’ve added two more comments and i think it would also make sense to change the wording of responseobject vs objectresponse as this is a bit confusing 🙂


Workaround for ovfenv not working after a reboot

Add a wrapper around ovfenv that checks if ovf properties are properly
returned. If not, read the data from the cache stored on disk.
Fixes #754
Fixes #747
Additional fixes:

Correctly sets the locale
creates firstboot file so that firstboot-only scripts do not execute
again
use HOST instead of HOSTNAME as HOSTNAME is a built-in variable

Testing:

tested in fusion 11.0.2
tested on VMC

@zjs thanks for a thorough review! I added the wrapper to sshd_permitrootlogin.sh as well.


[LibJuice][Libdatachannel] Update v0.9.6 / Update v0.16.4

Describe the pull request

What does your PR fix?

Updates libdatachannel to 0.16.4 and libjuice to 0.9.6. libjuice is a dependency of libdatachannel.

Which triplets are supported/not supported? Have you updated the CI baseline?

Same as before.

Does your PR follow the maintainer guide?

Yes.

Yes.
To merge after #22530.

Thanks!


GUI flagging updates

Hello,
We've been exploring the possibility of using magpy for data processing at USGS.  After an initial evaluation with our users, the 2 main features we need in order to complete our evaluation are 1) improved flagging tools, and 2) integration of baseline measurements from our existing systems.
This pull request includes changes to how data flagging works in the magpy gui.  Let us know if you have any comments or concerns.
Thanks,
Jeremy

Hi Jeremey,
I almost finished testing the methods you implemented. Great job! You included many improvements which are extremely nice. I have some issues now with non-magnetic records, which I am also analyzing (using arbitrary keys) but they should be easy to correct. I will merge your changes into master as soon as I have finished the test run and will include everything in version 0.3.97.
Cheers, Roman


Update azure-security-integration.md

add metadata tag engagement-fy23

Learn Build status updates of commit 1d95831:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/azure-vmware/azure-security-integration.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@suzizuber - since you have access to the private repos, you need to make these (and all) changes there. thanks!

Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.
After you make your changes in the private repo, review the articles on staging, and fix any validation issues, you can add the sign-off comment to let PR reviewers know that the updates are ready to be merged.
Read about authors working in the public repo for more information.
If you need help getting set up to work in the private repo, see Set up Git repository locally for documentation.
We'll close this PR. Thank you.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@suzizuber - since your changes are minor, we can reopen this if it's more convenient (and merge it as long as @jjaygbay1 approves)


How it support language detect using appDir for multi domain instead using segment path [lang] ?

Is your feature request related to a problem? Please describe.
How it support language detect using appDir for multi domain?

a.domain.com --- for english   (https://a.domain.com/products)
b.domain.com ---for UK          (https://b.domain.com/products)
don't need to [lang] folder

Describe the solution you'd like
No Idea from docs https://next-intl-docs.vercel.app/docs/next-13/client-components
Describe alternatives you've considered
no idea

You can probably already achieve this with rewrites. I'd like to support this natively in the middleware, I've got it in my todo list here: https://github.com/amannn/next-intl/pull/149


dial tcp: i/o timeout

Hello, I get this timeout everytime I try to pull on my RasberryPi armv6l.
$ time drive pull
Resolving...
 –
Get https://www.googleapis.com/drive/v2/files/root?alt=json: Post https://accounts.google.com/o/oauth2/token: dial tcp: i/o timeout

real	0m30.127s
user	0m27.780s
sys	0m0.530s

$ drive version
drive version: 0.3.2
Commit Hash: <CURRENT_COMMIT>
Go Version: <GO_VERSION>
OS: <OS_INFO>
BuildTime:

I am using your cross-compiled version, don't know if that may be a cause of this or just the fact that the device is slow and therefore the timeout may be set too low. My internet connection is not the best but should not be a problem for drive I guess.
$ speedtest-cli
Retrieving speedtest.net configuration...
Retrieving speedtest.net server list...
Testing from Telekom Austria (<IP>)...
Selecting best server based on latency...
b'Hosted by NEXT LAYER GmbH (Vienna) [5.46 km]: 615.748 ms'
Testing download speed........................................
Download: 2.29 Mbit/s
Testing upload speed..................................................
Upload: 0.09 Mbit/s

firewall or any other filtering or DNS should also not be the problem:
$ time curl -LI https://accounts.google.com/o/oauth2/token
HTTP/1.1 405 Method Not Allowed
Content-Type: application/json
Allow: POST
Content-Length: 33
Date: Mon, 09 Nov 2015 13:05:29 GMT
Expires: Mon, 09 Nov 2015 13:05:29 GMT
Cache-Control: private, max-age=0
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
Server: GSE
Alternate-Protocol: 443:quic,p=1
Alt-Svc: quic=":443"; p="1"; ma=604800

real	0m1.994s
user	0m1.410s
sys	0m0.110s

Hello @monojp, I've encountered this error everytime the internet goes down or when a connection is lost.

Makes sense. My connection may not be the best, but I doubt that it interrupts all the time. I'm connecting only via SSH from the outside btw. and make remote updates and stuff :smile:

Ah I see, true. So one possibility is that SSH does a best retry and can easily re-establish but Google's pipe times out after a certain time and since we aren't yet doing multipart/retryable uploads this might be a trip. Let's do some more research :) Please let me know if you or anyone else might have ideas on what might be causing this.

Interesting, I managed to find out a bit more. I'm blocking hosts on my raspi via "<IP_ADDRESS>" entries in my /etc/hosts and the file is ~12M big (yes, I know thats huuuge, but never had any problems with it). I am also running a dns server (dnsmasq) on it which reads the file into memory and does caching, so there should be no lookup delays.
After cleaning my /etc/hosts file and restarting my dns server, the first query to "accounts.google.com" took about 52ms and drive pull did work (although it took way longer than the first 30s to show me what will be pulled). After re-creating my big hosts file and another restart of dnsmasq the dialup errors started again.
without hosts-file:
$ time dig accounts.google.com +short
accounts.l.google.com.
<IP_ADDRESS>

real	0m0.127s
user	0m0.090s
sys	0m0.030s

with hosts-file:
$ time dig accounts.google.com +short
accounts.l.google.com.
<IP_ADDRESS>

real	0m0.129s
user	0m0.090s
sys	0m0.030s

"dig" reports that the query finishes in 1-50ms but in reality it takes more time than this. So I guess I'm killing my local name resolution with such a big hosts file on a raspberry pi... I also seems to be unrelated to the dnsmasq-server I am running. The big hosts file alone is slowing the whole system down.

Yes, I can confirm that my huge hosts file was the fault (was using lists from www.hosts-file.net). This seems to be a bottleneck on slow systems. I trimmed down the file and everything works now.

Thank you for the investigation and for the analysis this issue will actually be useful for other users, I think two have mentioned it before. If you'd like please feel free to make a wiki entry about this :)
Thank you!


Experiment: RTS Size Optimizations

Trying to reduce the RTS size regression incurred by the Rust version upgrade.

Applied to https://github.com/dfinity/motoko/pull/4677


Rename "clear" to "clearUndoHistory"

Having a top level function called clear is quite misleading. This doesn't look like it will clear undo history:
useStore.getState().clear()

I think we should either rename clear to clearUndoHistory or move all of these helper functions into a top level object, undoHelpers. So the above would look like this:
useStore.getState().undoHelpers.clear()

Yes. I like both suggestions, and I might lean towards the second suggestion.
The original idea to keep things very terse (and potentially unclear) was the minimalist approach the @pmndrs team took with zustand.

But I'd much prefer making things more clear. Thanks for this great suggestion!

In v2, all utilities will be under a temporal object attached to the store. Thank you for the great suggestion! I preferred nesting objects to keep concise names.


Support Relay components as markers

Using components which uses Relay currently doesn't work because the relay property isn't passed down when markers are drawn.
I'd like to make a PR for this but I don't really know how the library works. If @istarkov could give some advice on where to look it'd be great.

Maybe here?

IMHO the problem is the same as here https://github.com/istarkov/google-map-react/issues/64,
As I have no idea how to pass all context into other rendering tree.
So the problem is here https://github.com/istarkov/google-map-react/blob/master/src/google_map.js#L414
Have you tried to pass relay variables explicitly? As like as <Marker relay={relay} ?

Passing relay as a prop doesn't work, however passing the current RelayEnvironment as context seems to work.
When I render the component as-is I get these errors:

warning.js:44 Warning: Failed Context Types: Invalid prop/context relay supplied to Relay(MapMarker), expected undefined to be an object conforming to the RelayEnvironment interface. Check the render method of MapExplorer

warning.js:44 Warning: Failed Context Types: Required context route was not specified in Relay(MapMarker). Check the render method of MapExplorer

invariant.js:38 Uncaught Invariant Violation: RelayContainer: Relay(MapMarker) was rendered with invalid Relay context undefined. Make sure the relay property on the React context conforms to the RelayEnvironment interface

If I add this to the Map component
static childContextTypes = {
    relay: React.PropTypes.any
};
getChildContext() {
    return { relay: RelayCommonEnvironment.get() };
}

The errors disappear, but data isn't actually passed downstream (this.props.<fragmentName> on MapMarker is undefined).
RelayCommonEnvironment.get() returns the environment Relay was initialized with.
This is how the components are rendered
render() {
    const { markers } = this.props.mapExplorer;
    const comps = markers.map((marker, index) =>
        <MapMarker
            key={index}
            markerFragment={marker}
            lat={marker.location.lat} lng={marker.location.lng}
        />
    );

    return (
        <GoogleMap {...mapSettings}>
            {comps}
        </GoogleMap>
    );
}

(marker is not undefined when I assign it to markerFragment, so the value is changed by Relay somewhere between the creation and the rendering)

At now I have no idea how to pass all context vars into other rendering tree. Help wanted as in related issue. Ill close this issue as its the same problem as there.

Good news everyone! I think I solved the issue :tada: :tada:
Just follow the documentation.

First, explicitly requiring context to be accessible in the component which renders GoogleMap

class MapComponent extends React.Component {

    // This way
    static contextTypes = {
        router: React.PropTypes.object.isRequired,
        relay: React.PropTypes.object.isRequired
    };

    //...
}

Generate a new context in the rendering tree of each Marker. I find useful to use a HoC to do that, but you could do it in the component itself (moreover, this is probably not the best way to write an HoC)

class WithContext extends React.Component {
    // capture the fields passed by MapComponent
    static childContextTypes = {
        router: React.PropTypes.object.isRequired,
        relay: React.PropTypes.object.isRequired
    };

    // provide the context to children
    getChildContext() {
        return {
            router: this.props.context.router,
            relay: this.props.context.relay
        };
    }

    render() {
        const Component = this.props.component
        return <Component {...this.props} />;
    }
}

Pass your context from Map's render() method

render() {
    const markers = collection.map((item, index) =>
        <WithContext
            component={MapMarker}
            context={this.context}
            props_of_MapMarker={item}
            key={index}
            {...location}
        />
    );

    return (
        <GoogleMap {...mapOptions}>
            {markers}
        </GoogleMap>
    );
}

Enjoy! :tada:

@istarkov probably this strategy could be merged in the library, what do you think?

Should work without any hacks after this pr https://github.com/istarkov/google-map-react/pull/198
Now in 0.16v


Editing the captive http portal to use own images and styles

I have modified the src index.html to include a logo and included an image tag in the HTML. However this doesn't work when serving the portal?? I think the logo file needs to be included somewhere so it becomes available?
I also want to add my own custom fields to be saved on NVS do I need to create a separate page to do this or can I modify the portal page?

for your additional files you might check:
(depending on your Build system):
CMakeLists.txt -
5. EMBED_FILES src/style.css src/code.js src/index.html   ADD_YOUR_NEW_FILES_HERE)
and
10. set(COMPONENT_EMBED_FILES src/style.css src/code.js src/index.html  ADD_YOUR_NEW_FILES_HERE)
and/or
component.mk -
4. COMPONENT_EMBED_FILES := src/style.css src/code.js src/index.html ADD_YOUR_NEW_FILES_HERE


Add ACL functions to admin client

Resolves issue: https://github.com/tulios/kafkajs/issues/465

@Nevon Thanks for the thorough review! I opened the draft PR to check if the basic ACL test is working in the CI. I am still working to on it to make it ready for review, that's includes code cleanup, separating the test case into separate files, more proper validation checks in the admin client and others including your suggestions :smile:

What's the situation here? Is this PR ready to be merged?

Anything I can do to assist in getting this feature moving along?

Hey @EricMCornelius, I will take over this PR soon and make sure it gets merged. We had other priorities but now it's the time to get this one in.

Step 1 to get this to master (#898)

@Nevon take a final look, it's all good for me now.

I forgot about the Typescript types, that's still missing. I can add it later.


Closing a chat in pregame mutes all

When still in pregame, closing the chat will mute all.
There should be an exception if the game hasn't started yet.

New pre-release should address this issue


The pipeline triggered by Webhook is not shown in the KS running record

What is version of KubeSphere DevOps has the issue?
v3.3.0
How did you install the Kubernetes? Or what is the Kubernetes distribution?
Amazon Elastic Kubernetes Service
What happened?
The pipeline triggered by Webhook, which cannot be displayed in the record list, has been running in real time in the Jenkins console
ks console:

jenkins console：

Relevant log output
No response
Additional information
It's similar to this problem
https://github.com/kubesphere/ks-devops/issues/772#issue-1332563233

See also https://github.com/kubesphere/ks-devops/issues/772#issuecomment-1232493860
/close


added no-store header to st2 nginx configuration

Added the no-store cache control header in order to prevent webui from serving cached and not up-to-date versions of opened workflows.

I have no idea how to set this for / location only. I've now tried everything. Is it an issue if this was a global header?

Can you please validate with them where do they put the headers? I've put them into the / location, but it has been reported to me by my devs that this doesn't seem to work and they're still facing issues because they're loading stale flows from the cache. So, before this is merged, it would be nice if we knew whether this actually works.

Have your users disabled their cache locally?

no, but I haven't asked them to (and all the guides on how to do this on the web are sort of... hacky). I've had a setup on a virtual machine, where the install was local and this was a set and forget kind of thing. But now I'm moving to EKS and while I can just set it in the st2web containers and reload nginx, I don't like the thought of doing this after every update to the pipeline that restarts the pods


Bottom Navigation using with " react-native-router-flux "

I'm running sample project.
i'm using this module all works fine... but my question is :- keeping the footer fixed how can i change the body and navigate to another screen  ( using react-native-router-flux )..
Here is my code:-
import React, {Component} from 'react';
import BottomNavigation, {Tab} from 'react-native-material-bottom-navigation';
import Icon from 'react-native-vector-icons/MaterialIcons';
import {Actions} from 'react-native-router-flux';

export default class FooterTab extends Component {
    render() {
        return (
            <BottomNavigation
                labelColor="white"
                rippleColor="white"
                style={{
                    height: 56,
                    elevation: 8,
                    position: 'absolute',
                    left: 0,
                    bottom: 0,
                    right: 0
                }}
                onTabChange={(newTabIndex) => Actions.drawerMenu({newTabIndex : newTabIndex})} //tabNavigating(newTabIndex)}
            >
                <Tab
                    barBackgroundColor="#203E39"
                    label="Home"
                    icon={<Icon size={24} color="white" name="home" />}
                />
                <Tab
                    barBackgroundColor="#203E39"
                    label="Chat"
                    icon={<Icon size={24} color="white" name="chat" />}
                />
                <Tab
                    barBackgroundColor="#203E39"
                    label="Account"
                    icon={<Icon size={24} color="white" name="supervisor-account" />}
                />
                <Tab
                    barBackgroundColor="#203E39"
                    label="Log-Out"
                    icon={<Icon size={24} color="white" name="power-settings-new" />}
                />
            </BottomNavigation>
        );
    }
}

Here is my Screen:

I haven't used react-native-router-flux, so I can't tell you exactly how you navigate between screens. According to their docs, if you have <Scene key="chat" .. /> in your app, you navigate to this scene with Actions.chat().
Your question isn't really related to react-native-material-bottom-navigation. I think you'll get a better answer if you look through the examples in react-native-router-flux and ask them if anything is unclear.

i tried like this
import {Actions} from 'react-native-router-flux';
.....
  <BottomNavigation
                labelColor="white"
                rippleColor="white"
                style={{
                    height: 56,
                    elevation: 8,
                    position: 'absolute',
                    left: 0,
                    bottom: 0,
                    right: 0
                }}
                onTabChange={(newTabIndex) => alert(`New Tab at position ${newTabIndex}`)}
            >
                <Tab
                    onPress={() => Actions.home()}   <---------------------
                    barBackgroundColor="#203E39"
                    label="Home"
                    icon={<Icon size={24} color="white" name="home" />}
                />
              <Tab
                    onPress={() => Actions.chat()}   <---------------------
                    barBackgroundColor="#203E39"
                    label="chat"
                    icon={<Icon size={24} color="white" name="chat" />}
                />
</BottomNavigation>

i want the bottom navigation to be fixed but entire screen appears
my home screen:

Below code worked me thank you....
imports my Home ,muzic, contact and news components...
<View style={{flex: 1,}}>
                    <View style={{flex: 9, backgroundColor: 'lightblue'}}>
                        {this.state.activeTab === 0 ?
                            <Home />
                            :this.state.activeTab === 1 ?
                                <Muzic />
                                :this.state.activeTab === 2 ?
                                    <Contact />
                                    : <News />
                        }
                    </View>
                    <View style={{flex: 1}}>
                        <BottomNavigation
                            activeTab={this.state.activeTab}
                            labelColor="white"
                            rippleColor="white"
                            style={styles.bottomNavigation}
                            onTabChange={this.handleTabChange}
                        >
                            <Tab
                                barBackgroundColor="#37474F"
                                label="Home"
                                icon={<Icon size={24} color="white" name="ondemand-video" />}
                            />
                            <Tab
                                barBackgroundColor="#00796B"
                                label="Muzic"
                                icon={<Icon size={24} color="white" name="music-note" />}
                            />
                            <Tab
                                barBackgroundColor="#5D4037"
                                label="Contact"
                                icon={<Icon size={24} color="white" name="book" />}
                            />
                            <Tab
                                barBackgroundColor="#3E2723"
                                label="Newpaper"
                                icon={<Icon size={24} color="white" name="library-books" />}
                            />
                        </BottomNavigation>
                    </View>

can u please share the "handleTabChange( )" here ?

Hi .. @habeebrahmanpt., Hope this helps you
...
this.handleTabChange = this.handleTabChange.bind(this);
...
handleTabChange(newTabIndex, oldTabIndex) {
        this.setState({activeTab: newTabIndex});
    }

Thank You