gdal setup on travis sometimes fails

Description
... maybe we can simplify the Travis setup by using a Conda environment?
Currently I only use pywps with Conda.
Steps to Reproduce
Additional Information

GDAL/OGR is dependent on a few C libraries that require installation (or building) in order to run. I can see that the version is pegged to 2.1.0 (which is deprecated). Is there any interest in using the GDAL_VERSION env var instead to pull the actual gdal?
Does PyWPS currently install against GDAL3?

@Zeitsperre GDAL_VERSION is part of travis? We can use it to ease the travis installation. GDAL/OGR is only used by the validator. We should update it to the latest version. What you like to do this?

gdal is an issue again ... now on GitHub CI, see PR #580:
GitHub CI is using ubuntu-latest which is now using gdal=3.
Workaround in CI test is currently to use Test CI ubuntu-18.04
In our conda env we skip gdal ... it is optional:
https://github.com/conda-forge/pywps-feedstock/blob/master/recipe/meta.yaml

We could specify a build recipe for pip that pulls in GDAL and other geospatial libraries, but that would necessitate disabling some example processes. I'm not sure how you feel about that. From what I understand, even without the examples, GDAL is still needed, right?
It's interesting that the PyWPS conda recipe is so bare. I don't know if any of the listed libraries use GDAL in their requirements. Perhaps GDAL is unneeded ?

It's interesting that the PyWPS conda recipe is so bare. I don't know if any of the listed libraries use GDAL in their requirements. Perhaps GDAL is unneeded ?

GDAL is optional ... but used at some places. I would prefer to remove it in pywps ... but maybe there are reasons against this.
ping @jachym

Ultimately, the complication with GDAL has to do with the fact that it needs to have a corresponding version between the C and Python libraries, and pip is designed to install the newest version. Just a thought, but what if we were to pull the installed version with a command like this:
apt-get install libgdal-dev
GDAL_VERSION=$(gdal-config --version)
pip install gdal==$GDALVERSION

@cehbrecht @jachym
This is causing a CI failure for my latest PR.


Change dependabot to weekly with bundled dependencies if possible

Currently all the dependencies are checked I believe daily which means that all the updates are happening right next to one another.
It would be nice to see all of the updates bundled into one PR instead of 10 every week.
CONs:
if the PR breaks then you need to test each one so maybe this isn't the best idea.

instead, I've installed @tonybaloney's dependabot-bot
.github/dependabot-bot.yml
I've also made it only run on the packages in the pyproject.toml


Toggle Group Modifications

PR following discussion in #185
Discussion on choices I made is open.
I let some classes with deprecation warning which should appear in tests
I updated the Widgets notebook with Toggle Group example.

You did a much better job than I could!

Thanks so much for this. I've made one comment but am otherwise happy to merge.

I'm making the correction


Set the $PATH to include node_modules

From https://github.com/gtramontina/ghooks/pull/51

I think that the command is not executed with the proper $PATH because I don't think that it can find validate-commit-msg which is in node_modules/.bin/ which we add to the path when we run our scripts

Thanks for reporting I'll have a look into this during the day.
I have no clue anymore, why I used the cli lib's exec method anyway, as I planned to use something like ghooks runner as a template in the first place (same for #6); must have been simply too late for me ...


REST API Is Not Loading In CAS 4.2.6

CAS server version: 4.2.6.  The REST API works fine in 4.2.4 and 4.2.5.
Servers: Jetty and Tomcat 8
Include cas-server-support-rest in cas-server-webapp's build.gradle.
The only line in the log showing an issue is:
2016-09-30 08:47:24,203 WARN [org.springframework.web.servlet.PageNotFound] - <No mapping found for HTTP request with URI [/cas/v1/tickets] in DispatcherServlet with name 'cas'>

Please note I will take ownership of this issue and submit a fix.

This is not a bug.  The cas-server-support-rest jar was not being included in the packaged cas-server-webapp.war even though it was listed as a dependency.

Got confirmation from @wcrowell that this is now resolved in 4.2.7-SNAPSHOT.


Remove secrets and configmaps from the cache

Description
Changes proposed in this pull request:

...
...
...

Related issue(s)

/test all


Updated recipe for 3.8.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

requirements: run: shared-memory38;python_version<"3.8" must contain a space between the name and the pin, i.e. shared-memory38;python_version <"3.8"
requirements: run: typing-extensions;python_version<"3.11" must contain a space between the name and the pin, i.e. typing-extensions;python_version <"3.11"

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.
I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.
Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.


Require go 1.18

What does this PR change? What problem does it solve?
#4038 and #4028 require Go 1.18 to build. This rather large bump in the required minimum version is a result of making use of the generics support which was introduced in Go 1.18.
This PR also cleans up some no longer necessary workarounds and build constraints.
Was the change previously discussed in an issue or on the forum?
See #4028.

Checklist

[x] I have read the contribution guidelines.
[x] I have enabled maintainer edits.
[ ] I have added tests for all code changes.
[x] I have added documentation for relevant changes (in the manual).
[x] There's a new file in changelog/unreleased/ that describes the changes for our users (see template).
[x] I have run gofmt on the code in all commits.
[x] All commit messages are formatted in the same style as the other commits in the repo.
[x] I'm done! This pull request is ready for review.

github.com/hashicorp/golang-lru/v2 would also require 1.18.

Code changes LGTM. I suppose this (or any upgrade to >=1.16) would also close #2659.

LGTM.


ImpersonatingMitmManager - Bypass MITM depending on domain

Is it possible to make ImpersonatingMitmManager (when combined with LittleProxy) perform a direct passthrough without certificate impersonation, if upon a CONNECT, the domain does not match one of a series of whitelist regular expressions?
I need to have the proxy accepting all browser traffic, but I only want to run filters for a small percentage of said traffic, MITM needs to be selective so that HSTS enabled domains such as google.co.uk do not get intercepted, as otherwise, this stop a user being able to make google searches unless they stop the proxy server, make their searches, then start the proxy server back up afterwards.
Is this possible?
Looking over the code, it looks like clientSslEngineFor always calls getHostnameImpersonatingSslContext, so there is not a current way to do this, but I might have missed something.
The company I work for uses a home-rolled authentication protocol similar to HAWK when talking to microservices. This proves to be a pain when testing those microservices, so I wrote a Fiddler plugin that automatically adds the required authentication headers to any outgoing requests that look like they are for an internal company domain. This allows for standard REST requests to be made in the browser / rest client and for them to be transparent signed. However, we are now looking to move away from requiring Fiddler.
Edit: A bit more digging makes me think this is more littleproxy specific than browsermob-mitm specific. I will leave this question open in-case it isn't, but I will also ask the littleproxy people.

 I bet that can be solved on higher level
    final Set<String> whitelistDomains = new HashSet<>(Arrays.asList("google.co.uk", "github.com"));
    HttpProxyServer server = DefaultHttpProxyServer.bootstrap()
            .withPort(8080)
            .withFiltersSource(new HttpFiltersSourceAdapter() {
                public HttpFilters filterRequest(HttpRequest originalRequest, ChannelHandlerContext ctx) {
                    String uri = originalRequest.uri();
                    String domain = null;
                    try {
                        URL url = new URL(uri);
                        domain = url.getHost();
                    } catch (MalformedURLException e) {
                        // TODO: implement your custom logic here
                    }
                    if (whitelistDomains.contains(domain)) {
                        // Just skip filtering
                        return null;
                    } else {
                        return new HttpFiltersAdapter(originalRequest) {
                            @Override
                            public HttpResponse clientToProxyRequest(HttpObject httpObject) {
                                // TODO: implement your filtering here
                                return null;
                            }

                            @Override
                            public HttpObject serverToProxyResponse(HttpObject httpObject) {
                                // TODO: implement your filtering here
                                return httpObject;
                            }
                        };
                    }
                }
            })
            .start();

@NickEm
Thanks for posting that.
It is the opposite way around (only filter if in the list), but that is just a case of reversing the if.
However, unfortunately, this is not what I am looking for.
Even if you don't filter such a request, if it is HTTPS, the MITM manager will have already generated a self-signed certificate and will have used that to impersonate the server. This breaks applications that use certificate pinning (Which I incorrectly referred to as HSTS in my first post, and have since edited).
Similar to FiddlerCore's x-no-decrypt option, I don't even want certificate impersonation to occur if the request doesn't match the whitelist. Instead, the original non-mitm certificate should be returned, and subsequent requests that are encrypted inside the resulting CONNECT tunnel should be passed through as-is without decryption or encryption.
P.S: Given this is more of a discussion than an issue (yet), should I move this to stackoverflow?

@ScottDennison
All right, now I got it. Unfortunately, no answer so far, deeper investigation is required.

A bit more digging revealed that this isn't easily fixable inside browsermob-proxy mitm, and instead needs a change to LittleProxy. See my pull request at https://github.com/adamfisk/LittleProxy/pull/406
Note that pull request 402 (not mine) of LittleProxy upgrades LittleProxy to java 8. If that goes in, then this project would also then need upgrading.


[ragel] D tests pinned to gdc-5

ubuntu 18.04 is up to gdc-8
If we can, take the highest gdc on the system

Checking gdc-8 down through gdc-5.
ef54b3ad76f7b10142e26ad6c2eb5e19f6534588


Initialize project flow opens create_dbflow.sh script and does not initialize project structure under windows

Hi! I was trying to setup the extension under windows 11. I have installed properly sqlcl and the bash command is recognized under the default WSL. The first time, there was some java asking for permissions to execute, and after that, a create_dbflow.sh is opened, but just it, the folder structure doesn't get created and nothing is imported. I can't see any details about what failed. What could it be? thanks!

Sounds strange, maybe we should have a look at it via video call. To which email address can I send you a GoogleMeet invitation? And when is the best time for you (time zone)?

Yes sure! I'm in spain, GMT+2. I've added you in linkedin, I will provide my email to you there. This project looks amazing as it solves most of the problems I was looking to solve at my organization:

PLSQL development in files under git repositories and vscode development
Deployment between environments (Considering liquibase)
Oracle apex version control and comparisons

I already tried Oradew extension but it did have some missing functionality that this project seems to solve. I would also want to get this functionalities, but current extensions don't seem to work properly:

Fast code autocompletion within all plsql packages in the workspace (PLSQL language extension seems not updated and has bugs)
Ctrl + click to open related functions or go to declaration.  (PLSQL language extension seems not updated and has bugs)
SQL execution (The most performant seems SQL Tools)
Native sqldeveloper for vscode continues to be unusably slow and buggy without proper files support.

Hi @brMichal,
du hast doch auch Window 11. Kannst du ggf. Gabriel unterstützen?


