[BUG] ...Just got new fix for YNAB Toolkit and it was working for a few hours. Now I get a Toolkit error when I open YNAB in Chrome.

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

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. OSX, Windows]
Browser [e.g. chrome, firefox]
Toolkit Version [e.g. 2.22.0]

Setting Export
Please replace the text 'REPLACE_ME_WITH_SETTINGS' below with your exported Toolkit settings. You can export these by going to the Toolkit Options page, click the Import/Export Settings button at the top right and copying the text in the modal which appears.
Note! DO NOT replace the leading and trailing ``` characters as they are required formatting characters.
REPLACE_ME_WITH_SETTINGS

Just refreshed my ynab and got the following.....    "An error occurred in Toolkit for YNAB (a browser extension you installed to enhance YNAB). Click here to report the issue to the YNAB Toolkit project."   I assume it is the same as above as yesterday did not have a lot of my toolkit options like reports/pacing showing

Same here in Chrome :-(

I'm seeing the same thing in Brave. Still seeing it after updating and can't use YNAB unless I disable the toolkit.

Same!  The popup wont go away so cannot use YNAB, and without the toolkit there is a ton I can't do.

 UUID: 686c221f-a1c2-478f-fa65-8cd49d372ccd

Settings:
[{"key":"AccountsDisplayDensity","value":"0"},{"key":"AccountsEmphasizedInflows","value":false},{"key":"AccountsEmphasizedOutflows","value":false},{"key":"AccountsStripedRows","value":false},{"key":"AccountsStripedRowsColor","value":"#fafafa"},{"key":"AccountsStripedRowsDarkColor","value":"#1e1e1f"},{"key":"AssistedClear","value":false},{"key":"AutoDistributeSplits","value":false},{"key":"AutoEnableRunningBalance","value":false},{"key":"AutomaticallyMarkAsCleared","value":false},{"key":"BetterScrollbars","value":"0"},{"key":"BottomNotificationBar","value":false},{"key":"BudgetCategoryFeatures","value":true},{"key":"BudgetProgressBars","value":"0"},{"key":"BudgetQuickSwitch","value":false},{"key":"BudgetSpendingGoal","value":false},{"key":"BulkEditMemo","value":true},{"key":"BulkManagePayees","value":false},{"key":"CalculateIRR","value":false},{"key":"CalendarFirstDay","value":"0"},{"key":"CategoryActivityCopy","value":false},{"key":"CategoryActivityPopupWidth","value":"0"},{"key":"CategorySoloMode","value":"0"},{"key":"ChangeEnterBehavior","value":false},{"key":"ChangeMemoEnterBehavior","value":false},{"key":"CheckCreditBalances","value":true},{"key":"CheckNumbers","value":false},{"key":"ClearSelection","value":false},{"key":"CollapseInspector","value":false},{"key":"ColourBlindMode","value":false},{"key":"CompactAccountHeader","value":false},{"key":"CompactIncomeVsExpense","value":false},{"key":"ConfirmEditTransactionCancellation","value":false},{"key":"ConfirmKeyboardCancelationOfTransactionChanges","value":false},{"key":"CreditCardEmoji","value":false},{"key":"CtrlEnterCleared","value":false},{"key":"CurrentMonthIndicator","value":false},{"key":"CustomAverageBudgeting","value":false},{"key":"CustomFlagNames","value":false},{"key":"CustomizeColourScheme","value":true},{"key":"DateOfMoney","value":false},{"key":"DaysOfBuffering","value":false},{"key":"DaysOfBufferingDate","value":false},{"key":"DaysOfBufferingExcludeCreditCards","value":false},{"key":"DaysOfBufferingHistoryLookup","value":"0"},{"key":"DefaultCCToCleared","value":false},{"key":"DeselectTransactionsOnSave","value":false},{"key":"DisableToolkit","value":false},{"key":"DisplayMonthlyGoalsOverview","value":false},{"key":"DisplayTargetGoalAmount","value":"0"},{"key":"DisplayTotalMonthlyGoals","value":false},{"key":"DisplayTotalOverspent","value":false},{"key":"DisplayUpcomingAmount","value":false},{"key":"EasyTransactionApproval","value":false},{"key":"EditAccountButton","value":"0"},{"key":"EmphasizeNegativeLoans","value":false},{"key":"EnlargeCategoriesDropdown","value":true},{"key":"FilterCategories","value":true},{"key":"GoalIndicator","value":false},{"key":"GoalWarningColor","value":false},{"key":"GoogleFontsSelector","value":"0"},{"key":"HideAccountBalancesType","value":"0"},{"key":"HideAgeOfMoney","value":false},{"key":"HideClosedAccounts","value":false},{"key":"HideDebtRatio","value":false},{"key":"HideHelp","value":false},{"key":"HideReferralBanner","value":false},{"key":"HideTotalAvailable","value":false},{"key":"HighlightNegatives","value":false},{"key":"HoveredBudgetRows","value":false},{"key":"ImportNotification","value":"0"},{"key":"IncomeFromLastMonth","value":"0"},{"key":"IncomeVsExpenseHoverHighlight","value":true},{"key":"LargerClickableIcons","value":false},{"key":"LastReconciledDate","value":false},{"key":"LinkInMemo","value":false},{"key":"LinkToInflows","value":false},{"key":"LiveOnLastMonthsIncome","value":"0"},{"key":"MasterCategoryRowColor","value":false},{"key":"MasterCategoryRowColorSelect","value":"#d1d1d6"},{"key":"MasterCategoryRowDarkColorSelect","value":"#636366"},{"key":"MemoAsMarkdown","value":false},{"key":"MonthlyNotesPopupWidth","value":"0"},{"key":"NavDisplayDensity","value":"0"},{"key":"NotesAsMarkdown","value":false},{"key":"POSStyleCurrencyEntryMode","value":false},{"key":"Pacing","value":"2"},{"key":"PrintingImprovements","value":true},{"key":"PrivacyMode","value":"0"},{"key":"QuickBudgetWarning","value":false},{"key":"ReconcileAssistant","value":false},{"key":"ReconcileBalance","value":false},{"key":"ReconcileConfetti","value":false},{"key":"ReconciledTextColor","value":"0"},{"key":"RemovePositiveHighlight","value":false},{"key":"RemoveZeroCategories","value":false},{"key":"ResetColumnWidths","value":true},{"key":"RightClickToEdit","value":true},{"key":"RowHeight","value":"0"},{"key":"RowsHeight","value":"0"},{"key":"SavingsRatio","value":"0.10"},{"key":"ScrollableEditMenu","value":false},{"key":"SeamlessBudgetHeader","value":false},{"key":"SetMultipleFlags","value":false},{"key":"ShowAvailableAfterSavings","value":false},{"key":"ShowCategoryBalance","value":false},{"key":"SpareChange","value":false},{"key":"SplitTransactionAutoAdjust","value":false},{"key":"SplitTransactionAutoFillPayee","value":false},{"key":"SplitTransactionTabExpand","value":false},{"key":"SquareNegativeMode","value":false},{"key":"StealingFromFuture","value":false},{"key":"StripedBudgetRows","value":false},{"key":"SubtractUpcomingFromAvailable","value":"0"},{"key":"SwapClearedFlagged","value":false},{"key":"TargetBalanceWarning","value":false},{"key":"ToBeBudgetedWarning","value":false},{"key":"ToggleAccountColumns","value":true},{"key":"ToggleMasterCategories","value":false},{"key":"ToggleSplits","value":false},{"key":"ToggleTransactionFilters","value":"0"},{"key":"ToolkitReports","value":true},{"key":"UnclearedAccountHighlight","value":false},{"key":"ViewZeroAsEmpty","value":false},{"key":"l10n","value":"0"}]

The toolkit reports are not functioning but the button still seems to be there. Also maybe you have to disable progress bars.

Related, when attempting to reconcile this new error posts to console:
chunk.48e74788d3eed765e6a4.js:2 Error: Use native property getter instead of get wrapper for amount
    at e.get (chunk.48e74788d3eed765e6a4.js:2:3614495)
    at chunk.48e74788d3eed765e6a4.js:2:3389928
    at Array.reduce (<anonymous>)
    at get pendingTransactionsAmount (chunk.48e74788d3eed765e6a4.js:2:3389909)
    at vendor.c9f1f02143d0931f49ad666f027c7611.js:36:73851
    at e.untrack (vendor.c9f1f02143d0931f49ad666f027c7611.js:36:346875)
    at he.get (vendor.c9f1f02143d0931f49ad666f027c7611.js:36:73840)
    at B.r [as pendingTransactionsAmount] (vendor.c9f1f02143d0931f49ad666f027c7611.js:36:71934)
    at B.directImportStep (chunk.48e74788d3eed765e6a4.js:2:3393400)
    at B.startReconciling (chunk.48e74788d3eed765e6a4.js:2:3391838)

@adamflagg do you have any of these settings turned on:

I don't have those and don't have any problem. Is your account to reconcile a loan account? There has been some weird bugs I've noticed with that but they just rolled it out in the last two years.

@adamflagg do you have any of these settings turned on:

I don't have those and don't have any problem. Is your account to reconcile a loan account? There has been some weird bugs I've noticed with that but they just rolled it out in the last two years.

I have all of those turned off and it still does not work for me. I can still use YNAB but none of the features of the Toolkit are working for me.

I don't have any of these 'on' in my toolkit.  I assume I will just have to turn off toolkit in order to use ynab.  Thankfully I was able to reconcile this morning.

@adamflagg do you have any of these settings turned on:

I don't have those and don't have any problem. Is your account to reconcile a loan account? There has been some weird bugs I've noticed with that but they just rolled it out in the last two years.

Also having this issue. It happens by simply opening YNAB in Chrome. I turned off the Accounts options and still have issues.
[{"key":"AccountsDisplayDensity","value":"0"},{"key":"AccountsEmphasizedInflows","value":false},{"key":"AccountsEmphasizedOutflows","value":false},{"key":"AccountsStripedRows","value":false},{"key":"AccountsStripedRowsColor","value":"#fafafa"},{"key":"AccountsStripedRowsDarkColor","value":"#1e1e1f"},{"key":"AssistedClear","value":false},{"key":"AutoDistributeSplits","value":false},{"key":"AutoEnableRunningBalance","value":false},{"key":"AutomaticallyMarkAsCleared","value":false},{"key":"BetterScrollbars","value":"0"},{"key":"BottomNotificationBar","value":false},{"key":"BudgetCategoryFeatures","value":true},{"key":"BudgetProgressBars","value":"0"},{"key":"BudgetQuickSwitch","value":false},{"key":"BudgetSpendingGoal","value":false},{"key":"BulkEditMemo","value":false},{"key":"BulkManagePayees","value":false},{"key":"CalculateIRR","value":false},{"key":"CalendarFirstDay","value":"0"},{"key":"CategoryActivityCopy","value":false},{"key":"CategoryActivityPopupWidth","value":"0"},{"key":"CategorySoloMode","value":"0"},{"key":"ChangeEnterBehavior","value":false},{"key":"ChangeMemoEnterBehavior","value":false},{"key":"CheckCreditBalances","value":true},{"key":"CheckNumbers","value":false},{"key":"ClearSelection","value":false},{"key":"CollapseInspector","value":false},{"key":"ColourBlindMode","value":false},{"key":"CompactAccountHeader","value":false},{"key":"CompactIncomeVsExpense","value":false},{"key":"ConfirmEditTransactionCancellation","value":false},{"key":"ConfirmKeyboardCancelationOfTransactionChanges","value":false},{"key":"CreditCardEmoji","value":false},{"key":"CtrlEnterCleared","value":false},{"key":"CurrentMonthIndicator","value":false},{"key":"CustomAverageBudgeting","value":false},{"key":"CustomFlagNames","value":false},{"key":"CustomizeColourScheme","value":true},{"key":"DateOfMoney","value":false},{"key":"DaysOfBuffering","value":"6"},{"key":"DaysOfBufferingDate","value":false},{"key":"DaysOfBufferingExcludeCreditCards","value":false},{"key":"DaysOfBufferingHistoryLookup","value":"0"},{"key":"DefaultCCToCleared","value":false},{"key":"DeselectTransactionsOnSave","value":false},{"key":"DisableToolkit","value":false},{"key":"DisplayMonthlyGoalsOverview","value":false},{"key":"DisplayTargetGoalAmount","value":"1"},{"key":"DisplayTotalMonthlyGoals","value":false},{"key":"DisplayTotalOverspent","value":false},{"key":"DisplayUpcomingAmount","value":false},{"key":"EasyTransactionApproval","value":false},{"key":"EditAccountButton","value":"0"},{"key":"EmphasizeNegativeLoans","value":false},{"key":"EnlargeCategoriesDropdown","value":true},{"key":"FilterCategories","value":true},{"key":"GoalIndicator","value":true},{"key":"GoalWarningColor","value":false},{"key":"GoogleFontsSelector","value":"0"},{"key":"HideAccountBalancesType","value":"0"},{"key":"HideAgeOfMoney","value":false},{"key":"HideClosedAccounts","value":false},{"key":"HideDebtRatio","value":false},{"key":"HideHelp","value":false},{"key":"HideReferralBanner","value":false},{"key":"HideTotalAvailable","value":false},{"key":"HighlightNegatives","value":false},{"key":"HoveredBudgetRows","value":false},{"key":"ImportNotification","value":"0"},{"key":"IncomeFromLastMonth","value":"1"},{"key":"IncomeVsExpenseHoverHighlight","value":true},{"key":"LargerClickableIcons","value":false},{"key":"LastReconciledDate","value":"disabled"},{"key":"LinkInMemo","value":false},{"key":"LinkToInflows","value":false},{"key":"LiveOnLastMonthsIncome","value":"1"},{"key":"MasterCategoryRowColor","value":false},{"key":"MasterCategoryRowColorSelect","value":"#d1d1d6"},{"key":"MasterCategoryRowDarkColorSelect","value":"#636366"},{"key":"MemoAsMarkdown","value":false},{"key":"MonthlyNotesPopupWidth","value":"0"},{"key":"NavDisplayDensity","value":"0"},{"key":"NotesAsMarkdown","value":false},{"key":"POSStyleCurrencyEntryMode","value":false},{"key":"Pacing","value":"0"},{"key":"PrintingImprovements","value":true},{"key":"PrivacyMode","value":"0"},{"key":"QuickBudgetWarning","value":false},{"key":"ReconcileAssistant","value":false},{"key":"ReconcileBalance","value":false},{"key":"ReconcileConfetti","value":false},{"key":"ReconciledTextColor","value":"0"},{"key":"RemovePositiveHighlight","value":false},{"key":"RemoveZeroCategories","value":false},{"key":"ResetColumnWidths","value":false},{"key":"RightClickToEdit","value":false},{"key":"RowHeight","value":"0"},{"key":"RowsHeight","value":"0"},{"key":"SavingsRatio","value":"0.10"},{"key":"ScrollableEditMenu","value":false},{"key":"SeamlessBudgetHeader","value":false},{"key":"SetMultipleFlags","value":false},{"key":"ShowAvailableAfterSavings","value":false},{"key":"ShowCategoryBalance","value":false},{"key":"SpareChange","value":false},{"key":"SplitTransactionAutoAdjust","value":false},{"key":"SplitTransactionAutoFillPayee","value":false},{"key":"SplitTransactionTabExpand","value":false},{"key":"SquareNegativeMode","value":false},{"key":"StealingFromFuture","value":true},{"key":"StripedBudgetRows","value":false},{"key":"SubtractUpcomingFromAvailable","value":"0"},{"key":"SwapClearedFlagged","value":false},{"key":"TargetBalanceWarning","value":false},{"key":"ToBeBudgetedWarning","value":false},{"key":"ToggleAccountColumns","value":false},{"key":"ToggleMasterCategories","value":false},{"key":"ToggleSplits","value":false},{"key":"ToggleTransactionFilters","value":"0"},{"key":"ToolkitReports","value":true},{"key":"UnclearedAccountHighlight","value":false},{"key":"ViewZeroAsEmpty","value":false},{"key":"l10n","value":"0"}]

3.7.3 has been released to Firefox and is awaiting approval from Chrome. It should fix the issues.


Feature request: Approval/denial notification DMs

Too much effort for not enough gain; we can use threads to notify if necessary.


Bump nokogiri from 1.11.4 to 1.13.3

Bumps nokogiri from 1.11.4 to 1.13.3.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: nokogiri
dependency-type: indirect
...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>

created my-slides branch

Added new changes


Units of measure code compiles, but throws FatalExecutionEngineError at runtime when compiled with Optimize=false

The following code compiles fine.
open System

[<Measure>]
type foo

let works (xs: float<'u> []) flag =
    let inner = let zero = LanguagePrimitives.FloatWithMeasure 0. in fun x -> if flag then zero else x
    Array.map inner xs

let fails (xs: float<'u> []) flag =
    let inner = let zero = 0.<_> in fun x -> if flag then zero else x
    Array.map inner xs

[<EntryPoint>]
let main _ =

    works [|1.<foo>|] true |> ignore

    fails [|1.<foo>|] true |> ignore

    0

However, when compiled and run with Optimize=false (note: the error does not occur with Optimize=true), the call to 'works' works fine, but the call to 'fails' (which differs only by using LanguagePrimitives.FloatWithMeasure 0. instead of 0.<_>) throws the following exception:
FatalExecutionEngineError occurred
Message: Managed Debugging Assistant 'FatalExecutionEngineError' has detected a problem in 'C:\dev\BugReport\bin\Release\BugReport.exe'.
Additional information: The runtime has encountered a fatal error. The address of the error was at 0x71a6a2b6, on thread 0x19748. The error code is 0xc0000005. This error may be a bug in the CLR or in the unsafe or non-verifiable portions of user code. Common sources of this bug include user marshaling errors for COM-interop or PInvoke, which may corrupt the stack.
``

I can repro on VS2013 F# 3.1 (Fsharp.Core, <IP_ADDRESS>) only when compiling Debug configuration.

I think that I can found simpler repro code:
open System

let ok () =
    let inner =
        let zero = 0.<_>
        zero
    inner

let ng () =
    let inner =
        let zero = 0.<_>
        fun x -> zero
    inner 0

[<EntryPoint>]
let main _ =

    ok() |> ignore

    ng() |> ignore

    0

In this code, the line fun x-> zero inside ng function throws FatalExecutionEngineError exception.

I think this is the same as http://visualfsharp.codeplex.com/workitem/61.  It has been fixed in F# 4.0, which will be shipping with VS 2015.  I can repro in VS 2013/F# 3.1 but it works ok (and the assembly passes PEVerify) with VS 2015/F# 4.0 CTP.
Is it possible for you to move to F# 4.0?

Johanns workaround in that original bug seems to work here too, simply inlining the function makes the app work:
let inline ng () =
    let inner =
        let zero = 0.<_>
        fun x -> zero
    inner 0

Thank you for the info, @latkin and @rojepp .
It works fine for me :+1:

Ok, thanks a lot all!


Switch CI to github actions

It's a pain how many clicks it takes to get any info out of azure pipelines whatsoever, so let's see how this compares.

Ugh, cargo is still garbage at dealing with features in workspaces :(

Coverage claims to be working, but I'm not sure how to get it to produce a report.

What about Windows and Mac?


No exit button

Question - why there is no exit button?
Overview of the problem
<! This is about the Spark Users module >no
<! This is about the Spark Camps module > yes
<! My browser is: >chrome
<! I am sure this issue is not a duplicate? >not sure
Description
<! Description of the bug, enhancement, or question >
Steps to Reproduce
<!
1.login to spark with regular user
2. on the upper menu , press התנדבות button
3. in the התנדבות screen , there is no exit button

Expected behavior
<!

What you expected to happen --> to have an exit button

@amotenko I think this bug "belongs" to us.
actually there is an exit button = the midburn logo on the upper left side, but i guess no one knows that :)
Opened an issue here: https://github.com/Midburn/Volunteers/issues/135

@galnitsan , hope that helps
thanks @may-ben-arie


nio 2 convergence

This PR updates to NIO 2's convergence tags.

@tanner0101 This currently doesn't send the request, but makes a successful connection.
* Connected to api.development.push.apple.com ([IPv4]<IP_ADDRESS>/<IP_ADDRESS>:443


PRO: Mailqueue

Does anybody know if and where is a sample of Premium Mailqueue feature?

Just Add Mail Bkg process and Process Runner in SiteInitialisation


数据集问题

您好，请问能公布测试数据集吗

Thank you for your interest in our work! We will release the dataset recently, and I think it will be around tomorrow. We are currently uploading them.
Also, we hope you can ask questions in English in the issue, which is one of the basic etiquette of GitHub :)

I have released the WeatherKITTI dataset!


Add t-SNE component

Changelog
tSNE dimred implemented and tested
Issue ticket number and link
Closes #737
Checklist before requesting a review

[x] I have performed a self-review of my code

[ ] Conforms to the Contributor's guide

Check the correct box. Does this PR contain:

[ ] Breaking changes
[x] New functionality
[ ] Major changes
[ ] Minor changes
[ ] Documentation
[ ] Bug fixes

[ ] Proposed changes are described in the CHANGELOG.md

[x] CI tests succeed!

All comments should be fixed, minimal CHANGELOG.md entry added.


Add JavaScript / TypeScript library

Is your feature request related to a problem? Please describe.

Support for React Native
Support for Blazor

Offline mode to use react-native-sqlite-2 on React Native and IndexedDb on web properties - implement as separate packages.

My expertise is more in Angular/Ionic. Would love support there.

We will not be supporting a TypeScript library at this time.  This is because (a) the REST API is available, and (b) I don't have enough time or the requisite knowledge to support the TypeScript library for offline capabilities.


ARROW-15673 [R] Error gracefully if DuckDB isn't installed

@github-actions crossbow submit test-r-ubuntu-21.04

@github-actions crossbow submit test-r-ubuntu-21.04

@github-actions crossbow submit test-r-ubuntu-21.04
This particular job didn't have the print output step, but I've added it and it should happen now.

@github-actions crossbow submit test-r-ubuntu-21.04
Oops, the path wasn't quite right

@jonkeane thanks for the ubuntu test without ducked. It looks like that test block is being run:
Start test: meaningful error message when duckdb is not installed
  test-duckdb.R:28:3 [success]
End test: meaningful error message when duckdb is not installed

  test-duckdb.R:34:1 [skip]

@github-actions crossbow submit test-r-ubuntu-21.04


just installed xsoar and can t execute scripts

DBot
May 28, 2024 3:15 PM
Scripts returned an errorHide reason
Command:
!HelloWorldScript
Hide reason
Reason
Error from Scripts is : Script failed to run: Docker code runner got container error: [Docker code script is in inconsistent state, expected pong but didn't got any response, exit error: Container exit with error. container name: [demistoserver_pyexec-fd38c677-95ad-45b2-8985-96f46baac26d-demistopython<IP_ADDRESS>255--57] error: [exit status 1] stderr: [/usr/local/bin/python: can't find 'main' module in '/tmp/pyrunner/_script_docker_python_loop.py'
] (2619) (2610)] (2611) (2603)

@yasser-bk52 Please open a CS ticket at https://support.paloaltonetworks.com


[Bug] Twins-Svt-Base model not support dynamic shape due to hard-coded Reshape node input shape

Describe the bug
Similar as #724, Twins-Svt-Base Pytorch model can not be exported as simplified ONNX model with dynamic shape via pytorch2onnx.py
The root cause is Reshape_11 node with hard-coded input shape [1,96,3136] in ONNX model as follow:

To Reproduce
You may follow following step to reproduce the error in github master with commit 2037260
conda create -n mmcls python=3.6
conda activate mmcls
conda install pytorch==1.5.1 torchvision==0.6.1 -c pytorch
pip install openmim protobuf onnxruntime onnx-simplifier
git clone https://github.com/open-mmlab/mmclassification.git
cd mmclassification
mim install -e .
python tools/train.py configs/twins/twins-svt-base_8xb128_in1k.py
python tools/deployment/pytorch2onnx.py configs/twins/twins-svt-base_8xb128_in1k.py \
--checkpoint work_dirs/twins-svt-base_8xb128_in1k/latest.pth \
--output-file twin-svt-base-p16.onnx  --dynamic-export --simplify

Post related information

The output of pip list | grep "mmcv\|mmcls\|^torch"

mmcls              0.21.0          /home/xsun/mmclassification
mmcv-full          1.4.6
torch              1.5.1
torchvision        0.6.0a0+35d732a

config file modified it or created a new one.
I just use dummy 200 imagenet images, and change max_epochs as 1 for training, you may find detailed info as follow:twins-svt-base-p16-train.log, twins-svt-base-p16-pytorch2onnx.log

Closed according to #724


Traffic Portal server checks missing management interface column

In traffic ops, there is a column in the server checks page called MGMT for the management interface.  This column appears to be missing in Traffic Portal.

This is because in TP, the server checks (cache checks) table is not being dynamically created based on the data it has available.
https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_portal/app/src/modules/private/cacheChecks/cacheChecks.tpl.html#L34
^^ Those columns are "hard-coded" for a lack of a better term. I wasn't aware they had to be dynamically created. Will need to rethink how this table is built.

+1 for a fix on this issue.


? couldn't convert the error to RequestError

When I try the basic example on the README, I get the following error:

error[E0277]: `?` couldn't convert the error to `RequestError`
  --> src\main.rs:45:58
   |
45 |                     chatgpt_call::ask_chatgpt(text).await?;
   |                                                          ^ the trait `std::convert::From<chatgpt::err::Error>` is not implemented for `RequestError`
   |
   = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
   = help: the following other types implement trait `std::convert::From<T>`:
             <RequestError as std::convert::From<ApiError>>
             <RequestError as std::convert::From<DownloadError>>
             <RequestError as std::convert::From<reqwest::error::Error>>
             <RequestError as std::convert::From<std::io::Error>>
             <RequestError as std::convert::From<teloxide_core::serde_multipart::error::Error>>
   = note: required for `std::result::Result<(), RequestError>` to implement `FromResidual<std::result::Result<Infallible, chatgpt::err::Error>>`

Do you know what's wrong?

What is your main method? It looks as if it's return type is Result<(), RequestError>. Could you provide me your code?

I fixed it by not using ?, but match with ok and err
I use two libraries which return responses, so i guess they conflicted


deconstructibility?

@scottx611x : what's the status of https://github.com/refinery-platform/django_docker_engine/compare/scottx611x/add_deconstrucibility?expand=1? Can the branch be deleted? If it's work that could be integrated, is the migration necessary? In my mind, nothing here would necessarily depend on the database, but I could be thinking about it wrong.

@mccalluc Lets delete that implementation and we can start fresh after lunchtime


Update MoltenVK to 1.1.10

No ash upgrade in this one, so only need a minor version bump.
Once this is in I can tag and upload the new prebuilt MoltenVK.

Realized this was a bad branch name as it clashes with a potential tag. redoing PR.


The index of the Icons is void

hi, when i enter to the link i can't see nothing, just a blank page

Can you show what's going on in console and network tab?

@Carlosted 404


Do you have plans to support R-FCN or Light-Head-RCNN?

Do you have plans to support R-FCN or Light-Head-RCNN?

No plan for now. However, pull requests are welcome !

@roytseng-tw why set 'RPN:CLS_ACTIVATION: softmax' in yml file is error ？
rpn_cls_prob = rpn_cls_prob[:, 1].view(B, C // 2, H, W)
RuntimeError: invalid argument 2: size '[1 x 15 x 50 x 50]' is invalid for input with 2500 elements at /pytorch/torch/lib/TH/THStorage.c:41

Hi, it has been fixed now.


Let the user modify the prompt

Add a command line option for overriding the default prompt.
Saving a default prompt in the settings would be out of scope.

@ellipsis-dev please implement


iOS 10 deprecation warnings on devices(withMediaType:) in Xcode 8 GM

I was trying compile a project in Xcode 8.0 GM (swift3 branch), and got new deprecation warnings.
Screen captures below

Don't have time to fix at the moment so thought I'd file an issue.

I just downloaded the Xcode8 GM, I'll update the library tomorrow. Thank you for the hint!

The problem is fixed now! 👍


New Documentation

Create New documentation outlines.

Looks good in general. My only comment would be that there seems to be some repetition among pages when talking about Key Features and Who should use AIRI

Key Features are repeated in the README and overview because some people my only see the readme of the repo and go straight to get started and we want to give a quick overview even for them what the repo is about but it s a reduced version in the README.
On who should use AIRI it is repeated in overview and in FAQ because I do imagine who should use that will be a question for people that do not read the docs and also one of the most common things we did discuss when onboarding people in the project. So having it in FAQ too made sense.


Make regex <{}> family more prominent

Problem or new feature
Some folks have missed the capability of the various regex interpolation bits https://docs.raku.org/language/regexes#Regex_interpolation

eg this SO https://stackoverflow.com/questions/64909029/is-it-possible-to-do-boolean-assertions-with-raku-regex
me especially '<@' missed for a while

Suggestions
If applicable, suggest something towards the solution.
Maybe a page on regex "power tools"?

Maybe you wanted to link something with "this SO"?

red face

There's a table that shows only four types of interpolation:
https://docs.raku.org/language/regexes#Regex_interpolation
It just has <{}>,  and doesn't show anything like <?{}>.
Maybe it should be expanded?  A second table added?

Don't have any particular preference here. Your call.

Hi - perhaps I can inject a couple of thoughts...(?)
It feels to me that Regex Interpolation is a bit difference|improvement over perl5.
The topic gets introduced near the top of this explanatory page with interpolation of named regexen, something like this:
"Japanese pottery rocks!" ~~ / <$regex> /;  # Interpolation of $regex into /.../
Then there are the items in the table you link - about 20 sections further down. So very few people get that far before zoning out (unless they know what they are looking for).
How about lifting the table up just below the named regex section?
Anyway - just a thought...
Finally, then there are items that I think should be supported - but are not there yet:
<@list-of-matches>   #matches any item in the list, right?
<%????> #is there an intent for hashes (maybe match any key in the hash)
Don't know if these are worth a mention...?

How about lifting the table up just below the named regex section

Moving the table up sounds good.

Finally, then there are items that I think should be supported - but are not there yet:
<@list-of-matches> #matches any item in the list, right?

Ah, thanks for explaining that it's unsupported.  You mentioned
it before and I wondered why I couldn't figure out how to use it.

<%????> #is there an intent for hashes (maybe match any key in the hash)

Were it up to me, I might say it should do hash lookups, and match
if the value evaluates to True but not if it evaluates to False.

Don't know if these are worth a mention...?

If there's a clear plan to include them, I'd mention them.

<%????> #is there an intent for hashes (maybe match any key in the hash)
Were it up to me, I might say it should do hash lookups, and match
if the value evaluates to True but not if it evaluates to False.
How about match on the key (since usually that's a Str) and have the Capture (eg. $0) give back the value... ;-)

I've posted a new SO here to see if anyone knows https://stackoverflow.com/questions/65018490/raku-regex-list-interpolation

I would say the first place to look for historical design thoughts about Raku is design.raku.org.
(NB. The "Design" documents at design.raku.org are called "specs" for good reason -- to emphasize their nature as ultimately speculative specification. Imo nothing related to any of these speculations belongs in the doc unless the "specified" features are already in the actual specification, aka roast.)

For regexes the relevant design doc is S05.

An in page search for "<@" and "<%" yielded zero matches. So then I tried "%" and "@". I didn't see any relevant design discussion when going thru the % matches but saw lots when trawling thru the first few @ matches. I share some of it in this comment.
NB. This comment may be wildly short of what's in the doc. I only went thru some of the @ search, and even that was enough that I saw relevant text which I just happened to notice -- it wasn't directly caught by the search. So, to be crystal clear, I did not look thru the whole document, nor even the whole of clearly relevant sections such as the section discussing "Extensible metasyntax <...>". If folk truly want to know what @Larry thought, which mostly means what Larry thought, they really should laboriously trawl thru that document. I've done some work to illustrate the catch that such a trawl may reveal but I stopped once I felt I had a sufficient catch to be useful and demonstrate there's almost certainly much more interesting stuff to be found.

https://design.raku.org/S05.html#line_1635: A leading @ matches like a bare array except that each element is treated as a subrule (string or Regex object) rather than as a literal. That is, a string is forced to be compiled as a subrule instead of being matched literally. (There is no difference for a Regex object.) This assertion is not automatically captured.

https://design.raku.org/S05.html#line_1644: The use of a hash as an assertion is reserved.

https://design.raku.org/S05.html#line_1876: A leading * indicates that the following pattern allows a partial match. It always succeeds after matching as many characters as possible. (It is not zero-width unless 0 characters match.) For instance, to match a number of abbreviations, you might write any of:

    s/ ^ G<*n|enesis>     $ /gen/  or
    s/ ^ Ex<*odus>        $ /ex/   or
    s/ ^ L<*v|eviticus>   $ /lev/  or
    ...

https://design.raku.org/S05.html#line_3970: Array aliasing ... @<from>=...

OK I read the section @raiph refs. Well, if the words Extensible Metasyntax did not cause newbies (and middlebies) to run away, I would suggest taking this as a logical sequence for a (completely) rewritten section in the regex docs (if it made the actual language | implementation). Or - probably better, keep the name of "Regex Interpolation" and, in addition to promoting its visibility, add a subsection with the other members of the zoo mentioned in 05.
Hmmm - just googled 'site:docs.raku.org <foo=bar>' -> got nothing! Sooo - on 2nd thoughts I think there should be a new doc page, distinct from, and interlinked to, https://docs.raku.org/language/regexes. This idea means that the current section which is quite long and Is proven and 'correct' and reflects the perl5 RE stuff can stay unmolested. The new page is titled "regex interpolation" and follows the line of 05 Extensible Metasyntax, reflecting and maybe extending/including the current table (?).
Obviously all this needs to be checked against what is implemented.
Also can mop up the footnote from https://docs.raku.org/syntax/regex, namely A list of predefined subrules is listed in S05-regex of design documents.

NB. While I know the design docs quite well, they're frozen, and there's no process or judgment calls to consider. In contrast the end user docs are evolving, I don't know them or the process well, and the following reflects my lack of knowledge of these things.

a logical sequence for ... section in the regex docs

Is there no such "logical sequence" of assertions (<...>) in existing doc, even if some/many entries are missing?
I do see merit to organizing a document the way Larry did, namely to have a section focused entirely on <...> assertions within regexes, and then enumerating the options one by one. Or perhaps better still, giving each its own page, but having another page that transcludes them all.
If such a section existed I'd suggest a preamble entry also be written discussing <...> in the context of regexes more generally, because it's also used in relation to regexes in forms that aren't assertions within regexes, but in a manner that's overall strangely consistent with them and with other forms of use in Raku.

(completely) rewritten

To quote from an email I wrote today in another context but also about the docs:

If you are willing to put a great deal of effort into helping evolve the doc by both patiently discussing your concerns AND also writing and/or rewriting doc in accord with a mandate to do so based on a rough consensus, where rough doesn't mean unfriendly to any of those involved, then I am ... with you, and may even be talked into helping a bit.

Otherwise, I think that by far the most important thing is that we support folk who both really care about improving the doc and who will keep working on it in a manner that helps sustain progress for both our doc and that of the individuals doing the work.

(if it made the actual language | implementation).

I think the criteria would be better generally limited to a subset of:

Made roast. A lot of stuff that's in Rakudo does not belong in the doc.

Considered desirable. Imo some of the stuff in roast is not.^1

Even something to consider passes those two hurdles, I still think any move to include it in the doc ought generally be discussed at suitable length (defaulting to a longer period) until there's a clear consensus on including it, before even working toward a draft PR.
Of course, there'll be exceptions, but imo something like the above ought be the norm.

keep the name of "Regex Interpolation"

I think "interpolation" is generally understood to mean inserting something in something else, i.e. "regex interpolation" would suggest inserting a non-regex thing into a regex. I'd say most of the <...> assertions are regex things.

just googled 'site:docs.raku.org <foo=bar>' -> got nothing!

I got 178 matches, without the quotes. Perhaps you mean with '<foo=bar>'?
But if your point is the general one of google searchability, well, Raku is a case study in being google unfriendly (or google being Raku unfriendly).

Obviously all this needs to be checked against what is implemented.

Imo, against roast.

Also can mop up the footnote from https://docs.raku.org/syntax/regex, namely A list of predefined subrules is listed in S05-regex of design documents.

Again, imo any such action ought be against roast.

^1 Consider, for example, the arguably crazy transliteration functionality.

Thank you @raiph for clarifying my opinions - NB to all that I am writing as a consumer of the docs and anything I mentioned should be construed as a loose suggestion at best, certainly NOT as advice / guidance / instructions. Kudos and a free hand to those who are doing the work, guided by the processes.
On a couple of specifics:

I'm glad to hear that we agree on the
I am not necessarily for "Regex Interpolation" as the generic name for the <...> things in regexes (but, for the reasons mentioned I am rather against "Extensible Metasyntax" as a title)
Searching on <foo=bar> is not a wise thing anyway (apologies for the red herring) - my intent was to try and locate where the docs do mention the <foo=bar> concept.... for the record, its here https://docs.raku.org/syntax/regex

To give the capture a different name from the regex, use the syntax <capture-name=named-regex>. If no capture is desired, a leading dot or ampersand will suppress it: <.named-regex> if it is a method declared in the same class or grammar, <&named-regex> for a regex declared in the same lexical context.
And 100% agree that my phrase "what is implemented" should be "what is in roast".


Question: do you plan to add support for 4G modems? (MEGH-3122)

Would be great to be able to connect devices through 4G modem with esp_modem

@bbinet ,  Since RainMaker is not really linked to the underlying transport layer, this may be possible, but there are no plans to work on it right now.


Centralize XPath calls and failure_messages

This is a refactor that centralizes all calls to XPath and reduces duplication between node actions, matchers, and finders. It also exposes more finder power to the end user. For example, the following was previously not possible without knowledge of the XPath library:
page.find(:fillable_field, 'First Name')

More than anything, though, I think centralizing XPath logic and failure messages will make it easier to introduce more descriptive and helpful error messages, which I hope to work on if this pull request is accepted.

It's been a while but I finally got around to working on this a bit. I added the ability to define filters on custom selectors, that way we can define stuff like href and options as filters, and we don't need to send any options to XPath anywhere. I've removed all of those options in the XPath library as well. This change allowed me to remove split_options entirely, which is awesome. There's still some refactoring to be done, as there is more stuff we can make into filters now, such as selected, but we can do that later.
Thank you so much for your hard work on this Adam, this is a hugely important and long overdue change!

Oh yeah, I merged it, in case that wasn't clear ;)

@jnicklas Excellent! I'd been procrastinating writing specs for all of this because I wasn't quite sure how to go about it. I'm glad to see you merged it in, and I like where you've gone with the filters.


[Prototype] Render upgrade warning after command result if any GraphQL responses contain deprecations

🛑 Do not merge. This PR is for exploration.
#gsd:33165
Issue: https://github.com/Shopify/script-service/issues/6535
Brief proposal
https://user-images.githubusercontent.com/1707217/225382855-b72ec8bc-65c2-4ecd-b671-cda1ee4a9ac3.mov
How to test your changes?
partners branch: prototype/deprecate-script-service-proxy
export SHOPIFY_SERVICE_ENV=spin; export SPIN_INSTANCE=deprecate

Without Function
rm -rf extensions && pnpm shopify app deploy --path ~/path/to/app

With Function
pnpm shopify app generate extension --path ~/path/to/app --type=payment_customization --template=rust --name demo

pnpm shopify app deploy --path ~/path/to/app

🤔  I wonder if the strategy is overkill. Why not just directly output a deprecation warning whenever we hit it? I kind of feel like it's not our problem to minimize the number of times the message gets printed; more annoyance is a good thing. And that just happens to come with the advantage of not maintaining global state, figuring out which warning to display, etc.
By the way, will the message even appear if the user kills dev?

BTW the implementation merged already: https://github.com/Shopify/cli/pull/1597
(I can make any necessary changes this week in a separate PR)
@stephszeto I'll close this Prototype PR and respond in the other PR, sorry for the confusion


Improve support to HMR

Fix issue #27 on comment
Feat: add auto-reload-webpack-plugin
Refactor: improve modularization on webpack configs
Fix: change entry name
Feat: add support to .mjs files

@sibelius I gonna start working on it 😉


📝 Create utility formatter function for dates and times

This will be used to format movie/show release dates and movie/show runtimes

[x] Long format December 12th, 2022
[x] Medium format Dec 12, 2022
[x] Short format 12-12-22

I think it would be nice to just leverage the normal JS Date object, rather than use something like Moment or Luxon. I think we will have so few date formats that it will not be worth the bloat of another library. Plus, the Date object is actually pretty good these days.

🧪 Be sure to create unit tests as well!

Closed by #185


[cocoon] Simplify tests by sharing common codes in a util_test file

Some examples: branch_stream function exist in multiple files, such as https://github.com/flutter/cocoon/blob/master/app_dart/test/request_handlers/refresh_cirrus_status_test.dart#L39
Also MockGitHub class (https://github.com/flutter/cocoon/blob/master/app_dart/test/request_handlers/refresh_cirrus_status_test.dart#L233), etc.

This is obsolete.


Keyboard shortcut for File > Exit

Searched Open and Closed issues, no Titles to indicate this has been discussed yet.
There is no keyboard combination/shortcut associated with the File > Exit menu (at least on Windows 10). It would be great if this could be done, or at least configurable.
Thanks

I'm not seeing it...
CTRL + Q on my machine by default.
CTRL + W to close a single file (same as chrome tab close)
if you try it with no files open it will close the program
ALT+F4 as universal program close works as well
I'm running Linux most of the time but it works the Windows pretty much the same....
:confused:

Assuming maybe you mean the command key? Unless you’ve remapped something.
But yeah, command q is my go-to on my Mac. I’ll have to check how alt f4
behaves tomorrow at work. I’m wondering if it’s graceful or not, which
vscode has some issues with.
Thanks for the idea.
If it is graceful then perhaps it can be added to the File > Exit text.
On Tue, Dec 17, 2019 at 2:41 PM Ivan<EMAIL_ADDRESS>wrote:

I'm not seeing it...
CTRL + Q on my machine by default.
CTRL + W to close a single file (same as chrome tab close)
if you try it with no files open it will close the program
ALT+F4 as universal program close works as well
I'm running Linux most of the time but it works the Windows pretty much
the same....
😕
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/87189?email_source=notifications&email_token=AAJ445AQWIKQVCQL6OIBITDQZETPPA5CNFSM4J357T3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHDW46I#issuecomment-566718073,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJ445GZFVCGS47JSVDANMTQZETPPANCNFSM4J357T3A
.

CTRL+F4 also works as a graceful "Close File" (tried on Windows).
You can also use ALT F X to call File Exit.

{
  "key": "<your key>",
  "command": "workbench.action.quit"
}

CTRL + F4 does not work as it prompts to saved Untitled and Unsaved files (rather than caching).
ALT + F + X did work though
@bpasero's  solution is even better though, I should have thought of this. Now it's binded like on my Mac (or as close as I can get) with ALT + Q.
Thanks for the help all, and sorry to have wasted your time @bpasero !

That is a good point about the caching!
On Wed, 18 Dec 2019 at 12:27, umdstu<EMAIL_ADDRESS>wrote:

CTRL + F4 does not work as it prompts to saved Untitled and Unsaved files
(rather than caching).
ALT + F + X did work though
@bpasero https://github.com/bpasero's solution is even better though, I
should have thought of this. Now it's binded like on my Mac (or as close as
I can get) with ALT + Q.
Thanks for the help all, and sorry to have wasted your time @bpasero
https://github.com/bpasero !
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/87189?email_source=notifications&email_token=ADXXJL4XEEGPH2TMYG27EXTQZIJJ7A5CNFSM4J357T3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHF6P3I#issuecomment-567011309,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADXXJL7QELW6SYMOMRBS3RTQZIJJ7ANCNFSM4J357T3A
.


unzip vulnerable to CVE-2015-7696 and CVE-2015-7697

"If a user or automated system were tricked into processing a specially crafted zip archive, an attacker could possibly execute arbitrary code."

https://bugzilla.redhat.com/attachment.cgi?id=1073339
https://bugzilla.redhat.com/attachment.cgi?id=1075942

Pushed to staging aff3a23d670909f4f7ff9fac0bb273c32f1190eb

Thanks! Cherry-picked to release-15.09 as 05f1980eb079ac2136281e8283bceeb93dbe510e.

Cherry-picked to release-14.12 as aafebd27ea4e77017ea77dccf5c59acdd3bc9717.


Purchase Invoice Payment Discount % Not Calculating through API

``When creating a Purchase Invoice through the API v2, if you specify a value for invoiceDate, the Payment Discount % on the resulting purchase header is 0 even if the payment terms for the associated vendor specify a discount should be available and it does not calculate a discount when paid.
Example request (using a sandbox CRONUS USA, Inc. company):
{
    "vendorInvoiceNumber": "Test1234",
    "number":"TEST1234",
    "invoiceDate": "2021-05-27",
    "vendorNumber": "30000",
    "purchaseInvoiceLines": [{
        "lineType": "Account",
        "lineObjectNumber": "60100",
        "quantity": 1,
        "unitCost": 50,
        "dimensionSetLines": [{
            "code": "DEPARTMENT",
            "valueCode": "ADM"
        }]
    }]
}

Response:
{
<EMAIL_ADDRESS>"http://dev-18-1:7048/BC/api/v2.0/$metadata#purchaseInvoices/$entity",
<EMAIL_ADDRESS>"W/\"JzQ0Oyt3WWhFM3dOdCtoc1BsczVFdSsrMnVodXRuQTRWT3BFeXFvZEhYU0VSSnM9MTswMDsn\"",
    "id": "8f5d798f-01bf-eb11-a9cb-eea95a85519f",
    "number": "TEST1234",
    "invoiceDate": "2021-05-27",
    "postingDate": "2021-05-27",
    "dueDate": "2021-06-27",
    "vendorInvoiceNumber": "TEST1234",
    "vendorId": "058273be-d5be-eb11-bb69-000d3a269b8c",
    "vendorNumber": "30000",
    "vendorName": "Graphic Design Institute",
    "payToName": "Graphic Design Institute",
    "payToContact": "Bryce Jasso",
    "payToVendorId": "058273be-d5be-eb11-bb69-000d3a269b8c",
    "payToVendorNumber": "30000",
    "shipToName": "CRONUS USA, Inc.",
    "shipToContact": "",
    "buyFromAddressLine1": "33 Hitech Drive",
    "buyFromAddressLine2": "",
    "buyFromCity": "Miami",
    "buyFromCountry": "US",
    "buyFromState": "FL",
    "buyFromPostCode": "37125",
    "shipToAddressLine1": "7122 South Ashford Street",
    "shipToAddressLine2": "Westminster",
    "shipToCity": "Atlanta",
    "shipToCountry": "US",
    "shipToState": "",
    "shipToPostCode": "31772",
    "payToAddressLine1": "33 Hitech Drive",
    "payToAddressLine2": "",
    "payToCity": "Miami",
    "payToCountry": "US",
    "payToState": "FL",
    "payToPostCode": "37125",
    "currencyId": "00000000-0000-0000-0000-000000000000",
    "currencyCode": "USD",
    "orderId": "00000000-0000-0000-0000-000000000000",
    "orderNumber": "",
    "pricesIncludeTax": false,
    "discountAmount": 0,
    "discountAppliedBeforeTax": true,
    "totalAmountExcludingTax": 50,
    "totalTaxAmount": 0,
    "totalAmountIncludingTax": 50,
    "status": "Draft",
    "lastModifiedDateTime": "2021-05-27T15:38:21.087Z",
    "purchaseInvoiceLines": [
        {
<EMAIL_ADDRESS>"W/\"JzQ0O2FJUmZZS2RNNnRmaGdwZ21CcGlFaVJKZVRBZGdDY09CMFFFcnJ2WW4yWHM9MTswMDsn\"",
            "id": "915d798f-01bf-eb11-a9cb-eea95a85519f",
            "documentId": "8f5d798f-01bf-eb11-a9cb-eea95a85519f",
            "sequence": 10000,
            "itemId": "00000000-0000-0000-0000-000000000000",
            "accountId": "e98173be-d5be-eb11-bb69-000d3a269b8c",
            "lineType": "Account",
            "lineObjectNumber": "60100",
            "description": "Rent Expense",
            "unitOfMeasureId": "00000000-0000-0000-0000-000000000000",
            "unitOfMeasureCode": "",
            "unitCost": 50,
            "quantity": 1,
            "discountAmount": 0,
            "discountPercent": 0,
            "discountAppliedBeforeTax": false,
            "amountExcludingTax": 0,
            "taxCode": "NONTAXABLE",
            "taxPercent": 0,
            "totalTaxAmount": 0,
            "amountIncludingTax": 0,
            "invoiceDiscountAllocation": 0,
            "netAmount": 50,
            "netTaxAmount": 0,
            "netAmountIncludingTax": 50,
            "expectedReceiptDate": "2021-05-27",
            "itemVariantId": "00000000-0000-0000-0000-000000000000",
            "locationId": "00000000-0000-0000-0000-000000000000",
            "dimensionSetLines": [
                {
<EMAIL_ADDRESS>"W/\"JzQ0O1ZIMVVYNFkvYWdiZVNXbWk0N0xwaGdJM29nQjdUY3QzQlFzbVRNdnJCd289MTswMDsn\"",
                    "id": "91466ac4-d5be-eb11-bb69-000d3a269b8c",
                    "code": "DEPARTMENT",
                    "parentId": "915d798f-01bf-eb11-a9cb-eea95a85519f",
                    "parentType": "Purchase_x0020_Invoice_x0020_Line",
                    "displayName": "Department",
                    "valueId": "c2cf62ca-d5be-eb11-bb69-000d3a269b8c",
                    "valueCode": "ADM",
                    "valueDisplayName": "Administration"
                }
            ]
        }
    ]
}

From what I can tell, this is an order of operations issue. It is setting the Document Date before the Buy-From Vendor No. (because it is higher in the API page). The Document Date (in the Purchase Header table) sets a boolean value called UpdateDocumentDate to true and then when the Payment Terms Code is defaulted from the Vendor, there is a check against that value that prevents the discount from being set.
if not UpdateDocumentDate then
    Validate("Payment Discount %", PaymentTerms."Discount %")

It looks like this same issue also affects the pre-payment discount, but I haven't tested that explicitly.

Thank you for reaching out. Your request could be reporting a product bug not related to the AL application extensibility. Please reach out to the relevant support channels:

For collaboration in preview or beta versions of AL Language in Visual Studio Code (aka ModernDev), use GitHub (https://github.com/microsoft/al).
For Microsoft partners, for versions already in general availability and supported, file requests through Microsoft Partnersource (https://mbs.microsoft.com/partnersource/).
For ISVs/VARs who have discovered a bug in a in preview or beta version, use MS Collaborate (https://docs.microsoft.com/en-us/collaborate/).
For Business Central customers who have issues or found bugs, please contact your Microsoft partner.
For the new features please submit a product suggestion on https://aka.ms/bcideas

I don't understand why this isn't related to the AL application extensibility. The issue is with this page https://github.com/microsoft/ALAppExtensions/blob/master/Apps/W1/APIV2/app/src/pages/APIV2PurchaseInvoices.Page.al, which is part of the ALAppExtensions repo.

If you file a bug it will be done under SLA. If you don't need a quick solution of your problem, we can accept it as an extensibility error without strong commitments about expected time of the fix.


core-2022.4.0b0 does not work with temperature sensors

All my device temperature and humidity sensors do not seem to work on the new version of home assistant core-2022.4.0b0
All other sensors seem to work for some weird reason.

Update, also the alarm settings cannot be changed.
Hopefully you develop a new version for the community soon, thanks in advance

See #716


Error in calculation for run_at_sunset with offset

Problem/Motivation

Where you use run_at_sunset with a negative offset (eg -900) the first time the trigger executes at the expected time, but it resets the trigger to two days hence.

Expected behavior

When the trigger executed at 15mins before sunset on 2/25 I expected to look in the appdaemon admin console and see the trigger set for 15mins before sunset on 2/26. Instead it was set for 2/27.

For run_at_sunset with no offset, the expected behavior is observed
Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Hi!
Thanks for opening up a report, however, this is not related to the add-on, but AppDaemon itself. Please report the issue with AppDaemon.
Thanks! 👍


Internal Server Error after deployed to HANA DB

dear experts, I tried many times but still have no clue why there is an internal server error issue as screenshot shows.

Once I click "Go" (sorry for Chinese) and the error will come.
The same will come if I click "Create".
I already granted myself the required roles.

I tried to ask ChatGPT and here is the reply for my logs:
This error message is similar to the previous one you posted. It indicates that there is an issue with the SQL query being executed. The database is unable to recognize the column name ALIAS_1.DRAFTADMINISTRATIVEDATA.INPROCESSBYUSER.
Here are some steps to troubleshoot this issue:

Check the SQL Query: Ensure that the SQL query is written correctly. Make sure that the column ALIAS_1.DRAFTADMINISTRATIVEDATA.INPROCESSBYUSER exists in the TravelService_Travel_drafts table. If the column doesn't exist, you will need to correct the SQL query.

Check the Table Structure: Make sure that the table TravelService_Travel_drafts has the column DRAFTADMINISTRATIVEDATA.INPROCESSBYUSER. If the column doesn't exist, you will need to add it to the table or modify your SQL query to remove references to it.

Check the Database Schema: Ensure that the database schema is up-to-date and matches the schema expected by your application. If the schema is out of date, you may need to update it.

Check the Application Code: If the SQL query is being generated by your application code, there may be a bug in the code that is causing the incorrect query to be generated. Check the code to make sure it is correctly generating the SQL query.

If you're still having trouble after trying these steps, you may need to seek help from a database administrator or a developer familiar with the database and application.

Anyone here?


Bugfix/set job status

Change Job.status when calling one of the state-changing functions.
Changes

job.py: Change Job.status when calling one of the state-changing functions.
job_teat.py: Test that Job.status changes.

Enhancements (optional)
Job.status now changes when calling one of the state-changing functions.

[X] Unit tests
[X] Documentation

Fixes #287

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
7 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.9%) to 93.478%

Files with Coverage Reduction
New Missed Lines
%

pyzeebe/grpc_internals/zeebe_message_adapter.py
1
93.33%

pyzeebe/grpc_internals/zeebe_process_adapter.py
2
93.88%

pyzeebe/grpc_internals/zeebe_job_adapter.py
4
92.16%

Totals

Change from base Build<PHONE_NUMBER>:
-0.9%

Covered Lines:
731

Relevant Lines:
782

💛  - Coveralls


running rebase.sh in container this time

This change is

@JackQuincy,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@acs-bot test this please


DASHBOARD_CGI_URL_TMPL added to GS308EP

https://github.com/ckarrie/ckw-ha-gs108e/issues/12#issuecomment-2227316135

This fix is necessary to make the integration working for the GS308EP model. Can you please merge?


src: disable automatic buildkit GC

We have reason to believe that automatic GC is affecting daemon startup times. In this patch we disable automatic GC and instead rely on manual pruning of the buildkit cache. Once the daemon is ready we spawn an async task to run prune on any objects older than 14 days. We are already manaing the ceph volume approaching its size limit ourselves in the VM Agent.
Patch also adds some alerting when inode usage is high on a mountpoint.

[!IMPORTANT]
Disable automatic buildkit GC, implement manual cache pruning, and add inode usage monitoring in setup_builder.ts.

Behavior:

Disable automatic GC in writeBuildkitdTomlFile() in setup_builder.ts and rely on manual pruning.
Add pruneBuildkitCache() in setup_builder.ts to prune cache older than 14 days.
Start cache pruning asynchronously in startAndConfigureBuildkitd() in setup_builder.ts.
Monitor inode usage in setupStickyDisk() in setup_builder.ts and report if usage exceeds 80%.

Functions:

Modify startAndConfigureBuildkitd() in setup_builder.ts to remove device parameter.
Add isWarning parameter to reportBuildPushActionFailure() in reporter.ts.

Misc:

Remove unused device parameter from startBuildkitd() and writeBuildkitdTomlFile() in setup_builder.ts.

This description was created by  for ffa213400fb047f65d516435c1d9057f91093206. It will automatically update as commits are pushed.

Are we still planning on merging this?

Are we still planning on merging this?

unclear whether it helped, so im waiting on merging it. I probably will though cause its one less variable.


sqlite: schema?

Doesn't seem to work:
~/Documents $ sqlite3 mail.db
SQLite version 3.24.0 2018-06-04 19:24:41
Enter ".help" for usage hints.
sqlite> .schema alias
CREATE TABLE IF NOT EXISTS "alias" (
  "domain_id" integer NOT NULL,
  "recepient" varchar(256) NOT NULL,
  "username" varchar(128) NOT NULL,
  "updated_at" timestamp NOT NULL DEFAULT(CURRENT_TIMESTAMP),
  "created_at" timestamp NOT NULL
);
sqlite>
~/Documents $ usql mail.db
Connected with driver sqlite3 (SQLite3 3.23.1)
Type "help" for help.

sq:mail.db=> .schema alias
sq:mail.db->

.schema is not part of the actual SQLite3 database support. You will need to use the SQL introspection commands that are supported by that database. In SQLite3, that's the sqlite_master table, and the PRAGMA statements:
$ usql sqlite3://test.db
Connected with driver sqlite3 (SQLite3 3.23.1)
Type "help" for help.

sq:test.db=> create table t1 (v1 string, v2 string);
CREATE TABLE
sq:test.db=> select * from sqlite_master where type='table';
  type  | name | tbl_name | rootpage |                  sql
+-------+------+----------+----------+----------------------------------------+
  table | t1   | t1       |        2 | CREATE TABLE t1 (v1 string, v2 string)
(1 rows)

sq:test.db=> pragma table_info('t1');
  cid | name |  type  | notnull | dflt_value | pk
+-----+------+--------+---------+------------+----+
    0 | v1   | string |       0 |            |  0
    1 | v2   | string |       0 |            |  0
(2 rows)

sq:test.db=> SELECT
sq:test.db->   "cid" AS field_ordinal,
sq:test.db->   "name" AS column_name,
sq:test.db->   "type" AS data_type,
sq:test.db->   "notnull" AS not_null,
sq:test.db->   "dfltvalue" AS default_value,
sq:test.db->   pk != 0 AS is_primary_key
sq:test.db-> FROM pragma_table_info('t1');
  field_ordinal | column_name | data_type | not_null | default_value | is_primary_key
+---------------+-------------+-----------+----------+---------------+----------------+
              0 | v1          | string    |        0 | dfltvalue     |              0
              1 | v2          | string    |        0 | dfltvalue     |              0
(2 rows)

.schema is actually a meta command in the SQLite3 REPL command (the client equivalent, and what usql does), that wraps these calls.
For what it's worth, I wish all the databases supported SQLite3's PRAGMA's, as they are much easier to work with and are more intuitive (I think) than the various databases' meta tables. You can read about PRAGMA here: https://www.sqlite.org/pragma.html

Hey; I didn't know that. Thanks for teaching me!


Add getInputBox function to ICartesiDApp

📚 Context
There should be an entry point for outsiders to know which input box is the DApp listening to. This may be particularly useful for consensuses.
✔ Solution
Add a getInputBox function that returns the address of the input box where inputs to the DApp should be added to.
📈 Subtasks

[ ] Add function to ICartesiDApp and CartesiDApp
[ ] Add parameter to CartesiDApp constructor
[ ] Add parameter to functions and events from ICartesiDAppFactory and CartesiDApp
[ ] Add unit tests

FYI @tuler


add version number

hi, recently we want to your lib on https://cdnjs.com, i think maybe this lib only has one version, can we regards it as v1.0.0 on cdnjs? or if you have free time, we hope you can add git tag for this version, just in case if there will be a later version, our git auto-update config can add it automatically.
thank you very much!
https://github.com/cdnjs/cdnjs/issues/7125

@rafibomb can we tag the current release as v1.0.0 here: https://github.com/zurb/twentytwenty/releases
Thanks!


update sigstore-conformance tests

add bundle specific verification options

nvm, this needs the updated verifier that rebuilds the certs.


[HOLD for payment 2023-06-13] [$1000] Console error on click of the paypal payment method where Make default payment method option isn’t available(Error: Invalid prop style supplied to Button)

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Goto Settings -> Payments
Click on paypal method
Observe the console error in the devtools

Expected Result:
Console error should not be occurred
Actual Result:
Console error occurs
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: needs reproduction
Reproducible in staging?:  needs reproduction
Reproducible in production?:  needs reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/f8b27f61-c0d8-4b43-a31d-3927d582a8f2
Expensify/Expensify Issue URL:
Issue reported by: @Pujan92
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1684427630067449
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~011825e5129fec9a46
Upwork Job ID:<PHONE_NUMBER>176728064
Last Price Increase: 2023-05-31

Proposal by @Pujan92
Proposal
Please re-state the problem that we are trying to solve in this issue.
Console error on click of the paypal payment method where Make default payment method option isn’t available
What is the root cause of that problem?
For the button style we are passing the empty array here when default button option isn’t available for it, whereas in the button we are expecting style prop to be PropTypes.oneOfType([PropTypes.arrayOf(PropTypes.object), PropTypes.object])
https://github.com/Expensify/App/blob/cb6ba23ea1e99a3b332983568ee8e9aa0c2a09dd/src/pages/settings/Payments/PaymentsPage/BasePaymentsPage.js#L477
https://github.com/Expensify/App/blob/cb6ba23ea1e99a3b332983568ee8e9aa0c2a09dd/src/components/Button/index.js#L76
What changes do you think we should make in order to solve the problem?
We need to pass an empty object either in the array or separately to fulfill the required prop types.
style={[shouldShowMakeDefaultButton ? styles.mt4 : {}]}

OR
style={shouldShowMakeDefaultButton ? styles.mt4 : {}}

Not sure what's going on here and it's DEV so I'm going to go ahead and open this one up.

Hello,
Based on the error message, it looks like there is an issue with how the style property is being used in the Button component. It is possible that the style property is being supplied an incorrect value type, or it has not been defined.
To fix this error, I can take the following steps:

I will check the Button component's code implementation to ensure that the style property is defined as an object type. The style property value must be an object containing CSS style properties and values.
I will check the usage of Button component is passing an object as the value of the style property. And I will ensure that the object supplied contains valid CSS style properties and values.
For example:

<Button
  style={{ backgroundColor: 'blue', color: 'white', padding: '10px' }}
  onClick={handleClick}
>
  Click Me
</Button>

In the example above, the style property is being supplied with an object containing valid CSS style properties to apply the corresponding styling to the button.
3. I will check the React documentation on PropTypes and ensure that the correct type is defined in the Button component's prototype.

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~0125148e869fb3679c

Hello,
Based on the error message, it looks like there is an issue with how the style property is being used in the Button component. It is possible that the style property is being supplied an incorrect value type, or it has not been defined.
To fix this error, I can take the following steps:
I will check the Button component's code implementation to ensure that the style property is defined as an object type. The style property value must be an object containing CSS style properties and values.
I will check the usage of Button component is passing an object as the value of the style property. And I will ensure that the object supplied contains valid CSS style properties and values.
For example:
<Button
style={{ backgroundColor: 'blue', color: 'white', padding: '10px' }}
onClick={handleClick}

Click Me

In the example above, the style property is being supplied with an object containing valid CSS style properties to apply the corresponding styling to the button.
3. I will check the React documentation on PropTypes and ensure that the correct type is defined in the Button component's prototype.

Yep, agreed. @Pujan92's proposal looks good! 🚀

@Pujan92, i believe you need to comment in this issue before I can assign you to it 🙇

Ok, Done. I will raise a PR once it gets assigned to me. Thanks!

@mollfpr @NikkiWines PR is ready for review!

@mollfpr we still have plenty of time, though ahead of the regression ending, would appreciate you checking off the items above. Thank you!

@JmillsExpensify yup, I will finish it today. Thanks for the reminder!

Sorry for the delay @JmillsExpensify 🙏

[@mollfpr] The PR that introduced the bug has been identified. Link to the PR:

https://github.com/Expensify/App/pull/13648

[@mollfpr] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:

https://github.com/Expensify/App/pull/13648/files#r1226974514

[@mollfpr] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:

Soon we will migrate to TS, which warns in the editor. Also, it should be caught while reviewing the PR.

[@mollfpr] Determine if we should create a regression test for this bug.

Yes!

[@mollfpr] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

Goto Settings -> Payments
Click on the Paypal method
Verify there isn't any console error
👍 or 👎

Bump @JmillsExpensify :)

Thanks guys! Sorry for the delay. Jumping in now.

Summarizing payments, this is what I'm seeing:

Issue reporter: @Pujan92 $250
Contributor: @Pujan92 $1,500
Contributor+: @mollfpr $1,500

I've invited you both to the Upwork job. Bonuses will be paid out when payment is issue, with the offer now including the base.

Thanks @JmillsExpensify , Accepted!

Also, I disagree that we should add a regression test for console errors. I think this one is out of scope.

@Pujan92 You're all set! I added the bonus on final payment.

Alright, everyone has been paid out at this point and I don't think a regression test is in scope. Closing this issue out.


Problem (+ solution) when signing electron app using electron-sudo

I've had problems when signing my electron app for distribution in macOS. App signing and distribution is still a new world to me, so I will try my best to explain what was happening and how I fixed it.
I was using electron-builder to build my app for macOS. electron-builder needs to pack the app as an .asar file, files inside the .asar package are not a problem. The thing is it needs to smartUnpack folders in the project that have binaries in them in order for them to work. That means, getting those files outside the .asar package and placing them in other folder. node_modules/electron-sudo happen to be a folder that needs to be unpacked because it contains binaries.
Now, electron-builder goes ahead and tries to codesign everything that's outside the .asar file, and encounters with node_modules/electron-sudo/dist/bin/applet.app/Contents/MacOS/applet and node_modules/electron-sudo/dist/src/bin/applet.app/Contents/MacOS/applet and tries to codesign them, and throws the following error: myApp.app/Contents/Resources/app.asar.unpacked/node_modules/electron-sudo/dist/bin/applet.app/Contents/MacOS/applet: unsealed contents present in the bundle root.
After a little bit of research, I found that codesign does not like at all any files in the same folder level as the Contents folder. Aaaand that's where LICENSE lives. Tried to place LICENSE inside Contents, got the following error: myApp.app/Contents/Resources/app.asar.unpacked/node_modules/electron-sudo/dist/bin/applet.app/Contents/MacOS/applet: code object is not signed at all.
And the only thing that worked was removing both LICENSE files, after that electron-builder and codesign worked as expected.

TL;DR: the LICENSE files under dist/bin/applet.app and dist/src/bin/applet.app cause errors when trying to sign an app that uses electron-sudo as a dependency, please consider removing both files.

@rameerez in version 5.0 LICENSE will be removed.

Same error here. Is there any plan to have a minor bump? Unable to build my app. Thanks!

@pronebird workaround: npm install, then manually delete both files node_modules/electron-sudo/dist/bin/applet.app/README and node_modules/electron-sudo/dist/src/bin/applet.app/README, then try to build your app again.
You'll need to do this again every time npm rewrites node_modules/electron-sudo, but hey, at least you can build your app.

@rameerez Just an FYI for googlers the files you need to delete are present are LICENSE rather than README

I have same issue. Inevitably, I use other package.  sudo-prompt.

For googlers landing here, you can specify an 'afterPack' hook that cleans up these files in your package.json:
build: {
  "afterPack": "./build_hooks/afterPack.js",
}

And do something along the lines of:
const { promises: fs } = require( 'fs' )
const log = ( ...messages ) => console.log( ...messages )

exports.default = async function( context ) {

    const troublesome_files = [
        `dist/mac-arm64/battery.app/Contents/Resources/app.asar.unpacked/node_modules/electron-sudo/LICENSE`,
        `dist/mac-arm64/battery.app/Contents/Resources/app.asar.unpacked/node_modules/electron-sudo/dist/bin/applet.app/LICENSE`,
        `dist/mac-arm64/battery.app/Contents/Resources/app.asar.unpacked/node_modules/electron-sudo/src/bin/applet.app/LICENSE`
    ]

    try {
        log( '\n\n🪝 afterPack hook triggered: ' )
        await Promise.all( troublesome_files.map( file => {
            log( `Deleting ${ file }` )
            return fs.rm( file )
        } ) )
        log( 'Cleaned up LICENSE files\n\n' )
        return context
    } catch( e ) {
        log( `afterPack issue: `, e )
    }

}

You'll have to edit the file paths depending on how you're building and whether you are using electron-sudo or sudo-prompt.


go go 1.5

It looks like it went okay
On Thu, Aug 27, 2015 at 21:18 Brian Kassouf<EMAIL_ADDRESS>wrote:

Merged #57 https://github.com/Imgur/incus/pull/57.
—
Reply to this email directly or view it on GitHub
https://github.com/Imgur/incus/pull/57#event-394703833.


Run the managed unit tests on push/pr

Unfortunately, this failed. Gotta figure out how to fix this.

error MSB4019: The imported project "C:\Program Files\dotnet\sdk\8.0.400\Microsoft\WindowsXaml\v17.0\Microsoft.Windows.UI.Xaml.CSharp.targets" was not found.

Is this installed via some sort of dotnet workload?

Ugh, ok, so we can't use dotnet test for these because the Microsoft.Windows.UI.Xaml.CSharp.targets file exists in C:\Program Files\Microsoft Visual Studio\Enterprise\MSBuild\Microsoft\WindowsXaml\v17.0\Microsoft.Windows.UI.Xaml.CSharp.targets
Even if we try to run the tests manually by invoking vstest.console.exe on out\BehaviorsSDKManaged\bin\x86\Release\ManagedUnitTests.exe, it doesn't seem to do anything.
If I run them in VS, then it pops up a GUI app which might not be doable in a GitHub pipeline because it is probably headless.


Explore comment and formatting preserving source code generator

Explore if it's possible to preserve most comments and the source formatting in Generator. See recast.

A few additional notes:
One concept I found useful from Roslyn (c# and VB compiler) is the idea of leading and trailing trivia. Every token has leading and trailing trivia and the rules for what's leading and trailing are. The following is from biomejs' documentation

Every trivia up to the token/keyword (including line breaks) will be the leading trivia;
Everything until the next linebreak (but not including it) will be the trailing trivia;

const a = "foo"; // comment 1
// comment 2
const b = "bar";

The parts in [] is the trivia where the first [] is the leading trivia and the second [] is the trailing trivia.
0<EMAIL_ADDRESS>    ...
      1<EMAIL_ADDRESS>";" [] [Whitespace(" "), Comments("// comment 1")]
    1<EMAIL_ADDRESS>        ...
        1<EMAIL_ADDRESS>"const" [Newline("\n"), Comments("// comment 2"), Newline("\n")] [Whitespace(" ")]
  3<EMAIL_ADDRESS>"" [] []

What's nice about this approach is that if you move the const keyword (or the variable statement) is that it also moves the relevant comments. The same is true for when you move the ; (or as declaration).
This paper might also be worth reading (it also references a few other papers that might be worth checking out)


documentation update

Codecov Report

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

@@         Coverage Diff          @@
##           master   #12   +/-   ##
====================================
  Coverage      75%   75%
====================================
  Files           1     1
  Lines          48    48
====================================
  Hits           36    36
  Misses         12    12

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 c03f2fe...e621dc7. Read the comment docs.


FlipTableConverters.fromResultSet() is not public

flip-tables/src/main/java/com/jakewharton/fliptables/FlipTableConverters.java : line 100
The method signature doesn't include keyword "public", so calling it from another class raises a warning.
I'm using this in a Groovy-based test so it doesn't really matter, but it would make it harder to use in something more serious.
Happy to submit a pull request if it's useful, but first wanted to check whether it's intentional or I'm otherwise missing something.
Thanks for the tool! Otherwise works great and is totally saving me time in producing debug output.

Yep this looks like a simple oversight on my part. I'd happily take a PR for it and can make a release shortly thereafter.

Submitted a pull request. Wanted to contribute something to this AWESOME project.


Xtream codes integration

Is your feature request related to a problem? Please describe.
My IPTV provider is moving to Xtream Codes only as the only method to access channels. M3u playlists will no longer be supported.
Describe the solution you'd like
Add the ability to login using the Xtream Codes API. Once logged in via Xtream Codes there’s a similar folder structure containing streams.
Describe alternatives you've considered
Using an online generator like m3u4u, however the IPTV provider is proposing blocking access via this method also.
Additional context
Add any other context or screenshots about the feature request here.

Personally, I'm not interested in an XC API.
Since there are other streaming servers including their own APIs, M3U is the lowest common denominator. If your provider no longer wants to support this, it is more a "political" issue.
Players like VLC etc. will then also no longer work.

Thanks for the reply. I think login via XC is going to become more popular as providers block access to m3u playlists for security reasons.
Thanks
J

Use This.....https://github.com/pierre-emmanuelJ/iptv-proxy

https://github.com/tellytv/go.xtream-codes
Could this be useful in implementing this feature?

You can try our livestream companion which has full support to Xtream Codes and M3u:
https://github.com/muxpie/livestream-companion


Invalid path for multi-root workspace

Issue Type: Bug

Output panel contains a valid path:
/Users/aleksi/Code/My/vscode-bug-multiroot/project-2/project2.go

When ⌘+clicked, it tries to use an invalid path:
file:///Users/aleksi/Code/My/vscode-bug-multiroot/project/-2/project2.go

Note the extra / before -2. That seems to happen only with multi-root workspace when one root path is a prefix of another root path.
Example repo: https://github.com/AlekSi/vscode-bug-multiroot
Steps to reproduce:

git clone https://github.com/AlekSi/vscode-bug-multiroot.git
code vscode-bug-multiroot/bug.code-workspace
Install Go plugin (but that issue is not specific for it).
Open project2_test.go, click CodeLens' "run test".
go test runs go vet and notices a bug in project2.go. ⌘+click on the file path in the Output panel.

VS Code version: Code 1.30.2 (61122f88f0bf01e2ac16bdb9e1bc4571755f5bd8, 2019-01-07T22:48:31.260Z)
OS version: Darwin x64 18.2.0

This issue affects a group of people, has more than 10 :+1:, has steps to reproduce, and self-contained example. The fix is likely to be small and self-contained too. According to https://aka.ms/vscode-out-of-scope it should be reopened. @jrieken @isidorn @bpasero please reopen.

Sure, we can reopen.

I re-checked it, and it works now


New definitions

HI All,
Here are some definitions for some existing terms.
Please give me feedback. I plan to committ these
definitions during the first week of April.
Thanks,
Rama
GOID:5769
term:early endosome
definition:Small irregularly shaped intracellular
vesicles where the endocytosed molecules are initially
delivered
definition_Reference: Molecular Biology of the Cell,
Bruce, Alberts
GOID:5770
term:late endosome
definition:Intracellular vesicles where the hydrolytic
digestion of the endocytosed molecules by the lysosomal
hydrolases begins.
definition_Reference: Molecular Biology of the Cell,
Bruce /alberts.
GOID:16631
term:enoyl-[acyl-carrier protein] reductase activity
definition:Catalysis of the reaction:
Acyl-[acyl-carrier protein] + NAD(+) =
trans-2,3-dehydroacyl-[acyl-CAcarrier protein] + NADH.
definition_reference: EC:<IP_ADDRESS>
Note: GOIDs 4318 and 16631 are the same and should be
merged.
GOID:8131
term:amine oxidase activity
definition:Catalysis of the reaction: RCH2NH2 + H2O +
O2 = RCHO + NH3 + H2O2
definition_reference: EC-<IP_ADDRESS>, 14.13.6
Note: Amine Oxidase is used to refer to <IP_ADDRESS> and
<IP_ADDRESS>. I recommend removing amine oxidase as a parent
term and making 8131 a synonym of both 4041 and 8122
GOID:15664
term:nicotinamide mononucleotide permease activity
definition: catalysis of the transport of nicotinic
acid across biological membranes
definition reference: PMID:10869563
Reported by: rbalakri
Original Ticket: "geneontology/ontology-requests/1609":https://sourceforge.net/p/geneontology/ontology-requests/1609

thanks www.movied.org


Support allocator inside of runtime

rendered
Related PR https://github.com/paritytech/polkadot-sdk/pull/1658
BTW, I'm not a member of polkadot fellows, does this have any impact on RFC implementation?

I mentioned it in there already, it's basically orthogonal

I don't see how https://github.com/polkadot-fellows/RFCs/pull/4 is orthogonal. To me, it's one or the other, as they render the other PR useless. The only exception is we could do #61 plus some parts of #4 (in other words not all of #4).
From a pure logical point of view, I think that https://github.com/polkadot-fellows/RFCs/pull/4 is fundamentally a better idea because it doesn't complexify the flow of execution.
With what this PR proposes, the host will call a runtime function, then the runtime can call a host function, which can call a runtime function (alloc, realloc, or dealloc).
If alloc, realloc or dealloc lock a mutex that was already locked before the allocation/free, then you've got a deadlock.
If alloc, realloc or dealloc call a host function, then you might have an infinite loop.
You can counter-argue by saying that this is just a matter of being careful and that it won't happen in practice, but I think that it's still a point in favor of https://github.com/polkadot-fellows/RFCs/pull/4.
When it comes to performances, I have no idea which one of the two is better and I don't think it's possible to determine that without implementing them and comparing.

@tomaka

From a pure logical point of view, I think that #4 is fundamentally a better idea because it doesn't complexify the flow of execution.

I do not think so, it will never complexify the flow of execution, see the draft PR, it's very clear.

If alloc, realloc or dealloc lock a mutex that was already locked before the allocation/free, then you've got a deadlock.
Why there is a lock ? it's single thread. Even if there is a lock in wasm, this is a runtime logic bug, which will be encountered in runtime_apis, too. You can't prevent an exported function having a bug or falling into an infinite loop.

If alloc, realloc or dealloc call a host function, then you might have a stack overflow.

runtime_apis also wil encounter this problem.

You can counter-argue by saying that this is just a matter of being careful and that it won't happen in practice, but I think that it's still a point in favor of https://github.com/polkadot-fellows/RFCs/pull/4.

This is a matter of code practice, why don't you worry about runtime_api encountering such problems?

What I am most concerned about with this PR is the versatility of the runtime, which helps the substrate runtime expand. Haven't you discovered that by combining the runtime_api.reimplmentation and allow missing host functions configurations and removing the imported allocator, the substrate runtime can be a pure wasm (actually no need to call any host function).
Whether it is integrating into other ecosystems or integrating other ecosystems into substrate, it is convenient.

Around this and #4 ..
We'd ideally have the approximate goal that host calls should almost never pass owned data, only borrowed data like &'s [u8] and &'a mut [u8] buffers.
In principle, this requires all current host calls be replaced, not unlike #4 does, but realistically some hostcalls would still pass owned data if they really needed the owned data.  We'd often permit -> Vec<u8> instead of passing an allocator callback for example, but we'd replace some by -> &'static [u8] host calls, and avoid -> Vec<u8> host calls in other ways.
We'd gradually gain more from this RFC as we replaced more host calls by borrowing flavors.  Rust handles borrowed data nicest of course.  Yet, other langauges could avoid inefficencies like call wrappers that take owned being the runtime allocator, copy it to owned data behind the system allocator, make the host call, and then allocate & copy in reverse.  Instead, they'd make the hostcall directly on borrows of data managed by the runtime, either owned or borrowed.
In other words, I'd think this and changes like #4 should benefit each other.

@bkchr Hi, want to know your thinking

This allows the verification block to use pure wasm (just replace the host functions with wasm functions), which can extend the runtime verification to a lot of scenarios
@tomaka @bkchr

Just my two cents: I'm in favor of https://github.com/polkadot-fellows/RFCs/pull/4 over this RFC, and I also strongly dislike the the fact that this would require us to call back into the runtime from a host function, which is a can of worms that once opened exposes us to fun things like the possibility of a malicious program of overflowing the host's stack, etc. I think that if possible we should keep the model of "host calls don't call back into the runtime".
As far as performance is concerned, https://github.com/polkadot-fellows/RFCs/pull/4 should be as fast or faster when optimally implemented (that is, if we guarantee that every host call will only have to cross the guest-host boundary twice at worst, and only once at the best).

and all current runtime apis rely on the method you say you don't like.

Huh? But they don't call back into the guest? So can you clarify what you mean here?

Huh? But they don't call back into the guest? So can you clarify what you mean here?

I means sp_api::decl_runtime_apis!.  Alloc/dealloc is not different with them except the call conversion.

Huh? But they don't call back into the guest? So can you clarify what you mean here?

I mean the api defined by sp_api::decl_runtime_apis!. Alloc/dealloc is not different with them except the call conversion.

Huh? But they don't call back into the guest? So can you clarify what you mean here?

I means sp_api::decl_runtime_apis!. Alloc/dealloc is not different with them except the call conversion.

Sorry, I still don't know what you mean. (:
The way the host calls currently work is that they don't call back into the runtime. The runtime calls the host function, the host function does its thing, and the control returns back to the host. Yes, the host does call into the runtime initially so technically you have a chain of "host -> guest -> host", but that only happens once.
So for the sake of argument let's assume we implement this RFC. It will allow us to call the guest's allocator from the host. What is the use case here?

Allocate the initial input payload to the runtime API. But if we implement #4 then this is unnecessary.
Allocate the dynamically sized return values of the host calls. Ideally we do not want to do this anyway (because it will allow a recursive "host -> guest -> host -> guest -> host -> guest -> ..." call loop) and if we implement #4 then this is unnecessary (because no such host functions will exist anymore).

So I agree with @tomaka and I don't see how this RFC is orthogonal to #4; if we implement #4 then it pretty much makes this RFC pointless, unless you actually have an use case that could make use of this?

Supports a pure wasm environment to verify blocks. Currently, if you want pure wasm to verify blocks, you need to replace all host functions, but alloc itself cannot be replaced.
This reduces the requirements on the host environment and requires only a wasm executor, so the verification logic can be executed on many chains.

Supports a pure wasm environment to verify blocks. Currently, if you want pure wasm to verify blocks, you need to replace all host functions, but alloc itself cannot be replaced. This reduces the requirements on the host environment and requires only a wasm executor, so the verification logic can be executed on many chains.

But this is also true after implementing #4 as far as I can see, because the host-side allocator will not be used at all anymore.

This doesn't seem to hold true in the case of legacy host functions.
But rfc #4 is indeed a good improvement

This doesn't seem to hold true in the case of legacy host functions.

...which is exactly the same as this RFC, no? (:
Not that it matters, because the legacy host functions won't be used anymore for new blocks and will only be kept for sync compatibility.

Maybe you're right.
ext_input_size_version_1/ext_input_read_version_1 are more like a smart contract style design.
But my idea is to set up stubs for all import functions, but not actually call them.
I'm a bit convinced by you

Closed since RFC #4 will be implmented.


Fix Attrs Subclassing

#34 fixed directly subclassing Registry when using an attrs decorator. This PR fixes subclassing the resulting class when using an attrs decorator.

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (2e2303f) 100.00% compared to head (a9a7ba9) 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##              main       #35   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          265       284   +19
  Branches        53        60    +7
=========================================
+ Hits           265       284   +19

Flag
Coverage Δ

unittests
100.00% <100.00%> (ø)

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

Files Changed
Coverage Δ

autoregistry/_registry.py
100.00% <100.00%> (ø)

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


Preview Events

Hi!
I would like to know if there's any way to preview events like fullcalendar.
Thanks.

Other than by using the tooltip, there isn't a way to do this. Your best bet is to use some custom CSS and override this template. It's something I might add one day as an option.

Thanks @mattlewis92 I'll try it.

I had a look into this as it's not easy to add due to event spanning multiple days. I hope you managed to find a suitable solution from what I suggested before :)


feat: sup-closed sets are closed under finite suprema

From GrowthInGroups

*consistent in a way you don't see 😉
bors merge

*consistent in a way you don't see 😉

Note that there are exactly zero other lemmas in mathlib that take a supremum over a general conditionally complete lattice and have the name iSup. And there are many other lemmas in mathlib that take a supremum over a general conditionally complete lattice that also work for complete lattices, and are still called ciSup. And, as pointed out on the zulip thread, the disambiguation argument doesn't hold if there are more lemmas in mathlib.
So I would like to see some more factual arguments that this is consistent, as currently this is objectively increasing inconsistency in mathlib 😉

Note that there are exactly zero other lemmas in mathlib that take a supremum over a general conditionally complete lattice and have the name iSup.

There are at least three or four according to https://loogle.lean-lang.org/?q=iSup%2C+ConditionallyCompleteLattice


Rc fixes

Description
babel-pollyfil/async await was causing issues when building a binary saying window is not defined when launching. I think we just need to remove electron-webpack to have full control over it. Not sure why it was breaking but didn't spend much time debugging.

@skhameneh Merging this to release an RC. Let me know if there are any issues.


Generating documentation

I have been using Docile and Lexicon to document the functionality of the Diversity package for a while, and I've noticed that I ought to move over to the Base documentation. However, I can't work out how to do two things that I could previously do, and I'm wondering if you can help:

Document a module from another file, which I think I used to do using "!!include(../doc/ecology.md)". I realise that README.md seems to be automatically used for the main module documentation, but submodules don't seem to have that option as far as I know?
Have a summary for a function (maybe the idea doesn't exist any longer?), that I used to do using "!!summary(...)"
Automatically generate online documentation from the inline function documentation. Previously I generated github.io docs, but now people generally seem to use the much better readthedocs.

I don't mind if I use the new Base documentation or Docile, but at the moment I can't do these things with either, and I'd like to. I have an updated version of my package that works under 0.4 and 0.5-pre, but I'd like to get the documentation corrected before I release it...

!!include(../doc/ecology.md) can be replaced with
"$(readall("../doc/ecology.md"))"
func(x, y) = ...

Slightly more verbose, but should be a bit clearer to readers.
Submodule's won't automatically pick up documentation from anywhere. You'll need to add them manually above each module, ie.
"submodule docs..."
module Submodule
# ...
end

The eventual plan for docstring summaries is to extract those automatically. !!summary should just be replaced by a single line/sentence.
Online doc generation is in a bit of a limbo at the moment until I've got enough spare time to work on finishing off Docile's rewrite branch, https://github.com/MichaelHatherly/Docile.jl/tree/rewrite. It's pretty usable at the moment though and won't be changing significantly before being merged into master. Feel free to have a look at using that to generate docs, particularly the doc/ subdirectory and the template syntax, @{...}, used to splice inline docs into external files. Docile does not need to be imported into your module for any of this to work, so won't need to be added to the REQUIRE file and is just a "dev" dependency now.
Documenting functions prior to definition, ie
"..."
:func

function func(x, y)
    # ...
end

should be replaced with
"..."
function func end

# ...

or
"..."
function func(x, y)
    # ...
end

depending on whether you want to document the Function or the Method.
Hope that helps a bit, happy to give you a hand transferring docs if you run into any trouble. If anything isn't clear just given me a shout.

Thanks, that's helpful. If I give an absolute path - i.e.:
"$(readall("/Users/richardr/.julia/v0.5/Diversity/doc/ecology.md"))"
then that works, but it doesn't work as a relative path... is that right? If so, it's not as useful as it use to be, because I can't reference anything within the package, can I?

Ah, yeah, forgot about the abs path problem. If you've got a quite a few external docs then defining some nicer syntax would be useful, perhaps a @file_str macro such as
macro file_str(path)
    :(readall(joinpath(dirname(@__FILE__), $(esc(path)))))
end

that you can then use like so
module M

"$(file"../doc/func.md")"
func(x, y) = ...

end

or something like that. Probably worth adding to the rewrite branch at some point though.

Ah, that's great. I should have thought of that, thanks. I'll have a look at the rewrite branch now for online doc generation.