Re-designed from scratch

[Fixed]
isdigit method gives false result for float value. So, fixed it by spliting the values into '.' and checking each part using isdigit method.
[Modified]

More messagebox is added to make user-friendly.
More widget are added to show instruction when hovered over them.
Option is asked to user whether to show shadow in their pie-chart.
Replaced tk.Entry widget by ttk.Entry widget. ttk.Entry is way more attractive than tk.Entry.

[NEW]

Re-designed main window.
Re-designed register window.
Added functionality for editing values.
Replaced jpg image in README.md by .gif.
Label is added at the above of each text-widgets.
Replaced explode entry widget with LabelFrame and Radio-Buttons.
Changed the color of the most of the widgets to 'white' for better appearence.
Added check-button in register window for enabling and disabling text-widgets.
Changed color to the same as before clicking to the button when user clicks the buttons.
Added hand cursor when user hovers to the buttons, radio-buttons, labelframe and check-buttons.
Added arrow cursor when the text-widets in register window is disabled and xterm when enabled.
Added functionality of placeholder like in HTML but not in the exact way because tkinter does not supports the way it does in HTML.
As the program grew, it was very hard to track the work in a single file. So, I splitted file into:

run.py: Runs the entire program.
ui_main.py: Responsible to show the main GUI window.
commands.py: Responsible for the action when user clicks any buttons.
link.py: Responsilbe to open the github page to show the source code of this program.
tips.py: Responsible to show the pop-up window with some information when hovered to any widget.
include.py: Responsible for adding icon to the window and to position the window to the center of the screen.
ui_view.py: Responsible to show the GUI window of having the data entered by the user (In short, its Register GUI window.

Important Note
Since people who know about the github, they know about progrmming so what I feel is you don't need to write the important note stuff in README.md.

P.S. I think we came to the end of our project as I don't see any room for improvement. It was very exciting working in your project. Hope you upload more such exciting project so I can help you again.

If you want to contact me you can mail me in<EMAIL_ADDRESS>

Wow super cool pull request dude!

It was nice collaborating with you. Hope we get to work on another project soon!

Thank you very much. I hope too.


Error 'DISALLOWED_SQL_FUNCTION' in new superset update 4.0.2

Bug description
I updated the Docker image of Superset to the latest in my docker-compose file, which is 4.0.2. After this, I'm unable to read any data from the dataset. But when I revert back to 4.0.1, there is no issue with the SQL executions.

How to reproduce the bug

Update the docker-compose file to the latest (4.0.2).
Create a database connection.
Write an query to get data.
Error - 'DISALLOWED_SQL_FUNCTION'

Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Wow. @dosubot nailed!

Thank you, @dosu. It's working now.


Save Button only loads on page refresh for manually set data-pin-do tags

gatsby-plugin-pinterest version: 3.2.2

Problem description:
Save Button does not appear until page refresh if you don't include the saveButton attribute in the plugin options (which sets data-pin-hover) and instead include a tag where you want the pin it button to appear like so (which adds the save button for individual images):
<a href="https://www.pinterest.com/pin/create/button/" data-pin-do="buttonBookmark">
</a>

Suggested solution:
PR incoming
I can create a small reproduction if needed but wanted to submit the issue while it was fresh in my mind.

Thanks for bringing this up @robinske! Thank you for linking to docs as well - I think this makes total sense and it's probably a common use case. Let's follow up on the PR 🙂


enabling create app in current directory

Fixes #110
by specifying --force this will allow you to create project in current directory.
@developit just curious, the discussion emphasize upon the usage of --force?
What if we do it without this? Whats the harm with that?

 :P Merging this one 😄


c8d/daemon: Mount root and fill BaseFS

This fixes things that were broken due to nil BaseFS like docker cp
and running a container with workdir override.
This is more of a temporary hack than a real solution.
The correct fix would be to refactor the code to make BaseFS and LayerRW
an implementation detail of the old image store implementation and use
the temporary mounts for the c8d implementation instead.
That requires more work though.
Signed-off-by: Paweł Gronowski<EMAIL_ADDRESS>
- What I did
- How I did it
- How to verify it
- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

For upstreaming, squash with https://github.com/rumpl/moby/pull/104


Core :: Cleanup tasks for resource/configuration-service - Remove keptn-configuration-service ServiceAccount

As of v0.18, the resource-service will use the keptn-resource-service ServiceAccount, which has the permission to read secrets in order to be able to read upstream credentials. In versions <=0.17, that service was using the keptn-configuration-service ServiceAccount, which is still needed in v0.18, because otherwise the pod running the v0.17 resource service will not be able to access any git upstream credentials during the upgrade from 0.17 to 0.18.
After the release of 0.18, this keptn-configuration-service ServiceAccount can and should be removed.
Action Items

[ ] Remove the keptn-configuration-service Service Account and its related RoleBindings

DoD

[ ] Acceptance criteria are met
[ ] ZD tests work for updates from versions >=0.18 to the version including the changes introduced for this ticket

I guess this was already been done by this PR https://github.com/keptn/keptn/pull/8530

Resolved via https://github.com/keptn/keptn/pull/8530


[DONTMERGE] Test 6.21.1 conflct resolution

Regression with ORCA failed because there is known flaky test for parallel cursors


Replace brotlipy with brotlicffi

The brotlipy package has been renamed to brotlicffi.  Update the imports
and dependencies accordingly.  The major advanage of the new package
is that it no longer collides with the Python bindings provided
by brotli itself.

Note: if you want to continue supporting Python 2.7, this requires https://github.com/python-hyper/brotlicffi/pull/172 to be merged and released first.


[metadata] clear search scroll when complete

The search scroll must be closed when it's no longer needed otherwise elasticsearch will hold onto them until the timeout is reached. In previous versions of elasticsearch the number of scrolls that could be open was unlimited, with ES7 the default is now 500. It can be overriden with search.max_open_scroll_context.
https://www.elastic.co/guide/en/elasticsearch/reference/6.8/search-request-scroll.html#_clear_scroll_api

@hexedpackets updated if you could PTAL.

How come we didn't see any issues when we mirrored traffic via envoy?

@malish8632 we only did 1% of production traffic when dark loading which wasn't enough to surface this issue.


Fix output, suppress warning

Fix output: 0/1 images processed
Suppress this warning:
UserWarning: Argument interpolation should be of type InterpolationMode instead of int. Please, use InterpolationMode enum.

Thank you, this fix works well on google colab


BUG - Firestore - Getdocument v2.4.4

Hi,
Describe the bug
I can't get a document from Firestore for a few hours on my esp32
I was on a few weeks old version of your library
but after updated to the last version (v2.4.4) it is still the same.
To Reproduce
Steps to reproduce the behavior:

Launched the GetDocument example from Firestore folder with your credential.
The file will be created on your Firestore database
But your ESP32 will be stuck after serial print "Get a document..."
Nothing happen in several minutes....

IDE and its version:

Arduino
Version v2.4.4

ESP32 Arduino Core SDK version

Espressif systems version 1.0.6 --> I'm not sure it's the right answer.

Thanks for report this bug.
The bug was fixed, please update the library to v2.4.5.

Thank you !


Improve display when 2 lines on same track

When two lines uses the same tracks or route, current display put one on the other and users don't get the actual information. Same thing for stations.

There are 2 lines on the above picture, a blue and a red one.
Can we imagine that when 2 routes or 2 stations are very close, it shows only 1 line hatched or dotted.

Exemple on carto.metro map

@Kalepom this is an important issue, I agree!

@Kalepom I'm working on this!


Add a Korean l10n reviewer to OWNERS_ALIASES

This PR updates OWNERS_ALIASES
to add @pjhwa to sig-docs-ko-reviews. (Korean l10n team reviewer)
@pjhwa is qualified to be an reviewer according to the following requirements.
Member for at least 3 months: 14 Apr, 2020
Primary reviewer for at least 5 PRs to the codebase
is:pr assignee:pjhwa
Reviewed or merged at least 20 substantial PRs to the codebase
is:pr assignee:pjhwa
is:merged author:pjhwa
Nominated by a subproject approver
/cc @kubernetes/sig-docs-ko-owners
Thank you.

@pjhwa is eligible for Korean reviewer ! I would love to work with him :)
/cc @zacharysarah @jimangel

/lgtm
/approve


IdentityModel use with Xamarin Forms?

I am looking to evaluate IdentityModel2 for use within a Xamarin Forms application but am running into issues installing the corresponding nuget package due to PCL profile issues.
Issue = "Could not install package 'IdentityModel 2.0.0'. You are trying to install this package into a project that targets '.NETPortable,Version=v4.5,Profile=Profile78', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author."
Can you provide me with any direction on how this may have been resolved already, or give me some pointers on how I may resolve this on my own?

v2 is netstandard - i was under the impression this is working with Xamarin.
v1 is PCL - you can try that

Thanks, reverting to v1 installs correctly.
I think it'll be more a matter of how to get my Xamarin Forms app PCL projects to work with the netstandard libraries.
Thanks for your quick response!

@leastprivilege reading the docs, I can't find the DiscoveryClient class in the PCL version (1.13.1).
What's the alternative?

that is true. Feel free to backport it and PR.

There you go.

Will accept it?
When can I expect a new version on NuGet?


Add an example to read an environment variable

fixes #401

Thanks for the contribution.  The AppVeyor might be issues with the new Rust version on Windows.  Let me dig into that for you to make sure master is working as the errors seem to be unrelated to the code change.

OK, I dug into it and there is a symptom of new regression due to rust version update, but that is not causing the error in AppVeyor.

@AndyGauge Thanks for the quick response. I will update the code to work on windows as well.

I've updated the code and removed all the file operations. I will squash the commits once everything is fine with this PR.

I forgot to mention putting in a few lines about the code, but you took care of that already!  Thanks.

