bug: @wagmi/cli (React plugin) watchEvent might generate typescript errors

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
1.5.2
Current Behavior
Generate contracts will result in such watchContractEvent functions per contract
export function watchSomeContractEvent<
  TAbi extends readonly unknown[] = typeof someAbi,
  TEventName extends string = string
>(
  config: Omit<WatchContractEventConfig<TAbi, TEventName>, 'abi' | 'address'> & {
    chainId?: keyof typeof someAddress;
  },
  callback: WatchContractEventCallback<TAbi, TEventName>
) {
  return watchContractEvent(
    {
      abi: someAbi,
      address: someAddress[config.chainId as keyof typeof someAddress],
      ...config
    } as WatchContractEventConfig<TAbi, TEventName>,
    callback
  );
}

But this might produce typescript errors while compiling. E.g. integrate the generated data in a package und run tsc --build to publish it. I tried a lot of config mit the result ist always.

Conversion of type {insert someAbi here} may be a mistake because neither type sufficiently overlaps. If this was intentional, convert the expression to 'unknown' first.

The solution would be similar to the other generated methods
export function watchSomeEvent<
  TAbi extends readonly unknown[] = typeof someABI,
  TEventName extends string = string
>(
  config: Omit<WatchContractEventConfig<TAbi, TEventName>, 'abi' | 'address'> & {
    chainId?: keyof typeof oracleAddress;
  },
  callback: WatchContractEventCallback<TAbi, TEventName>
) {
  return watchContractEvent(
    {
      abi: someABI,
      address: someAddress[config.chainId as keyof typeof someAddress],
      ...config
    } as unknown as WatchContractEventConfig<TAbi, TEventName>,
    callback
  );
}

So just add the as unknown as WatchContra like it is done in other generated methods.
Expected Behavior
No compile errors
Steps To Reproduce

Create a Typescript project.
Generate some contracts in it
Run tsc --build

Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)
No response
Anything else?
No response

What version of TypeScript are you using? Please attach a minimal reproduction. Issue will be re-opened once that is provided.

Stumbled upon this today myself.
It's rather related to the actions plugin
created a quick repro:
https://stackblitz.com/edit/stackblitz-starters-vt97ap?file=src%2Fgenerated.ts


kodi: plugins cleanup

Motivation for this change

kodiPlugins holds more than just plugins for kodi... it also holds addons (which is a superset of plugins) and packages (like kodi-platform), so rename accordingly.
rename kodiPlugins.kodiWithPlugins to be more consistent with the rest of nixpkgs, and additionally fix so plugins (packages) work properly with other variants of kodi (like kodi-wayland).
get rid of config.kodi.* options as this was confusing and undocumented, replace with simpler kodi.withPackages mechanism which should be familiar to many users of nix

Example usage:
environment.systemPackages = with pkgs; [
  (kodi.withPackages (p: with p; [ inputstream-adaptive vfs-sftp ]))
];

WHY? As I mentioned in https://github.com/NixOS/nixpkgs/pull/115355 I would like to start including more addons for kodi in our repositories so I can have a more declarative kodi. This PR starts to cleanup the addon (plugin) situation for kodi.
TODO:

[x] Release notes.

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Thanks for the review @SuperSandro2000!

Release notes added, ready for merge!

Thanks @minijackson!


Custom pull descriptions

Adds a new input configuration option: pull_description.
The value is used as template for the description of pull requests created by this action.
Placeholders can be used to define variable values.
These are indicated by a dollar sign and curly braces (${placeholder}).
The action.yml and example workflows simply refer to the README for all available placeholders.
The README contains a new subsection (Placeholders) under Installation, to specify the available placeholders and what they are replaced with.
closes #51

Thanks @korthout! I sadly probably won't get a chance to test this out in until at least next week, but the implementation looks like exactly what I'd like.

@negz That's great to hear. I was planning on doing some additional testing today and then merging it, so I'm happy to hear you're positive about the config. Personally, I feel this feature also opens up the possibility to add more placeholders (e.g. related issues, something my team wants) without changing the current behavior for other users. So I believe this adds a lot of value. Thanks again for bringing up this idea.

I've tested it, and all works as expected: default + documented example.
You can also escape the hash character # with a backslash, like \# to please the GitHub yml editor. This does add the backslash to the actual description, but GitHub then simply ignores it when rendering the description. Personally, I prefer not escaping them.
I did note one small problem. Each placeholder can only occur once in the description. Only the first is replaced, the others are not. It's not really a bug, just the current behavior. Let's see if someone needs this at any point.


Punkt does not compile with Stack

While installing with Stack I get the following error:
Configuring punkt-0.1.1...
Building punkt-0.1.1...
Preprocessing library punkt-0.1.1...
[1 of 2] Compiling NLP.Punkt.Match  ( lib/NLP/Punkt/Match.hs, .stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS>/build/NLP/Punkt/Match.o )

lib/NLP/Punkt/Match.hs:24:5:
    Non type-variable argument
      in the constraint: regex-base-0.93.2:Text.Regex.Base.RegexLike.RegexLike
                           Regex b
    (Use FlexibleContexts to permit this)
    When checking that ‘chunk’ has the inferred type
      chunk :: forall b.
               regex-base-0.93.2:Text.Regex.Base.RegexLike.RegexLike Regex b =>
               Regex -> b -> [Either b b]
    In an equation for ‘re_split_impl’:
        re_split_impl re str
          = filter not_blank $ chunk re str
          where
              not_blank xs
                = if xs == Left "" || xs == Right "" then False else True
              chunk re str = maybe [Left str] link $ matchOnceText re str
              link (pre, match, post)
                = Left pre : Right (fst $ match ! 0) : chunk re post

I couldn't try it, but maybe it's just a matter of adding the suggested extension, FlexibleContexts.

Thanks for reporting!
I've created a branch, issue-001 that tentatively fixes this. All it does is
include an explicit type signature for chunk. Just to get you going:
$ git checkout https://github.com/bryant/punkt -b issue-001 punkt-001
$ cd punkt-001
$ ... #juststackthings

This looks like a conflict with the type checker and isn't specific to stack.
GHC (from 7.10.1 onwards) tries to infer a polymorphic type for the second
parameter (str) of re_split_impl.chunk despite the constraint from the top
level signature that str unifies with Text.
I've requested for clarification on #ghc, but won't be pushing to master until
this is cleared up.

Thanks for explaining the issue! I'll happily wait for clarification, I'm learning Haskell myself.

I got the. same error using cabal:
cabal sandbox init
cabal install punkt
...

But how to use the new branch in this setup? Do we have any way to say to cabal to use a branch of the punkt repository?


context: utilize new AfterFunc to avoid unneeded goroutines

This should be functionally identical but doesn't waste a goroutine and
is simpler

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
3caa9e2523e404504b7c30f6cde88fef187668c1
link
true
/test unit-tests-arm64

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


Add an option to change the port to reach the server

A option to change the TCP port used for control connections with the server from the default 7835 value could be useful.
Thanks.

Duplicate of #48.


Add container store tests

Reviewer:  @GioSensation
Asana: https://app.asana.com/0/0/1202105131841960/f
Description
Add tests for the container store
Steps to test

It wasn't actually, added now.
(Although the field scoring for the contact form is correct, the issue is just that we don't detect it's hidden).


Change Column to ListView

This optimization will prevent UI lag when no. of items list becomes very large

The second fix is part of the block that's run when scroll is set to false. How about when the user nests the widget with this fix now been a scrollable in another scrollable which will result in a rendering issue. Perhaps adding shrinkWrap will work.

The second fix is part of the block that's run when scroll is set to false. How about when the user nests the widget with this fix now been a scrollable in another scrollable which will result in a rendering issue. Perhaps adding shrinkWrap will work.


chore: add serde feature to network crate

This PR adds a serde feature to the network crate, along with serde support for PeersConfig, as mentioned in https://github.com/paradigmxyz/reth/pull/569. It also replaces the PeersConfig in bin/reth to avoid duping.

Codecov Report

Merging #653 (9859277) into main (c62574b) will increase coverage by 0.07%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #653      +/-   ##
==========================================
+ Coverage   72.11%   72.18%   +0.07%
==========================================
  Files         260      260
  Lines       26315    26317       +2
==========================================
+ Hits        18976    18998      +22
+ Misses       7339     7319      -20

Flag
Coverage Δ

unit-tests
72.18% <0.00%> (+0.07%)
:arrow_up:

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

Impacted Files
Coverage Δ

bin/reth/src/config.rs
0.00% <ø> (ø)

crates/net/network/src/lib.rs
100.00% <ø> (ø)

crates/net/network/src/peers/manager.rs
80.77% <0.00%> (-0.19%)
:arrow_down:

crates/net/network/src/peers/reputation.rs
63.15% <0.00%> (-1.71%)
:arrow_down:

crates/transaction-pool/src/pool/txpool.rs
58.21% <0.00%> (+0.51%)
:arrow_up:

crates/transaction-pool/src/test_util/mock.rs
60.37% <0.00%> (+6.66%)
:arrow_up:

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


Ready for release with assessment2 deliverables

Dear team. Please pull and carefully evaluate the development branch since there are a multitude of changes. Once we are all okay with the changes, it will be merged with the master branch.

I've re-run the reports and everything looks good. I've verified the file changes/commits and haven't noticed any issues. I'm okay with the changes and approve of this pull request.

Will do the merge later today. Thanks for the feedback.


classes/npm: allow NPM_ARCH=foo oe_runnpm to work

Not sure if : ${FOO:=bar} is a bash-ism. If it is, there is probably an alternate way to achieve the same thing.

Just noticed that this doesn't handle the CXX usage, which I'd also need to adjust.

