Issue on MQTT Subscribe

Hello,
I am trying to get this setup with my environment and ultimately communicate between HA and Hubitat. I am seeing a periodic refresh (every 1 min) of my HE devices to MQTT and see this in the debug log via mqtt publish message, but I never see mqtt-link subscribing to any topics via debug log and of course never responding to "incoming" mqtt message. Do I need to do more with the "Subscribe" parameter in the driver for setup or could it be something else.
Thanks.

Hi...
Make sure you are inserting /cmd/ before the object you are trying to control in the YAML
See issue #9 and its 2 solutions.


Fix for #6299: restore previous default shell with uninstall

Hey @zwhitten thanks for this fix. I pulled the changes in #5169 which is now ready for testing. If you want to help speed up the testing and merge (which should happen early next week), you can wget or curl it from the URL https://raw.githubusercontent.com/mcornella/oh-my-zsh/refactor-installer/tools/install.sh. Read the comments at the top of the script to know how to call it.
Thanks!

Closed by #5169.


#2734 keep the initial order of listeners

We need to run listeners at the same order in which they were declared in @Listeners({First.class, Second.class, Third.class})
Fixes #2734 and #1219
Did you remember to?

[ ] Add test case(s)
[x] Update CHANGES.txt
[x] Auto applied styling via ./gradlew autostyleApply

@asolntsev - Thank you so much for taking the time to raise a PR. Can you please help add tests that will essentially vet out the changes for the defects that you linked?

@krmahadevan Ugh... It was not easy, but I added the test: TestRunnerTest.java

@asolntsev - There are test failures. Please help take a look and help fix them.

@krmahadevan I have fixed the tests.
I think the last CI failure is not caused by my changes. It seems to be some flaky test caused by concurrent tests run:
test.failedreporter.FailedReporterTest > tearDown failure marker
  Error:   0.0sec test.failedreporter.FailedReporterTest > tearDown
  java.nio.file.FileSystemException: C:\Users\RUNNER~1\AppData\Local\Temp\testng-tmp-2956855115414577614673\testng-failed.xml: The process cannot access the file because it is being used by another process.

@asolntsev - Thank you so much for helping out with this PR. This now stands merged. Look forward to more such contributions

Yes! Achievement unlocked :)


bug: select * from t1 join t2 on t1.id=t2.id returns id separately from both tables