@AndyGauge I've squashed the commits.

@Dineshs91  would be happy to help you get the changes made to complete this.  Please let me know if you are in need of support.


feat: create alias for CovariantClass α α (· * ·) (· ≤ ·) etc

This may be worthwhile whether we eventually merge #13124.

!bench


Getting all ConceptMaps fails

Hi,
running GET /snowowl/fhir/ConceptMap ends up with
  "resourceType": "OperationOutcome",
  "issue": [
    {
      "severity": "error",
      "code": "exception",
      "diagnostics": "Something went wrong during the processing of your request. Exception: null",
      "details": {
        "text": "Bad Syntax in %s",
        "coding": [
          {
            "code": "msg_bad_syntax",
            "system": "http://hl7.org/fhir/operation-outcome",
            "display": "Bad Syntax in %s"
          }
        ]
      },
      "location": [],
      "expression": []
    }
  ]
}```

What is in: SNOMED-CT intl 20190731, SNOMED-CT UK 20190601, LOINC-SNOMED mappings 2017

Log here - https://pastebin.com/5uhyTL6K.

Any idea would be appreciated.

Petr

Hi @psiotwo,
Thank you for reporting the problem.
The issue was that the SNOMED CT FHIR support module did not properly fall back to the IDs when a given concept did not have a preferred term in the requested locale (language refset).
A newer image will be up soon with the fix.
Regards,
Mark


Invalid Host header

Cool repo! It's working nicely.
However when I try to connect to my Vue app running at localhost:8080, through your proxy, I get a document containing "Invalid Host header". And that's all I get! (Directly at localhost:8080 it works fine). Do you know if this error is something that comes from mehserve?

Turns out it was Vue's fault. Fixed it by creating in project root
// vue.config.js
module.exports = {
    // options...
    devServer: {
        disableHostCheck: true
    }
}

Thank you for sharing the solution 🙏

Another solution would bet o use allowedHosts:
// vue.config.js
module.exports = {
    // options...
    devServer: {
        allowedHosts: [".meh"],
    }
}


feat: remove function

Description
Implement the remove_XXX function.
These remove data paths defined by the user.

Related links
Jira: https://tier4.atlassian.net/browse/RT2-389
CARET_doc: https://tier4.github.io/CARET_doc/latest/configuration/intra_node_data_path/
ipynb: https://drive.google.com/file/d/1FOme9ao5oUEM7SrrpGMSWwg6hMdZVXWt/view?usp=drive_link
　yaml: https://drive.google.com/file/d/1iKZlExzQghfGGRyJC-mR_KjPTMhPJ_Jw/view?usp=drive_link

Notes for reviewers

Pre-review checklist for the PR author

[x] I've confirmed the contribution guidelines.
[x] The PR is ready for review.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR has been properly tested.
[ ] The PR has been reviewed.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] (Optional) The PR has been properly tested with CARET_report verification.
[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@atsushi421
Correction of review applied.
In addition, reproduced files are now available in the description section of the PR.
The reproduction yaml file is the output from CARET_demo with this operation.

@nabetetsu
Please review.
Also, reproduction scripts are available at Related links.

@taro-yu
Review Please.


Versions > 1.0.6 trigger NVD vulnerability problem

See https://nvd.nist.gov/vuln/detail/CVE-2017-18640
This could possibly be caused by the addition of PassthroughConstructor

Would be closed by https://github.com/owainlewis/yaml/issues/40


Update outdated files in the dev-1.20-ko.4 branch (2)

Fixes the part of #26284
This PR contains updates for the following files:

[x] M9. content/en/docs/concepts/services-networking/service.md | 1(+XS) 1(-)
[x] M10. content/en/docs/concepts/workloads/controllers/job.md | 1(+XS) 1(-)
[x] M11. content/en/docs/concepts/workloads/controllers/ttlafterfinished.md | 1(+XS) 1(-)
[x] M12. content/en/docs/reference/_index.md | 2(+XS) 1(-)
[x] M13. content/en/docs/reference/command-line-tools-reference/feature-gates.md | 337(+L) 151(-)

/assign @yoonian

/lgtm

Thank you ~!
/approve


Real commitment verification

This PR can be closed in favor of https://github.com/Snowfork/polkadot-ethereum/pull/266

Closing in favor of https://github.com/Snowfork/polkadot-ethereum/pull/266


Increase Sentry alert threshold to 80%

Value
Current alerting is too noisy
Functional Requirements:

Change threshold back to 80%

Acceptance Criteria:

Sentry alerting threshold is back to 80%

Notes:

Updated the sentry threshold  from 60% to 80%


Implement continuations in task-to-thread model.

This is done using a condition variable upon which the awaiting thread will block if the continuation has not be resumed by the point of await. The resuming thread will signal this condition variable, thereby unblocking the awaiting thread.
Rdar://99977665

@swift-ci please test

I was going to ask whether a CI run with the freestanding preset would be appropriate here, but I see https://github.com/apple/swift/pull/61835, so maybe that's blocked until that goes in?

preset=stdlib_S_standalone_minimal_macho_x86_64,build,test
@swift-ci please test with toolchain and preset

@swift-ci please test Windows platform

@swift-ci please test

preset=stdlib_S_standalone_minimal_macho_x86_64,build,test
@swift-ci please test with toolchain and preset

preset=stdlib_S_standalone_minimal_macho_x86_64,build,test
@swift-ci please test with toolchain and preset


 It is not useful every time.

I think this CI failure is a problem inside Travis https://travis-ci.org/crystal-lang/crystal/jobs/239531650.

ping


Unable to execute feature test against ScalaTest 3.0.0

I have a project here https://github.com/peterpilgrim/credit-suisse-crowd-funding and a commented out feature test
Is there an incompatibility between Finatra and Scala Test 3.0.0?
Here is my project's build.sbt. Is it something to do with the order of the dependencies? Or the dependency versions themselves?
Expected behavior
The feature test should invoke a GET /hello and return the "Hello world" plain text
Actual behavior
I actually found a stacktrace:
An exception or error caused a run to abort.
java.lang.AbstractMethodError
    at org.scalatest.Assertions$class.$init$(Assertions.scala:1342)
    at com.twitter.inject.server.EmbeddedTwitterServer.<init>(EmbeddedTwitterServer.scala:77)
    at com.twitter.finatra.http.EmbeddedHttpServer.<init>(EmbeddedHttpServer.scala:54)
    at uk.co.xenonique.clients.cs.crowdfund.loan.CrowdSourceServerFeatureTest.<init>(CrowdSourceServerFeatureTest.scala:14)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
    at java.lang.Class.newInstance(Class.java:442)
    at org.scalatest.tools.Runner$.genSuiteConfig(Runner.scala:1422)
    at org.scalatest.tools.Runner$$anonfun$31.apply(Runner.scala:1236)
    at org.scalatest.tools.Runner$$anonfun$31.apply(Runner.scala:1235)
    at scala.collection.immutable.List.map(List.scala:273)
    at org.scalatest.tools.Runner$.doRunRunRunDaDoRunRun(Runner.scala:1235)
    at org.scalatest.tools.Runner$$anonfun$runOptionallyWithPassFailReporter$2.apply(Runner.scala:1011)
    at org.scalatest.tools.Runner$$anonfun$runOptionallyWithPassFailReporter$2.apply(Runner.scala:1010)
    at org.scalatest.tools.Runner$.withClassLoaderAndDispatchReporter(Runner.scala:1500)
    at org.scalatest.tools.Runner$.runOptionallyWithPassFailReporter(Runner.scala:1010)
    at org.scalatest.tools.Runner$.run(Runner.scala:850)
    at org.scalatest.tools.Runner.run(Runner.scala)
    at org.jetbrains.plugins.scala.testingSupport.scalaTest.ScalaTestRunner.runScalaTest2(ScalaTestRunner.java:138)
    at org.jetbrains.plugins.scala.testingSupport.scalaTest.ScalaTestRunner.main(ScalaTestRunner.java:28)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)

Process finished with exit code 0

By the way, I also see the same stack trace from SBT sbt run
Steps to reproduce the behavior
To reproduce just sbt test in my project
Thanks very much for taking the time in advance!
+PP+

@peterpilgrim Finatra currently uses ScalaTest 2.2.6. It is not expected to be able to work with any higher version at this time.
FWIW, it looks like org.scalatest.Matchers which is mixed into the EmbeddedTwitterServer is the cause of some incompatibility between 2.2.6 and 3.0.0.
I understand it may not be possible but have you tried using the same ScalaTest version as Finatra?

I downgraded my project to Scalatest 2.2.6 as recommended by @cacoco .
I retested on Windows 10 and both Mac OS X and the feature tests now worked splendidly.
===========================================================================
uk.co.xenonique.clients.cs.crowdfund.loan.CrowdSourceServer Stats
===========================================================================
Crowd Source Loan Platform/admission_control/deadline/deadline_budget_ms = 299954.0 = [299954.0]
Crowd Source Loan Platform/admission_control/deadline/transit_latency_ms = 46.0 = [46.0]
Crowd Source Loan Platform/handletime_us                               = 5167.0 = [5167.0]
Crowd Source Loan Platform/request_latency_ms                          = 7.0 = [7.0]
Crowd Source Loan Platform/request_payload_bytes                       = 0.0 = [0.0]
Crowd Source Loan Platform/response_payload_bytes                      = 37.0 = [37.0]

Counters:
Crowd Source Loan Platform/connects                                    = 1
Crowd Source Loan Platform/received_bytes                              = 173
Crowd Source Loan Platform/requests                                    = 1
Crowd Source Loan Platform/sent_bytes                                  = 117
Crowd Source Loan Platform/success                                     = 1

Gauges:
Crowd Source Loan Platform/connections                                 = 1.0
Crowd Source Loan Platform/pending                                     = 0.0
finagle/build/revision                                                 = 3.73256323E11

===========================================================================
Closing EmbeddedHttpServer: uk.co.xenonique.clients.cs.crowdfund.loan.CrowdSourceServer
===========================================================================

Process finished with exit code 0

I'm closing this issue.


fixed dt in event rate

Codecov Report
Base: 0.14% // Head: 0.13% // Decreases project coverage by -0.00% :warning:

Coverage data is based on head (16538ec) compared to base (87e9947).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff            @@
##             dev     #23      +/-   ##
========================================
- Coverage   0.14%   0.13%   -0.01%
========================================
  Files          8       8
  Lines       1399    1432      +33
========================================
  Hits           2       2
- Misses      1397    1430      +33

Impacted Files
Coverage Δ

src/legend_data_monitor/analysis.py
0.00% <0.00%> (ø)

src/legend_data_monitor/parameters.py
0.00% <0.00%> (ø)

src/legend_data_monitor/plot.py
0.00% <0.00%> (ø)

src/legend_data_monitor/run.py
0.00% <0.00%> (ø)

src/legend_data_monitor/timecut.py
0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Home page shows RKE2 Custom cluster as Active when it has not successfully provisioned

Setup

Rancher version: v2.6-a01b164f2e371f04aea7c0c1864c687b8ad70cca-head
Browser type & version: Chrome

Describe the bug
Home page shows RKE2 Custom cluster as Active when it has not successfully provisioned
To Reproduce

Fresh install of rancher v2.6-head
Provision a downstream RKE2 Custom cluster with cluster's name exceeding 63 characters
Reproduced

Result
Rancher logs error out stating cluster's name must not exceed 63 characters.  From Cluster Management the cluster is in a Reconciling state.  From the Home page, the cluster is shown as Active
Expected Result
Cluster state on Home page should reflect Reconciling, as reported by both Rancher logs and Cluster Management
Screenshots
Cluster Management

Home

Rancher logs
2022/04/29 18:26:37 [ERROR] error syncing 'c-m-89c4fxmw/custom-926c73f36662': handler unmanaged-machine-secret: failed to create fleet-default/custom-926c73f36662 rke.cattle.io/v1, Kind=RKEBootstrap for unmanaged-machine c-m-89c4fxmw/custom-926c73f36662: RKEBootstrap.rke.cattle.io "custom-926c73f36662" is invalid: metadata.labels: Invalid value: "jkeslar-maxxx-break-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx": must be no more than 63 characters, failed to create fleet-default/custom-926c73f36662 rke.cattle.io/v1, Kind=CustomMachine for unmanaged-machine c-m-89c4fxmw/custom-926c73f36662: CustomMachine.rke.cattle.io "custom-926c73f36662" is invalid: metadata.labels: Invalid value: "jkeslar-maxxx-break-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx": must be no more than 63 characters, failed to create fleet-default/custom-926c73f36662 cluster.x-k8s.io/v1beta1, Kind=Machine for unmanaged-machine c-m-89c4fxmw/custom-926c73f36662: Machine.cluster.x-k8s.io "custom-926c73f36662" is invalid: metadata.labels: Invalid value: "jkeslar-maxxx-break-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx": must be no more than 63 characters, requeuing
2022/04/29 18:26:37 [ERROR] error syncing 'c-m-89c4fxmw/custom-926c73f36662': handler unmanaged-machine-secret: failed to create fleet-default/custom-926c73f36662 rke.cattle.io/v1, Kind=RKEBootstrap for unmanaged-machine c-m-89c4fxmw/custom-926c73f36662: RKEBootstrap.rke.cattle.io "custom-926c73f36662" is invalid: metadata.labels: Invalid value: "jkeslar-maxxx-break-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx": must be no more than 63 characters, failed to create fleet-default/custom-926c73f36662 rke.cattle.io/v1, Kind=CustomMachine for unmanaged-machine c-m-89c4fxmw/custom-926c73f36662: CustomMachine.rke.cattle.io "custom-926c73f36662" is invalid: metadata.labels: Invalid value: "jkeslar-maxxx-break-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx": must be no more than 63 characters, failed to create fleet-default/custom-926c73f36662 cluster.x-k8s.io/v1beta1, Kind=Machine for unmanaged-machine c-m-89c4fxmw/custom-926c73f36662: Machine.cluster.x-k8s.io "custom-926c73f36662" is invalid: metadata.labels: Invalid value: "jkeslar-maxxx-break-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx": must be no more than 63 characters, requeuing
2022/04/29 18:26:37 [ERROR] error syncing 'c-m-89c4fxmw/custom-926c73f36662': handler unmanaged-machine-secret: failed to create fleet-default/custom-926c73f36662 rke.cattle.io/v1, Kind=RKEBootstrap for unmanaged-machine c-m-89c4fxmw/custom-926c73f36662: RKEBootstrap.rke.cattle.io "custom-926c73f36662" is invalid: metadata.labels: Invalid value: "jkeslar-maxxx-break-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx": must be no more than 63 characters, failed to create fleet-default/custom-926c73f36662 rke.cattle.io/v1, Kind=CustomMachine for unmanaged-machine c-m-89c4fxmw/custom-926c73f36662: CustomMachine.rke.cattle.io "custom-926c73f36662" is invalid: metadata.labels: Invalid value: "jkeslar-maxxx-break-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx": must be no more than 63 characters, failed to create fleet-default/custom-926c73f36662 cluster.x-k8s.io/v1beta1, Kind=Machine for unmanaged-machine c-m-89c4fxmw/custom-926c73f36662: Machine.cluster.x-k8s.io "custom-926c73f36662" is invalid: metadata.labels: Invalid value: "jkeslar-maxxx-break-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx": must be no more than 63 characters, requeuing
2022/04/29 18:26:37 [ERROR] error syncing 'c-m-89c4fxmw/custom-926c73f36662': handler unmanaged-machine-secret: failed to create fleet-default/custom-926c73f36662 rke.cattle.io/v1, Kind=RKEBootstrap for unmanaged-machine c-m-89c4fxmw/custom-926c73f36662: RKEBootstrap.rke.cattle.io "custom-926c73f36662" is invalid: metadata.labels: Invalid value: "jkeslar-maxxx-break-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx": must be no more than 63 characters, failed to create fleet-default/custom-926c73f36662 rke.cattle.io/v1, Kind=CustomMachine for unmanaged-machine c-m-89c4fxmw/custom-926c73f36662: CustomMachine.rke.cattle.io "custom-926c73f36662" is invalid: metadata.labels: Invalid value: "jkeslar-maxxx-break-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx": must be no more than 63 characters, failed to create fleet-default/custom-926c73f36662 cluster.x-k8s.io/v1beta1, Kind=Machine for unmanaged-machine c-m-89c4fxmw/custom-926c73f36662: Machine.cluster.x-k8s.io "custom-926c73f36662" is invalid: metadata.labels: Invalid value: "jkeslar-maxxx-break-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx": must be no more than 63 characters, requeuing
2022/04/29 18:26:37 [ERROR] error syncing 'c-m-89c4fxmw/custom-926c73f36662': handler unmanaged-machine-secret: failed to create fleet-default/custom-926c73f36662 rke.cattle.io/v1, Kind=RKEBootstrap for unmanaged-machine c-m-89c4fxmw/custom-926c73f36662: RKEBootstrap.rke.cattle.io "custom-926c73f36662" is invalid: metadata.labels: Invalid value: "jkeslar-maxxx-break-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx": must be no more than 63 characters, failed to create fleet-default/custom-926c73f36662 rke.cattle.io/v1, Kind=CustomMachine for unmanaged-machine c-m-89c4fxmw/custom-926c73f36662: CustomMachine.rke.cattle.io "custom-926c73f36662" is invalid: metadata.labels: Invalid value: "jkeslar-maxxx-break-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx": must be no more than 63 characters, failed to create fleet-default/custom-926c73f36662 cluster.x-k8s.io/v1beta1, Kind=Machine for unmanaged-machine c-m-89c4fxmw/custom-926c73f36662: Machine.cluster.x-k8s.io "custom-926c73f36662" is invalid: metadata.labels: Invalid value: "jkeslar-maxxx-break-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx": must be no more than 63 characters, requeuing
2022/04/29 18:26:37 [ERROR] error syncing 'c-m-89c4fxmw/custom-926c73f36662': handler unmanaged-machine-secret: failed to create fleet-default/custom-926c73f36662 rke.cattle.io/v1, Kind=RKEBootstrap for unmanaged-machine c-m-89c4fxmw/custom-926c73f36662: RKEBootstrap.rke.cattle.io "custom-926c73f36662" is invalid: metadata.labels: Invalid value: "jkeslar-maxxx-break-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx": must be no more than 63 characters, failed to create fleet-default/custom-926c73f36662 rke.cattle.io/v1, Kind=CustomMachine for unmanaged-machine c-m-89c4fxmw/custom-926c73f36662: CustomMachine.rke.cattle.io "custom-926c73f36662" is invalid: metadata.labels: Invalid value: "jkeslar-maxxx-break-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx": must be no more than 63 characters, failed to create fleet-default/custom-926c73f36662 cluster.x-k8s.io/v1beta1, Kind=Machine for unmanaged-machine c-m-89c4fxmw/custom-926c73f36662: Machine.cluster.x-k8s.io "custom-926c73f36662" is invalid: metadata.labels: Invalid value: "jkeslar-maxxx-break-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx": must be no more than 63 characters, requeuing

Ticket needs to be transferred to rancher/rancher


Fix indentation in makefile

@sebastienvas: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
d344f7c5287f68be919288ceda01f533e3bdfd7a
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sebastienvas: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
d344f7c5287f68be919288ceda01f533e3bdfd7a
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
d344f7c5287f68be919288ceda01f533e3bdfd7a
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sebastienvas: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
d344f7c5287f68be919288ceda01f533e3bdfd7a
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
d344f7c5287f68be919288ceda01f533e3bdfd7a
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
d344f7c5287f68be919288ceda01f533e3bdfd7a
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sebastienvas: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
d344f7c5287f68be919288ceda01f533e3bdfd7a
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
d344f7c5287f68be919288ceda01f533e3bdfd7a
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
d344f7c5287f68be919288ceda01f533e3bdfd7a
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests-v1alpha3.sh
d344f7c5287f68be919288ceda01f533e3bdfd7a
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

tee was failing because the test dir was not being created.

@sebastienvas: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
d344f7c5287f68be919288ceda01f533e3bdfd7a
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
d344f7c5287f68be919288ceda01f533e3bdfd7a
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests-v1alpha3.sh
d344f7c5287f68be919288ceda01f533e3bdfd7a
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-unit-tests.sh
655de0e050d2e71e5ac38da87dbd4472ca6b9b4e
link
/test istio-unit-tests

prow/e2e-simpleTests.sh
655de0e050d2e71e5ac38da87dbd4472ca6b9b4e
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sebastienvas: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
d344f7c5287f68be919288ceda01f533e3bdfd7a
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
655de0e050d2e71e5ac38da87dbd4472ca6b9b4e
link
/test e2e-simple

prow/istio-pilot-e2e.sh
655de0e050d2e71e5ac38da87dbd4472ca6b9b4e
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sebastienvas: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
655de0e050d2e71e5ac38da87dbd4472ca6b9b4e
link
/test e2e-simple

prow/istio-pilot-e2e.sh
655de0e050d2e71e5ac38da87dbd4472ca6b9b4e
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
655de0e050d2e71e5ac38da87dbd4472ca6b9b4e
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sebastienvas: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
69394c80087672ed2a5df207da8f0761106b1122
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
69394c80087672ed2a5df207da8f0761106b1122
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sebastienvas: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
69394c80087672ed2a5df207da8f0761106b1122
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
c257f4b3b536368e23225e611797544aa752b248
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sebastienvas: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
c257f4b3b536368e23225e611797544aa752b248
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sebastienvas: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
b40b021be9ae98159d23af3e24d3023437c35c3c
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


⚠ St. Lawrence Global Observatory CKAN Sitemap has degraded performance

In c5b469d, St. Lawrence Global Observatory CKAN Sitemap (https://catalogue.ogsl.ca/sitemap/sitemap-1.xml) experienced degraded performance:

HTTP code: 200
Response time: 16527 ms

Resolved: St. Lawrence Global Observatory CKAN Sitemap performance has improved in c166b31 after 13 minutes.


Css issue after enabling v2 page cache module

I have followed all the steps as mentioned in https://github.com/budgetneon/v2pagecache.
When cache module is disable, everything works fine. But when i enable cache module, there is some problem with css in front end. I have attached screenshot for both of this cases.

Initially my site loooks as shown in image1.png i.e. When cache module is disable.
But when i enable cache module , my site looks as shown in image2.png.
Please help us.

I"m afraid I can't help much just looking at a screenshot.
If you have a live site that's currently having a problem, I could look.

Here is the link: http://yieldnotion.com/demos/trendvia/
Right now caching module is enabled.
Please check it.

Unfortunately, that didn't help much.   I don't see any notable errors.  I also don't see the time stamp at the bottom of the source that would indicate the page cache is on.  There's likely something about that theme, or some other plugin you're running that doesn't work well with the page cache.
Most often, the fix is to manually add some pattern to the $skip_urls array, denoting a url that you want the page cache not to fix.
Whatever the issue is, it doesn't appear to be something I can help with remotely.

Closing this.   The pagecache works with the default theme.   3rd party themes require work to research what urls should not be cached and subsequent changes to the configuration.

But how to decide which urls to be cached and which ones not. ?
--
Sincerely,
Parth Joshi
Startup Techno - Consultant | Corporate Trainer
parthjoshi.in | LinkedIN | Twitter | (M) +91 98252 95947
Sent from my iPhone

On 28-Jan-2016, at 8:31 PM, Budget Neon<EMAIL_ADDRESS>wrote:
Closing this. The pagecache works with the default theme. 3rd party themes require work to research what urls should not be cached and subsequent changes to the configuration.
—
Reply to this email directly or view it on GitHub.

You would need someone with some web developer level expertise to debug the problem and fix it.   We don't sell this module, and cannot devote time on how to figure that out for the various third party themes, sorry.


Fix test fails in windows PC

All Submissions:

[x] Have you followed the guidelines stated in CONTRIBUTING.md file?
[x] Have you checked to ensure there aren't any other open Pull Requests for the desired changed?

Description
Test output have fails releted windows routing.
I change route string and set TestState as not test class.

I rebase on the current main branch and change line breaks.
Please check this again.


Accessing gtag instance out of component

Hi, thanks for sharing :heart:
My question:
In an component controller, you can access lib instance by this.$gtag documented here, but what if I want to track outside component? Like in a service?
I need it to get clientId like documented here
gtag('get', 'UA-XXXXXXXX-Y', 'client_id', (clientID) => {
  // I have clientID here
});

I was trying following:
  const vueInstance = new Vue();
  vueInstance.$gtag.query('get', 'UA-XXXXXXXX-Y', 'client_id', (clientID: string) => {
    console.log("---------->", clientID);
  });

nothing happen, but query seems not to be the right method, so I tried calling directly:
  const vueInstance = new Vue();
  vueInstance.$gtag('get', 'UA-XXXXXXXX-Y', 'client_id', (clientID: string) => {
    console.log("---------->", clientID);
  });

but it says it is not callable, so neighter of them worked
How can I do it with vue-gtag? :pray:
I need it to put it into header for API calls, for further use on back-end. Thanks

Hi @luckylooke all features available in your component scope are also directly available as separate exported methods.
import { event, pageview } from 'vue-gtag';

event('my_event', {...})

Is this what you needed?

@MatteoGabriele I know that they are exported, but "get" is missing :man_shrugging:
Module '"vue-gtag"' has no exported member 'get'. Did you mean to use 'import get from "vue-gtag"' instead?ts(2614)

neither gtag method
Module '"vue-gtag"' has no exported member 'gtag'. Did you mean to use 'import gtag from "vue-gtag"' instead?ts(2614)

Could you share which version you are currently using?
get is not an API method I have included and also is not the default export, so you need to use the brackets.
In any case, you can use query.
To make an example, here, I have installed vue-gtag and immediately used query to get the client_id. You can use those methods everywhere. You don't need a Vue file. The only important part is first to install the Vue plugin.
import Vue from 'vue'
import App from './App.vue'
import VueGtag, { query } from 'vue-gtag'

Vue.use(VueGtag, {
  config: {
    id: 'UA-12345678-9'
  }
})

query('get', 'UA-12345678-9', 'client_id', (value) => {
  console.warn(value)
})

new Vue({
  render: h => h(App),
}).$mount('#app')

It seems I am using latest<EMAIL_ADDRESS>but typescript interface seems to be outdated then, or unfinished
    interface Gtag {
      (command: 'config', targetId: string, config?: ControlParams | EventParams | CustomParams): void;
      (command: 'set', config: CustomParams): void;
      (command: 'js', config: Date): void;
      (command: 'event', eventName: EventNames | string, eventParams?: ControlParams |  EventParams | CustomParams): void;
    }

When I suppresed ts error by uding "any" I have got the result, thanks :pray:
  (query as any)('get', config.gtag, 'client_id', (clientID: string) => {
   console.log('clientID', clientID)
 });


Specifying 'socksProxy' requires an integer for 'socksVersion'

Hello! I see (and hope) you plan to maintain this. I've create an issue on another fork but.. that guy doesn't care so there is no point to insist there.
I've take your fork and I see you have the same issue with the socks proxy, could you please add the following:
struct SocksProxy : ManualProxy { // copyable
	explicit SocksProxy(const std::string& address) { SetProxyAddress(address); }

	WEBDRIVERXX_PROPERTIES_BEGIN(SocksProxy)
	WEBDRIVERXX_PROPERTY(ProxyAddress, "socksProxy", std::string)
	WEBDRIVERXX_PROPERTY(Username, "socksUsername", std::string)
	WEBDRIVERXX_PROPERTY(Password, "socksPassword", std::string)
	**WEBDRIVERXX_PROPERTY(ProxyVersion, "socksVersion", int)**
	WEBDRIVERXX_PROPERTIES_END()
};

Then we can use:
SocksProxy("").SetProxyVersion(5)
This problem appears with chrome driver.
org.openqa.selenium.InvalidArgumentException: invalid argument: entry 0 of 'firstMatch' is invalid
from invalid argument: cannot parse capability: proxy
from invalid argument: Specifying 'socksProxy' requires an integer for 'socksVersion'
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'

However, afterwards I get the same crash.... https://prnt.sc/spe5bm
Could you give a hand ?
Thanks

SOLUTION HERE:
https://github.com/GermanAizek/webdriverxx/issues/14#issuecomment-816971664


Compilation help needed

Trying to compile the project results in:

error: failed to run custom build command for glutin_egl_sys v0.1.5`
Caused by:
could not execute process B:\Coding\WarthunderLocalsTool\wt_custom_lang-master\target\release\build\glutin_egl_sys-7ca3419910a611cb\build-script-build (never executed)
Caused by:
%1 is not a valid Win32 application. (os error 193)
warning: build failed, waiting for other jobs to finish...`

cargo v1.73.0
rustup v1.26.0
rustc v1.73.0

Could be that the egui dependency is outdated

Attempting to update Egui causes many breaking API changes which would need to be accounted for, however, i dont have enough time to continue maintaining this project.
I might consider picking up this project some time in the future when i can, though i would still be open to reviewing and merging pull requests.

I am not familiar with the Rust language or its package managers.
Trying with different versions of rustup (1.73.0, 1.26.0, 1.25.0) yields the same results.
Running cargo update does not fix things either.
In theory it should compile using the exact versions of dependencies that you used back in Jan 2022 however how to force it to do that is beyond my knowledge.
I will leave it up to your discretion  to close/leave this issue open.


This release includes permissions that haven't been declared in Play Console

Describe the bug
This release includes permissions that haven't been declared in Play Console. Go to Sensitive app permissions to update your permission declarations. Learn more
Error
You need approval to use the following Health Connect permissions in your app:
android.permission.health.READ_ACTIVE_CALORIES_BURNED
android.permission.health.READ_HEART_RATE
android.permission.health.READ_STEPS
android.permission.health.READ_DISTANCE
android.permission.health.READ_FLOORS_CLIMBED
To Reproduce
While uploading app bundle to play store
Expected behavior
A clear and concise description of what you expected to happen.
Environment:

Health Connect Version: 1.1.0
React Native Version: 0.72.4
New architecture enabled: No

@matinzd  Please help me this one. thanks in advance

Please read here: https://developer.android.com/health-and-fitness/guides/health-connect/publish/request-access

Google’s review process is beyond broke.  Good luck.


Can't use delete key in other inputs on page

When color pickers are present and one of them is set to gradient mode, the delete key on other inputs in the page stops working. Moving all color pickers into their own component did not resolve the issue.
When i press 'delete' in another input under these conditions the onChange event doesn't fire. Entering new characters works fine.

when i press 'delete' in another input under these conditions the onChange event doesn't fire

Fixed in V2.1.17

@hxf31891
In V2.1.7, pressing the delete key while in another input now correctly deletes text in that input but also now deletes gradient stops if there are more than 2.

Alright I'm going to do a little deeper dive into this, will update you soon.

Ok I feel like v2.1.9 is finally going to get solid behavior here. The gradient points now accept focus like an input does which should eliminate the bugs you've been describing which seem to stem from cross interaction between those two elements.
I've tested it pretty thoroughly but I would very much appreciate if you could detail any issues you find here. I am uncertain about the functionality specifically on Next so if thats part of your environment let me know how it looks.

Closing with assumption this is fixed in 2.1.9


Adding framerate graph module

People keep wanting to use this graph so I figured I would add it as an actual module so at the very least we have an easy and official way to maintain it.  Renamed from RuntimeProfiler to FramerateGraph because it is not really a profiler at all, just a graph of framerate.

Will make name fixes

Ok names are fixed


Bug: Error handling in listIntroductionPeers(pagination: Pagination?) function

Describe the bug
While debugging, an error log was noticed that originates from the listIntroductionPeers(pagination: Pagination?) function in the Conversations class. The error is caught and printed, but not rethrown, which prevents it from being handled by the client. This issue is to discuss whether this behavior is expected and if any changes are needed.

Steps to reproduce the bug
The error is triggered when calling Conversations.list(). The error message is
"Loading introduction from peers: queryError("query")".
The relevant code is in the listIntroductionPeers(pagination: Pagination?) function:
Sources/XMTP/Conversations.swift startLine: 247 endLine: 273

Closing, as intended -- if there’s bad data in an introduction message then we don’t want to break loading the rest of the introduction messages. Will reopen if this logic creates any issues.


Replace the FontStyle and FontFeature Rust types with the Protobuf implementations

Why were we converting the font features to a byte array and then back to a string? Either way, it needed to change one way or another because you can't have protobuf arrays with a specified size.

@timothyfroehlich could explain what the problem with the italic text was? Also, do you know why the dial&gauge test is failing?

@timothyfroehlich could explain what the problem with the italic text was? Also, do you know why the dial&gauge test is failing?

The problem was that the FontStyle enum shifted by one. 0 was Normal and 1 was Italics, but now 0 is Unspecified, 1 is Normal and 2 is Italics. I hadn't updated the DCF for HelloWorld so it was deserializing the DCF where FontStyle was 1, and with this update, 1 is now Normal.
One mitigation would have been to bump the number of the DCF version, so that old DCFs would be rejected, but that seemed unnecessary for a small change like this that will be followed by other changes.

@rylin8 Also, do you know why the dial&gauge test is failing?
Hadn't updated the screenshots.

@yiqunw700's change just went in so you'll have to update all the .dcf files

@yiqunw700's change just went in so you'll have to update all the .dcf files

Yeah. Sorry about the conflicts. 😿


vars should be able to take non-flat values

What happened?
Usecase: We are trying to create EKS Cluster using Crossplane and to create multiple Node-groups/launch-templates we are using terraform-provider to dynamically read the details from the claim.yaml
claim.yaml
kind: ManagedCluster
metadata:
  namespace: crossplane-system
  name: eks-cluster
parameters:
    region: us-east-2
    version: "1.21"
    nodeRole: arn:aws:iam::xxxxx:role/eksNodeRole
    nodeGroups:
      - desiredSize: 2
        maxSize: 2
        minSize: 2
        instanceType: m5.4xlarge
        label: fruit=apple
        volumeSize: 150
      - desiredSize: 1
        maxSize: 1
        minSize: 1
        instanceType: m5.4xlarge
        label: fruit=banana
        volumeSize: 80

As per current behavior, terraform-provider gives 2 options to pass variables - vars & varFiles.
varFiles supports data in HCL or JSON format.
vars support data in plain string - flat values only.
What environment did it happen in?
Crossplane version: 1.10.1
provider-terraform: 0.2.0
Kubernetes: 1.23
Solution could be to enhance vars to take non-flat values as input & internally convert to HCL/JSON to pass to terraform-provider.

Hey @ytsarev , when do we expect a new release with this feature available?


incorrect time to expire codes

🐛 Bug Report
In the current implementation the following incorrect behavior occurs:
some embedding was not chosen in the previous steps so it will be expired here, but it was chosen right on that step a couple lines above, but since self.cluster_size will be changed only in following lines, this embedding will be expired, but it should not.
This can be easily checked by adding these 2 lines
expared_but_taken = (self.cluster_size < self.threshold_ema_dead_code) & (embed_onehot.sum(0) > 0)
assert torch.any(expared_but_taken).
somewhere here
I think the correct code should be like in vector-quantize-pytorch repo, namely this line.

the expiring of the codes was moved to before the selection in order to solve inconsistent decisions between gpus, which would happen otherwise. In fact the lucidrains implementation was not distributed proof at the time we forked it, that is the reason for this change we did. While I agree this can lead to sub-optimal behavior in some cases (although expiration shouldn't happen too often), it makes the code simpler by not requiring further synchronization inside the VQ module.


"All Rights Reserved"

The LICENSE file claims MIT, however all the source files include the following:

Copyright (c) 2014, OneLogin, Inc.
All rights reserved.

Please update the source file headers to include the license text, and not say "All rights reserved" to clarify. The year should likely be updated as well to include all the years in which code was committed (and thus published) under this copyright.
This same issue also affects python-saml tree.

Noted, we will review


Date picker minute interval isnt working

datePickerCell.datePicker.minuteInterval = 30 doesn't change anything. It will set the value, but the UI doesnt change.

KHAFromViewController.swift, add cell.datePicker.minuteInterval = dateCell.datePicker.minuteInterval after line 116
https://github.com/EliteInstructorsInc/KHAForm.git


Translate doc proxies into chinese

chinese doc translation
and fix incorrect links
fixes #4052
/cc @zhangxiaoyu-zidif

This change is

@zjj2wry updated :)

LGTM


Wish: Include option to change ToDSType() to True

@dimven Wish for the FamilyInstance.ByGeometry node to have an additional input for setting the ToDSType to True. I saw here: https://forum.dynamobim.com/t/circumvent-revit-object-replacement/7459/9 that we can use this to circumvent the element binding and create  familyinstances from multiple runs without deleting the previous. In some cases users find this way of working suitable and most effective.

Could you provide an example workflow, where this would be useful ?

in some cases users find it easier to work like this: 1. Select faces, elements, edges etc etc. 2.Create some new geometry 3. name it 4.create family instance, 5. start over and repeat

From my experience, that option is very likely to introduce instability in the dynamo graph (duplicate elements being created on top of each other in a single run, dynamo crashing or freezing). Have you experienced something similar?
Closing the graph, without saving it, and then reopening and re-running it again to create new elements, is much more reliable.


Add Porsche Design System to componentLibraries

What I did
Hi, I'd like to introduce the Porsche Design System component library to the Community: Component Libraries list under https://open-wc.org/guides/community/component-libraries/ which is based on Web Components.

Porsche Design System provides developers with versioned packages of Web components, Angular components, React components and Vue components to build clean and high-quality frontends that innately come with the latest design definitions.

https://designsystem.porsche.com/

If I merge this, will we get a discount on a porsche?

If I merge this, will we get a discount on a porsche?

You could try PORSCHE10 but I make no guarantees 😆
Thanks for merging! 💯

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Invalid BASE price

This is my configuration file:
[main]
node = http://nodes.wavesnodes.com
# select the network: testnet or mainnet
network = mainnet
matcher = http://matcher.wavesnodes.com
order_fee = 300000
order_lifetime = 86400

[account]
private_key = my private key

[market]
amount_asset = WAVES
price_asset = mypriceid

[grid]
interval = 0.005
tranche_size = 200000000
grid_levels = 20
# base price calculation: LAST, BID, ASK, nnnnn (fixed constant price)
base = last
# amount flexibility in percent, 20% flexibility means that the amount of the order might flucture +/- 10% around the defined tranche_size
flexibility = 20
# grid type: SYMMEMTRIC, BIDS only, ASKS, only
type = symmetric

[logging]
logfile = bot.log

Out put when set base = LAST
[Jan 15 2020 07:02:03 UTC] :    Price Asset ID : XXXXXXXXXXXXXXXXXXXXXXXXXXXX
[Jan 15 2020 07:02:03 UTC] : --------------------------------------------------------------------------------
[Jan 15 2020 07:02:03 UTC] :
[Jan 15 2020 07:02:04 UTC] : Cancelling open orders...
[Jan 15 2020 07:02:05 UTC] : Deleting order history...
[Jan 15 2020 07:02:06 UTC] :
[Jan 15 2020 07:02:06 UTC] : Invalid BASE price
[Jan 15 2020 07:02:06 UTC] : Exiting.

Could any help possible?

That is because you have a new wallet without any orders. Either make an order or change the base property to BID or ASK instead of LAST


[enhancment] Enable non-silent install

When you install something with winget, winget downloads the installer and runs it silently. But I think it will  be good if there was an option to run it non-silently (like you would just execute the exe,msi,etc... from file explorer). It can be a flag, for example winget install Microsoft.dotnet --non-silent.

I believe this would be winget install —interactive that is a current existing flag.
But it is seems not yet supported from the spec
https://github.com/microsoft/winget-cli/blob/master/doc/ManifestSpecv0.1.md
Relates to #365 too.

@Yavor-aaa there is a bug as @cderv points out. We have been looking at either Silent or SilentWithProgress as the default install mode selected by the client. This feature could represent the ability to change the default client configuration if you like.

To me this issue is really just a copy of #365 and should be closed to avoid more duplication.

To me this issue is really just a copy of #365 and should be closed to avoid more duplication.

Okay, closing.


[AVM Module Issue]: App Configuration does not output endpoint

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Issue Type?
Feature Request
Module Name
avm/res/app-configuration/configuration-store
(Optional) Module Name if not listed above
No response
(Optional) Module Version
0.1.1
Description
Many operations (including, for example, creating a new app configuration settings) require the "endpoint".  Output the endpoint property of the app configuration resource.
(Inbound - will do a PR for this)
(Optional) Correlation Id
No response

This module is currently orphaned: https://github.com/Azure/Azure-Verified-Modules/issues/731

@jongio for notification.

@adrianhall We have created a PR for this issue. Please review.

PR link: https://github.com/Azure/bicep-registry-modules/pull/2586


Ability to edit a todo

Component state, adds ability to edit a todo.
Fixes #175

@steida need any help with that? Can change / refactor some bits if they do not match the overall app guidelines.

No, thank you. Will review and merge asap.

So with the new approach against using local state (still not a big fun of it), maybe we can modify it + add some goodies mentioned in your latest issue?

Yes we will, but wait for pure refactor please. Hopefully I made it today.

Check my implementation. Feel free to suggest any improvement.


how to build client-go

I am a newbie to Go. I cloned the client-go repo. Now what should I type into my shell to make this thing compile?
Actually I want to try to compile client-go into a shared C library as explained here:
https://medium.com/learning-the-go-programming-language/calling-go-functions-from-other-languages-4c7d8bcc69bf
But for that of course I first need to understand how to build it the normal way.

The client is normally statically linked and not built separately (although
you can build the examples).
If you just cloned the repo, you will need to set up your GOPATH before the
import paths will work.
I do not recommend doing the thing you are trying to do, though. Our
library is full of interfaces and objects to make it convenient to build
requests for go users. A consequence of this is that you will be writing
vast amounts of boilerplate function signature code if you want to use it
from C.
On Fri, Jun 9, 2017 at 2:01 AM, Thomas Koch<EMAIL_ADDRESS>wrote:

I am a newbie to Go. I cloned the client-go repo. Now what should I type
into my shell to make this thing compile?
Actually I want to try to compile client-go into a shared C library as
explained here:
https://medium.com/learning-the-go-programming-language/
calling-go-functions-from-other-languages-4c7d8bcc69bf
But for that of course I first need to understand how to build it the
normal way.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/client-go/issues/205, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAnglulLr7fQj-w2_10KfX7fQ7nzuBb7ks5sCQncgaJpZM4N1FgT
.


Help with ChooseDatabaseAtLogon functionality

Question
I wanted to set the ChooseDatabaseAtLogon functionality properly, but I'm stuck on some things.
I currently added the XpandSecurityModule in a basic application to make sure the mistake is not in our application. This isn't really working out. I have been debugging it and it turns out that when logging in, the connection string isn't set eventhough i selected a connection string from the lookup listview.
My question is: how to do it the right way?
Additional context
I have made a simple demo to demonstrate this. I added a SQLite database already, so you can immediately test. The username is admin and there is no password.
XafTestApp.zip

u need a default connection string to be used unitl login (no db is created yet) and also change thisline
e.ObjectSpaceProviders.Add(new XPObjectSpaceProvider(new ConnectionStringDataStoreProvider(ConfigurationManager.ConnectionStrings["LogonDBServerDefault"].ConnectionString)));

<add name="LogonDBServerDefault" connectionString="Integrated Security=SSPI;Pooling=false;Data Source=(localdb)\mssqllocaldb;Initial Catalog=SecurityTesterEasyTesta" />
    <add name="ConnectionString" connectionString="Integrated Security=SSPI;Pooling=false;Data Source=(localdb)\mssqllocaldb;Initial Catalog=SecurityTestera" />
    <add name="LogonDBServerDB1" connectionString="Integrated Security=SSPI;Pooling=false;Data Source=(localdb)\mssqllocaldb;Initial Catalog=SecurityTesterEasyTest1a" />
    <add name="LogonDBServerDB2" connectionString="Integrated Security=SSPI;Pooling=false;Data Source=(localdb)\mssqllocaldb;Initial Catalog=SecurityTesterEasyTest2a" />

Alright, thanks. Clear answer.

forgot to mention there is a win version for this controller

I saw, but it didn't add anything to the question, so I left that out.


Skill Name
FrankenPHP
Why?
Popular PHP app server
Reference Image

Code of Conduct Acknowledgment

[X] I have read and agree to the Code of Conduct.

Svg Logo:

@sckoorp I found better quality svg icon

@sckoorp I found better quality svg icon

aight thanks <3


CMS: Add duplicate buttons in ACL editor

Add duplicate buttons as indicated below

Instead of a button, i added an Icon which hide when are changes and show are not. @laurensgroeneveld Helps me to write tests for that.
Now i have to add a duplicate icon or button on the ACL.

@belljohan3 please have a look at the colour of the duplicate button? It feels a bit different from the other icons. Should it perhaps be the same colour as the "group" icon that is displayed to the left of the group name?

@ivanslabbert I agree, it was kind of deliberate to focus a bit more on the functionality and leave nicer styling for a follow-up PR. I created a small one to add a specific variant for this button that also removes the padding, which is a thing we ran into when adding the duplicate button for the individual ACLs. See https://github.com/bccsa/luminary/pull/144
Would love to hear what you think @belljohan3.

Hei @ivanslabbert and @laurensgroeneveld ! I read what wrote. Now, what should i do ?


Sql Server restore output

I'm running a RESTORE command at Sql Server 2008 .
At SSMS when run commands like the restore they show output with the percentage of the amount processed during they execution.
At the dbeaver 5.3.5 with the last microsoft driver (github) they show only when finished.
Is there some setting to enable this output for SQL Server statements "online" ?

is it still actual for you?

I will check in a couple of days and give feedback here.

Hi,
Short answer: yes.
I tested again, using dbeaver 7.0.4 and and mssql-jdbc-7.4.1.jdri8.jar .
Keep with the same behavior.
Never tested with newer SQL Server since I have no one here to test... so, this is with version 2008R2
RESTORE DATABASE [ab] FROM
  DISK = N'\\server\ab$\ab.bak'
  WITH  FILE = 1,
  move 'ABData'    TO 'E:\Databases\AB\AB.mdf'
 ,REPLACE
 ,NOUNLOAD,  STATS = 1

@uslss , you labeled to x:oracle, should be x:mssql .
btw, I ran this again, now using jdbc 8.2.2 with dbeaver v7.1.1 on SQL server 2008r2 and the problem still occurs.

thanks for your comment, I changed the label.
Also thanks, for checking :)

I think this may be related to a more general issue.
When you issue a print or raiserror statement in T-SQL, the output is buffered for the duration of the script execution.  Once the script has completed, the buffered data is sent to the client.
However, if you use raiserror(...) with nowait, per MS documentation

NOWAIT  Sends messages immediately to the client.

What with nowait actually does in practice is to send all the currently buffered information to the client.  For instance, if you run the following script in SSMS, you will see messages 1-3 immediately (rather than just message 3), and then three seconds later you'll see the last message:
print 'message 1';
raiserror('message 2',0,1);
raiserror('message 3',0,1) with nowait;

waitfor delay '00:00:03';

print 'last message';

If you comment out the with nowait in the above script and run it in SSMS, there will be a three second delay and then all four messages will be displayed.
I suspect that the restore command uses the same mechanisam as with nowait to send progress information during its execution.
DBeaver, however, doesn't seem to append that information to the Server Output window until after the script completes.
I frequently use raiserror(...) with nowait statements so I can track the progress of long-running processes.  Running such scripts in DBeaver is frustrating because those progress messages are not displayed until script completion, which negates their usefulness.

I also have this problem...


Create packrat logo for README

I suggest @TheThirdOne make a sloth.
On Wed, Sep 23, 2015 at 2:48 PM, Max Wofford<EMAIL_ADDRESS>wrote:

—
Reply to this email directly or view it on GitHub
https://github.com/hackedu/packrat/issues/13.

--
Zach Latta
hackEDU |<EMAIL_ADDRESS>

A rat sloth.

On Wed, Sep 23, 2015 at 4:04 PM, Max Wofford<EMAIL_ADDRESS>wrote:

A rat sloth.
—
Reply to this email directly or view it on GitHub
https://github.com/hackedu/packrat/issues/13#issuecomment-142756000.

--
Zach Latta
hackEDU |<EMAIL_ADDRESS>

I am not going to make a rat sloth. Try again.

@TheThirdOne A sloth rat?
/cc @zachlatta

I am so in for a sloth rat.

/cc @zachlatta @TheThirdOne

@MaxWofford completed this task!

(#74 closed this)


Fix workday not excluding holidays

Breaking change

Proposed change

Type of change

[ ] Dependency upgrade
[x] Bugfix (non-breaking change which fixes an issue)
[ ] New integration (thank you!)
[ ] New feature (which adds functionality to an existing integration)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

binary_sensor:
  - platform: workday
    country: US
    workdays: [mon, tue, wed, thu, fri]
    excludes: [holiday]
  - platform: template

Additional information

This PR fixes or closes issue: fixes #31034
This PR is related to issue:
Link to documentation pull request:

Checklist

[x] The code change is tested and works locally.
[x] Local tests pass. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist
[x] The code has been formatted using Black (black --fast homeassistant tests)
[x] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly.
Updated and included derived files by running: python3 -m script.hassfest.
[x] New or updated dependencies have been added to requirements_all.txt.
Updated by running python3 -m script.gen_requirements_all.
[x] Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

[ ] No score or internal
[ ] 🥈 Silver
[ ] 🥇 Gold
[ ] 🏆 Platinum

Hi @penright,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Let me learn a little more.
Also, I am creating this fix for my fork.


Removing upstatement/router as a dependency

Expected behavior
We are currently writing our own router package to use instead of upstatement's router (which supports named routes and route groups. - still alpha atm). It has a dependency on Altorouter too, but because we are using timber we are limited to using Altorouter at v1.1.0 - due to timber requiring upstatement's router.
I'm wondering if Timber has a hard requirement on upstatement's router, or whether it's been included for convenience / backwards compatibility? Are there any plans to remove the dependency?
What version of WordPress, PHP and Timber are you using?
Timber 1.3.4 - installed via composer

Indeed, I feel indebted to the backwards compatibility of it being there from the start. I'm planning on removing that in 2.x. Are there any temporary workarounds that are worth considering?

FYI, our Router is now stable and ready for use if this is of interest. As @adamtomat mentioned, it still uses AltoRouter under the hood but gives a more expressive API, along with PSR compliant support for Message objects (requests/responses) and Middleware.
https://github.com/Rareloop/router

I do agree that we should make Routing optional. Most problems that I see people trying to solve with routing can be solved with what WordPress already offers – even without having to update rewrite rules.
I’m adding this to the list for 2.x:

[ ] Remove Composer dependency upstatement/routes in 2.x.
[ ] Move content from Routing Guide over to Upstatement/routes.
[ ] Replace Routing Guide content with hint about why routing was disabled by default and a list of Routing libraries that can be used if routing should be required, like Rareloop/router, or still Upstatement/routes.

A pull request should be made against the 2.x branch.

The relevant pull request #1869 was merged. As of Timber 2.x, routing is optional.
If somebody has more routing libraries that work with Timber and that we could add to the documentation: pull requests are welcome!

Is it something that could be "backported"(?) to 1.x ?
upstatement/routes has, itself, some other dependencies and it seems it's not needed in the context of WordPress.

@drzraf I think this is something that we can only support for 2.x going forward. We want to be as as carful as possible to limit any breaking changes we introduce in 1.x. I totally agree with you in spirit, but we've felt a lot of (unexpected) pain/fallout for pulling deprecated functionality


STYLE: Convert a tab indent into spaces in BuildHeaderTest.py

PR Checklist

[x] No API changes were made (or the changes have been approved)
[x] No major design changes were made (or the changes have been approved)

I am the one who introduced it. I might have not spotted it, had I not looked at it in a different editor 😄
People very rarely look at that file, and there was not a lot deprecation-related changes recently.

Oh, and I was looking at it when trying to solve VNL warning. It turned out I was barking at the wrong tree, as the solution was VNL-specific.


Attempt to demonstrate ruby_package option failing to generate services properly when importing request/response messages

As mentioned in this mailing list thread, this PR attempts to demonstrate what appears to be mishandling of the ruby_package option for imported message types used as request/response message types when generating the service files.
Given a protobuf file defining request and response messages, specifying the ruby_package option, and a separate protobuf file defining the RPC service, specifying the same ruby_package, importing the messages and using those as the RPC endpoint request and response times.
Example
I've prepared a gist with what should demonstrate this unexpected behavior:
https://gist.github.com/mtodd/cb6c189b2d3dec494c7f81f5f5e288f6
Notice that the generated gRPC service file appears to ignore the configured ruby_package option, resulting in invalid Ruby code.

Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement.
After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.

User @mtodd isn't covered by a CLA. They will need to complete the form at https://identity.linuxfoundation.org/projects/cncf

Regards,
CLA GitHub bot

I think there are a couple of bugs here, one in the grpc-protoc-plugin and one that appears to be in the protoc side of it.

In the grpc-protoc-plugin, I think we should basically be passing package_name rather than file->package() on this line: https://github.com/grpc/grpc/blob/master/src/compiler/ruby_generator.cc#L212, because otherwise, as is currently, we are just ignoring and ruby_package statements from the current file when generating that bit of code. Things appear to be "working" in the non-import case because it looks like this problem is actually "cancelled out" by the next.

cc @TeBoring, when generating a service, I'm finding that, when a service includes a message that was imported from a file containing a ruby_package statement, the ruby_package from that file is appears to be ignored by the MethodDecriptor object. E.g., in https://github.com/grpc/grpc/blob/master/src/compiler/ruby_generator.cc#L44, if MethodDescriptor->input_type()->full_name() has the canonical package name rather than the ruby_package name. Is this expected, or a known issue?

I think the ruby grpc plugin should follow the logic here: https://github.com/protocolbuffers/protobuf/blob/master/src/google/protobuf/compiler/ruby/ruby_generator.cc#L415
The full name from method descriptor is the proto name instead of ruby generated class name.

I'd like to see this merged so I can validate the behavior of the client library from the canonical master branch as well 😸


remove deprecated vscode linting settings

Some settings in our settings.json file have been deprecated by vscode in order to enforce the use of vscode extensions for linters (flake8, mypy and pylint) as well as black autoformatter.
This PR removes those deprecated settings.

I think these changes were incorporated here: #167
Please let me know if there is anything else to do.

@nathan-stender I just reabased main and there's just one setting I changed that was not included: the "${workspaceRoot}/pyproject.toml" line in the "black-formatter.args" setting was preventing changes on the pyproject.toml settings for black to be picked up.


Скласти інтро

Скласти інтро (вступ), де в 2-4 реченнях описати, що замовник робить, що подобається робити, що хочеться робити краще, що важливо робити, тощо.

Considered one of the best street fighters ever, i have been taught the ways of Shotokan karate by my foster father, Sensei Gouken. I surpasse with my inner-mental strength. I am not the polished con-man my friend Ken is, but i am considered a master street fighter. I have won a World Championship crown from Shadaloo Tong Kingpin, Sagat some years ago. Sagat seeks revenge even to this day.

― I do not compete with others, the only competition that challenges me is myself. As a fighter, friend and an employee I am known as contemplative, tortured and driven.

Красиво 0_0

ACHIEVEMENTS
#1 in "Top 25 Street Fighter Characters" by IGN, who also called me "fancy", "icon" and "a testament to the virtue of simplicity" ❤
#2 in "Top 20 Street Fighter Characters of All Time" by GameDaily, same council found me worth of #6 place in "Top 25 Capcom Characters of All Time", which I proudly share with my partner Ken
I was named "5th Most Powerful Street Fighter Character" by Screen Rant-san
#71 in "Top 100 Heroes of All Time" by UGO Networks, also recognized #2 in their list of "Top 50 Street Fighter Characters"
In a survey of 4000 online matches for Super Street Fighter IV, I got to be the most popular character, with 16.6% of players choosing my side
LIFE & EDUCATION
To live is to fight and to fight is to live. I started learning fighting at my master Gouken's castle, I was beaten at head way too often to remember when exactly.


Failure to install on macos Bigsur 11.1

Hi !
On a fresh opam switch 4.11.1 I tried to install memtrace_viewer but the installation failed with
<><> Processing actions <><><><><><><><><><><><><><><><><><><><><><><><><><>  🐫
[ERROR] The compilation of memtrace_viewer failed at "/Users/vsiles/.opam/opam-init/hooks/sandbox.sh build dune build --profile release
        --default-target @install . --root . --cache-transport=direct".

#=== ERROR while compiling memtrace_viewer.v0.14.1 ============================#
# context     2.0.6 | macos/x86_64 | ocaml-base-compiler.4.11.1 | git+https://github.com/ocaml/opam-repository
# path        ~/.opam/4.11.1/.opam-switch/build/memtrace_viewer.v0.14.1
# command     ~/.opam/opam-init/hooks/sandbox.sh build dune build --profile release --default-target @install . --root . --cache-transport=direct
# exit-code   1
# env-file    ~/.opam/log/memtrace_viewer-52259-1872ec.env
# output-file ~/.opam/log/memtrace_viewer-52259-1872ec.out
### output ###
# dyld: Library not loaded: /usr/local/opt/libffi/lib/libffi.6.dylib
# [...]
# /bin/bash: line 1: 61271 Abort trap: 6           ./ffi_types_stubgen.exe > ffi_ml_types_stubgen.c
#         bash vendor/async_ssl/src/ffi_generated_stubs.c (exit 134)
# (cd _build/default/vendor/async_ssl/src && /bin/bash -e -u -o pipefail -c '../stubgen/ffi_stubgen.exe -c > ffi_generated_stubs.c')
# dyld: Library not loaded: /usr/local/opt/libffi/lib/libffi.6.dylib
#   Referenced from: /Users/vsiles/.opam/4.11.1/.opam-switch/build/memtrace_viewer.v0.14.1/_build/default/vendor/async_ssl/src/../stubgen/ffi_stubgen.exe
#   Reason: image not found
# /bin/bash: line 1: 61268 Abort trap: 6           ../stubgen/ffi_stubgen.exe -c > ffi_generated_stubs.c
# File "vendor/async_websocket/src/crypto.ml", line 2, characters 25-40:
# 2 | module CryptokitBignum = CryptokitBignum
#                              ^^^^^^^^^^^^^^^
# Warning 49: no cmi file was found in path for module CryptokitBignum

Indeed, I have .7, not .6:
[vsiles@vsiles-mbp:/usr/local/opt/libffi/lib]
$ ls -al
total 160
drwxr-xr-x   6 vsiles<PHONE_NUMBER>    192 Nov 23  2019 .
drwxr-xr-x  10 vsiles<PHONE_NUMBER>    320 Jan 22 15:47 ..
-r--r--r--   1 vsiles<PHONE_NUMBER>  38344 Sep 21 16:02 libffi.7.dylib
-r--r--r--   1 vsiles<PHONE_NUMBER>  39184 Nov 23  2019 libffi.a
lrwxr-xr-x   1 vsiles<PHONE_NUMBER>     14 Nov 23  2019 libffi.dylib -> libffi.7.dylib
drwxr-xr-x   3 vsiles<PHONE_NUMBER>     96 Sep 21 16:02 pkgconfig

FYI:
$ ocamlc --version
4.11.1
[vsiles@vsiles-mbp:/private/tmp/foo/bar]
$ opam --version
2.0.6

Any idea how to get this right ?
Thanks !

This is related to one of the vendored dependencies. The error is happening in the build of async_ssl and relates to ctypes. Maybe try installing those on your system and see if they fail. If they fail then I suggest trying their bugtrackers, if not report back here and we'll see if we can figure out what is wrong.

This is related to one of the vendored dependencies. The error is happening in the build of async_ssl and relates to ctypes. Maybe try installing those on your system and see if they fail. If they fail then I suggest trying their bugtrackers, if not report back here and we'll see if we can figure out what is wrong.

Good catch ! I get the same error installing async_ssl. I'll report the issue to them. Thanks for the help !

Good catch ! I get the same error installing async_ssl. I'll report the issue to them. Thanks for the help !


Fix scroll buttons disabled/enabled states in the Kiosk mode

I updated updateScrollButtonsState() function so it gets a proper disabled state when locations' length is lower than 8. Number 8 indicates maximum number of locations that are visible in the element without scroll.

Inside Search.jsx, I called newly created function newCategorySelected(). When new category is selected, and all locations to that category are rendered, we need to update disabled/enabled state of scroll buttons.

I performed a lot of scouting.

There's still some naming referring to locations and categories in the scroll buttons web component.

There's still some naming referring to locations and categories in the scroll buttons web component.

How about now @ammapspeople

New changes pushed @ammapspeople

I cleaned up a little bit now and we do not use additional property. We also do not check for length. @ammapspeople

What do you think about it now @ammapspeople ☝


why rotating the camera doesnt work when i use the example in redme ?

its fpscamerabundle that i need, hmm


Prevent read/write displaying system NFC "New tag collected" on Android

As soon as the following lines are called;
await NFC.writeNDEF(payload, once: true).first
and
await NFC.readNDEF(once: true).first;
The NFC is opened back up to the system which then causes an instant read of the tag.  This then causes the "New tag collected" page to be displayed (pixel 3).
Even though we only want to read one tag we're having to stream reading the NFC.  We then pause for a second before cancelling the stream.  Similarly we are having to start reading for 1 second directly after writing to prevent the system "New tag collected" page from being displayed.
Is there a way to detect that the tag has been removed before passing control back to the phone.

I've had a bit of a play about in NfcInFlutterPlugin and for reading put the following lines on line 208 before eventSuccess(formatNDEFMessageToResult(ndef, message)); will set a 1 second delay before being able to read another tag before the previous one is removed.
if (android.os.Build.VERSION.SDK_INT >= android.os.Build.VERSION_CODES.N) {
    adapter.ignore(tag, 1000, null, null);
}

For writing add the following lines after line 623 ndef.writeNdefMessage(message);
if (android.os.Build.VERSION.SDK_INT >= android.os.Build.VERSION_CODES.N) {
    adapter = NfcAdapter.getDefaultAdapter(activity);
    adapter.ignore(lastTag, 1000, null, null);
}

You can implement NfcAdapter.OnTagRemovedListener and add the following if you want to see when the callback is called.  You have to put this into the third parameter on adapter.ignore
@Override
public void onTagRemoved() {
    Log.e(LOG_TAG, "onTagRemoved");
}

see https://developer.android.com/reference/android/nfc/NfcAdapter#ignore(android.nfc.Tag, int, android.nfc.NfcAdapter.OnTagRemovedListener, android.os.Handler)

I've now integrated this code into my application and there is an a problem when writing.  I believe it is caused in the finally block when ndef.close() is called.  So instead of adding the code on line 623, I've added the ignore in the finally block.
try {
	ndef.close();
	if (android.os.Build.VERSION.SDK_INT >= android.os.Build.VERSION_CODES.N) {
		adapter = NfcAdapter.getDefaultAdapter(activity);
		if (adapter != null) {
			adapter.ignore(lastTag, 1000, null, null);
		}
	}
} catch (IOException e) {
	Log.e(LOG_TAG, "close NDEF tag error: " + e.getMessage());
}

@vilvic can you please tell me the solution to prevent "New Tag Collected" on Android?

@vilvic can you please tell me the solution to prevent "New Tag Collected" on Android?

@ghulamsabir5353 you can look at the diff (https://github.com/vilvic/nfc_in_flutter/commit/e668f4c3f266a77cd0761b374690e1bc57e89747)
The problem seemed to be as soon as you write the tag it immediately tries to read the tag.  You'll notice I added the following lines of code.
            if (android.os.Build.VERSION.SDK_INT >= android.os.Build.VERSION_CODES.N && !writeIgnore) {
                adapter.ignore(tag, ONE_SECOND, this, null);
            }

This signals that you are no longer interested in communicating with an NFC tag for as long as it remains in range.  See the document here... https://developer.android.com/reference/android/nfc/NfcAdapter#ignore(android.nfc.Tag, int, android.nfc.NfcAdapter.OnTagRemovedListener, android.os.Handler)

@ghulamsabir5353 you can look at the diff (https://github.com/vilvic/nfc_in_flutter/commit/e668f4c3f266a77cd0761b374690e1bc57e89747)
The problem seemed to be as soon as you write the tag it immediately tries to read the tag.  You'll notice I added the following lines of code.
            if (android.os.Build.VERSION.SDK_INT >= android.os.Build.VERSION_CODES.N && !writeIgnore) {
                adapter.ignore(tag, ONE_SECOND, this, null);
            }

This signals that you are no longer interested in communicating with an NFC tag for as long as it remains in range.  See the document here... https://developer.android.com/reference/android/nfc/NfcAdapter#ignore(android.nfc.Tag, int, android.nfc.NfcAdapter.OnTagRemovedListener, android.os.Handler)


[BUG] Bloxstrap saying "Roblox failed to launch" (NOT A ROBLOX ISSUE)

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[ ] I did not answer truthfully to all the above checkboxes.

Bloxstrap Version
2.8.1
What problem did you encounter?

This pops up when i start roblox using bloxstrap and i did test the normal roblox launcher that does not crash.
And i am using windows 11.
Bloxstrap Log
N/A

Did you ever fix it?

This pops up when i start roblox using bloxstrap and i did test the normal roblox launcher that does not crash.

Just to be clear, Roblox doesn't launch at all? You're not having the issue described in #3559, right?
If you're not, then upload your configuration please: https://github.com/bloxstraplabs/bloxstrap/wiki/Uploading-your-Bloxstrap-configuration

This pops up when i start roblox using bloxstrap and i did test the normal roblox launcher that does not crash.

Just to be clear, Roblox doesn't launch at all? You're not having the issue described in #3559, right?
If you're not, then upload your configuration please: https://github.com/bloxstraplabs/bloxstrap/wiki/Uploading-your-Bloxstrap-configuration

Feels like the same issue to me tbh, I fully understand that you're busy and all that but any chance we can get an estimate of when this can be fixed or maybe what other info you need from me to fix it on my issue, issue #3559?


Add camelCase to css-loader config

IMO when using css modules, most people would want camelCase, otherwise can fallback to styles.["camel-case"] instead of styles.camelCase.

Could we get this in, pretty please? This is so key.

Hey @kitze, I am a bit late to the party, but could this be optional? I use CSS-Modules together with react-css-modules, so you can just use a string instead of referencing to the object:
<div styleName="camel-case" />

is this feature published already? i'm still getting the class name with dash instead of camel case

by the way, in the meantime i'm doing:
import _ from 'lodash'

export default function cssModulesWrapper (cssObj) {
  return _.mapKeys(cssObj, (value, key) => _.camelCase(key))
}

and then in code:
import cssModulesWrapper from '../../../../core/utils/cssModulesWrapper'
const styles = cssModulesWrapper(require('./header.module.css'))


v1 :egg:

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (fc9310c) 100.00% compared to head (c25df39) 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff            @@
##              main        #1   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           17        17
=========================================
  Hits            17        17

Impacted Files
Coverage Δ

config/keyvault/__init__.py
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.