Yes missed that one.
I'm thinking about npm-native.bbclass with its own NPM_NATIVE_ARCH, NPM_NATIVE_CXX and oe_runnpm_native. Maybe that would be the most correct and "OE" way of doing this while avoiding bashism etc.
Baking native and target versions to same bbclass ( just like in #7 ) is always possibility but it does not feel as elegant to me.

... and I might be wrong and solution in PR #7 is actually the right one (with some improvements) ;)
This is tricky.

@jmesmon feedback appreciated :)
There can be common function for some inits just like in #7 but I wanted to keep things clear and simple and separate cleanly target and native functions and their variables. Here flags, ld, arch, cache dir, npm binary are configurable for target and native independently.
Also, this does not break compatibility with earlier versions in any way.
DEPENDS += " virtual/node-native"

RDEPENDS_${PN} += " node"

PACKAGE_DEBUG_SPLIT_STYLE = "debug-file-directory"

CCACHE = ""

NPM ?= "npm"
NPM_CACHE_DIR = "${WORKDIR}/npm_cache"
NPM_ARCH ?= "${TARGET_ARCH}"
NPM_LD ?= "${CXX}"
NPM_FLAGS ?= ""

# Target npm

oe_runnpm() {

	export NPM_CONFIG_CACHE="${NPM_CACHE_DIR}"

	[ -n "${http_proxy}" ] && export NPM_CONFIG_PROXY="${http_proxy}"
	[ -n "${https_proxy}" ] && export NPM_CONFIG_HTTPS_PROXY="${https_proxy}"
	[ -n "${HTTP_PROXY}" ] && export NPM_CONFIG_PROXY="${HTTP_PROXY}"
	[ -n "${HTTPS_PROXY}" ] && export NPM_CONFIG_HTTPS_PROXY="${HTTPS_PROXY}"

	bbnote NPM target architecture: ${NPM_ARCH}
	bbnote NPM cache directory: ${NPM_CONFIG_CACHE}
	bbnote NPM HTTP proxy: ${NPM_CONFIG_PROXY}
	bbnote NPM HTTPS proxy: ${NPM_CONFIG_HTTPS_PROXY}

	bbnote ${NPM} --arch=${NPM_ARCH} --target_arch=${NPM_ARCH} ${NPM_FLAGS} "$@"

	LD="${NPM_LD}" ${NPM} --arch=${NPM_ARCH} --target_arch=${NPM_ARCH} ${NPM_FLAGS} "$@" || die "oe_runnpm failed"

}

# Native npm

NPM_NATIVE ?= "npm"
NPM_CACHE_DIR_NATIVE = "${WORKDIR}/npm_cache"
NPM_ARCH_NATIVE ?= "${BUILD_ARCH}"
NPM_LD_NATIVE ?= "${BUILD_CXX}"
NPM_FLAGS_NATIVE ?= ""

oe_runnpm_native() {

	export NPM_CONFIG_CACHE="${NPM_CACHE_DIR_NATIVE}"

	[ -n "${http_proxy}" ] && export NPM_CONFIG_PROXY="${http_proxy}"
	[ -n "${https_proxy}" ] && export NPM_CONFIG_HTTPS_PROXY="${https_proxy}"
	[ -n "${HTTP_PROXY}" ] && export NPM_CONFIG_PROXY="${HTTP_PROXY}"
	[ -n "${HTTPS_PROXY}" ] && export NPM_CONFIG_HTTPS_PROXY="${HTTPS_PROXY}"

	bbnote NPM native architecture: ${NPM_ARCH_NATIVE}
	bbnote NPM cache directory: ${NPM_CONFIG_CACHE}
	bbnote NPM HTTP proxy: ${NPM_CONFIG_PROXY}
	bbnote NPM HTTPS proxy: ${NPM_CONFIG_HTTPS_PROXY}

	bbnote ${NPM_NATIVE} --arch=${NPM_ARCH_NATIVE} --target_arch=${NPM_ARCH_NATIVE} ${NPM_FLAGS_NATIVE} "$@"

	LD="${NPM_LD_NATIVE}" ${NPM_NATIVE} --arch=${NPM_ARCH_NATIVE} --target_arch=${NPM_ARCH_NATIVE} ${NPM_FLAGS_NATIVE} "$@" || die "oe_runnpm_native failed"

}

Looks OK to me (of course, so did the other ones until I stared at them for a bit longer :)

Ok. I'm going to commit that one and close this PR.
I personally do not have a a real-world scenario for using the _native variant so, please open a new PR or plain issue if you feel this needs further improvement :)
Thanks again for your valuable contribution.


Fix #61

Issue was the unquoted use of %.>% in pkgdown's reference list. We should either quote it or, in this case, remove it as it does not make sense in the Package global state section.
Thank you for your Pull Request! We have developed this task checklist from the
Development Process
Guide
to help with the final steps of the process. Completing the below tasks helps to
ensure our reviewers can maximize their time on your code as well as making sure
the oak codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task
or check off that it is not relevant to your Pull Request. This checklist is
part of the Github Action workflows and the Pull Request will not be merged into
the devel branch until you have checked off each task.

[x] Place Closes #<insert_issue_number> into the beginning of your Pull z
Request Title (Use Edit button in top-right if you need to update)
[x] Code is formatted according to the
tidyverse style guide. Run
styler::style_file() to style R and Rmd files
[x] Updated relevant unit tests or have written new unit tests, which should
consider realistic data scenarios and edge cases, e.g. empty datasets, errors,
boundary cases etc. - See
Unit Test Guide
[x] If you removed/replaced any function and/or function parameters, did you
fully follow the
deprecation guidance?
[x] Update to all relevant roxygen headers and examples, including keywords
and families. Refer to the
categorization of functions to tag appropriate keyword/family.
[x] Run devtools::document() so all .Rd files in the man folder and the
NAMESPACE file in the project root are updated appropriately
[x] Address any updates needed for vignettes and/or templates
[x] Update NEWS.md if the changes pertain to a user-facing function (i.e. it
has an @export tag) or documentation aimed at users (rather than developers)
[x] Build oak site pkgdown::build_site() and check that all affected
examples are displayed correctly and that all new functions occur on the "Reference" page.
[x] Address or fix all lintr warnings and errors - lintr::lint_package()
[x] Run R CMD check locally and address all errors and warnings - devtools::check()
[x] Link the issue in the Development Section on the right hand side.
[x] Address all merge conflicts and resolve appropriately
[x] Pat yourself on the back for a job well done! Much love to your accomplishment!

@ramiromagno  pkgdown::build_site() is giving an error. We may have to remove the %.>% from L59 in the yml file.

That is what my PR does, indeed.
On Thu, 20 Jun 2024, 19:46 Ram Ganapathy, @.***> wrote:

@ramiromagno https://github.com/ramiromagno pkgdown::build_site() is
giving an error. We may have to remove the %.>% from L59 in the yml file.
—
Reply to this email directly, view it on GitHub
https://github.com/pharmaverse/sdtm.oak/pull/62#issuecomment-2181316673,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEXRG4CWK54JUE3V6FL2CNDZIMPOVAVCNFSM6AAAAABJUPKVVGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBRGMYTMNRXGM
.
You are receiving this because you were mentioned.Message ID:
@.***>


omg this is soooooooo cute what the heck

and actually so accurate there's no issue I just wanted to give you props HAHA
ty and gl hehe

We really liked it too. So cute.


Updating path to runit in Dockerfile

Runit no longer appears to be in testing. When attempting to build the dockerfile on Ubuntu 16.04 and OSX 10.11, I received the following error:
# docker build -t doorman .
Sending build context to Docker daemon 1.838 MB
Step 1 : FROM alpine:latest
 ---> 7d23b3ca3463
Step 2 : RUN apk update
 ---> Running in 2752fc94a38c
