Rebase crash_dumper onto current Godot 4.3 master

This PR rebases the crash_dumper branch onto Godot's current master branch.
Note that I removed the mono re-hook as it seems to no longer be necessary.
I've only tested this on Windows, as that's the only platform I have available.

The merge conflicts appear to be expected as I chose to rebase rather than merging master.

I'm not sure how merging this should be done...
What did you need to do to rebase this work? I'm kind of guessing that it might be just more effective to redo this crash dumper feature on a clean branch from Godot master and just re-add fresh crash dumper library files and redo the hooking into the engine.

I remade the branch here. https://github.com/V-Sekai/godot/tree/vsk-crash-dumper-4.3-beta1

That remade branch looks fine to me based on a quick look. If there is a chance that this feature would finally make it into Godot soon I can probably make some time next week to do some stuff like:

determining if the signal handler overrides hack is still needed with the dotnet runtime
updating the breakpad version to latest commit as the previously extracted code is from 2021
testing that the crash dump generation (and decoding) still works

Here's my understanding.

Godot 4.3 is in beta and in feature freeze
I don't know when 4.4 merges, it could be 6 months 4.2 took or it could be the year that 4.3 took.

Since I want to have crash dumps today. I'll probably revive https://github.com/V-Sekai/godot-sentry-native and use sentry.io (a commercial service)

I don't mind redoing the work, or simply updating the breakpad integration - it looks relatively simple to do. Primarily, I wanted to update your PR into the Godot engine itself, instead of creating a new PR. It seems that redoing the branch would require me to do so. I'm a new contributor, so it's hard for me to gauge which is the best solution here.

A couple more notes:

testing that the crash dump generation (and decoding) still works

I tested this on windows and it works. I built Godot with debugging symbols and used OS.crash to force a crash, which generated a dump file in %appdata%. I was able to successfully extract a stack trace from the minidump using Visual Studio.

determining if the signal handler overrides hack is still needed with the dotnet runtime

The above was done with the dotnet module enabled, and I removed your re-init code in this branch, so I think it is no longer needed.

updating the breakpad version to latest commit as the previously extracted code is from 2021

I will try to get this done today.

If there is a chance that this feature would finally make it into Godot soon

To be honest, I have no idea what the chances of this are. I also find it quite demoralizing that critical features necessary for shipping a game like this are missing from the core engine. But I figured if I could add weight to and help out with the issue, perhaps there's a better chance.

I think what might work is that once you have your branch ready in your fork, I'll pull that to my local git repo and then force reset this repo's crash_dumper branch to match your branch, and then push that to github. I have a feeling that that would probably do the correct thing.

I've now updated the branch in my fork and tested that it's still functional at least on Windows: https://github.com/Chaosed0/godot-crash-dumper/tree/crash_dumper
Breakpad has been updated from Google's main branch. I removed all the test and HTTP upload files I could find. Here is a list of the new files, in case there are any that I missed that ought to still be removed:
 create mode 100644 thirdparty/breakpad/src/client/linux/data/linux-gate-amd.sym
 create mode 100644 thirdparty/breakpad/src/client/linux/data/linux-gate-intel.sym
 create mode 100644 thirdparty/breakpad/src/client/linux/minidump_writer/pe_file.cc
 create mode 100644 thirdparty/breakpad/src/client/linux/minidump_writer/pe_file.h
 create mode 100644 thirdparty/breakpad/src/client/linux/minidump_writer/pe_structs.h
 create mode 100644 thirdparty/breakpad/src/client/mac/UnitTests-Info.plist
 create mode 100644 thirdparty/breakpad/src/client/mac/handler/minidump_test.xcodeproj/project.pbxproj
 create mode 100644 thirdparty/breakpad/src/client/mac/handler/minidump_tests32-Info.plist
 create mode 100644 thirdparty/breakpad/src/client/mac/handler/minidump_tests64-Info.plist
 create mode 100644 thirdparty/breakpad/src/client/mac/handler/obj-cTestCases-Info.plist
 create mode 100644 thirdparty/breakpad/src/client/solaris/handler/exception_handler_test.cc
 create mode 100644 thirdparty/breakpad/src/common/dwarf/dwarf2reader_test_common.h
 create mode 100644 thirdparty/breakpad/src/common/dwarf/elf_reader.cc
 create mode 100644 thirdparty/breakpad/src/common/dwarf/elf_reader.h
 create mode 100644 thirdparty/breakpad/src/common/linux/dump_symbols.cc
 create mode 100644 thirdparty/breakpad/src/common/linux/dump_symbols.h
 create mode 100644 thirdparty/breakpad/src/common/linux/scoped_pipe.cc
 create mode 100644 thirdparty/breakpad/src/common/linux/scoped_pipe.h
 create mode 100644 thirdparty/breakpad/src/common/linux/scoped_tmpfile.cc
 create mode 100644 thirdparty/breakpad/src/common/linux/scoped_tmpfile.h
 create mode 100644 thirdparty/breakpad/src/common/linux/symbol_collector_client.cc
 create mode 100644 thirdparty/breakpad/src/common/linux/symbol_collector_client.h
 create mode 100644 thirdparty/breakpad/src/common/linux/synth_elf.cc
 create mode 100644 thirdparty/breakpad/src/common/linux/synth_elf.h
 create mode 100644 thirdparty/breakpad/src/common/mac/SymbolCollectorClient.h
 create mode 100644 thirdparty/breakpad/src/common/mac/SymbolCollectorClient.m
 create mode 100644 thirdparty/breakpad/src/common/mac/dump_syms.cc
 create mode 100644 thirdparty/breakpad/src/common/mac/dump_syms.h
 create mode 100644 thirdparty/breakpad/src/common/safe_math.h
 create mode 100644 thirdparty/breakpad/src/common/solaris/dump_symbols.cc
 create mode 100644 thirdparty/breakpad/src/common/solaris/dump_symbols.h
 create mode 100644 thirdparty/breakpad/src/common/test_assembler.cc
 create mode 100644 thirdparty/breakpad/src/common/test_assembler.h
 create mode 100644 thirdparty/breakpad/src/common/windows/symbol_collector_client.cc
 create mode 100644 thirdparty/breakpad/src/common/windows/symbol_collector_client.h
 create mode 100644 thirdparty/breakpad/src/google_breakpad/common/minidump_cpu_riscv.h

I have a feeling that at least the following are data files that should not be included:
 create mode 100644 thirdparty/breakpad/src/client/linux/data/linux-gate-amd.sym
 create mode 100644 thirdparty/breakpad/src/client/linux/data/linux-gate-intel.sym

Also these might be data generation only files that may not be needed for a stripped down client library compilation:
 create mode 100644 thirdparty/breakpad/src/client/mac/handler/minidump_test.xcodeproj/project.pbxproj
 create mode 100644 thirdparty/breakpad/src/client/mac/handler/minidump_tests32-Info.plist
 create mode 100644 thirdparty/breakpad/src/client/mac/handler/minidump_tests64-Info.plist
 create mode 100644 thirdparty/breakpad/src/client/mac/handler/obj-cTestCases-Info.plist
 create mode 100644 thirdparty/breakpad/src/client/solaris/handler/exception_handler_test.cc
create mode 100644 thirdparty/breakpad/src/common/dwarf/dwarf2reader_test_common.h
 create mode 100644 thirdparty/breakpad/src/common/dwarf/elf_reader.cc
 create mode 100644 thirdparty/breakpad/src/common/dwarf/elf_reader.h
 create mode 100644 thirdparty/breakpad/src/common/linux/dump_symbols.cc
 create mode 100644 thirdparty/breakpad/src/common/linux/dump_symbols.h
 create mode 100644 thirdparty/breakpad/src/common/mac/dump_syms.cc
 create mode 100644 thirdparty/breakpad/src/common/mac/dump_syms.h
 create mode 100644 thirdparty/breakpad/src/common/safe_math.h
 create mode 100644 thirdparty/breakpad/src/common/solaris/dump_symbols.cc
 create mode 100644 thirdparty/breakpad/src/common/solaris/dump_symbols.h
 create mode 100644 thirdparty/breakpad/src/common/test_assembler.cc
 create mode 100644 thirdparty/breakpad/src/common/test_assembler.h
 create mode 100644 thirdparty/breakpad/src/common/windows/symbol_collector_client.cc
 create mode 100644 thirdparty/breakpad/src/common/windows/symbol_collector_client.h

Some of those might be necessary, but I think at least some of those source files are purely for the dumping side of things or just tests, meaning that they are unnecessary to include with the godot engine. Though to be sure each platform's files should be inspected to see if some other headers include those files to be removed to do a sanity check on not removing important files. I should be able to also pretty easily test on Linux to make sure there aren't missing files that prevent compilation.

Removed those files and re-tested, and things appear to still work.

I found a few problems compiling on Linux, but I fixed those. The PR to Godot should now be updated.


proc-macro2-diagnostics update

https://github.com/coral-xyz/anchor/blob/862575a6496e2d92e9e95d226bc44d7cae1594e1/lang/syn/src/codegen/accounts/constraints.rs#L2
Is it possible to remove this dependency? The underlying library hasn't been updated in years and it's causing a dependency conflict with actix-web because it uses a pinned version of version-check. I submitted an issue to the library author in the hopes that it'll get updated but I'm trying this avenue as well.

Ok, I found the root usage of this library and it's linked to notifying users about deprecated constraints. https://github.com/coral-xyz/anchor/pull/429/files
It's definitely possible we could get rid of this crate if it was possible to replace the existing code with something else. That said it doesn't seem like a super high priority, though happy to look at PRs.


msg.sender differs from test to system call

I am getting odd behavior in my test suite -- my msg.sender value changes when I call a system, which breaks my test. This wasn't happening before I updated MUD to v31.1 -- any ideas why this is occurring?
testSpawn.t.sol:
    console.log("msg sender in spawn test:", msg.sender); // -> 0x1804c8
    spawnSystem.executeTyped("Jamaican me crazy", Coord(1, 1));

execute(bytes memory arguments) within SpawnSystem.sol:
    (string memory name, Coord memory location) = abi.decode(arguments, (string, Coord));
    console.log("msg sender in spawn system:", msg.sender); // -> 0x416C4

Are you using foundry's prank somewhere in testSpawn.t.sol? If not it's expected that the msg.sender in execute would be your test contract.

setting up a deployer prank has fixed the issue! Is this correct: the prank doesn't affect the msg.sender of the test function, just the msg.sender of all the functions it calls?

That's correct - prank sets it only for the next function call, startPrank sets it for all following function calls until stopPrank is called


Quiz questions in /15-intro-linear-algebra.ipynb

I think there are corrections to be made in the 4th and 5th questions of the second quiz:

They say 4 matrices, but there are 3
there is a bracket missing to close the second matrix
If you paste both in a cell, they give a scalar, so for both the answer would be (1), since "Python would do what we mean".

Also, I don't know if this was on purpose, but many questions of the second quiz are repeated in the final quiz.

thanks.


Checklist for v5.11 Packaged Release - name to be determined