it should only return the id once
i was working on supporting USING joins (select * from users join products using(id) and noticed this
Test FAILED: 'select * from users join products using (id) limit 1'
returned<EMAIL_ADDRESS>Johnson Rest Suite 322|West Lauriestad|IL|35865|94|1|hat|79.0

expected<EMAIL_ADDRESS>Johnson Rest Suite 322|West Lauriestad|IL|35865|94|hat|79.0

never mind this only applies to USING joins (and i assume NATURAL joins)


Prevent circular references in Type3 fonts

In corrupt PDF documents Type3 fonts may introduce circular dependencies, thus resulting in the affected font(s) never loading and parsing/rendering never completing.
Note that I've not seen any real-world examples of this kind of font corruption, but the attached PDF document was rather found in https://github.com/pdf-association/safedocs/tree/main/Miscellaneous Targeted Test PDFs
Please note: That repository contains a number of reduced test-cases that are specifically intended to test interoperability (between PDF viewer) and parsing/rendering for various kinds of strange/corrupt PDF documents.
Some of the test-cases found there may thus not make sense to try and "fix" upfront, in my opinion, unless the problems are also found in real-world PDF documents.

/botio test

/botio-linux preview

Nice work!
/botio makeref


swap out rayon managed thread pool with a dedicated CPU thread pool via tokio Runtime

https://docs.rs/tokio/1.14.0/tokio/#cpu-bound-tasks-and-blocking-code

this might be useful to reduce the maintenance burden by collapsing dependencies and unforeseen interactions, improve readability and enforce the "pay for what you use philosophy" but runtime wise it's functionally equivalent.


Expereince Page Dark Mode Card UI Bug

Current UI

Sample Reference for Expected UI

This should be done for all of the cards

heyy , I would like to work o this issue ?

@Sarthakjain594  Assigned for 2 days

I would like to work on this issue under LGM-SOC

@Amrutha1101 it's already assigned, look for other unassigned issues.

Heyy I have resolved that issue but i wanna ask that . Is the dark color to be applied to all the cards in the page or only these first three cards .

I would like to work on this issue under LGM-SOC

@Amrutha1101 you have 3 days to work on it.

What about the (background) open source cards in the page?

What colors do you want me to add for the highlighted ones?

Have a look at the issue description for #884 @Amrutha1101

@Amrutha1101 Please try to finish this asap

@Amrutha1101 Please try to finish this asap

I'll make a PR by the end of the day :)

Resolved and would be improved in further issues


Remove outdated deprecations

This removes a number of outdated deprecations in the deprecatedCompat project. I've left some of the unused deprecation logic in that project as we are likely to need to use it for future deprecations.

My first impression is that the change looks god, but I am a little terrified about removing some of this like the global factories as they seem to unfortunately still be getting used? (https://sourcegraph.com/search?q=context:global+ts\.createIdentifier\(+lang:typescript&patternType=regexp&sm=1&groupBy=repo)

Out of curioisity
@typescript-bot perf test this

My expectation is that tsc won't change but tsserver should get faster as it has to include these compat things (but, those benchmarks are still wonky until I merge my PR on ts-perf; been focusing on other things).

My first impression is that the change looks good, but I am a little terrified about removing some of this like the global factories as they seem to unfortunately still be getting used? (https://sourcegraph.com/search?q=context:global+ts\.createIdentifier\(+lang:typescript&patternType=regexp&sm=1&groupBy=repo)

The global factories have been deprecated since 4.0, I should think we've given plenty of time for users to migrate who aren't already using a pinned version of TypeScript.

While this might have a minor benefit to perf for tsserver operations, the real benefit is in the reduced startup time for tsserver/typescriptServices. None of the tsc perf tests are relevant, because nothing in deprecatedCompat is included in tsc.js.

Should we do this for other APIs and server protocol commands too ?

It is 5.0... 😄


Handle closed attendee registration

This PR adds a new AttendeeRequiredMixin and changes existing views
in the attendee and talk apps to use this mixin. The mixin makes sure
that views that require an attendee redirect to the attendee
registration view as long as the event allows attendee registration. If
the attendee registration is closed the mixin redirects to the
django_registration_disallowed url.
The PR also ensures that knowing the attendee registration URL is
not sufficient to register an attendee and that no attendee activation
is possible when the attendee registration has been closed.
All tests have been adapted, new tests have been added.
This fixes #160

Pull Request Test Coverage Report for Build 398

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.0001%) to 99.975%

Totals

Change from base Build 397:
0.0001%

Covered Lines:
3352

Relevant Lines:
3352

💛  - Coveralls


CLOUDP-74926: Add field country in User - ops manager go client

Proposed changes

Jira ticket: CLOUDP-74926

Checklist

[x] I have signed the MongoDB CLA
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added any necessary documentation (if appropriate)
[x] I have run make fmt and formatted my code

Further comments

The Create user endpoint for CM requires the field Country https://docs.cloudmanager.mongodb.com/reference/api/user-create/. This field wasn’t included in the user struct because the same endpoint for OM doesn’t use this field. (https://docs.opsmanager.mongodb.com/current/reference/api/user-create/)

Codecov Report

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

@@           Coverage Diff           @@
##           master      #62   +/-   ##
=======================================
  Coverage   55.08%   55.08%
=======================================
  Files          41       41
  Lines        1770     1770
=======================================
  Hits          975      975
  Misses        401      401
  Partials      394      394

Impacted Files
Coverage Δ

opsmngr/users.go
45.00% <ø> (ø)

Continue to review full report at Codecov.

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


start paused video

hi, hoy can load video from ulr, but start paused, no automatically play?
regards

I had add a property to control auto play when load completed,you can use it by "playView.autoStart = false".


Backport tsdb v0.7.1 to prometheus release-2.2

Proposal
We are using a nfs file system to storage prometheus data. However, this nfs system not support all nfs feature and we can't upgrade our prometheus from v2.2.1 -> v2.3.0，for v2.3.0 we would get a error like this:
level=info ts=2019-04-25T07:26:42.163002142Z caller=main.go:412 msg="Notify discovery manager stopped"
level=info ts=2019-04-25T07:26:42.163011785Z caller=main.go:588 msg="Notifier manager stopped"
level=info ts=2019-04-25T07:26:42.163023391Z caller=main.go:398 msg="Scrape discovery manager stopped"
level=error ts=2019-04-25T07:26:42.163111118Z caller=main.go:597 err="Opening storage failed lock DB directory: permission denied"

So, we are still using prometheus v2.2.1。But as the time go，we find a bug approved along with Unknown series references in WAL after crash，so we hope whether prometheus branch release-2.2 can backport this patch and fix the problem。
Bug Report
What did you do?
Running prometheus v2.2.1 with a nfs file system for storing data.
What did you expect to see?
when exists unknown series references in WAL samples, keep the series references。
And backport tsdb v0.7.1 to prometheus release-2.2 branch。
What did you see instead? Under which circumstances?
the logs show following
level=info ts=2019-04-25T07:48:43.196185867Z caller=web.go:382 component=web msg="Start listening for connections" address=<IP_ADDRESS>:9090
level=info ts=2019-04-25T07:48:43.196192061Z caller=main.go:504 msg="Starting TSDB ..."
level=warn ts=2019-04-25T07:48:44.098411172Z caller=head.go:320 component=tsdb msg="unknown series references in WAL samples" count=609875

and it would cause：
level=error ts=2019-04-25T07:56:13.695858467Z caller=db.go:281 component=tsdb msg="compaction failed" err="persist head block: write compaction: add series: out-of-order series added with label set \"{__name__=\\\"node_bmc_compatibility:avg1h\\\",_firmware_revision=\\\"3.19\\\",_host=\\\"9cdb2928-85a8-11e8-9396-52540075da0d\\\",_manufacturer_name=\\\"supermicro\\\",_product_id=\\\"1588\\\",hostname=\\\"vm19\\\",role=\\\"master\\\"}\""

Environment

System information:

# uname -srm
Linux 3.10.0-693.11.6.el7.smartx.1.x86_64 x86_64

Prometheus version:

prometheus --version
prometheus, version 2.2.1 (branch: HEAD, revision: bc6058c81272a8d938c05e75607371284236aadc)
  build user:       root@149e5b3f0829
  build date:       20180314-14:15:45
  go version:       go1.10

We usually only support the current stable release (2.9 as of now) so I don't see that we'll update the release-2.2 branch.
I'm closing it for now. If you have further questions, please use our user mailing list, which you can also search.


fixed the outdated redux dev tools documents url

fixed the outdated redux dev tools documents url

it moved to http://extension.remotedev.io/docs/API/Arguments.html

Thanks!


Make sure Vega-Lite nulls aren't converted to 0's

coercing null to numeric -> 0, which is very unfortunate behavior 👎

Problem will pop up anywhere there's a pivot

[ ] Trend/comparisons
[ ] Map
[ ] Links

Completed with Jan 2024 major site change push.


Ensure all dependencies are tracked

As a project developer, I want all currently untracked dependencies captured with spans, so that all sub-operations within the larger project operations are collected by Azure Monitor

[ ] Requests and dependencies available in Application Insights compared with expected set of requests and dependencies for the application (many libraries will auto instrument spans for their requests and dependencies)
[ ] Tracers and spans added to project code that wrap all missing requests and dependencies

Mentioned in #413


I can't Start Server

When I'm enter yarn test, nothing work then enter yarn start, nothing work too
What can I do

do you have the db server started and configured?

ㅅ

do you have the db server started and configured?

Yes I Configured on ormconfig.json and definitely started and Also reds-server


runtime: async preemption support on ARM64 breaks ARM64 on QEMU

The change in 1b0b9809046c1862f8ea0240fe016e516c67676f breaks QEMU support for Go programs, resulting in a variety of crashes ranging from segmentation faults, illegal instructions and scheduler panics (holding locks).
This is partially recovered by the change in 73d20f8186a091c8d7e81b621136770981cf8e44 which prevents the crashes, but results in extremely poor performance; processes appear only able to use about 10-15% of a core compared to ~100% prior to 1b0b9809046c1862f8ea0240fe016e516c67676f.
What version of Go are you using (go version)?

$ go version
go version devel +1b0b980904 Thu Nov 7 19:18:12 2019 +0000 linux/amd64

Does this issue reproduce with the latest release?
No
What operating system and processor architecture are you using (go env)?

In a checkout of gonum.org/v1/gonum/lapack/gonum, run GOARCH=arm64 go test -run Dgeev
I have tried to make a smaller reproducer, but have not managed yet.
What did you expect to see?
Other expected package failures.
What did you see instead?
A variety of crashes.

cc @aclements @cherrymui @ianlancetaylor
Is this something we need to fix for 1.14, since it is a regression?
Tentatively marking release blocker.

See https://github.com/golang/go/issues/15050#issuecomment-204131143 and https://github.com/golang/go/issues/1508#issuecomment-549859231.
Per the porting policy, supported platforms need to have a developer maintaining the port for that platform and a builder to run tests.  If folks are relying on it working, then

See https://github.com/golang/go/issues/15050#issuecomment-204131143 and https://github.com/golang/go/issues/1508#issuecomment-549859231.
QEMU has historically been fairly buggy for multi-threaded programs, so a regression here is not a big surprise.
Per the porting policy, supported platforms need to have a developer maintaining the port for that platform and a builder to run tests.  If folks are relying on QEMU being able to run Go programs, then someone needs to volunteer to either fix the QEMU bugs (or to actively maintain the workarounds on the Go side).

CC @neild @bufflig

We have a very minimal "keep arm/arm64 qemu-user working with go binaries" test that I committed at 5095e5d8e2cec3d6209e733652ead8ddc20fc7c2 (it only runs a hello world). But in general yeah, I don't think anyone has ever made a serious effort to keep qemu-user working and performant.

@ALTree, we intentionally deleted that test (in CL 206137) because it was flaky and nobody had volunteered to support the configuration it was testing.

@bcmills Ah, funny. I didn't have any memory of the deletion, even though you cc'ed me on the CL. So I guess qemu-user really shouldn't be expected to work smoothly.

As @bcmills said, QEMU user mode is not actually supported. I think this is a QEMU bug in handling async signals, especially with signal context modifications. And it's not only ARM64, but also other architectures. For reference, for AMD64, qemu-x86_64 doesn't work since at least Go 1.6 (due to other reasons, not async signal).
$ go1.6 build hello.go
$ qemu-x86_64 ./hello
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault

Does it work on qemu-arm64 if you set GODEBUG=asyncpreemptoff=1?

Yes, it runs very happily with that variable set.


Report bookrunner failures for each stage

Description of changes:
Adds a Python script that can be used to collect failures for each stage based on the bookrunner HTML report. The script is used to print this data in the bookrunner workflow.
Call-outs:

Testing:

How is this change tested? Testing through CI.

Is this a refactor change? No.

Checklist

[x] Each commit message has a non-empty body, explaining why the change was made
[x] Methods or procedures are documented
[x] Regression or unit tests are included, or existing tests cover the modified code
[x] My PR is restricted to a single feature or bugfix

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

It looks good to me. How hard would it be to actually print the failure? E.g.: Timeout x Crash.

This works on the HTML output, which means it would be much harder.
I submitted this as a "temporary" solution (that I was already using) so all of us can collect bookrunner metrics in just a few clicks. But actually, the best way to do this would be working on the run.json file that Litani produces. It's much easier to get the exact failures (or any other data, really) in there. However, I think run.json was being removed before uploading the results because of space constraints on GH pages. I'll look into that.


feat(UI-1047): add hubspot connection

Description
Based on this form:
https://github.com/autokitteh/autokitteh/blob/ee626d8aa29d5bd87739f4012b6d39924ed5a8db/web/static/hubspot/connect/index.html
Please create a new/edit connection forms on our side.
Take the icon from here and mention the source in the index.ts file:
https://www.svgrepo.com/svg/331433/hubspot
Linear Ticket
https://linear.app/autokitteh/issue/UI-1047/add-hubspot-connection
What type of PR is this? (check all applicable)

[ ] 💡 (feat) - A new feature (non-breaking change which adds functionality)
[ ] 🔄 (refactor) - Code Refactoring - A code change that neither fixes a bug nor adds a feature
[ ] 🐞 (fix) - Bug Fix (non-breaking change which fixes an issue)
[ ] 🏎 (perf) - Optimization
[ ] 📄 (docs) - Documentation - Documentation only changes
[ ] 📄 (test) - Tests - Adding missing tests or correcting existing tests
[ ] 🎨 (style) - Styles - Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
[ ] ⚙ (ci) - Continuous Integrations - Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
[ ] ☑ (chore) - Chores - Other changes that don't modify src or test files
[ ] ↩ (revert) - Reverts - Reverts a previous commit(s).

Please use this icon to get MIT license and not another: https://www.svgrepo.com/svg/443148/brand-hubspot


Addition of the choice of currency regardless of the selected language

After selecting the language in which you want the program to be displayed, the program should display the list of all the available currencies, all in 2 columns, example :
Select a language [default - 1] : 1

_("Fiat Currencies :\n")

- AUD  : _("Australian Dollar")           | $    |   - BHD  : _("Bahraini Dinar")              | .د.ب
- CAD  : _("Canadian Dollar")             | $    |   - INR  : _("Indian Rupee")                | ₹
- GBP  : _("British Pound Sterling")      | £    |   - SAR  : _("Saudi Riyal")                 | ﷼
- NZD  : _("New Zealand Dollar")          | $    |   - ZAR  : _("South African Rand")          | R
- USD  : _("United States")               | $    |   - BMD  : _("Bermudian Dollar")            | $
- ARS  : _("Argentine Peso")              | $    |   - CLP  : _("Chilean Peso")                | $
- MXN  : _("Mexican Peso")                | $    |   - HKD  : _("Hong Kong Dollar")            | 元
- VEF  : _("Venezuelan bolivar fuerte")   | B$   |   - KWD  : _("Kuwaiti Dinar")               | د.ك
- BRL  : _("Brazil Real")                 | R$   |   - MYR  : _("Malaysian Ringgit")           | RM
- PHP  : _("Philippine Peso")             | ₱    |   - SEK  | _("Swedish Krona")               | kr
- RUB  : _("Russian")                     | ₽    |   - UAH  : _("Ukrainian hryvnia")           | ₴
- CHF  : _("Swiss Franc")                 | CHF  |   - XDR  : _("IMF Special Drawing Rights")  | SDR
- PLN  : _("Polish Zloty")                | zł   |   - CZK  : _("Czech Koruna")                | Kč
- TRY  : _("Turkish Lira")                | ₺    |   - HUF  : _("Hungarian Forint")            | Ft
- EUR  : _("Euro")                        | €    |   - LKR  : _("Sri Lankan Rupee")            | ரூ
- NGN  : _("Nigerian Naira")              | ₦    |   - PKR  : _("Pakistani Rupee")             | ₨
- SGD  : _("Singapore Dollar")            | S$   |   - BDT  : _("Bangladeshi Taka")            | ৳
- DKK  : _("Danish Krone")                | kr.  |   - ILS  : _("Israeli New Shekel")          | ₪
- MMK  : _("Burmese Kyat")                | K    |   - NOK  : _("Norwegian Krone")             | kr
- THB  : _("Thai Baht")                   | ฿    |   - VND  : _("Vietnamese đồng")             | ₫/đ
- KRW  : _("South Korean Won")            | ₩    |   - IDR  : _("Indonesian Rupiah")           | Rp
- JPY  : _("Japanese Yen")                | ¥    |   - TWD  : _("New Taiwan Dollar")           | 圓
- CNY  : _("Chinese Yuan")                | ¥

_("Cryptocurrencies :\n")

- BTC  : Bitcoin                          | ₿    |   - XLM  : Lumens                           | XLM
- BNB  : Binance Coin                     | BNB  |   - BCH  : Bitcoin Cash                     | Ƀ
- LINK : Chainlink                        | LINK |   - YFI  : Yearn.finance                    | YFI
- ETH  : Ether                            | Ξ    |   - XRP  : XRP                              | ✕
- EOS  : EOS                              | ε    |   - LTC  : Litecoin                         | Ł
- DOT  : Polkadot                         | DOT  |   - SATS : Satoshi (0,00000001 BTC)         | sat
- BITS : Bits (100 satoshis)              | BITS

Select a currency [default - USD] : EUR

We can see in the example that the selected currency is "EUR", and not "29" or "15", as is the case for the choice of languages.
I think that it would be more practical / intuitive / ergonomic (in particular, because it would avoid seeing a list of numbers displayed before each line, which would force to re-edit each line of code to add spaces so that everything is correctly aligned)
There are also some characters (such as ₪) which cannot be displayed at the moment when the program is started, so we would have to find a way that would allow them to display correctly.

I add that, if, in the program, it is necessary to define a limit of the maximum number of characters for the currencies ("EUR", "USD", ect ..), it would be preferable to set it to 5 characters, and not 3 or 4, so that all currencies can be compatible, in case of future evolution of the API of coingecko.


Split and simplify the verifier test rules and start working on cxx_indexer_test [phab:D1669]

Created by shahms at 2017-05-23 21:33:03:
Update go_indexer_test to work with changes to verifier tests

zarko wrote at 2017-05-23 21:53:49:
I think that the files of substance (bzl, sh, etc) need copyright headers.

shahms wrote at 2017-05-23 22:05:58:

! In (earlier comment), zarko wrote:
I think that the files of substance (bzl, sh, etc) need copyright headers.

Done.

shahms wrote at 2017-05-23 22:06:06:

Add copyright headers

zarko accepted this revision at 2017-05-23 22:28:06

shahms closed via commit 96c8d96b04e1d8be353811603e03d611a03d8762 at 2017-05-24 14:37:57


Installation on Windows

For easy updating, can you update the pypi entry or add a setup script or toml file?

I'll try to figure it out again (was done before by a dev that is no longer available). For now you can just clone the repo, install the venv and requirements and it should work fine on windows.


[skip ci] refactor: Backport libs refactorations from [REDACTED]

Thx [REDACTED] bros!

how tf do you expect the bot to review ??

how tf do you expect the bot to review ??

Sad bot noises

ayo what??????????????


Z-index too low when used with other custom cards

Some custom cards set their own Z-index e.g Swipe-Card has a z-index of 1.
Bubble popup is also z-index:1 and causes popup items to go behind other elements.
Would it make sense for a popup to have a higher z-index?

Hi, an higher z-index than 1 will break a lot of features, for exemple the default HA more info panel is on z-index 1. Just one question but are your vertical-stack/pop-up right before your horizontal-buttons-stack? All pop-ups needs to be after all other cards to be displayed correctly.

 I did read your docs, but that slipped past me 😄
Solved by changing order of bubble card. Thanks.

 I did read your docs, but that slipped past me 😄
Solved by changing order of bubble card. Thanks.


Make 'push' an explicit, separate step from 'build'

Running build.ps1 may have 'push' side-effects when certain environment variables are set.  We should separate anything that "pushes" into a separate step

separation of concerns
avoids accidental package pushes
makes it safer for us to write automation that runs Universe builds for PRs, mirror builds, etc.
make it easier to figure out which variables are required for a successful push

@natemcmaster can you give examples of specific places where this is problematic?

This is typically most problematic when setting up a new TeamCity configuration. You have to very carefully setup environment variables to avoid accidental pushes. Environment variable configuration is inherited in TC so it's not obvious from looking at "build steps" if the artifacts will be pushed when the build finishes.
It's also tricky when setting up builds of feature branches or "personal builds" on TC that shouldn't be pushing packages.

Do you have a specific example where this could be a problem?

I only remember a few of accidental pushes in the last couple years, and they were to myget so it was low-impact or even went unnoticed. My bigger concern is that one day it be an accidental push to NuGet.org, not myget. Because we've merged "build" and "deploy" concepts into one command line gesture, it will most likely happen when a dev is working on a build script locally and forgets to unset some env var before invoking "build".

Repos where "build.ps1" may result in a push (given the right env variables)

https://github.com/aspnet/AzureIntegration
https://github.com/aspnet/Universe
https://github.com/aspnet/Coherence
https://github.com/aspnet/Coherence-Signed
https://github.com/aspnet/AspNetCoreModule

Is this a thing anymore with ProdCon? Safe to close?

Yes, this was mostly done as a part of ProdCon.


ts parameter and p='{x}d' parameter

According to :
http://www.networkerror.org/component/content/44.html?task=view

ts - Starting timestamp (Unix format). If blank, it uses today.

and

p - Period. (A number followed by a "d" or "Y", eg. Days or years. Ex: 40Y = 40 years.)

Which, used together allow to fine tune the date range of the data, ease the use of the downloaded file and make the library convenient for use cases involving data not starting from today.
In the current state of affair, we can process the returned dataframe in order to get only the desired range, but it's an unecessary waste of computional ressource and require to use a wrapper to make good use of the library beyond a single case.
The package should be modified in order to take that into account.

Would do integrate it with a pull request?


cdc, resolved_ts: reduce allocation in leadership resolver

What is changed and how it works?

Issue Number: Close #13665
What's Changed:

cdc, resolved_ts: reduce allocation in leadership resolver

Check List
Tests

Unit test

Release note
None

/merge

/merge


UI: Fix infinite redirection loop on /

[ ] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes

Server React UI index page on request to / instead of figuring out the path to redirect to. This fixes #4128
Append / prefix to other redirects. Without this the location is interpreted as relative and we end up doing weird redirections like /prefix/new/prefix/....

Verification
Tested Querier, Ruler, and Block Viewer UI locally with and without external prefixes

Yes, I'd say let's release a minor version with the patch.

I think I need to create a PR to the release-0.20 branch for that, right?

Finally managed to change the base correctly :dizzy_face:

The e2e tests are failing because of the busybox SHA pinning issue (which is fixed on main).

Are there any tests we could add? I remember how we've had lots of different fixes for the prefix stuff and the issue wasn't completely solved until tests were added that actually programmatically check whether everything works correctly :sweat:

As @GiedriusS suggested it'd be great to have tests.
About #4171 and #4202, do we need them for the end artifact or just for CI to pass? I don't have enough context on this.

About #4171 and #4202, do we need them for the end artifact or just for CI to pass? I don't have enough context on this.

I am sorry for the delay on this. I don't have enough context either, but I think we need them for both CI and the end artifact as we won't be able to create docker images to push. I am not even sure if both of them are required or if we can only use one of them.
But since the next release is very soon (first RC in 6 days I think), can we just merge this to main and go ahead.

Are there any tests we could add? I remember how we've had lots of different fixes for the prefix stuff and the issue wasn't completely solved until tests were added that actually programmatically check whether everything works correctly :sweat:

@GiedriusS  Yes, we do have tests for that, but I am not sure how can we add tests for these type of scenarios. There are a lot of places where things can go wrong :sweat_smile:
The E2E tests for routePrefix etc would have caught this but, but they access the /graph page directly and this bug only occurred when you tried to access /.

Depandabot CI is saying that the config file is wrong and it doesn't have anything like vendor in it's schema, but the documentation says otherwise :shrug:


examples fail on latest released version

Version 0.2.0 installed with pip can't run the current examples which expect condense to expand #228; i.e. ex01, 02, 05, 06, 09, …, ex28.  This leads to various errors, depending on how the solution vector is subsequently interpreted
Also ex29 fails with NameError: name 'ElementLineP2' is not defined #235.

conda deactivate
conda create -n skfem-ex28
conda activate skfem-ex28
conda install pip
pip install scikit-fem
pip install pygmsh
wget https://raw.githubusercontent.com/kinnala/scikit-fem/master/docs/examples/ex28.py
python ex28.py

I drafted new version 0.2.1. I should've called it 0.3.0 as it was backwards-incompatible, but oh well. I'm certain 1.0.0 happens during spring and after that I'm more careful with semver.


ModuleNotFoundError: No module named 'mmskeleton.version'?why I can not find version?Thanks!!!

same error

same error 5555555

I've already solved the problem by magic.. I opened the version.py in 'mmskeleton\mmskeletion\version.py' and found this .py is very simple, So I'm going to move the contents of this file to where the error was reported,however, as I was about to paste, I found that the red line disappeared，then I solved. If you dont have this magic,just paste it,I think it's gonna work, too.Good luck

Problem is solved by run "python setup.py build_ext --inplace" in the virtual environment. This commond leads to an error below, but it doesn't matter.

The key point is the part marked by a red arrow. This function generates the version.py file under mmskeleton\mmskeleton.


Advanced copy> partial JSON copy

System information:

Operating system (distribution) and version Win10
DBeaver version 6.3.5

Describe the problem you're observing:
Advanced copy> JSON doesn't work for a part of a table.
Steps to reproduce, if exist:

Select several cells in a table of Data Editor
Select Copy as JSON in Data Editor context menu

Actual result:

Error message appears "Error while exporting table row  Index 1 out of bounds for length 1"
Selected data is not copied.

P.S. The same situation with Data export:

select several cells
select "export data" in Context Menu for the cells
select Json
check "Selected columns only"
go through other steps of the wizard and press "Start"

dbeaver-debug.log

Fixed

verified


[RFC] Proposal to add more maintainers for long term project growth

Dear typst-lsp Maintainers and Contributors ,
Firstly, I would like to express my deepest respect and gratitude to the @nvarner . Your hard work has allowed typst-lsp to evolve into a tool that we all rely on and it is the infrastructure of the typst ecosystem.
I have noticed that, for various possible reasons, updates and maintenance of the project may not be as frequent as before. We fully understand that maintaining an open-source project requires a significant amount of time and effort, a contribution that cannot be measured in monetary terms. Therefore, I would like to propose a suggestion to help us collectively propel the development of typst-lsp.
With the growth of the project, we have seen some members who have been exceptionally active and professional in issue discussions, pull requests. To support the continuous development of typst-lsp, I suggest considering the expansion of maintainers.
For example here is a list of top5 contributors in the past 3 months: @PgBiel @Myriad-Dreamin @Enter-tainer @KillTheMule @astrale-sharp
I would like to ask for the community's and current maintainers' opinions:

Do we agree to invite more maintainers to join our team?
Regarding the mentioned community members, are there any other opinions or suggestions?

I hope hearing everyone's thoughts and am willing to participate in the discussion and implementation process.

Hey there, thanks for this proposal ❤
If nvarner is okay with this, i would indeed love to be more invested in this project, i love ide stuff
The project is really complex and i think there's a lot of stuff that only nvarner could give the final go to a change
In the time we need to get experienced enough to decide what's possible to merge, we could have a board of maintainers where two of us or more review PR's or our own work to do most of the work before nvarner has to confirm.

I can certainly help here in some form or another (maybe not with active contributions, but maybe reviewing from time to time, or other organizational stuff?).
With that said, I gave this proposal some thought and I was thinking that this could perhaps link to the idea of a GitHub organization for active contributors in the Typst community, similar to nix-community. We could move some more important community projects to that organization and make it easier to shift projects' maintainers over time. (Regarding the name of such an organization, it seems that someone has already taken the typst-community name, so I'm not sure if they'd be willing to give it to us, but that's something to consider.)
OTOH, while that seems sort of "ideal", it's understandable that not every large project owner could want to "forfeit" ownership of their own project like that - even if they'd remain the sole maintainer, it's valid to worry about being subject to bad management from the organization and thus involuntarily lose control over their own project. Therefore, such an approach would have to be planned out very carefully in order to ensure that the whole process is voluntary, and nobody is taken away from their projects without consent. Exceptions could be added in that regard, such as bad behavior by a specific project's maintainer (e.g. intentional "malware" being pushed or being inactive for several years or something else), but that could also be controversial. We'd have to study how nix-community handles this.
(Perhaps a more viable alternative to the above is have a smaller-scale organization of specific Typst contributors, not aiming to be the sole organization of contributors. But I'm not sure!)
So, for the time being, maybe a smaller scale organization, such as one named just "typst-lsp", could be created with a handful of contributors, and the current project leader (@nvarner) would naturally be the leader of the organization. But we'd definitely need feedback from them - maybe that's not what they desire at all, and that'd be 100% fine. We can always investigate alternatives to help them - and each other - as much as possible. 🙂

@Enter-tainer no need for the formality: you're entirely correct, and I really should have added some maintainers earlier. You or any of the people mentioned would be great.
For those interested, please leave a comment here.
@astrale-sharp you sound interested; to be explicit, would you like to be a maintainer?

thank you @nvarner I'm very glad to become a maintainer. I've go through lsp's code before and handled serveral typst version updates. I'm on work in weekdays but I have time in nights and weekends.

thank you @nvarner I'm very glad to become a maintainer. I've go through lsp's code before and handled serveral typst version updates. I'm on work in weekdays but I have time in nights and weekends.

I'm fine with being a maintainer.
But there is a question I'm not sure. It is that if there will be many maintainers, what's the best way of reviewing and accept PRs for lsp project? This should be determined by @nvarner.

I'm fine with being a maintainer.
But there is a question I'm not sure. It is that if there will be many maintainers, what's the best way of reviewing and accept PRs for lsp project? This should be determined by @nvarner.

I would love to be a maintainer (but I might need guidance at first)

@Enter-tainer @Myriad-Dreamin @astrale-sharp  thank you! I'll set you up as maintainers soon.
In terms of merging PRs, I'm not yet sure the best approach. For now, I'll leave the current settings on GH (pass CI, any maintainer can approve).
In general, I'm looking out for correctness and maintainability issues. Here are a few of my higher-level considerations:

The ideal implementations of language services should use relevant Typst functions when appropriate. That ensures that our code can't be broken by Typst changes (eg new syntax), so the language server will still work, and we won't have to spend time figuring out how changes affect us.
Generalizing the above, implementations should always use the highest level API they can. So, Typst language analysis functions are best, but if there isn't one, prefer to implement it via the syntax tree rather than the raw source code (eg semantic tokens replacing TextMate, though TM seems like it needs to come back in a small way).
LSP functionality should be written to the spec. (It's worth noting that the spec is very closely tied to VS Code and can be vague. Some things are documented only in GH issues. VS Code tends to have very good support for LSP, but some things, including syntax highlighting and configuration, are poorly or strangely integrated. It may need special casing in the near future.)

For good PRs unlikely to be controversial or have major bugs (eg crashing, breaking existing functionality), it should be fine for anyone to merge on their own. More complex ones I'm not sure, but if at least 2 approve, it's probably fine.
In the worst case, we have until each release to easily roll back changes which caused unexpected problems.

Amazing :D


feat(localizations): Add huHU localization

Description
Added hungarian language

Checklist

[X] npm test runs as expected.
[X] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[X] other: Localization

I forgot to add the Changeset. Not sure, if I could do it at this point, or should I open a new PR ?

@ezkomoly ignore it this time. We will add the changeset. :)

Hello @ezkomoly, thank you for the contribution!! :) It seems that a few things are missing for this PR to allow us to merge it:

export the hu-HU.ts from the localization package (need to export it from the index.ts)
add a changelog entry for this (check the changeset-bot comment of this PR)

Thanks for adding the changeset!
I exported huHU from the index.ts.


add target_temperature_step

closing https://github.com/mariusz-ostoja-swierczynski/tech-controllers/issues/71
This will allow to setup a temperature by each 0,1 Celcius degree (previously default was 0,5 degree)

Thanks! 👍


Reimport settings file

The Authoring Tool should allow the settings file to be re-imported.
This will allow the designer to make edits to the settings without starting over.

Fixed by e835aa556ac5a61d6adcbc3601944f3e07cca5d4.
Changes have also been deployed to GitHub Pages.


Second spark connection could hang (waiting state) in certain scenarios

Using sparklyr 0.3.12, and Spark 2.0.0
EMR Cluster r3.2xlarge, 1 master, 2 worker nodes

flights data (full set) is used. Data is copied from S3 to HDFS in csv format, and then loaded into Hive tables.
In IDE, open a spark connection
Run this command to cache flights data:

tbl_cache(sc, 'flights')

Create a Shiny application on Shiny Server that does some interaction with Spark and flights data.
Add the same command on top so data gets cached.
Launch the application on Shiny Server. This hangs indefinitely.

Note: The same Shiny app without any changes loads fine (after the long delay) if the first spark connection from IDE is closed.

I performed a similar investigation locally, here is my setup:
Starting spark standalone:
./start-master.sh
./start-slave.sh spark://Javiers-MBP-2.domain:7077

Running this from the first r session would work, but the second session would hang:
sc <- spark_connect(master = "spark://Javiers-MBP-2.domain:7077", spark_home = "/Users/javierluraschi/Library/Caches/spark/spark-1.6.1-bin-hadoop2.6")

copy_to(sc, iris)

The problem was resource starvation for the second application:

@fereshtehRS Do you see the second application also in waiting state?
If that's the case, we need to make sure there are enough resources in the cluster to run a second application. In my case, I was able to fix this as follows:
sconf <- spark_config()
sconf[["spark.cores.max"]] <- 1

sc <- spark_connect(
    master = "spark://Javiers-MBP-2.domain:7077",
    spark_home = "/Users/javierluraschi/Library/Caches/spark/spark-1.6.1-bin-hadoop2.6",
    config = sconf)

copy_to(sc, iris)

Notice that when the second application started is now available also in running state and the commands succeed:

I have simpler workflow that demonstrates the same issue (I think):

Connect to a cluster: sc <- spark_connect(master="yarn")
Cache a hive table: tbl_cache(sc, "hivetable")
Start a new R session
Connect to the same cluster (should create a new context)
Cache the same hive table
Caching hangs on second session

@nwstephens right, we need to make sure the second application is no longer in waiting state, this is independent of sparklyr. Is the second application in waiting state?
If that's the case, we can start by reducing the number of cores to troubleshoot the resource that is blocking the app to start:
sconf[["spark.cores.max"]] <- 1

@javierluraschi The Web UI on the EMR cluster is different, and not always helpful. In this case I don't see the WAITING status for the job while it is hanging. This is what is displayed for the job:

And if I drill into the job, this is what is displayed for stages:

And nothing is displayed if I drill further down.
But definitely the job is waiting, nothing is running for it (based on the UI). I tried with some different configurations with flights table (the big table), and got same results.
However, trying with another table that is much smaller didn't show this issue. So seems to be a resources issue.

I should also mention that when we terminate that operation from IDE, that doesn't terminate the Spark job. Therefore any operation we run after this also hangs. For example spark_disconnect(sc) wouldn't work.

@fereshtehRS did
sconf[["spark.cores.max"]] <- 1

helper at all? If you could grab me tomorrow to debug this together, that would be great, I still think there is probably a resource constraint somewhere that is blocking execution. I'll try to find you in slack as well.

Investigation follow up with Fereshteh: A resource constraint on Spark seems to be causing this issue since we found out that the second connection can succeed with different resource allocation for the connection. We could use this issue to consider providing better error reporting; however, this might be unfeasible without changing in Spark itself since I'm not yet aware of an API that would provide this functionality.

@javierluraschi  (and @nwstephens ) I have done more testing around this. This is definitely a resource constraint, and may be a bug in Spark with dynamicAllocation enabled. I will write up a document, but the summary is this:

With dynamicAllocation enabled, when the first context starts a heavy job, it requests and is being granted a large number of executors
When this job is completed the resources are not always freed (this might be a bug)
There is a configuration setting spark.dynamicAllocation.executorIdleTimeout with default value of 60s. I have set this to even lower values, but doesn't seem to take effect. Or may be because the executors don't seem to be idle (even after the job is done)
Second context starts a heavy job, requests a large number of executors, but not much is available. So this hangs until resources become available. Id we disconnect the first context, then this one runs smoothly.

A different scenario:

First context starts with a small job, and completes it.
Second context also starts with a small job, and completes it.
At this point both of the contexts have some executors allocated to them.
After this, each context could start a heavy job, and they both finish (no waiting).

Disabling dynamicAllocator:

With this, we need to pre-allocate resources. These parameters must be set such that the expected number of contexts could each have enough resources:

spark.executor.instances         10
spark.executor.cores             2

With correct settings, then the second context could also start a heavy job, and it completes in a normal fashion (no waiting).

Found this parameter for dynamicAllocation:
spark.dynamicAllocation.maxExecutors
We should be able to get around the "hang" issue using a reasonable max.

Great! Should we close this issue then? @fereshtehRS

sure; closing it.


added contrib to the docker image

This will allow using the --template-dir parameter when using the
go-swagger container

Thanks @casualjim. When will you release a new minor version?
Specifically how can I get a docker image with this change?


Only decode header

I would like to decode the header of a JWT to get the kid (i need the kid to get the JWK from redis).
Currently there is no way to get it because decode_unsecured don't want to parse JWT with signature part or alg header.
The best would be to create a trait for JwkSet and allow to customize how the JwkSet handle when and id is missing.
And thx for this lib, it's the only one able to manage JWK for ECDSA algorythms all other libs depend on ring which is only able to decode it from PEM or DER (and i didn't find a way to generate PEM from JWK).

