tensorflow version

Which version of tensorflow your code ran? I ran it under version 1.14.0, but it has some traceback.

I used the TF 1.10.0

I used the TF 1.9.0

tf-gpu  1.13.0

pip install --ignore-installed --upgrade https://storage.googleapis.com/tensorflow/linux/gpu/tensorflow_gpu-1.13.1-cp37-cp37m-linux_x86_64.whl
Collecting tensorflow-gpu==1.13.1 from https://storage.googleapis.com/tensorflow/linux/gpu/tensorflow_gpu-1.13.1-cp37-cp37m-linux_x86_64.whl
Using cached https://storage.googleapis.com/tensorflow/linux/gpu/tensorflow_gpu-1.13.1-cp37-cp37m-linux_x86_64.whl
Collecting astor>=0.6.0 (from tensorflow-gpu==1.13.1)
Using cached https://files.pythonhosted.org/packages/d1/4f/950dfae467b384fc96bc6469de25d832534f6b4441033c39f914efd13418/astor-0.8.0-py2.py3-none-any.whl
Collecting termcolor>=1.1.0 (from tensorflow-gpu==1.13.1)
Downloading https://files.pythonhosted.org/packages/8a/48/a76be51647d0eb9f10e2a4511bf3ffb8cc1e6b14e9e4fab46173aa79f981/termcolor-1.1.0.tar.gz
Collecting grpcio>=1.8.6 (from tensorflow-gpu==1.13.1)
ERROR: Could not find a version that satisfies the requirement grpcio>=1.8.6 (from tensorflow-gpu==1.13.1) (from versions: none)
ERROR: No matching distribution found for grpcio>=1.8.6 (from tensorflow-gpu==1.13.1)

/root/tf/UGATIT 11:26:54# python main.py Traceback (most recent call last):   File "main.py", line 1, in <module>     from UGATIT import UGATIT   File "/root/tf/UGATIT/UGATIT.py", line 5, in <module>     from tensorflow.contrib.data import prefetch_to_device, shuffle_and_repeat, map_and_batch ImportError: cannot import name 'prefetch_to_device' /root/tf/UGATIT 11:26:59# python -c 'import tensorflow as tf;print(tf.VERSION)' 1.6.0


[$500]  Reimbursements - "Unlock next-day reimbursements" section blinks

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

Version Number: 1.4.11-1
Reproducible in staging?: y
Reproducible in production?: y
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
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Navigate to staging.new.expensify.com
Go to Settings> Workspace> Reimbursements

Expected Result:
There should be no visual issues when open Reimbursements
Actual Result:
"Unlock next-day reimbursements" section blinks
Workaround:
Unknown
Platforms:

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

[x] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/93399543/1bf4d6cc-b906-4e14-a17c-2ec26cc8f526
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01188ed266452a88a6
Upwork Job ID:<PHONE_NUMBER>444499968
Last Price Increase: 2023-12-11

Proposal
Please re-state the problem that we are trying to solve in this issue.
Navigate to workspace > reimbursements, the third section unlock next-day reimbursements shows loading indicator instead of showing section without delay.
What is the root cause of that problem?
The next-day reimbursements are loaded using Policy.openWorkspaceReimburseView(props.policy.id). The bank accounts are not unique to each workspace i.e. bank accounts are shared across workspaces, open bank account in workspace A, that bank account is shown under reimbursements for workspace B.
https://github.com/Expensify/App/blob/cf918b6fb34336ffaa70a85cd83f2d6edea3bab1/src/pages/workspace/reimburse/WorkspaceReimburseView.js#L91
In the workspaceReimburseSection, the achState.state data is being loaded from props.reimbursementAccount before checking whether props.reimbursementAccount.isLoading is true or false. The achData.state does not have any prop linking to policyID of the workspace.
https://github.com/Expensify/App/blob/298d9d2db15db35dd49206151d9301e60ffb10a4/src/pages/workspace/reimburse/WorkspaceReimburseSection.js#L39
What changes do you think we should make in order to solve the problem?
When displaying WorkspaceReimburseSection, only the achData.state is needed. Instead of using openWorkspaceReimburseView to get achData, openReimbursementAccountPage() can be used. The openReimbursementAccountPage() is used when navigating to workspace > bank accounts and functionality wise returns the needed achData but without the policyID dependency.
https://github.com/Expensify/App/blob/298d9d2db15db35dd49206151d9301e60ffb10a4/src/pages/ReimbursementAccount/ReimbursementAccountPage.js#L275
In WorkspacesListPage.js, add useEffect to run once and call openReimbursementAccountPage(). By adding early enough in WorkspacesListPage, openReimbursementAccountPage() gets the time to load without the use of debounce.
https://github.com/Expensify/App/blob/298d9d2db15db35dd49206151d9301e60ffb10a4/src/pages/workspace/WorkspacesListPage.js#L109
const achData = lodashGet(reimbursementAccount, 'achData', {});

function fetchData(ignoreLocalCurrentStep) {
    // Show loader right away, as optimisticData might be set only later in case multiple calls are in the queue
    BankAccounts.setReimbursementAccountLoading(true);
    BankAccounts.openReimbursementAccountPage();
}

useEffect(
    () => {
        fetchData();
        return () => {
        // clear previous reimbursementAccount data
            BankAccounts.clearReimbursementAccount();
        };
    },
    // eslint-disable-next-line react-hooks/exhaustive-deps
    [],
); // The empty dependency array ensures this runs only once after the component mounts.

The debounce that was introduced due to openWorkspaceReimburseView in WorkspaceReimburseSection can be removed.
https://github.com/Expensify/App/blob/298d9d2db15db35dd49206151d9301e60ffb10a4/src/pages/workspace/reimburse/WorkspaceReimburseSection.js#L42
Add useEffect to just update shouldShowLoadingSpinner.
useEffect(()=>{
    setShouldShowLoadingSpinner(props.reimbursementAccount.isLoading);
}, [props.reimbursementAccount.isLoading])

Also in WorkspaceReimburseView, the fetchData callback can be removed.
https://github.com/Expensify/App/blob/cf918b6fb34336ffaa70a85cd83f2d6edea3bab1/src/pages/workspace/reimburse/WorkspaceReimburseView.js#L86C38-L86C38
Also remove fetchData() from the useEffect
https://github.com/Expensify/App/blob/cf918b6fb34336ffaa70a85cd83f2d6edea3bab1/src/pages/workspace/reimburse/WorkspaceReimburseView.js#L94

@ntdiary please also review proposal . I suggested the use of openReimbursementAccountPage() instead of openWorkspaceReimburseView(props.policy.id).

So far, I prefer @bernhardoj's https://github.com/Expensify/App/issues/32841#issuecomment-1850651744, and if you agree with my RCA analysis, can you please update your proposal?

Just holding on this ^

@ntdiary I tested the selected proposal and I was still getting blinks. Also need to factor that the achData.state is cleared when the user clicks on bank accounts and navigates back to workpage, then clicking in reimbursement would show the blinks. I do not have an ideal solution yet, even requesting the call earliar in WorkspacesListPage the blinks still show.

@ntdiary in regards to the expected behavior and the blinks the 'unlock next-day reimbursements' card should load seamlessly, i.e. there should be no delay in displaying the card similar to 'track distance' and 'capture receipts. That would be ideal solution.

np!

n regards to the expected behavior and the blinks the 'unlock next-day reimbursements' card should load seamlessly, i.e. there should be no delay in displaying the card similar to 'track distance' and 'capture receipts. That would be ideal solution.

@sourcecodedeveloper would you mind showing this with a screencapture? I'm not exactly sure how you're seeing this, but @ntdiary isn't.

@Julesssss I had suggested the spinner activity on the third card should not be visible similar to the first two cards but if the spinner activity is not considered to be visual issue then @ntdiary is correct i.e remove debounce.

Ah yeah it's not a big deal. I agree with this suggestion that we go with @bernhardoj's proposal.

PR is ready
cc: @ntdiary

@ntdiary @bernhardoj you've both been paid!
@ntdiary don't forget about the BZ checklist!

all set here then!


How to represent +1 and -1 in one bit?

As mentioned in the BinaryNet paper, we can use the XNOR-Bitcounting operation.
It seems to be reasonable, but when we really try to realize this in one bit, how should we represent -1? Should we convert it into 0?
And that seems to meet some problems when we try to xnor it with the input 8-bit vector, since mostly a negative number will be in 2-complement form..
I might be wrong, just a little bit confused since I was wondering how to achieve this on hardware...

In practice, we use 0s to represent the -1s,
XOR-popcount-adds to compute the weighted sums,
and finally we adjust these weighted sums so that we get the same result as a dot-product (for inputs constrained to (-1,1)).

Thanks for the reply! :)
Is it because the input pixel value is an 8bit uint number that we can use the XOR-popcount-adds method?
It does get a right answer with unsigned input vector, but how about a vector of signed numbers (maybe we do not need to consider such situation?)?

And what if one of the weight vector is all 1s? Overflowed?
In case of that, we should take a (8+log2(vectorlength))bit number to represent the output?


Get-DbaTopResourceUsage

Is this:

[x] feature
[ ] bug:

Proposal
This is a post 1.0 command, just placing this here as a reminder and include specific that myself and Chrissy already discussed.
Command that is built around Michael J Swart's top resource hog queries. Potential is to have a single command, then have parameters drive which resource set to return. Would need to make sure you are excluding the current session from the query, and what versions of SQL Server these support (think 2008+ only).
I have used these queries for years to gather information on a given instance and they work very well as-is. There is likely some improvements that can be made, or expanded upon with latest versions of SQL Server.

here you go, baw https://github.com/sqlcollaborative/dbatools/pull/2305


the remote server being used to run remote jobs is not obvious

It would be nice to have a check mark or something. Perhaps write out the name being used next to the remote button?

I think putting the name next to the remote button is the easiest way forward.

Cycic.java
Line 711-749.
Lines 718-738 are local

New server selection (and add/remove) in Cycic.
Removed the "Run" menubar


Status of this project

Firstly, I just want to say how grateful am I to the developers of this excellent library! Thanks, guys!
However, I'm a little nervous about its status. The last issue to be closed was on Feb 19, 2016 (almost 2 years ago), the last commit on Aug 5 2015 (well over 2 years ago), and the last PR to be merged on Mar 2, 2014 (almost 4 years ago). Looking through the open issues, there don't even appear to have been any comments from a developer in a long, long time. The web-site also fails to reflect the change in the project's licensing. It's looking very much as though this project is - at best - lacking support, and - at worst - completely dead.
I appreciate that maintaining the library can be a lot of effort, particularly when you're volunteering your time and effort. However, I'd welcome a statement of intent regarding the future of this library. What's the roadmap for future releases? If high-quality PRs are submitted, will they be accepted? Will a new maintainer be sought if necessary?

I found some time in the last few days to work on usb4java and bumped libusb to the latest 1.0.22 version and implemented all the stuff Luca listed in the last comment and additionally also the libusb_get_pollfds() function which was also missing.
I want to do a few more tests (Especially the new USBDK stuff on Windows) and then I guess usb4java is ready for a 1.3.0 release.
I'm closing this issue because it is not a bug report.


FuturesApiV2.Trading.GetOrderAsync does not report the state of an order

Describe the bug
When I use FuturesApiV2.Trading.GetOrderAsync the field Status is always "Initial".
To Reproduce
Used the given function with several OrderIds.
Have compared it to the "old" version FuturesApi.Trading.GetOrderAsync. Here the status is shwon correctly. Currently I am using this old version.
Expected behavior
A filled order should show in status "filled".
Debug logging
FuturesApi.Trading.GetOrderAsync result:

FuturesApiV2.Trading.GetOrderAsync result:

If you need more details please let me know.
I use your interface for some days now. And it looks really good to many. Some more minor issues. I will report them step by step.

Hi, it seems the documentation was incorrect for this, listing the property as status instead of the actually returned value state, but it's since the implementation been fixed. I'll adjust the mapping for it in next version.
Let me know if you have any other issues!

Thanks a lot. When will this version be available?

Nice. Love it
Gesendet von Outlook für Androidhttps://aka.ms/AAb9ysg

From: Jan Korf @.>
Sent: Friday, July 26, 2024 2:46:17 PM
To: JKorf/Bitget.Net @.>
Cc: SRNebu2007 @.>; Author @.>
Subject: Re: [JKorf/Bitget.Net] FuturesApiV2.Trading.GetOrderAsync does not report the state of an order (Issue #30)
Planning on releasing tomorrow, or Sunday latest
—
Reply to this email directly, view it on GitHubhttps://github.com/JKorf/Bitget.Net/issues/30#issuecomment-2252690461, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A64BSLSXGEAFAAQXJBLG6N3ZOJAJTAVCNFSM6AAAAABLNIFKNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJSGY4TANBWGE.
You are receiving this because you authored the thread.Message ID: @.***>

Fixed in latest version


Remove Global Variables $TimerEvent and $WebEvent

Description of the Change
This request aims to remove the global variables $TimerEvent and $WebEvent from the codebase to enhance security. These variables will be passed to the runspaces using System.Management.Automation.Runspaces.SessionStateVariableEntry.
Background:
Global variables can lead to several issues, including namespace pollution, difficulty in tracking modifications, unintended side effects, and security risks. To address these concerns, we are refactoring the code to avoid the use of global variables.
Changes:

Removed the global definitions of $TimerEvent and $WebEvent.
Passed these variables to the runspaces using System.Management.Automation.Runspaces.SessionStateVariableEntry.

Code changes
Before
function Start-PodeAzFuncServer {
    param(
        [Parameter(Mandatory = $true)]
        $Data
    )
    ....
    # reset event data
    $global:WebEvent = @{
        OnEnd            = @()
        Auth             = @{}
        Response         = $response
        Request          = $request
        Lockable         = $PodeContext.Threading.Lockables.Global
        Path             = [string]::Empty
        Method           = $request.Method.ToLowerInvariant()
        Query            = $request.Query
        Endpoint         = @{
            Protocol = ($request.Url -split '://')[0]
            Address  = $null
            Name     = $null
        }
        ContentType      = $null
        ErrorType        = $null
        Cookies          = @{}
        PendingCookies   = @{}
        Parameters       = $null
        Data             = $null
        Files            = $null
        Streamed         = $false
        Route            = $null
        StaticContent    = $null
        Timestamp        = [datetime]::UtcNow
        TransferEncoding = $null
        AcceptEncoding   = $null
        Ranges           = $null
        Metadata         = @{}
    }
}

function New-PodeRunspaceState {
    # create the state, and add the pode modules
    $state = [initialsessionstate]::CreateDefault()
    $state.ImportPSModule($PodeContext.Server.PodeModule.DataPath)
    $state.ImportPSModule($PodeContext.Server.PodeModule.InternalPath)

    # load the vars into the share state
    $session = New-PodeStateContext -Context $PodeContext

    $variables = @(
        (New-Object System.Management.Automation.Runspaces.SessionStateVariableEntry -ArgumentList 'PodeContext', $session, $null),
        (New-Object System.Management.Automation.Runspaces.SessionStateVariableEntry -ArgumentList 'Console', $Host, $null),
        (New-Object System.Management.Automation.Runspaces.SessionStateVariableEntry -ArgumentList 'PODE_SCOPE_RUNSPACE', $true, $null)
    )

    foreach ($var in $variables) {
        $state.Variables.Add($var)
    }

    $PodeContext.RunspaceState = $state
}

After
function Start-PodeAzFuncServer {
    param(
        [Parameter(Mandatory = $true)]
        $Data
    )
    ....
    # reset event data
    $WebEvent += @{
        OnEnd            = @()
        Auth             = @{}
        Response         = $response
        Request          = $request
        Lockable         = $PodeContext.Threading.Lockables.Global
        Path             = [string]::Empty
        Method           = $request.Method.ToLowerInvariant()
        Query            = $request.Query
        Endpoint         = @{
            Protocol = ($request.Url -split '://')[0]
            Address  = $null
            Name     = $null
        }
        ContentType      = $null
        ErrorType        = $null
        Cookies          = @{}
        PendingCookies   = @{}
        Parameters       = $null
        Data             = $null
        Files            = $null
        Streamed         = $false
        Route            = $null
        StaticContent    = $null
        Timestamp        = [datetime]::UtcNow
        TransferEncoding = $null
        AcceptEncoding   = $null
        Ranges           = $null
        Metadata         = @{}
    }
}

function New-PodeRunspaceState {
    # create the state, and add the pode modules
    $state = [initialsessionstate]::CreateDefault()
    $state.ImportPSModule($PodeContext.Server.PodeModule.DataPath)
    $state.ImportPSModule($PodeContext.Server.PodeModule.InternalPath)

    # load the vars into the share state
    $session = New-PodeStateContext -Context $PodeContext

    $variables = @(
        (New-Object System.Management.Automation.Runspaces.SessionStateVariableEntry -ArgumentList 'PodeContext', $session, $null),
        (New-Object System.Management.Automation.Runspaces.SessionStateVariableEntry -ArgumentList 'Console', $Host, $null),
        (New-Object System.Management.Automation.Runspaces.SessionStateVariableEntry -ArgumentList 'TimerEvent', $TimerEvent, $null),
        (New-Object System.Management.Automation.Runspaces.SessionStateVariableEntry -ArgumentList 'WebEvent', $WebEvent, $null),
        (New-Object System.Management.Automation.Runspaces.SessionStateVariableEntry -ArgumentList 'PODE_SCOPE_RUNSPACE', $true, $null)
    )

    foreach ($var in $variables) {
        $state.Variables.Add($var)
    }

    $PodeContext.RunspaceState = $state
}

Ah, I thought this is what you might have been referring to from #1295.
This actually doesn't resolve this particular scoping issue with $TimerEvent and $WebEvent. For the serverless $WebEvent the child runspace pools are never actually created by Pode 😉 everything is invoked at the parent scope, which must mean that AzFunc/Lambda invokes PowerShell scripts themselves as another child runspace - which would explain why $global: is needed.
For $TimerEvent I'm still baffled however, unless $global: is used even the state variable trick doesn't make the variable accessible (results below from the timers.ps1 example):

Using state variables from this PR, you can see Next/Last are blank, and that outputting the timer is blank as well:

Using $global:, you can see Next/Last are populated, and outputting the time is populated:

Setting $TimerEvent at the runspace pool level also exposes a variable hijacking issue; if you were to add a custom property to $TimerEvent in a timer scriptblock, then it would still be accessible in other timers, more so using +=.
The only way to really remove them properly, specifically for TimerEvent and for serverless the WebEvent, would be to pass them as explicit parameters to the timer/route scriptblock - but to do this now would be a hefty breaking change, for timers specifically, as it would change their initialisation to need param($TimerEvent) in the scriptblock. Another thought I've had is to move timers into their own separate runspace pool - similar to schedules -see what happens then.


feat(embeds): Handle more embeds

PR for #18

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

v1.6.0
GitHub release

Your semantic-release bot :package::rocket:


simplification idea

There are config settings:

DATABASE_PATH for sqlite3 only
DATABASE_DATABASE

potentially could remove the path setting and expect the database name to include path in config. This has the potential to be easier/less config ... there are arguments to be made for the reverse ;)

DATABASE_PATH isn't a good name for database name and DATABASE_DATABASE isn't a good name for database path. If we would keep just one setting, then it should be something different, but that would be a braking change.
When using Docker with sqlite3 no environment variables are needed, DATABASE_PATH is set in Dockerfile and all other configuration variables can be set in UI.
Documentation should be improved


somethingSelected() returns true if only whitespace is selected

Not sure if this is an issue but when doc.somethingSelected() returns true even if  only white space is selected.

My reading of the API is this: if nothing is selected, then hitting the delete key should not modify the document in any way. Removing white space modifies the document, therefore something has to be considered selected.

Yes, this method is behaving as it is intended.


How to test using flags?

First of all, I have following my docs/blogs/posts trying to find a way to test a simple CLI application and yours is the best so, thank you very much. My question is, how can I implement flags in the way you're doing the tests?
I have tried to do the following once I have a flag receiving a string to disable some fmt.Scan() I have in my code to confirm my actions. Seems like my flag gets ignored.
func TestCreateWallet(t *testing.T) {
	var expect = "ok"
	var actual = capturer.CaptureStdout(func() {
		var cmdTmp = &cobra.Command{}
		var argsTmp = []string{"arg1", "--testing", "enabled"}
		createWalletCmd.PreRun(cmdTmp, argsTmp)
	})

	assert.Equal(t, expect, actual, "Result as expected")
}

Any help will be highly appreciated and by the way, sry for the noob question. This is my first week coding in go.

Wasn't expecting that it would be seen by someone, thank you instead!!!

how can I implement flags

Good point!
I'll try what can I do to implement tests for option flags!🤞
To make it clear, all we need here is to test:

if the "--testing" boolean flag is set then the code notice it, right?

Wasn't expecting that it would be seen by someone, thank you instead!!!

how can I implement flags

Good point!
I'll try what can I do to implement tests for option flags!🤞
To make it clear, all we need here is to test:

if the "--testing" boolean flag is set then the code notice it, right?

Wasn't expecting that it would be seen by someone, thank you instead!!!

how can I implement flags

Good point!
I'll try what can I do to implement tests for option flags!🤞
To make it clear, all we need here is to test:

if the "--testing" boolean flag is set then the code notice it, right?

Flag + Value, like
--myflag myvalue

Wasn't expecting that it would be seen by someone, thank you instead!!!

Once the information is available in the internet, we shall consume it!
Even not having experience in Go, I'll try my best to find a way to do that. if I found the solution, I'll do a PR.

Wasn't expecting that it would be seen by someone, thank you instead!!!

how can I implement flags

Good point!
I'll try what can I do to implement tests for option flags!🤞
To make it clear, all we need here is to test:

if the "--testing" boolean flag is set then the code notice it, right?

Flag + Value, like
--myflag myvalue

Wasn't expecting that it would be seen by someone, thank you instead!!!

Once the information is available in the internet, we shall consume it!
Even not having experience in Go, I'll try my best to find a way to do that. if I found the solution, I'll do a PR.

@wallacepf
I think I found one way of; how to provide command options(args and flags) in the tests.
TL; DR
In the test function, copy/clone the rootCmd and override the variable by using SetArgs(), then Execute the cloned command.
TS; DR
func TestCreateWallet(t *testing.T) {
	// copy the entire rootCmd
	var cmdTmp = *rootCmd

	// Replace the entire argument
	var argsTmp = []string{"prerun", "arg1", "--testing", "enabled"}
	cmdTmp.SetArgs(argsTmp)

	// Run test
	var expect = "OK\n"
	var actual = capturer.CaptureStdout(func() {
		cmdTmp.Execute()
	})
	assert.Equal(t, expect, actual, "The two words should be the same.")
}

SetArgs sets arguments for the command. It is set to os.Args[1:] by default, if desired, can be overridden particularly useful when testing.

https://github.com/spf13/cobra/blob/7df62f7668c7fbeafd6dbb45ad0294f4ea08c0ec/command.go#L227-L231