It has been 8 months since the last packaged release of v5.0 -
https://github.com/kelaberetiv/TagUI/releases/tag/v5.0.0
There is typically an intended gap between implementing new features / bug fixes and putting those stuffs in a new packaged release which users will use by default for installation. The gap will allow time for users to try out new features and giving feedback on what might be broken or improved on, before putting those stuff into packaged installations for use in production.
There are some bug fixes, some new features, some improvements in readme. But nothing specific around a theme. This release is meant to round up all those changes. Siow Yi Sheng is joining AI Singapore and will be maintaining this project going forward. There is a new version of TagUI next year being explored, that is based on NodeJS. That will remove dependencies such as PhantomJS, CasperJS and dependencies of those projects.
Also, along with exploring the move to NodeJS, features that will be explored include an IDE (studio app for developing TagUI flows / scripts), orchestrator app (for scheduling automations through time-based or event-based etc), potentially reporting app (for collecting reports of automations done). That release probably would be TagUI v7 or v8.
Prior to that release, there are some changes to be made that are backward in-compatible, to refine and improve user experience. An example would be making Chrome visible mode as the default mode, and retiring PhantomJS mode to encourage use of Chrome headless mode, as most websites are designed and tested to work on Chrome not PhantomJS. And perhaps settling on a file extension such as .tag to standardise file naming. These changes would be in v6.
Prior to v6, this v5.11 aims to round up all the changes since v5.0 packaged release.

Checklist for v5.11 packaged release, copying @siowyisheng for info and to add-on -

[ ] validate current codebase's positive test signature matches
[ ] draft updated readme and rpa workshop of new commits
[ ] final check on readme, any corrections or improvements
[ ] unzip for windows on windows, put cutting edge version, zip
[ ] unzip for macos on macos, put cutting edge version, zip
[ ] unzip for linux on linux, put cutting edge version, zip
[ ] be aware of unneeded hidden files while zipping (eg .git)
[ ] consider changing host to TagUI repo's new release
[ ] and using the new URLs for packaged installations
[ ] check architecture diagram if any update is needed
[ ] commit changes and publish new release with summary
[ ] check through links in readme for incorrect mapping
[ ] test windows zip on positive test and general tests
[ ] test macos zip on positive test and general tests
[ ] test linux zip on positive test and general tests

Created PR above to make general readme improvements before v5.11 release.
After looking through commits, many changes are updated already in readme and are either new readme notes, bug-fixes or minor improvements. Below are the 3 new features that are needed to be added for v5.11 readme. Have made a local edit of readme for these features.
#466 - end_processes script to kill TagUI processes
#461 - support defining regions for OCR and snapshot
#559 - clipboard() helper function to get or put text

I don't have a name for this release yet, for now tentatively Pre-v6 Release because it's meant as a 'snapshot' of the version before the breaking changes are introduced from v6 onwards.
I expect in v7 and v8 there might be backward compatibility breaking changes as new technical roadblocks are discovered. And we should not be held back from doing so, to move towards the future stable state. This prev-v6 and v6 release will let users continue using their existing scripts until they are comfortable to move to v7 and v8.

All done, I'll do a summary of the changes in release notes over the weekend. I'll remove that new release and publish again with the files, otherwise the 1 commit after the release was done shows the commit done for the release happening after the release, which is misleading. First time trying to host the zips here, catch-22, whichever done first will have a momentary gap.
https://github.com/kelaberetiv/TagUI/releases/tag/v5.11.0

(no need re-attach the zips.
I publish with new tag v5.11.1, removed old tag v5.11.0, then re-publish as v5.11.0)

Ok done! - https://github.com/kelaberetiv/TagUI/releases/tag/v5.11.0
I put together the list of changes, write a short 1-liner for them, and add some general notes.

Copying @siowyisheng -

Made some updates the v5.11 release notes with some forward looking statements -

TagUI is a command-line tool for digital process automation (RPA)
New Features

#559 - clipboard() helper function to read & write
#466 / #417 - shell script to kill TagUI processes
#465 - support escape chars in live mode, eg '
#462 - improve snap step Chrome snapshots
#461 - support regions for OCR and snapshot
#442 - support non-terminal usage of TagUI

Bug Fixes

#648 - fix Chrome not closing for macOS & Linux
#597 - fix PHP warning for newer PHP versions
#592 - fix select step, change to match exactly
#553 - fix frame not working issue with Chrome
#549 - fix using variables dynamically in live mode
#497 - fix timeout hanging if no visual automation

General

#606 - graceful handling of invalid Python code
#589 - update readme to use Corretto OpenJDK
#490 - provide prettified codebase for readability
#459 - readme add section on TagUI for Python
#443 - timeout step to update SikuliX timeout
#423 - enable check step to work in for loop

This release rounds up all enhancements and bug fixes since the last packaged release 8 months ago.
New features worth noting would be the clipboard() helper function to read and write to the clipboard, the end_processes and end_processes.cmd scripts to let users kill all TagUI and integrations processes, and supporting (x1,y1)-(x2,y2) regions as identifiers for read and snap steps.
Siow Yi Sheng has joined AI Singapore and will be taking over future development of TagUI. Coming from a deep business background, he pivoted and made great leaps in tech, both in frontend and backend. The knowledge transfer and handover has begun, and this release is the last release which I'll be driving.
There are going to be very exciting developments next year. Including a TagUI IDE to make developing RPA workflows accessible to everyone, an Orchestrator for scheduling and managing workflows, and a Reporting Dashboard for a one-stop view of the executed workflows.

In the interim, v6 is being worked on, which will introduce changes that improve TagUI user experience. For example, using Chrome visible browser by default instead of PhantomJS invisible browser. The .raw .js .log files will not be generated by default as they are irrelevant to most users most of the time. Also, .tag will become the standard file extension for TagUI flow files. Because these improvements may require changes to how users currently use and setup TagUI, this next release will be bumped up to v6.
Other interesting features that Yi Sheng is working on include having the option to generate a Windows batch file or macOS script automatically so that users can double-click on a desktop icon to run the automation, having an option to launch TagUI in live mode directly, adding SHA hash to report option to prevent malicious tampering of auditing results, and visually looking for specified text on the screen. A POC on migrating TagUI from using PhantomJS to Node.js as the execution engine is also underway.


aarch64 platform mimx8mm/p update and new mimx8mn platform

This patchset includes the following updates:

Add new arm64 platform imx8mn platform support.
Clean up imx8mm and imx8mp Cortex-A platform support, each platform use two board configuration, one for non-SMP and the other for SMP kernel, both of them can boot from uboot command or Jailhouse inmate cell.
Enabled physical UART4 for all board configurations.
Update pinctrl_imx driver to be aarch64 compatible.
Enabled pinctrl for all these three platforms and it works with UART.

This PR depends on some hal_nxp PRs, they are in review progress:
https://github.com/zephyrproject-rtos/hal_nxp/pull/186

Nice work. Just a comment about commit messages: please add one even if it a short one.

Thanks your comments, will update it.

Nice work. Just a comment about commit messages: please add one even if it a short one.

Done, thanks.

Updated board document, please review again, thanks.

Dear maintainers, update this PR with the following updates, thanks for your review:
Unify SoC name from imx8m/n/p to mimx8m/n/p with the name in hal_nxp.
Add me to be codeowner of platform imx8mm/p/n ARM64 platforms.

As hal_nxp patches have been merged, so update west.yml to use actual commit ID.

Dear maintainers, rebased, no dependency now, please review and merge it, thanks.


update the way to parse month-end cron schedule

Signed-off-by: Liucw<EMAIL_ADDRESS>
What type of PR is this?
/kind feature

What this PR does / why we need it:
update the way to parse month-end cron schedule
Which issue(s) this PR fixes:

Fixes https://github.com/kubeclipper-labs/kubeclipper/issues/177
Special notes for reviewers:

Does this PR introduced a user-facing change?

None

Additional documentation, usage docs, etc.:

@x893675

Codecov Report

Merging #178 (2800fd8) into master (79f3c5c) will increase coverage by 0.68%.
The diff coverage is 35.87%.

@@            Coverage Diff             @@
##           master     #178      +/-   ##
==========================================
+ Coverage   12.63%   13.32%   +0.68%
==========================================
  Files         104      104
  Lines       15987    15565     -422
==========================================
+ Hits         2020     2074      +54
+ Misses      13718    13240     -478
- Partials      249      251       +2

Impacted Files
Coverage Δ

pkg/cli/deploy/deploy.go
17.04% <0.00%> (+0.47%)
:arrow_up:

pkg/cli/join/join.go
0.00% <0.00%> (ø)

pkg/cli/registry/registry.go
0.00% <0.00%> (ø)

pkg/cli/resource/resource.go
0.76% <0.00%> (+0.01%)
:arrow_up:

pkg/cli/utils/download.go
0.00% <0.00%> (ø)

pkg/cli/utils/file.go
0.00% <ø> (ø)

pkg/utils/sshutils/scp.go
0.00% <0.00%> (ø)

pkg/utils/sshutils/ssh.go
0.00% <ø> (ø)

pkg/utils/sshutils/sshcmd.go
0.00% <0.00%> (ø)

pkg/utils/sshutils/ssh_v2.go
21.23% <47.36%> (+14.44%)
:arrow_up:

... and 6 more

/retitle update cron schedule and unit test

/retitle update cron schedule parse and unit test

/lgtm
/approve

/cherrypick release-1.1


Sometimes eats a lot of RAM, makes sites laggy. No more updates?

Hi MidnightLizard community,
First of all thank you for this amazing repository, I really LOVE IT
Does anyone know why sometimes consume so much RAM and makes sites unresponsive? I do not know how to reproduce it , it just happens. If I have a lot of tabs opened or not. It happens on LibreWolf browser. Now I will test it on Brave browser.
This repository/extension is still maintained by someone or a branch of it? I love it and is more capable than other dark mode extensions and is sad to see that it has no more updates in a long time. Somebody know a similar open source extension?

Seems this extension has been abandoned. Real bummer


Move Language Server to New Parser

Description:
Move Language Server to New Parser. For the initial phase, it will simply enable SyntaxTree based compilation.

Closing since the task has been completed


Markdown newline behaviour (non-uniform)

Summary
Unfortunately, the newline behavior is not uniformly solved in many Markdown tools. Some require (correctly) the double spaces at the end of a line to insert a newline. Others do not require this. And a few apps even trim the lines (before saving) and delete these double spaces.
Obviously this double space trick is a holdover from earlier times where plain text documents often were wrapped at 78 characters with artificial linefeeds. Nowadays, all editors are capable of automatic line wrapping (based on window width), so this double space trick no longer brings any real advantages in Markdown. In fact this is a point that rather confuses many non-expert users (because the behaviour is unexpected).
For this reason I strongly recommend to include an optional configuration switch whether normal newlines (without double space) should be interpreted as a line break or not. This would improve the handling of external Markdown files, which are often displayed incorrectly.
Especially since there are some apps around (e.g. for mobile devices) that do not require / support double space and sometimes even remove them when saving.
📝 Reproduction steps
first line