Infer and cache date field format instead of re-parsing it for every document

The date field for the default format uses high CPU during parsing. A huge portion of date formatting time(close to 7.12% of CPU time in profiles) goes into parsing, which generally happens when the date format is optional for certain segments. Our customers don’t often set the date parser, but rely on the unoptimized default one. When I changed the date parsing format to a strict one for the same data set, the indexing throughput increased by 8%.
For logs, the date format does not change across different log lines. Hence, it is pretty inefficient to compute the date format for every single document. For such users, we could infer and set a stricter date format after parsing a few documents.
Additionally, 7% CPU seems too high just for date parsing. Maybe Java formatter has improved since the time I ran these tests. CPU profile shows that the most time goes into parsing the optional segments for the date.
Solutions?

We should definitely improve our documentation to clearly call out that the date mapping should be set to a stricter format if known well in advance.
Infer the date time parsing format when it is set top optional and re-use it across requests?

I wonder whether we can leverage the fact that most of the time all documents have the same date format. Maybe the date parser code can cache the date format and attempt to reuse it, only falling back to re-computing the date format when that fails?

Yes, we should cache it.

Started working on this issue, will share baseline benchmarking numbers soon to highlight the differences in cpu for different datetime field formats

Microbenchmarks

Experiment(datetime format)
Data
Average Time(ns/op)
Std Dev

epoch_millis
123456789
915.87
2.613

strict_date_optional_time||epoch_millis
123456789
1141.29
68.7

strict_date_optional_time
"2022-04-05T22:00:12Z"
3019.366
40.168

yyyy-MM-ddThh:mm:ssZ
"2022-04-05T22:00:12Z"
669.83
13.83

strict_date_time_no_millis
"2022-04-05T22:00:12Z"
1155.38
30.03

CPU % Diff Matrix:
| Candidate | strict_date_time_no_millis | strict_date_optional_time | yyyy-MM-ddThh:mm:ssZ
-- | -- | -- | -- | --
Baseline |   |   |   |
strict_date_time_no_millis |   | NA | $${\color{red}-161}$$ | $${\color{green}42}$$
strict_date_optional_time |   | $${\color{green}61}$$ | NA | $${\color{green}71}$$
yyyy-MM-ddThh:mm:ssZ |   | $${\color{red}-72}$$ | $${\color{red}-350}$$ | NA
Grab workload benchmark (Grab is synthetic data generated, osb-benchmark didn't have the workload for testing different data time mappings except http_logs which has a datetime type fallback where I didn't noticed any significant improvement)
We found no significant differences in search performance of both the formats

We've couple of approaches for caching datetime field

Cache it on a node level, if last X datetime parsing continuosly suceeded for a specific datetime field type on the node then we'll cache that type and for each document parsing we'll try the cached datetime field first given that the field mapping does contain the cached datetime field. This will be a micro optimization on a per node basis. It may lead to not honoring the order in which the customer defined the datetime field formatters. Also, any caching maintained will get reset on a node restart.
Cache it on a shard level, on each data node we maintain a mapping of shard to cached datetime field format. The criteria for caching will be similar i.e. for last X datetime parsing request on a particular shard succeeds for a specific datetime format then that format will be cached for the particular shard to be tried first for subsequent doc parsing request on the shard. This may also lead to opensearch not honoring the order of the datetime field formatters provided by the user. Also, any caching maintained will get reset on a node restart. This may also lead to different parsing flow on  different shards of the same index, so it may also address the shard level hotspots receiving different type of datetime fields.
Cache the datetime field format on an index level, after each successful date time parsing we update the index metadata datetime field mapping list with a reordered version containing the last used dateformatter as the first element so that it'll be tried out first for the subsequent indexing requests. This may also lead to us not honoring the order of formatters provided by the user in the datetime field mapping. The caching will not get reset on node restart and will be uniform across the shards for the particular datetime field parsing.
In case where user has provided optional datetime formats but a stricter datetime format suffices for last X datetime field parsing. We may choose to override the datetime format provided by the user to a stricter more optimized version and cache it on an index level for further use. This will lead to not honoring the list of datetime formats provided by the user and therefore customer expectations need to aligned on this.

Once we implement caching, a quick win will be to add a stricter format like strict_no_millis to the default formatter as one of the formatter so that the overhead of strict_date_optional_time will be minimized if the datetime fields conforms with the strict format at runtime
@prabs @tharejas @mgodwan please provide your thoughts on this


Storage location

Hi
pictures and videos are stored in sdcard / Pictures / packagename
It would be nice to configure this path.
Best wishes

Yeah this is a killer feature for us

done,
just cameraFragment.takePhotoOrCaptureVideo(callback, directoryPath, fileName)
will be on next release


Automations won't execute

Configuration

alias: Bedtime Feed Button 3 Bedroom kkk
description: ""
trigger:
  - device_id: 5fad79862faeafbfc3deb7144850c33d
    domain: zha
    platform: device
    type: remote_button_short_press
    subtype: button_3
condition: []
action:
  - type: turn_on
    device_id: 2f16da64200173ee31486f6e99212169
    entity_id: light.hall_light
    domain: light
    brightness_pct: 5
  - type: turn_on
    device_id: f4a42af744ff14a318e78f8781afe9ce
    entity_id: light.lounge_lamp
    domain: light
    brightness_pct: 20
  - type: turn_on
    device_id: 32613080c008b2099a0c2d61e668f8ed
    entity_id: light.kitchen_light_strip
    domain: light
    brightness_pct: 11
mode: restart

Describe the bug
No automations with any tapo bulb I have is running, or when it does jts say 1 out of 3. The device works when I then them on from Lovelace but not Via an automation.
Debug log

This error originated from a custom integration.
Logger: custom_components.tapo.common_setup
Source: helpers/update_coordinator.py:168
Integration: Tapo Controller (documentation, issues)
First occurred: 31 December 2022 at 22:27:01 (3 occurrences)
Last logged: 07:55:46
Error fetching tapo data: Unexpected exception:

Reverting back to tapo version 1.2.18 fixed it for me. No lag. Automations work. Seems strange

Just updated to the latest firmware again on the tapo integration and again it's stopped working. Definitely a fault from the update. Have downgraded from a snapshot and it's working flawless again, automations won't run and in the UI it won't show the light on when it's actually on.

Must add it's only the tapo bulbs which won't turn on so 100% an integration issue,  on the latest OS and the bulbs are the L530

v1.3.4 should fix this

Just updated and still doing it unfortunately. Rolled back to previous snapshot


LED_2 is used by the blemesh example application

Unfortunately there is only 1 LED that can be controlled by a GPIO on the DA1469x development kit boards (daughter plus motherboard). Therefore LED_2 is defined to to use the same GPIO as LED_1, which will be ok as long as they are not both used by the same application...

Good comment, i've updated to use an unused gpio that is brought out to a header allowing easy attachment of an external LED.


Update for new Rust (works with stable, beta and nightly)

And apparently my text editor removed trailing whitespace. I think its a good thing, so I did not revert that ;)

Hah, I thought it needed to be refactored around unstable features but I just forgot about the feature flags. I usually just compile with nightly and assume it compiles on stable if I don't have any feature flags in my crate, but that doesn't always cover dependancies. :smile: Thanks!


wsl.conf does not exist

After April update (1803-17134.1), in my WSL installation (Ubuntu) I don't find wsl.conf:
$ ls -lrt /etc/wsl*
ls: impossibile accedere a '/etc/wsl*': File o directory non esistente

Should I reinstall all WSL?

You can create it if it doesn't exist. Link here if you need it.


Add warnings for managing and publishing labels

Fixing style & branding issues with #1553 - closing this PR after pulling down changes.


[FEATURE REQUEST]

Description
Is your feature request related to a problem? Please describe.
Yes. This can help users know their current mental health state.
Describe the solution you'd like
We can design a simple and insightful test where users answer a series of questions about their feelings, behaviors, and overall well-being. Based on their responses, we will provide an assessment of their current mental health state. This assessment will include personalized suggestions and practical tips to help users improve and maintain their mental health. By offering guidance tailored to their specific needs, we aim to support users in taking positive steps towards better mental well-being.
Describe alternatives you've considered
no.
Additional Information
Context
Use Cases ------
1.Self-Assessment Tool: Users can evaluate their mental health status through a series of targeted questions.
2.Personalized Recommendations: Users receive customized tips and suggestions based on their assessment results.
3.Stress Management Guidance: The test provides specific strategies for managing stress tailored to the user's current mental state.
4.Early Detection: The tool helps identify early signs of mental health issues, prompting users to seek professional help if needed.
5.Resource Connection: Users are directed to relevant resources, such as articles, exercises, or professional services, based on their assessment outcomes.
6.User Engagement: The interactive nature of the test increases user engagement and encourages regular site visits.
Progress Tracking: Users can take the test periodically to track changes and improvements in their mental health over time.
Potential Implementation (optional)
We can implement this easily using HTML, CSS and Javascript.
Priority (optional)
High
Please assign me this feature under GSSOC.

ok let's discuss about this in discord channel.

Thank you for the opportunity, I'll try my best.


Account cycle

Question: if I make multiple listings with the same title (because I have many accounts of the same type), does it cycle through to the next one without delivering the same account twice? Or would I have to make each title unique? (like have #1, #2, etc. on the end of each title).
Also, would you have any interest (or are you able?) in developing an auto-delivery / e-commerce type system for Discord? (for selling game accounts) Paid job of course. Can provide contact info.

Yes, it cycles through accounts, from top to bottom. I don't really know what you mean by e-commerce system for discord, like a chatbot where you can buy accounts by entering commands or some sort of a website? How much are you offering for a such a thing? So we don't waste time.


Simplify smart contract functionality

Summary

The existing smart contract assumed the ability to swap to/from bank denoms to USDF.
Problem Definition

This is overly complex and isn't needed if we just determine the from/to addresses belonging to specific members and reporting accordingly for external settlement.
Proposal

Simplify smart contract by:

Tying aml/kyc attributes to specific bank members during creation
Removal of bank-specific coin to track who minted what
Allow any bank member to burn USDF irrespective of if they minted it or not

For Admin Use

[x] Not duplicate issue
[x] Appropriate labels applied
[x] Appropriate contributors tagged
[x] Contributor assigned/self-assigned

https://github.com/provenance-io/digital-currency-consortium/pull/99
https://github.com/provenance-io/digital-currency-consortium/pull/101


Update OSF-R

OSF-R is our reference implementation of "how to access the OSF API". It needs to be updated to match the v2 API at some point. This will be a good standalone task for someone if we have people that need something to do.

Starting with a simpler implementation of a Python API Client to get some of the concepts down, and will move to R once we are happy with that.

I'm going to not move this over. We can open a new issue if needed.


Defaulting to HTTP/2.0 breaks consumers using .NET Framework

#231 introduces a breaking change for consumers that use .NET Framework, as HTTP/2.0 is not a supported version in HttpRequestMessage.
Minimal repro with <TargetFramework>net472</TargetFramework>:
var adapter = new HttpClientRequestAdapter(new AnonymousAuthenticationProvider());
await adapter.SendNoContentAsync(new RequestInformation()
{
    URI = new Uri("http://example.com")
});

This works as expected on Microsoft.Kiota.Http.HttpClientLibrary version 1.3.8, but throws the following exception on 1.3.9 and 1.3.10:
Unhandled Exception: System.ArgumentException: Only HTTP/1.0 and HTTP/1.1 version requests are currently supported.
Parameter name: value
   at System.Net.HttpWebRequest.set_ProtocolVersion(Version value)
   at System.Net.Http.HttpClientHandler.CreateAndPrepareWebRequest(HttpRequestMessage request)
   at System.Net.Http.HttpClientHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)