I released v0.4.0. In this version I added a jwt::decode_header(input) function.
I hope this feature is usefull to you.

Thank you very much !


showAllTicks = false, Layouts don't run enough

Describe the bug
When you have showAllTicks == false.  The different layouts don't get run when simulation.tick() is called in the Graph._graphForcesConfig().
A work around is to make new force() functions and add them in so they are used here. We might want to consider doing that instead of where the LayoutHelper gets called.
I'm not sure if we would want all layouts to be a force instead of having them get called in the graph.builder.jsx buildLinkProps() with the call to  linkCallbacks"layoutCallback".
Expected behavior
layout helper function would get called for every alpha

refactored layout to work with forces


Fix packaging of sample application to support sourcemaps

OpenNTF » JavascriptAggregator #753 SUCCESS
This pull request looks good
(what's this?)


(SLURM CPU Count) Num workers=-1 uses os.cpu_count() but system cpu count might differ from SLURM given cpu cores.

os.cpu_count() returns total cpu count on the system but SLURM doesn't make all of them available. So depending on local v/s slurm the logic to get total num of workers will be different.

Good catch! Thanks for spotting that.


Feature: Use custom logo for custom platform(lfx)

Changes proposed ✍
Use LFX logo for members and activities when the platform is 'lfx'.
What
copilot:summary

copilot:poem
Why
How
copilot:walkthrough
Checklist ✅

[ ] Label appropriately with Feature, Improvement, or Bug.
[ ] Add screehshots to the PR description for relevant FE changes
[ ] New backend functionality has been unit-tested.
[ ] API documentation has been updated (if necessary) (see docs on API documentation).
[ ] Quality standards are met.
[ ]

 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.


Add picture from url

Hello,
I try to add images from url but I give the following error
stat: <url>: no such file or directory
I have to download it and then add or there is way to import from url?
Thanks

Please download the picture and insert it to the spreadsheet by AddPictureFromBytes.


add cpcc.txt

add cpcc.txt

School website:http://www.cpcc.edu/

I like programming very much, hope to get jetbrains'tool to learn more knowledge. Thank you very much

@dinghongchao Pull request merged. Please notice that the free licenses we grant student with are for high and higher education students, and for educational purpose only. Thank you!

thank you very much

@philipto  Yes i do.Thank you very much


BUG: Workflow runs only on certain changes

The workflow was running on every PR which is wrong. It should run only when files in cloud_chatops dir are changed or the workflow itself

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 81.08%. Comparing base (ff9b066) to head (a7d7548).

:exclamation:  There is a different number of reports uploaded between BASE (ff9b066) and HEAD (a7d7548). Click for more details.
HEAD has 3 uploads less than BASE

Flag
BASE (ff9b066)
HEAD (a7d7548)

4
2

rabbit_consumer
1
0

Additional details and impacted files
@@             Coverage Diff             @@
##           master     #161       +/-   ##
===========================================
- Coverage   97.20%   81.08%   -16.13%
===========================================
  Files          66        3       -63
  Lines        3046       74     -2972
===========================================
- Hits         2961       60     -2901
+ Misses         85       14       -71

Flag
Coverage Δ

rabbit_consumer
?

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Charm is in maintenance but does not recover

Bug Description
I have the charm deployed and sometimes it does go into unrecoverable maintenance mode. I assume there might be some issue with LEGO on our side and it feel like the charm does not retry, which leads to the case where my workload switches to K8s self signed certs.
prod-cla-checker@enterprise-engineering-bastion-ps6:~$ juju status
Model             Controller    Cloud/Region              Version  SLA          Timestamp
prod-cla-checker  prodstack-is  k8s-prod-general/default  3.1.8    unsupported  11:54:29Z

App                       Version  Status   Scale  Charm                     Channel  Rev  Address       Exposed  Message
charmed-cla-checker                active       1  charmed-cla-checker       edge       1  <IP_ADDRESS>   no
httprequest-lego-k8s               waiting      1  httprequest-lego-k8s      stable    40  <IP_ADDRESS>  no       waiting for units to settle down
nginx-ingress-integrator  24.2.0   active       1  nginx-ingress-integrator  stable    95  <IP_ADDRESS>  no       Ingress IP(s): <IP_ADDRESS>

Unit                         Workload     Agent  Address          Ports  Message
charmed-cla-checker/0*       active       idle   <IP_ADDRESS>
httprequest-lego-k8s/0*      maintenance  idle   <IP_ADDRESS>
nginx-ingress-integrator/0*  active       idle   <IP_ADDRESS>          Ingress IP(s): <IP_ADDRESS>

then I have to run
  374  2024-05-28 11:55:52 juju remove-unit httprequest-lego-k8s --num-units 1
  375  2024-05-28 11:56:09 juju add-unit httprequest-lego-k8s
  376  2024-05-28 11:56:13 juju status

to recover
can this be fixed?
To Reproduce

Environment

Relevant log output
-

Additional context
No response

Would you be able to provide the juju debug-log for this unit? One thing that could be happening is that we run lego as a separate process and wait for it to complete, maybe the timeout mechanism is broken.

@ghislainbourgeois prodstack cannot extract per app logs, they are empty.
I can just run juju debug-log but that is pretty much useless

@beliaev-maksim in the debug-log, would you see the events that the unit received? I am mostly interested in the history of events before it went in that state.

let me in meantime update to the latest revision.
but if you can look in parallel on what could happen, then it would be great

debuglog.txt
@ghislainbourgeois if you can find something

I'm pretty sure this issue was fixes when we moved to using the collect status event handler. In other words, if you refresh the charm you should be good to go.

let me test for a while, then by mid-end June we decide
thanks so far

@ghislainbourgeois @gruyaume
now it is even worse. Now I see all the charms active, but there is no certificate
that is a UX disaster...

Yes the charm won't show up as in error/blocked if it did not provide a certificate to a request. We are planning to add a field in the status to mention the number of certificate requests fulfilled (see #154) but the charm status itself will remain Active as it is functioning correctly.
Status     Message
Active     "1/3 certificate requests fulfilled"

@gruyaume what could be done for the charm to re-request the certs ?
I do not want to scale up/down every day

This is already done on update status events, every 5min (or however long the update status is set of the model), the charm will look at the outstanding certificate requests and re-request.

From what I investigated yesterday, the current version does not set the status to maintenance at all. So the previous issue should not reoccur.
I think we can definitely improve the logging and what we set in the status.
We also have some plans to get rid of the workload completely, making this charm k8s or machine agnostic, and it will also help us get more control on the certificate request process.

I'm going to close this as the original issue was addressed. The charm status message item is tracked through issue #154

latest deployment
$ juju status
Model             Controller    Cloud/Region              Version  SLA          Timestamp
prod-cla-checker  prodstack-is  k8s-prod-general/default  3.1.8    unsupported  08:40:58Z

App                       Version  Status  Scale  Charm                     Channel  Rev  Address       Exposed  Message
charmed-cla-checker                active      1  charmed-cla-checker       edge       1  <IP_ADDRESS>   no
httprequest-lego-k8s               active      1  httprequest-lego-k8s      stable    83  <IP_ADDRESS>  no
nginx-ingress-integrator  24.2.0   active      1  nginx-ingress-integrator  stable    95  <IP_ADDRESS>  no       Ingress IP(s): <IP_ADDRESS>

Unit                         Workload  Agent  Address          Ports  Message
charmed-cla-checker/0*       active    idle   <IP_ADDRESS>
httprequest-lego-k8s/0*      active    idle   <IP_ADDRESS>
nginx-ingress-integrator/0*  active    idle   <IP_ADDRESS>          Ingress IP(s): <IP_ADDRESS>

Reopenning based on feedback from @beliaev-maksim

@beliaev-maksim can you pleas include more information as to what the problem actually is. You mentioned having to scale up/down the charm but that's a workaround to a problem. What is the problem?
Also can you please provide the following information

Debug Logs
Relation data between httprequest and the tls requirer (using jhack)

@gruyaume my workload requires TLS on the connection. I use combination of LEGO with nginx to do it.
from juju status command all the workloads look to be green and active. However, after some time we start to receive an issue in production that requests fail due to self signed certificates.
I assume something gets corrupted on LEGO and my workload switches to Kubernetes self signed certs.
To recover proper certs I have to scale down and up the LEGO charm. That resolves the issue immediately.
debug logs you can find in the comment above:  https://github.com/canonical/httprequest-lego-k8s-operator/issues/162#issuecomment-2139592403
I cannot use jhack. That is ProdStack, I do not have sudo access to install external tools

What is the workload that switches to k8s self signed certs? Could the issue be there?

@gruyaume I think it is nginx
@mthaddon any idea ?

looks like there were a bunch of TLS issues on nginx
https://github.com/canonical/nginx-ingress-integrator-operator/issues/137 and https://github.com/canonical/nginx-ingress-integrator-operator/issues/138 and https://github.com/canonical/nginx-ingress-integrator-operator/issues/140 .

close the issue for now, will reopen if observe certificate issues


Imagespace SMQTK search

@jeffbaumes This is based off the CMU PR #106 since I wanted the helper function here as well.
Diff this: https://github.com/memex-explorer/image_space/compare/update-cmu-plugin-for-case-sensitivity...imagespace_smqtk_search
@aashish24

thanks @danlamanna :ghost:  I will have a look at it tonight.

@danlamanna how did you test it locally?

@aashish24 I used the SMQTK service Paul setup on OpenStack, and I loaded his mapping of sha1 -> filepath into my local mongo install.

Code LGTM even though I have not tested this yet. If it's helpful you can go ahead and merge this.


Turtlebot Mecanum Remote Control Front wheels do not spin.

ISSUE TEMPLATE ver. 0.4.0

Which TurtleBot3 platform do you use?

[ ] Burger
[ ] Waffle
[ ] Waffle Pi
[ x] Mecanum

Which ROS is working with TurtleBot3?

[ x] ROS 1 Kinetic Kame
[ ] ROS 1 Melodic Morenia
[ ] ROS 1 Noetic Ninjemys
[ ] ROS 2 Dashing Diademata
[ ] ROS 2 Eloquent Elusor
[ ] ROS 2 Foxy Fitzroy
[ ] etc (Please specify your ROS Version here)

Which SBC(Single Board Computer) is working on TurtleBot3?

[ ] Intel Joule 570x
[x ] Raspberry Pi 3B+
[ ] Raspberry Pi 4
[ ] etc (Please specify your SBC here)

Which OS you installed on SBC?

[ x] Raspbian distributed by ROBOTIS
[ ] Ubuntu MATE (16.04/18.04/20.04)
[ ] Ubuntu preinstalled server (18.04/20.04)
[ ] etc (Please specify your OS here)

Which OS you installed on Remote PC?

[x ] Ubuntu 16.04 LTS (Xenial Xerus)
[ ] Ubuntu 18.04 LTS (Bionic Beaver)
[ ] Ubuntu 20.04 LTS (Focal Fossa)
[ ] Windows 10
[ ] MAC OS X (Specify version)
[ ] etc (Please specify your OS here)

Specify the software and firmware version(Can be found from Bringup messages)

Software version: [x.x.x]
Firmware version: [x.x.x]

Specify the commands or instructions to reproduce the issue.

Go through turtlebot quick start guide
Upload Mecanum eample code from Arduino IDE
Using Remote control RC100B Move Robot

Copy and Paste the error messages on terminal.
None

Please describe the issue in detail.
I went through the quick start guide (standard turtlebot3 first) and got Navigation and Slam to work to check everything is set up correct.
Now, I went back using the Dynamixel Wizard application, and the usbtodxl arduino code, to set my front left and front right motors to ID's 3 and 4 and baud rates to 1mbs (as stated in the mecanum code). Then I upload the turtlebot3 friends example code Mecanum onto the OpenCR. I connect my remote control and only the back two motors spin.

Is there anything else that would limit my front motors responding to input?
Side question, I can build my own ROS packages for mecanum to create something similar to the given SLAM, correct? I noticed I cannot run bring up when the Mecanum code is on the OpenCR. Would it be easier to adjust the Arduino code to make it work with the standard Turtlebot ROS packages, or create new ROS packages?
Thanks in advance,
Austin

Hi @Mokiegmo
You have correctly set the ID and the Baud rate, but you also have to set the Operating Mode to Velocity Control mode as below.

I think it would be easier to start with modifying the existing example.
Please also note when modifying the hardware design, you should take care of the URDF as well.
Thank you.

This issue will be closed due to prolonged inactivity. Please try again with the Humble or Noetic versions, and if the issue persists, feel free to reopen it.


CB-14755 Introduce Cloudera Runtime 7.2.14

See detailed description in the commit message.

retest this please


feat: add button for quotedIdentifiersIgnoreCase flag

Q
A

Fixed issues?

Tests added + passed?
Yes

Changeset added?
Yes

Documentation PR link

Any dependency changes?
No

@hardikmaheshwari Could you please update the PR description so we can have some context when looking back at this in the future?

@akphi Added in some details. Please let me know if I am not following some convention or missing some detail that you think might be useful

@akphi Added in some details. Please let me know if I am not following some convention or missing some detail that you think might be useful

Great! Just one more thing is to update the table in the description, we don't have any tests here.

@akphi Added in some details. Please let me know if I am not following some convention or missing some detail that you think might be useful

Great! Just one more thing is to update the table in the description, we don't have any tests here.

@akphi done


Fixed #195 Search + Fixed #320 Session List within Tracks

Fixed #195 Search + Fixed #320 Session List within Tracks

@juslee @championswimmer Any thoughts?


imlibsetroot: init at 1.2

Motivation for this change
Add imlibsetroot to the package list.
Things done

[x] Tested using sandboxing
(nix.useChroot on NixOS,
or option build-use-chroot in nix.conf
on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] OS X
[x] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

I find this new version much cleaner, don't you?
LGTM

What command can I use to test the functionality of this package?
The following failed:
$ imlibsetroot capybara.jpg
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  2 (X_ChangeWindowAttributes)
  Serial number of failed request:  40
  Current serial number in output stream:  43

I am using (to set the same image on all screens) : imlibsetroot -x e -s f /path/to/picture
But your command should work (it works on my computer).
(About the failed check, I'll look into that as soon as I've got some time, but lately I've got my hands full)

The command worked anyway. I just didn't not saw my background because, I am using a tiling manager.


paragraph on virtual environment added in the debiai installation

paragraph on python virtual environment added in the debiai installation tutorial

 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.


[Refactor] Wait for apply finish when exec primary key publish version

Signed-off-by: zhangqiang<EMAIL_ADDRESS>What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[x] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

PrimaryKey table only submit apply task to thread pool and return success directly when we do publish version right now. If we query immediately after publish success, we may need to wait for version apply finish which cause unstable query time.
So we try to wait for apply finished when we exec publish version.
It is important to note that this solution is a temporary one and does not completely solve the problem of unstable query time, i will reconsider the primary key publish version mechanism and solve the problem in the future pr.
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

run starrocks_admit_test

run starrocks_admit_test


Lab 1 / kubectl cluster-info dump : error: missing apiVersion or kind and cannot assign it; no kind is registered for the type core.NodeList

$ kubectl cluster-info dump
error: missing apiVersion or kind and cannot assign it; no kind is registered for the type core.NodeList
$ kubectl version --short
Client Version: v1.11.0
Server Version: v1.10.3
Recommendation : Update docs and deploy Kubernetes version 1.11.2 or 1.11.0.

We'll look at a better info for troubleshooting section, but don't believe it's needed now in the create cluster lab.


a minimized window incorrectly reports itself as visible

After a window is minimized, document.hidden and document.visibilityState report respectively false and "visible".  The window.is_visible function reports the same.
This seems to contradict this.
Possibly related, window.set_minimized(false) sems to have no effect.  Instead, to unminimize a window you first have to hide it, which seems unfortunate:
    if req.method == "show" {
      window.set_visible(false); // needed if window is minimized
      window.set_visible(true);
    }

Electron does have a isMinimized method - but is not needed because show works on minimized windows.
This is on Fedora Linux 34 running Gnome/Wayland.

Minimizing a window is not the same as hiding it. window.set_minimzed(false) probably won't bring the window to the foreground so you probably have to combine it with window.set_focus(true)

"Minimizing a window is not the same as hiding it so document.hidden ans document.visibiltyState are correct."
The former statement does not imply the latter.  The link I gave explicitly states that a minimized window should be considered "hidden".
Electron does this IMO correctly, for what it's worth.
"window.set_focus(true) should force it be on the current desktop unminimzed and focused."
Doesn't work for me.  I just get a notification that the windiow "is ready" but it isn't made visible.  I tried variations of:
    if req.method == "show" {
      window.set_minimized(false);
      window.set_visible(true);
      window.set_focus();
    }

(Note set_focus doesn't take an argument.)


fix(4.3.0): typescript 4.8 issues, generation performance regression

Note: No need to back merge this.

Closing this PR but keeping the branch.


Format of start and end attributes for all_day events

Hey,
Thanks for this add-on. Its great and really valuable.
I am using a template to parse the data in each calendar attribute in order to find upcoming events etc.
However after updating to the most recent version I am having an issue that events that are "all_day" have a start and end attribute in the datetime.date format, where as before this was in the datetime.datetime format.
The impact is that my template now needs a check to see what format the start attribute is.
Are you able to update the attribute back to the previous format?
Hope this makes sense and isnt too hard. Thanks
This is what it is now:

summary: test event
start: '2023-05-18'
end: '2023-05-19'
all_day: true
description: ''
location: ''
categories: []
sensitivity: Normal
show_as: Free
attendees: []

However I am sure previously the format was:

summary: test event
start: '2023-05-18T14:15:00+00:00'
end: '2023-05-18T15:30:00+00:00'
all_day: true
description: ''
location: ''
categories: []
sensitivity: Normal
show_as: Busy
attendees: []

Sorry, no. HA Core requires them to be as a Date to be properly recognised as an all day event. And in actual fact (if I remember correctly) this is what other systems such as Google Calendar user as well, so it is better to be consistent. I think also Microsoft do the same thing. Not in front of a PC now so can’t check, but pretty sure that is the case.

Cool, good to know in which case I will update the template instead.
Thanks for the quick response!


When a doc page (that was meant to be loaded as an iframe inside the …

…main page) is loaded directly, detect that and redirect to the proper one.
Fixes #248.

Sorry for not mentioning this earlier. I have tested this locally. I think it's somewhat difficult to ensure (or even define) correctness when it comes to web technologies, but it is 1) an improvement and 2) targeted to a very specific case (window.parent == window -- which, according to https://developer.mozilla.org/en-US/docs/Web/API/Window/parent should never throw an exception) that is broken as is. So I think it's reasonable to deploy this and see if it behaves.


Does patch operator really require cluster-wide permissions?

I've configured a ServiceAccount (patch-operator) with permissions to read and modify secrets and configmaps in a particular namespace. I have this role:
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: patch-operator
rules:
- apiGroups:
  - ""
  resources:
  - secrets
  - configmaps
  verbs:
  - create
  - update
  - patch
  - get
  - list
  - watch
  - delete

And this rolebinding:
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: patch-operator
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: patch-operator
subjects:
- kind: ServiceAccount
  name: patch-operator

But when I deploy a patch that attempts to read from a ConfigMap and write to a Secret:
apiVersion: redhatcop.redhat.io/v1alpha1
kind: Patch
metadata:
  name: dex-config
spec:
  patches:
    dex-config:
      patchTemplate: |
        data:
          dex.config: "{{ (index . 1).data.config }}"
      sourceObjectRefs:
      - apiVersion: v1
        kind: Secret
        name: dex-config
        namespace: '{{ .metadata.namespace }}'
      targetObjectRef:
        apiVersion: v1
        kind: ConfigMap
        name: argocd-cm
        namespace: '{{ .metadata.namespace }}'
  serviceAccountRef:
    name: patch-operator

I see the manager logging:

E0919 20:29:05.707142       1 reflector.go:138] pkg/mod/k8s.io/client-go@v0.24.2/tools/cache/reflector.go:167: Failed to watch /v1, Kind=Secret: failed to list /v1, Kind=Secret: secrets is forbidden: User "system:serviceaccount:lars-sandbox:patch-operator" cannot list resource "secrets" in API group "" at the cluster scope

The SA demonstrably has appropriate permissions in the namespace, for example, I can do this:
TOKEN="$(oc sa get-token patch-operator)"
kubectl --token="$TOKEN" patch cm argocd-cm -p '{"data": {"dex-config": "this is a test"}}'
configmap/argocd-cm patched

Why is the patch operator trying to list resources in the cluster scope, rather than using the namespace scope? I don't want the service account to have cluster-wide Secrets access.

I am experiencing the same issue. It may be because sourceObjectRefs[].namespace is not taken into account, so your patch would be applied to all secrets with name dex-config (max one per namespace). Did you figure it out or you simply gave cluster-wide permissions ?

We just assigned cluster-wide permissions (and then realized that we didn't need the patch operator for what we were trying to do after all).


[WIP] 1.0.0 release

#63
What is done

[x] Keyword arguments were replaced with normal arguments
[x] Added dynamically built and included module that holds methods from json_schema for classes that inherit from Surrealist::Serializer

TODO

[x] Add benchmarks for associations
[ ] See how else performance could be improved
[x] Update README with ORMs section
[x] Update ROADMAP

@AlessandroMinali do you have ideas or suggestions what can be improved performance-wise or in general before the release?

Actually, I have done some profiling right now, and it seems that the most expensive operation in the whole gem was String#match :)
Measure Mode: wall_time
Thread ID:<PHONE_NUMBER>2540
Fiber ID:<PHONE_NUMBER>4260
Total: 21.248953
Sort by: self_time

 %self      total      self      wait     child     calls  name
  6.08      1.713     1.291     0.000     0.423   403940   String#match
  3.90      8.274     0.829     0.000     7.446   364374  *Hash#each
  3.10      3.088     0.658     0.000     2.430   403940   <Module::Surrealist::TypeHelper>#dry_type?

This is stupid, so I am going to fix that part of TypeHelper

More progress:
# ruby 2.5.0p0 (2017-12-25 revision 61468) [x86_64-darwin16]
# -- Instance --
# Comparison:
#   Surrealist: instance through .surrealize:    28945.6 i/s
#   Surrealist: instance through Surrealist::Serializer:    22889.2 i/s - same-ish: difference falls within error
#   AMS: instance:     1684.5 i/s - 17.18x  slower
#
# -- Collection --
# Comparison:
#   Surrealist: collection through Surrealist.surrealize_collection():       15.0 i/s
#   Surrealist: collection through Surrealist::Serializer:       12.8 i/s - 1.17x  slower
#   AMS: collection:        6.1 i/s - 2.44x  slower
#
# --- Without AMS logging (which is turned on by default) ---
#
# -- Instance --
# Comparison:
#   Surrealist: instance through .surrealize:    36503.6 i/s
#   Surrealist: instance through Surrealist::Serializer:    27772.8 i/s - 1.31x  slower
#   AMS(without logging): instance:     4751.2 i/s - 7.68x  slower
#
# -- Collection --
# Comparison:
#   Surrealist: collection through Surrealist.surrealize_collection():       15.2 i/s
#   Surrealist: collection through Surrealist::Serializer:       12.0 i/s - 1.27x  slower
#   AMS(without logging): collection:        6.1 i/s - 2.50x  slower
#
# --- Associations ---
#
# -- Instance --
# Comparison:
#   Surrealist (associations): instance through Surrealist::Serializer:     4122.8 i/s
#   Surrealist (associations): instance through .surrealize:     4056.9 i/s - same-ish: difference falls within error
#   AMS (associations): instance:     1721.8 i/s - 2.39x  slower
#
# -- Collection --
# Comparison:
#   Surrealist (associations): collection through Surrealist.surrealize_collection():        2.0 i/s
#   Surrealist (associations): collection through Surrealist::Serializer:        2.0 i/s - 1.02x  slower
#   AMS (associations): collection:        1.3 i/s - 1.52x  slower


Fixed cdr compile error when using ivy

Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[x] Build (npm run build) was run locally and any changes were pushed
[x] Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type
Please check the type of change your PR introduces:

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?
See https://github.com/ionic-team/ionic/issues/18403
Issue Number: 18403
What is the new behavior?
Fixes a problem with ivy compiler
Does this introduce a breaking change?

[ ] Yes
[x] No

Other information
I didn't test if it actually fixes the ivy compiler

Well I just realized this file is autogenerated.


CollapseBox applies hover styles to child Box components when an onClick handler is attached

I noticed this issue when trying to dynamically apply the label of a CollapseBox component upon the user clicking on the "more" button. If I remove the onClick handler from the CollapseBox below, the gray background hover style does not apply.
Olive LDK Version: 3.3.0, although I briefly tested 3.4.0-beta.1 and the issue was still present.
Steps to reproduce:

Create a new whisper
Paste the following code:

const { whisper } = require('@oliveai/ldk');

whisper.create({
  label: 'Hello world',
  components: [
    {
      type: whisper.WhisperComponentType.CollapseBox,
      open: false,
      // This onClick handler somehow triggers bg hover styles to the Box component below
      onClick: () => {
        console.log('foo');
      },
      children: [
        {
          type: whisper.WhisperComponentType.Markdown,
          body: '# this is fine'
        },
        // The component below has hover styles applied to it
        {
          type: whisper.WhisperComponentType.Box,
          direction: whisper.Direction.Vertical,
          justifyContent: whisper.JustifyContent.Left,
          children: [
            {
              type: whisper.WhisperComponentType.Markdown,
              body: '# this is not fine'
            }
          ]
        }
      ]
    }
  ]
});

Screenshot:

Hi @kevinfiol!  Thank you for bringing this issue to our attention.  We'll get back to you when we have a fix in place.

Coming in V27 (tomorrow or right after Thanksgiving), per today's call.

Fixed by HELPS-1702


Use Travis CI to run flake8 tests on all pull requests

@nccgroup would need to turn on the switch for this repo at https://www.travis-ci.org/nccgroup
http://flake8.pycqa.org will flag the Travis CI build if there are Python syntax errors or undefined names.
E901,E999,F821,F822,F823 are the "showstopper" flake8 issues that can halt the runtime with a SyntaxError, NameError, etc.  Most other flake8 issues are merely "style violations" -- useful for readability but they do not effect runtime safety.  This PR therefore recommends a flake8 run of these tests on the entire codebase.

F821: undefined name name
F822: undefined name name in __all__
F823: local variable name referenced before assignment
E901: SyntaxError or IndentationError
E999: SyntaxError -- failed to compile a file into an Abstract Syntax Tree

Thanks for the PF, we are not using Travis that often right now but maybe I will update it in the future.


[incubator/kafka] If RBAC is enabled in the cluster, the init container needs permissions

@benjigoldberg
What this PR does / why we need it:
This optionally creates a service account with needed permissions for the Kafka init container. On an RBAC enabled cluster the expose remote is not able to complete due to permissions needed.
Special notes for your reviewer:
In addition to RBAC which is most of the PR, this also adds an additional label to the services created. We have a custom ingress solution and need to be able to identify which service is tied to a pod since our ingress selects only on services. In order to minimize changes, I reused the same logic that the pod is labeled with. If there's a desire to not label a service with 'pod' I'm happy to adjust this label, but in this case the service will always be a 1:1 mapping to a pod, so it seemed to make sense.

/ok-to-test

@ephur thanks for the PR and the improvement to the chart!

/lgtm


[INLONG-2176] Add histogram metric and client-side metric output

Fixes #2176

Codecov Report

Merging #2177 (ebf0ab4) into master (c2439b5) will increase coverage by 0.01%.
The diff coverage is 30.94%.

@@             Coverage Diff              @@
##             master    #2177      +/-   ##
============================================
+ Coverage     12.57%   12.58%   +0.01%
- Complexity     1194     1208      +14
============================================
  Files           414      417       +3
  Lines         35282    35735     +453
  Branches       5546     5590      +44
============================================
+ Hits           4436     4499      +63
- Misses        30049    30435     +386
- Partials        797      801       +4

Impacted Files
Coverage Δ

.../inlong/tubemq/client/common/TClientConstants.java
66.66% <ø> (ø)

...q/client/consumer/SimpleClientBalanceConsumer.java
0.00% <0.00%> (ø)

...emq/client/consumer/SimplePullMessageConsumer.java
2.88% <0.00%> (-0.06%)
:arrow_down:

...emq/client/consumer/SimplePushMessageConsumer.java
8.39% <0.00%> (-0.14%)
:arrow_down:

.../tubemq/client/producer/SimpleMessageProducer.java
12.50% <0.00%> (-0.57%)
:arrow_down:

...e/inlong/tubemq/corebase/metric/AbsMetricItem.java
75.00% <0.00%> (ø)

...ng/tubemq/corebase/metric/GaugeNormMetricItem.java
100.00% <ø> (ø)

...ng/tubemq/client/consumer/BaseMessageConsumer.java
6.20% <3.70%> (-0.05%)
:arrow_down:

...inlong/tubemq/client/producer/ProducerManager.java
14.21% <9.09%> (+0.03%)
:arrow_up:

.../inlong/tubemq/client/config/TubeClientConfig.java
12.80% <13.04%> (+0.02%)
:arrow_up:

... and 14 more

Continue to review full report at Codecov.

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


Rename the api group name to be healthcheck.config.k8s.io

This PR renames the health check api group to be healthcheck.config.k8s.io, which is more OSS compared to the old one.
Fixes #3800

I assume config.k8s.io is reserved for core k/k resources. Since the healthcheck is under kpt repo now, maybe you can consider using kpt.dev, like config.healthcheck.kpt.dev? How do you plan to suggest HealthCheck to the kpt users?
CC @droot @mortent @justinsb  for inputs

The group is not reserved by kubernetes, at least from this doc. :-) https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#-strong-api-groups-strong-
I happy to change the group name to be more appropriate. waiting for advice;-)

We have used config.k8s.io in the past, but I think we prefer to use something under the kpt.dev domain.

Thanks for the context. Changed to config.healthcheck.kpt.dev.


parse_block_fix

 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.formath seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Is it possible to capture Sound to OBS or any Stream programs?

"The title is the content"

After connect, there will be a new recording device. Just add that device to OBS or other recording software.

Can't Find "new recording device" like program name or sound device, recording system captures only system sound (like realtek 3.5mm) or programs WITHOUT audioplayback. is there any way to record the bluetooth device sounds?

I have same question, I notice there is A2DP SNK device in device manager.
But it didn't show up in system neither recording device setting nor playback device setting.
And also not show up in OBS audio input capture or audio output capture device list.

I think this could be a system limition ? (Windows 11 23H2 22631)

@kgy9948 @shugen002
First connect BT output device in AudioPlaybackConnector.
Then play some music in that output device. (To make recording device active, otherwise it won't show in below step)
Open OBS, click Settings, Audio, select "Line (Device Name A2DP SNK)" in Mic/Auxiliary Audio.
Then you can see that device in Audio Mixer, you can now start recording.


Blank space shows when adding new rows

Referencing https://github.com/angular-ui/ng-grid/issues/2535#issuecomment-72177312
The issue doesn't seem limited to the infinite scroll, but happens when adding data.
I'm not quite sure what is causing it; but I can reproduce it by

Go to http://ui-grid.info/docs/#/tutorial/112_swapping_data demo
Adding a few lines then scrolling down
Continue to add lines, after 20+ lines added, you'll see a gap appear and will increase as you add more lines.
If you scroll up, the gap vanishes.

This happens due to the threshold check in GridRenderContainer's adjustRows.
It looks to see if the new scrollTop value is greater than the previous one and the new row index is greater than the previous one plus the "scroll Threshold".  This condition doesn't match because the new row index is much much less than the previous one because the scroll percentage is much less. i.e. the same scrollTop position on a canvas of 40 rows is very different than on a canvas of 30 rows.
The change that needs to be made is most likely taking the difference in scroll percentages into account and matching the row index different against that.

Fixed with 509e0071b192


Feature: Blog App Views Implementation

This pull request addresses the following tasks:

Implemented views for the All Users page based on the wireframe design.
Created templates for the Single User page, All Posts by a given User page, and Single Post page.
Added styling elements to match the wireframes, focusing on functionality first.

Changes Made

Created ERB templates for each page in the views directory.
Used methods from the Blog App models to process data and populate views.
Added minimal styling to ensure functionality and navigation.

Thank you for taking the time to review, @OyePriscilla.


Make collection of lower/upper bounds configurable

Storing lower/upper bounds might significantly increase the size of metadata for datasets with a big number of columns, which can degrade the performance of metadata operations. In most cases, users cluster/sort their data by a subset of data columns to have fast queries with predicates on those columns. In my view, it is reasonable to have a list of columns for which we want to collect stats and that should be configurable by the user.
Another option here is to add a flag to keep stats only for top-level columns. I believe the first approach is more flexible and will help us to properly support nested datasets. This will be really beneficial in light of upcoming changes for nested data in Spark.
This feature should coexist with #113.

I am wondering about the best way to implement this feature.
A few ideas that came to my mind are below.
Option 1 (TableProperties)
We will have to add multiple new properties.
For example, we might use something like this:
metrics.collection.enabled
metrics.collection.column-delimiter
metrics.collection.bounds.enabled
metrics.collection.bounds.columns

Instead of storing a list of columns, we can store a regular expression.
Then we will be able to construct a MetricsSpec based on those properties and pass it to writers.
Option 2 (Extend Metadata)
The previous option is a bit cumbersome. Alternatively, we can store a MetricsSpec directly in the metadata (similar to PartitionSpec) and expose an API to update it. Also, users will be able to provide a correct MetricsSpec while creating tables.
@rdblue any suggestions on this?

I'd prefer the simpler table property approach because it can be configured using existing SQL DDL (SET TBLPROPERTIES). Here's what I would do to keep the configuration small:

Define modes: full, counts, and none to express all metrics, just null/value counts, and no metrics
Allow setting a column default: metadata.metrics.default=full
Add column-level config: metadata.metrics.column.(column-name)=counts to allow per-column tuning

That way, the configuration stays simple and users can choose how to minimize the amount of configuration properties they need to set by controlling the default and then updating individual columns from there.

That's a clean way to control it! Let me go ahead and implement this.

@rdblue in light of recent changes, am I correct that this PR is about value_counts, null_value_counts, lower_bounds, upper_bounds only?

@aokolnychyi, I think that sounds good.


Fix the extension of the provider entrypoint

This PR should have an additional commit but GitHub has some problems today. On top of that - the .mjs change, unfortunately, broke some stuff because your transpiled files don't have explicit extension in relative imports. @mellson is working on a broader fix for this stuff in: https://github.com/partykit/partykit/pull/136


BUG: error processing signature

2023/02/19 23:34:28 error processing signature: executing scorecard-api call: Post "https://api.securityscorecards.dev/projects/github.com/ben-manes/caffeine": context deadline exceeded

See github action. Fails on the first attempt, succeeds on the second. Appears to be an intermittent problem that has occurred on multiple runs.

Happening again
https://github.com/ben-manes/caffeine/actions/runs/5679780844/job/15392599301

Happening again https://github.com/ben-manes/caffeine/actions/runs/5679780844/job/15392599301

We had an API outage that was resolved an hour ago. Since the issue was opened we've also added a retry, which should help with the initial intermittent problem.

wonderful, thanks! I'll close for now since it's understood and hopefully resolved.


Updated README file and fixed title of ariaMisclosure_tutorial

@rzinke can you refactor the changes. perhaps close, update and re-issue the PR of changes?


refactor: rename identifiers throughout the application

Motivation
Consistent naming will help understand the value of the identifier

Issues closed
closes #14

Compatibility tests

[ ] All tests pass
[ ]  New test were written

Intended version

[ ] Patch
[ ] Minor
[ ] Major

ignore checks (adjustments in future PR)


Fix switching accounts auth problem

Currently there is a problem that you can't switch account with new auth logic (after we make auth state reactive), my guess this is because we fire config event too late and in this method we wait for the last event which never will be emited because by the time we run send config we already missed this.
This PR just tries to take the last auth value, I'm not sure that maybe I should use currentAuthStatusOrNotReadyYet instead, but I think it should be not possible to run into config event without non init auth status observable.
Test plan

Try to switch accounts
Try to log out completely and sign in in multiple accounts

Changelog

I am not seeing the problem you report, though. Switching accounts does work for me. What is the problem that you are seeing?

It looks like it's not always reproducable, I've seen this problem yesterday and now I can't reproduce this for some reason. @kalanchan also has seen this so this is not my local machine problem.
The problem itself is when you try to switch account, UI doesn't pick up this change even though I see toast about that I have signed in on the instance.

I'm going to merge this one just to make sure that this problem won't happen again (I actually think that some PR from yesterday slightly changed ordering of auth events streams, I saw that for auth status was added skip operator) so probably that's why I don't this problem with auth anymore.