second line

✔ Expected result
first line
second line

❌ Actual result
first line second line

This is more of an enhancement.
how i'm reading your ask is to support HTML elements like line break (
)

No, this enhancement is pretty minimalistic ;-)
It's just about introducing a configurable option that toggles whether all lines that end with normal linebreaks but without trailing double spaces should be rendered as newline or not. Currently they are not, but if the "new" option is set they will.
The name of the option could be:
"Ignore double spaces at the end of a line and use every linebreak as a newline." -> ON / OFF
PS: The  in my example is only to clarify that there are no two spaces there. :-)

Where is this deemed standard behavior?

To illustrate the problem, I made a screenshot with several standard editors side-by-side. In the Markdown standard it is defined that (1) you have to insert a blank line to get a double line break (a paragraph) and that (2) a line must end on a double space to get a single line break (a newline).
However, most Markdown editors do not follow this confusing second rule. For this reason, there are many documents around the world that do not contain a terminating double-space for a single line break. All these documents are displayed differently by PowerToys Markdown Preview in comparision to the Markdown Editor previews.
You can easily try this yourself with the various online editors for Markdown, such as StackEdit or Dillinger.
https://stackedit.io/
https://dillinger.io/
Below is a screenshot showing an example with 3 standard editors to illustrate the problem. You can see that the PowerToys Markdown Preview (bottom right) "glues" the first and second line together. This is standard compliant, but unexpected for most users, because hardly nobody (in the common user group ;-) knows and applies this double space rule anymore.
I therefore suggest to add a switch to the PowerToys plugin to toggle this behavior so that PowerToys can display the MarkDown documents in both ways (standard compliant and new way).

Resolved with the release of v0.41.


Changes publicPath: '../fonts' to 'https://local.dev/{pageName}'/fonts/[filename].[ext]'

I am new to webpack and I can seem to find what I am doing wrong
Here What I Am Using For CSS:
{
    test: /\.scss$/,
    use: [
        // creates style nodes from JS strings
        {
            loader: 'style-loader',
            options: {
                sourceMap: true,
            },
        },
        {
            loader: 'css-loader',
            options: {
                sourceMap: true,
            },
        }, // translates CSS into CommonJS
        {
            loader: 'postcss-loader',
            options: {
                sourceMap: true,
            },
        },
        {
            loader: 'resolve-url-loader',
            options: {
                sourceMap: true,
            },
        },
        {
            loader: 'sass-loader',
            options: {
                sourceMap: true,
            },
        }, // compiles Sass to CSS
    ],
},

And Here Is My Fonts :
{
    test: /.(ttf|otf|eot|svg|woff(2)?)(\?[a-z0-9]+)?$/,
    use: [
        {
            loader: 'file-loader',
            options: {
                name: '[name].[ext]',
                outputPath: '../fonts',
                publicPath: baseURL + 'fonts',
            },
        },
    ],
},

And My baseURL const baseURL = 'wp-content/plugins/pratirupm-plugin/inc/assets/dist/';
What Ever I Put in my publicPath: 'xyz' the compiled blob file that style-loader adds to the dom appends the page url + baseURL
so for example when I click on blog page the asset url changes to:
https://local.dev/blog/wp-content/plugins/pratirupm-plugin/inc/assets/dist/fonts/fa-brands-400.woff
I dont know why its acting like that as I said i am new to webpack and stuff but when I compile the js and css in production with extract-text-plugin and if my publicPath:'../fonts' it stays as '../fonts' in the css file as well..
Thanks For Your Time

I encourage you to ask your question on StackOverflow instead. We try to use the issue tracker for bug reports and feature requests, as well as some discussions, but this appears to be a very localized question.
I’m closing for these reasons.


chore(dashboard): pretty import path

Overview
Adds support for pretty import paths so we can do import { Widget } from '~/types'
Legal
This project is available under the Apache 2.0 License.

@jmbuss works in jetbrains


torch binary not found in PATH

When I try to generate a Dataset using the other option I receive the following error:
Default value for torch_root "<PATHS>" invalid:
torch binary not found in PATH

However my path does include torch:
echo $PATH
/home/lucas/torch/install/bin:/usr/local/MATLA.......

echo $TORCH_ROOT
/home/lucas/torch

Any idea what could be causing this issue?

Just a guess - but you could try starting up the digits server with the --config option.   It asks for the path to torch if you do that, rather than using $PATH and other environment variables.

Thanks was definitely helpful in speeding up debugging! It turns out that I needed to point to the ~/torch/install folder (not ~/torch/install/bin which was in my PATH).


check collation oid is valid in strpos and replace for non deterministic collations

Description
Issues Resolved
[BABEL-5150]
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

