Improved crash logging & handling (EXPOSUREAPP-2572)

Relates to
EXPOSUREAPP-2572
Description
This PR adresses improved bug/problem logging and handling. It is designed to support developers & testers first (deviceForTesters) and the corresponding UI is integrated in the so called 'Testmenu'.
Improvement

called Exceptions can be tracked and processed with additional metadata (api version, build version, manufacture, etc.)
if available corresponding logs are attached to crashreport
complete report can be shared via Email, Messenger or personal utility to Developers or interested parties.

Note

additional relevant bug-cases have to be defined or added from time to time
to trigger a bugevent manually call exep.reportProblem (inside Bugreporter Class).

Screens

If we one day see something similar in the production builds for common users would be awesome.
Are there plans to also log timings of tasks/transactions to discover time out related problems?

Currently can't deploy the APK, getting a build error:
1/home/darken/git/cwa-app-android/Corona-Warn-App/build/tmp/kapt3/stubs/deviceForTestersDebug/de/rki/coronawarnapp/util/di/ApplicationComponent.java:8: error: [Dagger/MissingBinding] @de.rki.coronawarnapp.util.di.AppContext java.lang.String cannot be provided without an @Provides-annotated method.
public abstract interface ApplicationComponent extends dagger.android.AndroidInjector<de.rki.coronawarnapp.CoronaWarnApplication> {
                ^
      @de.rki.coronawarnapp.util.di.AppContext java.lang.String is injected at
          de.rki.coronawarnapp.bugreporting.processor.DefaultBugProcessor(context, …)
      de.rki.coronawarnapp.bugreporting.processor.DefaultBugProcessor is injected at
          de.rki.coronawarnapp.bugreporting.BugReportingModule.processor(processor)
      de.rki.coronawarnapp.bugreporting.processor.BugProcessor is injected at
          de.rki.coronawarnapp.bugreporting.reporter.DefaultBugReporter(…, processor, …)
      de.rki.coronawarnapp.bugreporting.reporter.DefaultBugReporter is injected at
          de.rki.coronawarnapp.bugreporting.BugReportingModule.reporter(reporter)
      de.rki.coronawarnapp.bugreporting.BugReporter is requested at
          de.rki.coronawarnapp.util.di.ApplicationComponent.getBugReporter()[WARN] Incremental annotation processing requested, but support is disabled because the following processors are not incremental: androidx.room.RoomProcessor (DYNAMIC).

> Task :Corona-Warn-App:kaptDeviceForTestersDebugKotlin FAILED

Awesome @BMItter !
@vaubaehn We're discussing it, would love to include it for power users, but let's see.


Fixed incomplete trace during const schema validation

Summary:
Added the field name to trace during non-nullable validation
Issue Reference(s):
Fixes #638
Build & Testing:

[x] I ran cargo test successfully.
[x] I have run ./lint.sh --mode=fix to fix all linting issues raised by ./lint.sh --mode=check.

Checklist:

[x] I have added relevant unit & integration tests.
[x] I have updated the documentation accordingly (if applicable).
[x] I have performed a self-review of my own code.

/claim #638


TR: use hostname from CRConfig if only a single TR in CRConfig

In situations where there is only a single TR in the CRConfig but actually multiple TRs in the system, using the server hostname in zone generation leads to the creation of invalid mname (master name) field in the SOA record unless the server hostname actually matches the single hostname in the CRConfig. In this scenario, it's preferable to just assume the hostname of the single TR in the CRConfig so that the resulting SOA mname is a real, resolvable name. That way all the TRs in the system will use the same SOA mname.
Otherwise, TR servers that aren't in the CRConfig will generate an SOA mname like my-tr.mycdn.example.com without actually resolving that to an A/AAAA record.

Which Traffic Control components are affected by this PR?

Traffic Router

What is the best way to verify this PR?

mvn clean test
If this is a bugfix, which Traffic Control versions contained the bug?

all

PR submission checklist

[x] This PR has tests
[x] bugfix, no docs required
[x] very minor bug fix, doesn't warrant a changelog entry
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

TR Ultimate Test Harness workflow fails until #7202 is addressed for CDN in a Box for developers


#27 Generate documentation for views that are under different root paths

Description: This PR resolves #27 . It allows to configure in Django settings the root paths of the services whose documentation is to be generated.

Modified ApiSchemaGenerator so that it takes the prefixes from the settings and returns the proper endpoints. File: edx_api_doc_tools/conf_utils.py.

Added get_endpoints_prefixes() method to return the prefixes from Django settings, in case no root paths were declared returns “/api/” as the default prefix. File: edx_api_doc_tools/conf_utils.py.

Updated the reference schema with the new generated schema so the test get_data_view() passes and the actual schema equals the reference schema. File: tests/expected_schema.json.

Added the explanation of how to specify the root paths in the settings file. File: docs/adding.rst.

@felipemontoya
@mariajgrimaldi
@morenol

Thanks for the pull request, @magajh! I've created OSPR-4996 to keep track of it in JIRA, where we prioritize reviews. Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.

@magajh Thank you for your contribution. Please let me know once it is ready for our review.

@natabene it's ready for review. Thank you!

Wanted to note that https://github.com/edx/api-doc-tools/pull/51 was just merged, and it solves a similar (if not the same) issue.

@magajh Even though your pull request wasn’t merged, please take a moment to answer a two question survey so we can improve your experience in the future.


[Azure Search] Remove inheritdoc and improve SearchCredentials documentation

<inheritdoc /> is not supported by the .NET API browser. As a workaround, I'm copying documentation instead. Also adding more detail to SearchCredentials per feedback from Heidi.
Once this is in the preview SDK, I'll merge it back to the GA SDK.
FYI @HeidiSteen @Yahnoosh @mhko @jeji1101

Description

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please add REST spec PR link to the SDK PR
[x] I have read the contribution guidelines.
[x] The pull request does not introduce breaking changes.

General Guidelines

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[x] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

minor inconsistancy -- not an error, just noting it:  "otherwise, false" vs "false otherwise"
Customizations/Search/Models/ExtensibleEnum.cs
Lines 73 and 88
On the short parameter descriptions, some have periods and some don't
Customizations/DataSources/DataSourceOperations.Customization.cs
Customizations/Indexers/IndexersOperations.Customization.cs
Customizations/Indexes/IndexesOperations.Customization.cs
unfamiliar HTML code -- I've never seen
There are 9 instances -- maybe do a search on the PR?
Here is one:
Customizations/Indexers/IndexersOperations.Customization.cs
Line 64
true if the indexer exists; false otherwise.

I approve the PR as long as the  is valid HTML syntax.

@HeidiSteen Ironically, it's the tags you didn't recognize that turned out to be the correct ones. This is technically .NET XML docs, not HTML, which can fool me sometimes. Not all HTML tags are supported by the .NET API Browser. In this case, <c></c> is supported, because it's how references or emphasis is indicated in .NET XML docs. Looking at how the existing docs are rendered on docs.microsoft.com, it appears that <b></b> is not supported, so I'm going to replace all the b's with c's.

@UD1412 Would you mind approving using your other GitHub account, @updixit? The PR needs to be approved by an account with merge permissions to the search-preview branch.

@brjohnstmsft @HeidiSteen is this ready to be merged.
We are in middle of upgrading our repo, so if this PR is ready to be merged, this has to be approved and merged today, else we will close this PR and you will need to open a new PR against the upgraded repo.

#sign-off

#sign-off

#sign-off

@azuresdkci retest this please


Fixed #28408 -- Added error message when updating with annotated expressions on joined fields.

Ticket: #28408

to aim of this pr is to generate better error message than before. I'm not sure how to document this. I didn't find a similar case.

passed for fellow review. hopefully, after their review, it would be clear what needed to be added to get this in.

@auvipy You've marked "Needs documentation" flag, so you should know what kind of documentation you expected :man_shrugging: .

Hi @felixxm, I tried to expand evaluating the expressions and added your new test cases. Could you review again?

Thanks for corrections, @charettes

@pope1ni Are you fine with the current state?

Yes.


Kotlin 2.0.10.

e: [ksp] No providers found in processor classpath.
e: Error occurred in KSP, check log for detail

> Task :selekt-java:kspJmhKotlin FAILED

> Task :selekt-android-sqlcipher:compileDebugKotlin

> Task :selekt-java:lintAnalyzeJvmTest
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':selekt-java:kspJmhKotlin'.
> A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction
166 actionable tasks: 141 executed, 21 from cache, 4 up-to-date
   > Compilation error. See log for more details

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':AndroidLibBenchmark:compileReleaseAndroidTestKotlin'.


Feature request: Increasing tolerance for missing whitespaces for relational algebra

Would it make sense to increase the tolerance of RelaX for missing whitespaces when using symbols for operations in relational algebra?
We already implemented it in our fork, but I do hesitate to create a pull request, because I am not sure yet, if the changes of the relational algebra grammar really work fine for all cases. I would appreciate if someone checked it.
In our fork we changed the grammar of relational algebra in this commit: https://github.com/mafo3186/relax/commit/9b7818c750f3c86dc8cea62d4df115f2248c5cb2
gh pages: mafo3186/relax with gist
This works anyway (with whitespaces)
π Name, SSN (
    σ month(date(Bdate)) = month(now()) ∧
        day(date(Bdate)) = day(now()) (
            STUDENT
     )
)

After changing the RA-grammar, this works, too:
πName,SSN(σ month(date(Bdate))=month(now())∧day(date(Bdate))=day(now())(STUDENT))
There are still required whitespaces in cases like this (operater "=" comparing attributes): could anybody explain, why?
πName,CourseId(σSTUDENT.SSN=ENROLL.SSN (STUDENT⨯ENROLL))
Whithout whitespace, there will still be an error:
πName,CourseId(σSTUDENT.SSN=ENROLL.SSN(STUDENT⨯ENROLL))
Error:

Fehler: in Zeile 1: Expected "(", "gamma", "pi", "rho", "sigma", "tau", "{", "γ", "π", "ρ", "σ", "τ", or relationName but "=" found.

Any kind of help would be welcome. If you think, this might be a good additional feature, we would appreciate the integration in the original tool.

Note: I did not fetch the upstream with the last 11 commits, because I could not solve the conflicts (yet) and also am unable to run the newest release of relax locally (yet).
Background:
We (HSD, eild.nrw) make our students use RelaX to learn relational algebra. Our evaluation revealed that they were annoyed by error messages which do not lead to finding the error. We discovered that in most cases the message was triggered by missing whitespaces between operators or brackets, without telling that whitespace was missing.  We could not figure out why there should be spaces and decided to change the grammar.
Since I'm new to the community, I welcome any hints if I should do anything differently.

@mafo3186 If you create a pull request, I will gladly take a look at it.

@r-prem Thank you, sounds great!
Before I do it: Is there by chance any way to create a pull request without fetching the upstream first? I guess not.

I did not fetch the upstream with the last 11 commits, because I could not solve the conflicts (yet) and also am unable to run the newest release of relax locally (yet).

I will try again today.


Fixes

Codecov Report

Merging #1 into master will increase coverage by -3.62%.

@@            Coverage Diff             @@
##           master       #1      +/-   ##
==========================================
- Coverage   90.43%   86.82%   -3.62%
==========================================
  Files           7        7
  Lines         617      645      +28
==========================================
+ Hits          558      560       +2
- Misses         59       85      +26

Impacted Files
Coverage Δ

voropy/mesh_tetra.py
99.41% <ø> (ø)
:white_check_mark:

voropy/about.py
100% <100%> (ø)
:white_check_mark:

voropy/base.py
61.9% <7.14%> (-27.39%)
:x:

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 d043d3c...e70b205. Read the comment docs.


Problems installing Cytoolz

Installing Cytoolz can lead to permission errors on Windows if VS 2019 Desktop development for C++ is not installed. There should be a fallback to plain Python Toolz if Cytoolz is not available, but there needs to be a way to make the installation of Cytoolz optional.
It might require tutorial instructions to install Cytoolz separately.

Apparently, Cytoolz 0.12.0 will install even if you have not downloaded VS 2019 Desktop development for C++, but you do need to run pip install cytoolz before installing Lexos. If using Anaconda, it may be preferable to run conda install -c anaconda cytoolz.
I won't close this issue until the documentation is updated at the least.

This issue has apparently been resolved. See:

https://github.com/pytoolz/cytoolz/issues/151
https://github.com/pytoolz/cytoolz/issues/163


[Snyk] Upgrade react-intersection-observer from 9.2.2 to 9.3.3

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade react-intersection-observer from 9.2.2 to 9.3.3.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 5 versions ahead of your current version.
The recommended version was released 21 days ago, on 2022-06-15.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Codecov Report

Merging #288 (c35821c) into main (f975fab) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #288   +/-   ##
=======================================
  Coverage   81.89%   81.89%
=======================================
  Files          28       28
  Lines         370      370
  Branches       55       55
=======================================
  Hits          303      303
  Misses         61       61
  Partials        6        6

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 f975fab...c35821c. Read the comment docs.


Applications: docs

Need to create documentation for apps development.

Need to mention dev console from task #522

Hello, I am an aspiring technical writer. I would love to help you guys with creating new documentation or updating old documentation if you are still in need.

Hello, I am an aspiring technical writer. I would love to help you guys with creating new documentation or updating old documentation if you are still in need.

@bravogeorge please contact me on Telegram (@bigromanov)


doc: when 'trust proxy' = true, req.ip stays a single ip

Before this change, the documentation stated that with 'trust proxy' set, both
req.ip and req.ips would be populated with the list of addresses from
X-Forwarded-For header.
This is true only for req.ips, while req.ip will only get the left-most entry.

Hi @muxator are you going to take another stab at the wording? Or you can open an issue about this and we can work on a PR -- in a PR review I can only give suggested changes around the areas changed, but it seems like other areas need wording changes, so not sure a good way to go about that on this PR if you didn't want to do them 👍


Error in "Obtain an Azure AD access token" and what are the various request json files?

First,
tokenEndpoint = "https://login.microsoftonline.com/{0}/oauth2/token"
should be
tokenEndpoint = "https://login.microsoftonline.com/{0}/oauth2/token".format(tennantId)
Also, each of these examples includes something like
appSubmissionRequestJson = "";  # Your submission request JSON
What is needed in that?  It's used but not set.  Unless null JSON is expected.

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

ID: 945eca76-6f63-3ea1-a667-bf670ab8d3a9
Version Independent ID: e77e4a75-589d-6ba3-95ca-58d7a721f072
Content: Python sample - submissions for apps, add-ons, and flights - Windows UWP applications
Content Source: windows-apps-src/monetize/python-code-examples-for-the-windows-store-submission-api.md
Product: uwp
Technology: publish
GitHub Login: @hickeys
Microsoft Alias: hickeys

We are changing the way we track issues filed from our documentation pages: please see this blog post for more details. Right now, this issue is being closed but if you feel it is still valid and has not been addressed, please re-open it with any more available information. Please note that if your question is more general and not related to documentation, Microsoft Q&A is a great way to get questions answered.


Invalid blockwise message stored

Hello,
the following section does store a message copy in linked_list_blockwise_sent_msgs even if the message that is sent is no block-wise message (e.g. a COAP_MSG_CODE_REQUEST_POST used for registration updates). I'm not sure if this is actually a bug, but maybe someone knows details on this.
https://github.com/ARMmbed/mbed-coap/blob/c9b32f8a790dcf7f52444041789c73555d88e581/source/sn_coap_protocol.c#L508-L515
Regards,
Sebastian

In a earlier version there is a hint why those non-blockwise messages are stored, I'm not sure if it is valid though: https://github.com/ARMmbed/mbed-coap/commit/aa17c223ddc9aeeca4352477c5a76d735c931643#diff-3f84b9912a0229ef13dff4882aff64b142dfaf05565e4d5101389ba59b100760L543


AttributeError: 'AsyncClient' object has no attribute 'cookie_jar'

Describe the bug
My configuration stopped working a few days ago. When I now try to reconfigure it it always fails with an unknown error.
To Reproduce
Steps to reproduce the behavior:

Go to the integrations page
Click on reconfigure
Use Login Proxy (without 2FA app key)
Unknown error is shown after submitting

Expected behavior
The integration should be configured correctly.
System details

Home-assistant (version): 2021.6.1
Hassio (Yes/No): Yes
alexa_media  (version from const.py or HA startup):  3.10.5
alexapy (version from pip show alexapy or HA startup):
Amazon 2FA is enabled (y/n). We will not debug login issues if unanswered: yes

Logs
2021-06-06 10:58:21 DEBUG (MainThread) [custom_components.alexa_media.config_flow] Using existing login
2021-06-06 10:58:21 DEBUG (MainThread) [alexapy.alexalogin] Unable to generate OTP; 2FA app key not configured
2021-06-06 10:58:21 DEBUG (MainThread) [authcaptureproxy.auth_capture_proxy] Refreshed 3 modifiers: ['autofill', 'prepend_relative_urls', 'change_host_to_proxy']
2021-06-06 10:58:21 DEBUG (MainThread) [custom_components.alexa_media.config_flow] Starting proxy for t****s@f********g - amazon.de
2021-06-06 10:58:21 DEBUG (MainThread) [custom_components.alexa_media.config_flow] Found existing proxy_view
2021-06-06 10:58:21 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_protocol.py", line 422, in _handle_request
resp = await self._request_handler(request)
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_app.py", line 499, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_middlewares.py", line 119, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 202, in forwarded_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 24, in request_context_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 78, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 144, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 135, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 155, in post
return await super().post(request, flow_id)
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 63, in wrapper
result = await method(view, request, *args, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 109, in post
result = await self._flow_mgr.async_configure(flow_id, data)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 202, in async_configure
result = await self._async_handle_step(flow, cur_step["step_id"], user_input)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 260, in _async_handle_step
result: FlowResult = await getattr(flow, method)(user_input)
File "/config/custom_components/alexa_media/config_flow.py", line 356, in async_step_user
return await self.async_step_start_proxy(user_input)
File "/config/custom_components/alexa_media/config_flow.py", line 383, in async_step_start_proxy
self.proxy.session.cookie_jar.update_cookies(
AttributeError: 'AsyncClient' object has no attribute 'cookie_jar'

Your alexapy version is outdated. Please ensure its updated and you don't have a random version in your /config.

I'm on alexapy==1.25.1. But I'm using HACS - so I never did any changes to alexapy myself?

Remove and readd from HACS.

I have the same issue.  I have removed from HACS and re-added several times, no luck.  I have confirmed alexapy=1.25.1

Uninstalling from HACS, restarting, removing /config/deps/lib/python3.8/site-packages/alexapy*, reinstalling via HACS, restarting HA again seemed to clear it up for me

I tried removing, restart, installing - without luck. Also I don't have the /config/deps folder as nniehoff has - it's empty.
What should be the correct alexapy version? Because it seems to me that 1.25.1 is the latest?!

Remove and readd the integration in HA as the workaround.

Works! Thanks!

The true way to fix this is to switch to httpx or to remove the resume dialogue.

Has anyone managed a successful workaround? I've tried all the above steps (remove, restart, readd) and not had any success so far. I always get to the final step of the configuration dialog where it asks you to confirm the generated 2FA code, and it fails with the above error.

Unfortunately, I also have the same problem. A new installation and deleting the .pickle did nothing for me either.
My alexapy is up to date.
Has anyone already found a workaround?

I finally got to work:
Install an Authenticator App on your phone.
Set up your Amazon account with 2FA.
Access Home Assistant using the mobile app on your phone.
-Enter Username ans Password
-Enter the CAPTCHA.
-Enter a 2FA code from your Authenticator App.

Remove and readd the integration in HA as the workaround.
You may need to delete the .pickle file too.

thanks! This works to me too!

This problem is still happening. What is necessary to get it fixed? Manual deletion of files as a workaround for months now.

Where is "the .pickle file"? I don't see one.

Where is "the .pickle file"? I don't see one.

login into ssh and then
cd config
find | grep .pickle
you will see it. Mine is under /config/.storage/

I managed to get it to work with the most recent version (v3.10.10) after doing the following steps:

remove integration in Home Assistant (Configuration -> Integrations -> Alexa Media -> Delete)
uninstall integration from HACS (HACS -> Integrations -> Alexa Media Player -> Uninstall)
check there is no pickle file (I think I deleted it in an earlier attempt)
restart Home Assistant
install v3.10.10 from HACS
go to Configuration -> Integrations and then follow installation instructions for the Integrations Page method exactly

When following the installation instructions, I used the settings for Login Proxy and left the default setting for the oauth ("mobile") login method as it was.
That finally fixed it for me!

Configuration -> Integrations -> Alexa Media only shows a Reconfigure button. No way to delete it that I can find.

@guystreeter while it was failing for me, I had two different entries for the failing integration. I think one of them had a "remove" function. However, it's possible I'm misremembering and I just ended up skipping that step and going straight to uninstall.

Has this ever been fixed? Encountering this endlessly today. Everything up-to-date.

@alandtse I'm also facing this issue. When is it planned for alexapy to switch to httpx? Alexapy shipping its own aiohttp was always a dirty hack causing issues like this unfortunately.

@alandtse I'm also facing this issue. When is it planned for alexapy to switch to httpx? Alexapy shipping its own aiohttp was always a dirty hack causing issues like this unfortunately.

The fact httpx doesn't have a websocket library may mean another path. The issue has nothing to do with the fact it has it's own aiohttp. Aiohttp didn't handle non-spec Amazon response with cookies so I had to patch it myself. That said, this can be easily fixed if someone figures out how to convert aiohttp cookies into a format that httpx can understand and back again. That's where this is breaking because I don't have any handoff code written yet. Actually, forcing authcaptureproxy down to 0.8.1 may be a workaround.

Handing cookies with httpx seems to be pretty straightforward. It allows for passing a cookiejar so you could share that between aiohttp and httpx
https://www.python-httpx.org/api/#cookies

Handing cookies with httpx seems to be pretty straightforward. It allows passing a cookiejar so you could share that between aiohttp and httpx
https://www.python-httpx.org/api/#cookies

Last I checked they weren't compatible. But if you figure it out, I will take a PR.

Seems that they're still not compatible as aiohttp is using its own implementation. How is the websocket authenticated? Cookie or authentication header? Couldn't you just use aiohttp for the websocket and httpx for everything else?

How is the websocket authenticated? Cookie or authentication header? Couldn't you just use aiohttp for the websocket and httpx for everything else?

It used to be cookies in the session object. However, the new websocket now explicitly calls for the cookies to be passed in the header. I haven't tested to see what happens if I clean the session object and only rely on the header cookies.
It seems really messy to include both. I may just revert auth_capture_proxy to use aiohttp since the only reason I swapped it was to avoid an issue with Tesla's interaction with aiohttp (that need is gone now). Aiohttp has little issues with random things so it seemed worth switching to avoid them.


Lighthouse report

Here is lighthouse report of current app: https://googlechrome.github.io/lighthouse/viewer/?gist=c66b549e98d9931bf477b06dcac5d321
There is a lot of room for improvements.

@naveed-ahmad I agree. Also, from a place where we are encompassing everyone and welcoming everyone, we should do a better job on accessibility. We left that one slide unfortunately.


Serialize entropy, if present, on an RST

We added the code directly as this needed to be rebased.


Breakpoint is not enabling for Groovy files

Type: Feature Request
I am trying to put Breakpoints for Groovy files debugging, but this Breakpoints feature is not working.
VS Code version: Code 1.81.1 (6c3e3dba23e8fadc360aed75ce363ba185c49794, 2023-08-09T22:22:42.175Z)
OS version: Windows_NT x64 10.0.22000
Modes:

Please file this on the repo for whichever extension is responsible for this, I assume the Java debug extension


How to make Editor Toolbar sticky inside an scrolling container?

I have a container with h={"900px"} overflowY={"scroll"}
Inside this container i have suneditor. Scrolling is working fine. But Editor toolbar does not stick to the container top.
Please Note : - If i do not put Editor in Scrolling container then toolbar sticks to the top of browser. Which is fine. But i want this to working in same way in scrolling container.

Please try it.
{
  stickyToolbar: -1
}

Please try it.
{
  stickyToolbar: -1
}

where to write this? For which class? I am using react.

Add to options.
Disable stickyToolbar.

Um.. The "stickyToolbar" is fixed on top in the "absolute" position.
Try positioning the top with "stickyToolbar".
{
  stickyToolbar: 50
}

I tried this, but it could not stop scrolling toolbar inside container.

Show me the html structure and style so I can test it


[aquamarine] Startup freeze on FreeBSD

Regression?
Yes
System Info and Version
 System/Version info
$ hyprctl systeminfo -c
Hyprland, built from branch main at commit 8b37e81374928856d8fd859b95a62c8bf4211901 portbld (?).
Date: Fri  9 Aug 2024 21:58:02 UTC
Tag: v0.42.0-4-g8b37e813 (aquamarine v0.3.1), commits: ?

flags: (if any)

System Information:
System name: FreeBSD
Node name: foo.bar
Release: 15.0-CURRENT
Version: FreeBSD 15.0-CURRENT #0 main-n271236-b3bbc6cc79a3: Wed Jul 17 22:47:30 UTC 2024 test@foo.bar:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL

GPU information:
vgapci1@pci0:0:2:0:	class=0x030000 rev=0x06 hdr=0x00 vendor=0x8086 device=0x1912 subvendor=0x1462 subdevice=0x7968
    vendor     = 'Intel Corporation'
    device     = 'HD Graphics 530'
    class      = display
    subclass   = VGA

os-release: NAME=FreeBSD
VERSION="15.0-CURRENT"
VERSION_ID="15.0"
ID=freebsd
ANSI_COLOR="0;31"
PRETTY_NAME="FreeBSD 15.0-CURRENT"
CPE_NAME="cpe:/o:freebsd:freebsd:15.0"
HOME_URL="https://FreeBSD.org/"
BUG_REPORT_URL="https://bugs.FreeBSD.org/"

plugins:

======Config-Start======

Config File: /tmp/hyprland.conf: Read Succeeded
debug {
      enable_stdout_logs = true
      disable_logs = false
}

exec-once = foot
exec-once = vkcube-xcb

======Config-End========

Description
Split from https://github.com/hyprwm/Hyprland/pull/6608. FreeBSD regressions cannot block merges.
Launching Hyprland manages to show default wallpaper but no windows appear. Neither mouse nor keyboard (including VT switch) work. Exiting Hyprland requires killing by timeout(1) or from another machine (e.g., serial console, ssh).
Affects DRM (Hyprland on VT console) but not Wayland (aquamarine-Hyprland on wlroots-Hyprland 0.41.2) session. AQ_NO_ATOMIC=1 doesn't help. Starting from a different VT doesn't help. Starting without Sway in background doesn't help.
How to reproduce
Start Hyprland from VT console such as /dev/ttyv0.
Crash reports, logs, images, videos
Runtime log and stacktrace

well it looks like a hang in udev_monitor_receive_device if I am reading it correctly but I have little clue as to what could be causing this.
libudev is likely compiled in release and thus some of the stack is missing but it looke like somewhere here

FreeBSD uses libudev-devd instead of systemd
libudev-zero was built with debug symbols, so the stacktrace in the log shows line numbers
udev_monitor_receive_device usage in aquamarine is similar to wlroots (where it works fine)
Hyprland shows wallpaper, so monitor stuff is likely a false positive

Could this be related to DMABUF instead? For example, FreeBSD currently lacks explicit sync.

yeah but your stacktrace shows it being stuck in udev_monitor_receive_device in a read syscall. Unless the stacktrace is wrong?
I'd assume it's stuck somewhere because the log is clearly empty in your case right after the event loop starts, unless you truncated the log.

Could this be related to DMABUF instead? For example, FreeBSD currently https://github.com/freebsd/drm-kmod/issues/278.

Explicit sync is disabled with render:explicit_sync = no which should not require any further action.
can you post a trace log? AQ_TRACE=1 HYPRLAND_TRACE=1 Hyprland and make sure debug:disable_logs = false before you launch

My guess is that there is nothing pollable and we dispatch outstanding once, which in sysd doesn't block but in BSD might. Try this hl patch:
patch.txt
unsure if this is correct, but it might work.

I've updated OP with the new log. After applying your patch Hyprland seems to work fine.

I assume the log is from patched, as it seems to run normally

I'll apply the patch, if anything happens after it and people report issues I'll just revert it. Doesn't hurt to try

FWIW, according to https://www.man7.org/linux/man-pages/man3/udev_monitor_enable_receiving.3.html udev_monitor_receive_device should return null if anything goes wrong (which I assume includes no event) so unless that manpage is sysd only that sounds like a bug in udev?

unless that manpage is sysd only that sounds like a bug in udev?

Need a smaller test case to reproduce without Hyprland. Other Wayland compositors (wlroots, smithay, kwin) didn't bump into this issue. Even Xorg uses udev_monitor_receive_device on FreeBSD: modesetting DDX and xf86-video-intel.
I'm not familar with libudev API myself.

at any rate, if the freeze is gone now on -git I'd consider this fixed

Agree. I've applied it downstream.


[general] Avoid double nested platforms

A necessary cleanup before we start cleaning dependencies. Almost certainly fully broken at this state, but opening this so @roblabs and @birkskyum are aware I'm working on it.
The next step is to cleanup the build infrastructure as the Node MR (#217) uncovered many issues.

This sounds like a great idea, @ntadej For the review it might be useful if you could share the cli commands you used to move the files around...

@ntadej , is this still releant? It seems reasonable to i.e. move macos from platform/ios/platform/macos to platform/macos, and so on, but is this branch maybe too dated at this?

I believe this is too far behind at this point, and it would be a lot of work to rebase, but we still have the pr as a reference.


Ability to forge/sign/inject endorsements

The changes in the PR are to support client application's ability to create, forge, sign, and inject new endorsements. I can provide working code example, just not sure where to put it in the repo.
Several functions were simply capitalized to be exported. A couple others were refactored to allow "helper functions" to be used instead of duplicating code.

Could you give me an  example about how to send a payment operation ?

@wade-liwei This PR is specific to creating/signing endorsements. Please open a new issue if you want to discuss something else.


The github bot should allow tbr reverts further back from top-of-tree

We needed to revert a Dart roll that was one commit back and the bot didn't land it: https://github.com/flutter/engine/pull/32496
The bot should land clean reverts TBR even if they are many commits back.
@godofredoc @keyonghan

/cc @ricardoamador could you please dup this one with the one you are working on?

Yes sir.

This is a duplicate of https://github.com/flutter/flutter/issues/108374


modified welcome page and other small  cosmetic corrections

Hi, yes i saw that error .I will try to fix it soon.
Thanks
בתאריך יום ד׳, 20 בספט׳ 2023, 13:39, מאת Amichai Ben-David <
@.***>:

@.**** requested changes on this pull request.
Looks good, but seems like there is an error and the workflow failed.
This is why I'm setting the "request changes"
—
Reply to this email directly, view it on GitHub
https://github.com/amichai-bd/fpga_mafia_wiki/pull/17#pullrequestreview-1635319948,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANZR34QMGHJ6Y2OHSN7OG2DX3LBWJANCNFSM6AAAAAA47UXMPU
.
You are receiving this because you authored the thread.Message ID:
@.***>

I I tried to find the problem by checking "sanity_check_build," but I couldn't figure out what's wrong. When I tried to push again, I got this message:
$ git push origin roman_branch
To https://github.com/amichai-bd/fpga_mafia_wiki.git
! [rejected]        roman_branch -> roman_branch (non-fast-forward)
error: failed to push some refs to 'https://github.com/amichai-bd/fpga_mafia_wiki.git'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. If you want to integrate the remote changes,
hint: use 'git pull' before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

following my previous Comment, I did "git pull, git add and git commit before"

In the log i can see the error:

I will try and fix it and push an update

ya, but you were missing the file "docs/TFM/projectTool/docusaurus.md"

Thanks, its weird because I could edit the site and every thing seems to be
ok.
The reason I couldnt push again was because I got errors in pull request?
בתאריך יום ד׳, 20 בספט׳ 2023, 17:59, מאת Amichai Ben-David <
@.***>:

ya, but you were missing the file "docs/TFM/projectTool/docusaurus.md"
—
Reply to this email directly, view it on GitHub
https://github.com/amichai-bd/fpga_mafia_wiki/pull/17#issuecomment-1727902258,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANZR34REMPLFBW542NHG4JDX3MADPANCNFSM6AAAAAA47UXMPU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks, its weird because I could edit the site and every thing seems to be ok. The reason I couldnt push again was because I got errors in pull request? בתאריך יום ד׳, 20 בספט׳ 2023, 17:59, מאת Amichai Ben-David < @.>:
…
ya, but you were missing the file "docs/TFM/projectTool/docusaurus.md" — Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANZR34REMPLFBW542NHG4JDX3MADPANCNFSM6AAAAAA47UXMPU . You are receiving this because you authored the thread.Message ID: @.>

Not exactly..
I suspect that the issue was that the file existed on you local machine, but you forgat to add it to the commit. So you were able run the site locally, but the github was missing the file and it failed

Thanks!
בתאריך יום ד׳, 20 בספט׳ 2023, 18:08, מאת Amichai Ben-David <
@.***>:

Thanks, its weird because I could edit the site and every thing seems to
be ok. The reason I couldnt push again was because I got errors in pull
request? בתאריך יום ד׳, 20 בספט׳ 2023, 17:59, מאת Amichai Ben-David < @
.
>: … <#m_-8855932093496651024_> ya, but you were missing the file
"docs/TFM/projectTool/docusaurus.md" — Reply to this email directly, view
it on GitHub <#17 (comment)
https://github.com/amichai-bd/fpga_mafia_wiki/pull/17#issuecomment-1727902258>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANZR34REMPLFBW542NHG4JDX3MADPANCNFSM6AAAAAA47UXMPU
https://github.com/notifications/unsubscribe-auth/ANZR34REMPLFBW542NHG4JDX3MADPANCNFSM6AAAAAA47UXMPU
. You are receiving this because you authored the thread.Message ID: @.>
Not exactly..
I suspect that the issue was that the file existed on you local machine,
but you forgat to add it to the commit. So you were able run the site
locally, but the github was missing the file and it failed
—
Reply to this email directly, view it on GitHub
https://github.com/amichai-bd/fpga_mafia_wiki/pull/17#issuecomment-1727920071,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANZR34RAJZFEPL656X3FFVTX3MBIFANCNFSM6AAAAAA47UXMPU
.
You are receiving this because you authored the thread.Message ID:
@.***>


I set the syn_bn   as True when doing multi GPU training, but the 3D AP is lower.

My environment is:
8*A6000
BATCH_SIZE_PER_GPU:4
batch_size:32
pytorch1.7.1
cuda11.1

I didn't do experiments with this large of a batch size, so unsure how performance is affected at these large batch sizes. I would recommend trying multiple runs at different batch sizes and different settings of sync_bn to see the performance if you are interested at these large batch sizes.


Score documentation

Hello,
After following recommendations from kubesec, most of my deployments get a score of 9 without any further recommendations, however there is a deployment that gets a score of 12.
Without extra notes, I cannot determine the difference between the deployments that score 9 and those that score 12.
Thank you!

@sublimino is there any documentation available on how the score gets computed

It's currently "Andy's Kubernetes threat model", so certainly deserves scrutiny.
It's internally modelled as  (+/-ve) points, but that could be renamed riskScore (or riskModifier etc) - any preference @stefanprodan? If we agree a key name I'll expose it in the response.

riskScore sounds good to me :)

The more points you score, the less risk you have though? what about secScore ?

Good point @naseemkullah! Will have a muse before I do it...


TypeError: Cannot read properties of null (reading 'get_label') at MultiSelect.svelte:75

In rare cases the line $: selectedLabels = selected.map(get_label)
https://github.com/janosh/svelte-multiselect/blob/8ab0d21a9793402fa8332bc9ced1fc3bcb340b24/src/lib/MultiSelect.svelte#L84-L85
raises
TypeError: Cannot read properties of null (reading 'get_label')
    at MultiSelect.svelte:75:33

Not sure exactly what is becoming null and what's trying to access null.get_label but
$: selectedLabels = selected?.map(get_label) ?? []

seems to fix it.

Hello, Janosh! First of all, thanks so much for this awesome component.
Getting straight to the point, I am running a lot into this specific error in my project using the library.

+    <MultiSelect bind:selected options={particleOptions} />

I believe I am using the component properly, and it has worked so far with this exact code until... it didn't for some reason. I am trying to search for the changes I made but... none seem relevant.
If you need to take a deeper look, everything is under this file in my repository.
Thanks again beforehand for all your effort. If you were able to somehow help me out on this one, it'd be awesome.
Hope you have a super nice day!

@jesi-rgb Thanks for reporting this! I'm also still seeing this same error but just in 1 one the dozen repos where I use svelte-multiselect.
https://github.com/sbsev/site/actions/runs/3200455674/jobs/5227373091#step:5:42
Have yet to figure out what exactly is going wrong and how to fix. https://github.com/janosh/svelte-multiselect/pull/122 apparently didn't solve the problem like I originally thought. Maybe comparing your repo with https://github.com/sbsev/site can reveal what sets them apart, i.e. why the error is only happening there.

Looks like my hunch about a circular module import was correct https://github.com/janosh/svelte-multiselect/pull/131/commits/75232710d2796b242a8833975f96fabea403e8b7.
v7.0.2 fixes it for real, at least on the repo I mentioned above: https://github.com/sbsev/site/actions/runs/3211769303/jobs/5250168078
Would be interested to hear if it solves your problem too.

 Cannot check right now but will tomorrow morning. Thanks anyways for your effort!

Janosh, this works perfectly now. Thanks SO much for your super quick attention and fix, you're literally the best.
Have a great Sunday!


Approving pipeline lists workflows twice

Component
web-ui
Describe the bug
Approving a pipeline lists its workflows twice. Duplicates are removed as soon as the pipeline starts.
probably a regression of #2757
System Info
ci.woodpecker-ci.org

Additional context

Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]

the database has correct records and after an reload it is fixed ... so that's most likely an WebUI bug, witch dont know what to do with getting the new created workflows pushed via eventstream (pubsub) again ...


[ISSUE #3667] upgrade rocketmq version to 4.9.5 andRocketmq request callback timeout

Fixes #3667
Motivation
Explain the content here.
Explain why you want to make the changes and what problem you're trying to solve.
Modifications
Describe the modifications you've done.
Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

@mxsm please fix the dependencies version error in the known-dependencies.txt file.

@mxsm please fix the dependencies version error in the known-dependencies.txt file.

I will

@xwm1992  fix it and resubmit pr again. PTAL~ thanks


compose typeahead: Add all public streams including unsubscribed streams.

Fixes: #5757.

This adds unsubscribed streams to typeahead with the basic logic of:

Changed source of typeahead to all streams and activity_score to -1 of unsubscribed streams.
Which means unsubscribed stream has the lowest position in stream name comparison but above those whose description matches. And then for lowest among those matched on the basis of description.

Which means always show unsubscribed streams to bottom but keep exactness first.
Testing Plan:

[x] node-tests

GIFs or Screenshots:

Updated with all the feedbacks and tests.
GIF:

@shubhamdhama I think maybe we want the symbol to be a bit further to the right; is that possible to arrange?  I think it'd look better eating into the bootstrap right side space than how it works here.

@timabbott Now there is no change in bootstrap-typeahead for the active-only-icon-display, but I'm finding it difficult to move the icon to the right padding of <a> tag with CSS : / Any help is welcomed. Another thing I noticed is that with current behavior if I have got a long stream name of an unsubscribed stream, then icon wraps to next line.

I would try doing something with a negative right margin?

Updated I've manually tested it a lot, but some manual testing before merging will be great.
@timabbott FYI

I tweaked the text to be a bit briefer, and merged this.  Thanks @shubhamdhama!


libpxgame.so hash mismatch

I've extracted the Kero Blaster data into ox0:data/kero. I keep getting a libpxgame.so hash mismatch.

Please be sure that your libpxgame.so is extracted from Kero Blaster 1.6.1, and is under  lib/armeabi-v7a folder.


added detailed GSSoC'24 contribution

This issue fixes Add GSSOC Contribution Details to Contribution Guide #91
Added GSSOC Contribution Details to Contribution Guide
Description
The contribution guide currently lacks details about how GSSOC'24 participants can contribute to the project effectively. It's important to provide clear instructions and guidelines to help GSSOC participants get started with contributing.
Instructions

Add information about GSSOC labels (gssoc, level-1, level-2, level-3) to the contribution guide.
Provide clear instructions on how GSSOC participants can find tasks that match their skills and interests.
Include any specific guidelines or tips for GSSOC participants to ensure a smooth contribution process.

Here is the updation screenshot:

This helps GSSOC'24 participants often look for tasks matching their skill levels. Labeling issues with level-1, level-2, level-3 allows participants to easily identify tasks that suit their expertise, fostering a positive contribution experience.

Increased Contributions: By making it easier for GSSOC participants to contribute, you're likely to receive more contributions during the program period, leading to project growth and improvement.

Hi @ashutoshgithubs , Can you review this PR and I would appreciate your feedback.

@ashutoshgithubs,I've made some updates to the level details and would appreciate it if you could take a look when you have a moment.


Improve output for core.sendmail when nothing sent

Want to be able to easily tell if an email was sent. The current message "Successfully sent mail" is misleading when we actually skip sending mail since the body is empty and we've selected not to send an empty body.
Of course, I'm open to changing the wording.

LGTM.

Merged, thanks.


Attribute placement

Going to complete this a bit more and add some better messaging so we can know when/why tasks might be/not be getting placed. Maybe along the lines of something that will help solve #636 as well
Overall adds a few things:

Singularity will keep track of all attributes for a slave, not just rack
you can reserve slaves with certain attributes (i.e. only run tasks that request them on those slaves)
you can have tasks only run on salves that match the attributes they request
added a /state/offers endpoint to show the most recent offer processing so we have insight into what was accepted/declined, and what tasks are still due and why offers for them were declined

@tpetr slimmed down the info in SingularityOfferState. Now, it just has the PendingTaskId, and either the offer id and host is was placed on or reasons that offers were declined for that task

Ok, changed up a number of things here:

Got rid of the /offerState node and corresponding ui
I am now storing a list of unmatched offers in the PendingTask object (updated fresh each time we process offers). This is a map of SlaveMatchState to a list of hosts that returned that slave match state. This should be helpful enough to give us some insight in the json view when a pending task seems to not be launching

/cc @tpetr

This has been i use and stable for a while, think we are good to merge this?

Commenting so that I remember:
The reserveSlavesWithAttributes should be a Map<String, List> so that we can reserve slaves with multiple different values for a certain attribute

@tpetr updated to take a list of values for reserved slave attributes

@tpetr added some tests in for the scheduler now as well, let me know if you have any other changes you'd like before we merge this in


Avahi: Fix CVE-2023-1981, add %check section

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[ ] The toolchain has been rebuilt successfully (or no changes were made to it)
[ ] The toolchain/worker package manifests are up-to-date
[ ] Any updated packages successfully build (or no packages were changed)
[ ] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[ ] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[ ] All package sources are available
[ ] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[ ] LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
[ ] All source files have up-to-date hashes in the *.signatures.json files
[ ] sudo make go-tidy-all and sudo make go-test-coverage pass
[ ] Documentation has been updated to match any changes to the build system
[ ] Ready to merge

Summary

Avahi has an issue here with a fix in this PR.
I have also enabled the basic built-in tests for the package. If we get a new version of Avahi (>=9.0) we will get even more tests (for example)
NOTE: 2.0 PR is here: https://github.com/microsoft/azurelinux/pull/10881
Change Log

Patch CVE-2023-1981
Enable %check section for Avahi

Does this affect the toolchain?

NO
Links to CVEs

https://brave-ocean-0baeae310.5.azurestaticapps.net/#/cve/CVE-2023-1981

Test Methodology

Local build
Buddy build: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=666009&view=results

2.0 check section hung, going to try and debug that before merging this into 3.0


Camera not opening to scan the qr code in new version 3 beta version.

Tried to test the live demo and it didn't open camera.
Also, tried to use it in my react project, happens the same.

same here! Actually it works in chrome (OS X) but I cannot get any image on my iphone (tested withIOS 15.6.1 in safari and mobile chrome)

same. i suspect this has something to do with recent iOS updates, because i definitely remember it working previously.

Same, the demo gives the error

undefined is not an object (evaluating 'navigator.mediaDevices.getUserMedia')

I suspect it has something to do with some recent iOS updates, because I definitely remember the same code worked before.

Same here. Permission granted, but window does not open in iPhone. Neither safari nor Chrome.

It works using HTTPS

@aelfannir i am using this for a project i am able to scan through the frontCamera but not able to open the rare camera what should i do

Hi everyone,
I hope this message finds you well. I am currently facing an issue with the QR scanner in my project. While I am able to successfully scan using the front camera, I am encountering difficulties in accessing the rear camera.
Here is the relevant code snippet:
jsx
<QrScanner
onScan={handleScan}
onError={handleError}
style={{ width: '100%' }}
facingMode="rare"
/>
Despite setting facingMode to "rare," the scanner continues to use the front camera.
I would greatly appreciate any insights or suggestions on how to resolve this issue and ensure the QR scanner utilizes the rear camera as intended.
Thank you in advance for your assistance.

Hi everyone,
I hope this message finds you well. I am currently facing an issue with the QR scanner in my project. While I am able to successfully scan using the front camera, I am encountering difficulties in accessing the rear camera.
Here is the relevant code snippet:
jsx
<QrScanner onScan={handleScan} onError={handleError} style={{ width: '100%' }} facingMode="rare" />
Despite setting facingMode to "rare," the scanner continues to use the front camera.
I would greatly appreciate any insights or suggestions on how to resolve this issue and ensure the QR scanner utilizes the rear camera as intended.
Thank you in advance for your assistance.

facingMode must be "environment" for back camera.


Greedy backspace

Greetings,
I've noticed strange behaviour of tagsinput, more exactly it deletes more that you could expect. When your have for example at least one tag and few text right below, if you select this text and press backspace key(only once), tagsinput will remove selected text and also previous tag.

Normally you could expect that it will delete only select text.
Many thanks.

:+1: I'm seeing this too.

This is related to an issue I just posted: https://github.com/timschlechter/bootstrap-tagsinput/issues/367
Not only is this a problem, but the delete key is also handled incorrectly. The solution for this problem is to check if there is a selection before checking the caret position.

Issue is resolved by #450.
Here's what I added to the library:
          case 8:
            if (doGetCaretPosition($input[0]) === 0) {
              var prev = $inputWrapper.prev();
              if (prev.length) {
                var prev_item = prev.data('item');
                // <<<<< TRP 12/27/15
                if((typeof prev_item === 'string' && prev_item ==$input.val()) || (typeof prev_item === 'object' && prev_item.name == $input.val())){
                  //console.log('remove b/c same name=value');
                  self.remove(prev.data('item'));
                }
                else{
                  //console.log('DONT remove b/c NOT sames name=value');
                }
                // >>>> TRP 12/27/15

              }
            }
            break;

thank you buddy its working fine...................:)

For me it does not work either …

Has anybody been able to solve this issue?

@tim-peterson thank you. You changes work. I was calling the min.js file, instead of the normal .js file for bootstrap tagsinput.


RxUI application as a target for "sharing content"

ghuntley [10:31 PM] @flagbug: I'm doing UWP currently, as is @moswald so
between us we got that covered.

flagbug [10:34 PM] @ghuntley: Beware, there are some major issues with RxUI
if your app is a target for a share operation:

https://msdn.microsoft.com/en-us/library/windows/apps/hh465251.aspx
because of the way that RxApp.MainThreadScheduler and friends work.

ghuntley [10:39 PM] @flagbug: can you give some examples of what you have
observed? Thanks for the heads up, not using sharing in this app fortunately.

flagbug [10:41 PM] @ghuntley: You have to set `RxApp.MainThreadScheduler`
when opening the app as share target, since the share target UI gets its own UI
thread and then, when you close the share UI, you have to set
`RxApp.MainThreadScheduler` back to its previous value, or else your main
application will crash.

See also https://github.com/reactiveui/ReactiveUI/issues/965

As a workaround, I'm doing something like this in the OnShareTargetActivated method:
// Capture the UI thread scheduler of the main application, so we can reset it, when we
// exit the share flyout
IScheduler realMainThreadScheduler = RxApp.MainThreadScheduler;
RxApp.MainThreadScheduler = new WaitForDispatcherScheduler(() => CoreDispatcherScheduler.Current);

// Pretty much the same goes for the DefaulltItemTemplate, since the template is
// generated on a different UI thread, we have to reset it here and change it back when
// closing the share target
//
// See https://github.com/reactiveui/ReactiveUI/issues/965 for more information
var previousTemplate = AutoDataTemplateBindingHook.DefaultItemTemplate;
AutoDataTemplateBindingHook.DefaultItemTemplate = new Lazy<DataTemplate>(() =>
{
    const string template = "<DataTemplate xmlns='http://schemas.microsoft.com/winfx/2006/xaml/presentation' xmlns:xaml='using:ReactiveUI'>" +
        "<xaml:ViewModelViewHost ViewModel=\"{Binding}\" VerticalContentAlignment=\"Stretch\" HorizontalContentAlignment=\"Stretch\" IsTabStop=\"False\" />" +
    "</DataTemplate>";
    var assemblyName = "";

    return (DataTemplate)XamlReader.Load(template.Replace("__ASSEMBLYNAME__", assemblyName));
});

Window.Current.Activate();
Window.Current.VisibilityChanged += (sender, ev) =>
{
    if (!ev.Visible)
    {
        RxApp.MainThreadScheduler = realMainThreadScheduler;
        AutoDataTemplateBindingHook.DefaultItemTemplate = previousTemplate;
    }
};


Tune node monitor grace period

See reason: https://discuss.kubernetes.io/t/how-to-reschedule-pod-on-another-node-if-node-fails-how-to-speed-up-rescheduling/7193/2
See how: https://github.com/k3s-io/k3s/issues/2278#issuecomment-738692882
Ref: And https://docs.k3s.io/cli/server#customized-flags-for-kubernetes-processes

https://github.com/PyratLabs/ansible-role-k3s

https://github.com/k3s-io/k3s/issues/1264

According to https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/, this should be used: https://kubernetes.io/docs/reference/config-api/kubelet-config.v1beta1/


Rotating a 3D plot causes flickering and changes in data visibility

Hi. I am trying to plot a series of scatter3d lines (one per timestamp), and when I rotate the plot interactively, it flickers heavily and  random points from the data are dropped, sometimes to the point that only a small portion of the plot is shown, and sometimes, there is no data at all. Is it a known problem?
Here are some screenshots when rotating the plot (the first one shows all of the data, and next are lost)

Could you make a minimal example of this and I would be happy to investigate. My first thought is maybe that you have some values for the view of the 3d model set in the config.

Hi! No, I left the configs as default, only added zero margin to layout YAML.
Anyway, while making a minimal example I discovered that this flickering only happens when you take data from a histogram (I have a prometheus datasource with "metric_bucket" metric, with labels le=1000, le=2000,...,le=39000,le=+Inf).
Here is a minimal example ("Processing script", all other sections are default, except margin: {b: 0, l: 0, r: 0, t: 0} added to layout):
let times = data.series[0].fields[0].values.map((t)=>new Date(t));
let values = data.series[0].fields[1].values;
lines = []
const N = 30
for(let i=0; i<times.length; i++) {
  let line = {
    y: Array.from({length: N}, (_, n) => n),
    x: Array.from({length: N}, (_, n) => times[i]),
    z: Array.from({length: N}, (_, n) => values[i]),
    type: 'scatter3d',
    mode: 'lines'
  };
  lines.add(line)
}

return {
  data: lines,
  layout: {
    showlegend: false,
  }
};

For every timestamp it creates a line of 30 points with value from 1st series, so it works with ordinary queries for, e.g. cpu temperature. And it does not flicker with these queries. But the moment you select a "something_bucket" metric, it starts flickering and missing data when you rotate the plot.

This is how the script works for a temperature metric. Yes, it's not pretty and not very usable, but it's a minimal example.
But if you choose a "something_bucket" metric with structure described above, and rotate the plot, at some points it can look like this:

Also you can notice that not only plot data gets distorted, but also axes and grids and axes tick labels.

Well, it's an upstream issue:
https://github.com/plotly/plotly.js/issues/3306
https://github.com/plotly/plotly.js/issues/6505
supposedly, the fix is in this PR: https://github.com/gl-vis/gl-axes3d/pull/23

The PR has not been approved in 3 years, but anyway this project is not the right place to fix this bug, so closing, yes. Thanks!


Use array spread to push multiple items to labelColors

I believe this should allow for arrays to be returned from labelColor. I have not tested it yet, but I am going to now.

I believe the spread operator does not work in IE11, which is a browser we support

Thanks for the PR. For now, I'm going to close this since it's failing the tests and incompatible with IE. Please feel free to reopen when those issues are addressed

@benmccann do you guys not use babel?

No, we don't

@benmccann any particular reason to not use it?

See https://github.com/chartjs/Chart.js/issues/5787#issuecomment-438153739


Allow main() to return error

Right now the compiler reports an error if main() returns an error
sandbox/foobar/main.go:5:6: func main must have no arguments and no return values

A throwaway script typically uses a log.Fatalln to exit on error:
func main() {
	err := doSomething()
	if err != nil {
		log.Fatalln(err)
	}

	err = doSomethingElse()
	if err != nil {
		log.Fatalln(err)
	}
}

It would be nice to just return the error, and get the same effect as calling log.Fatalln(err):
func main() error {
	err := doSomething()
	if err != nil {
		return err
	}

	err = doSomethingElse()
	if err != nil {
		return err
	}

	return nil
}

You can do the same thing with
func main() {
  var err error
 defer func() {
   if err != nil {
    log.Fatalln(err)
   }
 }()
	err = doSomething()
	if err != nil {
		return
	}

	err = doSomethingElse()
	if err != nil {
		return
	}
}

Returning error from main sends something outside the programmer's control. You might want to control how/where the error is show.

Don't use defer magic for this... just move the code into another function that returns an error:
package main

func main() {
	if err := run(); err != nil {
	}
}

func run() error {
	return nil
}

actually maybe i'll leave this open. In fact, I personally do it the way @DisposaBoy suggested. In which case, run becomes another name for main()

Why a log.Fatalln and not something else? With what logger? What if the main function panics before returning?
I think this complicates the language (https://golang.org/ref/spec#Program_execution) for very little benefit - just saving yourself four lines of code.

This was proposed (and rejected) in #27328, and as far as I can tell this report does not add any new motivating data on top of that, so closing.

Duplicate of #27328


[Bug] Quickstart example of cloud functions is not working (data parameter with numbers is not passed)

Description
Quickstart example of cloud functions is not working. Data parameter is not passed. Tested in Unity Editor and android devices, both of emulator and deployed versions. It always return "Firebase.Functions.FunctionsException: The function must be called with two arguments "firstNumber" and "secondNumber" which must both be numbers."
Reproducing the issue
Code is copied without modifications from https://github.com/firebase/quickstart-unity/tree/master/functions/testapp/Assets/Firebase/Sample/Functions
Firebase Unity SDK Version
12.2.1
Unity editor version
2022.3.16f
Installation Method
.unitypackage
Problematic Firebase Component(s)
Functions
Other Firebase Component(s) in use
Authentication, Database, Storage
Additional SDKs you are using
No response
Targeted Platform(s)
Android
Unity editor platform
Windows
Scripting Runtime
IL2CPP
Release Distribution Type
Open-source from this repo
Relevant Log Output
{"verifications":{"app":"MISSING","auth":"VALID"},"logging.googleapis.com/labels":{"firebase-log-type":"callable-request-verification"},"severity":"DEBUG","message":"Callable request verification passed"}

If using CocoaPods for Apple platforms, the project's Podfile.lock
No response

Hey @gudkovtimur, thanks for reaching out. I'm able to reproduce the issue. It seems that the server side code embedded in the quickstart hasn't been updated for quite sometime. I'll try and see if I can make a pull request to adjust this. Thanks!


build errors

Hi!
First Thanks for the great work you are doing! this is a verynice project.
I managed to compile for WT32-SC01 3.5" and flashed it
Ineede to change my computer in the meantime and got all the setup new the same way, but Iam getting now compilation errors.
I fresh cloned your project, I installed esp-idf-version 5.2 -> the same I have used before.
I also tried it with idf Version 5.0 but the same result. no successfull build
idf_py_stdout_output_36856.log
I have the build-log attached, pls help
Thanks
Regards
Joe

You are using IDF 5.2 and LovyanGFX has some bug which is fixed for this version.
You can read about it here
You can try using IDF 5.1.2 which should work fine for now.
More details and fix for IDF 5.2 is in the above link.

Hi Sukesh,
Thank you for the fast attention and reply!
I have tried with idf 5.1.2 but iam getting another build error.
/Users/Admin/Documents/A-TUX-ESP/ESP32-TUX/main/main.cpp: In function 'void app_main()':
C:/Users/Admin/Documents/A-TUX-ESP/ESP32-TUX/main/main.cpp:269:5: error: 'lcd' was not declared in this scope
269 |     lcd.init();         // Initialize LovyanGFX
  |     ^~~

ninja: build stopped: subcommand failed.
Log attached.
Kind Regards
Joe
From: Sukesh Ashok Kumar @.>
Sent: Wednesday, February 21, 2024 7:05 PM
To: sukesh-ak/ESP32-TUX @.>
Cc: joekam54 @.>; Author @.>
Subject: Re: [sukesh-ak/ESP32-TUX] build errors (Issue #51)
You are using IDF 5.2 and LovyanGFX has some bug which is fixed for this version.
You can read about it here https://github.com/lovyan03/LovyanGFX/issues/489
You can try using IDF 5.1.2 which should work fine for now.
More details and fix for IDF 5.2 is in the above link.
—
Reply to this email directly, view it on GitHub https://github.com/sukesh-ak/ESP32-TUX/issues/51#issuecomment-1957561220 , or unsubscribe https://github.com/notifications/unsubscribe-auth/BGKQVEW3P67FVIJSN6WIIYLYUYZN3AVCNFSM6AAAAABDTLHZE2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJXGU3DCMRSGA .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/BGKQVEQSN53OKRRDUY7TRADYUYZN3A5CNFSM6AAAAABDTLHZE2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTUVYBYI.gif Message ID: @.*** @.***> >

C:/Users/Admin/Documents/A-TUX-ESP/
Try not to use long folder tree since some of the compiler tools create issues.

Looks like LovyanGFX library access is missing (best guess).
Maybe you didn't get the submodules while cloning.

Hi Sukesh,
Thanks , it works now! 😊
Kind regards
Joe
Von: Sukesh Ashok Kumar @.>
Gesendet: Donnerstag, 22. Februar 2024 09:05
An: sukesh-ak/ESP32-TUX @.>
Cc: joekam54 @.>; Author @.>
Betreff: Re: [sukesh-ak/ESP32-TUX] build errors (Issue #51)
C:/Users/Admin/Documents/A-TUX-ESP/
Try not to use long folder tree since some of the compiler tools create issues.
Looks like LovyanGFX library access is missing (best guess).
Maybe you didn't get the submodules while cloning.
—
Reply to this email directly, view it on GitHub https://github.com/sukesh-ak/ESP32-TUX/issues/51#issuecomment-1958901028 , or unsubscribe https://github.com/notifications/unsubscribe-auth/BGKQVESJY6TT5JLJRI6O44TYU333VAVCNFSM6AAAAABDTLHZE2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJYHEYDCMBSHA .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/BGKQVEVSIE5XBRZJOREQYY3YU333VA5CNFSM6AAAAABDTLHZE2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTUYJ2SI.gif Message ID: @.*** @.***> >

…nice.. thanks for help getting me into esp-idf..
I will set up idf an VS-code on my linux PC, because I really hate to work on windows
KR
From: Sukesh Ashok Kumar @.>
Sent: Friday, February 23, 2024 5:25 PM
To: sukesh-ak/ESP32-TUX @.>
Cc: joekam54 @.>; Mention @.>
Subject: Re: [sukesh-ak/ESP32-TUX] build errors - error: 'INTR_CPU_ID_AUTO' was not declared in this scope (Issue #51)
@joekam54 https://github.com/joekam54
If you want a simple example just for your TFT WT32-SC01 you can try this new sample.
I am trying to get lvgl v9 working for this sample. But the current version is using v8.
https://github.com/sukesh-ak/IDF-ESP_LCD-LVGL
—
Reply to this email directly, view it on GitHub https://github.com/sukesh-ak/ESP32-TUX/issues/51#issuecomment-1961626721 , or unsubscribe https://github.com/notifications/unsubscribe-auth/BGKQVEUE5PUUOLOEPDFIK3LYVC7GLAVCNFSM6AAAAABDTLHZE2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRRGYZDMNZSGE .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/BGKQVERUDHSKRPHAFTOV2Q3YVC7GLA5CNFSM6AAAAABDTLHZE2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTU5QGGC.gif Message ID: @.*** @.***> >


chore(master): release 2.0.0

:robot: I have created a release beep boop
2.0.0 (2022-07-17)
⚠ BREAKING CHANGES

remove unused files

Features

remove unused files (63a026b)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/3h4x/movies-organizer/releases/tag/v2.0.0 :sunflower:


Fixed missing resources. Formatting and text

@zabil - was there a reason to use triple backticks instead of single. Triple is usually used for code blocks, not inline.
Also, would you mind running the images through optipng -o7 to reduce the sizes?

Scratch the optipng, I'll do that once after everything is in.

@ketan it was being used in the newer documentation.
https://github.com/gocd/documentation/blob/2d8ca027d1e1b8b2660d2667a2737a14a2f94099/user/installation/troubleshoot_installer.md
Made it consistent

Made it consistent

:+1:

... it was being used in the newer documentation ...

Sorry. I start out making them not be inline and sometimes inline them. At least GFM handles it properly when it is inline and with three backticks. So, I just don't bother with the single backtick.


Ability to call a neovim command after using fzf-lua

I was wondering if there was any good way to call a command after I am done using fzf-lua and have chosen a result.
My goal is to have my dashboard have a button that will use fzf-lua to pick and index.md file from one of my notebooks, then run some commands (specifically :ZkCd a command that changes into the selected notebook's directory). Here is the line that I currently have written up:
dashboard.button( "n", "   > Notebooks", [[:lua require("fzf-lua").files({ cwd = "~/Dropbox/Notebooks", cmd = "fd -e md -g 'index.md'"})<cr>]]),

While I can just concatenate other commands on with pipes, they all get called when the button is pressed. Is there any sort of way I can detect once fzf-lua has closed, or maybe just call the commands afterwards?
Thank you in advance.

Why don’t you add a global action handler and then map it as the default action?
_G.my_open = function(selected)
  vim.cmd('ZkCd ' .. selected[1])
end

require'fzf-lua'.files({ cwd = "~/Dropbox/Notebooks",
  cmd = "fd -e md -g 'index.md'", actions = { ['default'] = G.my_open }})

I tried looking through the documentation, but couldn't really figure out what actions does. Does it change the default action of the picker?
I still want it to maintain the original functionality of the .files picker, where it opens the selected file, I just then want the ability to run the ZkCd command. The snippet you provided seems to just run the ZkCd command.

Actions is a map of functions that process your selection based on the keybind you pressed with default being what’s called when you press Enter.
This should do what you want:
_G.my_open = function(selected, opts)
  require'fzf-lua'.actions.file_edit(selected, opts)
  vim.cmd('ZkCd')
end

That works beautifully, thank you so much :D
Love your work, really liking fzf-lua since changing from Telescope.

That works beautifully, thank you so much :D
Love your work, really liking fzf-lua since changing from Telescope.

Ty @AndOrangutan


use rustic-test-arguments by default

Hi,
Currently, the command rustic-cargo-test always runs with the default argument rustic-default-test-arguments. Users can set up a custom argument using C-u, but this is only applicable for the current run, and next time, users need to run C-u again to update the argument.
I fixed this issue by enabling rustic-cargo-test to run with rustic-test-arguments, which is initialized by rustic-default-test-arguments, and is only needed to be updated by users once using C-u.
Can you review and merge this PR if possible?
Thanks!

I agree this is something that needs to be fixed. The problem is really that the behavior is not consistent between using the popup and stand-alone command.  I would say this simplest way to fix this would be to unify the two cases.
https://github.com/brotzeit/rustic/blob/4879922524faff116535c9061af6e8a902609f65/rustic-cargo.el#L173-L180 bs
I imagine it looking like this
(cond (arg
       (setq rustic-test-arguments (read-from-minibuffer "Cargo test arguments: " rustic-default-test-arguments)))
      ((string-empty-p rustic-test-arguments)
       rustic-default-test-arguments)
      (t rustic-test-arguments))

The idea was that you can use the rerun commands if you want to reuse the stored arguments. I'm not sure why I decided to make this behavior different for the popup, maybe so you don't have to add two commands to the popup menu.
If we apply this change the rerun commands wouldn't be needed anymore and you would have to manually reset rustic-test-arguments if you want to use the default arguments again. There are probably people that got used to the way it works now.
Would it be ok for you if we replace the popup condition with a new option.
(cond (arg
          (setq rustic-test-arguments (read-from-minibuffer "Cargo test arguments: " rustic-default-test-arguments)))
         (rustic-cargo-always-use-stored-arguments ;; maybe better name ?
          (if (> (length rustic-test-arguments) 0)
              rustic-test-arguments
            rustic-default-test-arguments))
         (t
          rustic-default-test-arguments))

@brotzeit: in my patch, to reset rustic-test-arguments, users can just need to run rustic-cargo-test with C-u. It will prompt a question to reset that variable to rustic-default-test-arguments:
(setq rustic-test-arguments (read-from-minibuffer "Cargo test arguments: " rustic-default-test-arguments))

Nevertheless, I agree with you that this functionality is not straightforward and my patch also changed the current default behavior of rustic-cargo-test.
+1 vote for the use of option using rustic-cargo-use-stored-arguments.
Maybe change the name to rustic-cargo-use-last-stored-arguments or rustic-cargo-use-last-used-arguments?

@CeleritasCelery What do you think ?

I like the idea of making it a user option for preserving the current behavior if desired. We also probably want to update rustic-cargo-run to have the same behavior for consistency.
And my personal preference for bikeshedding over the variable name would be rustic-cargo-reuse-arguments 😄

@taquangtrung Do you still want to implement this?

@CeleritasCelery: seems that @brotzeit already implemented it in this commit: https://github.com/brotzeit/rustic/commit/064aeefc7eab7630aafde32fe378143a8c3d976d


Test github action workflow

Trigger github actions workflow to test integration of staging site
WARNING: Only users listed in the CODEOWNERS file can approve PRs!

📝 This PR updates the documentation.
👉 Preview this PR at: https://klutch.io/docs/pr-preview-23 .


Upmerge 25-03-2024

Why https://github.com/nrfconnect/sdk-mcuboot/pull/308 was reverted? @gmarull

Why #308 was reverted? @gmarull

maybe a mistake

reapplying in #311


#39: Fixed bug related to consuming all offsets from stale topic

When poll returns an empty result, fetch the current partition offset from Kafka instead of falling back to our own internal "latest" offset that we read from the topic at some point in the past.
This works around the case where, if we have a topic that used to have some records, but they were all expired, the consumer would keep looping infinitely.
It happens this way since the start and end offset of our empty-but-once-populated partition will be the same, 10 for example, but our internal latest offset is perhaps 5; and if no new records appear while we poll, we'll keep the '5', comparing it to the end offset of 10, forever assuming we need to read some more records.

Hey @jwarlander,
Thanks for the pull request!
I am going to review it soon.


Add pull request flow to Contributing guide

Oh, that's an interesting thought. I guess another way to approach it might be to just always require that the contributor include the PR # (which GitHub does by default) in the eventual "squashed and merged" commit subject? Sometimes I strip it manually which I could stop doing as you're right -- it's a useful link to the relevant discussion.
If preserved, then it could be easily referenced that way without having the extra commit (although it's obviously not clickable).

that sounds fine to me as long as there's some reference.

Sg, updated the guidelines with a note on preserving the PR#


engine: re-execute Tiltfile when config files for manifest change

Same deal as last time: there are a couple outstanding TODOs and no tests but I wanted to validate the approach.
One question that's not in the code: It seems to me that we don't want to filter out any file events based off of information in the Tiltfile. Does that seem right? We certainly don't want to filter out file events for the dockerfile and tiltfile anymore and I couldn't think of any other situations.

@nicks let me know what you think of this test. This doesn't work for kubernetes yaml yet, and I'll investigate why but I'm thinking that + additional refactors should wait until after this is merged to prevent merge conflicts.


Xuggler 5.4 issue | mvn build failure

[ERROR] Failed to execute goal on project stormcv-deploy:
Could not resolve dependencies for project nl.tno.stormcv:stormcv-deploy:jar:0.0.1-SNAPSHOT: Failure to find xuggle:xuggle-xuggler:jar:5.4
in http://github.com/sensorstorm/maven/raw/master/releases/ was cached in the local repository,
How to figure maven dependency for  xuggle:xuggle-xuggler:jar:5.4 or fix this issue?

The Xuggle repository at http://xuggle.googlecode.com/svn/trunk/repo/share/java/ does not exist anymore. I guess this has to do with the fact that Xuggle is not deprecated in favour of Humble Video. This means that another video reader must be integrated into StormCV in order for it to work again. Someone else has to do it since I no longer actively maintain this project...

I have downloaded the jar and added as a local maven dependency And build was successful.
https://github.com/lxb200709/xuggle/blob/master/repo/share/java/xuggle/xuggle-xuggler/5.4/xuggle-xuggler-5.4.jar


Design of a card in the events page is different from others.

Description
Design for third card or "Hello" event is different and it also contains some random words.
Screenshots

Additional information
No response
🥦 Browser
Google Chrome
👀 Have you checked if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

[X] I have read the Contributing Guidelines

Are you willing to work on this issue ?
Yes I am willing to submit a PR!

The cards are dynamic - meaning we are getting the info from DB

We will make changes to the DB shortly, however changes in the Frontend can be done so that they are of the same length


Improve register page error handling

What does this PR do?
Modify the existing script to handle errors when users trying to register, login or logout.
Fixed #27
Type of change
Bug fixes
Screenshots/Video
https://github.com/user-attachments/assets/f5c34191-b432-4847-8816-05e4f3cb3965
Additional context
I'm ensuring that the all other workflow works perfectly like before.

Hi @rajmanna-dev ,
I checked your Forked repo in my system. It works fine. But there are some conflicts occurred at the register route path function. Can you please resolve it so that I can merge it with the main branch and it will deployed into render app?


Add a flag for the user to decide to show trajectory conflicts and negotiations

The idea is to have trajectory conflicts and negotiations completely hidden except when the user specifically opens some kind of panel to look at that information (or maybe activate a flag). We don't generally need to report failed negotiations.
Regarding repeatedly failing negotiations
We could have a separate error channel for escalating repeatedly failing negotiations to the operator's attention, and that message could be channeled into an operator notification.

I think we should always show trajectory conflicts, but not the snack bar alert. Trajectory conflicts are considered normal operations in rmf so it should not raise any attention. Only when a robot failed to resolve the conflict after a certain amount of time then we consider it abnormal, but this requires a server to keep track of that data.
For negotiation, I thought the original design is to only show it when the negotiation panel is opened. There shouldn't be a need to show the negotiation trajectories layer checkbox in leaflet. It will always show when the user is in the negotiation panel and be hidden otherwise, all normal trajectories will also be hidden when we are showing negotiation trajectories. It looks like the design never got in so this change would be very welcomed.

I think we should always show trajectory conflicts, but not the snack bar alert. Trajectory conflicts are considered normal operations in rmf so it should not raise any attention. Only when a robot failed to resolve the conflict after a certain amount of time then we consider it abnormal, but this requires a server to keep track of that data.
For negotiation, I thought the original design is to only show it when the negotiation panel is opened. There shouldn't be a need to show the negotiation trajectories layer checkbox in leaflet. It will always show when the user is in the negotiation panel and be hidden otherwise, all normal trajectories will also be hidden when we are showing negotiation trajectories. It looks like the design never got in so this change would be very welcomed.

Ok, thanks for the feedback. I'll update the description.

For negotiation, I thought the original design is to only show it when the negotiation panel is opened. There shouldn't be a need to show the negotiation trajectories layer checkbox in leaflet. It will always show when the user is in the negotiation panel and be hidden otherwise, all normal trajectories will also be hidden when we are showing negotiation trajectories. It looks like the design never got in so this change would be very welcomed.

Yeah, that was the idea. Oh yeah, the negotiation trajectories are showed on top of the current trajectories, only when you click on a negotiation item (on the Omni-panel). So, if I understand correctly, the idea is to remove the current trajectory from the map and just show the negotiation when a negotiation is clicked, right?

Ok, thanks for the feedback. I'll update the description.

For negotiation, I thought the original design is to only show it when the negotiation panel is opened. There shouldn't be a need to show the negotiation trajectories layer checkbox in leaflet. It will always show when the user is in the negotiation panel and be hidden otherwise, all normal trajectories will also be hidden when we are showing negotiation trajectories. It looks like the design never got in so this change would be very welcomed.

Yeah, that was the idea. Oh yeah, the negotiation trajectories are showed on top of the current trajectories, only when you click on a negotiation item (on the Omni-panel). So, if I understand correctly, the idea is to remove the current trajectory from the map and just show the negotiation when a negotiation is clicked, right?

I think we should always show trajectory conflicts, but not the snack bar alert.

Got it. I think we should remove the snack alert when we implement the "grid" UI. But we can hide it with a flag for now

I think we should always show trajectory conflicts, but not the snack bar alert.

Got it. I think we should remove the snack alert when we implement the "grid" UI. But we can hide it with a flag for now

fixed by #222


test: get correct CIV tag in azure.sh

In order to run azure.sh inside CIV CI, we need to use the appropiate tag. This means getting prod tag when running in osbuild-composer and the pr tag when running in cloud-image-val
This pull request includes:

[ ] adequate testing for the new functionality or fixed issue
[ ] adequate documentation informing people about the change such as

[ ] submit a PR for the guides repository if this PR changed any behavior described there: https://www.osbuild.org/guides/

⚠ This PR introduces changes in at least one manifest (when comparing PR HEAD f65f883 with the main merge-base 989c640). Please review the changes. The changes can be found in the artifacts of the Manifest-diff job [0] as manifests.diff.
[0] https://gitlab.com/redhat/services/products/image-builder/ci/osbuild-composer/-/jobs/3124091875/artifacts/browse

The diff is on rhel-87 qcow2 image with customizations, which does not make much sense, since this PR can't be reasonably cause of the difference. 🤷♂


Create uetpeshawar.txt

Just followed the instruction for adding my university to this repository so that I can get my student license

@x-Waseem-x First stage of verification passed, official domain is uetpeshawar.edu.pk as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@x-Waseem-x Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Units other than meters and degrees

The referenced specification only considers Meters and Degrees.  Would it be possible to consider other units?  In the United States were have the State Plane Coordinate System with either defined units in "US Survey Foot" or "International Foot".
US Survey Foot = 0.3048006096
International Foot = 0.3048
I hard-coded the else statement to the US Survey Foot for EPSG:2276 data that I am working with just as a test. And I am very happy to have found success in properly tiling locally referenced imagery!
I don't know Python, but I could take a crack at adding a case statement for the defined units if there is no objection.
https://github.com/developmentseed/morecantile/blob/17020c555d4f09e3027cab755cf0f74744106774/morecantile/utils.py#L55
From note g in http://docs.opengeospatial.org/is/17-083r2/17-083r2.html#table_2:
If the CRS uses meters as units of measure for the horizontal dimensions,
then metersPerUnit=1; if it has degrees, then metersPerUnit=2pa/360
(a is the Earth maximum radius of the ellipsoid).

Thanks for opening the issue @lf73
I've opened a PR over https://github.com/developmentseed/morecantile/pull/86, it would be nice if you could confirm that this will fix your issue 🙏

@vincentsarago  Thank you very much for the elegant fix. I confirmed this solves the issue with all of the units. I confirmed with 2276, US Survey Foot; 2222, Foot; 4326, Degree; and 32631 Metre.  I am not aware of any other units in use.
Appreciate your help. TiTiler is working beautifully with the correct unit in place and hopefully this opens an opportunity for others to utilize. I am very happy not having to do projections and being able to keep native to our area.
By the way, the United States is making progress to international units! :-)  Just this year we eliminated the State Planes Coordinate Systems from using the US Survey Foot!! Only to go to the International foot!  Maybe in another 20 years, we will progress to the Metre, albeit we'll probably have to spell as Meter.....


lstm-specific dictionaries load Failed

Environment
Tesseract Open Source OCR Engine v4.0.0-beta.4-18-g4370
Linux bogon 3.10.0-862.3.3.el7.x86_64
Current Behavior:
I'm trying to fine tuning chi_sim by adding some characters
It goes well during training without any fault and I got my .traineddata file by --stop_training
But, when I trying to test it with tesseract command
tesseract test-0.png test --tessdata-dir ./chi_sim -l driver_name
I'v got these words
Failed to load any lstm-specific dictionaries for lang driver_name!!
this is what inside the file
combine_tessdata -d chi_sim/driver_name.traineddata
0:config:size=2106, offset=192
17:lstm:size=12169267, offset=2298
21:lstm-unicharset:size=382829, offset=12171565
22:lstm-recoder:size=94353, offset=12554394
23:version:size=21, offset=12648747
since " Tesseract 4.00 will run happily with a traineddata file that contains just lang.lstm, lang.lstm-unicharset and lang.lstm-recoder ", I thought I'v just satisfied this requirement
so what are these lstm-specific dictionaries?
are these data important?
will this issue critically influence my ocr result ?

Please see new langdata_lstm repository which has the source files used for LSTM training.
If you provide the wordlist, puncuation and numbers file for combine_lang_model command then it will create the dictionary dawg files.

I see, I should take up wordlist, puncuation and numbers files while create starter traineddata.
But I wonder that what's the main different between langdata_lstm and langdata, since they have almost the same file pattern
.singles_text seems the only file that langdata_lstm has while langdata doesn't
But, .singles_text looks much like .wordlist or, to be more precisely, the subset of .wordlist
what's the purpose of this .singles_text file? Is it necessary for lstm training?


send email notification for application approvals and rejections

Reticketing from @dcht00 at https://github.com/gratipay/gratipay.com/issues/3526#issuecomment-112797426:

What I meant as being confusing was I wasn't notified when my "new" application got approved (or denied). There was a ticket for that here, but the system should prob inform people in some other way they were approved than just seeing money starting to roll in :) What happens if they're denied registration?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/22335401-send-email-notification-for-application-approvals-and-rejections?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github).

Blocking this on #3568.

Done in #3568.


Make it compatible with Qmod Manager on Nexus

Both apps use the same Assembly-Csharp.dll

My reply on my repo gives a manual fix but I'll plan to allow a way of running my installer in a "compatibility mode" which won't overwrite other injections
https://github.com/Qwiso/QModManager/issues/1#issuecomment-367169184

@Qwiso you can look at/borrow my patching code, it already behaves that way.

@MartinSGill we both explicitly backup the original dll, is the issue.

I can make that an option on the installer. The backup shouldn't be an issue, unless we both choose the same filename. Unless your mod does something with the backup?
I only back it up to make uninstalling easier, nothing of mine actually makes use of the backup. It's not strictly necessary as a Steam validate will restore the missing/patched file. So I could just turn that feature off.

Sorry for not being clearer. Both of our installers will inject and function, I've tested that just now
What I noticed, when using File.Copy for backup we should ensure the version of Assembly-CSharp.dll is clean of other patching methods