I missed the PR but when the target is net462, the package System.Net.Http.WinHttpHandler is referenced.
If the target of the consumer is net472, surely this package will not be pulled in and WinHttpHandler will not be available?

@jcsawyer this directive #if NETFRAMEWORK covers all net framework versions (anything not net core effectively), so I'm not sure what the concern is?

@baywet if the package System.Net.Http.WinHttpHandler is referenced when the target is net462, will this work for consumers with a target of net472 or will it result in a The type or namespace name 'WinHttpHandler' could not be found?
I'm suspecting the latter?
The #if NETFRAMEWORK will resolve the type for net462 but no other NETFRAMEWORK target?

Ah, you're referring to this
I'm not sure whether other versions of netfx will favour the net462 version or the net standard versions. Maybe this is something that @andrueastman can shed a light on?
We might have to update the directive, or the condition for the package.

I am indeed.
If I drop:
<ItemGroup Condition="'$(TargetFramework)' == 'net462'">
    <PackageReference Include="System.Net.Http.WinHttpHandler" Version="[6.0,9.0)" />
</ItemGroup>

in a net472 project, any references to WinHttpHandler will fail to build.

Thanks for the additional information.
This is a fix we had in the previous version of the microsoft graph sdk for years nad here which only had net462 and netstandard2 targets while net472 was already available for years and we didn't get complaints about missing dependencies?

I believe in the context of a net472 project the package manager will pull the net462 dll and resolve the dependency.
This is validated with the latest https://www.nuget.org/packages/Microsoft.Kiota.Http.HttpClientLibrary/1.3.11 release.
The sample net4.7.2 project builds and runs as expected.
Any chance you can confirm if you are referencing the project as a submodule or as a package?

TIL NET Framework packages are confusing as anything!
It looks like everything is working with the 1.3.11 package - running a full e2e pipeline through on component to fully confirm for specific case, but I can re-open/open new issue if there are any problems there.
Many thanks

Thanks for keeping us in check! Closing


xwayland doesn't close

Version
Microsoft Windows [Version 10.0.25206.1000]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
setup using ms store 20.04 LTS then configure as outlined by https://tinyurl.com/donofrioworkremmina2020 mainly:
donofrio@hp6570b:~$ history
sudo apt-get update && sudo apt-get upgrade -y && sudo apt-get dist-upgrade -y && sudo apt-get autoremove -y && sudo apt-get autoclean -y && sudo sync && sudo sync
sudo apt-get install inxi –y
inxi -Fxz
sudo apt-get install xfce* xfce-* hexchat inxi ubuntu-desktop -y
cp .bashrc .bashrc-backup
echo "export DISPLAY=localhost:0.0" >> ~/.bashrc
echo "export LIBGL_ALWAYS_INDIRECT=1" >> ~/.bashrc
echo "export NO_AT_BRIDGE=1" >> ~/.bashrc
sudo chown root -r /tmp/.ICE-unix/
sudo ./fix-dbus.sh
sudo service cron start && sudo service cups start  && sudo service dbus start
Xwayland :1 &
WAYLAND_DISPLAY= DISPLAY=:1 xfce4-session
Expected Behavior
once xwayland session exited from parent (Xwayland :1 &) then the "top-level window" (penguin icon/window) aka "x close window" should exit the Xwayland session but it doesn't and only fix I've found is to logout/restart w11 machine
Actual Behavior
xwayland window just stays open (usable if I start up another session but if I am finished and want to clean up the tasktray it is still running - though cannot see in taskman)
Diagnostic Logs

@lewisdonofrio, thanks for reporting the issue. basically, your case, it's not really using WSLg as your X server nor wayland compositor facing applications, but WSLg is used only the last step to project your Linux desktop to windows side. In this case, the icon on Windows taskbar is not really representing your task-tray software, but your Linux desktop. Thus, you should see only one icon on Windows taskbar regardless how many Linux GUI application you launched in your desktop. By clicking "Close window", it sent request to WSLg over RDP, then your desktop software via wayland protocol, so I suggest you look into your session software to see how it's behaving on such request, thanks!

ok but the icon/app doesn't close when I client "close?"

So moreover how do I get windows "Move/Resize" along with the only one seen so far "Close" so far it goes fullscreen and I have to use "Start Menu"  to get back to the local Windows desktop?


Add u8g2 library support

u8g2 is a C library for creating text and graphics on monochrome displays.
This uses the screen driver with the u8g2 library.
I also included a handful of demo apps.

I haven't looked yet, but given that Amit approves and Tyler has tested this, I think we can safely last-call it.


mat-button cant be clicked on mat-cell

What is the expected behavior?
Button can be clicked in mat-cell
What is the current behavior?
Button cannot be clicked obviously
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Chrome, FF
Latest Angular/Material 7.3.5
Is there anything else we should know?
It was possible before Angular6 in other project. Right now when
  <ng-container matColumnDef="edit">
     Edit

<button mat-icon-button (click)="onClick()"><mat-icon>clear</mat-icon></button>

  </ng-container>

Button does not react at all.
without mat-*-button everything is working fine
Edit: I've figured this happens only when I pass data through function/ getter

@rhyre can you share a reproduction?

wow it was so long ago, I forgot what is was about. Probably got a workaround.
Can be closed.


Greyhound server stops giving with error "Backtrace functionality was not linked" on AWS

Hi,
I am running a greyhound server on AWS's m4.xlarge with entwine index hosted on s3 bucket. Have configured greyhound with cacheSize=2GB. The server keeps failing intermittently giving the following error.
Sweeping <RESOURCE_ID>...Got error 11
Backtrace functionality was not linked
Currently I have only 3 resources indexed in s3. Below are the logs from couple of failures:
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
Exception in pool task: Invalid lazperf chunk - no numPoints
Caught: Reservation failure
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
Sweeping RESOURCE_02... done
RESOURCE_1/info: 1 ms
Creating RESOURCE_02
Trying s3://had-ape-entwine-demo/index: SUCCESS
RESOURCE_02/info: 1 ms
Sweeping RESOURCE_03...Got error 11
Backtrace functionality was not linked
----Restarted docker------------------------
HP: 21117 / 24576: 85.9253%
RESOURCE_2/hier: 0 ms D: [18, 25)
RESOURCE_2/read: 4 ms D: [19, 20) P: 76
RESOURCE_2/read: 9 ms D: [15, 16) P: 6955
RESOURCE_2/read: 4 ms D: [18, 19) P: 90
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
RESOURCE_1/info: 1 ms
Sweeping RESOURCE_03...Got error 11
Backtrace functionality was not linked
The only thing I could see common is that its failing while sweeping RESOURCE_03.
What could be the reason of this failure?

Perhaps the invalid chunk above caused the issue - hard to say.  Either way, the new Entwine workflow (without Greyhound) is preferred: https://github.com/connormanning/entwine


Vue UI not launching

Version
3.5.1

Environment info
System:
    OS: macOS 10.14.3
    CPU: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
  Binaries:
    Node: 11.12.0 - /usr/local/bin/node
    npm: 6.9.0 -  /usr/local/bin/npm
  Browsers:
    Chrome: 73.0.3683.86 (default)
    Firefox: 66.0.1
    Safari: 12.0.3
  npmGlobalPackages:
    @vue/cli: 3.5.1
    aws: 0.0.3-2
    aws-sdk: 2.427.0
    chai: 4.2.0
    cross-spawn: 6.0.5
    cypress: 3.2.0
    firebase: 5.9.1
    firebase-tools: 6.5.0
    firebaseui: 3.5.2
    live-server: 1.2.1
    mocha: 6.0.2
    npm: 6.9.0
    particle-cli: 1.40.0
    stream-http: 3.0.0
    ts-node: 8.0.3
    typescript: 3.3.4000
    uuid: 3.3.2
    vue: 2.6.10
    vue-uuid: 1.1.1

Steps to reproduce
run 'vue ui' from terminal
What is expected?
Vue UI tool is started and launched automatically on http://localhost:8000
What is actually happening?
Terminal reports:
'🚀  Starting GUI...
🌠  Ready on http://localhost:8000

New tab is launched in Chrome, but nothing is displayed.

Recently updated from version 3.3.0.  Was having previously noted issue where using Vue UI tool would fail to build new projects correctly with that version.  Have attempted npm uninstall/reinstall of vue and @vue/cli with same results.
Additional Note:  Receive following warning when running npm install -g @vue/cli:
npm WARN deprecated<EMAIL_ADDRESS>cross-spawn no longer requires a build toolchain, use it instead

Suggest updating dependency to require cross-spawn in npm config to ensure newer package is used.

Forced to refresh the browser should be fine.

Refreshing the browser does not fix this. Using another browser (Firefox or GNOME web) on my Arch Linux system works fine. If I use the path http://localhost:8000/project/select that also works fine in Chrome. I see these errors in my console https://imgur.com/a/XyJUq9D. Both JS files contain HTML. I am using vue-cli 3.5.4.
I just starting trying out Vue and UI in the last few days. This and another basic issue #3664 are very disappointing :(

@bulletmark 	The GUI is still in beta, if you want the stable experience use the CLI in the terminal.

There must be a bug somewhere because vue ui is not working after installing everything from scratch node.js (10.16.3 LTS), npm and @vue/cli.
Firefox shows this error:
An error occurred during a connection to localhost:8000. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG
Chrome shows this error:
ERR_SSL_PROTOCOL_ERROR
Do you have any idea why the SSL of vui could be broken?