6 of 7 (85.71%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 73.663%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contrib/babelfishpg_tsql/src/collation.c
6
7
85.71%

Totals

Change from base Build<PHONE_NUMBER>9:
0.002%

Covered Lines:
44144

Relevant Lines:
59927

💛  - Coveralls


MercuryTrade Stops Functioning Between Launches

As the title suggests if I leave MercuryTrade open between launches it will often not close or not function at all the next time I open POE

I actually have this same issue as well, specifically it seems to stop working properly if i turn off my main monitor, when i turn it back on mercury trade's UI comes up slightly off position and notifications just don't work whatsoever, a quick restart fixes it but it is a small inconvenience.


How to build with one IDE, but use runIde with another? (eg for com.intellij.java)

I'm working on a plugin that requires com.intellij.java for a build step, where it needs it for some JPS related code in a submodule
So we've added it to bundledPlugins.
This works great when using IC, but when using RubyMine I get an error because it's not bundled.
eg
./gradlew runIde -PplatformType=RM -PplatformVersion=2024.1.4
* What went wrong:
Could not determine the dependencies of task ':jps-builder:compileJava'.
> Could not resolve all dependencies for configuration ':jps-builder:compileClasspath'.
   > Could not find bundled plugin with ID: 'com.intellij.java'. See https://jb.gg/ij-plugin-dependencies.

It works for other projects which don't have this same requirement.
I would love something similar to runIde, because I think otherwise I would need to pretty much re-invent what runIde does:

Build the project as normal
Copy the zip into the RubyMine/etc sandbox
Run debug, etc.

Not sure if this is a intellij gradle platform question or not, so happy to be moved as needed.

https://plugins.jetbrains.com/docs/intellij/tools-intellij-platform-gradle-plugin-testing-extension.html#intellijPlatformTesting
build.gradle:
intellijPlatformTesting {
    runIde {
        register("runIntelliJCommunity") {
            type = IntelliJPlatformType.IntellijIdeaCommunity
            version = providers.gradleProperty("platformVersion")
            prepareSandboxTask {
                sandboxDirectory = project.layout.buildDirectory.dir("rubymine-sandbox")
            }
        }
        register("runRubyMine") {
            type = IntelliJPlatformType.RubyMine
            version = providers.gradleProperty("platformVersion")
            prepareSandboxTask {
                sandboxDirectory = project.layout.buildDirectory.dir("rubymine-sandbox")
            }
        }
    }
}


Nuxt Js

How can I use this library in nuxt js? It doesn't work for me.

How can I use this library in nuxt js? It doesn't work for me.

@MiracleH please check this

How can I use this library in nuxt js? It doesn't work for me.

Nuxt version
2.15.7
It works for me. you should create new folder for all plugins like this:
plugins/v-google-translate.js
import Vue from "vue";
import vGoogleTranslate from 'v-google-translate';
Vue.use(vGoogleTranslate)

nxut.config.js
plugins: [
    { src: './plugins/v-google-translare.js', ssr: false }
],

How can I change language default en to ja

How can I change language default en to ja


Clarify usage of source for CDEvents

CDEvents include a source field that matches the source in CloudEvents (type: URI-reference). source + id should be globally unique, which means that source should identify the producer of events using a URI-reference.
I'm using Tekton events as an example of the possible options.
In Tekton today the source looks like:
"Ce-Id": "77f78ae7-ff6d-4e39-9d05-b9a0b7850527",
"Ce-Source": "/apis/tekton.dev/v1beta1/namespaces/default/taskruns/curl-run-6gplk",
"Ce-Specversion": "1.0",
"Ce-Subject": "curl-run-6gplk",
"Ce-Time": "2021-01-29T14:47:58.157819Z",
"Ce-Type": "dev.tekton.event.taskrun.unknown.v1",

However this is problematic because the source is different for every subject, which makes filtering events harder.
An alternative could be to use in the source the website of the platform that produces events, e.g.
"Ce-Id": "77f78ae7-ff6d-4e39-9d05-b9a0b7850527",
"Ce-Source": "https://tekton.dev/",
"Ce-Specversion": "1.0",
"Ce-Subject": "/apis/tekton.dev/v1beta1/namespaces/default/taskruns/curl-run-6gplk",
"Ce-Time": "2021-01-29T14:47:58.157819Z",
"Ce-Type": "dev.tekton.event.taskrun.unknown.v1",

That means that all events generated by any instance of Tekton would have the same source though.
I'm not aware of any standard way of identifying an instance of an application via an URI.
We could define something like <org-namespace>/tekton/<instance-descriptor>:
"Ce-Source": "tekton.dev/tekton/dogfooding",

This could identify the dogfooding Tekton instance used by the Tekton community.
Thoughts?

In Eiffel we have an object to describe the source, see the meta.source in Activity Triggered.
I would like to state something like

Source: Describes the sender of the event. By using the source the receiver should have the possibility to pinpoint the instance that sent the event.


Update README.md

// 100% below the smallest breakpoint,
// 50% from the next breakpoint and up,
// and 25% from the next breakpoint and up
<Box w={[ 1, 1/2, 1/4 ]} />
Changed the 'w' to 'width' in the responsive example code above.

Codecov Report

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

@@          Coverage Diff          @@
##           master    #29   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          10     10
  Lines         115    115
=====================================
  Hits          115    115

Continue to review full report at Codecov.

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


Rename or add alias property for "REGISTER_MANIFEST"

Would be nice if the MSI property were more self explanatory like "LOG_TO_EVENTLOG"
When I have to consult the documentation to figure out the purpose of a variable like this it feels like it does not follow "code as documentation" principles well enough.  But all the more so when it is a variable that users of will have absolutely no other context for (won't be looking at the code that uses it when they need to use it) - which is the case for all properties fed into MSIs because it is not easy for non-MSI packager to dissect the package to figure out the purpose and in this case it is just a condition on a custom action.

Related PR #5999

I have no objections to renaming (since the properties were only introduced in the latest preview versions) as long as the documentation issue gets updated as well:
https://github.com/PowerShell/PowerShell-Docs/issues/2007

Great!  I am also thinking that for MSI properties the same principle should be followed in new properties.
Obviously ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL - is an excellent example of contextless self-documenting naming!

REGISTER_MANIFEST is actually more self-explanatory for what this process actually does than LOG_TO_EVENTLOG. The instrumentation manifest is an ETW thing, not an Event Log thing, and "register" is the ETW terminology for passing off a set of data about your events to the system (register your provider with EventRegister(), register your manifest with wevtutil.exe, etc.).
Registering the manifest allows any ETW consumer to enable the provider by looking up the name and/or decode any events logged by this provider through the TDH APIs. It just so happens that the Event Log is an (not the) ETW consumer (in addition to its older logging APIs), and the service reflects your  elements in the manifest into its own Event Log channels, but that's really just a side-effect of registering the manifest.


lume().copy() is a no-op when lume({src: "docs" }) is set

Version
2.2
Platform
win / lin amd
What steps will reproduce the bug?
if src is set, static doesn't copy. in this configuration everything works fine. as soon as I uncomment src: "docs", none of those copy commands work.
// _config.ts
const site = lume({
    // src: "docs",
});

site.copy("./static", ".");
site.copy("../static", ".");
site.copy("static", ".");
site.copy("static");

How often does it reproduce? Is there a required condition?
always
What is the expected behavior?
static files should copy even if I set src.
What do you see instead?
no copy unless src left at default
Additional information
i spend several hours trying to nail it down, and as far as I can tell copy just doesn't do anything when src is set. I tried many combinations of paths (the docs say static should be relative to docs, and I tried that as well). I tried all different names to make sure there was no magic name handling (i started with _static) but nothing seemed to make a difference. If src is set, copy doesn't work in any combination I came up with.

If static folder is outside the docs folder, it isn't copied because Lume works only with files inside the src folder.
All paths in your document are resolved to ./docs/static (or ./static if src is empty), but ./docs/../static is not allowed because it would be outside the src folder.
Maybe it should show a warning to make it more clear?

Thanks for the tool, and the quick response. Yeah, some indication of a failed copy would be great I think. Also in the documentation I think it just said that copy is relative to src, so I assumed "../some/path" would be fine. Warning would be best, but some hint in the docs there would also be nice.

Agreed.
I'll update the documentation to make it more clear. And will include a warning in the next version of Lume.
Thanks!

https://lume.land/docs/configuration/copy-static-files/
2nd paragraph


CredDefense doesn't list DC's

When running the CredDefense.exe and selecting the Password Filtering > Install/ Uninstall no Unconfigured DC's are listed.
The *.dll hasn't been previously deployed.
OS is Windows Server 2016.
Any idea what would cause this? Selecting the Password Auditing option it does enumerate the domain and DC.
Thanks for your feedback.

That is strange, nothing is under the "Configured" list either? Does the DC
respond to a ping request? If not, that might be the issue. I believe I
have a check under the Password Filtering option that it attempts to ping
the DCs before listing them in either column. I should probably just take
that check out.
Let me know please. Thanks!
On Wed, Oct 4, 2017 at 3:54 AM, ddonders<EMAIL_ADDRESS>wrote:

When running the CredDefense.exe and selecting the Password Filtering >
Install/ Uninstall no Unconfigured DC's are listed.
The *.dll hasn't been previously deployed.
OS is Windows Server 2016.
Any idea what would cause this? Selecting the Password Auditing option it
does enumerate the domain and DC.
Thanks for your feedback.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/CredDefense/CredDefense/issues/5, or mute the thread
https://github.com/notifications/unsubscribe-auth/ALb0HCHPmA3qfTxX9-DjlHf4CISzEN3pks5so1XGgaJpZM4PtXEs
.

Correct, nothing under configured either.
Doing this on a DEV DC, so running the tool locally.

Today tried on a 2008R2 DC, same result DC not listed when trying to install.

Followed the manual steps from the blog post

install .dll
copy \epf folder
add registry key
reboot

That appears to work.

Hey @ddonders I've got the same issue.  Brand new 2012 DC in a test/dev lab, and the DC list is empty when I install CredDefense.  When you say you followed manual steps from the blog post, were you referring to:
--

Deploy the EasyPasswordFilter DLL to the %SystemRoot%\Windows\System32 directory on the target DC

Deploy the password list to %SystemRoot%\epf folder on the target DC

Add the EasyPasswordFilter value to the HKLM\System\CurrentControlSet\Control\Lsa\Notifications registry key on the target DC
--

I'm thinking I've done all these right but still have an empty DC list for CredDefense, so wondering if maybe I'm missing a step.
Thanks,
Brian

Just thought I'd give this a bump.
BUMP
;-)

Trying to get this post active again.

For those interested and having an Azure AD subscription, MS released in preview a feature that should achieve the same.
https://docs.microsoft.com/en-us/azure/active-directory/authentication/concept-password-ban-bad

Hey just ran into similar issues on a clean fresh install 2016 DC in my lab, but was an easy fix so maybe not the same problem.
Two points to keep in mind,

The tool uses Powershell under the hood, so script execution must be allowed.
This tool must write to protected portions of the OS, and while it is obvious the tool needs to run as admin, I realized it does not prompt to elevate.

So if you still having trouble try this:

Open Powershell and do Set-ExecutionPolicy -ExecutionPolicy RemoteSigned
Then download the latest bits, and right-click to run as administrator and see if that makes everything just work.

Couple things I wanted to note for new users:

this is an awesome project! thanks to all that have contributed

I could not list DC's as well, I had a 2012 R2 server, but realized I was running the installer (CredDefense.exe) off the DC, I ran off a win10 workstation that I had joined to that domain and it worked perfect.

the installer installed the \epf folder off the root of the c:\ drive not in the c:\windows directory as noted in the manual install instructions.

I am not sure the the "excludeupdated.txt" and the "updated.txt" is for that is included in the install .zip.

thanks again for making this such a great project!

@JacobPete  I did not do any work on building this so could be wrong, to your point
2. You will likely find if trying to run CredDefense.exe on a DC again, but run it as administrator, it should work just fine running from a DC.  The catch is that CredDefense must run as an administrator for the work it does on the DC.  When you log into windows with an admin account you are signed in with reduced privileges and must elevate to actually run anything with full admin rights.  However PSRemoting connects with full admin rights.   This means when you run the exe on a DC you have to right click and tell the system to run it as admin, but when you run it from a client with an account that has admin rights on a DC it is automatically elevated when it initiates the remote connection to the DC.
all else, good points


add support for export default defineMessages

if defineMessages is an export default expression, it wasn't handled, now it is.

Please update index.ts instead of index.js file. Thanks


Data Prepper ToC Update

Signed-off-by: carolxob<EMAIL_ADDRESS>Description
Modifies Data Prepper documentation table of contents for accuracy and usability.
Issues Resolved
Closes issue #2453.
Modifies existing ToC to look like the following:
Getting started
Using for common scenarios
  - Trace analytics [pending review]
  - Log analytics
  - S3 log analytics [removed until content exists]
  - Metrics ingestion [removed until content exists]
Authoring Pipelines [placeholder]
  - Pipeline options
  - Expression syntax
  - Sources
  - Buffers
  - Processors
  - Sinks
Administrating Data Prepper [placeholder]
  - Configuring Data Data Prepper
  - Peer forwarder [pending review]
  - Core APIs
  - Log4j configuration
  - Monitoring Data Prepper
Migrating from Logstash
Migrating from Open Distro Data Prepper

Checklist

[x] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@dlvenable Where should the Pipelines section fit in this structure? Right now, it's showing as last in the TOC, but can be moved to wherever it should fit.

@dlvenable Where should the Pipelines section fit in this structure? Right now, it's showing as last in the TOC, but can be moved to wherever it should fit.

Thanks for catching that. I can see two good places for it:

At the top-level.

Data Prepper
Getting started
Pipelines
Using for common scenarios
...

Under the "Authoring pipelines" section.

Authoring Pipelines
  - Pipelines
  - Pipeline options
  ...

@carolxob , Which do you think would be the best location? The concept of pipelines is very core to Data Prepper, so I tend to think option #1.

@dlvenable Regarding Pipelines, combined both of your suggestions so that it looks like this:
       -Pipeline options
       -Expression syntax
       - Sources
       - Buffers
       - Processors
       - Sinks

How does this look to you?

I think there's a usage of S3 Source and should be S3Source.


[Bug] Enable subject for policies

Kyverno Version
1.6.x
Kubernetes Version
1.23.x
Kubernetes Platform
KinD
Description
commented out the relevant blocks in the test cases.
Need to add userinfo.yaml for those policies.
Example:
for limit-configmap-for-sa-developer
subject:
  kind: ServiceAccount
  name: another-developer
  namespace: another-namespace

Steps to reproduce
NA
Expected behavior
NA
Screenshots
No response
Kyverno logs
No response
Slack discussion
No response
Troubleshooting

[X] I have read and followed the documentation AND the troubleshooting guide.
[X] I have searched other issues in this repository and mine is not recorded.

The new UserInfo schema can now handle this.


RUNNING state, process has stayed up for > than 1 seconds (startsecs)

when I run docker-compose --file ./docker-compose.dev.yml up --build
the terminal window looks like this:
supervisor/conf.d/supervisor.conf" during parsing
pb-app                 | Unlinking stale socket /var/run/supervisor.sock
pb-app                 | 2018-09-01 15:06:41,601 INFO RPC interface 'supervisor' initialized
pb-app                 | 2018-09-01 15:06:41,601 CRIT Server 'unix_http_server' running without any HTTP authentication checking
pb-app                 | 2018-09-01 15:06:41,602 INFO supervisord started with pid 1
pb-app                 | 2018-09-01 15:06:42,606 INFO spawned: 'app-scheduler' with pid 140
pb-app                 | 2018-09-01 15:06:42,610 INFO spawned: 'app' with pid 141
pb-app                 | 2018-09-01 15:06:42,614 INFO spawned: 'app-queue' with pid 142
pb-app                 | 2018-09-01 15:06:43,662 INFO success: app-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pb-app                 | 2018-09-01 15:06:43,662 INFO success: app entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pb-app                 | 2018-09-01 15:06:43,662 INFO success: app-queue entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

Is this correct?
After creating the admin user account, I can't access the running application at http://localhost:8080

The command output looks good.
Do you have an access to other application resources?
http://localhost:8081 - REST API documentation;
http://localhost:8083 - MailDev mailbox.

No - I get localhost refused to connect. on all ports

No, mac
On Sun, Sep 2, 2018 at 2:24 AM Oleksandr Tolochko<EMAIL_ADDRESS>wrote:

Do you use Windows host machine?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tooleks/photo-blog/issues/287#issuecomment-417910716,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABORPPa8gPT7to0bTbauA0w6w9GkCqMvks5uW4fHgaJpZM4WWQUI
.

Could you give me the output of the command docker container ls? Just to double check that application is up and running.
Otherwise, could you give me more info about your system? Do you use a Docker Toolbox or Docker for Mac? There are some differences: https://docs.docker.com/docker-for-mac/docker-toolbox/#the-docker-toolbox-environment

I updated my Docker and I can run the app now.
Here is docker container ls
~/projects/photo-blog (master)$ docker container ls
CONTAINER ID        IMAGE                  COMMAND                  CREATED             STATUS              PORTS                                      NAMES
2c2ab0d68558        nginx:1.13             "nginx -g 'daemon of…"   4 minutes ago       Up 4 minutes        80/tcp, <IP_ADDRESS>:8080-8082->8080-8082/tcp   pb-app-nginx
6298d87b2439        pb-app-php:7.2-fpm     "/entrypoint.sh /usr…"   4 minutes ago       Up 4 minutes        9000/tcp                                   pb-app
8c564602f22e        pb-prerender-node:10   "node server.js"         About an hour ago   Up 11 minutes       <IP_ADDRESS>:3000->3000/tcp                     pb-prerender
4b5d03d83e68        djfarrelly/maildev     "bin/maildev --web 8…"   About an hour ago   Up 11 minutes       25/tcp, <IP_ADDRESS>:8083->80/tcp               pb-maildev
24b87feb2f96        redis:3.2              "docker-entrypoint.s…"   About an hour ago   Up 11 minutes       6379/tcp                                   pb-redis
7bd9c8e3e1ce        mysql:5.7              "docker-entrypoint.s…"   About an hour ago   Up 4 minutes        <IP_ADDRESS>:3306->3306/tcp, 33060/tcp          pb-mysql
~/projects/photo-blog (master)$

Ok, cool. What version do you use now? This may be helpful for other Mac users.


[BUG] - Components/Table

Describe the bug
The table is re-rendered every time the mouse and keyboard are clicked. If you click sequentially first on the left mouse button, then on any button on the keyboard, the table will be rendered as a result 2 extra times. This is the sequence in which it works.
Your Example Website or App
https://codesandbox.io/s/zbgfe2?file=/App.js:0-1209&from-sandpack=true
Steps to Reproduce the Bug or Issue

Open sandbox
Activate flag in Profiler "Highlight updates when components render."
Click the left mouse button anywhere.
Table rerendered.
Press any key on the keyboard.
Table rerendered again!
Repeat this as many times as you want and the table will be rerendered all the time.

Expected behavior
The table should not be re-rendered by pressing the keyboard and mouse.
Screenshots or Videos

Operating System Version
Linux
Browser
Chrome

Hey @Yan-Zhelanov I couldn't see any re-render on  mouse hover, right/left click or pressing any keyboard key
https://user-images.githubusercontent.com/30373425/187081211-c899024b-dd62-47e2-8b34-3c195481c9f7.mov

@jrgarciadev how did you solve this issue?

Using the exact example in the nextui website. I can not get Topcontent to not rerender everytime I click anywhere in the table.
Im trying to implement the searchInput in topContent. Impossible! Even with correct memoization and callbacks


Add support for symbolic links for content, layout, static, theme

Note: This is for the content roots only, but that should satisfy most needs.
Fixes #1855

merged as e5aa477

This suggests that the content folder can be symlinked.
So my symlink points to a parent directory (I have tried other locations):
content -> ../content

It's populated with test files:
.
├── file-01.md
├── file-02.md
└── post
    ├── file-03.md
    └── file-04.md

But a build results in the following output:
$ hugo server --buildDrafts
Started building site
0 draft content
0 future content
0 pages created
0 non-page files copied
0 paginator pages created
0 tags created
0 categories created
in 21 ms
Watching for changes in /{DIRECTORY_NAME_HERE}/{data,layouts,static,themes}
Serving pages from memory
Web Server is available at http://localhost:1313/ (bind address <IP_ADDRESS>)

I notice the content folder isn't mentioned and there's a 0 by draft content.
Am I going wrong somewhere? I'm using v0.16 on OSX.
Thanks.

Please use http://discuss.gohugo.io/ -- if you believe it is a bug, please create a new one, I'm not reading old stuff (or, I did now, but in general).


[Feature Request] Add support for Amazon.it

Can you kindly add the support for Amazon.it (Italy)?
It would be amazing if Italians can use this great Integration!
Thank you =)