fetch http://dl-cdn.alpinelinux.org/alpine/v3.4/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.4/community/x86_64/APKINDEX.tar.gz
v3.4.3-66-gc73e68d [http://dl-cdn.alpinelinux.org/alpine/v3.4/main]
v3.4.3-62-gaaf1b40 [http://dl-cdn.alpinelinux.org/alpine/v3.4/community]
OK: 5968 distinct packages available
 ---> e004eba74087
Removing intermediate container 2752fc94a38c
Step 3 : RUN echo "@testing http://dl-4.alpinelinux.org/alpine/edge/testing" >> /etc/apk/repositories   && apk add --update               bash               build-base               git               libffi-dev               musl               nodejs               postgresql-dev               py-pip               python               python-dev               redis               runit@testing   && pip install --upgrade pip   && npm install -g bower less   && rm /var/cache/apk/*
 ---> Running in fe4e8398c569
fetch http://dl-cdn.alpinelinux.org/alpine/v3.4/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.4/community/x86_64/APKINDEX.tar.gz
fetch http://dl-4.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz
ERROR: unsatisfiable constraints:
  runit (missing):
    required by: world[runit]
The command '/bin/sh -c echo "@testing http://dl-4.alpinelinux.org/alpine/edge/testing" >> /etc/apk/repositories   && apk add --update               bash               build-base               git               libffi-dev               musl               nodejs               postgresql-dev               py-pip               python               python-dev               redis               runit@testing   && pip install --upgrade pip   && npm install -g bower less   && rm /var/cache/apk/*' returned a non-zero code: 1

Updating the path to the APK repos fixed this issue on both operating systems and the Dockerfile then was able to build successfully.

Thanks @Centurion89!


Parser optimization

Restructured both the AST and node builders to increase their performance by moving away from the builder pattern. This degrades code quality a bit (because the classes are quite big), but I think performance is most important when it comes to parsing. Besides I like the new NodeBuilder more than the 30 something builder classes we used to have.

Pull Request Test Coverage Report for Build 1206

827 of 845 (97.87%) changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 89.093%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Language/NodeBuilder.php
288
290
99.31%

src/Language/ASTBuilder.php
527
543
97.05%

Totals

Change from base Build 1195:
-0.01%

Covered Lines:
5146

Relevant Lines:
5776

💛  - Coveralls

Pull Request Test Coverage Report for Build 1206

827 of 845 (97.87%) changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 89.093%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Language/NodeBuilder.php
288
290
99.31%

src/Language/ASTBuilder.php
527
543
97.05%

Totals

Change from base Build 1195:
-0.01%

Covered Lines:
5146

Relevant Lines:
5776

💛  - Coveralls

I'm going to merge this because it's green.


Transition from on-rails to orbital camera mode.

[x] Define a way to make (invisible) clickable bounding boxes.
[x] Make clickable (invisible) bounding boxes for all sites (footprints).
[x] On-click: make the camera center transition to this site, and go into orbital mode.
[x] Define some way to exit the orbital mode (keypress / on screen button)
[ ] Optionally: Make the transition smooth.

We have not implemented smooth transition back to the drivemap, but I'm closing this issue nonetheless, since this is a very minor improvement.


latest version: in admin mode,  The term 'Requires' is not recognized as the name of a cmdlet, function, script file, or operable program

 The term 'Requires' is not recognized as the name of a cmdlet, function, script file, or operable program

some lines ps scipts. fixed!


Make research about hyperlinking action items.

Can anybody clarify that if we can hyperlink the action items and make them checkbox? @SWE574-Fall2023-Group1/all

Hyperlinking can be handled through markdown, closing.


Improve Canadian holidays

Fixes #535. Adds or corrects missing holiday descriptions in English and French in addition to updates to the Holiday definition file for Canada.

Thanks @kmcbride3 for this great update. I just looked into it and added some comments.

Thanks @kmcbride3 for this great update. I just looked into it and added some comments.

I appreciate you taking the time to review and add the comments. I've made the corrections for NB and SK's Civic holidays and responded about Victoria Day, Thanksgiving Day, and Boxing Day in NB - they're a bit of a grey area (to me, at least) as "prescribed days of rest", but I have no issues removing them if we want to stick exclusively with paid holidays.


ratsnest is wrong！

In kicad5.99, the ratsnest is not updated after running the plug-in！
The file must be saved and the ratsnest will not update correctly until the pcbnew is restarted.

@lvsoft
Application: KiCad PCB 编辑器 (64-bit)
Version: (5.99.0-12597-g9f841da98e), release build
Libraries:
wxWidgets 3.1.5
libcurl/7.78.0-DEV Schannel zlib/1.2.11
Platform: Windows 10 (build 19043), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
Date: Sep 28 2021 00:32:52
wxWidgets: 3.1.5 (wchar_t,wx containers)
Boost: 1.76.0
OCC: 7.5.0
Curl: 7.78.0-DEV
ngspice: 35
Compiler: Visual C++ 1929 without C++ ABI
Build settings:
KICAD_USE_OCC=ON
KICAD_SPICE=ON

Added this and solved it.
pcbnew.Refresh()

this was true for me as well, thank you for the fix!

Fixed by #8 from @HaydenHu


Error Broken Pipe

Good afternoon,
First of all thank you to the project, it's been very useful for our structure, great work.
I would like to ask for help with a slightly unusual situation, as we realize that sometimes we are encountering the following errors in the milter:
warning: milter inet: <IP_ADDRESS>: 3690: error writing command: broken pipe
With this we had to change the milter_default_action setting to accept because before the messages were following the default and generating error 4xx causing delay in receiving.
Do you know what may be causing this? Is it something related to the load / excess of messages?
I await contact.
Kind regards.

Hey, what version do you use? You can find the version number in the first log entry.

Good evening,
Thanks for the quick feedback, we are currently using the latest version, we have just implemented this new check in our email queues.
Kind regards.

Good night,
Another important detail I found in the logs, this mainly happens with messages received from office365 and gsuite.
Kind regards.

Can you please set the log level to debug in the config and restart the milter?
Are there any errors or exceptions logged while receiving the message? Can you reproduce the error? Are there any attachments within the mail?
Thank you for your support! 😉

Not sure if our issue is related we are using 3.4.3-1 through a yum install.
Using unix sockets we will start seeing this error in our smtp logs:
Milter (macromilter): write(Q) returned -1, expected 5: Broken pipe
Milter (macromilter): to error state
Not seeing anything in the macromilter logs, the process seems to be running fine and the .sock exists.  It only seems to be doing it for random emails not every single email.


Fix 'The code must not contain multiple blank lines in a row.' issue in LearnFiles\Basics\Strings.cs

CodeFactor found an issue: The code must not contain multiple blank lines in a row.
It's currently on:
LearnFiles\Basics\Strings.cs:29

Issue Resolved, no major change to code, just stylising errors.


Not opening in IE Mode

I followed the instructions here but the browser stopped opening in IE mode.  I think edge may have had an update locking IE down more because it worked as recently as last week.
I can right click the tab and refresh in IE mode and the browser resumes as intended, but that defeats the purpose of the automation.

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

ID: de9fa537-f960-f6f9-a39f-5ea14b41f01f
Version Independent ID: de9fa537-f960-f6f9-a39f-5ea14b41f01f
Content: Use Internet Explorer Driver to automate IE mode in Microsoft Edge - Microsoft Edge Development
Content Source: microsoft-edge/webdriver-chromium/ie-mode.md
Product: microsoft-edge
Technology: devtools
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

Hi @Hoffman-Rihm. Thanks for reaching out. This sounds more like an Edge/IE-mode automation bug than a documentation issue. Could you please post your issue on this feedback/discussion repository instead: https://github.com/MicrosoftEdge/EdgeWebDriver/issues ?
You will have more chances of getting a resolution to your problem over there. Thanks for your understanding. I hope you can find a solution to this soon.

Thanks you @captainbrosset! Actually I had an outdated WebDriver in the directory overriding the updated one in PATH.  I deleted the old one and now it is working.  Sorry, my error, no bug, all is well.

Oh that's even better! Glad you figured it out.


Add "Inline variable" refactoring

VSCode offers several "Extract to constant" refactorings that move a literal value into a constant. I often need the reverse operation: inlining a value that is currently defined in a constant.
Here are some examples.
// Before:
function add(a: number, b: number) {
  const result = a + b;
  return result;
}

// After inlining `result`:
function add(a: number, b: number) {
  return a + b;
}

// Before:
const message = 'Processing successful.';
console.log(message);

// After inlining `message`:
console.log('Processing successful.');

For reference, here is the documentation of that feature in ReSharper.

Please file a request on TypeScript: https://github.com/microsoft/TypeScript/

@JacksonKearl Thank you for your fast reply! I'm a bit confused, though. It is my understanding that the code for "Extract to constant" is part of this repository, not TypeScript. Am I missing something?

Duplicate of https://github.com/microsoft/TypeScript/issues/18459


cmd/gofmt: strange indentation in slice literal

As shown in playground https://play.golang.org/p/QpLaytT2yia, the following code has strange indent, that depends on the order of the elements.
package main

var a = []string{
	"xxxxxxxxxxxxxxxxxxxxx", // comment
	"xxxxx",                 // comment
	"x",                     // comment
}

var b = []string{
	"xxxxxxxxxxxxxxxxxxxxx", // comment
	"x",     // comment
	"xxxxx", // comment
}

func main() {}

That's intentional. See previous bugs on this topic. This is a frequent duplicate. The main duplicate is #10392.

First rule of gofmt: don't worry about gofmt's choices.

I wonder if this warrants a gofmt FAQ.

If we did, it should be of the form:

Q: gofmt did something unexpected!
A: Don't worry about it. Keep writing code.

:)


RVIZ crashes on load with segmentation fault (core dumped)

Hey. I'm trying to run a SLAM Robot including rplidar_ros and hector_slam as a ROS project inside a docker container. The installation should be correct and for example the launch of the lidar is working (launched as roslaunch rplidar_ros rplidar_a3.launch).
That makes me think, that the docker is set up correctly. However, when I try to launch a node which uses rviz, rviz is crashing.
So if I launch the file like this: roslaunch rplidar_ros view_rplidar_a3.launch the error looks like that:
process[rplidarNode-1]: started with pid [547]
[ INFO] [1642155667.631433022]: RPLIDAR running on ROS package rplidar_ros. SDK Version:1.9.0
process[rviz-2]: started with pid [553]
qt.qpa.xcb: failed to initialize XRandr
qt.qpa.xcb: X server does not support XInput 2
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
RPLIDAR S/N: DB8D9A87C5E392D2A5E492F84B58316C
[ INFO] [1642155668.144757265]: Firmware Ver: 1.27
[ INFO] [1642155668.144890910]: Hardware Rev: 6
[ INFO] [1642155668.147313544]: RPLidar health status : 0
qt.qpa.xcb: QXcbConnection: XCB error: 1 (BadRequest), sequence: 168, resource id: 53, major code: 131 (Unknown), minor code: 47
[ INFO] [1642155668.795137417]: current scan mode: Sensitivity, max_distance: 25.0 m, Point number: 15.9K , angle_compensate: 4
[rviz-2] process has died [pid 553, exit code -11, cmd /opt/ros/noetic/lib/rviz/rviz -d /schwarmroboter_ws/src/rplidar_ros/rviz/rplidar.rviz __name:=rviz __log:=/root/.ros/log/44a83bc6-7521-11ec-89d0-0242ac110002/rviz-2.log].
log file: /root/.ros/log/44a83bc6-7521-11ec-89d0-0242ac110002/rviz-2*.log

So first I thought it's an issue with the qt and xserver, but other graphical applications work. I did a lot of research to find the issue and saw a recommendation to run rviz normally. So the next thing I did was run rviz like this: rosrun rviz rviz.
This proceeds in the following error:
root@1b02a0358157:/schwarmroboter_ws# rosrun rviz rviz
qt.qpa.xcb: failed to initialize XRandr
qt.qpa.xcb: X server does not support XInput 2
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
[ INFO] [1642155951.722014067]: rviz version 1.14.11
[ INFO] [1642155951.722219222]: compiled against Qt version 5.12.8
[ INFO] [1642155951.722283544]: compiled against OGRE version 1.9.0 (Ghadamon)
[ INFO] [1642155951.773808847]: Forcing OpenGl version 0.
qt.qpa.xcb: QXcbConnection: XCB error: 1 (BadRequest), sequence: 168, resource id: 53, major code: 131 (Unknown), minor code: 47
Segmentation fault (core dumped)

Your environment
Using this Docker Image: https://hub.docker.com/layers/ros/library/ros/noetic-ros-core-focal/images/sha256-f14979b3e99f29bf1433552bfd1a3b683b87660395033f7902fcee9aa638f885?context=explore

RViz, Qt, OGRE, OpenGl version as printed by rviz:

[ INFO] [1642155951.722014067]: rviz version 1.14.11
[ INFO] [1642155951.722219222]: compiled against Qt version 5.12.8
[ INFO] [1642155951.722283544]: compiled against OGRE version 1.9.0 (Ghadamon)
[ INFO] [1642155951.773808847]: Forcing OpenGl version 0.

Help would be wonderfull.

rviz in docker works w/o problems for me. I guess you followed the general instructions here?
In general, this question should be better asked at https://answers.ros.org. Please, post real issues and bug reports here only.


Unable to register GoogleGroupPartRepository

Now, when a GoogleGroupPartRepository is registered in a bounded context, the following exception is thrown:
java.lang.IllegalStateException: Aggregates of the repository io.spine.users.google.c.group.GoogleGroupPartRepository neither handle commands nor react on events.
The aggregate part only imports events. Probably, the design of the part should be changed.

It's probably the bug in the repository registration code. If a repo only imports events, that's probably OK. It's not a usual case, but not necessarily a design flaw.

An aggregate, which only imports events looks like a projection. What's the reason to keep it as an aggregate instead of turning into a projection?
In this particular case, GoogleGroupPart applies external events related to a Google Group and mirrors the data about a Google Group in its state. Again, looks like it should be a projection.


Can't sendMessage (sendPhoto,...) to reply a specific message from other bot in supergroups

According to the Telegram Bot API document, methods like sendMessage, sendPhoto, etc., contain a parameter reply_parameters to describe the message to reply to. In this parameter, there is a field called message_id, which is the ID of the message that needs to be replied to.
When I use the Bot API to call these methods in a supergroup, the bot can only reply to messages sent by that bot itself or by users; it cannot reply to messages sent by other bots. In that case, the API responds with the error Bad Request: message to be replied not found.
Specifically, if the supergroup has 3 members: U1 (user), B1 (bot), and B2 (bot):

U1 sends a message -> B1 can reply, B2 can reply.
B1 sends a message -> B1 can reply, B2 cannot reply.
B2 sends a message -> B1 cannot reply, B2 can reply.

Is there a bug in these APIs, or have I passed an incorrect/missing parameter?
Steps to reproduce

Create a supergroup.
Add at least two bots to group, make sure that it have Send Messages permission.
From Bot1, send a message, e.g. message_id = 1
From Bot2, send other message to reply message_id=1 (reply_parameters={"message_id":1})
API response error code 400 with error message Bad Request: message to be replied not found.

Bots have no access to messages of other bots, and therefore can't reply them.


Fix Clippy warning

✓ Checklist:

[ ] This PR has been added to CHANGELOG.md (at the top of the list).

Codecov Report

Merging #169 (13e3612) into main (70506ae) will decrease coverage by 0.09%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #169      +/-   ##
==========================================
- Coverage   86.57%   86.48%   -0.10%
==========================================
  Files          54       54
  Lines        3613     3617       +4
==========================================
  Hits         3128     3128
- Misses        485      489       +4

Impacted Files
Coverage Δ

...nymizer_engine/src/transformers/datetime/format.rs
91.86% <0.00%> (-0.89%)
:arrow_down:

...atanymizer_engine/src/transformers/datetime/mod.rs
77.10% <0.00%> (-1.91%)
:arrow_down:

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 70506ae...13e3612. Read the comment docs.


Duplicates Not Handled Correctly

if you have more then one version of a film or tv show and select play which version, no matter which you select it seems to only play the highest resolution available

even if i select 720p it still plays the 1080p file

I can confirm this is broken. Unfortunately, it seems there is nothing in the request I get from Plex that would allow me to handle this. It sends me a request to fetch a play queue, and the queues for selections for different versions and the requests to play them are identical.


README: Use SVG badge icon

This is a trivial PR: avoid using PNG when there are SVG badge icons.

Thanks!


"createSubscriptionResolver" should  be allowed to be overridden with a custom resolver as happens with "createResolver" function

I'm working on a project with a multi-tenant micro-services architecture. I have a Main_GraphQL server which imports schemas from other GraphQL services using introspectSchema  and makeRemoteExecutableSchema.
Let's assume that tenant1 wants to import schema  from GraphQL_Service_1 and tenant2 from GraphQL_Service_2. The tricky thing is that both services have actually the same schema but the resolvers are different.
So what i need is when i get the call from tenant1 to run the resolvers from GraphQL_Service_1 and when i get a call from tenant2 to run the resolvers from GraphQL_Service_2.
I managed to achieve this for Query and Mutations by passing a customCreateResolver  to makeRemoteExecutableSchema.
The problem is that makeRemoteExecutableSchema doesn’t use the customCreateResolver function when creating the resolvers for subscriptions but it uses the default one.
Is it possible to allow overriding the subscription resolvers with a custom one as it happens now with the ones for Query and Mutation?
Thank you! I really need this.

In v5 makeRemoteExecutableSchema is deprecated in favor of wrapSchema which acts like transformSchema++, you can specify remote schema options and transforms. Missing piece is to pass a function to provide your own delegating resolver, just requires an additional argument. That would work for queries, mutations, subscriptions.
Folding into #1306

I'll be waiting for the custom delegating resolver parameter to come up then. Thank you. :)

Moving to v5.1, reopening to move any relevant discussion here.

Moved back into v5.0, track #1308
Thank you for pushing on this.

Moved back into v5.0, track #1308
Thank you for pushing on this.

That's realy great! Thank you!!


Update mr-dev-days.md

Docs Build status updates of commit 5b62fa3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/mr-dev-days.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


fix link

The old link not useful, so fix to a new.

Could you sign the CLA?

@Sn0rt could you sign the CLA so we can merge this?

No activity, closing.


Error: unrecognized cop or department RSpecRails/HttpStatus found in config/default.yml Did you mean RSpecRails/HaveHttpStatus?

I am getting this error, today suddenly my CI stopped working, as my Gemfile.lock is not part of the gem and it installs the latest available gems.
Error: unrecognized cop or department RSpecRails/HttpStatus found in /Users/ismail/.rvm/gems/ruby-3.3.0/gems/rubocop-rspec_rails-2.28.1/config/default.yml
Did you mean RSpecRails/HaveHttpStatus?
Any idea about it?

Seeing similar issue (using rubocop-rspec 2.28.0 and rubocop-rspec_rails 2.28.1). The release notes claim:

the cops related to rspec-rails are aliased (RSpec/Rails/Foo == RSpecRails/Foo) until v3.0 is released, so the change will be invisible to users until then

I wonder if the aliasing was not included in the release ... or a decision was made to not do the aliasing and the release notes are wrong?

It looks like this is an issue because RSpecRails/HaveHttpStatus is conditionally loaded, and do not exist if rack is not installed: https://github.com/rubocop/rubocop-rspec_rails/blob/b141576cf6fb1f75bb3e446b96d4c4f8266cc161/lib/rubocop/cop/rspec_rails_cops.rb#L6-L10
begin
  require_relative 'rspec_rails/http_status'
rescue LoadError
  # RSpecRails/HttpStatus cannot be loaded if rack/utils is unavailable.
end

@rubyonrails3 @mjankowski @ntkme Thank you for your reporting. I have created a PR for the fix below. Does the following solve it?

https://github.com/rubocop/rubocop-rspec/pull/1849

@ydah I think rack might be add as a dependency for rubocop-rspec_rails, but not rubocop-rspec. I don't use rails in my repo thus I don't think rack is needed for me.

@ydah  yes it does fix the issue for me. just tried this gem "rubocop-rspec", github: "rubocop/rubocop-rspec", ref: "198db78eef099ad605705ebce038ad3ba71ad6ef" and everything worked fine


"Plugin failed to decode" with nushell 0.90.1

Hi!
This plugin unfortunately does not work with the current nushell:
~> notify -t "test notification body" --summary "test title"
Error:   × Plugin failed to decode
  help: array had incorrect length, expected 3

Have you tried updating the plugin?

It’s the latest from crates.io.

They are updated now.
But since I don't update my crates often, the recommended approach would be to clone the repository and build the plugin from the source code. You can also consider using nupm to install plugins, especially those that require build time configuration. (for example clipboard plugin has custom nupm install script)


feat: add integer validation

fixes #1

:tada: This PR is included in version 1.1.0 :tada:
The release is available on:

GitHub release
1.1.0
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Adding new /embed api that accepts a list as input. Closes #7

@lebrunel Sorry the delay in answering. I was able to make a simple LiveBook to test the new /embed endpoint and it worked. As I mentioned, ( #7 ) I was not able to write the proper test to it.

Apologies @tubedude I was working on adding this literally just now! 😛 see d38f791
New release imminent!


nixos/transmission: fix AppArmor profile to include keyutils

Motivation for this change
Otherwise the transmission service fails to start in NixOS 18.03 when AppArmor is enabled (at least, under my configuration).
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Fits CONTRIBUTING.md.

So this needs also a backport? I am not a fan of maintaining this apparmor profile because it is likely to break whenever downstream dependency changes. I would actually suggest to remove it.

If it's about all libraries used, that's possible to extract e.g. from ldd $out/bin/.transmission-daemon-wrapped, right?


build error: target '@com_google_mediapipe//mediapipe:emscripten' is not visible from target '@com_google_mediapipe//mediapipe/calculators/tensor:compute_shader_unavailable'

System information

OS Platform and Distribution (e.g., Linux Ubuntu 20.04, WSL2): win11 docker (wsl2:ubuntu18.04)
Target (e.g. desktop cpu, android arm64): android arm64
Bazel version:
Python version:
GCC/G++ version:
Unity version:
Android NDK version (if building for Android):

Describe the problem
Hi homuler, I meet  a build error when I do python build.py build --android arm64 -vv.
I just followed your wiki Docker Linux Container part step by step. What should I do?
Full logs
[mediapipe@5b65ba016545 ~]$ python build.py build --android arm64 -vv
INFO (build.py): Building protobuf sources...
DEBUG (build.py): Running `bazel build -c opt --verbose_failures //mediapipe_api:mediapipe_proto_srcs`
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/llvm/llvm-project/archive/a87782c34d667d1c1a18fe82a9a7abfc72fd345b.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from http://mirror.tensorflow.org/github.com/bazelbuild/rules_closure/archive/cf1e44edb908e9616030cc83d085989b8e6cd6df.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/tensorflow/runtime/archive/fc70a32ecd248dd7612d75d2177125ed14541367.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_google_benchmark' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'pybind11_bazel' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'rules_python' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'xctestrunner' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'pybind11' because it already exists.
INFO: Build options --cpu, --crosstool_top, --fat_apk_cpu, and 2 more have changed, discarding analysis cache.
DEBUG: Rule 'rules_cc' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "3839996049629e6377abdfd04681ddeeb0cc3db13b9d2ff81bf46700cb4529f7"
DEBUG: Repository rules_cc instantiated at:
  /home/mediapipe/WORKSPACE:96:13: in <toplevel>
Repository rule http_archive defined at:
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/bazel_tools/tools/build_defs/repo/http.bzl:364:31: in <toplevel>
DEBUG: Rule 'rules_python' indicated that a canonical reproducible form can be obtained by modifying arguments shallow_since = "1564776078 -0400"
DEBUG: Repository rules_python instantiated at:
  /home/mediapipe/WORKSPACE:31:23: in <toplevel>
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/rules_pkg/deps.bzl:33:10: in rules_pkg_dependencies
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/bazel_tools/tools/build_defs/repo/utils.bzl:233:18: in maybe
Repository rule git_repository defined at:
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/bazel_tools/tools/build_defs/repo/git.bzl:199:33: in <toplevel>
INFO: Analyzed target //mediapipe_api:mediapipe_proto_srcs (0 packages loaded, 929 targets configured).
INFO: Found 1 target...
Target //mediapipe_api:mediapipe_proto_srcs up-to-date:
  bazel-bin/mediapipe_api/mediapipe_proto_srcs.zip
INFO: Elapsed time: 0.243s, Critical Path: 0.02s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
DEBUG (build.py): Unarchiving 'bazel-bin/mediapipe_api/mediapipe_proto_srcs.zip' to 'build/Scripts/Protobuf'...
INFO (build.py): Built protobuf sources
INFO (build.py): Downloading dlls...
DEBUG (build.py): Running `nuget install -o .nuget -Source https://api.nuget.org/v3/index.json`
Feeds used:
  /home/mediapipe/.nuget/packages/
  https://api.nuget.org/v3/index.json

All packages listed in /home/mediapipe/packages.config are already installed.
DEBUG (build.py): Copying '.nuget/Google.Protobuf.3.19.1/lib/netstandard2.0/Google.Protobuf.dll' to 'build/Plugins/Protobuf/Google.Protobuf.dll'...
DEBUG (build.py): Changing the mode of 'build/Plugins/Protobuf/Google.Protobuf.dll'...
DEBUG (build.py): Copying '.nuget/packages/google.protobuf/3.19.1/lib/netstandard2.0/Google.Protobuf.dll' to 'build/Plugins/Protobuf/Google.Protobuf.dll'...
DEBUG (build.py): Changing the mode of 'build/Plugins/Protobuf/Google.Protobuf.dll'...
DEBUG (build.py): Copying '.nuget/packages/system.memory/4.5.3/lib/netstandard2.0/System.Memory.dll' to 'build/Plugins/Protobuf/System.Memory.dll'...
DEBUG (build.py): Changing the mode of 'build/Plugins/Protobuf/System.Memory.dll'...
DEBUG (build.py): Copying '.nuget/packages/system.buffers/4.4.0/lib/netstandard2.0/System.Buffers.dll' to 'build/Plugins/Protobuf/System.Buffers.dll'...
DEBUG (build.py): Changing the mode of 'build/Plugins/Protobuf/System.Buffers.dll'...
DEBUG (build.py): Copying '.nuget/packages/system.runtime.compilerservices.unsafe/4.5.2/lib/netstandard2.0/System.Runtime.CompilerServices.Unsafe.dll' to 'build/Plugins/Protobuf/System.Runtime.CompilerServices.Unsafe.dll'...
DEBUG (build.py): Changing the mode of 'build/Plugins/Protobuf/System.Runtime.CompilerServices.Unsafe.dll'...
DEBUG (build.py): Copying '.nuget/System.Buffers.4.4.0/lib/netstandard2.0/System.Buffers.dll' to 'build/Plugins/Protobuf/System.Buffers.dll'...
DEBUG (build.py): Changing the mode of 'build/Plugins/Protobuf/System.Buffers.dll'...
DEBUG (build.py): Copying '.nuget/System.Memory.4.5.3/lib/netstandard2.0/System.Memory.dll' to 'build/Plugins/Protobuf/System.Memory.dll'...
DEBUG (build.py): Changing the mode of 'build/Plugins/Protobuf/System.Memory.dll'...
DEBUG (build.py): Copying '.nuget/System.Runtime.CompilerServices.Unsafe.4.5.2/lib/netstandard2.0/System.Runtime.CompilerServices.Unsafe.dll' to 'build/Plugins/Protobuf/System.Runtime.CompilerServices.Unsafe.dll'...
DEBUG (build.py): Changing the mode of 'build/Plugins/Protobuf/System.Runtime.CompilerServices.Unsafe.dll'...
INFO (build.py): Downloaded protobuf dlls
INFO (build.py): Building resource files
DEBUG (build.py): Running `bazel build -c opt --verbose_failures //mediapipe_api:mediapipe_assets`
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/llvm/llvm-project/archive/a87782c34d667d1c1a18fe82a9a7abfc72fd345b.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from http://mirror.tensorflow.org/github.com/bazelbuild/rules_closure/archive/cf1e44edb908e9616030cc83d085989b8e6cd6df.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/tensorflow/runtime/archive/fc70a32ecd248dd7612d75d2177125ed14541367.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_google_benchmark' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'pybind11_bazel' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'rules_python' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'xctestrunner' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'pybind11' because it already exists.
DEBUG: Rule 'rules_python' indicated that a canonical reproducible form can be obtained by modifying arguments shallow_since = "1564776078 -0400"
DEBUG: Repository rules_python instantiated at:
  /home/mediapipe/WORKSPACE:31:23: in <toplevel>
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/rules_pkg/deps.bzl:33:10: in rules_pkg_dependencies
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/bazel_tools/tools/build_defs/repo/utils.bzl:233:18: in maybe
Repository rule git_repository defined at:
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/bazel_tools/tools/build_defs/repo/git.bzl:199:33: in <toplevel>
DEBUG: Rule 'rules_cc' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "3839996049629e6377abdfd04681ddeeb0cc3db13b9d2ff81bf46700cb4529f7"
DEBUG: Repository rules_cc instantiated at:
  /home/mediapipe/WORKSPACE:96:13: in <toplevel>
Repository rule http_archive defined at:
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/bazel_tools/tools/build_defs/repo/http.bzl:364:31: in <toplevel>
INFO: Analyzed target //mediapipe_api:mediapipe_assets (0 packages loaded, 29 targets configured).
INFO: Found 1 target...
Target //mediapipe_api:mediapipe_assets up-to-date:
  bazel-bin/mediapipe_api/mediapipe_assets.zip
INFO: Elapsed time: 0.136s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
DEBUG (build.py): Unarchiving 'bazel-bin/mediapipe_api/mediapipe_assets.zip' to 'build/Resources'...
DEBUG (build.py): Unarchiving 'bazel-bin/mediapipe_api/mediapipe_assets.zip' to 'Assets/StreamingAssets'...
INFO (build.py): Built resource files
INFO (build.py): Building native libraries for Android...
DEBUG (build.py): Running `bazel build -c opt --verbose_failures --config=android_arm64 //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android`
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/llvm/llvm-project/archive/a87782c34d667d1c1a18fe82a9a7abfc72fd345b.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from http://mirror.tensorflow.org/github.com/bazelbuild/rules_closure/archive/cf1e44edb908e9616030cc83d085989b8e6cd6df.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/tensorflow/runtime/archive/fc70a32ecd248dd7612d75d2177125ed14541367.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_google_benchmark' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'pybind11_bazel' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'rules_python' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'xctestrunner' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'pybind11' because it already exists.
INFO: Build options --cpu, --crosstool_top, --fat_apk_cpu, and 2 more have changed, discarding analysis cache.
DEBUG: Rule 'rules_cc' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "3839996049629e6377abdfd04681ddeeb0cc3db13b9d2ff81bf46700cb4529f7"
DEBUG: Repository rules_cc instantiated at:
  /home/mediapipe/WORKSPACE:96:13: in <toplevel>
Repository rule http_archive defined at:
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/bazel_tools/tools/build_defs/repo/http.bzl:364:31: in <toplevel>
DEBUG: Rule 'rules_python' indicated that a canonical reproducible form can be obtained by modifying arguments shallow_since = "1564776078 -0400"
DEBUG: Repository rules_python instantiated at:
  /home/mediapipe/WORKSPACE:31:23: in <toplevel>
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/rules_pkg/deps.bzl:33:10: in rules_pkg_dependencies
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/bazel_tools/tools/build_defs/repo/utils.bzl:233:18: in maybe
Repository rule git_repository defined at:
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/bazel_tools/tools/build_defs/repo/git.bzl:199:33: in <toplevel>
ERROR: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/com_google_mediapipe/mediapipe/calculators/tensor/BUILD:34:29: in alias rule @com_google_mediapipe//mediapipe/calculators/tensor:compute_shader_unavailable: target '@com_google_mediapipe//mediapipe:emscripten' is not visible from target '@com_google_mediapipe//mediapipe/calculators/tensor:compute_shader_unavailable'. Check the visibility declaration of the former target if you think the dependency is legitimate
ERROR: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/com_google_mediapipe/mediapipe/calculators/tensor/BUILD:34:29: Analysis of target '@com_google_mediapipe//mediapipe/calculators/tensor:compute_shader_unavailable' failed
INFO: Repository flatbuffers instantiated at:
  /home/mediapipe/WORKSPACE:494:14: in <toplevel>
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/tensorflow/workspace2.bzl:880:28: in workspace
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/tensorflow/workspace2.bzl:65:16: in _initialize_third_party
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/flatbuffers/workspace.bzl:6:20: in repo
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:126:21: in tf_http_archive
Repository rule _tf_http_archive defined at:
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:79:35: in <toplevel>
INFO: Repository eigen_archive instantiated at:
  /home/mediapipe/WORKSPACE:494:14: in <toplevel>
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/tensorflow/workspace2.bzl:880:28: in workspace
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/tensorflow/workspace2.bzl:63:11: in _initialize_third_party
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/eigen3/workspace.bzl:14:20: in repo
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:126:21: in tf_http_archive
Repository rule _tf_http_archive defined at:
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:79:35: in <toplevel>
INFO: Repository android_opencv instantiated at:
  /home/mediapipe/WORKSPACE:291:13: in <toplevel>
Repository rule http_archive defined at:
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/bazel_tools/tools/build_defs/repo/http.bzl:364:31: in <toplevel>
INFO: Repository com_google_absl instantiated at:
  /home/mediapipe/WORKSPACE:80:13: in <toplevel>
Repository rule http_archive defined at:
  /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/bazel_tools/tools/build_defs/repo/http.bzl:364:31: in <toplevel>
ERROR: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/com_google_mediapipe/mediapipe/calculators/tensor/BUILD:280:11: errors encountered resolving select() keys for @com_google_mediapipe//mediapipe/calculators/tensor:tensors_to_detections_calculator
ERROR: Analysis of target '//mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android' failed; build aborted:
INFO: Elapsed time: 1.968s
INFO: 0 processes.

I'm not sure but maybe a bug.
If you're in a hurry, please use https://github.com/homuler/MediaPipeUnityPlugin/releases/tag/v0.8.2 and try again.

Im already using the v0.8.2. I will try to use nother version

That mustn't be, because mediapipe:emscripten is introduced at https://github.com/homuler/MediaPipeUnityPlugin/commit/de44dac3ad5261212d95bc59f57ef1c65802de11#diff-ca06b029e04771cf9438ff1576ec8755401c4acb65faf28ef4d9abc8807bb5e4, which is committed after v0.8.2.

I couldn't reproduce the error. If someone encounter this issue, please let me know.

same issue !

It looks like this error is caused by bazel 5.0.0.
It occurs on Docker container only (does not occur on host machine) because .bazelversion is not copied to it.


Build the test library for tls_engine consistently

@bneradt fixed all the other tests so that the supporting programs and libraries are built in the main build.  This PR fixes up the remaining test library, async_engine.so to be built the same way.
PR #7591 fixes build error on ubuntu release introduced by this PR.

CI build fails on Ubuntu boxes.
../../tests/tools/plugins/async_engine.c: In function 'delay_method':
../../tests/tools/plugins/async_engine.c:230:3: error: ignoring return value of 'write' declared with attribute 'warn_unused_result' [-Werror=unused-result]
  230 |   write(signal_fd, &buf, sizeof(buf));
      |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../../tests/tools/plugins/async_engine.c: In function 'spawn_delay_thread':
../../tests/tools/plugins/async_engine.c:254:5: error: ignoring return value of 'pipe' declared with attribute 'warn_unused_result' [-Werror=unused-result]
  254 |     pipe(pipefds);
      |     ^~~~~~~~~~~~~
cc1: all warnings being treated as errors

Cherry-picked to v9.1.x branch.


Missing character in "Tag names can't contain these characters"

The colon ":" character is also not a valid character. It is missing for the list.

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

ID: bc003943-8bc8-10ac-e633-5640cff3c397
Version Independent ID: f8826361-f601-acf9-3e3d-c96579c02093
Content: Tag Azure resources for logical organization
Content Source: articles/azure-resource-manager/resource-group-using-tags.md
Service: azure-resource-manager
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@brokenjpl - How were you trying to set the name when you got an error? I ran tests for Azure CLI and the portal using : in the name, and both tests worked.

For some reason, I able to use ":" when using the Java SDK as well. But then I get an error when using the Azure Portal Web interface. Attached with error message.

What type of resource are you trying to apply the tag to? I wonder if a particular resource type is being too restrictive in the validation.

I've tried both on VirtualMachines and ResourceGroups.

Maybe this is a bug in the Azure Portal UI?

Thanks for your help.
I've opened a thread here:  https://social.msdn.microsoft.com/Forums/azure/en-US/4d556a76-d1f6-49cd-b334-8bd5ace16abe/azure-portal-bug-in-tagging-resources?forum=azureapimgmt#4d556a76-d1f6-49cd-b334-8bd5ace16abe

A fix is in the works.

Thanks for the update @tfitzmac.
Would you know if this is a Portal Azure UI issue, or a documentation issue?  Will I still be allowed to use the colon [:] character in a tag name?

Great. Thanks much!

@brokenjpl - this has been fixed in the portal.

#please-close

Thanks for the update.

Hi all,
It looks as if this bug has resurfaced in the portal:

Thanks,
Adam


triton server

Do you support triton server deployment?

Since we built this upon TRT-LLM, You can integrate it with Triton server based on the official repo The Triton TensorRT-LLM Backend


Provided types map file "/usr/local/lib/node_modules/typescript/lib/tsserver.js/../typesMap.json" doesn't exist

TypeScript Version:  3.0.3

Search Terms:
tsserver.js typesMap.json
Code
Expected behavior:
Actual behavior:
/usr/local/lib/node_modules/typescript/lib/tsserver.js is not a directory
Info 0    [15:37:44.511] Starting TS Server
Info 1    [15:37:44.524] Version: 3.0.3
Info 2    [15:37:44.525] Arguments: /usr/local/Cellar/node/10.8.0/bin/node /usr/local/bin/tsserver
Info 3    [15:37:44.525] Platform: darwin NodeVersion: 10 CaseSensitive: false
Info 4    [15:37:44.531] Provided types map file "/usr/local/lib/node_modules/typescript/lib/tsserver.js/../typesMap.json" doesn't exist

Playground Link:
Related Issues:

Fixed by #26793


Header section is a bit too wide

Header height changes

[ ] Add fixed tab bar pinned to top on scroll
https://zpl.io/am93036

Mobile version fixes

[ ] Text should be center alignment and with paddings around
[ ] Add paddings to stores badges

This issues was dropped from the list due to the rebranding of the wallet website as can be seen in other project issues


fixed cli.md errors

fixed two errors:
1, Connect Thing to Channel
2, Send a message over HTTP

@aronezhang please follow contribution guidelines explained in CONTRIBUTING.md.
Sign-off your commits and correct PR title.

@aronezhang please sign-off your commits or this PR will be closed due to inactivity.

Connect CLI command fixed here: https://github.com/mainflux/mainflux/pull/1051
Messages command documentation fixed here: https://github.com/mainflux/docs/pull/18


ci: change renovate strategy

Changing the strategy to pin

:tada: This PR is included in version 2.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


a 0 total default to 100

if you put 0 as the total it will show as 100 (sometime you don't want to change the logic but just happen to have nothing to insert in the db that particular time.)
var cliProgress = require("cli-progress")
const pb = new cliProgress.Bar();
pb.start(0, 0);

will show
progress [----------------------------------------] 0% | ETA: nulls | 0/100
instead of
progress [----------------------------------------] 0% | ETA: nulls | 0/0

HI Jean,
thanks for your report. this behaviour is not intended...it is caused by some default values which take precedence in case the provided values are invalid (for example 0).
this.value = startValue || 0;
this.total = total || 100;

i could an an about condition like startValue===total to the .start() function which immediately returns in such cases.
what do you think ?
best regards, Andi

thats a good, suggestion! i think we can do this without any backward compatibility issue.

please try the latest version from the master branch.

 Never write code in a rush before a meeting. Wasn't even the right value haha.
Anyway I just tried it and it work perfectly. It even get completed when I call .stop().
Thanks and have a 🌠 for your trouble :)

You plan on releasing the new version when? seem like haven't done that in a while, the official one is still 1.3.0.

HI Jean,
thats not correct. The GitHub as well as the related NPM release are pointed to v1.4.1 (since 4 month).
I will release v1.5.0 today :)

On github it seem the latest version is still 1.3.0 no? or I'm I misreading this.
http://i.imgur.com/kp1kNbW.png
Anyway npm is updated and that's all I needed, thanks!

Click on show 4 newer tags on the top of the last drafted release

This issue still remains in 1.5.0 because of this line  https://github.com/AndiDittrich/Node.CLI-Progress/commit/7605d2cd0713c1b05397d4f0edb7eabc8cc5a3d8#diff-cd4284509ea6de13aeaac4abc9e81bbdR75 please reopen this issue


Added 3 month java program from Bright Boost

Hacktoberfest notes:

due to volume of submissions, we may not be able to review PRs that do not pass tests and do not have informative titles.
please read our contributing guidelines
be sure to check the output of Travis-CI for linter errors
if this is your first open source contribution, make sure it's not your last!

What does this PR do?
Add Resource(s) | Remove Resource(s) | Add info | Improve Repo
For resources
Description
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[ ] Not a duplicate
[ ] Included author(s) if appropriate
[ ] Lists are in alphabetical order
[ ] Needed indications added (PDF, access notes, under construction)

please remove dot files and start over with a fresh branch


chore: release version 0.10.0

At this point, the release of Timefold Quickstarts is ready to be published.

Release branch has been created.
Git tag has been published.
PR has been prepared to switch development branch to a new SNAPSHOT version.

To finish the release of Timefold Quickstarts,
review and merge this PR to update the stable branch with new code.
Afterward, delete the branch that this PR is based on.
(Typically a button appears on this page once the PR is merged.)

Testing PR, closing.


Add pygments to code hilighting

Based on https://frankindev.com/2017/03/18/syntax-highlight-with-rouge-in-jekyll/ details and http://pygments.org/demo/6350479/?style=manni stylesheet
Closes #50

Note: spaces above/below block are too big, also, line numbers might be better separated by some bar or something to make it more clear.... so... Request  for feedback!


standalone npm module for reactive

> npm install <?reactive> -g

need a npm name for reactive to close this issue.


feat(NumberTheory/FermatNumber): fermatNumber_succ_succ

Can I ask what this lemma is needed for? It's a bit specific and the use of natural subtraction makes me a bit iffy.

Can I ask what this lemma is needed for? It's a bit specific and the use of natural subtraction makes me a bit iffy.

I needed this when I was showing that for all n > 1, the Fermat Number F_n can be written in infinitely many ways as n^2 - 2m^2 for positive natural m and n. For this one needs a starting case and then can construct bigger and bigger examples. (Now of course one can ask what this would be needed for...)
I though this two term non-linear recursion is so basic that it might be useful in other contexts.
But I'm happy to close this pr if you think it is useless.
I think I partly share the suspicion of natural subtraction, at least I can't think of other simple recursive formulas relating simple sequences of natural numbers, which cannot be rewritten in a way to avoid the subtraction.

It's a general fact that given any nonzero integer t, if the solution x ^ 2 - 2 * y ^ 2 = t has one solution, it has infinitely many (and similarly for x ^ 2 - d y^2 for any positive squarefree d). This follows from the theory of Pell equations. So the "infinitely many ways" assertion is not surprising here.
I think there's no harm in adding a lemma for the specific identity you're using here, fermatNumber (n + 2) = (fermatNumber (n + 1)) ^ 2 - 2 * (fermatNumber n - 1) ^ 2. But it needs a better name; and  I completely agree with @vihdzp that the use of Nat subtraction should be avoided. I would suggest you write it as an identity for (fermatNumber (n + 2) : \Z) instead, so the subtraction on the RHS is interpreted as integer rather than Nat subtraction.

I think that writing this for the integers is also the sort of thing that can result in a theorem statement that ends up not being very useful. I would like there to be an actual purpose to proving this.

Meh, we're doing pure mathematics here, what does "actual purpose" mean? :smile:
Seriously, there is some genuine mathematical interest in determining for which n the statement ∃ (x y : ℤ), x ^ 2 - 2 * y ^ 2 = n is true (while there is definitely no interest at all in the analogue for Nat subtraction). The identity used here is perhaps not deep, but it is kind of cute. I would vote for merging, and we can let Moritz show us in later PR's what he wants this identity for.

I'm still keen that we should have a version of the statement using Int rather than Nat subtraction. Could you add this as well? It should be very quick to do given that you have the inequality already.

bors d=loefflerd

I'm still keen that we should have a version of the statement using Int rather than Nat subtraction. Could you add this as well? It should be very quick to do given that you have the inequality already.

I added a Int version. Not sure if this is what you had in mind: distinguishing them by namespace.

This is pretty much ready now; once CI passes, I'll hit merge. Can you add a sentence or two of description to the github PR page header? This will be automatically picked up by the merge script and used as the commit message.

Done, thanks for the review, @loefflerd

bors r+


Add heat depth argument

We need an argument to control the depth between heats for flank firing. We'll also make this available in the strip technique as well.

Here's what the heat_depth argument can do:


Image Picker Squashed images when taking picture/picking from gallery in Portrait mode on iOS real device

Internal: b/143434874
Tested on both a real iPhone 8 Plus & iPhone X device, when taking a portrait picture or selecting a portrait picture from the gallery it is squashing the image so the image appears flattened, i'm using the latest version of image picker (image_picker 0.6.1+4) the code i am using is the standard code when using image picker:
var image = await ImagePicker.pickImage(source: source, maxWidth: 800.0);
This was working fine in an earlier version of the plugin (I need this newest version as it has a fix for retrieveLostData) but now that i've updated i've noticed this is an issue. The below screenshots you can see the images really aren't great when they are squashed. If I do not specify a maxWidth then this seems to work but I never had an issue with this before, has something changed whereby if you only specify one dimension it is not longer working?

Image when taken by the camera:

Image after processed by the image picker:

cc @cyanglaz

This should be fixed with https://github.com/flutter/plugins/pull/2070. Could you update to 0.6.1+10 and confirm?

@callumclift Did flutter/plugins#2070 fix the issue for you?

@cyanglaz updated to 0.6.1+11 and it seems to working fine now, thanks!

@callumclift That's great! I'm closing the issue now. Feel free to leave a comment here if the same issue occurs again and I'll reopen the issue to further investigate.

This issue is still exist on Iphone 12 pro, when I'm taking image from gallery image still rotate,
then I'am using custom code to disable rotate but still not working.
Future<File> fixExifRotation(File image, {deleteOriginal: false}) async {
  Directory tempDir = await getTemporaryDirectory();
  String tempPath = tempDir.path;
  var uuid = Uuid();
  final String processedImageUuid = uuid.v4();

  List<int> imageBytes = await image.readAsBytes();

  List<int> result = await FlutterImageCompress.compressWithList(
    imageBytes,
    quality: 100,
    rotate: 0,
  );

  String imageExtension = basename(image.path);

  File fixedImage = File('$tempPath/$processedImageUuid$imageExtension');

  await fixedImage.writeAsBytes(result);

  if (deleteOriginal) await image.delete();

  return fixedImage;
}


Crash when select current month

Descriprion
Sometimes, click on the "Select Current Month" button makes the app crash with the following exception:
UnhandledException - unhandled exception: System.ArgumentOutOfRangeException: Year, Month, and Day parameters describe an un-representable DateTime.
   at System.DateOnly..ctor(Int32 year, Int32 month, Int32 day)
   at NickvisionMoney.GNOME.Views.AccountView.OnDateRangeEndYearChanged() in /run/build/org.nickvision.money/NickvisionMoney.GNOME/Views/AccountView.cs:line 1318
   at NickvisionMoney.GNOME.Views.AccountView.<.ctor>b__70_28(Object sender, NotifySignalArgs e) in /run/build/org.nickvision.money/NickvisionMoney.GNOME/Views/AccountView.cs:line 252
   at GObject.Closure.InternalCallback(IntPtr closure, IntPtr returnValuePtr, UInt32 nParamValues, ValueData[] paramValuesData, IntPtr invocationHint, IntPtr userData)

How to reproduce

Open an account
Mess arround with viewing/filtering options (can't tell exactly with action(s) trigger the error)
Click on the "Select Current Month" button

Expected behaviour
Filter transaction by the month selected in the calendar widget
System Info
Hardware Information:

Hardware Model: ASUS TUF GAMING B550M-PLUS WIFI II
Memory: 32,0 GiB
Processor: AMD Ryzen™ 5 5600 × 12
Graphics: AMD Radeon™ RX 550 / 550 Series
Disk Capacity: 1,0 TB

Software Information:

Firmware Version: 3002
OS Name: Arch Linux
OS Build: rolling
OS Type: 64-bit
GNOME Version: 45.3
Windowing System: Wayland
Kernel Version: Linux 6.7.1-arch1-1
Formats: Brasil

App Information

Version: 2024.1.0
Package: Flatpak
Source: Flathub

Thanks for reporting this bug.
Reproducing consistently:

Click show current month when on February 2024
Change end year from 2024 Feb 29 to 2023 Feb 29 (impossible date)
Crash!

I found another way to reproduce it consistently:

Click "Select Current Month"
Click "Reset To Today"
Click "Select Current Month"
Crash

Seems like that one too is the same bug.  It's not happening on #780 branch. If possible would you be able to confirm the pr fixes it?

https://github.com/NickvisionApps/Denaro/releases/tag/2024.2.0
Will be available through Flathub in 20 minutes


Input string was not in a correct format.

v 0.8.1
Getting unhandled exception and config.json shows:
https://pastebin.com/Jtm54ysS
if I delete config.json so that it gets recreated and contains this:
https://pastebin.com/xJGnsQqW
all is good again, until some point in time when it throws the exception again.

Ditto. (Was just going to raise this issue myself.)

Please try the latest version with better logging and post the stacktrace here (in DiffusionToolkit.log)
https://github.com/RupertAvery/DiffusionToolkit/releases/tag/beta_v0.8.3

Will do, soon as it happens.

The actual error seems to occur when reading the window pane sizes, when the current region does not use decimal point (.) as a decimal separator.  This should be fixed. Please update and let me know if there is still a problem.

Will do case it happens.


Restore YouTube Username from Handle to Custom: Not working in Desktop Firefox when logged in

I suppose it is the same cause as https://github.com/yakisova41/return-youtube-comment-username/issues/43, with its corresponding fix https://github.com/yakisova41/return-youtube-comment-username/commit/8da40a3746f3d78ae3e382e2ca13af598561d2f4.
The script would not work on desktop Firefox when logged in. It works properly when not logged in on Firefox or if using chromium based browsers either logged in or not. No request is made to fetch the username in the Network tab, but I do not see any extra error messages either.
Reproduction Steps

Create a new profile in Firefox, load in TamperMonkey/ViolentMonkey and your script from GreasyFork.
Open www.youtube.com and pick a video, better pause once the video is loaded but not required.
Scroll down and YouTube comments should have usernames, new browser?key= requests would appear if Network tab is open.
Log in to YouTube, and return to the same video.
Scroll down and YouTube comments should have handles, new browser?key= requests would not appear if Network tab is open.

Versions Tested

v0.5.7 to v0.5.10 (Firefox 114.0.2/TamperMonkey v4.18.1)
V0.5.10 (Firefox 114.0.2/ViolentMonkey v2.14.0)
v0.5.10 to v0.5.14 (Librewolf 110.0.1/ViolentMonkey v2.14.0)

Thanks for reporting.
This issue is due to YouTube native coding issue for their custom elements implementation in Firefox.
Therefore, it is not directly related to the account login status. It is not related to UserScript manager you used.
This issue would not happen in Chrome because Chrome and YouTube both belong to Google.
Please update to the latest version (>=0.5.16). Please close the issue if it works for you.

I can confirm it works now and thanks for your explanation. I didn't expect you to fix it in 2 hours at midnight.
I have attempted to remove all youtube cookies and the Firefox 114.0.2 with v0.5.10 test is done with a fresh profile as a separate instance(when my main profile is also running) logging into my main account. The problem persisted, led me to the conclusion that logging in is the cause of the issue.
PS: I have found YouTube UX becoming worse and worse, but community improvement and the creator base have sort of locked me in. I guess that have also put them in a bind if they want to keep that advantage. Rewriting it will probably just lead to another reddit situation.

From my understanding, the YouTube engine rendering is set to your account + browser application. Clear cookie or fresh profile won't help. The javascript files are the same. The difference is your web page retrieved from YouTube server.
But it usually would not create big issue to your watching experience, just sometimes your userscripts or extensions might not work due to those weird configurations.

I just upgraded the following script to make it more powerful to reset the YouTube settings, including those related to account login issue (incorrect account authorisation settings).
https://greasyfork.org/en/scripts/457255-reset-youtube-settings
Recommend that you can use it to reset once.
You can check in console window that
Before:
typing document.querySelector('ytd-watch-flexy').firstElementChild === null and press enter, show true
After (success):
typing document.querySelector('ytd-watch-flexy').firstElementChild === null and press enter, show false


Add ResourceInherit derive macro

Motivation
When working with ConfigMap data, it is often expected to have a specific data structure on the inner content. While defining a CRD is the standard way of resolving the fields validation, it is sometimes not possible or desirable at the moment.
This generally requires a manual conversion via serde, which involves creating a custom structure for the data content, which is only one field away from being a fully replicated ConfigMap or Secret definition (in the context of the problem).
Choosing this direction may require implementing Resource trait manually, which adds to the amount of glue code.

Solution
Provide a ResourceInherit derive macro, capable of inheriting Resource implementation of the specified upstream object.
The resulting code can look like the following:
use k8s_openapi::api::core::v1::ConfigMap;

#[derive(ResourceInherit)]
#[inherit(resource = "ConfigMap", namespaced)]
struct TypedMap {
    metadata: ObjectMeta,
    data: Option<TypedData>,
}

struct TypedData {
    field: String,
}

Hey, this is a cool idea.
As a quick first impression, I think it makes sense, although it does not necessarily save much in terms of user code since custom structs can re-use type information with the dynamic api:
https://github.com/kube-rs/kube/blob/7ff120a1cad8797b098919eada1485573ea722c5/examples/dynamic_pod.rs#L25-L28
However, there's a reasonable argument for this in terms of complexity, by being able to just use the normal (non-dynamic api) and not have to learn about concepts of erasure.

Yes, agree, I felt that this is explored area already, but at the moment of writing, this model looked natural to me. I believe unstable-client features should work with this implementation out of the box.

Hmm, I actually tried using it with similar to dynamic_pod example:
let secret_api: Api<CertSecret> = Api::namespaced_with(
            ctx.client.clone(),
            "cattle-fleet-system",
            ApiResource::erase::<Secret>(&()),
 );

and got:
60 |         let secret_api: Api<CertSecret> = Api::namespaced_with(
   |                                           ^^^^^^^^^^^^^^^^^^^^ the trait `k8s_openapi::Metadata` is not implemented for `CertSecret`

Since the secret follows different model - data vs spec, does it make sense to use generated resource definition?

hm, yeah. you'd actually have to use the dynamic api fully for the non-compliant core objects with erase (no Object or derive CustomResource bypass):
let secret_api: Api<DynamicObject> = Api::namespaced_with(
            ctx.client.clone(),
            "cattle-fleet-system",
            ApiResource::erase::<Secret>(&()),
 );

which means secondary Value unpacking, and it does make the dynamic api less attractive for known types. let me review this a bit more properly.


Add privacy control for player video feeds

For competition layouts which support video feed, nestrischamps should not grab the video feed of webcam without user consent.
TODO:

The producer window should have some ui control to allow/disallow player feed

Simple checkbox could do.

Done


pilot: wait for queue to complete in test

Please provide a description of this PR:

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
b3c6d5542e82c22d7cfc9d7e1114d2175090d41d
link
true
/test unit-tests

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

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
b3c6d5542e82c22d7cfc9d7e1114d2175090d41d
link
true
/test unit-tests

unit-tests-arm64_istio
b3c6d5542e82c22d7cfc9d7e1114d2175090d41d
link
true
/test unit-tests-arm64

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


Remove in-place updates and fix return values

Currently, some models perform in-place updates which breaks ReverseDiff support (#58) and return values that do not exist (if isempty(intercept_ranef)). Both issues are fixed by the PR.
Probably it would be good to add some tests.
Fixes #58.

I will add the tests. Thanks for the PR!
One thing: why are we returning nothing now? What if the user wants to perform posterior predictive checks?

Because currently the return values are broken. Some of the to-be-returned parameters don't always exist since they are not sampled if isempty(intercept_randef). Alternatively, we could fix that by return different named tuples, depending on whether they exist or not, but then the model function becomes unstable. So with the current setup the simplest thing to do that ensures type stability and that return values actually exist is to return nothing.
I'm not sure how you usually perform posterior predictive checks. But e.g. using rand(model) will just sample a NamedTuple (or maybe Tor changed it to a Dìct already since NamedTuple does not work as generally IIRC) of the variables, so it's not necessary to explicitly return a named tuple of variables in general. For posterior predictive checks, I think, it would also be useful to use the conditioning syntax but that's probably best left for another PR.

@devmotion you know what might be causing this with Tracker:
Not implemented: convert tracked Tracker.TrackedReal{Float64} to tracked Float64

https://github.com/TuringLang/TuringGLM.jl/runs/8196333415?check_suite_focus=true#step:6:721

Zygote also fails with:
Zygote: Error During Test at /home/runner/work/TuringGLM.jl/TuringGLM.jl/test/runtests.jl:41
  Got exception outside of a @test
  Can't differentiate foreigncall expression $(Expr(:foreigncall, :(Core.tuple("pt", StatsFuns.RFunctions.libRmath)), Float64, svec(Float64, Float64, Int32, Int32), 0, :(:ccall), %11, %12, %13, %14, %10, %9, %8, %7)).
  You might want to check the Zygote limitations documentation.
  https://fluxml.ai/Zygote.jl/latest/limitations

Yep, that's expected when you work with cdfs of t distributions in Julia. It's one of the few cases that still call out into Rmath, and hence it can't be differentiated by Zygote without a custom rule.

Ok, we can merge this so that we support ReverseDiff and FowardDiff.


Fatal error when creating a swarm

Docker version: latest
I created a node aimed to be a manager. Before I successfully create a manager node and initiated swarm.
I configured a firewall before joining the second manager... then, when I tried to join, it interrupted the joining process... but it joined like worker(?). I tried to leave the swarm, it said that this node was a manager, so I tried to force it... and it was not possible.
Then I removed the manager (the first one) and it leaved correctly... then I tried again with de second one... and it was not possible (again).
Now, when restarting, docker daemon fails. This is the output:
docker.service
Loaded: loaded (/etc/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2016-09-07 17:01:38 UTC; 9s ago
Process: 1521 ExecStart=/usr/bin/docker daemon -H tcp://<IP_ADDRESS>:2376 -H unix:///var/run/docker.sock --storage-driver aufs --tlsverify --tlscacert /etc/docker/ca.pem --tlscert /etc/docker/server.pem --tlskey /etc/docker
Main PID: 1521 (code=exited, status=1/FAILURE)
Sep 07 17:01:38 manager2 docker[1521]: time="2016-09-07T17:01:38.108066059Z" level=info msg="Graph migration to content-addressability took 0.00 seconds"
Sep 07 17:01:38 manager2 docker[1521]: time="2016-09-07T17:01:38.108870788Z" level=warning msg="Your kernel does not support swap memory limit."
Sep 07 17:01:38 manager2 docker[1521]: time="2016-09-07T17:01:38.110026338Z" level=info msg="Loading containers: start."
Sep 07 17:01:38 manager2 docker[1521]: .time="2016-09-07T17:01:38.185243038Z" level=info msg="Firewalld running: false"
Sep 07 17:01:38 manager2 docker[1521]: time="2016-09-07T17:01:38.624032796Z" level=info msg="Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be used to set a preferred IP ad
Sep 07 17:01:38 manager2 docker[1521]: time="2016-09-07T17:01:38.714473968Z" level=info msg="Loading containers: done."
Sep 07 17:01:38 manager2 docker[1521]: time="2016-09-07T17:01:38.715392307Z" level=fatal msg="Error creating cluster component: could not find local IP address: dial udp <IP_ADDRESS>:2377: connect: network is unreachab
Sep 07 17:01:38 manager2 systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Sep 07 17:01:38 manager2 systemd[1]: docker.service: Unit entered failed state.
Sep 07 17:01:38 manager2 systemd[1]: docker.service: Failed with result 'exit-code'.
What can I do to solve it? should I remove the node and create a new one?

@fincaminimo Can you please confirm the version of Docker you're using (for example by pasting the output of docker info)? Thanks!

Sorry but right now I haven't that problem because I've reinstalled all the
host's software. I cannot help you any more, but say that I think it was
1.12.1...
El mié., 7 sept. 2016 a las 19:57, Arnaud Porterie (<
<EMAIL_ADDRESS>escribió:

@fincaminimo https://github.com/fincaminimo Can you please confirm the
version of Docker you're using (for example by pasting the output of docker
info)? Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/issues/26381#issuecomment-245364265,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABM022youC9gP9TSQ1yvl0I7DNB4buw3ks5qnvr_gaJpZM4J3J00
.

--
Arkaitz Múgica Islas<EMAIL_ADDRESS>943 562 147 / 902 002 635

Let me go ahead and close this issue, as there's no reproducible setup now, but feel free to comment if you think I closed by mistake