Updated from 10.15.1 to 10.16.3.
Same problem.
Reverted back to 10.15.1 and vue ui worked again
Tried 10.16.3 again and it died
Updated to the latest version 12.11.1 and vue ui works again
So somewhere between 10.15.1 and the latest version it doesn't work (or perhaps just 10.16.3 LTS specifically)

Unfortunately now building the project doesn't work anymore and throws out other errors


add boilerplate templates and verification

What type of PR is this?

not sure what kind is, will go without one
What this PR does / why we need it:
adding boilerplate templates and hack/verify-boilerplate.sh
Which issue(s) this PR fixes:

N/A
Does this PR introduce a user-facing change?:

NONE

Thanks! As discussed offline, we do not have presubmits configured for ingress2gateway now.
Will add it tomorrow and ping for a review again.

attempt to add the presubmits: https://github.com/kubernetes/test-infra/pull/29895/files

/retest

Thanks @LiorLieberman! This change LGTM, but it looks like we need to fix some things before this can actually merge.
/approve

/retest

This is blocked by https://github.com/kubernetes-sigs/ingress2gateway/pull/29
Once this merged, I will rebase.

/retest

/retest

/retest

/retest

Thanks @LiorLieberman!
/lgtm


Why does the recap often show events after death. Am i misunderstanding it?

I've had several instances where the deathrecap shows attacks after the character already died.
In this example the player was overkilled at the 5th event down (-4s)

It shows on both views

Is this intentional? if so, why does this happen?

This is unfortunately just how the game processes damage events. The animation of final sting takes 4 seconds to play, the damage however is already recorded as soon as the bee finishes casting it. DeathRecap records events as they are snapshot by the server. Say if you used a lot of mitigation before you died, even though the damage number has not appeared yet on your screen the bee finished casting before you used your mitigation (that is how it will appear in the death log) and the damage will be applied unmitigated.

so even if it feels counter intuitive to see the damage numbers not as they showed on your screen, this way you'll be able to tell if you died because mitigation / healing was applied too late (after the server snapshot the damage)

A bit confusing, but at least theres a proper reason for it. Thanks for the explanation!


Responses of SSR sites served without compression

The HTML & JSON responses of my Remix app don't get automatically compressed by Cloudfront.
❯ npx sst version
0.1.1

So, I think this happens because these responses use the streamifyResponse handler on AWS lambda and Cloudfront doesn't compress streamed responses, I think


health-check does not appear to function properly in containerized environment

Bug Description
If I'm understanding this correctly; the --health-check flag does not seem to be workable in a containerized environment at all. Probe checks come from an address external to the pod; so pinning the server to localhost will force any kubernetes startup/liveness/readiness probes to fail.
Using health-check in alloydb-auth-proxy
/alloydb-auth-proxy <project> --health-check --http-port=8090 --structured-logs --credentials-file=<mounted_secret_file>

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 <IP_ADDRESS>:8090          <IP_ADDRESS>:*               LISTEN      5079/alloydb-auth-p

Events:
  Type     Reason     Age                    From     Message
  ----     ------     ----                   ----     -------
  Warning  Unhealthy  2m18s (x469 over 72m)  kubelet  Readiness probe failed: Get "http://<pod_ip>:8090/readiness": dial tcp <pod_ip>:8090: connect: connection refused

^ <pod_ip> would be the address of the kube pod.
Using use_http_health_check in cloud-sql-proxy
/cloud_sql_proxy -instances=<instances> -credential_file=<mounted_secret_file> -use_http_health_check -health_check_port=8090 -structured_logs

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 :::8090                 :::*                    LISTEN      23/cloud_sql_proxy

