Rule Idea: Using named argument for include with_context or boolean twig extension calls

Rule(s) related to or rule(s) missing
Rule Idea.
Expected behavior
I'm using with_context = false a lot in my twig files. While updating twig cs fixer to the latest version I stumble over that existing {% include %} where migrated and just use , false for it. For more transparent I prefer to use named argument for the with_context parameter:
{{ include('include.html.twig', {}, with_context = false) }}

So I thought maybe it would be nice to have a rule for the with_context or even for all boolean based twig extensin calls.
Actual behavior
No rule yet:
{{ include('include.html.twig', {}, false) }}

Hi,
First, I'm not sure about having such rule here since it may be consider too much opinionated.

One could prefer having no named param
One could prefer having every named param
You prefer to use named param for the third param only

Second, I'm not sure about how easy a fixer would be.
In include('include.html.twig', {}, false), I don't have an easy way to know which value is the third param. I could consider it after the second , ; but I have to take care of code like

include(getTemplate(foo, bar), {}, false)
include(foo, with_context = false)

Maybe you could be interested in a custom Node-based rule like
https://github.com/VincentLanglet/Twig-CS-Fixer/blob/3.0.0/src/Rules/Node/ValidConstantFunctionRule.php
Since it play with Node rather than Token, you can easily access to function arguments, and you'll be able to write a rule:

Checking the with_context param is set to false
Checking it use the named_param.

The only drawback is the fact that Node-based rule are not fixable (so far).

@VincentLanglet the basic idea what was in my mind case is if not on a specific argument instead a specific scalar types. If a given value to a twig extension call is a boolean value and it is not a named argument add the name of the argument. So more a BooleanNamedArgumentRule.
-{{ someExtension(someOtherExtension(true), {}, true) }}
+{{ someExtension(someOtherExtension(name_2: true), {}, name_2: true) }}

cases like following would stay untouched:
-{{ someExtension(someOtherExtension(otherArgument), {}, withContext) }}
+{{ someExtension(someOtherExtension(otherArgument), {}, withContext) }}

But I understand you decision if its to complex to keep it out of core.

The only drawback is the fact that Node-based rule are not fixable (so far).

Current case I want to avoid adding non fixable validators to the twig lint task, but yeah would be another option.

@VincentLanglet the basic idea what was in my mind case is if not on a specific argument instead a specific scalar types. If a given value to a twig extension call is a boolean value and it is not a named argument add the name of the argument. So more a BooleanNamedArgumentRule.

I think this have to be on specific argument since I cannot guess the name of the argument.
You will need to end with some config like
['include' => [3 => 'with_context']]

and list all the wanted methods.

But I understand your decision if its to complex to keep it out of core.

I'll let the issue open to get feedback/suggestions, ... but yeah I think it might be better out of core.
I can still help you if you want to try working on the custom rule.

The only drawback is the fact that Node-based rule are not fixable (so far).

Current case I want to avoid adding non fixable validators to the twig lint task, but yeah would be another option which I keep in my backmind.

I understand. If you want to make the rule fixable it would require

That the tool is able to have NodeBasedRule fixable (I don't think it's possible)
To write the rule with TokenBasedRule

It may be possible with TokenBasedRule with the logic:

If the token is not a FUNCTION_TYPE, returns
If the name is not "include" returns
Take the related ( if exists
count the , before the related ) and skip any content when another (, { or [ came (until the closer).
then check the parameter value
if you don't find the named parameter, add it

Thank you for your detailed feedback. Let see if I'm the only one which searching for such rule.
Are there some instruction docs about how to create custom Node or Token based rules?

Are there some instruction docs about how to create custom Node or Token based rules?

ATM no, you have to get inspired by existing rules. But it's on my todo to improve the doc. Any feedback/PR is welcomed.

Thank you for your detailed feedback. Let see if I'm the only one which searching for such rule.
Are there some instruction docs about how to create custom Node or Token based rules?

I'm working on documentation (still wip) about writing such rules https://github.com/VincentLanglet/Twig-CS-Fixer/blob/main/docs/custom.md any feedback is welcome @alexander-schranz

BTW @alexander-schranz https://github.com/VincentLanglet/Twig-CS-Fixer/pull/302 introduce a new NAMED_ARGUMENT_SEPARATOR_TYPE token which could help to write your rule.
Anyway, I consider this rool won't be implemented in this library so I'll close.
I can still help to implement it (in your project) here or in a discussion


error with cargo new: could not find '/git/.git_template/' to stat

Problem
Rust newbie. I'm seeing a bizarre error right out of the box. Google coming up empty so I guess I'm the only one?
$ cargo new hello-rust
error: Failed to create package `hello-rust` at `/home/githorse/hello-rust`

Caused by:
  could not find '/git/.git_template/' to stat: No such file or directory; class=Os (2); code=NotFound (-3)

Steps
I'm following the Getting Started steps:
$ curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
$ rustup update # just for kicks
$ rustup --version
rustup 1.23.1 (3df2264a9 2020-11-30)
$ cargo --version
cargo 1.51.0 (43b129a20 2021-03-16)
$ cargo new hello-rust
🤦

Notes
I don't have a /git/.git_template ... is that a thing? I do have a ~/.git_template. Either way cargo probably should not blow up without it.
Providing the required template does resolve the error:
$ sudo mkdir /git
$ sudo ln -s ~/.git_template /git/.git_template
$ cargo new hello-rust
     Created binary (application) `hello-rust` package

But again ... why?

Hm, that is strange! Could you try running git config init.templateDir and check if it is set to anything?  Or maybe run git config --list to see if there are any other config settings that might be changed from the default?

Got it in one! Config fail on my part (the path was being set by $MISSING_VARIABLE_HERE/git/.git_template). My bad.
Still, maybe Cargo could issue a warning here rather than failing. git clone for instance just gives me a warning but doesn't fail. I must have had this issue for a while now (through many installs of different tools) but haven't noticed until now. But probably not a corner case worth worrying about :)


Needed for Statamic Git Automation purposes.

https://statamic.dev/git-automation#remote-setup

[ ] Bug fix #…?

[ ] New feature?

[ ] BC breaks?

[ ] Tests added?

[ ] Docs added?
Please, regenerate docs by running next command:
$ php bin/docgen

When using the Git Automation functionality in Statamic the current remote branch needs to be a 'non-tag' branch, otherwise we can't sync back the changes upstream.
By adding $target = get('branch', 'HEAD'); the update_code script tries to use the selected deployment branch.
For extra context: https://statamic.dev/git-automation#remote-setup

relates to https://github.com/deployphp/deployer/issues/3464


ci: fix release assets dirs

#169  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @AngelOnFira and the rest of your teammates on  Graphite


rust-analyzer-unwrapped: 2024-09-02 -> 2024-11-11

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for rust-analyzer-unwrapped is: Modular compiler frontend for the Rust language
meta.homepage for rust-analyzer-unwrapped is: https://rust-analyzer.github.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS

[!CAUTION]
A test defined in passthru.tests did not pass.

found 2024-11-11 with grep in /nix/store/s6zbrv0f8y7igvlj6fxjmxs8n28y8p9v-rust-analyzer-unwrapped-2024-11-11
found 2024-11-11 in filename of file in /nix/store/s6zbrv0f8y7igvlj6fxjmxs8n28y8p9v-rust-analyzer-unwrapped-2024-11-11

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath

ra-multiplex
rust-analyzer
rust-analyzer-unwrapped
vscode-extensions.rust-lang.rust-analyzer

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/s6zbrv0f8y7igvlj6fxjmxs8n28y8p9v-rust-analyzer-unwrapped-2024-11-11 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rust-analyzer-unwrapped https://github.com/r-ryantm/nixpkgs/archive/59426917801866c10df709f9fd398780ec4271ed.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/59426917801866c10df709f9fd398780ec4271ed#rust-analyzer-unwrapped

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/s6zbrv0f8y7igvlj6fxjmxs8n28y8p9v-rust-analyzer-unwrapped-2024-11-11
ls -la /nix/store/s6zbrv0f8y7igvlj6fxjmxs8n28y8p9v-rust-analyzer-unwrapped-2024-11-11/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 4 packages built:

ra-multiplex
rust-analyzer
rust-analyzer-unwrapped
vscode-extensions.rust-lang.rust-analyzer

Maintainer pings
cc @oxalica for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Hello @oxalica, Is there something that I can do to help merging this PR?

Hello @oxalica, Is there something that I can do to help merging this PR?

It seems that the tests are falling. Looking into that and fixing them would be the first step.


python37Packages.identify: 1.5.13 -> 1.5.14

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python37Packages.identify is: "File identification library for Python"
meta.homepage for python37Packages.identify is: "https://github.com/chriskuehl/identify"
meta.changelog for python37Packages.identify is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.5.14 with grep in /nix/store/dsrx6wlmchfhrzqmld3llgzgyjkgav77-python3.7-identify-1.5.14

directory tree listing: https://gist.github.com/da526eb86c394f6a0b9d9fce4e778a13

du listing: https://gist.github.com/9105e554d809277cef70cc72be0dd5ce

Rebuild report (if merged into master) (click to expand)

28 total rebuild path(s)

7 package rebuild(s)

7 x86_64-linux rebuild(s)
7 i686-linux rebuild(s)
7 x86_64-darwin rebuild(s)
7 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
pre-commit
python37Packages.identify
python37Packages.pre-commit
python38Packages.identify
python38Packages.pre-commit
python39Packages.identify
python39Packages.pre-commit

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/dsrx6wlmchfhrzqmld3llgzgyjkgav77-python3.7-identify-1.5.14 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python37Packages.identify https://github.com/r-ryantm/nixpkgs/archive/8c24833f1103cceba7c56265e39b99929764bcf5.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/dsrx6wlmchfhrzqmld3llgzgyjkgav77-python3.7-identify-1.5.14
ls -la /nix/store/dsrx6wlmchfhrzqmld3llgzgyjkgav77-python3.7-identify-1.5.14/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

6 packages built:

pre-commit (python38Packages.pre-commit)
python37Packages.identify
python37Packages.pre-commit
python38Packages.identify
python39Packages.identify
python39Packages.pre-commit

Maintainer pings

Result of nixpkgs-review pr 114010 at 8c24833f run on aarch64-linux 1

6 packages built:

pre-commit (python38Packages.pre-commit)
python37Packages.identify
python37Packages.pre-commit
python38Packages.identify
python39Packages.identify
python39Packages.pre-commit

1 suggestion:

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/identify/default.nix:15:3:
   |
15 |   meta = with lib; {
   |   ^


rename build directory to lib and add an index.js file

I think it's a standard to provide a ready to go package on npm:
src       # ES6
lib       # transpiled files (ES5)
index.js  # npm package entry point

:+1:
On Tue, Jun 2, 2015 at 4:26 PM, Giulio Canti<EMAIL_ADDRESS>wrote:

I think it's a standard to provide a ready to go package on npm:
src       # ES6
lib       # transpiled files (ES5)
index.js  # npm package entry point
—
Reply to this email directly or view it on GitHub
https://github.com/buildo/web-framework/issues/3.

--
Giovanni
~ buildo

ops.. there's already an index.js file in src. The additional root/index.js file is useless. Pointing to "main": "lib/index.js" in package.json is enough

Yup, but I think anyway that lib instead of build is sort of a
convention
On Tue, Jun 2, 2015 at 4:43 PM, Giulio Canti<EMAIL_ADDRESS>wrote:

ops.. there's already an index.js file in src. The additional
root/index.js file is useless. Pointing to "main": "lib/index.js" in
package.json is enough
—
Reply to this email directly or view it on GitHub
https://github.com/buildo/web-framework/issues/3#issuecomment-107977274.

--
Giovanni
~ buildo

lib instead of build is sort of a convention

:+1:

dist?
gabriele
~ buildo

On 02 Jun 2015, at 16:45, Giovanni Gonzaga<EMAIL_ADDRESS>wrote:
Yup, but I think anyway that lib instead of build is sort of a
convention
On Tue, Jun 2, 2015 at 4:43 PM, Giulio Canti<EMAIL_ADDRESS>wrote:

ops.. there's already an index.js file in src. The additional
root/index.js file is useless. Pointing to "main": "lib/index.js" in
package.json is enough
—
Reply to this email directly or view it on GitHub
https://github.com/buildo/web-framework/issues/3#issuecomment-107977274.

--
Giovanni
~ buildo
—
Reply to this email directly or view it on GitHub.

AFAIK dist is for minimized files and/or browser distributions
lib should be the standard on npm

:+1:
gabriele
~ buildo

On 02 Jun 2015, at 16:51, Giulio Canti<EMAIL_ADDRESS>wrote:
AFAIK dist is for minimized files and/or browser distributions
lib should be the standard on npm
—
Reply to this email directly or view it on GitHub.


Routing not working

Command
add, new
Is this a regression?

[X] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
Routing not working inside project folder applications
localhost:4200/admin/dashboard
Minimal Reproduction
Create New Project
ng new <somename>
Create new application under projects
ng g application admin
Add route in main app ( file name: app.routes.ts)
import { Routes } from '@angular/router';
import { AppComponent as AdminAppComponent } from '../../projects/admin/src/app/app.component';
export const routes: Routes = [
  {
    path: 'voice',
    component: AdminAppComponent,
  },
];

Create component under
ng g c dashboard
Create route under Admin app
import { Routes } from '@angular/router';
import { AppComponent } from './app.component';
import { DashboardComponent } from './dashboard/dashboard.component';

export const routes: Routes = [
  {
    path: '',
    component: AppComponent,
    children: [
      { path: 'dashboard, component: DashboardComponent },
      { path: '**', redirectTo: 'dashboard' },
    ],
  },
];

Exception or Error
No response
Your Environment
ng version

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 17.3.8
Node: 20.12.0
Package Manager: npm 10.5.0
OS: win32 x64

Angular: 17.3.10
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1703.8
@angular-devkit/build-angular   17.3.8
@angular-devkit/core            17.3.8
@angular-devkit/schematics      17.3.8
@angular/cli                    17.3.8
@schematics/angular             17.3.8
rxjs                            7.8.1
typescript                      5.4.5
zone.js                         0.14.6

Anything else relevant?
No response

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular-cli.
If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.


Add an ob doc command to get links to documentation.

Can you update the changelog and add something to the readme?


Change to IBI Group

Checklist

[ ] Appropriate branch selected (all PRs must first be merged to dev before they can be merged to master)
[ ] Any modified or new methods or classes have helpful JavaDoc and code is thoroughly commented
[ ] The description lists all applicable issues this PR seeks to resolve
[ ] The description lists any configuration setting(s) that differ from the default settings
[ ] All tests and CI builds passing

Description
Change code owners to IBI Group

Codecov Report

Merging #260 into dev will decrease coverage by 11.37%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##                dev     #260       +/-   ##
=============================================
- Coverage     31.56%   20.19%   -11.38%
+ Complexity      655      399      -256
=============================================
  Files           151      151
  Lines          8082     8082
  Branches       1079     1079
=============================================
- Hits           2551     1632      -919
- Misses         5219     6304     +1085
+ Partials        312      146      -166

Flag
Coverage Δ
Complexity Δ

#end_to_end_tests
?
?

#unit_tests
20.19% <ø> (ø)
399 <ø> (ø)
:arrow_down:

Impacted Files
Coverage Δ
Complexity Δ

.../conveyal/datatools/manager/models/LoadStatus.java
0% <0%> (-100%)
0% <0%> (-1%)

...a/com/conveyal/datatools/manager/auth/Actions.java
0% <0%> (-100%)
0% <0%> (-1%)

...manager/jobs/CreateFeedVersionFromSnapshotJob.java
0% <0%> (-100%)
0% <0%> (-4%)

...ls/manager/models/FeedValidationResultSummary.java
0% <0%> (-92%)
0% <0%> (-4%)

...yal/datatools/manager/jobs/FetchSingleFeedJob.java
0% <0%> (-82.36%)
0% <0%> (-6%)

...ls/manager/jobs/NotifyUsersForSubscriptionJob.java
0% <0%> (-72.35%)
0% <0%> (-7%)

...va/com/conveyal/datatools/manager/models/Note.java
0% <0%> (-66.67%)
0% <0%> (ø)

.../com/conveyal/datatools/manager/models/Bounds.java
0% <0%> (-64.29%)
0% <0%> (-5%)

.../conveyal/datatools/manager/models/Deployment.java
0% <0%> (-61.3%)
0% <0%> (-21%)

...com/conveyal/datatools/manager/models/Project.java
30% <0%> (-55%)
2% <0%> (-5%)

... and 38 more

Continue to review full report at Codecov.

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

:tada: This PR is included in version 3.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Bug Report:  Audio book section is looking empty, which is portraying that the owner has a few resources

Reproduction steps
scroll down to audio books section and tsee the error
Expected behavior
It should have more beautiful designing, animations or hover effects as the rest of the website has.
Actual Behavior
The blank area under the audio books section  is not looking nice

👀 Have you spent some time to check if this issue has been raised before?

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

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

hey @piyushkhurana2019  are you working on this issue? if not assign it me

hey @piyushkhurana2019 are you working on this issue? if not assign it me

yes i would love to work on it once @SauravMukherjee44 assign this issue to me

I am interested to work on this issue please assign me this task under GSSOC.


Change base image back to busybox

After updating to the latest Docker image today, I found that my setup broke because the base image is now scratch. Considering busybox is a pretty lightweight image already, this seems to have minimal benefit, while making troubleshooting and other use cases needlessly difficult.
For example, my entrypoint is of the form /bin/sh -c "tail -F /goaccess/logs/access_log | goaccess ... since goaccess isn't natively able to follow log files across renames/rotations.

Thank you for reporting this. It should be fixed. Please let me know how it goes on your end.


Improve installation of executable

Closes #13

Codecov Report
Base: 100.00% // Head: 100.00% // No change to project coverage :thumbsup:

Coverage data is based on head (6f60514) compared to base (5bb66d6).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #14   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           30        30
=========================================
  Hits            30        30

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


FIXED_LIST config

Sorry but i can't manage how to configure the webapi repository as a FIXED_LIST
I've found the MULTICAST example, webapi/conf/repository.json
{
  "clusters" : [
    {
      "name" : "myCluster",
      "mode" : "MULTICAST",
      "address" : "<IP_ADDRESS>",
      "port" : 31999
    }
  ]
}

I know that the mode will be "FIXED_LIST", but how to configure members ?
https://github.com/griddb/webapi/blob/master/Parameters.md
transactionMember is a String, What to put in transactionMember / sqlMember please ?
{
  "clusters" : [
    {
      "name" : "myCluster",
      "mode" : "FIXED_LIST",
      "transactionMember" : "?",
      "sqlMember" : "?"
    }
  ]
}

Thank you for your usage.
Could you please set with "(IP address of GridDB node):(portNo)" format for transactionMember / sqlMember ?
Default portNo for transactionMember (sqlMember) is 10001 (2001).
The setting of transactionMember (sqlMember) is used to connect to GridDB node with Java Client (JDBC Driver).
For example:
    ...
    "transactionMember" : "<IP_ADDRESS>:10001"
    "sqlMember" : "<IP_ADDRESS>:20001"
    ...

FIXED_LIST: fixed list method for GridDB node
https://github.com/griddb/docs-en/blob/master/manuals/GridDB_FeaturesReference.md#fixed_list-fixed-list-method
notificationMember for Java client
https://griddb.org/docs-en/manuals/GridDB_Java_API_Reference.html#GridStoreFactory.html__getGridStore(java.util.Properties)
notificationMember for JDBC Driver
https://github.com/griddb/docs-en/blob/master/manuals/GridDB_JDBC_Driver_UserGuide.md#connection-url-format


[T2A3][W15-A1] Ng Shao Hui

Ready for review

Good that you attempt to put one change per commit.

Some comments added. Feel free to add more comment if you have any questions. Once you are done, you may close the PR after reading comments.


Issue #SB-17795 feat: double encoding

Codecov Report

Merging #828 into release-2.9.0 will increase coverage by 0.04%.
The diff coverage is 100%.

@@                 Coverage Diff                 @@
##             release-2.9.0     #828      +/-   ##
===================================================
+ Coverage            40.99%   41.03%   +0.04%
- Complexity            1021     1023       +2
===================================================
  Files                  150      150
  Lines                10140    10147       +7
  Branches              1123     1123
===================================================
+ Hits                  4157     4164       +7
  Misses                5564     5564
  Partials               419      419

Impacted Files
Coverage Δ
Complexity Δ

...otification/sms/providerimpl/Msg91SmsProvider.java
72.87% <100%> (+0.74%)
26 <1> (+1)
:arrow_up:

...notification/sms/providerimpl/ProviderDetails.java
92.3% <100%> (+1.39%)
6 <2> (+1)
:arrow_up:

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 c262a91...819c029. Read the comment docs.


[calibration] test rig calibration with CCTag on synthetic data

[ ] debug if there are problems
[ ] asses quality of results

This may need a new dataset with more cctags visible in all the images


Avoid passing null

Issue created from code comment with imdone.io

TODO:  @Sandy Avoid passing null id:127
src/vs/workbench/services/configuration/node/configuration.ts:458
@imdone - Efficiently manage your project's technical debt. imdone.io

Issue closed by removing a comment.

TODO:  @Sandy Avoid passing null id:127 gh:153
src/vs/workbench/services/configuration/node/configuration.ts:458
@imdone - Efficiently manage your project's technical debt. imdone.io


Cannot sign multi-sig transaction with signTx() API

Cannot get a transaction from a multi-sig address signed by Nami. It can be reproduced here:
https://cardano-multi-sig-app-testnet.vercel.app/treasuries/ggGCggBYHOQS%2Buq87qmsRuz8yOT2uBUUMfIJdTZXihGvyK2CAFgcFwxHqjkD0nXzcTZjPYqaiSoVfR1aVqRDZF9UwA%3D%3D/owCBglggSYpmLRbdr9yrtUJnQ7TxzzJnFSetlbwITUfwKv2cneQAAYKCWDkA5BL66rzuqaxG7PzI5Pa4FRQx8gl1NleKEa%2FIrbpRy3QPWMQKvlgSoibx5Y7npWyWLPub3wt%2F4WYaAExLQIJYOTAEbb36RJc2RVgT46BGQ5ITZdCTHBgi3tCzRUtrBG29%2BkSXNkVYE%2BOgRkOSE2XQkxwYIt7Qs0VLaxoA4mL%2FAhoAAn7B
Click Sign with nami shows: {code: -1, info: 'Inputs do not conform to this spec or are otherwise invalid.'}
Source code: https://github.com/ADAOcommunity/cardano-multi-sig-app/pull/25/files#diff-2ad0e9c5a24152a2381aff1cf48211765b5444dd71295b090a50db3b9625df96R461

Closed. The bug was on mine.


More Distributions

Adding the torch.distributions package, and about half of the implementations.

It's a big change - I took a look through all of it and didn't spot any problems


Invalid message _rpc_applicationUpdated

Relase 2014-02-14
Windows 8.1 cmd (Admin mode), apple iPhone 5, debug mode is on.
D:\System\ios-debug> ios-webkit-debug-proxy
device udid: f756a******************
called
sending 295 bytes
sending 4 bytes
sending 295 bytes
sent 295 bytes
initial read=4
297 bytes following
received 297 bytes
success with type com.apple.mobile.lockdown
initialized config_dir to C:\ProgramData\Apple\Lockdown
sending 4847 bytes
sending 4 bytes
sending 4847 bytes
sent 4847 bytes
initial read=4
239 bytes following
received 239 bytes
ValidatePair success
internal pairing mode
using 30377145-********************** as SystemBUID
sending 431 bytes
sending 4 bytes
sending 431 bytes
sent 431 bytes
initial read=4
354 bytes following
received 354 bytes
Session startup OK
SessionID: 185A6003-B1B9-4CA5-B166-26DF7ED5DF66
Enable SSL Session: true
SSL mode enabled, cipher: AES256-SHA
sending 339 bytes
sending 4 bytes
SSL_write 4, sent 4
sending 339 bytes
SSL_write 339, sent 339
sent 339 bytes
SSL_read 4, received 4
initial read=4
330 bytes following
SSL_read 330, received 330
received 330 bytes
success
has a value
sending 359 bytes
sending 4 bytes
SSL_write 4, sent 4
sending 359 bytes
SSL_write 359, sent 359
sent 359 bytes
SSL_read 4, received 4
initial read=4
343 bytes following
SSL_read 343, received 343
received 343 bytes
stopping session 185A6003-B1B9-4CA5-B166-26DF7ED5DF66
sending 374 bytes
sending 4 bytes
SSL_write 4, sent 4
sending 374 bytes
SSL_write 374, sent 374
sent 374 bytes
SSL_read 4, received 4
initial read=4
238 bytes following
SSL_read 238, received 238
received 238 bytes
success
SSL mode disabled
Invalid message _rpc_applicationUpdated: <dict>
        <key>WIRApplicationBundleIdentifierKey</key>
        <string>com.apple.mobilesafari</string>
        <key>WIRApplicationNameKey</key>
        <string>Safari</string>
        <key>WIRIsApplicationProxyKey</key>
        <false/>
        <key>WIRIsApplicationActiveKey</key>
        <integer>0</integer>
        <key>WIRApplicationIdentifierKey</key>
        <string>PID:699</string>
</dict>

@elennaro I experienced same behaviour with original iwdp utility, one-two replugs solved this for me

Thanks @artygus, but no luck with replugs.
Maybe I should delete ITunes?
The point is I have so small C/C++/Visual Studio that can't even compile last release (from git) on windows :(

@elennaro what iOS version is running on your device?

8.1.3 (12B466)

@elennaro trying to reproduce on win 7 with the same iOS version, no luck
i can see this error only when i press the home button leaving Safari Browser, hm..

@elennaro just made a test build that stubs this rpc message, check this out http://sourceforge.net/projects/ios-webkit-debug-proxy-win32/files/test-builds/ios-webkit-debug-proxy-win32-debug-rpc_stub.zip/download

@artygus thanks.
Now I see nothing but there is no connection to ios-debug-proxy from browser too.
The log is:
D:\System\ios-debug> ios-webkit-debug-proxy
device udid: f756a*************************************
called
sending 295 bytes
sending 4 bytes
sending 295 bytes
sent 295 bytes
initial read=4
297 bytes following
received 297 bytes
success with type com.apple.mobile.lockdown
initialized config_dir to C:\ProgramData\Apple\Lockdown
sending 4847 bytes
sending 4 bytes
sending 4847 bytes
sent 4847 bytes
initial read=4
239 bytes following
received 239 bytes
ValidatePair success
internal pairing mode
using 30377145-120370020653981736 as SystemBUID
sending 431 bytes
sending 4 bytes
sending 431 bytes
sent 431 bytes
initial read=4
354 bytes following
received 354 bytes
Session startup OK
SessionID: 307EC3BA-B598-4677-8631-E6049735A677
Enable SSL Session: true
SSL mode enabled, cipher: AES256-SHA
sending 339 bytes
sending 4 bytes
SSL_write 4, sent 4
sending 339 bytes
SSL_write 339, sent 339
sent 339 bytes
SSL_read 4, received 4
initial read=4
330 bytes following
SSL_read 330, received 330
received 330 bytes
success
has a value
sending 359 bytes
sending 4 bytes
SSL_write 4, sent 4
sending 359 bytes
SSL_write 359, sent 359
sent 359 bytes
SSL_read 4, received 4
initial read=4
343 bytes following
SSL_read 343, received 343
received 343 bytes
stopping session 307EC3BA-B598-4677-8631-E6049735A677
sending 374 bytes
sending 4 bytes
SSL_write 4, sent 4
sending 374 bytes
SSL_write 374, sent 374
sent 374 bytes
SSL_read 4, received 4
initial read=4
238 bytes following
SSL_read 238, received 238
received 238 bytes
success
SSL mode disabled

And that's is.
The phone itself is recognized by windows and even iTunes window appears each time I plug it in.

@elennaro may it be a windows firewall issue? could you you disable it for a minute?

@artygus I've turned off Windows Firewall.
Seems no luck again. The log is exactly as above, however iPhone shows again "Trust this PC" dialogue.

@elennaro when you navigate to localhost:9221 what do you see?

@artygus
Hm....
For: http://localhost:9221/
iOS Devices:

    localhost:9230 - Elennaro's iPhone

and for http://localhost:9230/
Inspectable pages for Elennaro's iPhone:
http://fellor.co/#/login  //that's no link to click further

@elennaro can you see the shield icon the right of the address bar?

@artygus Yes. shame on me!!!
Sorry for waiting your time with this last post!
Thank you so much for such good help!
It works smooth and clear!
Should I close this one?

@elennaro haha, no problem
yes, please


BUG: same feature column creates duplicate tensors for DNNLinearCombinedRegressor

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Mac OS X 10.11.6
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 1.3.0
Python version: 3.5.2
Bazel version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:
Exact command to reproduce:

Describe the problem
It seems that the same feature column creates two tensors for DNNLinearCombinedRegressor (see voc_embed in graph below). Is this the right behavior we expected?
The behavior stems from that feature column is processed by DNN and Linear independently, see code: dnn and linear
Source code / logs
# coding: utf-8
import tensorflow as tf
from tensorflow import feature_column as fc

f = fc.embedding_column(
        fc.categorical_column_with_vocabulary_list("voc", ["a", "b"]),
        dimension=8)
e = tf.estimator.DNNLinearCombinedRegressor(
        model_dir="/tmp/tf/test_dnn",
        linear_feature_columns=[f],
        dnn_feature_columns=[f],
        dnn_hidden_units=[10])

def input_fn():
    return ({"voc": tf.identity(
                        tf.constant(["a", "b", "a"], name="voc_input"),
                        name="identity")},
            tf.constant([1, 0, 1]))

e.train(input_fn, steps=10)

It doesn't look like ideal behavior, but perhaps it's not unexpected.  @ispirmustafa

yes. it's not ideal. we can improve it.

How about converting feature_column to _LazyBuilder at first, and the feeding _LazyBuilder to DNN and LR? I guess the solution could solve the problem (and is lightweight).

Oh, I forget the optimizer problem: if a tensor is owned by both DNN and LR network, does it bring conflict as the tensor is trained by two optimizer?

Hi, @ispirmustafa . Does anyone work on it? Do you have any good idea? Thanks.

Hi @facaiy ,
as you suggested using _LazyBuilder works. We should not open _LazyBuilder as a public API though.
also sending _LazyBuilder around will complicate the underlying functions.
If you find a way which does not complicate API, would be happy to review it.
nobody is working on it yet. contributions welcome.

Sure, I'd like to take a try. Thank you for explanation, @ispirmustafa .

It has been 14 days with no activity and this issue has an assignee.Please update the label and/or status accordingly.


caliper-core: add tests for assignedMessage

Checklist

[X]  A link to the issue/user story that the pull request relates to
[ ]  How to recreate the problem without the fix
[ ]  Design of the fix
[ ]  How to prove that the fix works
[X]  Automated tests that prove the fix keeps on working
[ ]  Documentation - any JSDoc, website, or Stackoverflow answers?

Issue/User story
Fixes part of #1557
Steps to Reproduce

Existing issues

[ ] Stack Overflow issues
[ ] GitHub Issues
[ ] Discord history

Design of the fix

Validation of the fix

Automated Tests

What documentation has been provided for this pull request

@aklenik Do you want to take a look ?

Sorry, I'm closing this PR due to some signoff issues at my end. Will be opening a new PR with the changes. Sorry for the  inconvenience caused.

Moved to #1561


sile: v<IP_ADDRESS> -> v0.10.3; adjust build process

Motivation for this change
New release of SILE upstream (announcement) has new dependencies and a different build system. Overall it should be easier to packages, but for this release cycle there are several changes.
Note I am not a Nix user, I am an upstream maintainer trying to facilitate this update. There are several things NOT done yet that I don't know how to fix:

[x] The ./configure command needs to be passed the --with-system-luarocks argument if, as in the current package, all the external Lua Rocks are being supplied by the package manager. Alternatively if it would be better for Nix not to bother with those and just have SILE bundle the deps itself, you can just drop all the Lua package deps and not pass this argument and it will bundle everything.
[ ] The man page should get packaged too, is it?

If there is anything else I can facilitate so this packages easily let me know.
Things done

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

[ ] 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"
[ ] 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] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I managed to build it with https://github.com/NixOS/nixpkgs/commit/3264166cc3db3356dd367a606f4e16c3526d016b, https://github.com/NixOS/nixpkgs/commit/acf4f8b6c8707a1acb5bf67131acd0311a31d1ff, and https://github.com/NixOS/nixpkgs/commit/2ca5d8ddfb3e73d8acfb36e228cacf505ba059bc
On darwin needs tweaks for https://github.com/NixOS/nixpkgs/issues/65351

@marsam Thanks for your work on this. Please instruct me if I'm doing something wrong handling this PR. I just rebased on master and cherry picked your commits.
Something doesn't seem right about the addition of compat53 in the Lua module list. That module is a collection of shims to add Lua 5.3 features to 5.2 and 5.1. Both the configure process and the runtime should know it is not needed in this  case.

Something doesn't seem right about the addition of compat53 in the Lua module list

it's required by configure for lua<5.3, and currently nixpkgs uses lua 5.2, if you don't want compat53 I think you can either patch configure.ac or use lua5_3
https://github.com/sile-typesetter/sile/blob/fba931a416b6f9118a096a170f78929e31a99595/configure.ac#L109-L111

@marsam My apologies, I thought Nix was at Lua 5.3. I have removed that commit as it was completely bogus.

I see CI has passed. Dose that mean anything?
From the upstream side the only remaining question I have about this is whether the man page ended up where it was supposed to. Otherwise I think it's up to you Nix folks to review and help check off the regular PR checklist ;-)
Thanks for the help everybody.

Thank you @alerque, I'm going to address the man page installation in another PR

@marsam It seems like make install is putting it in a standard location, so it might already be captured. Thanks again for all the help!


[turborepo] Cannot find module 'turbo' when using docker to build

What version of Turborepo are you using?
1.7.0
What package manager are you using / does the bug impact?
Yarn v1
What operating system are you using?
Mac
Describe the Bug
I have been using turbo repo and building my apps using docker and was working perfectly with v1.6.3 until 1.7.0 released, the turbo cli can't be found after doing yarn global add turbo on docker.
 => [installer 1/8] WORKDIR /app                                                                                0.2s
 => [runner 2/4] RUN addgroup --system --gid 1001 nodejs                                                                                3.1s
 => [builder 2/4] RUN yarn global add turbo                                                                                30.7s
 => [runner 3/4] RUN adduser --system --uid 1001 ***                                                                                2.0s
 => [installer 2/8] COPY .gitignore .gitignore                                                                                0.5s
 => [builder 3/4] COPY . .                                                                                7.3s
 => ERROR [builder 4/4] RUN turbo prune --scope=*** --docker                                                                     1.6s
------
 > [builder 4/4] RUN turbo prune --scope=*** --docker:
#17 1.472 /app/node_modules/turbo/bin/turbo:13
#17 1.472     throw e;
#17 1.472     ^
#17 1.472
#17 1.472 Error: Cannot find module 'turbo'
#17 1.472 Require stack:
#17 1.472 - /app/node_modules/turbo/node-platform.js
#17 1.472 - /app/node_modules/turbo/bin/turbo
#17 1.472     at Function.Module._resolveFilename (node:internal/modules/cjs/loader:985:15)
#17 1.472     at Function.resolve (node:internal/modules/cjs/helpers:109:19)
#17 1.472     at downloadedBinPath (/app/node_modules/turbo/node-platform.js:44:44)
#17 1.472     at generateBinPath (/app/node_modules/turbo/node-platform.js:67:15)
#17 1.472     at Object.<anonymous> (/app/node_modules/turbo/bin/turbo:7:5)
#17 1.472     at Module._compile (node:internal/modules/cjs/loader:1155:14)
#17 1.472     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1209:10)
#17 1.472     at Module.load (node:internal/modules/cjs/loader:1033:32)
#17 1.472     at Function.Module._load (node:internal/modules/cjs/loader:868:12)
#17 1.472     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) {
#17 1.472   code: 'MODULE_NOT_FOUND',
#17 1.472   requireStack: [
#17 1.472     '/app/node_modules/turbo/node-platform.js',
#17 1.472     '/app/node_modules/turbo/bin/turbo'
#17 1.472   ]
#17 1.472 }
------

Expected Behavior
Should be able to run turbo command RUN turbo ..... on docker after installing turbo
To Reproduce
Use this sample Dockerfile and build it
FROM --platform=linux/amd64 node:16.18-alpine AS base

RUN apk add --no-cache libc6-compat
RUN apk add --update --no-cache openssl1.1-compat
RUN apk update

WORKDIR /app
ARG SCOPE
ENV SCOPE=${SCOPE}

FROM base AS builder
# Set working directory
WORKDIR /app
RUN yarn global add turbo@${TURBO_VERSION}
COPY . .
RUN turbo prune --scope=${SCOPE} --docker

SCOPE is the app or package you want to build with docker
Reproduction Repo
No response

going backward with<EMAIL_ADDRESS>will solve the issue for now

Thanks for the report and repro! We'll take a look at this, it does appear to be a bug

Thanks for the report and repro! We'll take a look at this, it does appear to be a bug

Same thing with with-docker example

Hey, here's what appears to be going on.
You're copying your entire directory here: COPY . . which is going to include your node_modules/. Now, when you run turbo prune ..., it's going to (correctly) defer to your local turbo here because it does exist. However, because you copied from your local machine (mac), turbo will only have the turbo-darwin-64 package installed instead of the turbo-linux-64 package which it needs for alpine.
I'm going to take a look at a fix for this on our end. In the meantime you can unblock by either:

Removing your local turbo yarn remove turbo -W and letting the global turbo that you're installing in the container handle everything
Run a yarn install after the COPY . . so turbo can install the correct version for your new environment (not ideal as this will be slower)

@tknickman I'm having the same issue with with-docker example. Here is a log:

➜  code npx degit vercel/turbo/examples/with-docker with-docker
> cloned vercel/turbo#HEAD to with-docker
➜  code cd with-docker
➜  with-docker git init . && git add . && git commit -m "Init"
Initialized empty Git repository in /Users/igorbelogurov/code/with-docker/.git/
➜  with-docker git:(main) docker network create app_network
➜  with-docker git:(main) yarn install
➜  with-docker git:(main) COMPOSE_DOCKER_CLI_BUILD=1 DOCKER_BUILDKIT=1 docker-compose -f docker-compose.yml build
[+] Building 27.1s (19/41)
 => [with-docker-web internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 32B                                                                                0.0s
 => [with-docker-api internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 32B                                                                                0.0s
 => [with-docker-web internal] load .dockerignore                                                                                0.0s
 => => transferring context: 32B                                                                                0.0s
 => [with-docker-api internal] load .dockerignore                                                                                0.0s
 => => transferring context: 32B                                                                                0.0s
 => [with-docker-api internal] load metadata for docker.io/library/node:alpine                                                                                26.9s
 => [auth] library/node:pull token for registry-1.docker.io                                                                                0.0s
 => [with-docker-web installer  1/11] FROM docker.io/library/node:alpine@sha256:ab3603cb7934b21f1ffb522b1a1d538809516c6e4cd73b144716bc1830aad1a6                                      0.0s
 => [with-docker-api internal] load build context                                                                                23.4s
 => => transferring context: 300.52MB                                                                                23.3s
 => CACHED [with-docker-web runner 2/8] WORKDIR /app                                                                                0.0s
 => CACHED [with-docker-web runner 3/8] RUN addgroup --system --gid 1001 nodejs                                                                                0.0s
 => CACHED [with-docker-web runner 4/8] RUN adduser --system --uid 1001 nextjs                                                                                0.0s
 => [with-docker-web internal] load build context                                                                                23.7s
 => => transferring context: 300.52MB                                                                                23.6s
 => CACHED [with-docker-web installer  2/11] RUN apk add --no-cache libc6-compat                                                                                0.0s
 => CACHED [with-docker-web installer  3/11] RUN apk update                                                                                0.0s
 => CACHED [with-docker-web installer  4/11] WORKDIR /app                                                                                0.0s
 => CACHED [with-docker-web builder 5/7] RUN yarn global add turbo                                                                                0.0s
 => [with-docker-api builder 6/7] COPY . .                                                                                2.1s
 => ERROR [with-docker-api builder 7/7] RUN turbo prune --scope=api --docker                                                                                0.4s
 => CACHED [with-docker-web builder 6/7] COPY . .                                                                                0.0s
 => ERROR [with-docker-web builder 7/7] RUN turbo prune --scope=web --docker                                                                                0.3s
------
 > [with-docker-api builder 7/7] RUN turbo prune --scope=api --docker:
#0 0.310 /app/node_modules/turbo/bin/turbo:13
#0 0.310     throw e;
#0 0.310     ^
#0 0.310
#0 0.310 Error: Cannot find module 'turbo'
#0 0.310 Require stack:
#0 0.310 - /app/node_modules/turbo/node-platform.js
#0 0.310 - /app/node_modules/turbo/bin/turbo
#0 0.310     at Module._resolveFilename (node:internal/modules/cjs/loader:1053:15)
#0 0.310     at Function.resolve (node:internal/modules/helpers:118:19)
#0 0.310     at downloadedBinPath (/app/node_modules/turbo/node-platform.js:44:44)
#0 0.310     at generateBinPath (/app/node_modules/turbo/node-platform.js:67:15)
#0 0.310     at Object.<anonymous> (/app/node_modules/turbo/bin/turbo:7:5)
#0 0.310     at Module._compile (node:internal/modules/cjs/loader:1239:14)
#0 0.310     at Module._extensions..js (node:internal/modules/cjs/loader:1293:10)
#0 0.310     at Module.load (node:internal/modules/cjs/loader:1096:32)
#0 0.310     at Module._load (node:internal/modules/cjs/loader:935:12)
#0 0.310     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:84:12) {
#0 0.310   code: 'MODULE_NOT_FOUND',
#0 0.310   requireStack: [
#0 0.310     '/app/node_modules/turbo/node-platform.js',
#0 0.310     '/app/node_modules/turbo/bin/turbo'
#0 0.310   ]
#0 0.310 }
#0 0.310
#0 0.310 Node.js v19.4.0
------
------
 > [with-docker-web builder 7/7] RUN turbo prune --scope=web --docker:
#0 0.301 /app/node_modules/turbo/bin/turbo:13
#0 0.301     throw e;
#0 0.301     ^
#0 0.301
#0 0.301 Error: Cannot find module 'turbo'
#0 0.301 Require stack:
#0 0.301 - /app/node_modules/turbo/node-platform.js
#0 0.301 - /app/node_modules/turbo/bin/turbo
#0 0.301     at Module._resolveFilename (node:internal/modules/cjs/loader:1053:15)
#0 0.301     at Function.resolve (node:internal/modules/helpers:118:19)
#0 0.301     at downloadedBinPath (/app/node_modules/turbo/node-platform.js:44:44)
#0 0.301     at generateBinPath (/app/node_modules/turbo/node-platform.js:67:15)
#0 0.301     at Object.<anonymous> (/app/node_modules/turbo/bin/turbo:7:5)
#0 0.301     at Module._compile (node:internal/modules/cjs/loader:1239:14)
#0 0.301     at Module._extensions..js (node:internal/modules/cjs/loader:1293:10)
#0 0.301     at Module.load (node:internal/modules/cjs/loader:1096:32)
#0 0.301     at Module._load (node:internal/modules/cjs/loader:935:12)
#0 0.301     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:84:12) {
#0 0.301   code: 'MODULE_NOT_FOUND',
#0 0.301   requireStack: [
#0 0.301     '/app/node_modules/turbo/node-platform.js',
#0 0.301     '/app/node_modules/turbo/bin/turbo'
#0 0.301   ]
#0 0.301 }
#0 0.301
#0 0.301 Node.js v19.4.0
------
failed to solve: executor failed running [/bin/sh -c turbo prune --scope=web --docker]: exit code: 1
➜  with-docker git:(main) ✗

@bibblebabl thanks for the report, a fix is available here https://github.com/vercel/turbo/pull/3301, it's a quick one - just include node_modules in the examples root .dockerignore.
This was an oversight on our end originally, you should always be re-installing inside the container to ensure any platform specific dependencies (like turbo) get correctly installed.
@aindong this will fix your issue as well - add a .dockerignore with:
node_modules

That ensures the globally installed turbo won't defer to a local turbo that was installed on the wrong system.
You can find out more about turbo global vs local in our blog post https://turbo.build/blog/turbo-1-7-0#global-turbo

@bibblebabl thanks for the report, a fix is available here #3301, it's a quick one - just include node_modules in the examples root .dockerignore.
This was an oversight on our end originally, you should always be re-installing inside the container to ensure any platform specific dependencies (like turbo) get correctly installed.
@aindong this will fix your issue as well - add a .dockerignore with:
node_modules

That ensures the globally installed turbo won't defer to a local turbo that was installed on the wrong system.
You can find out more about turbo global vs local in our blog post https://turbo.build/blog/turbo-1-7-0#global-turbo

Thanks! sorry for late replying and checking this ticket, I can confirm that the solution above fixes the issue <3

FWIW I just ran into the same problem, adding the .dockerignore file fixed the Cannot find module 'turbo' error, but then I got this error:
[+] Building 115.5s (18/22)
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 37B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 52B                                                                                0.0s
 => [internal] load metadata for docker.io/library/node:alpine                                                                      0.7s
 => [internal] load build context                                                                                1.7s
 => => transferring context: 532.51kB                                                                                1.7s
 => CACHED [installer  1/11] FROM docker.io/library/node:alpine@sha256:ab3603cb7934b21f1ffb522b1a1d538809516c6e4cd73b144716bc1830a  0.0s
 => CACHED [runner 2/5] WORKDIR /app                                                                                0.0s
 => [runner 3/5] RUN addgroup --system --gid 1001 nodejs                                                                            0.4s
 => [installer  2/11] RUN apk add --no-cache libc6-compat                                                                           2.7s
 => [runner 4/5] RUN adduser --system --uid 1001 graphql                                                                            0.3s
 => [installer  3/11] RUN apk update                                                                                2.5s
 => [installer  4/11] WORKDIR /app                                                                                0.0s
 => [installer  5/11] COPY .gitignore .gitignore                                                                                0.0s
 => [builder 5/7] RUN yarn global add turbo                                                                                41.7s
 => [builder 6/7] COPY . .                                                                                1.1s
 => [builder 7/7] RUN turbo prune --scope=graphql-api --docker                                                                      0.4s
 => [installer  6/11] COPY --from=builder /app/out/json/ .                                                                          0.0s
 => [installer  7/11] COPY --from=builder /app/out/yarn.lock ./yarn.lock                                                            0.0s
 => ERROR [installer  8/11] RUN yarn install                                                                                66.1s
------
 > [installer  8/11] RUN yarn install:
#18 0.315 yarn install v1.22.19
#18 0.390 [1/5] Validating package.json...
#18 0.397 [2/5] Resolving packages...
#18 0.590 [3/5] Fetching packages...
#18 62.43 [4/5] Linking dependencies...
#18 62.44 warning "workspace-aggregator-91768be5-f176-4f58-a5a4-6d2f3c4a5cf5 > graphql-api ><EMAIL_ADDRESS>has unmet peer dependency "@prisma/client@*".
#18 62.44 warning "workspace-aggregator-91768be5-f176-4f58-a5a4-6d2f3c4a5cf5 > graphql-api ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>#18 62.44 warning "workspace-aggregator-91768be5-f176-4f58-a5a4-6d2f3c4a5cf5 > graphql-api ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>#18 62.44 warning "workspace-aggregator-91768be5-f176-4f58-a5a4-6d2f3c4a5cf5 > graphql-api ><EMAIL_ADDRESS>has unmet peer dependency "typescript@*".
#18 64.85 [5/5] Building fresh packages...
#18 65.28 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
#18 65.28 error /app/node_modules/bufferutil: Command failed.
#18 65.28 Exit code: 1
#18 65.28 Command: node-gyp-build
#18 65.28 Arguments:
#18 65.28 Directory: /app/node_modules/bufferutil
#18 65.28 Output:
#18 65.28 gyp info it worked if it ends with ok
#18 65.28 gyp info using<EMAIL_ADDRESS>#18 65.28 gyp info using<EMAIL_ADDRESS>| linux | arm64
#18 65.28 gyp ERR! find Python
#18 65.28 gyp ERR! find Python Python is not set from command line or npm configuration
#18 65.28 gyp ERR! find Python Python is not set from environment variable PYTHON
#18 65.28 gyp ERR! find Python checking if "python3" can be used
#18 65.28 gyp ERR! find Python - "python3" is not in PATH or produced an error
#18 65.28 gyp ERR! find Python checking if "python" can be used
#18 65.28 gyp ERR! find Python - "python" is not in PATH or produced an error
#18 65.28 gyp ERR! find Python
#18 65.28 gyp ERR! find Python **********************************************************
#18 65.28 gyp ERR! find Python You need to install the latest version of Python.
#18 65.28 gyp ERR! find Python Node-gyp should be able to find and use Python. If not,
#18 65.28 gyp ERR! find Python you can try one of the following options:
#18 65.28 gyp ERR! find Python - Use the switch --python="/path/to/pythonexecutable"
#18 65.28 gyp ERR! find Python   (accepted by both node-gyp and npm)
#18 65.28 gyp ERR! find Python - Set the environment variable PYTHON
#18 65.28 gyp ERR! find Python - Set the npm configuration variable python:
#18 65.28 gyp ERR! find Python   npm config set python "/path/to/pythonexecutable"
#18 65.28 gyp ERR! find Python For more information consult the documentation at:
#18 65.28 gyp ERR! find Python https://github.com/nodejs/node-gyp#installation
#18 65.28 gyp ERR! find Python **********************************************************
#18 65.28 gyp ERR! find Python
#18 65.28 gyp ERR! configure error
#18 65.28 gyp ERR! stack Error: Could not find any Python installation to use
#18 65.28 gyp ERR! stack     at PythonFinder.fail (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:330:47)
#18 65.28 gyp ERR! stack     at PythonFinder.runChecks (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:159:21)
#18 65.28 gyp ERR! stack     at PythonFinder.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:202:16)
#18 65.28 gyp ERR! stack     at PythonFinder.execFileCallback (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:294:16)
#18 65.28 gyp ERR! stack     at exithandler (node:child_process:427:5)
#18 65.28 gyp ERR! stack     at ChildProcess.errorhandler (node:child_process:439:5)
#18 65.28 gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
#18 65.28 gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:291:12)
#18 65.28 gyp ERR! stack     at onErrorNT (node:internal/child_process:483:16)
#18 65.28 gyp ERR! stack     at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
#18 65.28 gyp ERR! System Linux 5.15.49-linuxkit
#18 65.28 gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
#18 65.28 gyp ERR! cwd /app/node_modules/bufferutil
#18 65.28 gyp ERR! node -v v19.4.0
#18 65.28 gyp ERR! node-gyp -v v9.3.0
#18 65.28 gyp ERR! not ok
------
executor failed running [/bin/sh -c yarn install]: exit code: 1

Fixed it by changing
FROM node:alpine AS installer
RUN apk add --no-cache libc6-compat

to
FROM node:alpine AS installer
RUN apk add --no-cache libc6-compat python3 make g++


Fix issue #466 (bed12tobed6 handling -n parameter incorrectly)

Made the -n option not expect another string after it.
Also changed the comment saying that all options expect 2 strings.
See issue #466.

Thanks!


[Feature 12] Choose Features

Responsible for implementing user story 4 (creating the requisite controllers and presenters). Modifies the input data based on the 3 transformations that can be applied to either the x_1 and x_2 data points.

So, what do you think of adding just more points to the dataset, for example points right now are x,y and if you choose squared you add a points x^2,y

That is an excellent idea! I have another question for how to arrange the data for training. As it stands the output after applying the necessary features is the following (example: where only Y^2 feature is chosen);
[
[   // Original Dataset 1 (BLUE POINTS)
[x11, x12, x13, ...],  // x values
[y11, y12, y13, ...]   // y values
],
[   // Original Dataset 2 (ORANGE POINTS)
    [x21, x22, x23, ...],  // x values
    [y21, y22, y23, ...]   // y values
],
...
[   // Squared Dataset 1 (BLUE POINTS)
    [x11, x12, x13, ...],              // same x values
    [y11*y11, y12*y12, y13*y13, ...]   // squared y values
],
[   // Squared Dataset 2 (ORANGE POINTS)
    [x21, x22, x23, ...],              // same x values
    [y21*y21, y22*y22, y23*y23, ...]   // squared y values
]]

I could also arrange it in a IND Array as we spoke about yesterday. As this would be better suited for the Training Entity. Could write out an example of what that array would look like because I dont fully understand how it would be arranged.


Delta indexes sql_joined_field missing where table.delta = true

We have an index
_I am using apartment gem and modified thinking_sphinx/configuration.rb (sphinx_multiplier is merged again at config generation as this was causing issues of not hitting the right index multiplier - not the issue here)
indexes 'SELECT people.id sphinx_multiplier AS sid, positions.job_title AS person_position_job_title FROM people INNER JOIN positions ON positions.person_id = people.id GROUP BY sid, job_title ORDER BY sid', as: :person_position_job_title, source: :query

produces for core and delta
sql_joined_field = person_position_job_title from query; SELECT people.id * 66 + 2  AS sid, positions.job_title AS person_position_job_title FROM people  INNER JOIN positions ON positions.person_id = people.id GROUP BY sid, job_title ORDER BY sid

where as this should be for the _delta index definition:
sql_joined_field = person_position_job_title from query; SELECT people.id * 66 + 2  AS sid, positions.job_title AS person_position_job_title FROM people  INNER JOIN positions ON positions.person_id = people.id  **WHERE people.delta = true** GROUP BY sid, job_title ORDER BY sid

When running delta indexes it was taking forever as it was not having the WHERE people.delta = true   clause added

In my case i used "delta" as the column - so a quick hack was
  def build_sql_query
    @sql_query = builder.sql_query
    if delta?
      @sql_query += " WHERE #{model.quoted_table_name}.delta = true"
    end
    @sql_query_range ||= builder.sql_query_range
    @sql_query_pre += builder.sql_query_pre
  end

Thanks for reporting this @bkd.
I'm not quite sure how to best approach this though, given the field is based on a custom SQL string - adding in the logic to reliably parse SQL into Thinking Sphinx feels like a significant jump in complexity for what my gut suggests is an edge-case. Not that your case isn't valid, just that I don't think it's common.
If yourself or others can come up with a solution that doesn't involve the SQL parsing/manipulation, I'd love to hear about it! But at least for now, I'm to close this issue given I'm not going to do anything about it myself at this point in time.


Added error handling for when no data is found in importers.dicom()

I used RuntimeError because no existing exception (at least that I found) fits the situation. I also didn't really want to create a custom exception since that would be more complicated to catch for users.

Looks good! That being said, could you add support/error handling if there is a directory inside the directory that's passed to  the dir option. Right now, if the code detects a directory inside the directory that it is reading, it will crash out. Maybe that's the behavior that we want, but I'm thinking that it should probably just ignore any directories inside a directory and just read the files.

Added that check, also made it ignore non .dcm files while reading (there's an option to turn that off). I removed cases of catching and raising blank Exceptions so errors are more descriptive.


Endpoint for redemptions

Rebalancing was replaced by redemptions. Please create an endpoint that returns user related redemption info.
inputs - user address, collateral address/symbol, start timestamp
output - collateral sold, bnUSD repaid
similar to https://balanced.sudoblock.io/api/v1/docs#/stats/get_stats_rebalanced_api_v1_stats_rebalanced_get

Still valid and needed


chore: Move 210217 release notes to the correct path

@AbelHu , merging this PR because the change/fix is obvious and brings no harm, also we have AKS release notes relying on this release note.


Two check reports required?

see https://github.com/PhoenicisOrg/phoenicis/pull/2229

Checkstyle job
testtool

Would it be possible to combine this in one check report?

Wasn't aware that this is caused by the chosen reporter.


No Account data

When I use this library and run this standard code:
include_once('src/snapchat.php');
$username = "XXX"; // Your snapchat username
$password = "XXX"; // Your snapchat password
$gEmail   = "XXX"; // Gmail account
$gPasswd  = "XXX"; // Gmail account password
$debug = true; // Set this to true if you want to see all outgoing requests and responses from server
$snapchat = new Snapchat($username, $gEmail, $gPasswd, $debug);
$snapchat->login($password);
var_dump($snapchat->getFriends());

It returns an empty array and I'm not sure why because I have plenty of friends linked to that account. Upon login no errors are reported, a var_dump() of the login() function returns this:
array(2) { ["error"]=> int(0) ["data"]=> NULL }
There are also no snaps returned by the getSnaps() function. Why isn't any of my account data (friends snaps, etc...) showing up?

@CasualKyle can you post your debug log?

Sure can!
http://pastebin.com/raw.php?i=XXWRsyi6

Is it possible my IP has been blocked?

I have the same issue. I changed line 428 to read
if (is_object($jsonResult) && property_exists($jsonResult, "status") && $jsonResult->status == '-103')
but other than that, I have the same result (empty friends array).
The return value of the login() function is quite empty too:
Array
(
    [error] => 0
    [data] =>
)

I have the same issue too, I have posted it before and @mgp25 said it is possible that my IP has been blocked.
I'm using my local machine to run it, but it doesn't work. when I try to login using my android mobile connected to my wireless network it works.
I think it is the same IP address for my network,
Do you think there is some other reason for this issue?
Thank you

Same thing here, not sure what's going on.

Yes, it is because of the IP, if you don't get any result when logging in, then you are blocked, you should get a lot of info and updates.
Regards

But I'm running it on localhost, so it'd my local IP that is blocked? Pretty sure I can login from a phone using the same network.

@Voiceeeeee try with the latest code


Customizing The SignUp Route - Missing response.headers

Hello, I'm customizing my SignUp view w a "MyFancySignupForm" :)
I'm able to get my customer SignUpForm container to render, the problem is submitting the UserForm to Rails and then calling:
    dispatch({
      type: 'LOGGED_IN',
      payload: authToken
    });

The issue is my fetch signup request's response does not include the headers which are required to get the authToken within const auth = response.headers.get('Authorization');
I looked at what's happening in the react-devise library and I haven't been able to figure out what I'm doing wrong.. How is react-devise on SignUp Form Submit, getting the response.headers in the response?
Here's my code:
  handleSubmit(data) {
    const request = new Request('http://localhost:4300/auth/', {
     method: 'POST',
     headers: new Headers({
       'Accept'       : 'application/json',
       'Content-Type' : 'application/json',
     }),
     body: JSON.stringify({ user: data })
    });

    fetch(request).then(response => {
      return tryLogin(response, this.props.dispatch);
    });

const tryLogin = (response, dispatch) => {
  const auth = response.headers.get('Authorization');
  console.log(response.headers)

In the above, response.header is coming back {} even though in Chrome's network tab I see the response headers with the auth info react-devise needs.. Any help is appreciated.

Finally figured it out, I was submitting to the wrong port 4300. I did not realize I needed to post to node and not the rails endpoint like all my other APIs. Not sure why but it is working :)
Commenting above to hopefully help someone else in the future!


General board widgets have unused JOB_NAME filter enabled

Duplicates #1665, closing older one.
@vdelendik could you please add desired behavior?

JOB_NAME as enabled parameter appeared due to the inconsistency with params and labels...
By default after installing fresh system it should be disabled and located among "SHOW MORE" filters

Unable to reproduce in ui: 1.405-SNAPSHOT server: 1.593-SNAPSHOT client: 1.0-SNAPSHOT.


UI: Edit a button effect

Category

[ ] Documentation
[ ] Resource Addition
[ ] Codebase
[x] User Interface
[ ] Feature Request

Description
Hover effect would be added to github button under 'About' section.

Please assign me this issue under JWOC 2024.

Hey @madhurima316, there is a box shadow that is used as a hover effect to the 'GitHub' button and we want to keep it for now. So, we're closing this one.


[Bug] [golangci-lint] golangci-lint error messages need to be handled

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
golangci-lint throws error information
What you expected to happen
golangci-lint error messages need to be handled
How to reproduce

commit PR

Anything else

Version
main
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Will fix it next week

Will fix it next week

good~

fixed


Scene Tree's Move Up/Down shortcuts don't work when remapped to ALT + Up and ALT + Down.

Godot version
3.4.2
System information
Windows 10
Issue description
I wanted to map the Scene Tree's Move Up and Move Down shortcuts from CTRL + Up and CTRL + Down to use ALT + Up and ALT + Down, since it's what I've been comfortable with to in the Script Editor, as well as being a common shortcut in the programs I've worked with.
Doing this doesn't work, despite there being no conflicting key combinations that may make this malfunction, at least not that I know of.
Mapping them to ALT + Keypad Add/Subtract works as expected.
Mapping them to CTRL + any other key works as expected.
Mapping them to use SHIFT, or just simply NOT including CTRL seems to cause problems.
Mapping other, "single use" shortcuts in the Scene Tree to use ALT instead of CTRL works as expected.
Steps to reproduce

Create a new Scene containing two or more Nodes;
Focus on the Scene Dock and, with the default mapping to CTRL + Up/Down, test the shortcut;
Now, go to the Editor Settings, then Shortcuts, and change Move Up and Move Down to not include the CTRL modifier;
E.g. Keypad Add, Keypad Subtract, Alt + UP, Shift + Down...
Focus on the Scene Dock again, test the shortcuts. They should not work.
Go to Editor settings again, change these shortcuts to ALT + Keypad Add/Subtract.
Test the shortcuts again. They should work just fine.

Minimal reproduction project
I don't believe there's need.

Can you reproduce this on the master branch? You can download a nightly build here

This also occurs in latest, with the addition that mapping the shortcuts to singular keys (for instance any of the Keypad keys) without modifiers no longer seems to work.


feat: Handle the Repositories  more than 1000

I have refactored the code and added another method to handle the time slots separately.

Did you find a solution for datetime range problem? You mentioned, that the current implementation does not cover the whole time slot defined in configuration file.


Add fixes for datacollector and dataprovider

Changes

Comments

#396  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @forstmeier and the rest of your teammates on  Graphite


Replace conda logo PNG images with SVG files

This pull request replaces two PNG files for the two types of conda logos present on the website with their SVG equivalents.

That view came from resizing my desktop in two columns. I guess it should be hidden at a certain viewport.

That view came from resizing my desktop in two columns. I guess it should be hidden at a certain viewport.

Oh no, I previewed this deployment in my phone and noticed that

Thanks for the feedback all. Yeah, I notices those imperfections as well. If any one has better SVG skills than I do, please feel free to update this in a subsequent pull request.


Documentation issue

The extract tags processor example in the docs does not work https://gnmic.openconfig.net/user_guide/event_processors/event_extract_tags/
processors:
  # processor name
  sample-processor:
    # processor type
    event-extract-tags:
      value-names:
        - `/(\w+)/(?P<group>\w+)/(\w+)`

The regex contains backticks that throw an error
failed loading config file: While parsing config: yaml: line 48: found character that cannot start any token
Error: no subscriptions or inputs configuration found

Remove the backticks and it works.
Also can I suggest more examples for the feature. I am struggling to understand how it works.

Thanks for reporting this, will fix it.
The example is pretty much the only use of this processor. It was added to allow extracting parts of a path and use them as tags. Some Arista routers send keys as path elements for certain paths.
It uses regex named capture groups. Matching named capture groups are added as tags to the outgoing event message.
The example in the docs extracts the second path element of each path (statistics in the suggested input) and sets it as tag with name group.


[RFC] Refactor btree in metanode

This patchset refactors the usage of btree in metanode:

remove unnecessary clone of tree
rename helper functions to show its semantic apparently, like renaming GetTree to CloneTree
change metanode.BtreeItem to a new interface which inherits from btree.Item
avoid modifying the original btree module
introduce version to metanode.Btree and implementations of metanode.BtreeItem
introduce GetForRead and GetForWrite for metanode.Btree

GetForWrite is responsable for COW. Here is how we do COW:

tree.ver = 1, items_in_tree.ver = 1
oldTree = CloneTree(tree) => oldTree.ver = 1, tree.ver = 2, they share all items
tree.GetForWrite(key)
3.1 item_in_tree.ver != tree.ver
3.2 new_item = copy(item_in_tree)
3.3 new_item.ver = tree.ver
3.4 ReplaceOrInsert(new_item) => oldTree keeps old item, while tree has new_item
3.5 return new_item
oldTree.GetForRead(key) => item_in_oldTree.ver = 1

Received, we will review the code as soon as possible. @awzhgw @xiangcai1215


Fix "trackers still on" when closing via tray

When the user chooses to minimize the app to the system tray and tries to exit the app, the "Trackers still on" warning would still appear even if all trackers were disconnected. Updates the tray code to filter the trackers correctly.
Also adds v0.13.2 to the metainfo xml file
Fixes #1264.

So I DID find an actual bug! Nice- Oh, and it does work :3

Haha yeah, I was very confused and tried literally every single possible combination to reproduce it and couldn't. Ended up looking into the code itself and found the inconsistency

This shouldn't be needed. Why are there still trackers timed out in the list even if it's properly disconnected? We don't necessarily need to show the warning, but it feels like just timed out should still be considered as "connected".

Idk, I mean, all I do is flick the power switch to turn off the official slimes and... Yeah...


MINOR: KStreams SuppressionDurabilityIntegrationTest should set StreamsConfig.STATE_CONFIG_DIR.

This sets StreamsConfig.STATED_DIR_CONFIG to temp directory in KStreams SuppressionDurabilityIntegrationTest, to match StreamsTestUtils.
This is a similar fix to #5826.

Ah, sorry about that (again). LGTM.

retest this please

LGTM.
Test failure is kafka.api.SaslPlaintextConsumerTest.testCoordinatorFailover, not related.

retest this please

retest this please

retest this please

retest this please


Migration SQL throws error

I followed the tutorial and noticed the migration script for EF core throws exception. why?
rm -r Migrations
dotnet ef migrations add InitialCreate
after set connection string to production database in azure SQL using powershell or cmd, attempted to update database.
 dotnet ef database update
Here is the result:
Build started...
Build succeeded.
info: Microsoft.EntityFrameworkCore.Infrastructure[10403]
Entity Framework Core 3.1.3 initialized 'MyDatabaseContext' using provider 'Microsoft.EntityFrameworkCore.Sqlite' with options: None
System.ArgumentException: Format of the initialization string does not conform to specification starting at index 0.
at System.Data.Common.DbConnectionOptions.GetKeyValuePair(String connectionString, Int32 currentPosition, StringBuilder buffer, Boolean useOdbcRules, String& keyname,
String& keyvalue)
at System.Data.Common.DbConnectionOptions.ParseInternal(Dictionary2 parsetable, String connectionString, Boolean buildChain, Dictionary2 synonyms, Boolean firstKey)
at System.Data.Common.DbConnectionOptions..ctor(String connectionString, Dictionary`2 synonyms, Boolean useOdbcRules)
at System.Data.Common.DbConnectionStringBuilder.set_ConnectionString(String value)
at Microsoft.Data.Sqlite.SqliteConnectionStringBuilder..ctor(String connectionString)
at Microsoft.EntityFrameworkCore.Sqlite.Storage.Internal.SqliteDatabaseCreator.Exists()
at Microsoft.EntityFrameworkCore.Migrations.HistoryRepository.Exists()
at Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.Migrate(String targetMigration)
at Microsoft.EntityFrameworkCore.Design.Internal.MigrationsOperations.UpdateDatabase(String targetMigration, String contextType)
at Microsoft.EntityFrameworkCore.Design.OperationExecutor.UpdateDatabaseImpl(String targetMigration, String contextType)
at Microsoft.EntityFrameworkCore.Design.OperationExecutor.UpdateDatabase.<>c__DisplayClass0_0.<.ctor>b__0()
at Microsoft.EntityFrameworkCore.Design.OperationExecutor.OperationBase.Execute(Action action)
Format of the initialization string does not conform to specification starting at index 0.

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

ID: df55b676-8ff7-1470-3525-d0edfd406af6
Version Independent ID: ac264c26-7196-870b-760f-94a97ae437e8
Content: Tutorial: ASP.NET Core with Azure SQL Database - Azure App Service
Content Source: articles/app-service/tutorial-dotnetcore-sqldb-app.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@farjaf  Thanks for the question! We are investigating and will update you shortly.

farjaf, Apologies for the delay!   Kindly review the Connection String value for correctness. the local development environment uses a Sqlite database file, and the Azure production environment uses a connection string from App Service. With Active Directory authentication, you want both environments to use the same connection string. In appsettings.json, replace the value of the MyDbConnection connection string with:
"Server=tcp:<server-name>.database.windows.net;Authentication=Active Directory Device Code Flow; Database=<database-name>;"
For ASP.NET Core, setting connection strings in App Service are like setting them in  in Web.config, but the values you set in App Service override the ones in Web.config. Kindly review the value here - Configure connection strings.
At runtime, connection strings are available as environment variables, prefixed with the following connection types:
SQLAzure: SQLAZURECONNSTR_
Custom: CUSTOMCONNSTR_

Thanks Ajay,
I've already achieved the result with updating the connection string to Azure SQL but when followed the tutorial to update the connection string before sql migration I suspect it caused the issue. I tried both Powershell and CMD. Any ideas? also why we need to update from environmental variables?
(Below from tutorial)
Set connection string to production database
PowerShell
$env:ConnectionStrings:MyDbConnection="<connection-string>"
CMD (no quotes)
set ConnectionStrings:MyDbConnection=<connection-string>
Bash (no quotes)
export ConnectionStrings__MyDbConnection=<connection-string>
Thanks


Automower Aspire status change to fault after a while

Prerequirements
[ ] I have connected my mower(s) to the Automower Connect App
[ ] I have connected my Husqvanra developers account to the Authentication API
[ ] I have connected my Husqvarna developers account to the Automower Connect API
Describe the bug
The vacuum.automower_aspire says fault after a while when it's docked, but there isn't a fault.
When the automower finished, it goes back to the docking station. then the status changed in docked.
after a while it says fault(fout) but it hasn't any fault.
Screenshots

Can you share the device diagnostics, when the mower is in fault state?

It looks like that the fault has something to do with GPS coördinates. Because the automower aspire r4 has no gps.
Home assistant is trying to fetch the gps dat with no succeed, then it gives the error in the log

Is it possible to create an option to disable gps function in home assistant?

Ah okay. Never thought about an mower without GPS. I think I can do it automatically. But can you share the device diagnostics? You can find it in the integrations overview, when you click on your mower device. That makes it easier to code.

Can you try the new beta version 2023.5.1b5?
The missing GPS should be fixed. But maybe there are still some other issues

Sorry, i couldn't add text file on my phone yesterday.
Should i manually copy the new files?
Normally i update through hacs

You can update through hacs. Just activate the button for showing beta versions

It looks like, it's fixed. Maybe you could also automatically detect if the mower has headlights or nog, when i change headlight it gave me an error also

Unfortunately, it is not fixed, it gives errors about gps.
Deze fout is ontstaan door een aangepaste integratie.
Logger: aiohttp.server
Source: custom_components/husqvarna_automower/calendar.py:68
Integration: Husqvarna Automower (documentation, issues)
First occurred: 13:43:56 (1 occurrences)
Last logged: 13:43:56
Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request
resp = await request_handler(request)
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 85, in security_filter_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 227, in forwarded_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 80, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 235, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 146, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/calendar/init.py", line 542, in get
calendar_event_list = await entity.async_get_events(
File "/config/custom_components/husqvarna_automower/calendar.py", line 134, in async_get_events
return await self.async_get_events_data(hass, start_date, end_date)
File "/config/custom_components/husqvarna_automower/calendar.py", line 68, in async_get_events_data
lat = mower_attributes["positions"][0]["latitude"]
IndexError: list index out of range

Yes I've fixed this already here #461.
I can also do the headlight stuff the next days.

Can you copy the changes of #461 manually for a test, or should I create a new release?

Release is out

Can you check if in version 2023.5.1b7 the headlight_mode entity is  not generated anymore. It's probably still in your device, but orphaned.

Yes the headlight mode is gone, i still have status fault sometimes, i cannot see it anymore in the logs

Send me the device diagnostics when the mower is in fault mode

I cannot download the diagnostic now, it won't download
This i see in the logs
Deze fout is ontstaan door een aangepaste integratie.
Logger: aiohttp.server
Source: custom_components/husqvarna_automower/diagnostics.py:25
Integration: Husqvarna Automower (documentation, issues)
First occurred: 16:19:00 (1 occurrences)
Last logged: 16:19:00
Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request
resp = await request_handler(request)
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 85, in security_filter_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 227, in forwarded_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 80, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 235, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 146, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/diagnostics/init.py", line 246, in get
data = await info.config_entry_diagnostics(hass, config_entry)
File "/config/custom_components/husqvarna_automower/diagnostics.py", line 25, in async_get_config_entry_diagnostics
"data_of_all_mowers": async_redact_data(coordinator.data["data"], TO_REDACT),
TypeError: 'NoneType' object is not subscriptable

That's strange, because I didn't changed anything there. Can you delete line 14 in the diagnostics.py, restart ha and try it again?

Yes i did but it doesn't work, it still can't download diagnostics, it says failed

Okay. What's the error message?
As an alternative you can turn on debug logging and submit me the part the part which automower.session returns.

Here is a part of the log
aioautomower log.txt

This is what i can see if i check the state and compare it to the same time in the logs
Fault state:
2023-05-25 14:49:37.622 DEBUG (MainThread) [aioautomower.session] Got status-event, data: {'id': '7f6d468c-3a40-4e2d-87d1-7fb3841a4462', 'type': 'status-event', 'attributes': {'battery': {'batteryPercent': 100}, 'mower': {'mode': 'MAIN_AREA', 'activity': 'PARKED_IN_CS', 'state': 'STOPPED', 'errorCode': 0, 'errorCodeTimestamp': 0}, 'planner': {'nextStartTimestamp':<PHONE_NUMBER>000, 'override': {'action': 'IPLANNER_OVERRIDE_ACTION_NOT_ACTIVE'}, 'restrictedReason': 'SENSOR'}, 'metadata': {'connected': True, 'statusTimestamp':<PHONE_NUMBER>531}}}
Docked state:
2023-05-25 13:14:12.029 DEBUG (MainThread) [aioautomower.session] Got status-event, data: {'id': '7f6d468c-3a40-4e2d-87d1-7fb3841a4462', 'type': 'status-event', 'attributes': {'battery': {'batteryPercent': 95}, 'mower': {'mode': 'MAIN_AREA', 'activity': 'CHARGING', 'state': 'RESTRICTED', 'errorCode': 0, 'errorCodeTimestamp': 0}, 'planner': {'nextStartTimestamp':<PHONE_NUMBER>000, 'override': {'action': 'IPLANNER_OVERRIDE_ACTION_NOT_ACTIVE'}, 'restrictedReason': 'SENSOR'}, 'metadata': {'connected': True, 'statusTimestamp':<PHONE_NUMBER>863}}}

You could maybe check also the activity, because the activity stays the same, parked in cs

Hm, I just saw the activity was checked before. So the state in the above example should actually be docked
https://github.com/Thomas55555/husqvarna_automower/blob/7fa28854c9b773f570d945ed24b4a9a31fbb30cf/custom_components/husqvarna_automower/vacuum.py#L108

But PARKED_IN_CS should already return STATE_DOCKED. Independently if the mower is stopped or not. So I can't find the problem. But wit the latest beta the download of the diagnostics should work again. Maybe you can download it again, when the mower is in fault mode. Maybe a mistake happend somewhere.

config_entry-husqvarna_automower-e5b434b00103e0c37ebc6f85df257e6e.json.txt

The problem is still not fixed, with the beta 8 version it still gives sometimes a fault when the mower is at the docking station

In what state was the mower, when you created the diagnostics file?
Because in this time, it was not PARKED_IN_CS but the activity was NOT_APPLICABLE.
And I can't just track weather the state is STOPPED, according to the docs (https://developer.husqvarnagroup.cloud/apis/automower-connect-api#openapi), stopped is more like an error:
STOPPED - Mower is stopped, and cannot be started remotely. Start requirements (safety or other) are not fulfilled.

Log 01-06-2023.txt
at the time of 6:49 it changed into fault. see the log. maybe because it still tries to do an "get position" event?

No. It's just because of the state STOPPED
Did the mower stated working again, without that you did anything at the mower?

Yes after an hour of 2 it change back to docked or when the mower starts with mowing schedule, do you need all logs of today?

No. I'll write an email to Husqvarna the next days and ask them for support.

With update 2023.6.1 beta the fault is unfortunately not gone.

Yes. I didn't changed anything regarding this. But I wrote an email to Husqvarna yesterday and asked for support.

I've an answer from Husqvarna now. This is an known bug with this mower. There will be an firmware update for your mower in two weeks, which fixes the bug. After installing the FOTS update, it should work.
Let me know the result.

Okay, i wait until then and let you know, thanks for your effort

We installed the new firmware update for the mower last friday.
Now the mower stays docked, there is no fault anymore in home assistant, only if there is a real fault.
Thanks for your effort!


Port QEMU guest agent to ARM64 for Windows

Hello! Just want to let you know that we are very interested in this feature :blush:


Release the latest version in Marketplace

What you want to add
I would appreciate it if you could update the version of this workflow that resolves PR #165
Why this is needed
Because I am a heavy user of this project :)

@HelloRusk Hi, I forgot to create a release :pray: Published v2.0.2 and overrode v2 with v2.0.2.

Thank you!


How to customize/disable facade/ignition?

facade/ignition debugbar

still do not highlight LINE where errors happened. White on white. Old panel did it "black on black"

by some reason it forces bootstrap for 12 cols with 70 rem max-width. seriosly, i have 2560 monitor and have to F12 each time to remove max-width property? Damn, it preffers to cut filenames because left sidebar is smaller than class names!!!

where is the FUNCTION ARGUMENTS of each step?

Who decide to install it in Laravel by default?

First of all, it may be because of cultural differences, but your writing seems very aggressive.
If the view isn't optimized for 2560 monitor, I guess the maintainer doesn't have that. Please always feel free to send pull requests if you know how to make something better or pay a developer to solve those issues for you.
If you just want to remove the package (as written in the issue title) run
composer remove facade/ignition on the command line.
And last but not least: this is the repository for the laravel framework. encountered issues should always be reported to the package that causes it. So for the third party package in this case you can use this one to report bugs.

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.

Once the capital will give you for 3 years along only 300 euros and nobody wants to listen, you understand that "cultural difference" :D
I was angry about replacing old ignition that gives nothing except hiding db password for these guys who upload on production with DEBUG=true.
i'd like to see removed all the debug panels because old one was hardcoded, but facade\ignition replaces filp\whoops. i trieds to launch whoops manually - theres no method "catch" or something, i need to explore whole handler laravel module to understand that "handlers" flow.
i still dont understand how to configure or how it works, and yes, when i remove both of debug bars inside "App\Handler.php" - it works as expected.
i think its bad way - installing libraries that does "something" like "we expect" instead of well configurable

Beautiful - composer remove facade/ignition works as expected. Clean. Now I don't get false-positive security vulnerability warnings every time there's an exception during development :grin:


volume creation fails when datastore name is having embedded spaces e.g. "datastore (1)"

Steps to reproduce:

rename existing datastore which is not having spaces e.g. datastore => datastore (1)
invoke volume creation (docker volume create --driver=vmdk --name=MyVol22334 -o size=1gb)

Expectation: volume creation should succeed
Note: having spaces in datastore name is a valid name in vc context; while adding ESXs to VC which is having same datastore name; VC renames datastore by appending '(N)' for later ESX automatically
Current result: volume creation is failing with following outcome
-----------from console---------------
# docker volume create --driver=vmdk --name=MyVol22334 -o size=1gb
Error response from daemon: create MyVol22334: VolumeDriver.Create: Failed to create /vmfs/volumes/datastore (1)/dockvols/MyVol22334.vmdk. /bin/sh: syntax error: unexpected "("

-------from docker-volume-vsphere.log -------------
2016-12-13 20:34:06.835956871 +0000 UTC [ERROR] Create volume failed error="Failed to create /vmfs/volumes/datastore (1)/dockvols/MyVol22334.vmdk. /bin/sh: syntax error: unexpected \"(\"\n" name=MyVol22334

on ESX side:
----------from vmdk_ops.log ----------
12/13/16 20:34:06 2663252 [photon2-[datastore (1)] dockvols/MyVol22334.vmdk] [INFO   ] executeRequest 'get' completed with ret={u'Error': 'Volume MyVol22334 not found (file: /vmfs/volumes/datastore (1)/dockvols/MyVol22334.vmdk)'}
12/13/16 20:34:06 2663252 [photon2-[datastore (1)] dockvols/MyVol22334.vmdk] [INFO   ] *** createVMDK: /vmfs/volumes/datastore (1)/dockvols/MyVol22334.vmdk opts = {u'size': u'1gb', u'fstype': u'ext4'}
12/13/16 20:34:06 2663252 [photon2-[datastore (1)] dockvols/MyVol22334.vmdk] [INFO   ] executeRequest 'create' completed with ret={u'Error': 'Failed to create /vmfs/volumes/datastore (1)/dockvols/MyVol22334.vmdk. /bin/sh: syntax error: unexpected "("\n'}

created volumes are not viewable so pulling into 0.12 release. If user happens to rename the datastore with embedded namespace, it will run into following issue.
using admin cli:
[root@sc-rdops-vm07-dhcp-193-230:~] /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py ls
Invalid destination specification:
vmkfstools: (1)/dockvols/f7d20fb8-ead2-4327-ad6f-066c82a76930/dockerVol_1486430383.vmdk: No name specification expected.
Failed to stat /vmfs/volumes/vsanDatastore (1)/dockvols/f7d20fb8-ead2-4327-ad6f-066c82a76930/dockerVol_1486430383.vmdk. VMDK corrupted. Please remove and then retry

The following is the test steps and results.

two volumes have been created in datastore "tmp(datastiore1)"
rename the datastore name to "tmp (datastore1)" (add a space in the datastore name)
run "docker volume ls"

root@photon-eZ5ILvREQ [ ~ ]# docker volume ls
DRIVER              VOLUME NAME
vmdk                vol1@tmp- (datastore1)
vmdk                vol2@tmp- (datastore1)

run "docker volume create" to create a new volume "vol3"

root@photon-eZ5ILvREQ [ ~ ]# docker volume create --driver=vmdk --name=vol3 -o size=100MB
vol3

run "docker volume ls" again, which list all three volumes.

root@photon-eZ5ILvREQ [ ~ ]# docker volume ls
DRIVER              VOLUME NAME
vmdk                vol1@tmp- (datastore1)
vmdk                vol2@tmp- (datastore1)
vmdk                vol3@tmp- (datastore1)


feat: Adds dotnet release tool

replaces the python publish reporter release tool from  .net release tool.

Hi @jskeet ,
I 've addressed the first round of review comments. Please have a look and share your valuable feedback.
Thanks,


Add gzip encoding for HTTP requests

Apply this for each request by appending this to the default header: Accept-Encoding: gzip

Example at Go SDK:

Header: https://github.com/conductor-sdk/conductor-go/blob/main/sdk/settings/http_settings.go#L29
Decompress: https://github.com/conductor-sdk/conductor-go/blob/main/sdk/client/api_client.go#L610-L618