In order to get this working properly can you follow these steps or similar to provide a copy of the email(s) Amazon sends?

Sure!
Here attached you can find two emails type: the one I receive when Amazon ships and the one I receive when the shipping is delivered.
Please tell me if you need also the order confirmation email.
Thank you!
Emails.zip

This will be a little tricky since they don't use "shipment-tracking".
I'll see what I can get done.

If I can help, I can tell you that an italian Telegram Bot can track Amazon Shipment using the link inside that email.

I worked it out 👍

This should work in b16.

B16 breaks with:
Logger: custom_components.mail_and_packages.helpers
Source: custom_components/mail_and_packages/helpers.py:264
Integration: Mail and Packages (documentation, issues)
First occurred: 10:39:07 PM (43 occurrences)
Last logged: 10:39:08 PM
Error searching emails: SEARCH command error: BAD [b'Could not parse command']

Your image path is wrong.

I corrected it (don't use it), but the remaining error is still there:
Logger: custom_components.mail_and_packages.helpers
Source: custom_components/mail_and_packages/helpers.py:264
Integration: Mail and Packages (documentation, issues)
First occurred: 12:26:47 AM (43 occurrences)
Last logged: 12:26:48 AM
Error searching emails: SEARCH command error: BAD [b'Could not parse command']

Please enable debugging and report what shows up in the log.

I found the issue, typo in the search builder, b17 will resolve it.

So, I tried b17 and those are my findings.
Please, forgive me if it isn't professional, I never coded anything =D

The setup of Gmail is OK (probably no changes from other countries due to the fact it's always Google.com);

This is the setup I used on an Home Assistant Supervised on Docker istance:

Those are the entities generated by the integration:

This is the custom card configuration I'm using to a quick understanding if it's working or not:

As you can see from my last screenshot, I have some question:
1- Do I have the Delivery Message Sensor? If yest, which one is it? Did I miss some sensor from the "Sensor List" selected during the setup?
2- If I click on my "Amazon Package Sensor" link, It opens Amazon.com instead of Amazon.it.
3- When it's supposed to have the first image on the  card? Do I have to wait the next mail from Amazon?
Thank you for your work!

One more finding:
I have one package in transit from Amazon. Expected delivery on Monday.
Probably the counter is 0 cause the integration will scan only new emails and not the old. Is this corrected?

One more finding:
I have one package in transit from Amazon. Expected delivery on Monday.
Probably the counter is 0 cause the integration will scan only new emails and not the old. Is this corrected?

This is covered by the wiki.
As for the custom card, that's all @moralmunky, feel free to open a feature request on the custom card's github about the link.
Alternatively you could use some examples from the wiki to display your deliveries as well.

This is covered by the wiki.
As for the custom card, that's all @moralmunky, feel free to open a feature request on the custom card's github about the link.
Alternatively you could use some examples from the wiki to display your deliveries as well.

Thank you as usual for your reply!
I'll switch to another card, thank you!

Delivery message sensor is also covered in the wiki. You must create one yourself, examples are provided.
The link in the card is hard coded for Amazon.com. Not sure of a way to change that based on the integration, I suppose it could be an option in the card setting to provide the address the link should take you to.
Please create a request in the card repository.

Hello, i'm still trying B17. But all of the sensors used are listing 0 packages. Today i'm going to receive 4 shimpents.
Do I wrong something?

Please enable debugging and post the messages from the log.


Enable MetricsExporter and PrometheusRules only on main namespace

In a multi storagecluster scenario, both metrics-exporter and PrometheusRules should only be enabled on the main namespace.

@aruniiird is this still WIP?

All the changes are done (except for the functional tests).
Verified the fix on @iamniting provided cluster...

@jmolmo , fix is now tested.
@umangachapagain , please take a look


Fix "Your code installation is corrupt..." message?

Why does this show up? No other extension I have does this.
While the extension is nice, seeing that message pop up (and being recommended to just hide it) doesn't inspire much quality.
After doing some research, this also means that future visual code updates will overwrite this extension's installed files? That doesn't sound very stable.
I'd love to use the extension otherwise, but I have also experienced visual code just closing, and upon reopening it the extension was gone.

The popup shows up because the extension makes a direct editing to one of vs code installation files. The ideal would be to avoid doing this but this is the only way to make this feature possible.
There are some other extensions that use patching and they trigger the popup as well.

"Your Code installation appears to be corrupt. Please reinstall." Even after uninstalling Tabs Color. Not good. I dont want reinstall IDE because of coloring tabs.

Maybe you could add a tiny external script that "unpatches" the files to avoid having to potentially reinstall: either from a backup or just stripping the added content (you could surround it by some headed/end comments)
Btw Is it just bootstrap-window.js ?

@dimateos the ideal solution is to run an script that will clear the patch at the extension's uninstall. Nobody has managed to make it work though, please follow this thread here #16

I guess that is good enough given the current API

IMPORTANT NOTE : AFTER INSTALLING TABSCOLOR YOU MAY GET THE POPUP "YOUR CODE INSTALLATION IS CORRUPT..." UPON RESTART. JUST CLICK ON THE GEAR ICON AND CHOOSE DON'T SHOW AGAIN.

^ You should mention it in the readme to avoid users seeing the message after unisntalling etc


Move react/react-dom to dev and peer dependencies

Fixes #13

Just a friendly ping on this pull request @pbojinov . Is it possible to get this in and a new version released? I'd be happy to help out with any of that work.

@pbojinov any updates to this possibly?


xmldata:fromJson silently fails to convert json to xml

Description:
With the code below I'm expecting to get
xml2 is xml
<root>ERROR_CODEERROR_DETAILS</root>

but instead I'm getting
xml2 is xml
{"code":"ERROR_CODE","details":"ERROR_DETAILS"}

It looks like in the case 2 xmldata:fromJson silently fails.
Steps to reproduce:
$ bal version
Ballerina 2201.0.3 (Swan Lake)
Language specification 2022R1
Update Tool 1.3.9

$ cat issue.bal
import ballerina/http;
import ballerina/io;
import ballerina/xmldata;

public function main() returns error? {
    // CASE 1

    json json1 = {
        code: "ERROR_CODE",
        details: "ERROR_DETAILS"
    };

    xml? xml1 = check xmldata:fromJson(json1);

    if xml1 is xml {
        io:println("xml1 is xml");
    }
    io:println(xml1);

    // CASE 2

    http:BadRequest badRequest = {
        body: {
            code: "ERROR_CODE",
            details: "ERROR_DETAILS"
        }
    };
    io:println(badRequest);

    json json2 = <json> badRequest?.body;
    xml? xml2 = check xmldata:fromJson(json2);

    if xml2 is xml {
        io:println("xml2 is xml");
    }
    io:println(xml2);
}

$ bal run issue.bal
Compiling source
	issue.bal

Running executable

xml1 is xml
<root>ERROR_CODEERROR_DETAILS</root>
{"status":object http:StatusBadRequest,"body":{"code":"ERROR_CODE","details":"ERROR_DETAILS"}}
xml2 is xml
{"code":"ERROR_CODE","details":"ERROR_DETAILS"}

@kalaiyarasiganeshalingam Can you check on this

This problem is in the different type of JSON format, which is returned by json json2 = <json> badRequest?.body; and json json2 = badRequest?.body.toJson();
Run the following code to find these differences:
import ballerina/http;
import ballerina/io;

public function main() returns error? {
    http:BadRequest badRequest = {
        body: {
            code: "ERROR_CODE",
            details: "ERROR_DETAILS"
        }
    };

    json json1 = <json> badRequest?.body;
    json json2 = badRequest?.body.toJson();
    map<json> mapJson2 = check json2.ensureType();
    io:println(mapJson2);
    map<json> mapJson1 = check json1.ensureType();
    io:println(mapJson1);
}

The following error is returned by map<json> mapJson1 = check json1.ensureType();
error: {ballerina}TypeCastError {"message":"incompatible types: 'map<anydata>' cannot be cast to 'map<json>'"}

@MaryamZi Do we have any reason to return different types of JSON from these?

Thanks @MaryamZi
Yes, it works when converting to JSON first and then using xmldata:fromJson.


regression: pixi tries to GET pypi.org/simple in offline environment

Checks

[x] I have checked that this issue has not already been reported.

[x] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
# pixi.toml
[project]
authors = ["Moritz Wilksch<EMAIL_ADDRESS>channels = [
  "https://artifactory.internal-stuff.com/artifactory/conda-forge-mirror",
]
description = "Add a short description here"
name = "pixi-mre"
platforms = ["linux-64"]
version = "0.1.0"

conda-pypi-map = {}

[tasks]

[dependencies]
python = ">=3.13.0,<3.14"
setuptools = ">=75.3.0,<76"

[pypi-options]
no-build-isolation = ['mre']

[pypi-dependencies]
mre = { path = ".", editable = true }

# pyproject.toml
[project]
name = 'mre'
version = '0.1.0'

Issue description
pixi tries to GET pypi.org/simple in an offline environment even though the pypi-conda-map is set to {}. This setup used to work in pixi=0.34.0 but is broken with 0.35.0. I also tried overriding the find-links option, but that didn't help or is there a recommended override value?
➜  pixi-mre pixi i -vvvv
DEBUG pixi_config: Loading config from /etc/pixi/config.toml
 INFO pixi_config: Loaded config from: /etc/pixi/config.toml
DEBUG pixi_config: Loading config from /home/USERNAME/.config/pixi/config.toml
 INFO pixi_config: Loaded config from: /home/USERNAME/.config/pixi/config.toml
DEBUG pixi_config: Loading config from /home/USERNAME/.config/pixi/config.toml
 INFO pixi_config: Loaded config from: /home/USERNAME/.config/pixi/config.toml
DEBUG pixi_config: Loading config from /home/USERNAME/.pixi/config.toml
DEBUG pixi_config: Failed to load global config: /home/USERNAME/.pixi/config.toml (error: failed to read config from '/home/USERNAME/.pixi/config.toml')
DEBUG pixi_config: Loading config from /home/USERNAME/Documents/pixi-mre/.pixi/config.toml
DEBUG pixi_config: Failed to load local config: /home/USERNAME/Documents/pixi-mre/.pixi/config.toml (error: failed to read config from '/home/USERNAME/Documents/pixi-mre/.
pixi/config.toml')
DEBUG pixi::project: Symlink already exists at '/home/USERNAME/Documents/pixi-mre/.pixi/envs', skipping creating symlink.
 INFO pixi::environment: verifying prefix location is unchanged, with prefix file: /opt/pixi/envs/pixi-mre-14179212012911116289/envs/default/conda-meta/pixi_env_prefix
 INFO pixi::lock_file::update: the lock-file is up-to-date
DEBUG pixi::environment: Wrote environment file to: "/opt/pixi/envs/pixi-mre-14179212012911116289/envs/default/conda-meta/pixi"
DEBUG pixi::rlimit: Attempted to set RLIMIT_NOFILE to 1024 but was already set to 65535
 INFO pixi::environment: Creating prefix file at: /opt/pixi/envs/pixi-mre-14179212012911116289/envs/default/conda-meta/pixi_env_prefix
 INFO pixi::environment: No update needed for the prefix file.
 INFO pixi::environment: Checking if history file exists: /opt/pixi/envs/pixi-mre-14179212012911116289/envs/default/conda-meta/history
 INFO pixi::lock_file::resolve::uv_resolution_context: uv keyring provider is disabled
DEBUG uv_client::base_client: Using request timeout of 30s
TRACE get_cacheable:read_and_parse_cache{file=/tmp/USERNAME/cache/rattler/cache/uv-cache/flat-index-v1/html/b2a7eb67d4c26b82.msgpack}: uv_client::cached_client: No cache
entry exists for /tmp/USERNAME/cache/rattler/cache/uv-cache/flat-index-v1/html/b2a7eb67d4c26b82.msgpack
DEBUG get_cacheable: uv_client::cached_client: No cache entry for: https://pypi.org/simple
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: uv_client::cached_client: Sending fresh GET request for https://pypi.org/simple
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: uv_auth::middleware: Handling request for https://pypi.org/simple
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: uv_auth::middleware: Request for https://pypi.org/simple is unauthenticated, checking cache
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: uv_auth::cache: No credentials in cache for URL https://pypi.org/simple
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: uv_auth::middleware: Attempting unauthenticated request for https://pypi.org/simple
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: hyper_util::client::legacy::pool: checkout waiting for idle connection: ("https", pypi.org)
DEBUG get_cacheable:fresh_request{url="https://pypi.org/simple"}: reqwest::connect: starting new connection: https://pypi.org/
DEBUG get_cacheable:fresh_request{url="https://pypi.org/simple"}: reqwest::connect: proxy(http://MYPROXY:3128) intercepts 'https://pypi.org/'
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: hyper_util::client::legacy::connect::http: Http::connect; scheme=Some("http"), host=Some("IP
2"), port=Some(Port(3128))
DEBUG get_cacheable:fresh_request{url="https://pypi.org/simple"}: hyper_util::client::legacy::connect::http: connecting to MYPROXY:3128
DEBUG get_cacheable:fresh_request{url="https://pypi.org/simple"}: hyper_util::client::legacy::connect::http: connected to MYPROXY:3128
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: reqwest::connect: tunneling HTTPS over proxy
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: hyper_util::client::legacy::pool: checkout dropped for ("https", pypi.org)
DEBUG get_cacheable:fresh_request{url="https://pypi.org/simple"}: uv_client::base_client: Transient request failure for https://pypi.org/simple, retrying: error sending
request for url (https://pypi.org/simple)
  Caused by: client error (Connect)
  Caused by: unsuccessful tunnel
 WARN get_cacheable:fresh_request{url="https://pypi.org/simple"}: reqwest_retry::middleware: Retry attempt #0. Sleeping 373.638361ms before the next attempt
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: uv_auth::middleware: Handling request for https://pypi.org/simple
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: uv_auth::middleware: Request for https://pypi.org/simple is unauthenticated, checking cache
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: uv_auth::cache: No credentials in cache for URL https://pypi.org/simple
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: uv_auth::middleware: Attempting unauthenticated request for https://pypi.org/simple
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: hyper_util::client::legacy::pool: checkout waiting for idle connection: ("https", pypi.org)
DEBUG get_cacheable:fresh_request{url="https://pypi.org/simple"}: reqwest::connect: starting new connection: https://pypi.org/
DEBUG get_cacheable:fresh_request{url="https://pypi.org/simple"}: reqwest::connect: proxy(http://MYPROXY:3128) intercepts 'https://pypi.org/'
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: hyper_util::client::legacy::connect::http: Http::connect; scheme=Some("http"), host=Some("IP
2"), port=Some(Port(3128))
DEBUG get_cacheable:fresh_request{url="https://pypi.org/simple"}: hyper_util::client::legacy::connect::http: connecting to MYPROXY:3128
DEBUG get_cacheable:fresh_request{url="https://pypi.org/simple"}: hyper_util::client::legacy::connect::http: connected to MYPROXY:3128
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: reqwest::connect: tunneling HTTPS over proxy
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: hyper_util::client::legacy::pool: checkout dropped for ("https", pypi.org)
DEBUG get_cacheable:fresh_request{url="https://pypi.org/simple"}: uv_client::base_client: Transient request failure for https://pypi.org/simple, retrying: error sending
request for url (https://pypi.org/simple)
  Caused by: client error (Connect)
  Caused by: unsuccessful tunnel
 WARN get_cacheable:fresh_request{url="https://pypi.org/simple"}: reqwest_retry::middleware: Retry attempt #1. Sleeping 245.370932ms before the next attempt
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: uv_auth::middleware: Handling request for https://pypi.org/simple
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: uv_auth::middleware: Request for https://pypi.org/simple is unauthenticated, checking cache
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: uv_auth::cache: No credentials in cache for URL https://pypi.org/simple
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: uv_auth::middleware: Attempting unauthenticated request for https://pypi.org/simple
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: hyper_util::client::legacy::pool: checkout waiting for idle connection: ("https", pypi.org)
DEBUG get_cacheable:fresh_request{url="https://pypi.org/simple"}: reqwest::connect: starting new connection: https://pypi.org/
DEBUG get_cacheable:fresh_request{url="https://pypi.org/simple"}: reqwest::connect: proxy(http://MYPROXY:3128) intercepts 'https://pypi.org/'
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: hyper_util::client::legacy::connect::http: Http::connect; scheme=Some("http"), host=Some("IP
2"), port=Some(Port(3128))
DEBUG get_cacheable:fresh_request{url="https://pypi.org/simple"}: hyper_util::client::legacy::connect::http: connecting to MYPROXY:3128
DEBUG get_cacheable:fresh_request{url="https://pypi.org/simple"}: hyper_util::client::legacy::connect::http: connected to MYPROXY:3128
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: reqwest::connect: tunneling HTTPS over proxy
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: hyper_util::client::legacy::pool: checkout dropped for ("https", pypi.org)
DEBUG get_cacheable:fresh_request{url="https://pypi.org/simple"}: uv_client::base_client: Transient request failure for https://pypi.org/simple, retrying: error sending
request for url (https://pypi.org/simple)
  Caused by: client error (Connect)
  Caused by: unsuccessful tunnel
 WARN get_cacheable:fresh_request{url="https://pypi.org/simple"}: reqwest_retry::middleware: Retry attempt #2. Sleeping 1.64212909s before the next attempt
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: uv_auth::middleware: Handling request for https://pypi.org/simple
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: uv_auth::middleware: Request for https://pypi.org/simple is unauthenticated, checking cache
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: uv_auth::cache: No credentials in cache for URL https://pypi.org/simple
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: uv_auth::middleware: Attempting unauthenticated request for https://pypi.org/simple
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: hyper_util::client::legacy::pool: checkout waiting for idle connection: ("https", pypi.org)
DEBUG get_cacheable:fresh_request{url="https://pypi.org/simple"}: reqwest::connect: starting new connection: https://pypi.org/
DEBUG get_cacheable:fresh_request{url="https://pypi.org/simple"}: reqwest::connect: proxy(http://MYPROXY:3128) intercepts 'https://pypi.org/'
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: hyper_util::client::legacy::connect::http: Http::connect; scheme=Some("http"), host=Some("IP
2"), port=Some(Port(3128))
DEBUG get_cacheable:fresh_request{url="https://pypi.org/simple"}: hyper_util::client::legacy::connect::http: connecting to MYPROXY:3128
DEBUG get_cacheable:fresh_request{url="https://pypi.org/simple"}: hyper_util::client::legacy::connect::http: connected to MYPROXY:3128
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: reqwest::connect: tunneling HTTPS over proxy
TRACE get_cacheable:fresh_request{url="https://pypi.org/simple"}: hyper_util::client::legacy::pool: checkout dropped for ("https", pypi.org)
DEBUG get_cacheable:fresh_request{url="https://pypi.org/simple"}: uv_client::base_client: Transient request failure for https://pypi.org/simple, retrying: error sending
request for url (https://pypi.org/simple)
  Caused by: client error (Connect)
  Caused by: unsuccessful tunnel
  × default: error installing/updating PyPI dependencies
  ├─▶ Failed to read `--find-links` URL: https://pypi.org/simple
  ├─▶ Failed to fetch: `https://pypi.org/simple`
  ├─▶ Request failed after 3 retries
  ├─▶ error sending request for url (https://pypi.org/simple)
  ├─▶ client error (Connect)
  ╰─▶ unsuccessful tunnel

pixi=0.34.0 works:
➜  pixi-mre pixi exec -s pixi=0.34.0 -- pixi install
✔ The default environment has been installed in '/opt/pixi/envs'.

Expected behavior
Similar to 0.34.0 I can prevent the attempted internet access by setting the conda-pypi-map to empty.

maybe related to #2417?

Hmm, I am unsure if I understand entirely. Is this a problem when you already have a lockfile or is this for a completely fresh project? Does mre have any additional dependencies or not?
The pypi-conda mapping doesn't really tie in with accessing pypi.org. Those are separate things.
It's "somewhere" in uv where the pypi index is accessed.
We could potentially add an option to the PyPI options in the pixi / pyproject toml to influence this variable: https://github.com/prefix-dev/pixi/blob/0c8343851fa33440d843fbbb6deaa48a268c154e/src/lock_file/resolve/pypi.rs#L233-L234
Setting that to offline should make things work for your usecasee.

Yes, this is a completely fresh project without an existing lock file and no additional dependencies. Basically, the editable install of my local package now requires internet access and didn't before. Exposing an "offline" option would be great!
You're right, it might be a change in uv itself 🤔
The conda-pypi-map has always been a necessary configuration to work in offline envs because otherwise pixi attempts fetching the map from a prefix.dev server. But you're right in that it shouldn't be related to the pypi issue.


get_starting_seeds returns nothing

hi, it seems that get_starting_seeds returns nothing..

error during 3D generation -- Can't instantiate abstract class AtomFragmentLibrary with abstract methods get, len

Hi, this is an environment issue caused by different or conflicting versions of Pytorch / Pytorch-Geometric. Please check to make sure your environment setup matches what I've included in environment.yml. Alternatively, you can try to manually add the methods def get(...): return __get__(...) and def len(...): return __len__(...) to the Dataset classes that are throwing this error.


Unused varaibles in LedControl.cpp

.pio/libdeps/mega/LedControl/src/LedControl.cpp: In member function 'void LedControl::clearDisplay(int)':
.pio/libdeps/mega/LedControl/src/LedControl.cpp:100:9: warning: variable 'offset' set but not used [-Wunused-but-set-variable]
     int offset;
         ^~~~~~
.pio/libdeps/mega/LedControl/src/LedControl.cpp: In member function 'void LedControl::setDigit(int, int, byte, boolean)':
.pio/libdeps/mega/LedControl/src/LedControl.cpp:163:9: warning: variable 'offset' set but not used [-Wunused-but-set-variable]
     int offset;
         ^~~~~~
.pio/libdeps/mega/LedControl/src/LedControl.cpp: In member function 'void LedControl::setChar(int, int, char, boolean)':
.pio/libdeps/mega/LedControl/src/LedControl.cpp:181:9: warning: variable 'offset' set but not used [-Wunused-but-set-variable]
     int offset;
         ^~~~~~

Either use them or remove them

There is already a pull request since ~9 month to avoid this warning ;)

Which one? I didn't see an open issue for this 😬

It`s a library, PR is in the repo for the LEDControl (not on my PC)

Ahhhh

Can't do this without the library changing, closing.


Version catalog error message do not include path to the toml file.

I messed up a toml declaration and got :
`org.gradle.api.InvalidUserDataException: Invalid TOML catalog definition:

Problem: In version catalog libs, parsing failed with 2 errors.
Reason: At line 2, column 26: Unexpected '.', expected a newline or end-of-input
At line 3, column 13: Unexpected '.', expected a newline or end-of-input.
Possible solution: Fix the TOML file according to the syntax described at https://toml.io.
Please refer to https://docs.gradle.org/8.0/userguide/version_catalog_problems.html#toml_syntax_error for more details about this problem.`

nice message except it would be much better to also include the file path in question...

Thank you for your interest in Gradle!
This issue will be closed as a duplicate of

#20368

Please add your use case and 👍 to that issue.


Issues #17, #18, #20, #25 - Indoor map

#17, #18, #20, #25
In this pull request, I aim to bring in the following functionality:

The ability to navigate between 2 rooms on the 8th floor of the Hall building (no other buildings are currently supported

The ability to generate the shortest path between 2 rooms on the same floor.

Displaying room numbers, and information on the indoor map

Wow, amazing work! 😍
I ran the code and tried various points on the map. I found some issues:

Although these are rooms, the map displays a path between the two escalators
From: hall-806.03
To: hall-840
The path between these two rooms is generating over the glass walls next to the escalators
From: hall-820.01
To: hall-840

I also ran all UI and unit tests, everything is passing 🙂
Please look into the two navigation scenarios and commenting your code 😬

I made a fix to the SVG file, so now no paths will be generated that cross through the glass wall


Fix fcm endpoint JSON format

Short description
The JSON format of the fcm API endpoint is not in the format the app expects it to be.
Proposed changes
Each message needs to have the following attributes: id, message, timestamp, title.

Looks good! Could you add a changelog note again?

I just had the same thought ;-)


Add missing opening tag in Get-started > Multi-Container

Proposed changes
Add a missing opening tag for a code snippet : https://docs.docker.com/get-started/07_multi_container/#running-our-app-with-mysql

Oh! I just merged a similar fix in https://github.com/docker/docker.github.io/pull/12040, so this one will no longer be needed. Thanks for contributing!

Oh! I just merged a similar fix in https://github.com/docker/docker.github.io/pull/12040, so this one will no longer be needed. Thanks for contributing!


Terrain RGBA read, GTLFImporter Name Correcting

I added control to GLTF Importer name extraction.
I have the map heights read as floats. For this reading method, it will be enough to set the float to the rgba value.

Would be nice to have 1 feature per PR. This way it may be easier to track them down,  cherry-pick, roll back, etc.

@qwertyu131 Can you please explain the function of importer changes, on real world example? I struggle to understand it.

Json -> "images":[{"name":"images_name.png","bufferView":0,"mimeType":"image/png"}
Even though the json data has name, uri_name was being set.
In the outputs, the image name parts were like texture_%d.png. It will be a problem for those who want to use the names of the files.

I merged GLTF part manually.
I don't want to merge terrain part because it is basically your personal file format support. Storing floats bit-by-bit in the image is way too specialized and there are no public tools that can generate such images.


add ryantm to reviewer team

:tada:
I'll probably deploy this later today. Don't hesitate to ping me when the bot does weird things.

Deployed!


minifier should be portable and support runtime dispatch

Currrently, the function json_minify is SIMD accelerated only on AVX2, it does not support runtime dispatch and there is no fast ARM version.
It is a  low-hanging fruit.
Related: this PR https://github.com/lemire/simdjson/pull/383
cc @jkeiser

Yeah, genericizing that will be an enlightening exercise!
On Mon, Dec 2, 2019, 8:48 AM Daniel Lemire<EMAIL_ADDRESS>wrote:

Currrently, the function json_minify is SIMD accelerated only on AVX2, it
does not support runtime dispatch and there is no fast ARM version.
It is a low-hanging fruit.
Related: this PR #383 https://github.com/lemire/simdjson/pull/383
cc @jkeiser https://github.com/jkeiser
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lemire/simdjson/issues/384?email_source=notifications&email_token=AAE74IWFIVDNN5DDSVFPKQLQWU343A5CNFSM4JTYXJPKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H5KV27Q,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAE74IWESBAZWGYXMTJDRK3QWU343ANCNFSM4JTYXJPA
.


Error when adding slimmemeter

Describe the bug
When adding a slimmemeter as a meter, I get a 404
Steps to reproduce
I've added the following node in my config
`meters:

name: slimmemeter
type: template
template: slimmelezer
usage: grid
host: <IP_ADDRESS> # IP-Adresse oder Hostname`

When starting EVCC I get ERROR 2024/10/03 14:42:36 grid meter: add[0]: unexpected status: 404 (Not Found)
When go to either of the following URLs in a browser I get correct data
http://<IP_ADDRESS>/sensor/power_consumed
http://<IP_ADDRESS>/sensor/power_consumed_phase_3
Configuration details
meters:
  - name: slimmemeter
    type: template
    template: slimmelezer
    usage: grid
    host: <IP_ADDRESS> # IP-Adresse oder Hostname

Log details
ERROR 2024/10/03 14:42:36 grid meter: add[0]: unexpected status: 404 (Not Found)

What type of operating system are you running?
HomeAssistant Add-on
Nightly build

[X] I have verified that the issue is reproducible with the latest nightly build

Version
No response

See template- the URLs are different:
/sensor/power_returned

It is: https://docs.evcc.io/docs/devices/meters#slimmelezer-v2


Fix Intercom created date

Intercom contact noticed that the signed up date and last seen date are the same for our users on Intercom.
"This is because the created_at timestamp should be the signed up date for the user, not the current timestamp. I think you are sending is the current timestamp here."

See Carmelo comes in as a new addition on intercom here:

See below that Carmelos has been registered for 3 months and is not new. It is taking the data from the last time they logged in:

@petecoderdojo this is fixed now, tested and deployed. Congratulations on your first PR, @josmas! :)


Added support for 7zip SFX archives

Scans for magic header when ReaderOptions.LookForHeader is set

run dotnet csharpier . after refreshing the tools to get the formatting please
not sure I grasp why AutoArchiveFactory is needed but looks good to me if tests pass

AutoArchiveFactory allows to unify tests with or without IArchiveFactory provided (e.g. if none - auto is used). I assume it could be useful in other scenarios too.


Scroll Lock Requires Target Element

I have a page that does NOT have an element I desire to remain scrollable once the page is scroll locked with iOS .  I simply want to lock the page scroll.  In order to work around this, I had to place an empty "display:none" element on the page and use it as the target element.  Easy work around; however, tripped me up for a while.

This is a duplicate of #55.

They stopped the repairs. I had to do it myself, in the same way, with a new version of typeScript. And fix these problems for everyone to use.
npm i body-scroll-lock-upgrade

repair log，Refer to the releases page.


non-working touchpad

uhhh

i have msi modern 15 b7m

oh

i have msi modern 15 b7m,
with a ryzen 5 7530u.
the rest of the configuration seems to be identical to the modern 15 a5m.
everything works fine in monterey, even the webcam, but the touchpad doesn't.
i tried to add voodooi2c (because in windows device manager the touchpad is marked as connected via I2C bus), but I got some error.
removing/disabling voodoops2 didn't solve the problem, although i don't think that's the issue here.

i tried installing voodooI2C again, it worked, now it shows touchpad in settings but it doesn't work ! turning it on/off with the button doesn't help of course.
also lots of text like this:
VoodooI2CELAN touchpad driver: invalid report (1)
maybe it's because the touchpad is not ELAN, but in that case I don't know what to do at all. please help.
i also attach a screenshot of the installed voodooi2c and voodoops2 (for keyboard and mouse) kexts:

i checked in windows again, more in depth, and found that this touchpad is ELAN after all.
but it doesn't work with voodooi2celan.
does anyone know what could be the problem?

ref: https://www.reddit.com/r/hackintosh/comments/hhf263/kext_elan_ps2_touchpad_new_kext/?rdt=49293
If it doesn't work try VoodooSMBus kext

Also, you could checkout this commit
Ensure the Trackpad plugin is inside the VoodooPS2Controller.kext/Plugins directory.

oh
i don't think it's gonna work in my case.
but i'm gonna try it anyway

I installed a new version of voodoops2, of course it didn't work, also the command key for some unknown reason to me, swapped with the option key.

gonna try voodoosmbus

just as i thought, voodoosmbus doesn't work either.

anyway, none of the methods worked and the touchpad still doesn't work.

and it also disappeared from the settings

the only thing I can say is that the touchpad here is definitely ELAN.
because that's what it says in windows device manager.
i reverted the configuration with voodooI2C but it still doesn't work, however the touchpad is showing up in the settings again.

Try this version

ok i'm gonna try it

again, it's not working.
i want to repeat myself, the touchpad is connected via I2C, and of course VoodooPS2 will do no good.
everything boots, but again, the system does not see the touchpad, which is confirmed by its absence in the settings.

re-verify the ACPI directory, make change if needed based on your configuration.
Also order plugins correctly on config.plist if needed. (Also recheck PS2 or I2C using AIDA64 if possible)

to be honest, i don't know hackintosh at all, and i don't know what changes i need to make based on my configuration.
i've replaced the entire ACPI directory several times with the one I just downloaded from your repository, i haven't changed the order of kexts and plugins in the config.
and i have already attached a screenshot of the current order of plugins and kexts in another post.
about AIDA64, i'll try to download and check it now.
i also want to note that some applications, for example Google Chrome (based on chromium) hangs and crashes, sometimes even kernel panic happens. it is written here that applications based on electron/chromuim are laggy when dragging and dropping.

in my case, they just freeze on startup and crash.

AIDA64 also says that my ELAN touchpad is connected via I2C

(on the screenshot it says 12C - this is probably a typo in google lens translator, the original says I2C)

Sorry, I don't have any solution.
Yes, all electron / chromium based crashes and hangs in my device.

Sorry, I don't have any solution.

thanks anyway, at least for trying to help (≧▽≦)

LOOL. i  just had to remove VoodooI2CELAN and VoodooI2CSynaptics, leaving only VoodooI2C and VoodooI2CHID, and it works!!! with all gestures!!!!

and by the way, i think you know what a hung google chrome looks like, but i'll attach a picture anyway


Success or failure block not call when http status code return 400

I'm using AFNetworking 3.0, I've a function to get JSON from server, everything works fine if I pass true parameters and vice versa server return http status code = 400, at that moment neither success or failure block was called. Below is my function:
func getToken(userName : String, pass : String){
        let urlAPI = UrlApi();
        let requestURL = URL(string: urlAPI.tokenURL());
        let body = NSDictionary(dictionary: ["userId" : userName, "password" : pass]);
        sessionManager = AFHTTPSessionManager();
        sessionManager.requestSerializer.timeoutInterval = 30;//in seconds
        sessionManager.responseSerializer = AFJSONResponseSerializer();
        sessionManager.responseSerializer.acceptableContentTypes = Set<String>(arrayLiteral: "application/json");
        sessionManager.post((requestURL?.absoluteString)!, parameters: body, success: {(task : URLSessionDataTask, response : Any) in
            let resultDic = response as! NSDictionary;
            let temp = resultDic.value(forKey: "message") as? String;
            if temp != nil && temp != "" {
                self.delegate.failGetToken!(errMess: temp!);
            }
            else{
                let defaults = UserDefaults.standard;
                defaults.setValue(pass, forKey: "PASSWORD");
                defaults.synchronize();
                self.delegate.completeGetToken!(token: resultDic.value(forKey: "access_token") as! String);
            }
        }, failure: { (task : URLSessionDataTask, error : Error) in
            self.delegate.failGetToken!(errMess: error.localizedDescription);
            } as? (URLSessionDataTask?, Error) -> Void);
    }

If userName != "baodng" and pass != "0000", the bug will appear.
Thanks in advance with any help!

From this it looks like your AFHTTPSessionManager may be getting deallocated when getToken(userName:pass:) finishes, and before the request finishes. Try keeping a reference to the session manager around until the request finishes.


Installation in Windows

We would like to understand how to register or install the odbccpp.dll file such that it is part of the list in the Drivers tab of the ODBC Data Source Administrato

That way client applications can use a data source name and the driver wrapper to then connect to SQL Server.  The idea is to have the ability to inspect the SQL and potentially optimize it before submitting it to SQL Server for execution
Thanks!

It seems there is a misunderstanding of what the odbc-cpp library is. The odbc-cpp library is just a wrapper of the ODBC API that allows to work with one of the available ODBC drivers (see your image) installed on a given machine. In other words, it is not a driver and any installation (copying to a custom directory) won't list it in the tab mentioned above.

I understand it is just a wrapper that then loads the actual driver. However, we need to make it look like a driver to the operating system so that a client application such as SQL Server management studio can access it by using the DSN..
Get Outlook for iOShttps://aka.ms/o0ukef

From: Maxim Rylov @.>
Sent: Thursday, March 10, 2022 4:30:46 AM
To: SAP/odbc-cpp-wrapper @.>
Cc: carl1121 @.>; Author @.>
Subject: Re: [SAP/odbc-cpp-wrapper] Installation in Windows (Issue #28)
It seems there is a misunderstanding of what the odbc-cpp library is. The odbc-cpp library is just a wrapper of the ODBC API that allows to work with one of the available ODBC drivers (see your image) installed on a given machine. In other words, it is not a driver and any installation (copying to a custom directory) won't list it in the tab mentioned above.
—
Reply to this email directly, view it on GitHubhttps://github.com/SAP/odbc-cpp-wrapper/issues/28#issuecomment-1063846876, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVEFIRPBSMSEPEJBSGM4EL3U7G6MNANCNFSM5QK7DNGQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>

The SQL Server management studio wont' be able to access it in no case, unless you use the wrapper in your C++ implementation of the client application.

Correct, not in it’s current state.  We are thinking of writing another program to use the Microsoft ODBC installer API in order to add the wrapper to the list of drivers.  So that the odbccpp.dll is a driver facade to the underlying SQL Server driver.
We think an installation program is needed per the following
https://docs.microsoft.com/en-us/cpp/mfc/tn048-writing-odbc-setup-and-administration-programs?view=msvc-170
[https://docs.microsoft.com/en-us/media/logos/logo-ms-social.png]https://docs.microsoft.com/en-us/cpp/mfc/tn048-writing-odbc-setup-and-administration-programs?view=msvc-170
TN048: Writing ODBC Setup and Administration Programs for MFC Database Applications | Microsoft Docshttps://docs.microsoft.com/en-us/cpp/mfc/tn048-writing-odbc-setup-and-administration-programs?view=msvc-170
Applications using MFC database classes will need a setup program that installs ODBC components. They may also need an ODBC Administration program that will retrieve information about the available drivers, to specify default drivers and to configure data sources.
docs.microsoft.com
On Mar 10, 2022, at 7:26 AM, Maxim Rylov @.***> wrote:

The SQL Server management studio wont' be able to access it in no case, unless you use the wrapper in your C++ implementation of the client application.
—
Reply to this email directly, view it on GitHubhttps://github.com/SAP/odbc-cpp-wrapper/issues/28#issuecomment-1064001471, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVEFIRLPCGPN4GYV4FVB7SDU7HTANANCNFSM5QK7DNGQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>

Hi carl1121,
This project is a C++ wrapper of the C-based ODBC API. It is not a wrapper of an ODBC driver, so there is no way to register the compiled .dll as an ODBC driver.
If you'd like to develop an ODBC driver wrapper, a good starting point might be an actual ODBC driver. You might have a look at the open-source PostgreSQL ODBC driver (https://git.postgresql.org/gitweb/?p=psqlodbc.git;a=tree) to get an idea how to implement an ODBC driver.
Cheers,
Stefan


Add custom properties to atom-workspace to track editor properties

Description of the Change
Rather than directly setting rules on atom-text-editor, declare several CSS custom properties on the atom-workspace and then reference them in equivalent styling for atom-text-editor. These track the editor's current font size, font family, and line height.
Alternate Designs
Declaring a set of static rules at the same time as the dynamically injected ones feels weird. On the other hand, I attempted to define these statically in text-editor.less and this resulted in inconsistent application when reloading the editor.
Why Should This Be In Core?
Many packages can rely on this without bundling similar functionality for monitoring these changes. Additionally, in core we can use generic names like --editor-font-size without the need for something like a prefix.
Benefits
Many packages are manually monitoring these changes and updating styles directly. This avoids situations like:

atom/github tracking styles
Atom IDE Outline tracking styles

Possible Drawbacks
We may move to custom properties in the long run for theming, and this might commit us to an API we may want to change later. Other than that, none I can think of.
Verification Process
Reload Atom and verify the three text editor properties. Change each at runtime through settings and verify each is reflected.
Applicable Issues

Declaring a set of static rules at the same time as the dynamically injected ones feels weird. On the other hand, I attempted to define these statically in text-editor.less and this resulted in inconsistent application when reloading the editor.

I tried ☝ moving these to text-editor.less and haven't noticed any issues. It might be that text-editor.less gets loaded before the global-text-editor-styles, resulting in showing the default font for a short time?

Should we move the current default to the settings? Otherwise using var(--editor-font-family) will have an empty value.

Awesome ideas. Just incorporated all of them :)

cc @BinaryMuse this should allow you to clean up tracking this state in the GH package 🤩

Is there a reason why only --editor-font-family has been added? Wouldn't it make sense to add CSS properties for all of the LESS variables currently in use? I think the two could co-exist for a considerable time, eventually the LESS variables could be phased out.