Multiple Warnings from 'StyleCopTask' task

When pulling and building the source, I have multiple of the below error.

Severity
Code
Description
Project
File
Line
Suppression State

Error

The "StyleCopTask" task could not be loaded from the assembly C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild..\StyleCop 4.7\StyleCop.dll. Could not load file or assembly 'file:///C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\StyleCop 4.7\StyleCop.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the  declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.
XboxWdpDriver
C:\Program Files (x86)\MSBuild\StyleCop\v4.7\StyleCop.targets
98
Error

Full build log below from re-build build.txt

@WilliamsJason - is there a way to make stylecop optional in this project? I believe it's optional for the rest of the solution.
@ryzngard - this should just work, we point to the StyleCop via the registry, can you check this key? HKLM\Software\CodePlex\StyleCop TargetsDir ? Looks like it's finding your Enterprise install of VS 2017 and then not finding Stylecop.  Might just have to install it.

I thought we'd made it optional :/
@MattHyman was mentioning you can add StyleCop as a NuGet dependency. We should switch to that, it should avoid forcing people to manually install it (or not install it and miss warnings that we should be fixing).

I tried the nuget version, at least for me it did not work with the UWP projects.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Jason Williams<EMAIL_ADDRESS>Sent: Thursday, November 30, 2017 10:21:33 AM
To: Microsoft/WindowsDevicePortalWrapper
Cc: Matt Hyman; Mention
Subject: Re: [Microsoft/WindowsDevicePortalWrapper] Multiple Warnings from 'StyleCopTask' task (#277)
I thought we'd made it optional :/
@MattHymanhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmatthyman&data=02|01|mathy%40microsoft.com|f291764b3e734f066afb08d5381f3236|72f988bf86f141af91ab2d7cd011db47|1|0|636476628993791881&sdata=%2F3f7JmbITITVtFzO9wbr55jywGrcr8EUd6eRjm%2FNuJA%3D&reserved=0 was mentioning you can add StyleCop as a NuGet dependency. We should switch to that, it should avoid forcing people to manually install it (or not install it and miss warnings that we should be fixing).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FWindowsDevicePortalWrapper%2Fissues%2F277%23issuecomment-348275783&data=02|01|mathy%40microsoft.com|f291764b3e734f066afb08d5381f3236|72f988bf86f141af91ab2d7cd011db47|1|0|636476628993791881&sdata=JFqwqnYtlfXvV1CAZab6gNYIRWAG%2BGm2O642Cj%2FyuPk%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABc0Y1sZVrbTX-Nsz5mgDo_8u5ykMNdVks5s7vItgaJpZM4Qk28a&data=02|01|mathy%40microsoft.com|f291764b3e734f066afb08d5381f3236|72f988bf86f141af91ab2d7cd011db47|1|0|636476628993791881&sdata=s9P10CWiu2KK5fFnGyDVQ9v%2Fy01RMn2OgekGQ2u378k%3D&reserved=0.

I'm going to turn off StyleCop build integration. Maybe we can eventually sort out the NuGet package but for now everyone running StyleCop will need to run it via 'Tools->Run StyleCop' since the build integration seems to be having issues when StyleCop is installed.


add missing level

Docs Build status updates of commit 45df628:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sysinternals/bread/toc.yml
:white_check_mark:Succeeded

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

Docs Build status updates of commit 6d9bb2b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sysinternals/bread/toc.yml
:white_check_mark:Succeeded

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

Docs Build status updates of commit 7a044a3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sysinternals/bread/toc.yml
:white_check_mark:Succeeded

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

This breadcrumb looks better than what's live right but still doesn't render some of the children topics and I'm not if it's because they're not actually in that hierarchical path for this to work. Probably removing some of the children here would make this work better.

Can you merge @lukekim? I don't have permissions.


Add transfer command

What :computer:
Why :hand:
Evidence :camera:

Notes :memo:

@ronibarylko please, make sure to fill the PR description template


Constructor body context is not set properly

IntelliJ IDEA developer here.
In AbstractConstructorClassProcessor you use
constructor.withBody(PsiMethodUtil.createCodeBlockFromText(blockText.toString(), psiClass));

Please try using constructor as the context instead of psiClass. This should make resolve within the constructor body working.
Why this matters?
Some IDEA inspections (e.g. Redundant assignment) analyze constructor bodies, including your generated constructor. While you generate it as this.field = field;, the context is set to the class, not to the constructor, thus right-hand field is not resolved to constructor parameter, but resolved to the field, so this assignment looks bogus to analyzer and it can make wrong conclusions.
Example:
@AllArgsConstructor
public final class Test {
  private int age = 10; // this assignment should be marked as redundant
}

The field initialization should be marked as redundant, as the field is always reassigned in synthetic constructor. However inspection doesn't mark it, because it thinks that field is used in the constructor before assignment.
Note that I did not test whether my suggestion works, but in general all generated method bodies should have the corresponding method as the context.

@amaembo Thank you Tagir! Didn't know full value of context. The next plugin build will contain your suggested fix.


Cannot find pico-debug DAP adapter with list command using Ubuntu

Hello,
I cannot find the pico debug adapter (https://github.com/majbthrd/pico-debug) using pyocd list on Ubuntu. Using windows the adapter appears just fine. I use the latest version of pyocd on both operating systems.
What am I doing wrong or has anyone else issues like this?
Regards, Christian

Try run pyocd list with sudo?

Try run pyocd list with sudo?

I did. No other result. I also added the product/vendor ID to the udev file. The board appears when i run lsusb. So it is found by the OS basically.


Prune tx

Description

Checklist

[x] Targeted PR against correct branch.
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[x] Wrote unit tests.
[ ] Re-reviewed Files changed in the Github PR explorer.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@7142fbf). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #103   +/-   ##
=========================================
  Coverage          ?   68.31%
=========================================
  Files             ?       29
  Lines             ?     1256
  Branches          ?        0
=========================================
  Hits              ?      858
  Misses            ?      370
  Partials          ?       28

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 7142fbf...03652bc. Read the comment docs.


z-slider bar issue

It seems the number of z-sliders cannot keep correct if the pixel size is set small.
After reshaping the stack, the z-slider number is 0-39 when the image number is 40. (this is produced with Raw_img_stack_512_axial.tif)

But after 'Select image layer', it shows as 0-38 when the pixel size is changed from 6.5 to 5.5um.

The z-slider number goes back to 0-39 when the pixel size is set as 7um.

This issue also shows the dependence on the system. It can be produced by a windows with the pixel size of 5.5 um or smaller, a windows with 5.45 or smaller and a Mac.
The rescaleZ function is to do with the pixel size. And the issue could be a rounding error in calculating the number of steps in z somewhere.

Hi @Meizhu-Liang, thanks for pointing this out.
I believe it is a napari issue and I posted a question on imagesc.
In the meantime, I double-checked and I can confirm that it is a visualization issue only, the data shape is not affected.
I'll fix it as soon as I have news from the napari developers

Thanks for updating me the issue.
Best regards,
Meizhu
From: Andrea @.>
Sent: 09 June 2022 17:13
To: @.>
Cc: Liang, @.>; @.>
Subject: Re: [andreabassi78/napari-sim-processor] z-slider bar issue (Issue #13)
This email from @.*** originates from outside Imperial. Do not click on links and attachments unless you recognise the sender. If you trust the sender, add them to your safe senders listhttps://spam.ic.ac.uk/SpamConsole/Senders.aspx to disable email stamping for this address.
Hi @Meizhu-Lianghttps://github.com/Meizhu-Liang, thanks for pointing this out.
I believe it is a napari issue and I posted a question on imageschttps://forum.image.sc/t/displayed-image-size-changing-when-rescaling-z-axis/68085.
In the meantime, I double-checked and I can confirm that it is a visualization issue only, the data shape is not affected.
I'll fix it as soon as I have news from the napari developers
—
Reply to this email directly, view it on GitHubhttps://github.com/andreabassi78/napari-sim-processor/issues/13#issuecomment-1151334789, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARWCUXQ2SAK75DLYUYGVXNTVOIJ3NANCNFSM5YKLZ2GQ.
You are receiving this because you were mentioned.Message ID: @.***>


download fails when records are more than 1k

Possible soultion: http://stackoverflow.com/questions/16761927/aw-snap-when-data-uri-is-too-large

Fixed here: 0da358d9f6ccab0c86b0e414aaf4f472726e6996


Add support for deleting workloads

Create the API and ciao-cli support for deleting unused public or private workloads. Modify BAT tests to delete the test workload.
Fixes: #949, #950, #951, #952, #1135

Coverage decreased (-0.08%) to 66.035% when pulling a735c559d439f5a2cee7599c97c68661a03d007e on kaccardi:topic/delete-workloads into 2d65bc06357f15cba13ddec1e3ad8f731e77d71a on 01org:master.

Coverage decreased (-0.08%) to 66.035% when pulling a735c559d439f5a2cee7599c97c68661a03d007e on kaccardi:topic/delete-workloads into 2d65bc06357f15cba13ddec1e3ad8f731e77d71a on 01org:master.

I'm getting 500 Internal server error for the two error cases, workload does not exist and workload is in use, e.g.,
{"error":{"code":500,"name":"Internal Server Error","message":"Workload definition still in use"}}

Is this expected?

@kaccardi Just a couple of minor comments and questions.  I gave it a good test and everything is working for me on SingleVM.  Nice to see all the BAT tests running as well.

@markdryan I forgot to fix the error response for those 2 error conditions. They should have returned NotFound or Forbidden.

Coverage decreased (-0.07%) to 66.03% when pulling 95afdb034e965958fd31f0e14c94cf776256dd8a on kaccardi:topic/delete-workloads into 9bb2e66dedfc75713f9bfe3f65e75bd6a7d47d23 on 01org:master.

@markdryan @rbradford updated to address your feedback.


Error: Non-relative paths are not allowed when 'baseUrl'

Hello!
I'm absolutely loving TSX, the dev experience is 💯
I started getting this error recently, I believe it is since the recent support for paths in tsconfig.
Error: Non-relative paths are not allowed when 'baseUrl' is not set. Did you forget a leading './'?
    at file:///Users/jameshomer/Projects/Rosewood/node_modules/.pnpm/get-tsconfig@4.0.2/node_modules/get-tsconfig/dist/index.mjs:3:7227
    at Array.map (<anonymous>)
    at file:///Users/jameshomer/Projects/Rosewood/node_modules/.pnpm/get-tsconfig@4.0.2/node_modules/get-tsconfig/dist/index.mjs:3:7105
    at Array.map (<anonymous>)
    at se (file:///Users/jameshomer/Projects/Rosewood/node_modules/.pnpm/get-tsconfig@4.0.2/node_modules/get-tsconfig/dist/index.mjs:3:7002)
    at ce (file:///Users/jameshomer/Projects/Rosewood/node_modules/.pnpm/get-tsconfig@4.0.2/node_modules/get-tsconfig/dist/index.mjs:3:7533)
    at file:///Users/jameshomer/Projects/Rosewood/node_modules/.pnpm/@esbuild-kit+esm-loader@2.2.0/node_modules/@esbuild-kit/esm-loader/dist/index.js:1:338
    at ModuleJob.run (node:internal/modules/esm/module_job:198:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:385:24)

Here is tsonfig.json
{
  "extends": "./.svelte-kit/tsconfig.json",
  "compilerOptions": {
    "allowJs": true,
    "checkJs": true,
    "esModuleInterop": true,
    "forceConsistentCasingInFileNames": true,
    "resolveJsonModule": true,
    "skipLibCheck": true,
    "sourceMap": true,
    "strict": true
  }
}

And .svelte-kit/tsconfig.json
{
	"compilerOptions": {
		"baseUrl": "..",
		"paths": {
			"$lib": [
				"src/lib"
			],
			"$lib/*": [
				"src/lib/*"
			]
		},
		"rootDirs": [
			"..",
			"./types"
		],
		"importsNotUsedAsValues": "error",
		"isolatedModules": true,
		"preserveValueImports": true,
		"lib": [
			"esnext",
			"DOM"
		],
		"moduleResolution": "node",
		"module": "esnext",
		"target": "esnext"
	},
	"include": [
		"../src/**/*.js",
		"../src/**/*.ts",
		"../src/**/*.svelte"
	],
	"exclude": [
		"../node_modules/**",
		"./**"
	]
}

I was able to fix the issue by manually adding baseUrl to my root tsconfig.json.
It seems like perhaps the extends feature is supported for paths but not baseUrl, maybe this is relevant to get-tsconfig?
Furthermore, after I added baseUrl which fixed this isuue I then had to add .js onto a couple of relative module paths - not a big deal but I thought this loader was supposed to support this automatically. ie. lodash/orderBy -> lodash/orderBy.js.
Thanks!

Ah yes sorry, it's not relative 😅 but basically it was working without the .js in the path and then when I updated tsx it started complaining. I'll try and get a repro together.


Broken documentation link

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://github.com/Azure/Industrial-IoT/blob/master/docs/deploy/howto-deploy-local.md'
Click on 'Run the Industrial IoT modules locally'
Routed to 'https://github.com/Azure/Industrial-IoT/blob/master/docs/howto-install-iot-edge.md.'
See 404 error

Expected behavior
Routed to a docs page called 'Run the Industrial IoT modules locally'

#274


How to use limit() and offset() in subquery?

I want to use limit() in a subquery.
limit() seems to work on the main query, but limit() doesn't seem to work on the subquery.
offset() is also the same.
I guess it's because limit() and offset() work when fetch() is called.
Is there any way to use limit() in a subquery?
My Code
JPAQuery<Tuple> tupleJPAQuery = queryFactory.select(

                shop.language,

                ExpressionUtils.as(

                        JPAExpressions.select(languageInfo.name)

                                .from(languageInfo)

                                .where(languageInfo.code.eq(shop.language))

                                .limit(1)

                        , "languageName"

                )

        )
        .from(shop)

        .limit(1);

JPQLSerializer serializer = new JPQLSerializer(JPQLTemplates.DEFAULT);

serializer.serialize(tupleJPAQuery.getMetadata(), false, null);

System.out.println(serializer.toString());

tupleJPAQuery.fetch();

What I Expected
select
            shop0_.shop_name as col_0_0_,
            (select
                languagein1_.code_name
            from
               language_code languagein1_
            where
                languagein1_.code=shop0_.language
            limit ?) as col_1_0_
        from
            shop shop0_ limit ?

The result
select
            shop0_.shop_name as col_0_0_,
            (select
                languagein1_.code_name
            from
               language_code languagein1_
            where
                languagein1_.code=shop0_.language) as col_1_0_
        from
            shop shop0_ limit ?

Serialized Query(Hibernate Query)
select Shop.shopName, (select languageInfo.name
from LanguageInfo languageInfo
where languageInfo.code = Shop.language) as languageName
from Shop Shop

Environment
Querydsl version: 5.0.0
Querydsl module: 5.0.0
Database: PostgreSQL
JDK: Oracle openjdk 17.0.2

I think you're using it correctly, I am afraid it appears there is a bug in the serializer that ignores the applied limit and offset.

@jwgmeligmeyling  Has this bug been fixed? I had this problem too,I find that the limit is only concatenated after calling the fetch() method.

Thank you for your reply.I just looked at it, and maybe the min()/max() function is a better fit for this operation,So I don't think it's a bug.

I have the same problem !


Merge main to live with new release notes

Docs Build status updates of commit 166c682:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/overview/quantum-computers-and-simulators.md
:white_check_mark:Succeeded
View

articles/quickstarts/get-started.md
:white_check_mark:Succeeded
View

articles/quickstarts/install-jupyter.md
:white_check_mark:Succeeded
View

articles/resources/relnotes.md
:white_check_mark:Succeeded
View

articles/resources/toc.yml
:white_check_mark:Succeeded

articles/tutorials/quantum-random-number-generator.md
:white_check_mark:Succeeded
View

articles/tutorials/toc.yml
:white_check_mark:Succeeded

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/machines/index.md
:white_check_mark:Succeeded
View

articles/user-guide/machines/qc-trace-simulator/index.md
:white_check_mark:Succeeded
View

articles/user-guide/quickref/iqsharp.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 7b7ce55:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/overview/quantum-computers-and-simulators.md
:white_check_mark:Succeeded
View

articles/quickstarts/get-started.md
:white_check_mark:Succeeded
View

articles/quickstarts/install-jupyter.md
:white_check_mark:Succeeded
View

articles/resources/relnotes.md
:white_check_mark:Succeeded
View

articles/resources/toc.yml
:white_check_mark:Succeeded

articles/tutorials/quantum-random-number-generator.md
:white_check_mark:Succeeded
View

articles/tutorials/toc.yml
:white_check_mark:Succeeded

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/machines/index.md
:white_check_mark:Succeeded
View

articles/user-guide/machines/qc-trace-simulator/index.md
:white_check_mark:Succeeded
View

articles/user-guide/quickref/iqsharp.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


CanFdSocket read_frame crash fix

Reading a standard CAN frame through the CanFdSocket leads to a crash due to mismatching sizes in the frame construction’s copy_from_slice. Thix fix has been tested and builds valid CAN frames.

Does CanFdSocket::read_raw_frame need the same fix? https://github.com/socketcan-rs/socketcan-rs/blob/master/src/socket.rs#L617

Does CanFdSocket::read_raw_frame need the same fix? https://github.com/socketcan-rs/socketcan-rs/blob/master/src/socket.rs#L617

I think so. Fixed it too

Oof. Sorry, my bad. I was hacking on this update before I got an FD controller.


use_icu_alternatives_on_android feature porting.

Porting from Lite-15 into Lite-17.  Controlled by flag: use_icu_alternatives_on_android
XWalkCoreShell.apk(ARM), reduced size=22.2 -15.7 = 6.5M

@peter,  icu porting done.


fix: flaky tests error

Description
for cargo test , some error case:
case 1:
called `Result::unwrap()` on an `Err` value: Os { code: 24, kind: Uncategorized, message: "Too many open files" }

solution: use ulimit command to add resource , such as: ulimit -n 10240

case 2:  spawn too many server
try to add exponential backoff mechanism(sleep time) to retry,  Not sure it can fix the CI error.
Related Issue
Related #3133
Proposed Changelog

Added exponential backoff mechanism(sleep time) to retry for test

@casey code review plz :)

Thanks for the PR! I actually want to solve this in a different way. I'm going to add an /update endpoint which updates the index, which is only available during tests. So the client can make a request to /update and know that the index will have been updated, without having to poll the index. This should be more reliable, and avoid a loop entirely.


Ignore test folder

ignore test folder for codecov calculation

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (361e36c) 75.00% compared to head (f29de11) 75.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #26   +/-   ##
=======================================
  Coverage   75.00%   75.00%
=======================================
  Files           4        4
  Lines           8        8
=======================================
  Hits            6        6
  Misses          2        2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


chore: increase electron-builder compression to maximum

@Kong/team-insomnia closing this one, not worth taking into consideration for the time being.
There's negligible save in size when using the maximum compression option and the packaging for example for release-recurring increases from 20 mins to 30 mins.


Use time_intervals in Silences function module

What did you do?
In the Silences function module, although the start time and end time can be set, it cannot meet the requirements.
What did you expect to see?
Use time_intervals in Silences function module
Although silence can be achieved indirectly through the time_intervals of the route module, it is more hoped that all the silence rules are in the silence module.

There is such a scenario:
Matchers

instance=<IP_ADDRESS>:9100
alertname=ServerCpuUsage

Silence from 0:00 to 6:00 every day

Can someone please pay attention to this issue

yes, I also need a feature like this

yes, I also need a feature like this

#3317

make.

I'm not sure to understand why the existing mute time interval doesn't work for your use case.

if i want to add a new silence like :
Matchers
- instance=<IP_ADDRESS>:9100
- alertname=ServerCpuUsage

Silence from 0:00 to 6:00 every day

Time interval, cannot be set to repeat every day

hmm they can
name: off-hours
time_intervals:
- times:
  - start_time: 00:00
    end_time: 06:00

add a new silence

add a new silence，How to use this off-hours in web ui, or in api ？

Time interval, cannot be set to repeat every day

hmm they can
name: off-hours
time_intervals:
- times:
  - start_time: 00:00
    end_time: 06:00

I mean, in the silence function, the current version cannot use this off-hours in web ui, right?

Currently there are two rules for Silences, one is configured in the  module in the configuration file, and the other is configured on the Web UI of Alertmanager, but this way of configuration does not support time_intervals, I I think it is necessary to support, there are many users with corresponding scenarios.

I also really need this new feature.


The type initializer for 'ReactiveUI.ReactiveNotifyPropertyChangedMixin' threw an exception.

I tried to make a small program, but when I run, I get an exception.
The type initializer for 'ReactiveUI.ReactiveNotifyPropertyChangedMixin' threw an exception.
at ReactiveUI.WhenAnyMixin.WhenAny[TSender,TRet,T1,T2] (TSender This, System.Linq.Expressions.Expression1[TDelegate] property1, System.Linq.Expressions.Expression1[TDelegate] property2, System.Func3[T1,T2,TResult] selector) [0x00000] in C:\projects\reactiveui\src\ReactiveUI\VariadicTemplates.cs:123    at ReactiveUI.WhenAnyMixin.WhenAnyValue[TSender,TRet,T1,T2] (TSender This, System.Linq.Expressions.Expression1[TDelegate] property1, System.Linq.Expressions.Expression1[TDelegate] property2, System.Func3[T1,T2,TResult] selector) [0x0000d] in C:\projects\reactiveui\src\ReactiveUI\VariadicTemplates.cs:106
at App11.ViewModels.Login..ctor () [0x00008] in D:\VS\App11\App11\App11\ViewModel\Login.cs:38
at App11.Pages.Login..ctor () [0x00013] in D:\VS\App11\App11\App11\Pages\Login.cs:21
at App11.App..ctor () [0x0001b] in D:\VS\App11\App11\App11\App.xaml.cs:17
at App11.Droid.MainActivity.OnCreate (Android.OS.Bundle bundle) [0x00027] in D:\VS\App11\App11\App11.Android\MainActivity.cs:23
at Android.Support.V4.App.FragmentActivity.n_OnCreate_Landroid_os_Bundle_ (System.IntPtr jnienv, System.IntPtr native__this, System.IntPtr native_savedInstanceState) [0x00011] in <27c17fe440cf491ba8255bcefade6e02>:0
at (wrapper dynamic-method) System.Object:35cc9c0b-4e93-4a2c-86c9-f0c818d3c2a3 (intptr,intptr,intptr)
Usually with other packages this happens when something is not installed on the target platform, but all that needs to be installed.
 What are the versions of the Rx libraries (Rx-Core, Rx-Linq, etc.... ) that got added to your projects? Sometimes I've noticed some weirdness with those versions. I just make sure they are all 2.2.5 and that works for me

Rx libraries version 2.2.5.
I created an empty project and linked the library. Added the call "WhenAnyValue".
Has included "First Chance exceptions".
Here's the trace:
1.
at ReactiveUI.ReactiveNotifyPropertyChangedMixin..cctor () [0x00020] in C:\projects\reactiveui\src\ReactiveUI\ReactiveNotifyPropertyChangedMixin.cs:20
2.
at ReactiveUI.WhenAnyMixin.WhenAny[TSender,TRet,T1,T2] (TSender This, System.Linq.Expressions.Expression1[TDelegate] property1, System.Linq.Expressions.Expression1[TDelegate] property2, System.Func3[T1,T2,TResult] selector) [0x00000] in C:\projects\reactiveui\src\ReactiveUI\VariadicTemplates.cs:123    at ReactiveUI.WhenAnyMixin.WhenAnyValue[TSender,TRet,T1,T2] (TSender This, System.Linq.Expressions.Expression1[TDelegate] property1, System.Linq.Expressions.Expression1[TDelegate] property2, System.Func3[T1,T2,TResult] selector) [0x0000d] in C:\projects\reactiveui\src\ReactiveUI\VariadicTemplates.cs:106
at App13.Class1..ctor () [0x00008] in D:\VS\App13\App13\App13\Class1.cs:27
at App13.MainPage..ctor () [0x00008] in D:\VS\App13\App13\App13\MainPage.xaml.cs:14
at App13.App..ctor () [0x0000f] in D:\VS\App13\App13\App13\App.xaml.cs:16
at App13.Droid.MainActivity.OnCreate (Android.OS.Bundle bundle) [0x00027] in D:\VS\App13\App13\App13.Android\MainActivity.cs:23
at Android.Support.V4.App.FragmentActivity.n_OnCreate_Landroid_os_Bundle_ (System.IntPtr jnienv, System.IntPtr native__this, System.IntPtr native_savedInstanceState) [0x00011] in <27c17fe440cf491ba8255bcefade6e02>:0
at (wrapper dynamic-method) System.Object:7ab7c9c4-63df-49b8-9789-fe2f27dd8656 (intptr,intptr,intptr)
3.
at ReactiveUI.WhenAnyMixin.WhenAny[TSender,TRet,T1,T2] (TSender This, System.Linq.Expressions.Expression1[TDelegate] property1, System.Linq.Expressions.Expression1[TDelegate] property2, System.Func3[T1,T2,TResult] selector) [0x00000] in C:\projects\reactiveui\src\ReactiveUI\VariadicTemplates.cs:123    at ReactiveUI.WhenAnyMixin.WhenAnyValue[TSender,TRet,T1,T2] (TSender This, System.Linq.Expressions.Expression1[TDelegate] property1, System.Linq.Expressions.Expression1[TDelegate] property2, System.Func3[T1,T2,TResult] selector) [0x0000d] in C:\projects\reactiveui\src\ReactiveUI\VariadicTemplates.cs:106
at App13.Class1..ctor () [0x00008] in D:\VS\App13\App13\App13\Class1.cs:27
at App13.MainPage..ctor () [0x00008] in D:\VS\App13\App13\App13\MainPage.xaml.cs:14
at App13.App..ctor () [0x0000f] in D:\VS\App13\App13\App13\App.xaml.cs:16
at App13.Droid.MainActivity.OnCreate (Android.OS.Bundle bundle) [0x00027] in D:\VS\App13\App13\App13.Android\MainActivity.cs:23
at Android.Support.V4.App.FragmentActivity.n_OnCreate_Landroid_os_Bundle_ (System.IntPtr jnienv, System.IntPtr native__this, System.IntPtr native_savedInstanceState) [0x00011] in <27c17fe440cf491ba8255bcefade6e02>:0
at (wrapper dynamic-method) System.Object:7ab7c9c4-63df-49b8-9789-fe2f27dd8656 (intptr,intptr,intptr)

Hmm nothing is jumping out at me... If you can upload the simple project and I see if it works for me? Otherwise maybe something is getting linked away? Is the Linker Behavior don't Link?

You are sure your WhenAnyValue is property formed i.e. this.WhenAnyValue(x => x.Prop1, x => x.Prop2 etc and not like this.WhenAnyValue(x => Prop1, X => Prop2 .... etc ?

Yes, I am sure.
I in a separate project did everything as simple as possible for the test.
string _p1;
        public string p1
        {
            get { return _p1; }
            set { this.RaiseAndSetIfChanged(ref _p1, value); }
        }

        string _p2;
        public string p2
        {
            get { return _p2; }
            set { this.RaiseAndSetIfChanged(ref _p2, value); }
        }
...
        this.WhenAnyValue(e => e.p1, p => p.p2,
                (__p1, __p2) => true)
                .ToProperty(this, v => v.ob1, out _ob);

If you can stick a small, failing sample somewhere, I'm more than happy to look at it.

It is very strange.
When I wanted to give you a small example, I reduced the size of the project by removing all the packages from the folder packages. After that I decided to make sure that the bug remained. I started the project and after I restored all the packages, the application worked correctly.
Perhaps I was mistaken in the sequence of installing packages when creating a project.
Could you tell us in which order to install correctly the nuget reactiveui packages.(pcl -> android -> android reactiveui_eventc etc)

I don't know if I've ever really done any specific order sometimes nuget/obj/bin  just get weird and it helps to go clean :-/ The only issue I've had is that sometimes the RX libraries will install the 2.3.0 of rx-platform services which doesn't seem to go over well.  Consequently I'll usually set Dependency Behavior to Lowest at first install just to make sure 2.2.5 of all the Rx libraries get installed and then just work from there.

It's really strange, but it works for me)
Thank you all for answering the question.


Bug 2081788: Ocp/align160622

Align to latest upstream change. Includes support for deploying the webhooks via the csv.

/bugzilla refresh

/retest


The wrong chart type

Type of issue
Typo
Feedback
Hello,
I noticed a discrepancy in the code provided within the chart section. While the author used ExcelScript.ChartType.columnStacked, the displayed chart appears to be a Column clustered chart. It would be beneficial to adjust the code to ExcelScript.ChartType.columnClustered to accurately reflect the chart's appearance.
Thank you for sharing this informative article.
Best regards,
Karim
Page URL
https://learn.microsoft.com/en-us/office/dev/scripts/develop/scripting-fundamentals
Content source URL
https://github.com/OfficeDev/office-scripts-docs/blob/main/docs/develop/scripting-fundamentals.md
Author
@o365devx
Document Id
bf0955e2-2a06-ea7d-3d78-c8c52294d23a

Hi @kvazirinejad,
Thanks for reaching out. I just double-checked and the image is showing the correct chart type. Both charts look very similar in this scenario when there aren't multiple values for each category.

I'm going to close the issue, but if there's something I'm missing, please leave a comment and I'll reopen the issue.


Good

nice work.thank you very much.I want to konw where I can download BraTs 2018 dataset.Thanks!

To get access to the BraTS 2018 data, please use the registration page ('https://www.med.upenn.edu/sbia/brats2018/data.html')
To get access to the BraTs 2016+2017 data, you can download in 'http://medicaldecathlon.com'


QP Separator Items: Improve keybinding to navigate between sections

I introduced a keybinding recently (#207028) which works well for inline separators but not item separators... it was focusing the last item in a section when you go up.
Revisit to focus the first item in a section.

Fixed in https://github.com/microsoft/vscode/pull/207520

I verified that Alt+DownArrow and Alt+UpArrow on Windows navigate between sections on a quick pick, always focusing the first item of a section. Let me know if that's not what this issue is about.


Swiper Coverflow Effect is broken on initial load, then it is fixes itself after few seconds

Check that this is really a bug

[X] I confirm

Reproduction link
https://codesandbox.io/p/devbox/swiper-react-effect-coverflow-6pxf4v?file=%2Fsrc%2FApp.jsx%3A10%2C23
Bug description
Hello I am using next 14.1.0. I have problem with Swiper Coverflow effect. It is not just Coverflow effect, I also tested it on Cube effect and I have simmular problem.
When I refresh the page, swiper with coverflow effect is not applied, but after few seconds coverflow effect is applied.
Same situation is for Cube effect.
I thought the problem might be with my data which is prefecthed on server, but I also tried it with hardcoded values, and I have same problem.
In this link is video of what is happening. I have copied code from reprocuction link in my next 14.1.0 app.
https://streamable.com/e08hl8
Everything else is same.
Expected Behavior
It should apply Coverflow effect on initial loading.
Actual Behavior
It does not apply Coverflow effect on initial loading.
Swiper version
11.0.7
Platform/Target and Browser Versions
mac OS Google Chrome,  Safari , Brave
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[X] I'm willing to open a PR

t0ggles-create swiper

Probably related to how next initializes Swiper, try using the core version of Swiper, and your demo link is not working


Felix can write to two logfiles.

Confusing. One has logs reading config from etcd correctly, the other has 'EtcdException: Unable to decode server response: timed out' (I'll raise another issue for that.)
[root@calico-rh01 calico]# ls -ltr
total 27784
-rw-r--r--. 1 root root   496320 Jun  5 10:24 felix.log.2015-06-03
-rw-r--r--. 1 root root 19568895 Jun  5 10:24 felix.log

I've just noticed that the felix exception appears in both log files.

Conflict between log-rotate and felix?

@plwhite I think you wrote the logging setup, are you a good person to look at this?

I think in general we need to sort out our log rotation story.  There's also a problem on Ubuntu, where Felix does its own log rotation, but so does upstart, leading to ridiculously named log files.

@DaveLangridge could you please confirm that there was only one Felix running?

Yes. Only one felix.

Closing this as a duplicate of #249, we'll centralise work there.


Does not work with SSR: false

Applying ssr: false to nuxt.config breaks the CSRF composable.
The cookie is generated correctly, but the csrf token is not passed back to the client and therefore useCsrf() always returns undefined

After speaking with @Baroshem in the Nuxt Discord:  https://discord.com/channels/473401852243869706/1087072837648519298/1087072837648519298
I have decided to close this issue as it seems to not be feasible to implement CSRF without SSR in this manner
I'll look at alternative methods and If I find something universal to implement, I'll open a PR

Great, can't wait to see your implementation. PRs are welcome :)


Error after update Three dependency: export 'sRGBEncoding' (imported as 'c') was not found in 'three'

Using the latest version of @googlemaps/three: 4.0.11
After updating "three" dependency to latest (0.164.0 at time of writing).  See this Migration Guide: https://github.com/mrdoob/three.js/wiki/Migration-Guide#151--152

THREE.sRGBEncoding is now THREE.SRGBColorSpace

I notice in code this is kept in place for backwards compatibility: https://github.com/googlemaps/js-three/blob/d6d8601b379caca3a280deae4a9cbad5baf9ad40/src/three.ts#L397
But the export is no longer available with latest Three version, so unable to update at the moment.
Could this backwards compatibility be removed or is there an other work-around?

I think the simple fix would be to look up the explicit value used in older three.js versions and replace the import with a const declaration. Alternatively, we could add a minimum version for the three peer-dependency and remove that. Since the former option wouldn't be a breaking change, I'd be in favor of that.

If you would like to upvote the priority of this issue, please comment below or react on the original post above with :+1: so we can see what is popular when we triage.
@GKersten Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:

Check the issue tracker - bugs and feature requests for Google Maps Platform APIs and SDKs
Open a support case - Get 1:1 support in Cloud Console.
Discord - chat with other developers
StackOverflow - use the google-maps tag

This is an automated message, feel free to ignore.

https://github.com/mrdoob/three.js/blob/d04539a76736ff500cae883d6a38b3dd8643c548/src/constants.js#L155


SC metrics/schema dashboard

This is a next step kind of feature...I implemented the show() function to work with layout data using the dynamic tool loading, but we really need a way to turn the json manifest into something browser viewable. Some of the important feature of the dashboard:
-table of metrics
-30,000ft snapshot of layout (color annotated png). (sanity check).
-flowgraph diagram
-generation of expandable menu for settings of variables used for runs (like current autogen in sphinx)
-clickable links to all source files
-clickable links to all reports/result files
-ability to load multiple json files to do metrics display as a function of time stamp, histogram, (with notes for diff in settings)
Given that we have all the information nicely captured in a json file for each run, I think this could be pretty exciting, but I am really  out of my domain here...
What do you think about using dash/flask for creating a metrics/schema dashboard?
https://dash.plotly.com/introduction
https://dash.gallery/Portal/

Closing our oldest issue thanks to @GabrielAguirre1 !


On dashboard deployment page add a section for "URLs"

We can see them on the "overview box" widget but I think it will be good to also have a dedicated section with a table view like for the Output parameters.

@mebster do you agree? This will allow to have the same cards to fix #185


Performance best practices

Adds a document listing common performance pitfalls in ASP.NET Core apps and how to avoid them.
Fixes #9526
@Rick-Anderson 	edit: Internal review URL

For now I would put this under the Other topics node of the TOC (see aspnetcore/toc.md). We can decide about a top-level Performance node and what belongs in it later.

I think it would be valuable to have a top-level Performance node (including sections like diagnostics tools, performance features, and best practices (this doc)). I'm fine with putting this in Other topics for the moment, though, until we have more content for the performance node.
Is there any reason not to have a perf node other than lack of content?

No reason.  We had it before the last TOC reorg but got rid of it because we didn't really have enough content to justify it.

@tdykstra 	@scottaddie 	@guardrex 	hold feedback. I'm PR'ing this PR.

@mjrousos 	I wasn't able to create a PR to merge into this PR, so I created #9645. I'm just getting started, it's not ready for review. Maybe @scottaddie 	can tell you how to create PR's so I can more easily PR your PR.

Closing this since #9645 added this doc.


Adopt official kubeadm logo

This is a Feature Request

What would you like to be added
Change https://kubernetes.io/docs/setup/independent/install-kubeadm/ and https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm/ to use the official kubeadm logo.
Why is this needed
Glitz and flair
/priority backlog
Comments

I'll work on this once logo is selected.

https://github.com/kubernetes/kubeadm/issues/1588

Logo is selected, waiting on PR for official artwork.

New logo is available in draft.

I'll update it once merged to master

kubeadm logo now adopted.

Done
/close


Just in case you didn't know F3+N does this (and F3+F4 allows you to cycle all of them)

I am awake of this, it's just these keybindings can be fiddly to perform compared to a single key press.
That's where my idea for this mod came along, just to make building a tiny bit easier.


Durations should not accept months

Currently, Duration("P0-1-0T0:0:0"), i.e., a 1-month duration, does not throw an error. Converting this duration to seconds gives some arbitrary number (different every time).
Of course, this is not the intended duration format. However, XIOS does accept durations in this format, so we should be careful when passing these around.
XIOS always sets the number of days in a month to 30, which could cause a lot of confusion. It would be better to just disallow such formats inside Duration.

Closed by #637.


easymotion tags look weird

By default, the easymotion markers look pretty funky (see screenshot below).

I know that you can style them to some extent with:
vim.easymotionMarkerBackgroundColor,
vim.easymotionMarkerForegroundColorOneChar,
vim.easymotionMarkerForegroundColorTwoChar,
vim.easymotionMarkerWidthPerChar,
vim.easymotionMarkerHeight,
vim.easymotionMarkerFontFamily,
vim.easymotionMarkerFontSize,
vim.easymotionMarkerFontWeight,
vim.easymotionMarkerYOffset.
However, no matter what I do, I can't get it to look like they are normal characters in the document because of the offsets of the text within the markers and the x-offset of the marker relative to the letters in the actual document.
Also, half of them are italic for some reason? I'm not really sure what that means.
What I think would be really helpful is either:

An option to provide arbitrary CSS for the tags so users can style them however they want (e.g. padding, margins, line-height)
Or, an option to display them in-line with the text so it just looks like the actual text of the document is changing when you go into jump mode, the way it is in Vim

You may use other vim extension.
VimStyle has no easymotion features.

If I didn't want easy motion, I could also just disable it with "vim.easymotion": false. My point is that I want to use it but I want it to be legible


Allow for borrowing during use if guaranteed immovability

Motivation:
Currently you cannot borrow a value mutable why it is currently being borrowed. This is a core aspect of Rust and should not be removed, however, there are legitimate uses for wanting to do something like this and with the proposal this would become more easy to accomplish safely.
Example (of what is wanted to be done):
#[derive(PartialEq)]
struct Actor {
    hp: i32,
    attacking: bool,
}

impl Actor {
    pub fn new() -> Actor {
        Actor {
            hp: 10,
            attacking: false,
        }
    }

    pub fn damage(&mut self) {
        self.hp -= 1;
    }
}

fn main() {
    let mut actors = vec![Actor::new(), Actor::new()];
    actors[1].attacking = true;

    for actor in actors.iter_mut() {
        //if an actor is attacking, damage all the other actors
        if actor.attacking {
            //doesnt compile due to two mut borrows
            for actor2 in actors.iter_mut() {
                if actor2 != actor {
                    actor2.damage();
                }
            }
        }
    }
}

This was taken from here.
There are ways to work around this currently but generally it requires convoluted methods or extra allocations which are undesirable especially for people coming to rust.
A working example that leaves most of the algorithm the same has the following main, gotten from here:
fn main() {
    let actors = UnsafeCell::new(vec![Actor::new(), Actor::new()]);
    unsafe {
        (*actors.get())[1].attacking = true;
    }

    for actor in unsafe { (*actors.get()).iter_mut() } {
        //if an actor is attacking, damage all the other actors
        if actor.attacking {
            for actor2 in unsafe { (*actors.get()).iter_mut() } {
                if actor2 != actor {
                    actor2.damage();
                }
            }
        }
    }
}

Proposition:
A new type of borrowing, called immovable borrow which can be done at any time, even when another item has borrowed it. This would only allow mutations that are guaranteed not to require a move. These would only be allowed with mutable borrows. To my knowledge most actions on intrinsics are no-move but there may be others.
This would be implemented by two item: iter_mut_immov() which would be for generated mutable immovable references for iterating through and immov which would be a keyword use in conjunction with &mut (ie &mut immov) for getting these sorts of borrows individually.
An error that recommends this type of borrow would also be implemented.
This proposal does ask for adding a new keyword or at least a new contextual keyword (then it would be &immov mut)
Example:
Using this proposition the following would be done:
fn main() {
    let mut actors = vec![Actor::new(), Actor::new()];
    actors[1].attacking = true;

    for actor in actors.iter() {
        //if an actor is attacking, damage all the other actors
        if actor.attacking {
            //now with immovable borrow
            for actor2 in actors.iter_mut_immov() {
                if actor2 != actor {
                    actor2.damage();
                }
            }
        }
    }
}

Mutations are still a problem even if it's immovable and single-threaded:
https://manishearth.github.io/blog/2015/05/17/the-problem-with-shared-mutability/

Thank you very much for the article, good read.
However, I would argue that the enum example that he talked about counts as moving so would not be allowed with such a borrow

counts as moving

I'm not sure what you mean by that.  If the "immovable mutable borrow" doesn't let you assign to a field of the borrowed thing, how is it mutable at all?

It counts as moving if the change would invalidate a interator pointing at it.
As to mutable, this is to be a restricted form so that so rust is easier to use is some use cases

Isn't it possible for mutation to invalidate iterators even without moving? You could make it safe by assuming the iterator's referent contains no references of its own, but that rules out even the basic use case of iterating over collections.

It is possible that some mutations invalidate iterators but not all of them. If you have a vec of items that includes a vec then pushing to that would not be allowed but writing to some i32 field would


Parks

When adjoining days with zero contribs are surrounded by towers, I think those 0 contrib days should be merged together to create larger park-land sections, as it typically means the user went on holidays.
This merging into park-land wont make sense for the part of the year which is still in the future.  Perhaps some building equipment could be put on the future few weeks, to indicate those weeks are "under construction", and then park-land for future weeks ahead of that.

I currently have no plan of adding new features. Thanks for the idea, maybe in the future.

Also add roads between building blocks

?

May be in future 🫠 but roads and cars on road would look nice.

Im pretty sure that there are roads already.

Vr city of Github Great!

Sharks with laz0r beams attached to their heads plz; kthnxbie < 3

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @lomartins, @Texhnolyze47, @hhuseyinpay, @benji6, @S7venLights, @Ac0rnz, @jbuisine, @GentlemanMC, @heroslender, @happygong, @lidangzzz, @TIT8, @dddsssl, @HZongLin, @loganynguyen, @afro-cloud, @mtlbrownsugar, @dedouwe26, @Vyvy-vi, @ruthiel, @IAMAGeeker, @LuckysHere, @ismailkhan-dev, @JingkunLiu, @Sangeppato, @22yeetz22, @1fahh, @gumdropsteve, @HananoshikaYomaru, @nserrano199, @Fern1ck, @aeyno, @noxonsu, @shimonosatoru, @balance-wtf, @Rookiewan, @prajwalpathak, @johnLitoBardinas, @Aman9das, @VCStardust, @mnnkhndlwl, @Zeczero, @cwmke, @ngocanhtve, @brndnsvr, @samirelanduk, @KNipunDananjaya, @miquelrossello, @kellyjoe256, @cyd1310997


Install binance-futures-connector-python and then install binance-connector-python file send override conflict

Before submitting a new issue, please check if a similar issue has already been filed.
Issue subject
Briefly describe the issue here.
Install binance-futures-connector-python and then install binance-connector-python file send override conflict
Expected behaviour
Describe what should happen.
um_futures file is overwritten

[binance-connector-python] and [binance-futures-connector-python] act on the binance folder at the same time
Actual behaviour
Describe what happens instead. Please include the complete failure message.
Traceback (most recent call last):
File "/Users/snieopq/PycharmProjects/flaskProject/Webhook/Futures/user_data.py", line 6, in
from binance.um_futures import UMFutures
ModuleNotFoundError: No module named 'binance.um_futures'
Steps to reproduce
Provide steps to let us know how we can reproduce this issue.
import time
import logging
from binance.lib.utils import config_logging
from binance.um_futures import UMFutures
from binance.websocket.um_futures.websocket_client import UMFuturesWebsocketClient

import logging
from binance.spot import Spot
from binance.um_futures import UMFutures
from binance.lib.utils import config_logging

config_logging(logging, logging.DEBUG)

spot_client = Spot()
print(spot_client.time())

um_futures_client = UMFutures()
logging.info(um_futures_client.time())

this works for me.

Hi @1163849662, since there's no new updates from you for a while since our last comment, we're closing this post for now. Please feel free to reopen if necessary.


Participation of SD in meeting with industry partner

In order to be able to bring the team's technical perspective to the meetings with the industry partner, at least one software developer attends in addition to the POs. Ideally, participation should be alternated.

@AnnaH3003 This is the wrong repository.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-31-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4735

Questions ?
Please refer to the Backport tool documentation


Add ValidDate type

The tests will fail until #12 is merged but I figured I may as well raise the PR because I'm sure there are other changes I'll need to make too.

This is really weird, the tests are failing for me locally on uses R.toString-like string representations.

Oops, I hadn't upgraded to the new version of Ramda.

I don't think we should include $.ValidDate in $.env. When one applies a function of type a -> a -> a, we determine all the types of which the first argument is a member. We then do the same for the second argument. If the intersection of these two sets is empty, we throw a type error which lists all the first argument's types. 1 could soon belong to half a dozen types. To avoid long error messages I suggest we leave $.env as is and make future types available à la carte.
We need to work out how best to document additional types such as $.ValidDate. Mind having a go at updating the README?

Yeah, I wasn't sure where to put it so I just stuck it in env. I'll move it out now and update the README.

So I've added documentation about ValidDate. When we add more types, this should become a section that lists the various additional types available and gives examples of their use but for the moment I though it would look odd for just one type.

I envisage the final documentation looking like this:
Types
sanctuary-def defines Type values for JavaScript's built-in types:

$.Array :: Type -> Type
$.Boolean :: Type
$.Date :: Type
$.Error :: Type
$.Function :: Type
$.Null :: Type
$.Number :: Type
$.Object :: Type
$.RegExp :: Type
$.String :: Type
$.Undefined :: Type

sanctuary-def also defines $.Any, the type of which every JavaScript value
is a member.
In addition, many more restrictive versions of the above types are available but not
loaded into the environment by default. These include:

$.ValidDate
$.ValidNumber
$.FiniteNumber
$.NonZeroValidNumber
$.NonZeroFiniteNumber
$.Integer;
$.NonZeroInteger
$.RegexFlags

ValidDate
Defines a date type that does not include invalid JS date objects.
const def = $.create($.env.concat([$.ValidDate]));

const sinceEpoch = def('sinceEpoch',
                       {},
                       $.ValidDate, $.Number],
                       date => date.getTime() / 1000);

sinceEpoch(new Date('foo'))
// ! TypeError: ‘sinceEpoch’ expected a value of type ValidDate as its first argument;
// received new Date(NaN)

And so on...

This looks good, though there's another structure which would involve less duplication:
### Types
#### `Any`
#### `Array`
#### `Boolean`
#### `Date`
#### `Error`
#### `FiniteNumber`
#### `Function`
#### `Integer`
#### `NonZeroFiniteNumber`
#### `NonZeroInteger`
#### `NonZeroValidNumber`
#### `Null`
#### `Number`
#### `Object`
#### `RegExp`
#### `RegexFlags`
#### `String`
#### `Undefined`
#### `ValidDate`
#### `ValidNumber`
### `env`

The env section would simply list the types included in $.env, each linking to its documentation.
I'll put together a pull request to restructure the documentation, so this pull request can remain focused on defining $.ValidDate. :)

Will I remove the interim documentation I've added in this PR?

You can update this pull request now, Stefano. :)

Great stuff! :zap:

:deciduous_tree:


Update importdata Script

Now when running the importdata.sh script, the script checks whether a provided database or collection already exists before attempting to create it or not. @code4clouds also made the suggested change of switching from sed to ed for speed gains when downloading our sample data.
Fixes #79.

Where I've run the load_env.sh previously
→ ./data/importdata.sh

Step 1. Confirming locations...
Is this the correct resource group name? [CadetDemo] Y,N (leave blank for Y):
Resource group confirmed.
Is this the correct CosmosDB account name? [demo-pjdb] Y,N (leave blank for Y):
Account name confirmed.

Step 2. Creating Cosmos DB database...

Checking whether the database 'IMDb' already exists...
Creating database 'IMDb'...
Database 'IMDb' has been created.

Step 3. Creating Cosmos DB collections...
Checking whether the collection 'titles' exists...
(1 of 3) Creating collection 'titles'
Collection 'titles' has been created.
Checking whether the collection 'names' exists...
(2 of 3) Creating collection 'names'
Collection 'names' has been created.
Checking whether the collection 'principals_mapping' exists...
(3 of 3) Creating collection 'principals_mapping'
Collection 'principals_mapping' has been created.
Step 4. Importing IMDb data to Cosmos DB...

(1 of 3) Importing data from file 'title.basics.tsv' to collection 'titles'...
2019-02-05T10:47:29.996-0500    connected to: demo-pjdb.documents.azure.com:10255
[... abridged ...]
2019-02-05T11:05:30.417-0500    imported 5611000 documents

Import to 'titles' is complete

(2 of 3) Importing data from file 'name.basics.tsv' to collection 'names'...
2019-02-05T11:05:30.740-0500    connected to: demo-pjdb.documents.azure.com:10255
[... abridged ...]
2019-02-05T11:29:49.615-0500    imported 9117045 documents

Import to 'names' is complete

(3 of 3) Importing data from file 'title.principals.tsv' to collection 'principals_mapping'...
2019-02-05T11:29:50.166-0500    connected to: demo-pjdb.documents.azure.com:10255
[... prematurely ended due to a network issue ...]
Step 5. Finished importing data. Cleaning up...
removed 'title.basics.tsv'
removed 'name.basics.tsv'
removed 'title.principals.tsv'

Step 6. Reducing throughput on Azure...

Setting 'titles' throughput to 1700 to reduce cost...
{
  "offer": {
    "_etag": "\"00004329-0000-0000-0000-5c59cea80000\"",
    "_rid": "8rZ1",
    "_self": "offers/8rZ1/",
    "_ts":<PHONE_NUMBER>,
    "content": {
      "offerIsAutoScaleEnabled": false,
      "offerIsRUPerMinuteThroughputEnabled": false,
      "offerMinimumThroughputParameters": {
        "maxConsumedStorageEverInKB": 0,
        "maxCountOfSharedThroughputCollectionsEverCreated": 0,
        "maxThroughputEverProvisioned": 0
      },
      "offerThroughput": 1700,
      "userSpecifiedThroughput": 1700
    },
    "id": "8rZ1",
    "offerResourceId": "cpBLANnPiQM=",
    "offerType": "Invalid",
    "offerVersion": "V2",
    "resource": "dbs/cpBLAA==/colls/cpBLANnPiQM=/"
  }
}

Setting 'names' throughput to 1700 to reduce cost...
{
  "offer": {
    "_etag": "\"00004429-0000-0000-0000-5c59ceab0000\"",
    "_rid": "0No1",
    "_self": "offers/0No1/",
    "_ts":<PHONE_NUMBER>,
    "content": {
      "offerIsAutoScaleEnabled": false,
      "offerIsRUPerMinuteThroughputEnabled": false,
      "offerMinimumThroughputParameters": {
        "maxConsumedStorageEverInKB": 0,
        "maxCountOfSharedThroughputCollectionsEverCreated": 0,
        "maxThroughputEverProvisioned": 0
      },
      "offerThroughput": 1700,
      "userSpecifiedThroughput": 1700
    },
    "id": "0No1",
    "offerResourceId": "cpBLAM8UXCM=",
    "offerType": "Invalid",
    "offerVersion": "V2",
    "resource": "dbs/cpBLAA==/colls/cpBLAM8UXCM=/"
  }
}

Setting 'principals_mapping' throughput to 1700 to reduce cost...
{
  "offer": {
    "_etag": "\"00004529-0000-0000-0000-5c59ceae0000\"",
    "_rid": "TdiW",
    "_self": "offers/TdiW/",
    "_ts":<PHONE_NUMBER>,
    "content": {
      "offerIsAutoScaleEnabled": false,
      "offerIsRUPerMinuteThroughputEnabled": false,
      "offerMinimumThroughputParameters": {
        "maxConsumedStorageEverInKB": 0,
        "maxCountOfSharedThroughputCollectionsEverCreated": 0,
        "maxThroughputEverProvisioned": 0
      },
      "offerThroughput": 1700,
      "userSpecifiedThroughput": 1700
    },
    "id": "TdiW",
    "offerResourceId": "cpBLAJ8b+qw=",
    "offerType": "Invalid",
    "offerVersion": "V2",
    "resource": "dbs/cpBLAA==/colls/cpBLAJ8b+qw=/"
  }
}
This may take 10 minutes to be reflected in the portal.Complete!


test: un-ignore path_can_go_deeper_255_bit

#471  👈
master

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

Join @pepyakin and the rest of your teammates on  Graphite


style: use align-items in hero block

Summary
Related Issue

Checklist

[ ] Tests updated (or not required).
[ ] Documentation updated (or not required).

!canary

!canary


tag_list appearing without the separator (commas) when editing a object

Inserting via form the tags separated by commas (tag1, tag 2...). When editing an object, the tags will apear with no commas (tag1 tag2) inside the form and if you save it will merge into a one giant tag ("tag1 tag2").

Fixed with


Send circuits to Quantum Engine in batches

Each call to Quantum Engine incurs a large overhead in network latency. Currently the only way to batch jobs (and hence reduce this overhead) is to use parameter sweeps. However, it is well known that parameter sweeps have serious limitations, such as the inability of many circuit optimizers to handle parameters. It would be very useful to be able to send non-parameterized circuits in batches too.
@dabacon

This is now completed.  See https://cirq.readthedocs.io/en/latest/google/engine.html#running-circuits-in-batch for details.

#3135 for follow up thoughts on the interface


squid:S1155 - Collection.isEmpty() should be used to test for emptiness

This pull request is focused on resolving occurrences of Sonar rule
squid:S1155 - Collection.isEmpty() should be used to test for emptiness.
You can find more information about the issue here:
https://dev.eclipse.org/sonar/rules/show/squid:S1155
Please let me know if you have any questions.
George Kankava

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

ok to test

jenkins retest this

@mswiderski Sorry about that. PR Updated.


Enable DMA for STM32L4 SPI

Enable DMA for eS-WiFi communication
Use low power waiting for adapter ready
Fix clock setup

bors r+

bors r+


todayButton styles are overriding the rest

When the Today button is set, the entire calendar turns gray (#f0f0f0? the same color as the Today button). This started happening after upgrading from 0.29.0 to 0.33.0. It is occurring on the example page as well for the Today button example: https://hacker0x01.github.io/react-datepicker/#example-3

The button takes the complete height of the calendar. Shouldn't .react-datepicker__today-button have clear:left?

This issue was caused in 6ec4cb9ad2ef0393a9d66519b4bf51e896104bda, specifically in https://github.com/Hacker0x01/react-datepicker/commit/6ec4cb9ad2ef0393a9d66519b4bf51e896104bda#diff-9da5657b359639ae904fe748a1fb2b4cR119.


Add systemd service file

Adding systemd service file to support systemd initialization manager.
Issue: #36
Test: Verified service on Ubuntu
Signed-off-by: Ritul Jasuja<EMAIL_ADDRESS>

@lucasdemarchi Please review.

Thank you, pull request merged! :octocat: Sent from GH.

The comment above was done by mistake. I'll review the correct PR.


pb-java v1.0.0

version update v1.0.0
Now support following functionality
talk(botname, input)
talk(botname, clientId, input)
talk(botname, clientId, input, extra) //with recent calls always true
atalk(botname,input)
atalk(botname,clientId,input)
atalk(botname,clientId,input,extra) //with recent calls always true

Necessary changes made in atalkDebugBot and README.md


Compatibility with doctrine/mongodb-odm

https://github.com/Atlantic18/DoctrineExtensions/blob/fbc95cd0d22560000e82eb6838011b366425d16c/lib/Gedmo/SoftDeleteable/Filter/ODM/SoftDeleteableFilter.php#L22
Here we must return array to comply to function signature.

Completed already in the master branch. Please give the 3.0-dev version a shot if you'd like to test MongoDB ODM 2.0 compatibility.

@AkenRoberts great, thanks. I'll try it.


Weird coordinates under chi_tra_vert.traineddata

Hi, many thanks to this fantastic work and all of you!
I am here to report some wired situations about coordinates when chi_tra_vert_*.traineddata is used.

tesseract 4.1.0
leptonica-1.78.0
libgif 5.1.4 : libjpeg 9c : libpng 1.6.37 : libtiff 4.0.10 : zlib 1.2.11 : libwebp 1.0.2 : libopenjp2 2.3.1
Found AVX2
Found AVX
Found SSE
Found libarchive 3.3.3 zlib/1.2.11 liblzma/5.2.4 bz2lib/1.0.6

ProductName:	Mac OS X
ProductVersion:	10.13.6
BuildVersion:	17G65

tesseract with makebox set all characters' X coordinates and their width to zero
tesseract [--oem 1] chi_tra_vert_test_1.jpg chi_tra_vert_1_test -l chi_tra_vert makebox

tesseract with lstmbox failed
tesseract [--oem 1] chi_tra_vert_test_2.jpg chi_tra_vert_2_test -l chi_tra_vert lstmbox

And here are my questions:

Why I got wrong coordinates?
Why the OCR characters results are right while their coordinates are wrong?
Though nothing related to the wired  cases. Noticed that the vertical Chinese characters are only supported by 4.x versions, and 4.x versions only have the line-level bounding-boxs as their labeled data. How can the tesseract recognize the single character in the line?
Noticed that there is not GPUs training method, it's a little disturbing to train a lstm-based nerual network with CPUs, any experience(datasets amount and the time cost, etc) would really help!

Best!

@amitdo, I transferred it now.

Thanks!

Now I See that the OP already posted this issue with different title here:
#2679

So let's close the current one as a duplicate.


Vegeta sends RST_STREAM with 'cancel' error flag on a closed stream

Version and Runtime
Vegeta 12.8.3
Golang: go1.15.2 linux/amd64
Version: 12.8.3
Commit: d9b795aec8585a0fb435072f68d842d596c332de
Runtime: go1.14 linux/amd64
Date: 2020-03-25T11:03:54Z"

Expected Behaviour
After the server sends DATA with END_STREAM flag Vegeta should not send anything more in the same stream.
Actual Behaviour
Vegeta sends an HTTP2 request to the server. The HEADERS frame contains END_STREAM flag so after processing the request the server sets the stream to HALF_CLOSED_REMOTE state (as per https://tools.ietf.org/html/rfc7540#section-5.1).
Then the server sends the response and the DATA frame contains the END_STREAM flag to fully close it.
So far so good.
But in some cases Vegeta also sends a new frame for the same stream with error code CANCEL (https://tools.ietf.org/html/rfc7540#section-7). Spec complaint server may complain here with connection error (https://tools.ietf.org/html/rfc7540#section-5.4.1)
Steps to Reproduce
I've found this issue while trying to load test Apache Tomcat web server.

Download Tomcat from https://tomcat.apache.org/download-90.cgi
Unzip/Untar it
Edit /path/to/tomcat/conf/server.conf and remove the comments around this connector: https://github.com/apache/tomcat/blob/27c4109a7a686b71454205faab909e5e1f041b18/conf/server.xml#L102-L113
Generate self-signed certificate and update the paths for certificateKeyFile and certificateFile attributes. The certificateChainFile attribute could be removed.
Start Tomcat with: cd /path/to/tomcat/, ./bin/startup.sh
Check ./logs/catalina.out that there are no errors
Run Vegeta against Tomcat:

     echo -e '{"method": "GET", "url": "https://localhost:8443/examples/index.html"}' | vegeta attack -format=json -http2 -rate=0 -max-workers=100 -insecure -duration=5s | vegeta encode > /tmp/http2.json; and vegeta report -type=json /tmp/http2.json | jq .

Additional Context
There is a discussion about this at https://lists.apache.org/thread.html/r6f9ce1521346d5ced72c82a4b5d882a624514c9a7b308ad54f064ba1%40<users.tomcat.apache.org>

The issue seems related to https://github.com/golang/go/issues/27208
Since https://github.com/golang/net/commit/1c5f79cfb1642860bbe00b6cfce66700c01e04f6 if there is a problem with reading the response body the http client will send RST_STREAM with Cancel error. But since the server has closed the stream the processing of the RST_STREAM frame will lead to more errors.


make installer manjaro compatible

would be a shame if this were only compatible with ubuntu 14.04

I've been thinking about this and similar requests we've been receiving internally.
It will probably make more sense to write manual setup instructions for Linux.
There are just too many distributions out there to support and maintain an automated setup script for all of them.

i totally agree that its not a good idea to attempt a multiplatform install script.
it should be made possible and clear though that this great project can be used with other distros than nubuntu.
I am looking forward to a CONTRIBUTING.md file and will gladly create a wiki page with install instructions for arch based systems according to the instructions i find there.


Blank chart in PDF when using wkhtmltopdf

Hi,
I'm using c3.js (http://c3js.org/) and wkhtmltopdf (http://wkhtmltopdf.org/) to generate a PDF of the HTML page my chart lives on. My chart displays fine in the browser but is blank in wkhtmlpdf. Wkhtmltopdf reports no Javascript errors but the resulting PDF does not include the chart. Does anyone have a work around for this?
./wkhtmltopdf --javascript-delay 5000 "http://c3js.org/samples/chart_donut.html" ~/test.pdf

Hi,
Can you ask in Google Group https://groups.google.com/forum/#!forum/c3js ? As you can see here https://github.com/masayuki0812/c3#using-the-issue-queue , Github issues are for bug reports and feature requests only.


math lib

Add mathlib for jou
(sorry, my now repo doesn’t update to the old pull request, so l created a new one)

Successed

A better solution would be to make a new branch before you edit the files. The problem is that you make all your pull requests from your main branch.

Turns out that neither pow10 nor exp10 work on Windows. But that's fine: we don't really need them since you can do pow(10, x) anyway.

Thanks for working on this!


Files manager

This branch adds a manager-esque FilesManager to handle files, with accompanying tests.
Please review #120 first (I merged that into this branch; writing these tests were how I realized how loose the mock service was)

[Current coverage][cc-pull] is 88.14%

Merging [#121][cc-pull] into [master][cc-base-branch] will increase coverage by 1.39%

@@             master       #121   diff @@
==========================================
  Files            10         10
  Lines           362        371     +9
  Methods           0          0
  Messages          0          0
  Branches         50         50
==========================================
+ Hits            314        327    +13
+ Misses           34         30     -4
  Partials         14         14

Powered by Codecov. Last updated by [2e3b0b2...f52fd9b][cc-compare]
[cc-base-branch]: https://codecov.io/gh/lxc/pylxd/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/lxc/pylxd/compare/2e3b0b203b095ff950b0bb81527d5d730f9cc7bd...f52fd9b2da193b3b651553357f7984c6d07cc00d
[cc-pull]: https://codecov.io/gh/lxc/pylxd/pull/121?src=pr

lgtm


[BEAM-234] Remove last vestige of the words DirectPipeline

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @davorbonaci

LGTM, but we could have bundled this PR in a bigger change.


[VS Code] RPC connection closed.

Error:
RPC connection closed.
Steps to Reproduce:

Version Data

extensionName
VSLS

extensionVersion
0.3.709

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.27.2

platformName
MacOS

platformVersion
17.7.0

@daytonellwanger My partner use vscode for win10 , it reproduced about 4 or 5 times in a whole day.

Hey @luckymark , let me make sure I understand. You use Live Share session with a partner on VS Code on Win10. You're also on VS Code, but on Mac. In the middle of a Live Share session - about 4/5 times anyway - the session abruptly ends and you get a notification that says "RPC connection closed?"

I got the same error here are my logs if you need them
LiveShareLogs.zip

Experiencing the same error on Mac OSX. The session does not abruptly end, but it does not even start. The error appears right away when starting a new session.

We're already tracking this issue via #1353, so I'm going to close this as a duplicate. Note that I migrated over your logs as well.


Constant Moonraker warnings

Describe the bug
Moonraker shows warning:
Moonraker warnings found.
file_manager: Klipper configuration file not located in 'config' folder.

Klipper Config Path: /etc/klipper.cfg

Config Folder: /var/lib/moonraker/config

Steps To Reproduce
Steps to reproduce the behavior:
services.moonraker = {
  ## Requires group klipper to access /run/klipper/api socket
  group = "klipper";
  enable = true;
  address = "<IP_ADDRESS>";

  # Allows control of system wide reboot, shutdown etc via client API
  allowSystemControl = true;

  settings = {
    server = {
      max_upload_size = 16384;
    };
    octoprint_compat = {
      enable_ufp = true;
      webcam_enabled = true;
    };
    authorization = {
      force_logins = true;
      cors_domains = [
        "http://*.lan"
        "http://*.local"
      ];
      trusted_clients = [
        "<IP_ADDRESS>/8"
        "<IP_ADDRESS>"
      ];
    };
  };
};

users.groups.klipper = {
  gid = 982;
};
users.users.klipper = {
  uid = 982;
  group = "klipper";
  isSystemUser = true;
};

services.klipper = {
  package = cfg.package;
  enable = true;
  # I think octoprint integration requires the same user
  # as octoprint, thus 'octoprint' by default.
  # Thus, we cannot set it without a conflict if we're using octoprint.
  user = "klipper";
  group = "klipper";
  # DO NOT ENABLE! DOES NOT TRIGGER UPDATES WHEN CHANGE
  # copy config to mutable file path
  # mutableConfig = true;
    firmwares = {
      mcu = {
        enable = true;
        configFile = ./printers/${cfg.printerType}/mcu.env;
      };
    };
};

Expected behavior
No warnings.
Screenshots

Notify maintainers

@cab404
@vtuan10
@zhaofengli
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"aarch64-linux"`
 - host os: `Linux 6.1.52, NixOS, 23.11 (Tapir), 23.11.20231128.7c4c205`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - nixpkgs: `/etc/nixPath`

Annoys me a great deal as well. Trying to figure out, why it even matters.

Well, it's just a no-wont-change, without any reason really. So I guess we either have to patch that part out, or just place the configuration file in the moonraker configuration directory, Which seems rather annoying.

Moonraker provides a script for MainsailOS and FluiddPi which fixes this by creating a symlink. How about we do the same or add a bind mount to the serviceConfig?

Moonraker provides a script for MainsailOS and FluiddPi which fixes this by creating a symlink. How about we do the same or add a bind mount to the serviceConfig?

That doesn't work, I've tried it out (symlink), and am currently trying to find a solution here https://github.com/Arksine/moonraker/issues/767 .
It seems like there will be provided a way to opt out, which would be ideal, or if the symlink part worked then it would also be OK.
If symlink worked, then the following could be added to the moonraker module
  systemd.tmpfiles.rules = [
    "L /var/lib/moonraker/config/klipper.cfg - - - - /etc/klipper.cfg"
  ];

For now I'm just patching the moonraker package using the following (not recommended, hopefully moonraker will be updated soon-ish).
{ pkgs, ... }:

let
  moonrakerConfigPatch = pkgs.writeText "moonraker-config.patch" ''
diff --git a/moonraker/components/file_manager/file_manager.py b/moonraker/components/file_manager/file_manager.py
index edae73f..7379e0d 100644
--- a/moonraker/components/file_manager/file_manager.py
+++ b/moonraker/components/file_manager/file_manager.py
@@ -194,26 +194,6 @@ class FileManager:
             self.server.register_static_file_handler(
                 "klippy.log", log_path, force=True)

-        # Validate config file
-        cfg_file: Optional[str] = paths.get("config_file")
-        cfg_parent = self.file_paths.get("config")
-        if cfg_file is not None and cfg_parent is not None:
-            cfg_path = pathlib.Path(cfg_file).expanduser()
-            par_path = pathlib.Path(cfg_parent)
-            if (
-                par_path in cfg_path.parents or
-                par_path.resolve() in cfg_path.resolve().parents
-            ):
-                self.server.remove_warning("klipper_config")
-            else:
-                self.server.add_warning(
-                    "file_manager: Klipper configuration file not located in "
-                    "'config' folder.\n\n"
-                    f"Klipper Config Path: {cfg_path}\n\n"
-                    f"Config Folder: {par_path}",
-                    warn_id="klipper_config"
-                )
-
     def validate_gcode_path(self, gc_path: str) -> None:
         gc_dir = pathlib.Path(gc_path).expanduser()
         if "gcodes" in self.file_paths:
'';
in {
  services.moonraker = {
    package = pkgs.moonraker.overrideAttrs (fAttrs: pAttrs: {
      patches = [ moonrakerConfigPatch ];
    });
  };
}

I've opened two PRs. One that bumps the moonraker package to include a commit that has the option file_manager.check_klipper_config_path, which can be set false.
And another one, that sets this to false, if NixOS manages the klipper configuration.

@eyjhb Oh, nice! Thank you! :) I... briefly spoke to them about this myself, and they, for some bizarre reason, just 'recommended' I use Debian, and seemed totally disinterested in fixing the problem. I'm glad you got something to work! :)

@eyJhb Oh, nice! Thank you! :) I... briefly spoke to them about this myself, and they, for some bizarre reason, just 'recommended' I use Debian, and seemed totally disinterested in fixing the problem. I'm glad you got something to work! :D

I think they mostly opposed that it was formulated as NixOS is using "hacks" to run their software (which I understand a maintainer does not want to deal with), however, this warning has nothing to do with anything NixOS related as such. :) - But yeah, initially they seemed disinterested in discussing any kind of work-around, but I'm happy that we came to an agreement with the maintainer, without (hopefully), being too much of a inconvenience :)
If anyone wants to run have a temp override, then it's available here
    package = pkgs.moonraker.overrideAttrs (fAttrs: pAttrs: {
      version = "unstable-2023-12-1$";

      src = pkgs.fetchFromGitHub {
        owner = "Arksine";
        repo = "moonraker";
        rev = "42357891a3716cd332ef60b28af09f8732dbf67a";
        sha256 = "sha256-5w336GaHUkbmhAPvhOO3kNW5q7qTFVw3p0Q+Rv+YdYM=";
      };
    });

@eyJhb

I think they mostly opposed that it was formulated as NixOS is using "hacks" to run their software

I guess the word 'hacks' has different connotation for me than it does for some devs. I'll have to watch that in the future! :P


Please add a per-application startup-folder option for workspaces

Description of the new feature / enhancement
Workspaces is great for launching multiple apps simultaneously. It provides long overdue functionality for Windows. The one thing I haven't reliably been able to do so far is customize the settings for all applications in such a way as to specify their startup-folder location. With some applications (e.g., Windows Terminal), I can add another command-line parameter (-d <path>) that seems to work. But many applications often lack this ability. I know that the Windows API methods to launch processes all take startup paths, so it would be a trivial addition to the existing data set but pay a lot of dividends in time saved for opening/saving files from within those applications and other startup-folder sensitive operations.
Scenario when this would be used?
For applications that don't offer a command-line option to specify a startup folder, this would be helpful in many scenarios:

Standard open/save dialogs starting in the folder I want them to by default, rather than having to change them every single time.
Applications being able to find their proper set of configuration files based on startup path.
Applications that generate files in the same folder as their executable dumping them where I actually want them.

And many more.
Supporting information
I think the ask is pretty clear, but as a Windows developer I'll put it this way:

Add UI to capture startup paths.
Add UI to edit application startup paths--please allow environment variables to be referenced by said UI!
Add code to resolve those startup paths when launching to hand them off to the Windows process-related APIs.

Interesting idea and something we should look into.


⚠ Tyre Pharmacy has degraded performance

In 94eec9b, Tyre Pharmacy (https://tyrepharm.ru/) experienced degraded performance:

HTTP code: 200
Response time: 10485 ms

Resolved: Tyre Pharmacy performance has improved in f9d7635 after 11 minutes.


Bump the version of chef depending on the label associated with PR

Description
Introduces new functionality to our CI system that allows us to control the type of version bump we want for a given PR based on the Labels applied. With this, we can do proper semver while still automatically bumping our versions as necessary.
As it stands, the existing behavior of bumping the patch level on every merge will continue. Once we have the necessary labels created we can migrate to using those.
In the near future we plan to roll out a Github status check that will ensure we have the appropriate labeling applied to a PR before it can be merged.
Check List

[ ] New functionality includes tests
[ ] All tests pass
[ ] RELEASE_NOTES.md, has been updated if required (not required for bugfixes, required for API changes)
[ ] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco

Should probably go to the developer's meeting and an RFC.

@lamont-granquist is there a specific aspect of this that you think requires an RFC? There's nothing in RFC047 that specifically mentions the method by which we bump our version, only that we adhere to semver.

We currently have a monthly release cadence of minor versions which people have come to expect, if we're planning on changing that it should probably go through the RFC process, even if it isn't written down anywhere yet (it really should be).

So major bumps should definitely get removed IMO, the risks of a bad bump seem to me to outweigh the work of doing it by hand once a year. For minor revs, this seems like it would do one minor rev per tagged PR, which is not how I think you meant this to work? Regardless, I would like to see a "plot explanation" as to the goals of the change and reason for it. An RFC works or you can write something up in here :-) I think there is a general feeling from the community that the release process is getting un-grokably complex so changes to it should get higher levels of scrutiny at this point.

This is a change that gets us much closer to the actual stated aims of SemVer, as well as the process documented in RFC 47 - specifically, that when we add new features, rather than improvements or bug fixes, we'll bump the minor version. I don't think we need an RFC, but we are intending to communicate via the usual channels (developer meeting, discourse, etc) when this takes effect.
The main point to this change is that it makes it possible to safely do security point releases or regression releases - since right now a human having hand bumped the minor version number post release is the only demarcation, we've seen that new features get merged after a release but before that version bump, which means that we can't then do a security release for that minor without dragging along new features, too.
We'll still have a monthly cadence of releases that will not deprecate new features or bump major.

This PR was motivated by the recent security issue that affected mixlib-archive. The realization made by the internal Chef teams responsible for cutting new releases was that given our current version bumping model, which bumps the build/patch version on every merge PR,  Chef Maintainers can be put into a situation where a security or hot fix release could be complicated or result in confusion for the user. This complication arises out of a few practices and procedures that exist in how PRs against chef/chef are currently handled.
I’ll start with a review on how Chef is released. Per RFC-087,  once a month (on an agreed upon date) we select a build from the current channel. This is typically the most recent build, but sometimes it is not. The reasons vary but there are many factors that go into deciding which build to promote and we can’t always be sure we’re going to pick the most recent build. Maybe the most recent build has an experimental feature and the consensus is that it’s not ready. Maybe X.Y.Z has a bug, but X.Y.Z-1 does not so to try and stay within the timeline provided by RFC-087 we select X.Y.Z-1. Sometimes it is a better choice not to select the most recent build but instead some build from the recent past.
After the build has been selected we bless this build and notify the community that it X.Y.Z is our release candidate. Per RFC-087, there is a waiting period before we can formally promote that build to stable. During this time, there is currently no “code freeze” on master, meaning that new feature code could be merged to master resulting in builds for X.Y.Z+1 and X.Y.Z+2. The current practice is not to immediately bump the minor version to X.Y+1 (though doing so would still not protect us against scenarios mentioned in the previous paragraph).
So, the current scenario we are in is that X.Y.Z could have an issue that requires a security or hot-fix. With the current processes (and other factors that I outlined above) there is no guarantee that version X.Y.Z+1 is available or that X.Y.Z+N would not contain new functionality that was not given adequate time to be tested during the waiting period. The end result is that to get the security or hot-fix out we would either need to a) also include the new functionality, b) release X.Y.Z+N (but not include the functionality that was introduced in the interim), or c) release the hot fix as X.Y+1.0 and make next month’s release X.Y+2.Z.
So when looking to address this problem a number of solutions came up but the current design was motivated around the following guideline from RFC-047:
Given a version number MAJOR.MINOR.BUILD:

Increment the MAJOR version when the release will break existing functionality
Increment the MINOR version when you add any new features
The BUILD version is the same as PATCH, but is increased automatically by the build system

The guideline regarding the MINOR version is not a guideline we currently follow. Right now the MINOR version gets bumped once per month regardless of whether any new features were added. Additionally, the BUILD/PATCH version will get bumped on every PR merge even if the resulting Chef gem/binary would have no changes (in the cases where documentation, travis, or other non-binary related files are the only ones changed) resulting in the potential situation where X.Y.Z and X.Y.Z+1 are functionally identical.
During my analysis I determined that it would be pretty simple to add new functionality to chef/chef’s version bumping logic (housed within chef/chef’s Rakefile) that could bump the version based on the labels associated with the PR, thereby giving control to Maintainers to determine version bumping at the time of PR review. This label-based process would be functionally equivalent to manually bumping the version in that it would have the following benefits:

We could decide not bump the version (and thus not trigger a build) if it was not necessary (in the case of changes to non-binary files such as tests, documentation, etc).
We could give Chef Maintainers more fine-grained control over whether a patch or minor bump was necessary on a per-PR basis, allowing us to be in compliance with RFC-047.
Because of the above, security and hot-fixes could be easily cherry-picked to MAJ.MIN “branches” even after new functionality is merged.

Now, using the label-based automation rather than manually bumping the version continues to give us the following benefits:

The process is easily repeatable and does not require an additional PR.
Because every bump still results in a build, it would not increase the time it would take for users to receive fixes via the current channel.
It does not add additional burden on Maintainers to manually bump and trigger new releases.
Whether or not a PR deserved a MINOR bump could be changed without requiring a new commit be pushed to the branch.  This could be useful if it was determined that several “new feature” PRs should be merged but only have a single MINOR version bump.
This same process, if successful, could be easily applied to other Chef OSS projects, resulting in a consistent experience for maintainers across a variety of products.

Now I understand there is some concern that the change in versioning structure could cause confusion with users. To that I might argue that the bump to Chef 13 would be a perfect time to establish a new versioning pattern. We’ve already made it clear to our users that things are going to change post Chef 13, and tweaking the rate at which MINOR versions increment I think will be relatively minor. It might even have some unintended positive benefits to users who install from current in their ability to live on the edge but still have some control on the new functionality that enters into their systems.
I also want to emphasize that the way in which we communicate with the users about stable releases will not change. We will still make monthly releases where the release notes will contain all the changes since the previous stable release and the changelog would also continue to make stable releases it's section headers (regardless of how many minor release bumps occurred during that time).
With resources like discourse.chef.io and  downloads.chef.io I think that users will have access to all the information they need to know what the latest version of Chef is, how many releases are they behind, and what has changed since their last release. I know that the Chef Community team, and Chef Software as a whole, is heavily invested in ensuring that users are successful with Chef. If the switch to adhering to RFC-047 leads to confusion amongst our users I’m confident that we will find ways to address that confusion.
If you have any further questions or clarifications, please let me know and I’ll be happy to speak to them asynchronously.

You're still going to have the problem where PRs labelled as "patches" are still being merged to master without bumping the minor version.  That means if you pick 13.2.45 as the release candidate it is entirely possible that 13.2.46, 13.2.47 and 13.2.48 are submitted after the rc has been picked and only labelled to do a minor bump.
The problem that I see with that is that those assignments are being made by humans, and there's no agreement over what constitutes a "patch" or a "minor" release.  The SemVer policy itself is fairly vague on this statement, and its particularly vague when its applied to chef-client and the definition of what is a formally documented public API and what is not becomes blurry.
And to backtrack a bit on history, RFC-047 is not the latest agreement on what our version numbering policy means.  At the time that all of the gem locking rake tasks were added into the chef/chef project there was a meeting where it was discussed as to what the version numbers on the project meant.  At that meeting it was agreed upon that we'd modify SemVer.  And one of the reasons why we would do that is that there was no reliable definition of what minor and patch release were.  Since we were adopting a more continuous delivery model then we would treat the minor number as the blessed release number, and the patch number would become a build number.   This agreement was made in a meeting in Chef HQ and apparently never made it into any RFC.
The way that I see it, if you want to really ensure that we can do security releases of the latest release of chef-client then we need to clearly think about what we're doing which is supporting a branching model.  Once we have picked an rc we need to not do any subsequent patch release and the minor number needs to be incremented.  So when 13.2.45 is picked as a release candidate master becomes 13.3.0 for the next commit.  Then if there are build issues or subsequent security issues those get cherry-picked onto 13.2.46, 13.2.47, etc.
Another model is that we simply adopt that the minor version becomes the build version and every commit is auto bumped so that 13.45.0 becomes the release candidate.  Then 13.45.1 becomes available as the next patch release.  Most releases in currently would then be dot-zero releases, and we would have very large build numbers (13.231.0 would be the 231st commit past 13.0.0 on master).
The model being proposed does not seem to me to address the problem of additional commits past the rc since it allow "patchy" commits.  And it clearly opens up the hole where someone submits a "patchy" commit and then later does an "oopsie that should have been a minor version bump" but with properly immutable artifacts there's no way to renumber them and erase that mistake.

Also one other thing is that I brought up this problem in that meeting at Chef HQ and wanted it addressed.  I was told very clearly that the new CI/CD way of doing things was that master just rolled forwards and that we would never branch for security fixes, and the train just kept running straight down the tracks.
I had my doubts about that, and the person who was most vocal about that model has left the company and it seems that we want to address this problem now.  However, I do not see how this proposal even fixes the problem.

So to summarize what I said at the dev meeting, I think before we discuss the specifics of this proposal we need to drop down a level and talk about semantic information in version numbers. I think there are somewhat distinct camps on this and without some agreement (or at least someone above me on the org chart picking a side and saying we're doing that now) I think we're going to keep talking past each other. I will try to summarize both but since I am very biased please call me out if I'm strawman-ing here.
On one side is the view that version numbers are largely consumed by automated tools and that as long as we follow SemVer, the specifics aren't super important. In this view the important semantic data when comparing two version numbers (other than major rev for compat level which I think we all agree on) is just "newer" or "older" (or "same" but again, ignoring that case). I think the argument here is that in general people tend to set aside time to upgrade based on their own schedule (which was discussed a lot in the CalVer RFC and related stuffs) and are going to just pick whatever version is current and upgrade to that with whatever work that entails.
The other side is saying that having a rough "distance" measure between two version numbers is useful beyond just knowing which is more recent. Seeing 12.9 and then 12.14 you can get a rough idea of how far apart in both time and therefore code without any additional information.
Further complicating this talk about version numbers is the fact that we've already done this conversion on the patch number, effectively making it only useful for relative comparisons. I think that case is very different because the goal from the start was that we would only ever promote one (or maybe two if we need to fix a blocker) version for a given minor release. This is now reflected in how we talk about version numbers, instead of talking about 11.16.2 we just say 12.18 and that's generally unambiguous. This is very different from the effect of de-information-ing the minor number.
Given the very strong user expectations that 13.0 will be followed by 13.1, combined with the benefits from being able to judge "distance" between two stable releases, I think that we should try to preserve these properties in the version number. We could still do that with a label-based auto-bump, but I'm not sure it would be worth the extra complexity. That would mean that once a month someone would have to submit a bumper PR with a label rather than a PR that just changes the version like we do now.
I would also like to echo Lamont's concerns that even if we do end up with the minor rev being a monotonic incrementer and nothing more, that this is still not a great solution to the original problem because the "CD from master all the time" structure is itself the part that makes hotfix branching difficult. This was understood when we moved to it, that we just wouldn't do those and would require users to get other changes sometimes. I'm still not a huge fan of the CD approach and I'm totally on-board with making hotfix branches easier but I think it's going to require a much deeper re-evaluation of how we do releases.

To throw another possible solution inspired from Applesoft BASIC into the mix:
We can continue to abuse the patch version and have it autoincrement by 10 or even 100 on every commit.  That leaves open future versions for branching after every single commit.  If we went with 100x then that leaves open two digits which could be used to communicate to users, where the ones digit could be simple "oopses" while the tens would get incremented for security releases.  So 12.19.3300 would be the RC, 12.19.3301 would be the first "oops", while 12.19.3310 would be the "openssl broke the world (again)" release.  Of course that only leaves 10 slots open for "oops"es.
Basically, that keeps the minor number human-meaningful, while abusing the patch number to accomplish whatever goals we want.

I think it'd be useful to shift the conversation over to https://github.com/chef/chef-rfc/pull/250.


Publish to NPM

[ ] Update all docs to point to the new package rather than @react-native-mapbox-gl/maps