*curl run from internal VM within same kube cluster
$ curl -vL http://<pod_ip>:8090/startup
*   Trying <pod_ip>:8090...
* Connected to <pod_ip> (<ip>) port 8090 (#0)
> GET /startup HTTP/1.1
> Host: <pod_ip>:8090
> User-Agent: curl/7.83.1
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Tue, 18 Oct 2022 22:44:20 GMT
< Content-Length: 2
< Content-Type: text/plain; charset=utf-8
<
* Connection #0 to host <ip> left intact
ok

Environment

OS type and version: alpine linux on kubernetes
Proxy version: 0.5.1

Can you use --http-addr <IP_ADDRESS> here?
(If this really doesn't work by default, we should update the examples using k8s here)

@kurtisvg as far as I can tell this flag is unavailable in the version I'm using (0.5.1); in fact the description of the health-check flag explicitly states it can ONLY be bound to localhost.

We fixed this in #131 which will be in the next release (v0.6.0). We're a bit behind schedule with the release freeze from Cloud Next, but now that's lifted, I'll just ship the new release today. I'll update here when it's ready.

@enocom that'd be perfect! Thanks so much for the quick responses y'all

if I can make one small suggestion it would be to clear up some of the verbiage here now that http-address is configurable in 0.6.0

I have an issue for tightening up the documentation and will add that to the list.

@enocom yep that took care of it, thanks again for the quick turnaround!

You bet. Glad it's working for you.


Create only one private route table when single_nat_gateway is true

Right now, this module is creating a route table for every subnet even when there is a single NAT Gateway. This is unnecessary, as all the route tables are using the same NAT Gateway, and multiple subnets can be associated with the same route table.
I propose that when the user elects to use a single NAT Gateway, all the private subnets should be associated with just a single private route table.

I just ran into this myself, I only needed a single NAT instance and therefore assumed that would only create a single routing table across all the private subnets (3 subnets in my case). Unfortunately I was still left with 3 private routing tables. I'd like to see this module support a single private routing table 👍

Any update on this?
@lorengordon's fork looks very good. can you create a pr and merge it?

@yardensachs I should be able to take a look at this during upcoming weekends.

Apparently, it will be during next weekends... sorry for the delay!

Thanks

Isn't the creation multiple subnets per AZ?  I see now. Just be aware that NAT traffic between the nat and instances across AZs will incur cross-az data charges. (A cautionary tale)

@antonbabenko thank you!


NodeBroker: delta protocol with incremental updates

[ ] Write RFC
[x] Implement blue-green workaround
[x] Merge blue-green workaround to 24-3
[x] Merge blue-green workaround to 24-2
[ ] NodeBroker refactoring?
[ ] DynamicNameserver refactoring?
[ ] Implement delta protocol in NodeBroker
[ ] Implement delta protocol in DynamicNameserver

Closing in favor of #11064.


pip install requirement file

Hi,
I'd like to use this tool to manage asset for my GEE account but am running into some issues with the pip install.  I get the following error after following your instructions on install:
You must give at least one requirement to install (see "pip help install")
I tried the --allow-all-external and --allow-unverified but it looks like these functions have been deprecated.  Do you have any suggestions?
Thanks!
Jon

Hi,
Can you paste here how exactly are you running the installation? My suspicion is that you are missing the dot in the command, i.e. doing: pip install instead of pip install . in the root directory of the program. Let me know if it helped!
Cheers,
Lucas

That did the trick!  Missed the period in the documentation.
Thanks!
Jon

Great! Shout if I can help further.


Issue 44749: Rendering query grid uses two DB connections concurrently

Rationale
Using multiple connections concurrently is bad because it can lead to deadlocks trying to get DB connections from the pool during heavy load. Better to use a single connection when possible, including for the main grid and its aggregate query
Changes

Check if we have a Connection we can reuse from the primary ResultSet that's driving the grid's data

I found a simpler approach compared to my previous attempt. I've queued multiple instances of BVT-A for both Postgres and SQLServer to make sure there's not an intermittent failure lurking.


Django Celery trace.id integration

What does this pull request do?

Set automatically the trace_parent (when available) for a Celery task.
Allow to disable this feature globally
Allow to opt-out of this feature per task

Todo

[x] Set automatically the trace_parent (when available) for a Celery task.
[ ] Allow to disable this feature globally by setting ELASTIC_APM["CELERY_CORRELATION"] to True or False
[x] Allow to opt-out of this feature per task
[x] Document this new feature
[ ] Add relevant tests ?

Related issues
closes #1370

@beniwohli Thanks :)
Ok, so I added the headers inconditionnally and fixed a possible bug.
I don't know what kind of test to add nor how to properly add them (although I seen the 'test' directory). If anyone can help.
Otherwise it's good to go for me.

Hey @TPoret, sorry for the delay on this PR. I looked into how we could test this, but unfortunately, Celery doesn't trigger the before_task_publish signal when in "always eager" mode (see https://github.com/celery/celery/issues/3864). So as it is, we can't automatically test this without a substantial change in how we run celery tests.
Did you test the functionality in your environment and saw satisfactory results?

Hello @beniwohli no worries for the delay.
Yes I had good results, although on some Celery versions I had to add a fix (see https://github.com/elastic/apm-agent-python/pull/1371/commits/0ee3e966da1ca5b48e54846f8bb934229d91c549)


pandas colums as strings to force use of contains filtering

https://stackoverflow.com/questions/39092067/pandas-dataframe-convert-column-type-to-string-or-categorical?rq=1

solved, but perhaps contains is not the best way of searching. for example atomic number of 1 would return 1, 11, 10, 21, 31 etc


COT-672 Map "Type C" equipment Facility Code in HMC Room Attributes Table

…able
Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/COT-672
Change description
Map "Type C" equipment Facility Code in HMC Room Attributes Table
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

PIPELINE: https://build.hmcts.net/job/HMCTS_d_to_i/job/hmc-cft-hearing-service/view/change-requests/job/PR-423/


Indent list of open files

Similar to #17130

Same question as the other change -- does anybody depend on this? I guess probably not, since @rbuckton signed off an a previous change.


Anonymous user for Kibana and ElasticSearch in ODFE 1.11.0

Hi all,
I'd like to get anonymous user both for ES and Kibana with ODFE 1.11.0. As far as I saw, the instructions at opendistro-for-elasticsearch/security#42 are obsolete so I tried to adapt them for 1.11.0 with no luck. This is what I tried:

In config.yml enable anonymous access.

  dynamic:
    http:
      anonymous_auth_enabled: true

Created anonymous role with required permission at roles.yml (this is what needed to be changed)

opendistro_security_anonymous:
  reserved: true
  cluster_permissions:
    - 'CLUSTER_COMPOSITE_OPS_RO'
  index_permissions:
    - index_patterns:
        - '*'
      allowed_actions:
        - 'indices:data/read*'
        - 'indices:admin/mappings/fields/get*'

Created role mapping for opendistro_security_anonymous_backendrole role at roles_mapping.yml file

opendistro_security_anonymous:
  backend_roles:
  - "opendistro_security_anonymous_backendrole"

Executed securityadmin tool to apply changes
Updated kibana.yml to enable anonymous access for kibana (and restarted)

# Anonymous access
opendistro_security.auth.anonymous_auth_enabled: true

The result is I can read the .kibana index querying the cluster but I still see the login page in Kibana.
Thanks for your help!

We are doing some "spring cleaning in the fall", and to make sure we focus our energies on the right issues and we get a better picture of the state of the repo, we are closing all issues that we are carrying over from the ODFE era (ODFE is no longer supported/maintained, see post here).
If you believe this issue should still be considered for current versions of OpenSearch, apologies! Please let us know by re-opening it.
Thanks!


#35: Handle hover events (new)

Issue:

#35

Past PR:

#114

Couldn't reproduce the bug in main branch, so the fix is probably not needed.


Could you add more apis such as Front() and PushFront()?

Dear author,
I have a requirement such as to inquire the first element of queue but not pop it. It's just like what Front() does in std::vector.
Also I want to push one element in the front of queue.
Do you think these two functions Front and PushFront can be added in? Thank you.

Do you think these two functions Front and PushFront can be added in?

In a multi-threaded application front would return a reference to an element in the queue. By the time the element is examined, another thread may pop this element, leaving you with an invalid reference. For this reason pop is not an applicable use case for this non-blocking queue.
You may need to use a non-blocking queue which is based on hazard (smart) pointers, or use a blocking queue, e.g. std::vector with std::mutex.


Add stim.PauliString.iter_all

Include optional min_weight and max_weight arguments that control how many non-identity terms there can be.
Unsure what the default behavior should be w.r.t. iterating over signs, and imaginary signs.

Is the idea here it to produce all 4^N  possible Pauli strings (or a subset of them dependent on the weight) given N qubits (times 4 for +/-1 and +/- i)? Sounds like a small modification of this on the C++ side or some itertools gymnastics on the python side.

@fdmalone  Yeah that's exactly it. There are a few tricky things beyond the bit twiddle tricks to jump straight from one to the next:

The pauli string can be larger than one word. For example, it might be a 1000 qubit pauli string.
The things the bit twiddle trick is going between aren't quite right. "X_" and "Y_" and "Z_" all have weight 1. After you generate a permutation of weight w, you then have to generate the 3^w Pauli strings compatible with that weight.
Writing iterators in C++ is a giant pain compared to python.

I think it should be the case that generating all Pauli strings of weight w with length n takes time O(n w 3^w). Generating all paulis of weight 1 to weight 3 of length 256 should probably take less than a second. At least, less than second without python in the loop. If python literally can't allocate enough objects in that time, then oh well.
I think it would also be nice if by default it iterated from low weight to high weight, ascending from simple errors to complex errors. But that's not necessary.

Sounds good. Can I get assigned to this, sounds fun.

@fdmalone Any updates?

@Strilanc  Sorry, got pulled into other things. I should have a PR later today


Fix expression at path FilePath .... failed to parse error and introduce nix-gitignore (fix impurity in release.nix)

seems like docker image uses an old version of nix

Oh I almost forgot to say this: thank you for the PR @srghma!

@ixmatus, as I wrote, nix-gitignore will work only on nix 2.0
https://github.com/siers/nix-gitignore/#for-nix-20-or-higher

@adnelson can we drop nix2 support?

@srghma oh, then I don't think we should use nix-gitignore for now; as a user, I definitely use nixfromnpm in non-nix2.0 environments.

ok, the fix wasnt hard at all)

👍


Allow ui-negative-number in ui-percentage-mask

In percentage mask, analise the tag ui-negative-number e correct value
and mask

Coverage decreased (-0.9%) to 96.388% when pulling 1aea674a6c83faafb63397adc9f5a36aa8553d8b on Konageski:master into 2ea60560c71434283494c9e83a2d3065bafece99 on assisrafael:master.

Coverage decreased (-0.7%) to 96.571% when pulling 790f8a4fdfe552f815ab89f09138bc935dd7854b on Konageski:master into 2ea60560c71434283494c9e83a2d3065bafece99 on assisrafael:master.

I'm not sure about this change.
Can you implement a test case that shows the behavior you need?

Today is not possible to use negative number in percentage-mask field.
This change able to use ui-negative-number in ui-percentage-mask field.
I use this change in my system.
<input type="text" name="negativePercentage" ng-model="obj.negativePercentage" class="form-control"  ui-percentage-mask="2" **ui-negative-number** required>

+1

This definitely should be available in this lib. Thanks @Konageski.

Replaced by #300


Add custom ESGST header to requests

This should allow cg to identify which requests are coming from ESGST.

What an original idea!


Tile.Image and canvas

Add a new function to OpenLayers.Tile.Image to get a canvas context of the image.
This function can be used to get the image data in a base64 encoding (with an optional format conversion), to save the image using the File API or to get the pixel color at a specific position.

Note: the function returns a canvas context but the canvas is still available in the canvas property:
var context = tile.getCanvasContext();
if (context) {
  var data = context.canvas.toDataURL('image/jpeg');
}

For now, I'm using the canvas to store the tiles for offline use and to analyse the pixel color (just experiments, nothing really finished yet).
Offline: I'm using getCanvasContext to transform the image to a base64 string and store it into the browser (localStorage, Web SQL Database, IndexedDB, ...)
Pseudo code:
for (var i = 0, ilen = layer.grid.length; i < ilen; i++) {
  for (var j = 0, jlen = layer.grid[i].length; j < jlen; j++) {
    var tile = layer.grid[i][j];
    var dataUrl = tile.getCanvasContext().canvas.toDataURL();
    // cache is a wrapper around the storage system
    cache.set(tile.url, dataUrl);
  }
}

Then, when offline, the Tile.Image.setImgSrc(url) will receive a data URI from the cache instead of an URL.
Pixel analyse: getCanvasContext is used to get the pixel color under the mouse cursor to notify the user that he can click to get more infos:
Pseudo code:
map.events.register('mousemove', this, function(evt) {
  // layer is my raster POI layer, transparent png image with some markers
  // just pretend that getTileFromPixel() and getPixelRelativeToTile() exists ...
  var tile = getTileFromPixel(layer, evt.xy);
  var pixel = getPixelRelativeToTile(tile, evt.xy);
  var imgData = tile.getCanvasContext().getImageData(pixel.x, pixel.y, 1, 1);
  // imgData is the color (RGBA), an array of int (0-255), length == 4
  if (imgData.data[3] !== 0) {
    // the pixel under the cursor is not transparent; notify the user.
    map.div.style.cursor = 'pointer';
  } else {
    map.div.style.cursor = '';
  }
});

d6adcceb961199d480ca8fd8618ddafed2efb2c7 adds the crossOrigin attribute to allow cross-domain images requests, detailed article: http://blog.chromium.org/2011/07/using-cross-domain-images-in-webgl-and.html (this article is about WebGL but it's the same for canvas).
This new attribute has no effect on normal usage (when not using getCanvasContext or if the browser doesn't support canvas). Tested with FF, Chrome and IE7.

FYI: canvas.toDataURL is not supported on Android 2.x.

Unfortunately setting img.crossOrigin in Firefox 10 causes the image to not load, and the onImageError function will be invoked, when using tiles from non CORS enabled sources. You can see that by trying the lite.html example (vs. the osm.html example, where tiles have the Access-Control-Allow-Origin header set).

See https://github.com/fredj/openlayers/pull/2

I've created a small example to show the new function usage but it doesn't work in FF (save osm-grayscale.html into the examples dir).
The tiles are correct (data url instead of url) but the layer is not in grascale. Works well in Chrome.


Add Items to Editable List via Script?

Hi upgradeQ - first off thank you VERY much for your great tutorial/cheatsheet - it has helped me wrap my head around the various OBS objects. I have a question you might be able to answer - let me first setup the problem. I have a string list stored programmatically (e.g. from a pandas dataframe), let's say list_items = ["Item 1", "Item 2", "Item 3"]. I noticed that the regular list/combo-box has the function obs_obs_property_list_add_string(obs_property_t *p, const char *name, const char *val) to insert items. My question is if you are familiar with how to do likewise for the editable list? I can't find much in the documentation regarding this. Thank you for your help and advice!

Hello @jdbodyfelt , I've not yet used obs_properties_add_editable_list , however there is a lot of API usage examples here.

Sweet! Thanks for that link! Sure I can dig something out from it. Currently, making end users edit their own CSVs and just loading to a disabled multiline text. Dirty, but it works.


fix: dedupe advisory paths in yarn auditor

Fixes #239
Duplicate paths were fixed in the npm auditor but not the yarn one as it runs through different code.  I moved the dedupe code into getSummary as this is common to all the implementations.

Released in v6.1.2, available now!


How to replace absolute with relative URLs in docs-scraper?

Hello,
I am currently working on a documentation website generated with Jekyll, and Meilisearch has been pretty easy to add, with the docs-scraper and  the docs-searchbar.
In fact, I have many instances of my documentation website hosted in different places
That means that I have to run the docs-scraper for each site (update of repository).
I wish I could run only one scraper for all my sites, and be independent of where each documentation site is hosted. so my question is:

Is it possible to replace absolute with relative URLs in docs-scraper?.

I guess, I can do that somehow overriding some of the logic from the source code of the scraper. But is there another way? (maybe someone else has already thought/discussed about that).
Thanks in advance!!

Hello @suppadeliux!
Does the start_urls option work for your usecase?
https://github.com/meilisearch/docs-scraper#start_urls
You can define the absolute URL in the array like:
{
  "start_urls": ["https://www.mysite1.com", "https://www.mysite2.com"]
}

Sorry if I miss understood your issue.
PS: I transfer your issue into the docs-scraper repo


Plugin system

The base for a plugin system and I build one plugin to test with

My screen record tool is cutting short so here are 3 gifs to show the features of the plugin.

Looks awesome!! A plugin system for this component ? Right ?

Yes I added a plugin system for this component

Sorry I accidentally clicked on close PR button. terminal-in-react-pseudo-file-system-plugin seems like you're developing a plugin system where any user can create a plugin for the component. Awesome!!

The gifs are of the plugin I created here https://github.com/jcgertig/terminal-in-react-pseudo-file-system-plugin

the code in this pr allows anyone to add plugins

terminal-in-react-pseudo-file-system-plugin is just my test plugin

I want to discuss something with you. But where ?

The changes in this pr are breaking so this would have to be a major release

add a gitter chat for the repo?

Ok! I will go ahead and make a chat room.

Can you resolve the conflicts ? I've pushed some changes (merged history feature) !

@nitin42 done also im looking into the hound ci issue

Did you also fixed this👇  in this PR ?

No in the last one

One more thing, last time I checked color, backgroundColor and barColor were properly applied. Facing some gotchas now!

Try changing these props... and let me know if its working or not!

I think we are overriding some of the styles. May be that's why ?

See this :

@nitin42 fixed

Think we can go ahead and add this as the v1 of the plugin system Im still working on new bits but will be a while

Just remember these changes are breaking to older versions

@nitin42 ^

Looks great! I'm going to my bed now but I'll merge this in the morning and will publish the V1 then 😄

Close, Minimise and Maximise not working !! Please look into this..

Yup. Checked everything! not working 👇

Close, Max and Min were not working but I've fixed this. Thanks!


Create OSRD of iteration 1

Define the scope of the iteration and create the requirements specification document of the iteration 1.

OSRD created.


⚠ Bofrost.at has degraded performance

In 632ed4c, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 981 ms

Resolved: Bofrost.at performance has improved in da50ce1 after 30 minutes.


Fix Clang Compile Warnings/Errors (and Typos)

Clang (e.g. 14.0.5) issues compile errors for several issues when compiled with strict settings. Specifically, the capitalization of the Windows header file is incorrect, NULL is accidentally used in some places, and there are some implicit casts and signedness comparisons that should be clarified.
There are also a lot of typos both in the comments and in error messages.
This PR fixes all identified issues, separated into two commits which can be cherrypicked as the repository manager desires.

@geometrian Thanks! I didn't realized there are so much typos in comments 😅
For header filename capitalization, IIRC it was an annoying issue of the combination of compiler front-end's (virtual) filesystem and underlying OS'  filesystem(especially emerges when cross-compiling). For example MinGW uses all lower-case header filenames.  So I gave up using Capitalized header file name.

https://reviews.llvm.org/D21113
https://github.com/commercialhaskell/stack/issues/3918

so possible solution may be...
#ifdef __MINGW32__ // mingw gcc, llvm-mingw(clang)
#include "windows.h"
#elif defined(_MSC_VER) || [clang-cl and clang on case-sensitive filesystem(how to determine?)]
#include "Windows.h"
#else
#include "windows.h"
#endif

Yah; I noticed it failed on MinGW when the CI check failed, and pushed another commit up, which fixes it. It works similarly to what you just now suggested: it normally uses <Windows.h>, while on MingGW it uses <windows.h>. The internet tells me there are still other cases if it's supposed to run on mobile or ancient Windows, but for now at least this is better than before and passes all tests. Sigh, MS 😩
Another solution to consider for Clang particularly would be to temporarily disable the warning for #includeing that one file, or to get the functionality some other way (e.g. C++17 std::filesystem; I know you're targeting C++11, but 2022 > 2011, sooo).

@geometrian Thanks! Merged!

Another solution to consider for Clang particularly would be to temporarily disable the warning for #includeing that one file

Since tinygltf uses few WIn32 API, how about declare it explicitly in tiny_gltf.h and do not include windows.h header file?

how about declare it explicitly in tiny_gltf.h and do not include windows.h header file?

Not sure what you mean? Like, making the user include <Windows.h> themselves? Or, forward-declaring the Win32 API functions? I generally feel like both options could be potentially surprising, but could work. I personally think the current method is good (maybe a few tweaks down the road, even robust to weird MS platforms), especially if stuff like moving implementation to the ".cc" file or using a modern language standard aren't on the table.

temporarily disable the warning for #includeing that one file

Just to clarify, the idea there was to make Clang be quiet about the nonportability of the filename. The warning is correct, but not fixable by anyone for this particular file now that MS has defined different cases, nor relevant to actual portability given that it's a platform-specific header. Disabling the warning to ignore fundamental brokenness is just as good in my head as patching around the brokenness.

forward-declaring the Win32 API functions?

Yes I meant it: e.g.
extern int MultiByteToWideChar(...)
#define CP_UTF8 ...

temporarily disable the warning for #includeing that one file

This would be also an solution. Additional PR to suppress clang warning for #include <Windows.h> appreciated!

Err, the solutions are orthogonal; only one is required. If you really wanted to, you could do both:
#ifdef __clang__
	#pragma clang diagnostic push
	#pragma clang diagnostic ignored "-Wnonportable-system-include-path"
#endif
//(Windows.h include stuff here.)
#ifdef __clang__
	#pragma clang diagnostic pop
#endif

but again there's no point, since the header is now being included more portably.
If you're just using it for MultiByteToWideChar though, one should probably change all this to #include <stringapiset.h> instead of <Windows.h>. Perhaps the capitalization of that is more reliable, even besides including far less stuff.


\uD83B\uDE00 is an 'IDStart', or is it?

Hello
U+1EE00 is an id start, if I've not been mistaken; but
https://github.com/jquery/esprima/blob/master/test/fixtures/ES6/identifier/invalid_escaped_surrogate_pairs.js fails. Looks like it is not just esprima though, as chrome is also failing to parse var \uD83B\uDE00.
I'm not sure whether it's me missing something, but I would be glad to know. Thanks!

ID_Start code points represented as a surrogate pair are not valid identifiers. var \u{1EE00} and var 𞸀 are valid indeed, but var \uD83B\uDE00 isn’t.
See:

Valid JavaScript variable names in ECMAScript 6
Valid JavaScript variable name validator

I had no idea that was the case; now I know what UnicodeEscapeSequence stands for in the spec -- Thanks a lot @mathiasbynens for the clarification!


add transformers gptq support

Proposal to fix https://github.com/huggingface/text-generation-inference/issues/962

perhaps I am doing something wrong, but when I made this change and volumed in the change, this did not fix the issue.
docer-compose volume:
- ./server/text_generation_server:/usr/src/server/text_generation_server


proposal: sync: Add sync.MutexMap generic type

Proposal Details
Proposal: Add sync.MutexMap generic type
I propose adding a new generic sync.MutexMap type that provides a type-safe, mutex-protected map implementing the same API as sync.Map plus a Len() method. This type would serve as an alternative to sync.Map for the common case where a basic mutex-protected map is sufficient or where sync.Map would not perform well.
Background
The current sync.Map documentation states: "Most code should use a plain Go map instead, with separate locking or coordination, for better type safety and to make it easier to maintain other invariants along with the map content."
However, developers must currently implement their own mutex-protected maps, leading to:

Duplicated code across projects
Potential subtle correctness issues
Inconsistent implementations

Use Cases

Session Storage: Web servers often need to store session data with mixed read/write patterns. A mutex-protected map is ideal for this common scenario where cache hit rates are unpredictable.

Configuration Management: Applications that need to occasionally update configuration values while handling frequent reads. Unlike sync.Map which is optimized for read-mostly workloads, MutexMap performs well with mixed access patterns.

Connection Pools: Managing a pool of database or network connections where connections are frequently borrowed and returned, requiring balanced read/write access.

Request Deduplication: Services that need to track and deduplicate in-flight requests, where items are frequently added and removed.

Rate Limiting: Tracking request counts per user/IP with frequent counter updates, where sync.Map's optimization for non-overlapping writes doesn't provide benefits.

Performance Considerations

Memory Usage: A MutexMap may use less memory than sync.Map as it only needs a single map and mutex, though this should be verified with benchmarks.

Cache Behavior: The simpler memory layout of a mutex-protected map could potentially improve CPU cache utilization, but this needs empirical validation.

Predictable Behavior: The performance characteristics of mutex-based locking are well understood, potentially making performance easier to reason about.

Proposal
Add a new generic type sync.MutexMap that wraps a standard map with a mutex:
type MutexMap[K comparable, V any] struct {
    // contains filtered or unexported fields
}

// New creates a new MutexMap
func NewMutexMap[K comparable, V any]() *MutexMap[K, V]

// Methods with type safety
func (m *MutexMap[K, V]) Store(key K, value V)
func (m *MutexMap[K, V]) Load(key K) (value V, ok bool)
func (m *MutexMap[K, V]) LoadOrStore(key K, value V) (actual V, loaded bool)
func (m *MutexMap[K, V]) LoadAndDelete(key K) (value V, loaded bool)
func (m *MutexMap[K, V]) Delete(key K)
func (m *MutexMap[K, V]) Range(f func(key K, value V) bool)
func (m *MutexMap[K, V]) Clear()
func (m *MutexMap[K, V]) Swap(key K, value V) (previous V, loaded bool)
func (m *MutexMap[K, V]) CompareAndSwap(key K, old, new V) bool
func (m *MutexMap[K, V]) CompareAndDelete(key K, old V) bool
func (m *MutexMap[K, V]) Len() int

Rationale

Type Safety: Generic implementation provides compile-time type checking
Performance: A mutex-protected map may be more efficient for workloads sync.Map is not intended for
Safety: Providing a standard implementation helps avoid common mistakes
Convenience: Reduces boilerplate in codebases
Length: Unlike sync.Map, a mutex-protected map can efficiently track its size

Compatibility
This change is fully backwards compatible as it only adds new functionality.
Implementation
I'm happy to implement this if the proposal is accepted. The implementation would include:

Core type and methods
Comprehensive test suite
Benchmarks comparing performance with sync.Map under various workloads
Documentation and examples

Related Issues and Documentation

sync: new version of sync.Map #47643 (closed)
sync: reduce contention between Map operations with new-but-disjoint keys #21035
sync: document when and when not to use Map
Package sync > type Map 				¶ 				 				1.9
sync: add examples for Mutex and RWMutex
proposal: typesafe sync.Map - affected/package: /x/sync #52085 (closed)
proposal: x/sync: add multimap #61939 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

Duplicate of #47657


[Bug] 多吉云更新报错：cannot unmarshal number into Go struct field UploadCdnCertResponseData.data.id of type string

描述问题
[2024-11-07 12:00:58]
部署失败
failed to execute sdk request 'cdn.UploadCdnCert': json: cannot unmarshal number into Go struct field UploadCdnCertResponseData.data.id of type string

duplicate #308

感谢！已经彻底解决！部署成功


precision lower than mmdetection on coco2014?

❓ Questions and Help
I train the e2e_mask_rcnn_X_101_32x8d_FPN_1x.yaml as the given configs on coco2014，here is the final model:
maskrcnn_benchmark.trainer INFO: eta: 0:00:00  iter: 180000  loss: 0.5438 (0.6606)
loss_box_reg: 0.0952 (0.1084)  loss_classifier: 0.2156 (0.2108)  loss_mask: 0.2093 (0.2437)
loss_objectness: 0.0153 (0.0431)  loss_rpn_box_reg: 0.0171 (0.0547)  time: 0.6992 (0.6999)
data: 0.0103 (0.0102)  lr: 0.000100  max mem: 5877

the evaluation result is as follows:
Evaluate annotation type *bbox*
DONE (t=39.88s).
Accumulating evaluation results...
DONE (t=6.57s).
 Average Precision  (AP) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.361
 Average Precision  (AP) @[ IoU=0.50      | area=   all | maxDets=100 ] = 0.573
 Average Precision  (AP) @[ IoU=0.75      | area=   all | maxDets=100 ] = 0.392
 Average Precision  (AP) @[ IoU=0.50:0.95 | area= small | maxDets=100 ] = 0.215
 Average Precision  (AP) @[ IoU=0.50:0.95 | area=medium | maxDets=100 ] = 0.395
 Average Precision  (AP) @[ IoU=0.50:0.95 | area= large | maxDets=100 ] = 0.460
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=  1 ] = 0.308
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets= 10 ] = 0.493
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.519
 Average Recall     (AR) @[ IoU=0.50:0.95 | area= small | maxDets=100 ] = 0.333
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=medium | maxDets=100 ] = 0.557
 Average Recall     (AR) @[ IoU=0.50:0.95 | area= large | maxDets=100 ] = 0.647