I did add a sample of using flags and its tests in https://github.com/KEINOS/Hello-Cobra/pull/9, but we need to add this one too.

@wallacepf
I think I found one way of; how to provide command options(args and flags) in the tests.
TL; DR
In the test function, copy/clone the rootCmd and override the variable by using SetArgs(), then Execute the cloned command.
TS; DR
func TestCreateWallet(t *testing.T) {
	// copy the entire rootCmd
	var cmdTmp = *rootCmd

	// Replace the entire argument
	var argsTmp = []string{"prerun", "arg1", "--testing", "enabled"}
	cmdTmp.SetArgs(argsTmp)

	// Run test
	var expect = "OK\n"
	var actual = capturer.CaptureStdout(func() {
		cmdTmp.Execute()
	})
	assert.Equal(t, expect, actual, "The two words should be the same.")
}

SetArgs sets arguments for the command. It is set to os.Args[1:] by default, if desired, can be overridden particularly useful when testing.

https://github.com/spf13/cobra/blob/7df62f7668c7fbeafd6dbb45ad0294f4ea08c0ec/command.go#L227-L231

I did add a sample of using flags and its tests in https://github.com/KEINOS/Hello-Cobra/pull/9, but we need to add this one too.

I found this sample repo very useful.

https://github.com/tkit/go-cmd-example @ GitHub

It defines the sub-command as a function rather than declaring it into a variable.
package cmd

import (
	"github.com/spf13/cobra"
)

func NewCmdShow() *cobra.Command {
	type Options struct {
		Optint int    `validate:"min=0,max=10"`
		Optstr string `validate:"required,alphanum"`
	}

	var (
		o = &Options{}
	)

	cmd := &cobra.Command{
		Use:   "show",
		Short: "A brief description of your command",
		PreRunE: func(cmd *cobra.Command, args []string) error {
			return validateParams(*o)
		},
		Run: func(cmd *cobra.Command, args []string) {
			cmd.Printf("show called: optint: %d, optstr: %s", o.Optint, o.Optstr)
		},
		SilenceErrors: true,
		SilenceUsage:  true,
	}
	cmd.Flags().IntVarP(&o.Optint, "int", "i", 0, "int option")
	cmd.Flags().StringVarP(&o.Optstr, "str", "s", "", "string option")

	return cmd
}

func init() {
}

This way seems to ease testing.
package cmd

import (
	"bytes"
	"github.com/mattn/go-shellwords"
	"testing"
)

func TestShow(t *testing.T) {
	cases := []struct {
		command string
		want    string
		errWant string
	}{
		{command: "cmd-test show", want: "", errWant: "Parameter error: Optstr is required"},
		{command: "cmd-test show --int 10", want: "", errWant: "Parameter error: Optstr is required"},
		{command: "cmd-test show --str test", want: "show called: optint: 0, optstr: test"},
		{command: "cmd-test show --str \"test1 test2\"", want: "", errWant: "Parameter error: Optstr is not valid test1 test2"},
		{command: "cmd-test show --int 1000 --str 123", want: "", errWant: "Parameter error: Optint cannot be greater than 10"},
		{command: "cmd-test show --int -1 --str abc", want: "", errWant: "Parameter error: Optint must be greater than 0"},
		{command: "cmd-test show --int 1 --str abc", want: "show called: optint: 1, optstr: abc"},
	}

	for _, c := range cases {
		buf := new(bytes.Buffer)
		cmd := NewCmdRoot()
		cmd.SetOutput(buf)
		cmdArgs, err := shellwords.Parse(c.command)
		if err != nil {
			t.Fatalf("args parse error: %+v\n", err)
		}
		cmd.SetArgs(cmdArgs[1:])
		if err := cmd.Execute(); err != nil {
			if c.errWant != err.Error() {
				t.Errorf("unexpected error response: errWant:%+v, get:%+v", c.errWant, err.Error())
			}
		}

		get := buf.String()
		if c.want != get {
			t.Errorf("unexpected response: want:%+v, get:%+v", c.want, get)
		}
	}
}

I found this sample repo very useful.

https://github.com/tkit/go-cmd-example @ GitHub

It defines the sub-command as a function rather than declaring it into a variable.
package cmd

import (
	"github.com/spf13/cobra"
)

func NewCmdShow() *cobra.Command {
	type Options struct {
		Optint int    `validate:"min=0,max=10"`
		Optstr string `validate:"required,alphanum"`
	}

	var (
		o = &Options{}
	)

	cmd := &cobra.Command{
		Use:   "show",
		Short: "A brief description of your command",
		PreRunE: func(cmd *cobra.Command, args []string) error {
			return validateParams(*o)
		},
		Run: func(cmd *cobra.Command, args []string) {
			cmd.Printf("show called: optint: %d, optstr: %s", o.Optint, o.Optstr)
		},
		SilenceErrors: true,
		SilenceUsage:  true,
	}
	cmd.Flags().IntVarP(&o.Optint, "int", "i", 0, "int option")
	cmd.Flags().StringVarP(&o.Optstr, "str", "s", "", "string option")

	return cmd
}

func init() {
}

This way seems to ease testing.
package cmd

import (
	"bytes"
	"github.com/mattn/go-shellwords"
	"testing"
)

func TestShow(t *testing.T) {
	cases := []struct {
		command string
		want    string
		errWant string
	}{
		{command: "cmd-test show", want: "", errWant: "Parameter error: Optstr is required"},
		{command: "cmd-test show --int 10", want: "", errWant: "Parameter error: Optstr is required"},
		{command: "cmd-test show --str test", want: "show called: optint: 0, optstr: test"},
		{command: "cmd-test show --str \"test1 test2\"", want: "", errWant: "Parameter error: Optstr is not valid test1 test2"},
		{command: "cmd-test show --int 1000 --str 123", want: "", errWant: "Parameter error: Optint cannot be greater than 10"},
		{command: "cmd-test show --int -1 --str abc", want: "", errWant: "Parameter error: Optint must be greater than 0"},
		{command: "cmd-test show --int 1 --str abc", want: "show called: optint: 1, optstr: abc"},
	}

	for _, c := range cases {
		buf := new(bytes.Buffer)
		cmd := NewCmdRoot()
		cmd.SetOutput(buf)
		cmdArgs, err := shellwords.Parse(c.command)
		if err != nil {
			t.Fatalf("args parse error: %+v\n", err)
		}
		cmd.SetArgs(cmdArgs[1:])
		if err := cmd.Execute(); err != nil {
			if c.errWant != err.Error() {
				t.Errorf("unexpected error response: errWant:%+v, get:%+v", c.errWant, err.Error())
			}
		}

		get := buf.String()
		if c.want != get {
			t.Errorf("unexpected response: want:%+v, get:%+v", c.want, get)
		}
	}
}

Tried this last example but seems like my get isn't returning any value, below you will find the entire code:
package cmd

import (
	"bytes"
	"encoding/json"
	"fmt"
	"io/ioutil"
	"log"
	"net/http"

	"github.com/spf13/cobra"
)

// Wallet Object
type Wallet struct {
	Name string   `json:"name"`
	Tags []string `json:"tags"`
}

var wlt *Wallet

var tags []string
var tFlag string

func createWalletCmd() *cobra.Command {
	cmd := &cobra.Command{
		Use:   "wallet",
		Short: "Create a new wallet",
		Args:  cobra.ExactArgs(1),
		PreRun: func(cmd *cobra.Command, args []string) {
			wlt = new(Wallet)
			wlt.Name = args[0]

			if len(tags) == 0 {
				wlt.Tags = append(wlt.Tags, "default")
			} else {
				for _, v := range tags {

					wlt.Tags = append(wlt.Tags, v)
				}
			}

			if tFlag != "enabled" {

				fmt.Println("Wallet:", wlt.Name, "\nTags:", wlt.Tags, "\nIs this operation correct? y/N")

				var decision string

				fmt.Scan(&decision)
				if decision != "y" {
					log.Fatal("Wallet Insertion Cancelled", wlt.Name, tFlag)
				}
			} else {
				fmt.Println("OK")
			}

		},
		Run: func(cmd *cobra.Command, args []string) {

			jsonData, _ := json.Marshal(wlt)

			response, err := http.Post(appURL+"wallet", "application/json", bytes.NewBuffer(jsonData))
			if err != nil {
				// fmt.Printf("ok")
				if tFlag == "enabled" {
					fmt.Printf("OK")
				} else {
					log.Fatal(err)
				}

			} else {
				data, _ := ioutil.ReadAll(response.Body)
				fmt.Println(string(data))
			}

		},
	}
	cmd.Flags().StringVar(&tFlag, "testing", "", "for testing")
	cmd.Flags().MarkHidden("testing")
	cmd.Flags().StringSliceVarP(&tags, "tags", "t", []string{}, "Add tags to the wallet (For more than one, use csv)")

	return cmd
}

func init() {
	createCmd.AddCommand(createWalletCmd())
}

my test file
package cmd

import (
	"bytes"
	"testing"

	"github.com/mattn/go-shellwords"
)

func TestShow(t *testing.T) {
	cases := []struct {
		command string
		want    string
		errWant string
	}{
		{command: "wallet MyWallet --testing enabled", want: "OK", errWant: ""},
	}

	for _, c := range cases {
		buf := new(bytes.Buffer)
		cmd := createWalletCmd()
		cmd.SetOutput(buf)
		cmdArgs, err := shellwords.Parse(c.command)
		if err != nil {
			t.Fatalf("args parse error: %+v\n", err)
		}
		cmd.SetArgs(cmdArgs[1:])
		if err := cmd.Execute(); err != nil {
			if c.errWant != err.Error() {
				t.Errorf("unexpected error response: errWant: %+v, get:%+v", c.errWant, err.Error())
			}
		}

		get := buf.String()
		if c.want != get {
			t.Errorf("unexpected response: want: %+v, get: %+v", c.want, get)
		}
	}
}

the output after running the test
Running tool: /usr/local/bin/go test -timeout 30s -run ^TestShow$ wallet-cli/cmd

OK
OK--- FAIL: TestShow (0.00s)
    /Users/wallacepf/Dev/wallet project/go_wallet_cli/cmd/create_wallet_test.go:36: unexpected response: want: OK, get:
FAIL
FAIL	wallet-cli/cmd	0.518s
FAIL

These "OK" were printed from my cobra command and that's why it gets really odd. Even though my script is returning twice the OK (One in the prerun and the other one in the Run) it's not taken in consideration. Both OKs were added just to validate the test ok? JFYI

Tried this last example but seems like my get isn't returning any value, below you will find the entire code:
package cmd

import (
	"bytes"
	"encoding/json"
	"fmt"
	"io/ioutil"
	"log"
	"net/http"

	"github.com/spf13/cobra"
)

// Wallet Object
type Wallet struct {
	Name string   `json:"name"`
	Tags []string `json:"tags"`
}

var wlt *Wallet

var tags []string
var tFlag string