Loading and preparing results...
DONE (t=4.56s)
creating index...
index created!
Running per image evaluation...
Evaluate annotation type *segm*
DONE (t=43.13s).
Accumulating evaluation results...
DONE (t=6.25s).
 Average Precision  (AP) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.331
 Average Precision  (AP) @[ IoU=0.50      | area=   all | maxDets=100 ] = 0.541
 Average Precision  (AP) @[ IoU=0.75      | area=   all | maxDets=100 ] = 0.352
 Average Precision  (AP) @[ IoU=0.50:0.95 | area= small | maxDets=100 ] = 0.151
 Average Precision  (AP) @[ IoU=0.50:0.95 | area=medium | maxDets=100 ] = 0.359
 Average Precision  (AP) @[ IoU=0.50:0.95 | area= large | maxDets=100 ] = 0.480
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=  1 ] = 0.293
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets= 10 ] = 0.454
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.475
 Average Recall     (AR) @[ IoU=0.50:0.95 | area= small | maxDets=100 ] = 0.278
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=medium | maxDets=100 ] = 0.517
 Average Recall     (AR) @[ IoU=0.50:0.95 | area= large | maxDets=100 ] = 0.623
2019-02-22 08:10:21,759 maskrcnn_benchmark.inference INFO: OrderedDict([('bbox', OrderedDict([('AP', 0.36133887907093726), ('AP50', 0.5726409013708667), ('AP75', 0.39222788414397924), ('APs', 0.21467701327635888), ('APm', 0.39488310429312873), ('APl', 0.45967256947157153)])), ('segm', OrderedDict([('AP', 0.3311802775758692), ('AP50', 0.5414932401844765), ('AP75', 0.35199652963065065), ('APs', 0.15109910831968543), ('APm', 0.3589733553080113), ('APl', 0.4801035835717649)]))])

However，the result is much lower than the mmdetection results,which is as follows:

I wonder if you could help me to figure out why the precision is lower? thx

Hi,
This is very weird. We have trained those models and we matched the results in Detectron, see https://github.com/facebookresearch/maskrcnn-benchmark/blob/master/MODEL_ZOO.md#end-to-end-faster-and-mask-r-cnn-baselines, which is 42.2 for boxes and  37.8 for masks
What is the version of PyTorch and maskrcnn-benchmark that you are using? For maskrcnn-benchmark, can you tell us what is the last commit in the codebase?
Also, what command did you use to train the model?
It would be good to understand what happened, but I don't think it was a regression that was added to maskrcnn-benchmark recently.

@fmassa
- Pytorch :1.0.0   py3.6_cuda9.0.176_cudnn7.4.1_1
- maskrcnn-benchmark:
branch master
commit f8b0118392aae793771cfc6cd869ad0a601d5c92
Author: xelmirage<EMAIL_ADDRESS>Date:   Tue Feb 19 17:00:48 2019 +0800
- command
export NGPUS=3
python -m torch.distributed.launch --nproc_per_node=$NGPUS
 /tools/train_net.py --config-file "configs/e2e_mask_rcnn_X_101_32x8d_FPN_1x.yaml"
- dataset
coco2014

The MAX_ITER is 180000 following the default configuration,so as other configurations.
I wonder if training for longer periods will lead to better results.

@zhangliukun you are not following the right learning rate adaptation rules.
The default config is for 8 GPUs, you'd need to modify the number of iterations, the learning rates and the learning rate schedules in order to match the results from the config.
Check the information in https://github.com/facebookresearch/maskrcnn-benchmark#single-gpu-training for more details
If when modifying the number of iterations, learning rate and learning rate schedules as expected you still see lower accuracies, please let me know


Why do I add PSNR and SSIM values are very low

Why do I add PSNR and SSIM values are very low

PSNR value below 10

Hi.
I don't understand your question.
Could you please elaborate?

I added the PSNR value between SR and HR to your program, but during the training, I found that the PSNR value was very low.

I added the PSNR value between SR and HR to your program, but during the training, I found that the PSNR value was very low.


[Electron] Using @azure/app-configuration in electron for feature flags throws error

Package Name: @azure/app-configuration
Package Version: "latest"
Operating system: MacOS BigSur version 11.6
nodejs
v16.3.0:
browser
Google Chrome 96.0.4664.93
typescript
"~4.4.0":
electron
"16.0.0"
Describe the bug
I am trying to get the feature flags from app config using AppConfigurationClient and a connection string. When running the web application, everything seems to work as expected, but when building the web app and serving it within an electron context I receive the following error when trying to get listConfigurationSettings:
Error: ProxyPolicy is not supported in browser environment
To Reproduce

Create a web application (Angular in my case).
Create a service which fetches the listConfigurationSettings from AppConfigurationClient when initialising the app.
Build the web application.
Serve the web build using electron.

@CatalinMates Apologies for the delay in response here, we missed this in our triage. @HarshaNalluru will take look at this by next week

Hi @CatalinMates,
I've tried "listing" in a sample angular app, seems to work fine for me.

I've created a sample angular app with the code to do the listing and it seems to work fine.
https://github.com/HarshaNalluru/angular-app-issue-19267
Please give that a try.
Or Let me know how your setup is different.
Or Provide us a simple sample repro.
Or Let me know the steps to recreate your issue.

Thanks for the reply and for the effort @HarshaNalluru!
The problem that I've encountered, is not when using the angular app. (works fine also for me for angular app). The problem occurred when I've tried to use the build of the angular app within electron context.
So, building the angular app, and serving the build using electron, to have a native (macOS/Windows) App

@CatalinMates Can you provide a repo where you have this setup that we can use to replicate the issue?

Thanks, @CatalinMates, haven't used that before. Will try it out and let you know if I can repro.
As Ramya asked, it would be better/faster if you provide the example.

As you haven't provided the exact steps to repro your issue, went ahead with a quick-start template for the angular app in the context of electron.
Followed the quick-start template and added the previous listing-settings snippet to the sample and was able to list the settings properly without much of a hassle.
Look at the screenshot below.

To try the sample app

Clone the repo https://github.com/HarshaNalluru/electron-angular-issue-19267
Update the connection string in electron-angular-quick-start\workspaces\electron-app\main\services\multiples-service.ts file
Follow the commands below

# Then go into the repository
cd electron-angular-quick-start

# After that, install dependencies
npm install

# And finally run the app (dev mode)
npm start

This is just a quick sample and the readme might have unnecessary information from the original repo.
If you have trouble following this, let me know if you want more info.


Move pytket requirement to extra

Pytket is not needed when using lambeq as a parser.

For this one to make more sense, we need first some to decouple Tket from our diagram manipulation and make Tket only relevant to TketModel, as it should be. This is already work in progress internally, and it will be probably included in Release 0.5.0.

This would be now closed (see above comment).


Camera Escura Moto C

The Camera Goes Dark on Moto C.
When comparing the operating system camera quality with the floating camera package quality, you see the poor quality, especially in dark places, meaning the camera gets a lot worse than the "native" quality.

The Camera Goes Dark on Moto C.
When comparing the operating system camera quality with the floating camera package quality, you see the poor quality, especially in dark places, meaning the camera gets a lot worse than the "native" quality.

Hi @VictorsAlves
if you're still experiencing this problem with latest stable, please create a new issue and provide the information required in the template.
Thank you


Testing