func createWalletCmd() *cobra.Command {
	cmd := &cobra.Command{
		Use:   "wallet",
		Short: "Create a new wallet",
		Args:  cobra.ExactArgs(1),
		PreRun: func(cmd *cobra.Command, args []string) {
			wlt = new(Wallet)
			wlt.Name = args[0]

			if len(tags) == 0 {
				wlt.Tags = append(wlt.Tags, "default")
			} else {
				for _, v := range tags {

					wlt.Tags = append(wlt.Tags, v)
				}
			}

			if tFlag != "enabled" {

				fmt.Println("Wallet:", wlt.Name, "\nTags:", wlt.Tags, "\nIs this operation correct? y/N")

				var decision string

				fmt.Scan(&decision)
				if decision != "y" {
					log.Fatal("Wallet Insertion Cancelled", wlt.Name, tFlag)
				}
			} else {
				fmt.Println("OK")
			}

		},
		Run: func(cmd *cobra.Command, args []string) {

			jsonData, _ := json.Marshal(wlt)

			response, err := http.Post(appURL+"wallet", "application/json", bytes.NewBuffer(jsonData))
			if err != nil {
				// fmt.Printf("ok")
				if tFlag == "enabled" {
					fmt.Printf("OK")
				} else {
					log.Fatal(err)
				}

			} else {
				data, _ := ioutil.ReadAll(response.Body)
				fmt.Println(string(data))
			}

		},
	}
	cmd.Flags().StringVar(&tFlag, "testing", "", "for testing")
	cmd.Flags().MarkHidden("testing")
	cmd.Flags().StringSliceVarP(&tags, "tags", "t", []string{}, "Add tags to the wallet (For more than one, use csv)")

	return cmd
}

func init() {
	createCmd.AddCommand(createWalletCmd())
}

my test file
package cmd

import (
	"bytes"
	"testing"

	"github.com/mattn/go-shellwords"
)

func TestShow(t *testing.T) {
	cases := []struct {
		command string
		want    string
		errWant string
	}{
		{command: "wallet MyWallet --testing enabled", want: "OK", errWant: ""},
	}

	for _, c := range cases {
		buf := new(bytes.Buffer)
		cmd := createWalletCmd()
		cmd.SetOutput(buf)
		cmdArgs, err := shellwords.Parse(c.command)
		if err != nil {
			t.Fatalf("args parse error: %+v\n", err)
		}
		cmd.SetArgs(cmdArgs[1:])
		if err := cmd.Execute(); err != nil {
			if c.errWant != err.Error() {
				t.Errorf("unexpected error response: errWant: %+v, get:%+v", c.errWant, err.Error())
			}
		}

		get := buf.String()
		if c.want != get {
			t.Errorf("unexpected response: want: %+v, get: %+v", c.want, get)
		}
	}
}

the output after running the test
Running tool: /usr/local/bin/go test -timeout 30s -run ^TestShow$ wallet-cli/cmd

OK
OK--- FAIL: TestShow (0.00s)
    /Users/wallacepf/Dev/wallet project/go_wallet_cli/cmd/create_wallet_test.go:36: unexpected response: want: OK, get:
FAIL
FAIL	wallet-cli/cmd	0.518s
FAIL

These "OK" were printed from my cobra command and that's why it gets really odd. Even though my script is returning twice the OK (One in the prerun and the other one in the Run) it's not taken in consideration. Both OKs were added just to validate the test ok? JFYI

@wallacepf

seems like my get isn't returning any value

OMG. The same thing happened to me. The buf isn't buffering anything.
But the original sample did work. And I found that cobra version differs from ours. (See below)
Details running the sample
$ git clone https://github.com/tkit/go-cmd-example.git
Cloning into 'go-cmd-example'...
remote: Enumerating objects: 38, done.
remote: Total 38 (delta 0), reused 0 (delta 0), pack-reused 38
Unpacking objects: 100% (38/38), done.

$ cd go-cmd-example
$ go mod init sample
go: creating new go.mod: module sample
go: copying requirements from Gopkg.lock

$ go install
....

$ go test ./...
?       sample  [no test files]
ok      sample/cmd      (cached)

$ cat go.mod | grep cobra
        github.com/spf13/cobra v0.0.1

$ cat go.mod
module sample

go 1.15

require (
        github.com/fsnotify/fsnotify v1.4.2
        github.com/go-playground/locales v0.11.2
        github.com/go-playground/universal-translator v0.16.0
        github.com/hashicorp/hcl v0.0.0-20171017181929-23c074d0eceb
        github.com/inconshreveable/mousetrap v1.0.0
        github.com/magiconair/properties v1.7.3
        github.com/mattn/go-shellwords v1.0.3
        github.com/mitchellh/go-homedir v0.0.0-20161203194507-b8bc1bf76747
        github.com/mitchellh/mapstructure v0.0.0-20171017171808-06020f85339e
        github.com/pelletier/go-toml v1.0.1
        github.com/spf13/afero v1.0.0
        github.com/spf13/cast v1.1.0
        github.com/spf13/cobra v0.0.1
        github.com/spf13/jwalterweatherman v0.0.0-20170901151539-12bd96e66386
        github.com/spf13/pflag v1.0.0
        github.com/spf13/viper v1.0.0
        github.com/tkit/go-cmd-example v0.0.0-20171126084729-c013a3f0a738
        golang.org/x/sys v0.0.0-20171124171047-4ff8c001ce4c
        golang.org/x/text v0.1.1-0.20171102192421-88f656faf3f3
        gopkg.in/go-playground/validator.v9 v9.9.0
        gopkg.in/yaml.v2 v2.0.0-20171116090243-287cf08546ab
)

The whole problem is:

The sample and ours both use the currently deprecated function SetOutput() ...

I switched from SetOutput() to SetOut() and did work. Hope this helps!

@wallacepf

seems like my get isn't returning any value

OMG. The same thing happened to me. The buf isn't buffering anything.
But the original sample did work. And I found that cobra version differs from ours. (See below)
Details running the sample
$ git clone https://github.com/tkit/go-cmd-example.git
Cloning into 'go-cmd-example'...
remote: Enumerating objects: 38, done.
remote: Total 38 (delta 0), reused 0 (delta 0), pack-reused 38
Unpacking objects: 100% (38/38), done.

$ cd go-cmd-example
$ go mod init sample
go: creating new go.mod: module sample
go: copying requirements from Gopkg.lock

$ go install
....

$ go test ./...
?       sample  [no test files]
ok      sample/cmd      (cached)

$ cat go.mod | grep cobra
        github.com/spf13/cobra v0.0.1

$ cat go.mod
module sample

go 1.15

require (
        github.com/fsnotify/fsnotify v1.4.2
        github.com/go-playground/locales v0.11.2
        github.com/go-playground/universal-translator v0.16.0
        github.com/hashicorp/hcl v0.0.0-20171017181929-23c074d0eceb
        github.com/inconshreveable/mousetrap v1.0.0
        github.com/magiconair/properties v1.7.3
        github.com/mattn/go-shellwords v1.0.3
        github.com/mitchellh/go-homedir v0.0.0-20161203194507-b8bc1bf76747
        github.com/mitchellh/mapstructure v0.0.0-20171017171808-06020f85339e
        github.com/pelletier/go-toml v1.0.1
        github.com/spf13/afero v1.0.0
        github.com/spf13/cast v1.1.0
        github.com/spf13/cobra v0.0.1
        github.com/spf13/jwalterweatherman v0.0.0-20170901151539-12bd96e66386
        github.com/spf13/pflag v1.0.0
        github.com/spf13/viper v1.0.0
        github.com/tkit/go-cmd-example v0.0.0-20171126084729-c013a3f0a738
        golang.org/x/sys v0.0.0-20171124171047-4ff8c001ce4c
        golang.org/x/text v0.1.1-0.20171102192421-88f656faf3f3
        gopkg.in/go-playground/validator.v9 v9.9.0
        gopkg.in/yaml.v2 v2.0.0-20171116090243-287cf08546ab
)

The whole problem is:

The sample and ours both use the currently deprecated function SetOutput() ...

I switched from SetOutput() to SetOut() and did work. Hope this helps!

After some coding, I started to feel capturer.CaptureStdout() is a lot easier to test and read, and short as well.

After some coding, I started to feel capturer.CaptureStdout() is a lot easier to test and read, and short as well.

@KEINOS so first of all I have to say thank you very much to get engaged with me in this adventure hehehe. I could fix the code and properly get it tested and validated. What I did to get it properly working was:
package cmd

import (
	"bytes"
	"testing"

	"github.com/kami-zh/go-capturer"
	"github.com/stretchr/testify/assert"
)

func TestShow(t *testing.T) {
	var contains string
	var cmdTmp = createWalletCmd()
	var argsTmp = []string{"wallet teste", "--testing", "enabled"}
	buf := new(bytes.Buffer)
	result := capturer.CaptureStdout(func() {
		cmdTmp.SetOut(buf)
		cmdTmp.SetArgs(argsTmp)
		cmdTmp.Execute()
	})
	contains = "OK"

	assert.Equal(t, result, contains, "Not OK")

}

and it simply worked as expected! Once again, thank you very much and I believe you can close the case.

@KEINOS so first of all I have to say thank you very much to get engaged with me in this adventure hehehe. I could fix the code and properly get it tested and validated. What I did to get it properly working was:
package cmd

import (
	"bytes"
	"testing"

	"github.com/kami-zh/go-capturer"
	"github.com/stretchr/testify/assert"
)

func TestShow(t *testing.T) {
	var contains string
	var cmdTmp = createWalletCmd()
	var argsTmp = []string{"wallet teste", "--testing", "enabled"}
	buf := new(bytes.Buffer)
	result := capturer.CaptureStdout(func() {
		cmdTmp.SetOut(buf)
		cmdTmp.SetArgs(argsTmp)
		cmdTmp.Execute()
	})
	contains = "OK"

	assert.Equal(t, result, contains, "Not OK")

}

and it simply worked as expected! Once again, thank you very much and I believe you can close the case.

Nice! and clean! Glad that you solved it!
And because of this, I also got a little deeper into cobra and go, thank you too!
I found that searching the answer together like this one let us learn.
So I opened the GitHub Discussions tab above. Feel free to share questions again there!

For some reason, I couldn't move this issue to the Discussions, so I'll leave this question here in the issue.

Now closing! :tada:

Nice! and clean! Glad that you solved it!
And because of this, I also got a little deeper into cobra and go, thank you too!
I found that searching the answer together like this one let us learn.
So I opened the GitHub Discussions tab above. Feel free to share questions again there!

For some reason, I couldn't move this issue to the Discussions, so I'll leave this question here in the issue.

Now closing! :tada:


Nuxt app extremely slow start after adding the module.

Environment

Operating System: Darwin
Node Version:     v18.16.0
Nuxt Version:     ^3.12.1
Nitro Version:    -
Package Manager<EMAIL_ADDRESS>Builder:          webpack
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
npx nuxi init test-app
yarn add @nuxtjs/tailwindcss

Add @nuxtjs/tailwindcss to modules

Describe the bug
On removing the module, I can see normal build time.
On adding the module, following are the logs:
Logs:
ℹ Vite client warmed up in 320631ms                                                                                4:36:25 PM
ℹ Vite server warmed up in 340586ms                                                                                4:36:45 PM
✔ Nuxt Nitro server built in 182991 ms

Additional context
No response
Logs
No response

Some how, I cannot reproduce on stackblitz, i.e. start time is consistent with or without module. Please suggest a fix as this is becoming very annoying.
Restarted the system already.
Cleared and reinstalled node modules already.

Sorry I need more context? Is your project repository public, or you can share the relevant configurations (nuxt.config, tailwind.config, etc)
Are you supposed to be getting a Vite server/client if the builder is webpack?

Yes, I narrowed down the culprit to tailwind config file. As soon as I remove config file, server starts properly.
Attaching files below:
package.json
{
  "name": "nuxt-app",
  "private": true,
  "type": "module",
  "scripts": {
    "build": "nuxt build",
    "dev": "nuxt dev",
    "generate": "nuxt generate",
    "preview": "nuxt preview",
    "postinstall": "nuxt prepare"
  },
  "dependencies": {
    "@nuxtjs/tailwindcss": "6.11.4",
    "@tailwindcss/forms": "^0.5.7",
    "nuxt": "^3.12.1",
    "vue": "^3.4.27",
    "vue-router": "^4.3.2"
  }
}