What this change ? (comparing to #89)

it's me not knowing what I am doing :) Sorry about that.
Was meant to be an isolated merge in my fork. Closing it here.


[MoF] Replay flow breaks with patch enabled

By running the game with thcrap enabled (tested using only the EN language pack), starting a replay of a stage makes it end at that stage instead of automatically continuing into the next ones. Tried without thcrap, vpatch enabled and the issue does not present itself.
Non-steam version, latest thcrap release (2021-10-24) and 2020-04-27 tested as well, no changes.

Duplicate of https://github.com/thpatch/thcrap-tsa/issues/46 (not to be rude, someone simply reported the issue before you)


improve routing

Since our app is made with react our app should be a single page application and i can see that whenever i go to another page the page refreshes
https://github.com/user-attachments/assets/1e8daf6f-8231-4285-800b-57c0529fe0cc
PLease assign me i'll try to fix it

@STXRSHIVA it's because of React router components, furthermore if you able to fix it do it your side and raise your PR.

@STXRSHIVA how its gives any output without any source, run inside frontend folder not inside local repository!

thanks got it

resolved!


Fix GPS logging + CSV export is broke (not sure if one broke the other...)

GPS isn't being logged, fixed in branch notifications
Now noticed CSV export is a bit off, looks like it's getting a return carriage. Will look into it.
owlogs_2018-05-27_14_55.csv.txt

Is this issue related to why I can't find any of my ride logs now? They are
listed in the app but I can't find the files anywhere on my device. Also
when I tap on a ride in the app the app spins its wheels for a few minutes
and then returns to the logged ride list without doing anything.
On Wed, May 30, 2018, 10:36 AM Kevin Watkins<EMAIL_ADDRESS>wrote:

GPS isn't being logged, fixed in branch notifications
Now noticed CSV export is a bit off, looks like it's getting a return
carriage. Will look into it.
owlogs_2018-05-27_14_55.csv.txt
https://github.com/ponewheel/android-ponewheel/files/2054592/owlogs_2018-05-27_14_55.csv.txt
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ponewheel/android-ponewheel/issues/69, or mute the
thread
https://github.com/notifications/unsubscribe-auth/APHfOc8jRQ9Q7bHK0ogaDK0_iHq-xv_Aks5t3ryCgaJpZM4UThwB
.

@muellergit Hit the dots in the upper right (next to scan), you'll see Logged Rides in there. You can export any ride and share it.

Right, you just export the ride and share it - it's not file based anymore,
but stored/exported from a local database.
Not being able to open a ride, not sure, it may be related. If you have the
error logs that would help. And/or wait until this fix comes out and give
it a try...
-- Kevin
On Wed, May 30, 2018 at 10:29 AM Erik Babel<EMAIL_ADDRESS>wrote:

@muellergit https://github.com/muellergit Hit the dots in the upper
right (next to scan), you'll see Logged Rides in there. You can export any
ride and share it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ponewheel/android-ponewheel/issues/69#issuecomment-393249575,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0LrbCrKyClUjeGeDhp97gV9wh_YLVPks5t3tb9gaJpZM4UThwB
.

Where can I find the error logs? I can't swipe right from the logged rides
screen where the "error" is occurring. Not sure if it is a error now
though, see below.
I tried a few more tests with the app... The app seems to be returning with
"No chart data" because the app is still working on displaying the charts
for several minutes and then my phone screen locks and the app stops its
processing. My phone is also low on internal storage currently, only has
500MB available, so not sure if that is contributing to the time that the
app takes to process the log data into the charts.
If the app usually takes multiple minutes to produce the charts, maybe the
export file option could be made available before the app starts to do that
processing or ideally while it is doing that? I have verified that if I
manually lock my screen to interrupt the app's chart processing that I can
then go back and select the "export file" option immediately.

Here is the chart I came up with from monitoring voltage when doing full
range testing. This works pretty well, but doesn't work while the batteries
on under load because the voltage sags. For the stock battery the range
estimates are all half of this chart.
{Unloaded Volts} ~ {Range remaining} = {Actual charge remaining} {Estimated
Trip Distance}
54V ~ 15 miles = 100% 1
53V ~ 12 miles = 80% 3
52V ~ 9 miles = 60% 6
51V ~ 6 miles = 40% 9
50V ~ 4 miles = 25% 11
49V ~ 3 miles = 20% 12
48V ~ 2 mile = 12% 13
47V ~ 1 mile = 6% 14
46V ~ 0.5 mile = 3% 15
42V = EMPTY = 0% 15.5
These are the miles of range expected for each volt used, across the
discharge curve:
54V to 50V = 3 mpV miles per volt
50V to 48V = 1 mpV
48V to 46V = 0.5 mpV
46V to 42V = 0.5 mile
On Sat, Jul 14, 2018 at 12:40 PM Kevin Watkins<EMAIL_ADDRESS>wrote:

@muellergit https://github.com/muellergit
The %/State of Charge comes directly off the OW (0-100). I assume it keeps
an internal voltage chart, that gets out of line occasionally and needing a
reset by draining the battery and nosediving on hillway ave.
Thoughts on how we can extend the model you have to any battery source?
From what I can tell on https://en.wikipedia.org/wiki/State_of_charge
this would be an "offline" technique reading the battery current comparing
it over time w/ a hash/lookup table. The table would be the model, reset
manually or when the board is 100%. Something like that. We could add
another "estimated/smart/extended battery %" metric having an option to
making that the primary source of truth for battery % off the board.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ponewheel/android-ponewheel/issues/76#issuecomment-405038568,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APHfOcdu6k8haHsE1PJpwbJNWSowkZ2Iks5uGi0NgaJpZM4VPpV_
.

Ok, here are a couple more thoughts on this.
How about a setting where you can enter your total Watt hours of batteries
and the app uses that in its range calculation? It would have the stock
battery Wh as a default but you could change it to include any add on or
CnR batteries.
The voltage/range chart I made is directly proportional to voltage/charge
of course. And those discharge curves are available for the cells. You can
see my chart is a rough approximation of the curve and corner where the LFP
pack starts to drop off quickly.
Using the actual curve in the app calculation would be much better than my
3 region approximation, and the voltage could be a moving median average
over some seconds to get a more steady voltage level for the look up. Going
further, the actual curves could be included for different temperature
regions. And range could also be adjusted based on the current ride and how
far off the expected look up value for range is versus actual odometer.
On Jul 14, 2018 12:50 PM, "Mike Mueller"<EMAIL_ADDRESS>wrote:
Here is the chart I came up with from monitoring voltage when doing full
range testing. This works pretty well, but doesn't work while the batteries
on under load because the voltage sags. For the stock battery the range
estimates are all half of this chart.
{Unloaded Volts} ~ {Range remaining} = {Actual charge remaining} {Estimated
Trip Distance}
54V ~ 15 miles = 100% 1
53V ~ 12 miles = 80% 3
52V ~ 9 miles = 60% 6
51V ~ 6 miles = 40% 9
50V ~ 4 miles = 25% 11
49V ~ 3 miles = 20% 12
48V ~ 2 mile = 12% 13
47V ~ 1 mile = 6% 14
46V ~ 0.5 mile = 3% 15
42V = EMPTY = 0% 15.5
These are the miles of range expected for each volt used, across the
discharge curve:
54V to 50V = 3 mpV miles per volt
50V to 48V = 1 mpV
48V to 46V = 0.5 mpV
46V to 42V = 0.5 mile
On Sat, Jul 14, 2018 at 12:40 PM Kevin Watkins<EMAIL_ADDRESS>wrote:

@muellergit https://github.com/muellergit
The %/State of Charge comes directly off the OW (0-100). I assume it keeps
an internal voltage chart, that gets out of line occasionally and needing a
reset by draining the battery and nosediving on hillway ave.
Thoughts on how we can extend the model you have to any battery source?
From what I can tell on https://en.wikipedia.org/wiki/State_of_charge
this would be an "offline" technique reading the battery current comparing
it over time w/ a hash/lookup table. The table would be the model, reset
manually or when the board is 100%. Something like that. We could add
another "estimated/smart/extended battery %" metric having an option to
making that the primary source of truth for battery % off the board.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ponewheel/android-ponewheel/issues/76#issuecomment-405038568,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APHfOcdu6k8haHsE1PJpwbJNWSowkZ2Iks5uGi0NgaJpZM4VPpV_
.

@muellergit - this sounds sweet, a setting that you can enter total watt hours and/or presets, like for the two-x. Your chart seems like a good first cut, and it's heaps better then what we have now - and gets us an estimated distance trip distance.
How are you on doing a first cut of this? You seem to know it better than any of us. Let us know, I can try to add it as well, but not sure I know enough about this to do it right.


How should I run it? My microbit v2 device has no led light

log:
➜  discovery git:(gh-pages) ✗ cd microbit/05-led-roulette
➜  05-led-roulette git:(gh-pages) ✗ cargo embed --features v2 --target thumbv7em-none-eabihf
    Finished dev [unoptimized + debuginfo] target(s) in 0.31s
      Config default
      Target /Users/jameszow/Documents/RustWorkSpace/discovery/microbit/05-led-roulette/target/thumbv7em-none-eabihf/debug/led-roulette
     Erasing sectors ✔ [00:00:00] [#######################################################################################]  4.00KiB/ 4.00KiB @ 26.19KiB/s (eta 0s )
 Programming pages   ✔ [00:00:00] [#######################################################################################]  4.00KiB/ 4.00KiB @ 11.60KiB/s (eta 0s )
    Finished flashing in 0.419s

I didn't see the effect

By the way, what is the command to enter gdb? I used this command, but it is obviously incorrect
arm-none-eabi-gdb -q -ex "target remote :1337" target/thumbv7em-none-eabihf/debug/led-roulette

did you uncomment the line in Embed.toml like we had to do in 03-setup?
As for gdb, from the discovery/microbit directory, I used gdb-multiarch target/thumbv7em-none-eabihf/debug/led-roulette followed by (gdb) target remote :1337


Added Swedish translation

A complete swedish translation.
Some minor liberties where taken in the translation.
ex:
Instead of asking i the user wants to loose their changes, the text now asks the user if he wants to continue despite the changes not being saved.
It just makes better sense in swedish.

Thanks for the update @Evanion :)


osbuild-worker-config: create an rpm with the config we use in our worker images

This would in principle allow image builder to build its own worker AMIs.

Ideally, this should now "just work", but there appears to be bugs to fix:
{
  "customizations": {
    "packages": [
      "osbuild-composer-worker-config"
    ],
    "payload_repositories": [
      {
        "baseurl": "https://download.copr.fedorainfracloud.org/results/packit/osbuild-osbuild-composer-2838/epel-8-x86_64/",
        "rhsm": false
      }
    ]
  },
  "distribution": "rhel-86",
  "image_name": "ImageBuilderWorker",
  "image_requests": [
    {
      "architecture": "x86_64",
      "image_type": "aws",
      "upload_request": {
        "options": {
          "share_with_accounts": [
            "..."
          ]
        },
        "type": "aws"
      }
    }
  ]
}

Turns out the above bug was caused by me forgetting to include EPEL++ in the list of repositories. We should improve the error reporting, but otherwise all good.

Fixed request:
{
  "customizations": {
    "packages": [
      "osbuild-composer-worker-config"
    ],
    "payload_repositories": [
      {
        "baseurl": "https://download.copr.fedorainfracloud.org/results/packit/osbuild-osbuild-composer-2838/epel-8-x86_64/",
        "rhsm": false
      },
      {
        "baseurl": "https://dl.fedoraproject.org/pub/epel/8/Everything/x86_64/",
        "rhsm": false
      },
      {
        "baseurl": "https://repositories.timber.io/public/vector/rpm/el/8/noarch/",
        "rhsm": false
      },
      {
        "baseurl": "https://repositories.timber.io/public/vector/rpm/el/8/x86_64/",
        "rhsm": false
      }
    ]
  },
  "distribution": "rhel-86",
  "image_name": "ImageBuilderWorker",
  "image_requests": [
    {
      "architecture": "x86_64",
      "image_type": "aws",
      "upload_request": {
        "options": {
          "share_with_accounts": [
            "761215030869"
          ]
        },
        "type": "aws"
      }
    }
  ]
}

(fails on building, but that's likely due to a bug in this PR)


GEORADIUS with STOREDIST support

Expected behavior
georadius GEO  73.9064 18.5453 10 km STOREDIST userResultSet

userResultSet key points to a sortedSet which is sorted by distance.
Actual behavior
Redisson currently only supports the STORE option
georadius GEO  73.9064 18.5453 10 km STORE userResultSet

This creates a sortedSet using the hash value.
Steps to reproduce or test case
Redis version
Redisson version
3.10.4
Redisson configuration

Done