nuxt.config.ts
// https://nuxt.com/docs/api/configuration/nuxt-config
export default defineNuxtConfig({
  modules: ["@nuxtjs/tailwindcss"],
  css: [
    "~/assets/css/style.css",
    "~/assets/css/additional-styles/range-slider.css",
    "~/assets/css/additional-styles/theme.css",
    "~/assets/css/additional-styles/toggle-switch.css",
    "~/assets/css/additional-styles/utility-patterns.css",
  ],
  devtools: { enabled: true },
});

tailwind.config.js REMOVING THIS FILE SOLVES THE ISSUE
module.exports = {
  content: [
    './**/*.{vue,js,ts,jsx,tsx}',
  ],
  theme: {
    extend: {
      fontFamily: {
        inter: ['Inter', 'sans-serif'],
        nycd: ['Nothing You Could Do', 'cursive'],
      },
      fontSize: {
        xs: ['0.75rem', { lineHeight: '1.5' }],
        sm: ['0.875rem', { lineHeight: '1.5715' }],
        base: ['1rem', { lineHeight: '1.5', letterSpacing: '-0.01em' }],
        lg: ['1.125rem', { lineHeight: '1.5', letterSpacing: '-0.01em' }],
        xl: ['1.25rem', { lineHeight: '1.5', letterSpacing: '-0.01em' }],
        '2xl': ['1.5rem', { lineHeight: '1.415', letterSpacing: '-0.01em' }],
        '3xl': ['1.875rem', { lineHeight: '1.333', letterSpacing: '-0.01em' }],
        '4xl': ['2.25rem', { lineHeight: '1.277', letterSpacing: '-0.01em' }],
        '5xl': ['3rem', { lineHeight: '1', letterSpacing: '-0.01em' }],
        '6xl': ['3.75rem', { lineHeight: '1', letterSpacing: '-0.01em' }],
        '7xl': ['4.5rem', { lineHeight: '1', letterSpacing: '-0.01em' }],
      },
      letterSpacing: {
        tighter: '-0.02em',
        tight: '-0.01em',
        normal: '0',
        wide: '0.01em',
        wider: '0.02em',
        widest: '0.4em',
      },
    },
  },
  plugins: [
    // eslint-disable-next-line global-require
    require('@tailwindcss/forms'),
  ],
};

DAMN!! Is this because of contents? Is it scanning node_modules too?

You got it! No need to specify content as the module already does the right optimised paths for you. 🙂


⚠ Bofrost.lu has degraded performance

In da0407c, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 890 ms

Resolved: Bofrost.lu performance has improved in 725625a after 6 minutes.


[WIP] 6413/integrate endpoints for post scheduling

#6413
Integrate endpoints for post scheduling and handle permissions for clients

added endpoints for publish scheduled post and get all scheduled posts
from/to option for get scheduled posts
frontend can fetch scheduled posts in admin (tested)
remove client type check in auth middleware, because it brings no value!

TODO

[x] wait for subscriber branch (both subscriber branch and i integrated a handling for handling client context ----> we use external)

closed because of #6861


Dev/targets.ini

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
This pull request uses the latest changes to the testing tools to implement multi-platform system tests. This required:

adding targets.ini files to each system test class directory
restructuring the system test directories to PharLap, Linux, and Common (both)
restructuring the test dependencies to match this new structure

Why should this Pull Request be merged?
This enables the ATS to run tests for supported RT platforms.
What testing has been done?
Tests were manually executed on the ATS host for each target in the config file.

Update PR name


Do not cancel sending output SB messages for in-flight executions aft…

…er the SB  listener stopped
There is no need to throw the OperationCancelledException for output binding if we signaled that the host is stopping. Other extensions do not cancel the sending:
https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/storage/Microsoft.Azure.WebJobs.Extensions.Storage.Queues/src/Triggers/QueueTriggerBinding.cs#L120
https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/storage/Microsoft.Azure.WebJobs.Extensions.Storage.Blobs/src/Triggers/BlobTriggerBinding.cs#L169

API change check
API changes are not detected in this pull request.

Any update on this PR? This is blocking us from successfully leveraging net 6 function using service bus in any sort of scaling plan such as premium.

Any update on this PR? This is blocking us from successfully leveraging net 6 function using service bus in any sort of scaling plan such as premium.

I second this - we are also blocked from resolving a bug that we believe is being caused by the cancellation that this PR removes

With the proposed change to no longer signal cancellation when draining in https://github.com/Azure/azure-sdk-for-net/pull/36792, the fix here becomes obsolete. The fix to the customer issue can be tracked instead in https://github.com/Azure/azure-sdk-for-net/pull/36792


Create Organisation Profile Type and Industry Dropdowns are too narrow

Currently:

Verified in STG  for 'Create Org" as working fine but it is NOT for EDIT org profile, Refer attached GIF:

adding new bug to fix this issue for EDIT Org page too #1621


devtools vuex not working

🐛 when using vueDevTools vuex not update correctly
we are using your package but when vuex updated the state data did'nt update in vueDevTools

This is a known issue with the Vue devtools although I believe there is a workaround - see https://github.com/danielroe/typed-vuex/issues/108


Getting rid of jQuery megaissue

The process itself became kind of an unorganized mess. I thought it would make sense to keep track of stuff here.
Contributors, please feel free to get involved and help with the process. It will take some time, so every PR counts.
Another goal should be to never merge anything new that has jQuery code added.
How to help
Every module/theme known to be free of jQuery code will be marked with an X.
Feel free to reference to this issue (#907) when doing related work.
Helpful links

"You might not need jQuery". A great website. Lists direct native JS replacements of many of the jQuery functions. Easy to use and very helpful.
"Cheat sheet for moving from jQuery to vanilla JavaScript"

Modules and themes

Themes

[ ] admin_default
[ ] Huraga

Modules

[x] Activity
[x] Api
[x] Branding
[x] Cart
[ ] Client
[x] Cookieconsent (#908)
[x] Cron
[ ] Currency
[x] Custompages
[x] Dashboard
[ ] Email
[ ] Embed
[x] Example
[x] Extension
[ ] Formbuilder
[x] Hook
[x] Index
[ ] Invoice
[x] Kb
[x] Massmailer
[x] News
[x] Notification
[x] Order
[x] Orderbutton
[ ] Page
[x] Paidsupport
[ ] Product
[x] Profile
[x] Queue
[x] Redirect
[x] Seo
[x] Servicecustom
[ ] Servicedomain
[ ] Servicedownloadable
[ ] Servicehosting
[x] Servicelicense (#908)
[x] Servicemembership
[ ] Serviceproxmox
[x] Spamchecker
[ ] Staff
[x] Stats
[ ] Support
[x] System
[ ] Theme
[x] Wysiwyg

Misc

[ ] Installer

[ ]  Installer

The entire thing will need a rewrite for this. Every single part of it relies on jQuery I believe

[ ]  Installer

The entire thing will need a rewrite for this. Every single part of it relies on jQuery I believe

Yes. The wizard thing entirely relies on jQuery.

I'm moving this back in the roadmap to 1.1-1.2 as it depends on a complete rewrite of the installer which is also roadmapped for those releases (#1683). Yes, it would be nice to have for 1.0 but the list of tasks before that release is huge and as the current installer works I don't feel that the release of a replacement is a release blocker.


Add support to make module dora work

unshift slash into MEMFS

cc @shaoshuai0102

Current coverage is 93.10% (diff: 100%)

Merging #8 into master will increase coverage by 0.12%

@@             master         #8   diff @@
==========================================
  Files             2          2
  Lines           114        116     +2
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            106        108     +2
  Misses            8          8
  Partials          0          0

Powered by Codecov. Last update 147d823...c894aeb

Merged with a path.sep bug to be fixed in master later.


Options.click seems not working

Options.click = true is not working in way I understand it.
When I turn it on (Options.click = true), I expected my click events to work as normal. But in fact I have normal behaviour only for input,textarea and select elements, as I see in code.
Fast fix - smt like on screen

Was wrong. Evil is here.


[Bug]: Document viewer widget looks different in Edge browser

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Document viewer widget looks different in Edge browser

Steps To Reproduce

Open release in Edge
Drag and drop document viewer widget

Public Sample App
No response
Version
cloud

@shwetha-ramesh
For PDF rendering Document viewer used iframe and Browser-Wise has rendering iframe is different.
so I don’t think it is an issue.

@somangshu  can you plz help here .
Here I don’t think it is an issue. we can close this issue.


Can't use curl with this addon

I'm trying to use the homebridge-cmdswitch2 plugin as suggested in https://community.home-assistant.io/t/homekit-location-to-trigger-automations-in-home-assistant-using-a-software-switch-requires-no-homekit-hardware/17235/8
Unfortunately the scripts don't work because curl can't be found:
[8/26/2017, 9:29:39 AM] [CMD switch] Initializing cmdSwitch2 platform...
[8/26/2017, 9:29:39 AM] Loading 0 accessories...
[8/26/2017, 9:29:39 AM] [CMD switch] Initializing platform accessory 'Mauricio is Home'...
[8/26/2017, 9:29:39 AM] [CMD switch] Failed to determine Mauricio is Home state.
[8/26/2017, 9:29:39 AM] [CMD switch] /config/homebridge/mbonani_status.sh: line 1: /usr/bin/curl: not found

But curl is there in the host:
root@hassio:~# which curl
/usr/bin/curl

And the script run normally in the shell:
core-ssh:/config/homebridge# ./mbonani_status.sh
{"attributes": {"friendly_name": "Mauricio at home"}, "entity_id": "input_boolean.mbonani_home", "last_changed": "2017-08-26T11:57:19.829657+00:00", "last_updated": "2017-08-26T11:57:19.829657+00:00", "state": "on"}

Can you help me on that?

I also have the same problem. It looks like the following needs to be added to the docker file please:
apt-get -qq -y install curl

I agree on adding curlsince it would be useful in many cases.

Updated milestone, will be part of a larger project, see: https://github.com/orgs/hassio-addons/projects/2

Broken link :-(

The links works on my machine.
Nevertheless, GitHub linked it just above your comment "New build system & base images".

@mauriciobonani Ok, I've learned something new today. Organisation projects are not visible to the public and GitHub currently offers no way to make them public.
Nevertheless, it's on the board ;)

Looking forward for the new version release

Will be automatically be fixed as soon as #28 is implemented/closed.

This issue is fixed in v2.0.0 of the add-on.


Fixes for issues #10 and #11

Fixes #10
Fixes #11

This change is

Awesome work here! Thank you!
I merged updates to this resource module so if you rebase the common tests should pass.

Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

a discussion (no related file):
Would you be up to creating a unit tests, for at least the changes in this PR? I added a template in the Tests/Unit folder.

DSCResources/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1, line 380 at r1 (raw file):

$blDriveType

We should avoid abbreviations. Could we maybe call this $DriveTypeValue or similar (not sure of the best naming here) so that it' more clear that it contain the numeric value of the volume type.

DSCResources/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1, line 388 at r1 (raw file):

            $vol = $null

            if (Split-Path -Path $blv.MountPoint -IsAbsolute) {

We should have open and closing braces on separate rows.

DSCResources/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1, line 390 at r1 (raw file):

Get-WmiObject

Please use Get-CimInstance instead.
https://ci.appveyor.com/project/PowerShell/xbitlocker/build/<IP_ADDRESS>#L1097

DSCResources/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1, line 390 at r1 (raw file):

            if (Split-Path -Path $blv.MountPoint -IsAbsolute) {
                # MountPoint is a Drive Letter
                $vol = Get-WmiObject -Namespace "root\cimv2\security\microsoftvolumeencryption" -Class Win32_Encryptablevolume -ErrorAction SilentlyContinue | Where-Object {($_.DriveLetter -eq $blv.Mountpoint) -and ($_.VolumeType -eq $blDriveType)}

The difference here is the Where-Object. Maybe we could call Get-CimInstance once, before the if-block, and the evaluate the result using Where-Object depending if it is a absolute path or not?

DSCResources/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1, line 391 at r1 (raw file):

                # MountPoint is a Drive Letter
                $vol = Get-WmiObject -Namespace "root\cimv2\security\microsoftvolumeencryption" -Class Win32_Encryptablevolume -ErrorAction SilentlyContinue | Where-Object {($_.DriveLetter -eq $blv.Mountpoint) -and ($_.VolumeType -eq $blDriveType)}
            } else {

We should have open and closing braces on seperate rows.

Comments from Reviewable

Review status: all files reviewed at latest revision, 6 unresolved discussions, some commit checks failed.

README.md, line 105 at r1 (raw file):

### Unreleased
* Converted appveyor.yml to install Pester from PSGallery instead of from Chocolatey.
* Fixed issue which caused xBLAutoBitlocker to incorrectly detect Fixed vs Removable volumes

If an entry resolves an issue please reference the issue where applicable. You may suffix (it's optional) each entry with your name. Example of the format for the entry.
* Descriptive entry ([issue #123](https://github.com/PowerShell/xPSDesiredStateConfiguration/issues/123). [Name/Alias (@github_account)](https://github.com/github_account)`

Comments from Reviewable

Codecov Report

:exclamation: No coverage uploaded for pull request base (dev@f718d81). Click here to learn what that means.
The diff coverage is 0%.

@@          Coverage Diff          @@
##             dev     #14   +/-   ##
=====================================
  Coverage       ?   3.29%
=====================================
  Files          ?       3
  Lines          ?      91
  Branches       ?       0
=====================================
  Hits           ?       3
  Misses         ?      88
  Partials       ?       0

Impacted Files
Coverage Δ

...s/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1
1.96% <0%> (ø)

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 f718d81...1e2e6b2. Read the comment docs.

When you have resolved the review comments, or if you need to discuss a comment. Could you please go into Reviewable and write 'Done' (or click the done-button) on each of the review comments. This allows me to acknowledge (resolve) the review comments and I know that you are done with each change. After you written 'Done' on each review comment,  or comment on the review comment if it needs further discussion, then click the big green 'Publish' button on top of the page. That will send all your comments back as one big comment to this PR.
You find Reviewable if you click on the big purple Reviewable-button in the PR description.

Review status: 0 of 11 files reviewed at latest revision, 7 unresolved discussions.

a discussion (no related file):
Previously, johlju (Johan Ljunggren) wrote…
Would you be up to creating a unit tests, for at least the changes in this PR? I added a template in the Tests/Unit folder.

I am not very fluent with Pester, I used it only handful of times for my experiments. I can try (have to learn it sooner or later anyway), but it's gonna be slow and probably lot of trial-and-failure

README.md, line 105 at r1 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
If an entry resolves an issue please reference the issue where applicable. You may suffix (it's optional) each entry with your name. Example of the format for the entry.
* Descriptive entry ([issue #123](https://github.com/PowerShell/xPSDesiredStateConfiguration/issues/123). [Name/Alias (@github_account)](https://github.com/github_account)`

Done.

DSCResources/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1, line 380 at r1 (raw file):
Previously, johlju (Johan Ljunggren) wrote…

$blDriveType

We should avoid abbreviations. Could we maybe call this $DriveTypeValue or similar (not sure of the best naming here) so that it' more clear that it contain the numeric value of the volume type.

Done.

DSCResources/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1, line 388 at r1 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
We should have open and closing braces on separate rows.

Done.

DSCResources/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1, line 390 at r1 (raw file):
Previously, johlju (Johan Ljunggren) wrote…

Get-WmiObject

Please use Get-CimInstance instead.
https://ci.appveyor.com/project/PowerShell/xbitlocker/build/<IP_ADDRESS>#L1097

Done.

DSCResources/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1, line 390 at r1 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
The difference here is the Where-Object. Maybe we could call Get-CimInstance once, before the if-block, and the evaluate the result using Where-Object depending if it is a absolute path or not?

Done.
Out of curiosity and for my education: what's the difference? This is in IF-ELSE so GET-CIMINSTANCE does not get called twice anyway.

DSCResources/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1, line 391 at r1 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
We should have open and closing braces on seperate rows.

Done.

Comments from Reviewable

@MartinVokurek seems this PR are changing more files than it should. Maybe the rebase didn't work correctly? There are a commit from me, see https://github.com/PowerShell/xBitlocker/pull/14/commits.
Could you pleas try the rebase again? See here for help (same as resolving conflicts) https://github.com/PowerShell/DscResources/blob/master/GettingStartedWithGitHub.md#resolve-merge-conflicts

Review status: 1 of 11 files reviewed at latest revision, 1 unresolved discussion.

a discussion (no related file):
Previously, MartinVokurek (Martin Vokurek) wrote…
I am not very fluent with Pester, I used it only handful of times for my experiments. I can try (have to learn it sooner or later anyway), but it's gonna be slow and probably lot of trial-and-failure

Then this is a good opportunity to learn! Happy to give pointers, and if you get stuck on errors I will help you solve them. :slightly_smiling_face:

DSCResources/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1, line 390 at r1 (raw file):
Previously, MartinVokurek (Martin Vokurek) wrote…
Done.
Out of curiosity and for my education: what's the difference? This is in IF-ELSE so GET-CIMINSTANCE does not get called twice anyway.

No problem, happy to explain. It's basically to reduce duplicated code where we can. If we someday need to change the Get-CimInstance call, we only have to change it at one location, reducing that someone forgets to change the second call (or third or forth location if it were to be used more).
For example, we could also have move up the ($_.VolumeType -eq $DriveTypeValue) to the Get-CimInstance call. But that might be to excessive, we don't have to go overboard with it either. :slightly_smiling_face:
| Where-Object {
    $_.VolumeType -eq $DriveTypeValue
}
``

No need to don anything more with this. This looks good as-is.

DSCResources/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1, line 381 at r3 (raw file):

        switch ($DriveType)
        {
            "Fixed"

We should use single-quotes where applicable. Throughout.

DSCResources/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1, line 383 at r3 (raw file):

$DriveTypeValue

We should change this to $driveTypeValue (I wrote it wrong in previous comment). We should use camelCase on local variables (parameters use PascalCase). Throughout.

DSCResources/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1, line 395 at r3 (raw file):

$EncryptableVolumes

We should change this to $encryptableVolumes. We should use camelCase on local variables (parameters use PascalCase). Throughout.

DSCResources/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1, line 395 at r3 (raw file):

$EncryptableVolumes=Get-CimInstance

Please add spaces around the equal sign.

Comments from Reviewable

I tried another rebase, but I think it's not getting any better. It's just two files, maybe it would be the easiest for me to drop the whole branch and start again fresh?

Review status: 1 of 11 files reviewed at latest revision, 5 unresolved discussions.

DSCResources/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1, line 381 at r3 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
We should use single-quotes where applicable. Throughout.

Done.

DSCResources/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1, line 383 at r3 (raw file):
Previously, johlju (Johan Ljunggren) wrote…

$DriveTypeValue

We should change this to $driveTypeValue (I wrote it wrong in previous comment). We should use camelCase on local variables (parameters use PascalCase). Throughout.

Done.

DSCResources/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1, line 395 at r3 (raw file):
Previously, johlju (Johan Ljunggren) wrote…

$EncryptableVolumes

We should change this to $encryptableVolumes. We should use camelCase on local variables (parameters use PascalCase). Throughout.

Done.

DSCResources/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1, line 395 at r3 (raw file):
Previously, johlju (Johan Ljunggren) wrote…

$EncryptableVolumes=Get-CimInstance

Please add spaces around the equal sign.

Done.
Gosh, I am no developer, if I have to try to remember all these nuances, my willingness to fix anything will quickly return back to zero :-)

Comments from Reviewable

Yes, if the rebase didn't work, I think that would be the quickest to create a new branch and open a new PR. :slightly_smiling_face:

Review status: 0 of 11 files reviewed at latest revision, 2 unresolved discussions.

DSCResources/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1, line 395 at r3 (raw file):
Previously, MartinVokurek (Martin Vokurek) wrote…
Done.
Gosh, I am no developer, if I have to try to remember all these nuances, my willingness to fix anything will quickly return back to zero :-)

You are doing great! That's part whats the reviews are for, helping with this. :slightly_smiling_face:
Style guidelines are not easier for developers either. :slightly_smiling_face:  I think being an IT Pro (engineer or developer) coding PowerShell is much the same.

Comments from Reviewable

Review status: 0 of 11 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

DSCResources/MSFT_xBLAutoBitlocker/MSFT_xBLAutoBitlocker.psm1, line 395 at r3 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
 That's part whats the reviews are for, helping with this. :slightly_smiling_face:
Style guidelines are not easier for developers either. :slightly_smiling_face:  I think being an IT Pro (engineer or developer) coding PowerShell is much the same.

Yeah, but for my Support Engineer persona, the magic of Powershell is that you can do something "fast" and not bother about code beauty :)
Ok, I'll switch to another branch, try to build some small tests and create another PR.

Comments from Reviewable

Closing after failed rebase, will open another PR with new branch


Added ProxyKitClient as optional argument

Code discussed in #124
I moved the creation of ProxyKitClient outside of the forwarding hotpath since it uses reflection to generate httpClients

Thanks for PR! Will take a look shortly.

I improved on the PR in https://github.com/damianh/ProxyKit/commit/a7623d9e19fa47df4a89d04c85b008459dd6368d . Instead, ProxyKitClient is injected into ProxyMiddleware and passed to the ForwardToContext via HttpContext.Items. This removes the need for the optional parameter and potentially confused users ("when do I use that?")

	That's perfect. Yeah, I only used the optional argument to be able to test the performance, the user should not need to deal with it. 👍 👍

	/Anders (from phone)

On Sun, Jun 30, 2019 at 10:16 PM +0200, "Damian Hickey"<EMAIL_ADDRESS>wrote:
I improved on the PR in a7623d9 . Instead, ProxyKitClient is injected into ProxyMiddleware and passed to the ForwardToContext via HttpContext.Items. This removes the need for the optional parameter and potentially confused users ("when do I use that?")
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Fix #930 Hyper-V Administrators group localization issue

Local group names are localized on windows and therefore to support windows installations with different locale CDK installer cannot use 'Hyper-V Administrators' group name when adding current user into it using net localgroup command. First it should get localized name by SID (security identifier) for the group using powershell script.

test this

Codecov Report

Merging #931 into master will decrease coverage by 0.09%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master     #931     +/-   ##
=========================================
- Coverage   95.41%   95.31%   -0.1%
=========================================
  Files          39       39
  Lines        3445     3630    +185
  Branches      294      528    +234
=========================================
+ Hits         3287     3460    +173
- Misses        158      160      +2
- Partials        0       10     +10

Impacted Files
Coverage Δ

browser/model/cdk.js
99.2% <100%> (-0.8%)
:arrow_down:

browser/services/platform.js
100% <100%> (+0.95%)
:arrow_up:

browser/services/credentialManager.js
96.87% <0%> (-3.13%)
:arrow_down:

browser/pages/location/controller.js
92.3% <0%> (-2.86%)
:arrow_down:

browser/pages/install/controller.js
78.84% <0%> (-2.75%)
:arrow_down:

browser/main.js
98.48% <0%> (-1.52%)
:arrow_down:

browser/model/devstudio.js
96.8% <0%> (-0.97%)
:arrow_down:

browser/model/helpers/downloader.js
95.27% <0%> (-0.63%)
:arrow_down:

browser/services/data.js
97.06% <0%> (-0.59%)
:arrow_down:

... and 27 more

Continue to review full report at Codecov.

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


Barcode Markers Still not working - Get the value of a barcode on recognition?

Describe the bug
Barcode markers are recognised by the system but no visual is displayed for them (no overlay)
To Reproduce

Expected behavior
A Yellow box should be displayed over the marker but it is not

The console output shows
numMarkers()
getMarker.id, getMarker.idMatrix ,getMarker.pos - pulled from the marker info struct
Additional context
Is there a way to return the barcode value when it is recognised - i.e to display the value of the marker as the overlay for example - show the camera a barcode marker 6 and the number 6 appears, show the camera a barcode marker 25 then number 25 is shown. - the ID or idMatrix from the marker info struct seems to return just a -1 and 0 for all barcode markers respectively.

Hi
to the a-scene add 'detectionMode: mono_and_matrix;' in the same place of matrixCodeType. it should work

Hi,
Thanks for the quick reply!
I’ll give it a go :)

you can register an aframe component on the marker entity (e.g. eventhandler) and then register the eventhandler component on a js script. On that, you can listen to 'markerFound' events. that tells you when the marker is recognized.
so you can first set a data-* attribute with the value number on the HTML and then, knowing which marker has triggered the events, retrieve that data with entity.getAttribute(...)
example on how to use markerFound events:
https://github.com/jeromeetienne/AR.js/blob/master/aframe/examples/marker-events.html


[Feature Request] Strong-typed JSON fields

Background
Related Pisma issue: https://github.com/prisma/prisma/issues/3219
Proposed Solution

Add language-level "type" declaration support (not mapped to database tables) #783
Enforce schema checking at runtime for the strongly-typed fields through enhanced PrismaClient

Fixed in 2.8.0


Related column isn't marked as foreign key

Why related columns are not marked as foreign key in PostgreSQL? All querying works as they should like the column is foreign key but in the table column isn't marked as foreign key. Here is SO question related to it with more details https://stackoverflow.com/questions/61561193/clarification-on-foreign-key-in-aqueduct

For me it adds foreign key constraint. Maybe it is some kind of bug with the GUI you are using to access your database.

@joeconwaystk yes i think it is a bug in GUI.. I’m using pgadmin btw...


chip-tool did not find the matter wifi device (CON-485)

I run the chip-tool pairing command on the Ubuntu virtual machine, but the device cannot be paired. What is the reason for this? The following is my chip-tool log information
chip-tool operating environment: MacOS running Ubuntu 20.04 virtual machine
matter-pair.txt

@Focalcrest-Madi
Please attach complete logs and device logs too.

@jadhavrohit924
The attachment is the complete log and device log.
chip-tool.log
device.log

@Focalcrest-Madi This does not look an issue on the ESP32 side. The chip-tool logs show that it found the device with the matching discriminator and tried to connect over BLE
[1683853359.576417][194361:194362] CHIP:BLE: Device discriminator match. Attempting to connect.

But, nothing happened after that. The device did not even get the BLE connection request. Please check if BLE communication is working fine on the host machine running the chip-tool

Ubuntu can not share the bluetooth adapter with chip-tool. So if you are using bluetooth for other purposes you have to install a second adapter (USB adapters are $2) and then use --ble-adapter=1 on the chip-tool command.

Closing this as it isn't an issue on the ESP32 side.


[spec] Rename May 2018 Upgrade files

Adding hyphens makes the date more human-readable, and still sorts properly.

Love human readable dates. 👍


Container folder is not a project file 0.75.4

Description
I updated my project from 0.74.1 to 0.75.4. In ios folder I have the container folder with GTM file. When I run from terminal I have this error xcodebuild: error: '/Users/bogdan/apps/react-native-mobile-app/ios/container' is not a project file.
If I run from xcode the build is successful. Can you help me to fix this problem from terminal?
Steps to reproduce

after update to 0.75.4
when I run yarn ios

React Native Version
0.75.4
Affected Platforms
Runtime - iOS
Output of npx react-native info
`System:
  OS: macOS 14.4.1
  CPU: (16) x64 Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz
  Memory: 172.63 MB / 52.00 GB
  Shell:
    version: 3.2.57
    path: /bin/bash
Binaries:
  Node:
    version: 18.19.0
    path: /usr/local/bin/node
  Yarn:
    version: 1.22.19
    path: /usr/local/bin/yarn
  npm:
    version: 10.2.3
    path: /usr/local/bin/npm
  Watchman:
    version: 4.9.0
    path: /usr/local/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /Users/bogdan/.rbenv/shims/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.5
      - iOS 17.5
      - macOS 14.5
      - tvOS 17.5
      - visionOS 1.2
      - watchOS 10.5
  Android SDK: Not Found
IDEs:
  Android Studio: 2021.3 AI-213.7172.25.2113.9123335
  Xcode:
    version: 15.4/15F31d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.10
    path: /usr/bin/javac
  Ruby:
    version: 2.7.5
    path: /Users/bogdan/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.75.4
    wanted: 0.75.4
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false`

Stacktrace or Logs
`error Command failed with exit code 66: xcodebuild -list -json -project /Users/bogdan/apps/react-native-mobile-app/ios/container
2024-10-08 09:56:50.644 xcodebuild[86734:4199341] Writing error result bundle to /var/folders/r5/wpsjwhg9245cgqcjs95l5kjc0000gn/T/ResultBundle_2024-08-10_09-56-0050.xcresult
xcodebuild: error: '/Users/bogdan/apps/react-native-mobile-app/ios/container' is not a project file.
Error: Command failed with exit code 66: xcodebuild -list -json -project /Users/bogdan/apps/react-native-mobile-app/ios/container
2024-10-08 09:56:50.644 xcodebuild[86734:4199341] Writing error result bundle to /var/folders/r5/wpsjwhg9245cgqcjs95l5kjc0000gn/T/ResultBundle_2024-08-10_09-56-0050.xcresult
xcodebuild: error: '/Users/bogdan/apps/react-native-mobile-app/ios/container' is not a project file.
    at makeError (/Users/bogdan/apps/react-native-mobile-app/node_modules/execa/lib/error.js:60:11)
    at module.exports.sync (/Users/bogdan/apps/react-native-mobile-app/node_modules/execa/index.js:194:17)
    at /Users/bogdan/apps/react-native-mobile-app/node_modules/@react-native-community/cli-platform-apple/build/tools/getInfo.js:81:41
    at Array.reduce (<anonymous>)
    at getInfo (/Users/bogdan/apps/react-native-mobile-app/node_modules/@react-native-community/cli-platform-apple/build/tools/getInfo.js:74:15)
    at getConfiguration (/Users/bogdan/apps/react-native-mobile-app/node_modules/@react-native-community/cli-platform-apple/build/commands/buildCommand/getConfiguration.js:36:37)
    at Object.func (/Users/bogdan/apps/react-native-mobile-app/node_modules/@react-native-community/cli-platform-apple/build/commands/runCommand/createRun.js:113:52)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Command.handleAction (/Users/bogdan/apps/react-native-mobile-app/node_modules/@react-native-community/cli/build/index.js:118:9)
error Command failed with exit code 1.`

Reproducer
is private
Screenshots and Videos

Hi @BogdanRad, I understand that the reproducer is private, but can you try to replicate the minimal setup starting from this template? Otherwise it would be quite hard for us to help you.
In 0.75 we introduced some changes in the CLI, so this specific use case might got broken. cc. @blakef, @szymonrybczak and @thymikee that worked on the CLI recently.

I can replicate this, it's CLI bug from a feature added 4 months ago (react-native-community/cli#2415).  It's make some assumptions about what's in the xcworkspace contents.xcworkspacedata XML file.  If I start adding other files via the Xcode project navigator:

It blows up:

We could make this a little more robust in the CLI:

@cipolleschi I think @BogdanRad is unblocked as he can build with Xcode, but I'll add some tests and try get a fix out on the CLI.

I'm going to close this as it isn't a React Native bug.  Please track the progress on react-native-community/cli#2522.


Fixing snapshot version

Closes #1521
Fixes # .
Did you remember to?

[ ] Add test case(s)
[ ] Update CHANGES.txt

We encourage pull requests that:

Add new features to TestNG (or)
Fix bugs in TestNG

If your pull request involves fixing SonarQube issues then we would suggest that you please discuss this with the
TestNG-dev before you spend time working on it.

@cbeust - Since this is a pretty straight forward change, please help take a look and kindly facilitate the merge.


extensions do not load

Although
https://github.com/pombase/pombase-chado/issues/1079
now loads without  missing bits,
https://www.pombase.org/gene/SPBC15D4.07c
The extensions are still missing. These would be useful, I think (although possibly I would request a precomposed GO term for these substrates). What so I need to do to  get these CHEBI Ids tio display (despite the fact that these were comma-separated, rather than pipe, these should still load (it just has a slightly different meaning)

I made the fix in #1079 after the load started.  It should be OK on Friday morning.

Sorry, I misread your comment.  We need to add the ChEBI IDs from the extension to the mini PR OBO file (pombe-embl/mini-ontologies/pombe_mini_PR.obo).  I've just done that and I'll check on Saturday morning.

I wonder if there are any more ChEBI Id in the uniprot annotations...

I wonder if there are any more ChEBI Id in the uniprot annotations...

Here are the pombe and japonicus annotations from the GOA GAF: https://curation.pombase.org/kmr44/gene_association.goa_uniprot.gz
These are the only annotations where there's a ChEBI ID in an extension:

DB object ID
DB Object Symbol
GO ID
DB:Reference
Evidence Code
With or From
Assigned By
Annotation Extension

Q9Y7M3
pib2
GO:0140786
GO_REF:0000024
ISO
SGD:S000002991
PomBase
has_input(CHEBI:28300),part_of(GO:1904263)

O14140
rpn15
GO:0043167
PMID:34439840
EXP

DisProt
has_input(ChEBI:3312)

P41820
bfr1
GO:0042626
PMID:16849797
TAS

PomBase
has_input(CHEBI:48080)

O74312
atg9
GO:0017128
GO_REF:0000024
ISS
UniProtKB:Q12142
UniProt
has_input(CHEBI:58088),has_input(CHEBI:57643),has_input(CHEBI:57262),has_input(CHEBI:64612),part_of(GO:0045332),positively_regulates(GO:0000045)

P36619
pmd1
GO:0008559
PMID:1349418
IMP

PomBase
has_input(CHEBI:52646),part_of(GO:1990961)

O14031
pgt1
GO:0034634
PMID:18662319
IDA

PomBase
has_input(CHEBI:16856)

O14031
pgt1
GO:0034634
PMID:18662319
IDA

PomBase
has_input(CHEBI:17858)

O14031
pgt1
GO:0034634
PMID:18662319
IMP

PomBase
has_input(CHEBI:17515)

We need to add the ChEBI IDs from the extension to the mini PR OBO file (pombe-embl/mini-ontologies/pombe_mini_PR.obo). I've just done that and I'll check on Saturday morning.

I did that but the annotation didn't load because of a different error:
line 48915: positively_regulates() not allowed for molecular_function, annotation: SPBC15D4.07c.1 <-> phospholipid scramblase activity

Now that I've looked at this again, the atg9 annotation still doesn't load.  But it has changed a lot in this release of GOA and now doesn't load for a different reason, which looks like a bug: pombase/pombase-chado#1093
The atg9 annotation is the only annotation from GOA that has a CHEBI term in the extension that we should be loading.  The other pombe annotations are either from PomBase or DisProt so are ignored.


[l10n]:LOC:[JP],[IT],[ES] Truncated text in "Development" input

Description
String "Admin Version: x.y.z" is truncated in localized extension
To Reproduce
Steps to reproduce the behavior:

Install AEM sidekick extension to Chrome browser https://chrome.google.com/webstore/detail/aem-sidekick/ccfggkjabjahcjoljmgmklhpaccedipo
Right Click on extension icon > Options
Click "Advanced" in right nav menu
Scroll down to "Development"
Click "Development"

Expected behavior
String "Admin Version: x.y.z" is not truncated in input
Screenshots

Additional context
String is localized in GlaaS
String ID
admin_version_placeholder#message || Admin Version: x.y.z || Localized

@rofe Is there a way to make the box a bit longer?


sickgear: 0.24.15 → 0.25.11

Motivation for this change
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@Artturin, encountered the same issue but as far as I can tell it is expected behaviour when not configured. (Also happens with the current version on the main branch)
Best seek or wait for a user or maintainer to test this.

runs

Wait so the SickBeard.py was being copied for the NixOS service. So there was one sickbeard service and depending on the package it would use sickbeard, sickgear or sickrage. So this change breaks the service.

Changing the ExecStart in the service from ${sickbeard}/SickBeard.py to ${sickbeard}/bin/${sickbeard.pname}
I think will fix it (sickrage, for example, no longer ships the SickBeard.py file).... so I think this is the best solution? But I'm not 100% sure

sickrage should be changed to install to $out/opt too

I'm working on it now. The newer versions require python3

So I need to include all of those packages from nix in the build (I only ask because there are a lot of them sweat_smile

If it is overwheliming you could leave the current version (which still had dependencies in /lib) and leave the version bump for a future person to do the refactoring.


Error creating Docker provider error="could not find default bridge network"

Here's my system (I realize it's fairly non-standard):

Mac mini M2
macOS 15.1.1
Podman 5.3.0

My config files are pretty darn close to the stock examples:
# compose.yaml

services:
  tailscale-docker-proxy:
    image: almeidapaulopt/tsdproxy:latest
    privileged: true
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - datadir:/data
      - ./config:/config
    restart: unless-stopped
volumes:
  datadir:

☝ I had to add privileged: true to get past an earlier error.
👇 When I change the error level to trace it fails schema validation.
# config/tsdproxy.yaml

defaultproxyprovider: default
docker:
  local: # name of the docker provider
    host: unix:///var/run/docker.sock
    defaultproxyprovider: default
tailscale:
  providers:
    default:
      authkey: tskey-auth-****
log:
  level: info # set logging level info, error or trace
  json: false # set to true to enable json logging
proxyaccesslog: true # set to true to enable container access log

Whenever I run compose, the logs look like this:
Initializing server
Version
loading configuration from: /config/tsdproxy.yaml
Validating configuration...
Setting up logger
10:23PM INF Log Settings Log level=info
10:23PM INF Starting server Version=
10:23PM INF Setting up proxy proxies
10:23PM INF Initializing WebServer
10:23PM INF Health check set to ready
�10:23PM ERR Error creating Docker provider error="could not find default bridge network" module=proxymanager
10:23PM ERR No Target Providers found module=proxymanager
�10:23PM INF request host=<IP_ADDRESS>:8080 method=GET status=200 url=/health/ready/

As you can see, the /health/ready/ endpoint pings just fine. I've tried all sorts of different configurations but cannot get past this error.
Thanks!

Thank you. I can now start up successfully and use the trace logging level. The proxy isn't showing up in my Tailscale dashboard, but I'll do some experimenting with tokens and such to see if I can get this working. I appreciate it!
Initializing server
Version
loading configuration from: /config/tsdproxy.yaml
Validating configuration...
Setting up logger
3:19PM INF Log Settings Log level=trace
3:19PM INF Starting server Version=
3:19PM INF Setting up proxy proxies
3:19PM DBG Setting up Tailscale Providers module=proxymanager
3:19PM DBG Created Proxy provider module=proxymanager provider=default
3:19PM INF Initializing WebServer
3:19PM INF Health check set to ready
3:19PM DBG Creating proxies for provider module=proxymanager provider=local
�3:19PM INF request host=<IP_ADDRESS>:8080 method=GET status=200 url=/health/ready/

... The proxy isn't showing up in my Tailscale dashboard...

Of course it wasn't. I had removed the tsdproxy.enable: "true" label from my compose when trying to get to a minimal config 🤦

Can I close?


picking from auto completion is no longer possible

For firefox mobile on Android only. For desktop firefox and chrome on Android it works.
I think this is since #88.
When picking the location it does not show the marker and also does not know the resolved location.

As well as on iOS

Of course I didn’t really test #88 on mobile due to the lack of a real keyboard 🙄

We also need to listen for touch cancel. Otherwise things get selected when one tries to scroll the result list for example.

Solved this with https://github.com/graphhopper/graphhopper-maps/pull/107


Fix possible infinite loop in responder_lite

When querying with asyncio pysnmp with uneven number of oids an infinite loop occurres

Hey @thekafkaf
i merged the pull request on inexio/snmpsim the fork where we try to maintain the snmpsim for the community as much as we can, so as you got any questions write me or open an issue on this forked Repo.
Whether you want to get to the snmplabs docu that is sadly not available anymore on the original site you can look at our website, we tried to recover what we could recover. Link is here.


Fix invalid parsing indents for comments

Fixes #332
Fixes #331
Also properly find wrong indent for 'standalone' comments:
*** Tests Cases ***
# valid comment
  # invalid comment
Test case
    No Operation

Codecov Report

Merging #336 (f318803) into master (7d0e0d6) will increase coverage by 0.05%.
The diff coverage is 98.24%.

@@            Coverage Diff             @@
##           master     #336      +/-   ##
==========================================
+ Coverage   97.43%   97.48%   +0.05%
==========================================
  Files          23       23
  Lines        1909     1947      +38
==========================================
+ Hits         1860     1898      +38
  Misses         49       49

Impacted Files
Coverage Δ

robocop/utils/__init__.py
100.00% <ø> (ø)

robocop/utils/utils.py
98.79% <83.33%> (+0.02%)
:arrow_up:

robocop/checkers/spacing.py
98.70% <100.00%> (+0.23%)
:arrow_up:

Continue to review full report at Codecov.

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


Set log level in config file

Defaults to INFO, both on read (to make sure that old setups without the value in config.yaml don’t fail) and generation of new config file.
Sets the peewee logger to WARNING

Oh snap. Forgot about github adding all subsequent commits to a pull request. Most of these are not appropriate. So closing.
If you believe anyone of them is of value, then I can make a new one.


Linking multiple verses from a chapter

Hi, linking many verses that are together is easy, but is there a way to link to for example: Mat 6:1-3,6 ?
If not, can you implement? thanks!

Hi, this was already suggested in #22, so I'm closing this issue. Just to recap - this feature would be quite difficult to implement, but maybe one day I'll add it. As of right now I don't see it as a priority, but it would certainly be nice to have.


Cleanup and bugfixes

Conformity to PEP8 and general prettiness
Added build script and icon
Move applications into submenu and fix the list being updated

Hello @JMY1000, this looks great, but may I suggest committing only a few small changes in a pull request.
Keep up the good work!


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_16napxcr9k/clone/recipe/meta.yaml:22: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_16napxcr9k/clone/recipe/meta.yaml:29: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: /tmp/abs_16napxcr9k/clone/recipe/meta.yaml:40: http_url: http://github.com/python-zk/kazoo is not https
Errors were found


.Net Core project cannot load the new created tasks.json

VSCode Version: Code 1.11.2 (6eaebe3b9c70406d67c97779468c324a7a95db0e, 2017-04-13T08:03:11.395Z)
OS Version: Windows_NT ia32 6.1.7601
Extensions:

Extension
Author
Version

Bookmarks
alefragnani
0.14.1

theme-onedark
azemoh
0.4.3

jshint
dbaeumer
0.10.15

vscode-eslint
dbaeumer
1.2.8

githistory
donjayamanne
0.2.0

python
donjayamanne
0.6.3

xml
DotJoshJohnson
1.7.0

tslint
eg2
0.12.0

docthis
joelday
0.4.3

cpptools
ms-vscode
0.11.0

csharp
ms-vscode
1.9.0

vscode-icons
robertohuertasm
7.6.0

JavaScriptSnippets
xabikos
1.4.0

Steps to Reproduce:

create a new .net core project, (dotnet new console -n test)
Press F5 then pop up warning to initialize launch configuration
Press F5 again then click the configure task runner and the tasks.json will create automatically.
Although the task "build" is already in the tasks.json, the vscode still warn there is no task "build"

Reload the vscode can solve the problem. I am not sure whether other project will encounter this bug

This got fixed for the upcoming build. Available in insiders already.


Research on enhancing validation errors for component schemas

Current Behavior
Presently RJSF errors are not much descriptive for users to understand. Research on AJV validator to know how can we customize those errors.
Desired Behavior
Augment component-source schemas with enhanced descriptions, if we able to "render" our enhanced descriptions with the sourced descriptions, preferring our enhanced descriptions.

Docs links
Errors
Docs links
AJV6 interceptor?
Lint check for valid Meshery Docs URLs in UI-schemas

Implementation

Acceptance Tests

Mockups

Contributor Guides and Handbook

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

hey @Yashsharma1911 can i work on this issue

hey @Yashsharma1911 can i work on this issue

Thankyou @Akshaybagai52 for raising your hand, have you previously worked with RJSF or AJV by chance, if not no worries
FYI this issue is only to research and discuss possible solutions, If solution will be feasible we will proceed with implementation, I'll update the issue more for you to deep dive into it


Dependency 'androidx.credentials:credentials:1.2.0-rc01' requires libraries and applications that  depend on it to compile against version 34 or later of the Android APIs.

Steps to reproduce

Download the flutter_news_template
Follow the instructions to configure it
Run it

Expected results
flutter_news_template should run without any error because I did not edit anything. I only followed the instructions given in the installation and running video from flutter
Actual results
Dependency 'androidx.credentials:credentials:1.2.0-rc01' requires libraries and applications that depend on it to compile against version 34 or later of the Android APIs.
       :app is currently compiled against android-33.

       Also, the maximum recommended compile SDK version for Android Gradle
       plugin 7.4.2 is 33.

Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[Paste your output here]

Yes! I had those errors too initially. I had to upgrade the Android plugin version, compile and target sdk to 34, I downgraded JDK to 17 and the gradle too to its compatible version before most of those errors disappeared, but then a new error popped up, which is the twitter_login error. I discovered that its version 4.4.2 (<3.0.0 dart version)  is incompatible with the dart version constraint. I've left it. :(

Hi guys 👋🏻
The problems you are seeing are due to the version of flutter you are using, I suggest you try flutter 3.22.2.
We are working on updating the toolkit to support the latest version of flutter, this should be done soon, probably next week.
@danagbemava-nc @lerowi45

Could you try it with the latest version of the toolkit 1.0.14?
@danagbemava-nc @lerowi45

Closing the issue as it should be resolved using the latest version of the template, feel free to reopen the issue if the problem persists.