[jira] [Resolved] (MYNEWT-768) Document newtmgr image erase subcommand
[ https://issues.apache.org/jira/browse/MYNEWT-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu resolved MYNEWT-768. --- Resolution: Fixed > Document newtmgr image erase subcommand > --- > > Key: MYNEWT-768 > URL: https://issues.apache.org/jira/browse/MYNEWT-768 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to document *newtmgr image erase* subcommand for 1.1. See PR > https://github.com/apache/incubator-mynewt-newt/pull/60. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-768) Document newtmgr image erase subcommand
[ https://issues.apache.org/jira/browse/MYNEWT-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049955#comment-16049955 ] Wanda Chiu commented on MYNEWT-768: --- Updated doc in this pr: https://github.com/apache/incubator-mynewt-site/pull/202 Also added more help text for the the newtmgr image erase command in this PR:https://github.com/apache/incubator-mynewt-newtmgr/pull/2 > Document newtmgr image erase subcommand > --- > > Key: MYNEWT-768 > URL: https://issues.apache.org/jira/browse/MYNEWT-768 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to document *newtmgr image erase* subcommand for 1.1. See PR > https://github.com/apache/incubator-mynewt-newt/pull/60. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MYNEWT-776) 1.1 newtmgr commands need to be updated with new global flags
Wanda Chiu created MYNEWT-776: - Summary: 1.1 newtmgr commands need to be updated with new global flags Key: MYNEWT-776 URL: https://issues.apache.org/jira/browse/MYNEWT-776 Project: Mynewt Issue Type: Task Security Level: Public (Viewable by anyone) Components: Documentation Affects Versions: v1_1_0_rel Reporter: Wanda Chiu Assignee: Wanda Chiu Priority: Minor Fix For: v1_1_0_rel Need to update documentation to include new global flags added/changed in 1.1 newtmgr tool commands. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (MYNEWT-762) newtmgr conn add need to be updated for 1.1
[ https://issues.apache.org/jira/browse/MYNEWT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu resolved MYNEWT-762. --- Resolution: Fixed > newtmgr conn add need to be updated for 1.1 > > > Key: MYNEWT-762 > URL: https://issues.apache.org/jira/browse/MYNEWT-762 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to update 1.1 documentation for **newtmgr conn add** and remove > **addr** and **addrtype** as valid parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-762) newtmgr conn add need to be updated for 1.1
[ https://issues.apache.org/jira/browse/MYNEWT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044809#comment-16044809 ] Wanda Chiu commented on MYNEWT-762: --- The documentation for the newtmgr conn add command is in this PR:MYNEWT-762 Doc Update for 1.1 newtmgr conn add format. Marking this Jira as resolved and opening a separate JIRA to document all the newtmgr commands with the new global flags and will wait until we are closer to the release to document since things are still changing. For example - the *-n --devicename* flag has been changed to --name flag. > newtmgr conn add need to be updated for 1.1 > > > Key: MYNEWT-762 > URL: https://issues.apache.org/jira/browse/MYNEWT-762 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to update 1.1 documentation for **newtmgr conn add** and remove > **addr** and **addrtype** as valid parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (MYNEWT-724) mynewt, build on ubuntu
[ https://issues.apache.org/jira/browse/MYNEWT-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu resolved MYNEWT-724. --- Resolution: Fixed > mynewt, build on ubuntu > --- > > Key: MYNEWT-724 > URL: https://issues.apache.org/jira/browse/MYNEWT-724 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Affects Versions: v1_0_0_rel > Environment: Linux Version: > lsb_release -a > Distributor ID: Ubuntu > Description: Ubuntu 14.04.4 LTS > Release: 14.04 > Codename: trusty > Go version: > go version > go version go1.7 linux/386 >Reporter: Filipe >Assignee: Wanda Chiu >Priority: Minor > > when building the mynewt on ubuntu I have an error on go builder: > syscfg/syscfg.go:965: constant 4294967295 overflows int > Seems that the SYSCFG_INTERRUPT_PRIO_MAX is too big for the variable "int" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MYNEWT-693) newtmgr conn add command needs better error checking
[
https://issues.apache.org/jira/browse/MYNEWT-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wanda Chiu closed MYNEWT-693.
-
> newtmgr conn add command needs better error checking
>
>
> Key: MYNEWT-693
> URL: https://issues.apache.org/jira/browse/MYNEWT-693
> Project: Mynewt
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
> Components: Newtmgr
>Affects Versions: v1_0_0_rel
>Reporter: Wanda Chiu
>Assignee: Wanda Chiu
>Priority: Minor
> Fix For: v1_1_0_rel
>
>
> The *newtmgr conn add* command currently only checks that the user provides a
> connection profile name for a command argument. It does not require the user
> to specify arguments such as *type* and *connstring*. For example:
> {code}
> newtmgr conn add myprofile
> Connection profile myprofile successfully added
> {code}
> The command needs better error checking and , minimally, should require the
> user to specify the *type* and *connstring* arguments.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (MYNEWT-640) Add an newt target "amend" feature to amend or delete target variable values
[
https://issues.apache.org/jira/browse/MYNEWT-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wanda Chiu closed MYNEWT-640.
-
> Add an newt target "amend" feature to amend or delete target variable values
> -
>
> Key: MYNEWT-640
> URL: https://issues.apache.org/jira/browse/MYNEWT-640
> Project: Mynewt
> Issue Type: Improvement
> Security Level: Public(Viewable by anyone)
>Affects Versions: v1_0_0_beta2
>Reporter: Wanda Chiu
>Assignee: Wanda Chiu
>Priority: Minor
> Fix For: v1_1_0_rel
>
>
> This is a feature enhancement request (for post 1.0) to support an "append"
> feature that allows a user to change or append to current target variable
> values:
> The *newt target set* sets a variable value with the value
> specified in the command. It overrides the variable's previous values. For
> example, the eventq_nordic target has the follow syscfg.yml content:
> {code}
> ### Package: targets/eventq_nordic
> syscfg.vals:
> CONFIG_NEWTMGR: 1
> LOG_NEWTMGR: 1
> SHELL_TASK: 1
> {code}
> Run *newt target set eventq_nordic syscfg=LOG_NEWTMGR=0* and the syscfg.yml
> file changes to:
> {code}
> ### Package: targets/eventq_nordic
> syscfg.vals:
> LOG_NEWTMGR: 0
> {code}
> Currently users can't append or change specific values for a variable and
> without overriding all values. This support would be useful for target
> variables other than the *syscfg* variable, e.g *cflags*, *lflags*, etc
> (See MYNEWT-543)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (MYNEWT-694) newt run command should query user for version number instead of skipping create image step
[ https://issues.apache.org/jira/browse/MYNEWT-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu closed MYNEWT-694. - > newt run command should query user for version number instead of skipping > create image step > --- > > Key: MYNEWT-694 > URL: https://issues.apache.org/jira/browse/MYNEWT-694 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) > Components: Newt >Affects Versions: v1_0_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > The *newt run* command currently skips the create image step if the user does > not provide a version number for the command. It would be useful to have the > command query the user for a version number and to let the user know that the > command will use default version 0 if one is not provided. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MYNEWT-761) 1.1 Documentation needs to be updated for newtmgr "mpstats" and "taststats" command
[ https://issues.apache.org/jira/browse/MYNEWT-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu closed MYNEWT-761. - > 1.1 Documentation needs to be updated for newtmgr "mpstats" and "taststats" > command > --- > > Key: MYNEWT-761 > URL: https://issues.apache.org/jira/browse/MYNEWT-761 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > *newtmgr mpstats* and *newtmgr taskstats* commands have been changed to > *newtmgr mpstat* and *newtmgr taskstat* (singular instead of plural) post > 1.0. The command guide and tutorials need to be updated to use the new > version for 1.1 documentation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MYNEWT-763) Add documentation for newt target amend command
[ https://issues.apache.org/jira/browse/MYNEWT-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu closed MYNEWT-763. - > Add documentation for newt target amend command > --- > > Key: MYNEWT-763 > URL: https://issues.apache.org/jira/browse/MYNEWT-763 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to add documentation for *newt target amend* command (MYNEWT-640) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MYNEWT-764) Update Doc for newt run command
[ https://issues.apache.org/jira/browse/MYNEWT-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu closed MYNEWT-764. - > Update Doc for newt run command > --- > > Key: MYNEWT-764 > URL: https://issues.apache.org/jira/browse/MYNEWT-764 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to document that *newt run* command now queries the user for a version > (or use default 0) the version is not provided for an application target, > instead of skipping the create-image step. (See MYNEWT-694) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-762) newtmgr conn add need to be updated for 1.1
[ https://issues.apache.org/jira/browse/MYNEWT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038190#comment-16038190 ] Wanda Chiu commented on MYNEWT-762: --- Confirmed with Chris. 1.1 will use -t --timeout flag for timeout. The -t --trace flag will not be supported in 1.1. Also, since the new flags -n -t and -r are global persistent flags, all newtmgr commands in the newtmgr command guide will need to be updated as they all list the values of the global flags. > newtmgr conn add need to be updated for 1.1 > > > Key: MYNEWT-762 > URL: https://issues.apache.org/jira/browse/MYNEWT-762 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to update 1.1 documentation for **newtmgr conn add** and remove > **addr** and **addrtype** as valid parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MYNEWT-762) newtmgr conn add need to be updated for 1.1
[ https://issues.apache.org/jira/browse/MYNEWT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu updated MYNEWT-762: -- Summary: newtmgr conn add need to be updated for 1.1 (was: ble addressing in newtmgr conn add need to be updated for 1.1) > newtmgr conn add need to be updated for 1.1 > > > Key: MYNEWT-762 > URL: https://issues.apache.org/jira/browse/MYNEWT-762 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to update 1.1 documentation for **newtmgr conn add** and remove > **addr** and **addrtype** as valid parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (MYNEWT-762) ble addressing in newtmgr conn add need to be updated for 1.1
[ https://issues.apache.org/jira/browse/MYNEWT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036049#comment-16036049 ] Wanda Chiu edited comment on MYNEWT-762 at 6/3/17 7:19 PM: --- Documentation updates need to include: 1) Removing addr and addrtype connection profile parameters (they are now specified in the connstring) 2) New connstring formats for ble, ble_oic, serial and serial_oic 3) New -n --devicename persistent flag that specifies the name of the target BLE device and overrides the profile settings. 4) New -t --timeout persistent flag that specifies the timeout 5) New -r --tries persistent flag that specifies the total number of tries in case of timeout. 6) Removal of -t --trace flag. *NOTE: Need to confirm that this should be removed. If it shouldn't be removed, then we will need a different flag for timeout since they both use -t* was (Author: cwanda): Documentation updates need to include: 1) Removing addr and addrtype connection profile parameters (they are now specified in the connstring) 2) New connstring formats for ble, ble_oic, serial and serial_oic 3) New -n --devicename persistent flag that specifies the name of the target BLE device and overrides the profile settings. 4) New -t --timeout persistent flag that specifies the timeout 5) New -r --tries persistent flag that specifies the total number of tries in case of timeout. 6) Removal of -t --trace flag. **NOTE: Need to confirm that this should be removed. If it shouldn't be removed, then we will need a different flag for timeout since they both use -t** > ble addressing in newtmgr conn add need to be updated for 1.1 > - > > Key: MYNEWT-762 > URL: https://issues.apache.org/jira/browse/MYNEWT-762 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to update 1.1 documentation for **newtmgr conn add** and remove > **addr** and **addrtype** as valid parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (MYNEWT-762) ble addressing in newtmgr conn add need to be updated for 1.1
[ https://issues.apache.org/jira/browse/MYNEWT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036049#comment-16036049 ] Wanda Chiu edited comment on MYNEWT-762 at 6/3/17 7:19 PM: --- Documentation updates need to include: 1) Removing addr and addrtype connection profile parameters (they are now specified in the connstring) 2) New connstring formats for ble, ble_oic, serial and serial_oic 3) New -n --devicename persistent flag that specifies the name of the target BLE device and overrides the profile settings. 4) New -t --timeout persistent flag that specifies the timeout 5) New -r --tries persistent flag that specifies the total number of tries in case of timeout. 6) Removal of -t --trace flag. **NOTE: Need to confirm that this should be removed. If it shouldn't be removed, then we will need a different flag for timeout since they both use -t** was (Author: cwanda): Documentation updates need to include: 1) Removing addr and addrtype connection profile parameters (they are now specified in the connstring) 2) New connstring formats for ble, ble_oic, serial and serial_oic 3) New -n --devicename persistent flag that specifies the name of the target BLE device and overrides the profile settings. 4) -t --timeout persistent flag that specifies the timeout 5) -r --tries persistent flag that specifies the total number of tries in case of timeout. > ble addressing in newtmgr conn add need to be updated for 1.1 > - > > Key: MYNEWT-762 > URL: https://issues.apache.org/jira/browse/MYNEWT-762 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to update 1.1 documentation for **newtmgr conn add** and remove > **addr** and **addrtype** as valid parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (MYNEWT-762) ble addressing in newtmgr conn add need to be updated for 1.1
[ https://issues.apache.org/jira/browse/MYNEWT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036049#comment-16036049 ] Wanda Chiu edited comment on MYNEWT-762 at 6/3/17 7:16 PM: --- Documentation updates need to include: 1) Removing addr and addrtype connection profile parameters (they are now specified in the connstring) 2) New connstring formats for ble, ble_oic, serial and serial_oic 3) New -n --devicename persistent flag that specifies the name of the target BLE device and overrides the profile settings. 4) -t --timeout persistent flag that specifies the timeout 5) -r --tries persistent flag that specifies the total number of tries in case of timeout. was (Author: cwanda): Documentation updates need to include: 1) Removing addr and addrtype connection profile parameters (they are now specified in the connstring) 2) New connstring formats for ble, ble_oic, serial and serial_oic 3) New -n --devicename persistent flag that specifies the name of the target BLE device and overrides the profile settings. > ble addressing in newtmgr conn add need to be updated for 1.1 > - > > Key: MYNEWT-762 > URL: https://issues.apache.org/jira/browse/MYNEWT-762 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to update 1.1 documentation for **newtmgr conn add** and remove > **addr** and **addrtype** as valid parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-762) ble addressing in newtmgr conn add need to be updated for 1.1
[ https://issues.apache.org/jira/browse/MYNEWT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036049#comment-16036049 ] Wanda Chiu commented on MYNEWT-762: --- Documentation updates need to include: 1) Removing addr and addrtype connection profile parameters (they are now specified in the connstring) 2) New connstring formats for ble, ble_oic, serial and serial_oic 3) New -n --devicename persistent flag that specifies the name of the target BLE device and overrides the profile settings. > ble addressing in newtmgr conn add need to be updated for 1.1 > - > > Key: MYNEWT-762 > URL: https://issues.apache.org/jira/browse/MYNEWT-762 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to update 1.1 documentation for **newtmgr conn add** and remove > **addr** and **addrtype** as valid parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MYNEWT-767) 1.1 Doc needs to be updated for new shell implementation
[ https://issues.apache.org/jira/browse/MYNEWT-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu updated MYNEWT-767: -- Component/s: Documentation > 1.1 Doc needs to be updated for new shell implementation > > > Key: MYNEWT-767 > URL: https://issues.apache.org/jira/browse/MYNEWT-767 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to update 1.1 documentation for shell improvements in > https://github.com/apache/incubator-mynewt-core/pull/256. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MYNEWT-768) Document newtmgr image erase subcommand
[ https://issues.apache.org/jira/browse/MYNEWT-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu updated MYNEWT-768: -- Component/s: (was: Newtmgr) Documentation > Document newtmgr image erase subcommand > --- > > Key: MYNEWT-768 > URL: https://issues.apache.org/jira/browse/MYNEWT-768 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to document *newtmgr image erase* subcommand for 1.1. See PR > https://github.com/apache/incubator-mynewt-newt/pull/60. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MYNEWT-768) Document newtmgr image erase subcommand
Wanda Chiu created MYNEWT-768: - Summary: Document newtmgr image erase subcommand Key: MYNEWT-768 URL: https://issues.apache.org/jira/browse/MYNEWT-768 Project: Mynewt Issue Type: Task Security Level: Public (Viewable by anyone) Components: Newtmgr Affects Versions: v1_1_0_rel Reporter: Wanda Chiu Assignee: Wanda Chiu Priority: Minor Fix For: v1_1_0_rel Need to document *newtmgr image erase* subcommand for 1.1. See PR https://github.com/apache/incubator-mynewt-newt/pull/60. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MYNEWT-767) 1.1 Doc needs to be updated for new shell implementation
Wanda Chiu created MYNEWT-767: - Summary: 1.1 Doc needs to be updated for new shell implementation Key: MYNEWT-767 URL: https://issues.apache.org/jira/browse/MYNEWT-767 Project: Mynewt Issue Type: Task Security Level: Public (Viewable by anyone) Affects Versions: v1_1_0_rel Reporter: Wanda Chiu Assignee: Wanda Chiu Priority: Minor Fix For: v1_1_0_rel Need to update 1.1 documentation for shell improvements in https://github.com/apache/incubator-mynewt-core/pull/256. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-762) ble addressing in newtmgr conn add need to be updated for 1.1
[ https://issues.apache.org/jira/browse/MYNEWT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033660#comment-16033660 ] Wanda Chiu commented on MYNEWT-762: --- Ensure that other parameters supported in newtmgr conn add are ported to the new newtmgr and any differences are documented. > ble addressing in newtmgr conn add need to be updated for 1.1 > - > > Key: MYNEWT-762 > URL: https://issues.apache.org/jira/browse/MYNEWT-762 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to update 1.1 documentation for **newtmgr conn add** and remove > **addr** and **addrtype** as valid parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (MYNEWT-719) Newtmgr fails to build on 32 bit for Mac OS
[
https://issues.apache.org/jira/browse/MYNEWT-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wanda Chiu resolved MYNEWT-719.
---
Resolution: Won't Fix
> Newtmgr fails to build on 32 bit for Mac OS
> ---
>
> Key: MYNEWT-719
> URL: https://issues.apache.org/jira/browse/MYNEWT-719
> Project: Mynewt
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
>Affects Versions: v1_1_0_rel
> Environment: Mac OS
>Reporter: Wanda Chiu
>
> Go cross compile of Newtmgr fails to build for Mac OS/32 bit. Set GOARCH=386
> and build on Mac OS (GOOS can take on default or set to darwin).
> Note: Newtmgr builds successfully for Linux 32 bits(GOOS=Linux GOARCH=386).
> The build has the following errors on vendor code:
> {code}
> mynewt.apache.org/newt/newtmgr/vendor/github.com/tarm/serial
> vendor/github.com/tarm/serial/serial.go:128: undefined: Port
> vendor/github.com/tarm/serial/serial.go:139: undefined: openPort
> # mynewt.apache.org/newt/newtmgr/vendor/github.com/runtimeco/gatt
> vendor/github.com/runtimeco/gatt/device_darwin.go:35: undefined: xpc.XPC
> vendor/github.com/runtimeco/gatt/peripheral_darwin.go:222: undefined: xpc.Dict
> vendor/github.com/runtimeco/gatt/peripheral_darwin.go:223: undefined: xpc.Dict
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MYNEWT-719) Newtmgr fails to build on 32 bit for Mac OS
[
https://issues.apache.org/jira/browse/MYNEWT-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030613#comment-16030613
]
Wanda Chiu commented on MYNEWT-719:
---
I believe we can close this issue, since the Mac OS versions that were we are
supporting only run on 64 bit machines. Changing the status to resolved.
> Newtmgr fails to build on 32 bit for Mac OS
> ---
>
> Key: MYNEWT-719
> URL: https://issues.apache.org/jira/browse/MYNEWT-719
> Project: Mynewt
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
>Affects Versions: v1_1_0_rel
> Environment: Mac OS
>Reporter: Wanda Chiu
>
> Go cross compile of Newtmgr fails to build for Mac OS/32 bit. Set GOARCH=386
> and build on Mac OS (GOOS can take on default or set to darwin).
> Note: Newtmgr builds successfully for Linux 32 bits(GOOS=Linux GOARCH=386).
> The build has the following errors on vendor code:
> {code}
> mynewt.apache.org/newt/newtmgr/vendor/github.com/tarm/serial
> vendor/github.com/tarm/serial/serial.go:128: undefined: Port
> vendor/github.com/tarm/serial/serial.go:139: undefined: openPort
> # mynewt.apache.org/newt/newtmgr/vendor/github.com/runtimeco/gatt
> vendor/github.com/runtimeco/gatt/device_darwin.go:35: undefined: xpc.XPC
> vendor/github.com/runtimeco/gatt/peripheral_darwin.go:222: undefined: xpc.Dict
> vendor/github.com/runtimeco/gatt/peripheral_darwin.go:223: undefined: xpc.Dict
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (MYNEWT-762) ble addressing in newtmgr conn add need to be updated for 1.1
[ https://issues.apache.org/jira/browse/MYNEWT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030101#comment-16030101 ] Wanda Chiu edited comment on MYNEWT-762 at 5/30/17 8:54 PM: For 1.1 all the BLE addressing parameters are moved to the connstring and quite a few more parameters for BLE have been added. Documentation for the *newtmgr conn add* command need to be updated. was (Author: cwanda): For 1.1 all the BLE addressing parameters are moved to the connstring and there are quite a few more parameters have been added. newtmgr conn add documentation need to be updated. > ble addressing in newtmgr conn add need to be updated for 1.1 > - > > Key: MYNEWT-762 > URL: https://issues.apache.org/jira/browse/MYNEWT-762 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to update 1.1 documentation for **newtmgr conn add** and remove > **addr** and **addrtype** as valid parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MYNEWT-762) ble addressing in newtmgr conn add need to be updated for 1.1
[ https://issues.apache.org/jira/browse/MYNEWT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu updated MYNEWT-762: -- Summary: ble addressing in newtmgr conn add need to be updated for 1.1 (was: addr and addrtype are no longer valid parameters for newtmgr conn add) > ble addressing in newtmgr conn add need to be updated for 1.1 > - > > Key: MYNEWT-762 > URL: https://issues.apache.org/jira/browse/MYNEWT-762 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to update 1.1 documentation for **newtmgr conn add** and remove > **addr** and **addrtype** as valid parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-762) addr and addrtype are no longer valid parameters for newtmgr conn add
[ https://issues.apache.org/jira/browse/MYNEWT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030101#comment-16030101 ] Wanda Chiu commented on MYNEWT-762: --- For 1.1 all the BLE addressing parameters are moved to the connstring and there are quite a few more parameters have been added. newtmgr conn add documentation need to be updated. > addr and addrtype are no longer valid parameters for newtmgr conn add > - > > Key: MYNEWT-762 > URL: https://issues.apache.org/jira/browse/MYNEWT-762 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to update 1.1 documentation for **newtmgr conn add** and remove > **addr** and **addrtype** as valid parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (MYNEWT-649) "newt target set" allows random variable to be set; should allow only valid variable settings.
[ https://issues.apache.org/jira/browse/MYNEWT-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu resolved MYNEWT-649. --- Resolution: Fixed > "newt target set" allows random variable to be set; should allow only valid > variable settings. > -- > > Key: MYNEWT-649 > URL: https://issues.apache.org/jira/browse/MYNEWT-649 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Aditi Hilbert >Assignee: Wanda Chiu > Fix For: v1_1_0_rel > > > The "newt target set" command should have a check for allowed settings. > For example, I can set the variable "bogus" with a value and target.bogus > will be added to the target.yml file. Do we have a list of all the valid > variables so we can add the validation to the command? What I have listed as > valid variables in the `newt target set" command documentation are: app, bsp, > loader, build_profile, cflags, aflags, lflags, syscfg. > We should make sure the "newt vals" command also covers this set of valid > target variables to make things consistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (MYNEWT-764) Update Doc for newt run command
[ https://issues.apache.org/jira/browse/MYNEWT-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu resolved MYNEWT-764. --- Resolution: Fixed > Update Doc for newt run command > --- > > Key: MYNEWT-764 > URL: https://issues.apache.org/jira/browse/MYNEWT-764 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to document that *newt run* command now queries the user for a version > (or use default 0) the version is not provided for an application target, > instead of skipping the create-image step. (See MYNEWT-694) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (MYNEWT-763) Add documentation for newt target amend command
[ https://issues.apache.org/jira/browse/MYNEWT-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu resolved MYNEWT-763. --- Resolution: Fixed > Add documentation for newt target amend command > --- > > Key: MYNEWT-763 > URL: https://issues.apache.org/jira/browse/MYNEWT-763 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to add documentation for *newt target amend* command (MYNEWT-640) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MYNEWT-640) Add an newt target "amend" feature to amend or delete target variable values
[
https://issues.apache.org/jira/browse/MYNEWT-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wanda Chiu updated MYNEWT-640:
--
Summary: Add an newt target "amend" feature to amend or delete target
variable values (was: Add an newt target "append" feature to change or append
target variable values)
> Add an newt target "amend" feature to amend or delete target variable values
> -
>
> Key: MYNEWT-640
> URL: https://issues.apache.org/jira/browse/MYNEWT-640
> Project: Mynewt
> Issue Type: Improvement
> Security Level: Public(Viewable by anyone)
>Affects Versions: v1_0_0_beta2
>Reporter: Wanda Chiu
>Assignee: Wanda Chiu
>Priority: Minor
> Fix For: v1_1_0_rel
>
>
> This is a feature enhancement request (for post 1.0) to support an "append"
> feature that allows a user to change or append to current target variable
> values:
> The *newt target set* sets a variable value with the value
> specified in the command. It overrides the variable's previous values. For
> example, the eventq_nordic target has the follow syscfg.yml content:
> {code}
> ### Package: targets/eventq_nordic
> syscfg.vals:
> CONFIG_NEWTMGR: 1
> LOG_NEWTMGR: 1
> SHELL_TASK: 1
> {code}
> Run *newt target set eventq_nordic syscfg=LOG_NEWTMGR=0* and the syscfg.yml
> file changes to:
> {code}
> ### Package: targets/eventq_nordic
> syscfg.vals:
> LOG_NEWTMGR: 0
> {code}
> Currently users can't append or change specific values for a variable and
> without overriding all values. This support would be useful for target
> variables other than the *syscfg* variable, e.g *cflags*, *lflags*, etc
> (See MYNEWT-543)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (MYNEWT-640) Add an newt target "amend" feature to amend or delete target variable values
[
https://issues.apache.org/jira/browse/MYNEWT-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wanda Chiu resolved MYNEWT-640.
---
Resolution: Fixed
> Add an newt target "amend" feature to amend or delete target variable values
> -
>
> Key: MYNEWT-640
> URL: https://issues.apache.org/jira/browse/MYNEWT-640
> Project: Mynewt
> Issue Type: Improvement
> Security Level: Public(Viewable by anyone)
>Affects Versions: v1_0_0_beta2
>Reporter: Wanda Chiu
>Assignee: Wanda Chiu
>Priority: Minor
> Fix For: v1_1_0_rel
>
>
> This is a feature enhancement request (for post 1.0) to support an "append"
> feature that allows a user to change or append to current target variable
> values:
> The *newt target set* sets a variable value with the value
> specified in the command. It overrides the variable's previous values. For
> example, the eventq_nordic target has the follow syscfg.yml content:
> {code}
> ### Package: targets/eventq_nordic
> syscfg.vals:
> CONFIG_NEWTMGR: 1
> LOG_NEWTMGR: 1
> SHELL_TASK: 1
> {code}
> Run *newt target set eventq_nordic syscfg=LOG_NEWTMGR=0* and the syscfg.yml
> file changes to:
> {code}
> ### Package: targets/eventq_nordic
> syscfg.vals:
> LOG_NEWTMGR: 0
> {code}
> Currently users can't append or change specific values for a variable and
> without overriding all values. This support would be useful for target
> variables other than the *syscfg* variable, e.g *cflags*, *lflags*, etc
> (See MYNEWT-543)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (MYNEWT-694) newt run command should query user for version number instead of skipping create image step
[ https://issues.apache.org/jira/browse/MYNEWT-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu resolved MYNEWT-694. --- Resolution: Fixed > newt run command should query user for version number instead of skipping > create image step > --- > > Key: MYNEWT-694 > URL: https://issues.apache.org/jira/browse/MYNEWT-694 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) > Components: Newt >Affects Versions: v1_0_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > The *newt run* command currently skips the create image step if the user does > not provide a version number for the command. It would be useful to have the > command query the user for a version number and to let the user know that the > command will use default version 0 if one is not provided. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (MYNEWT-761) 1.1 Documentation needs to be updated for newtmgr "mpstats" and "taststats" command
[ https://issues.apache.org/jira/browse/MYNEWT-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu resolved MYNEWT-761. --- Resolution: Fixed > 1.1 Documentation needs to be updated for newtmgr "mpstats" and "taststats" > command > --- > > Key: MYNEWT-761 > URL: https://issues.apache.org/jira/browse/MYNEWT-761 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > *newtmgr mpstats* and *newtmgr taskstats* commands have been changed to > *newtmgr mpstat* and *newtmgr taskstat* (singular instead of plural) post > 1.0. The command guide and tutorials need to be updated to use the new > version for 1.1 documentation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-763) Add documentation for newt target append command
[ https://issues.apache.org/jira/browse/MYNEWT-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16029731#comment-16029731 ] Wanda Chiu commented on MYNEWT-763: --- Updates are here https://github.com/apache/incubator-mynewt-site/pull/191. Also the command is changed from newt target append to newt target amend. > Add documentation for newt target append command > > > Key: MYNEWT-763 > URL: https://issues.apache.org/jira/browse/MYNEWT-763 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to add documentation for *newt target append* command (MYNEWT-640) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MYNEWT-763) Add documentation for newt target amend command
[ https://issues.apache.org/jira/browse/MYNEWT-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu updated MYNEWT-763: -- Summary: Add documentation for newt target amend command (was: Add documentation for newt target append command) > Add documentation for newt target amend command > --- > > Key: MYNEWT-763 > URL: https://issues.apache.org/jira/browse/MYNEWT-763 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to add documentation for *newt target amend* command (MYNEWT-640) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MYNEWT-763) Add documentation for newt target append command
[ https://issues.apache.org/jira/browse/MYNEWT-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu updated MYNEWT-763: -- Description: Need to add documentation for *newt target amend* command (MYNEWT-640) (was: Need to add documentation for *newt target append* command (MYNEWT-640) ) > Add documentation for newt target append command > > > Key: MYNEWT-763 > URL: https://issues.apache.org/jira/browse/MYNEWT-763 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to add documentation for *newt target amend* command (MYNEWT-640) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-764) Update Doc for newt run command
[ https://issues.apache.org/jira/browse/MYNEWT-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16028779#comment-16028779 ] Wanda Chiu commented on MYNEWT-764: --- Doc updated in PR: https://github.com/apache/incubator-mynewt-site/pull/190 > Update Doc for newt run command > --- > > Key: MYNEWT-764 > URL: https://issues.apache.org/jira/browse/MYNEWT-764 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to document that *newt run* command now queries the user for a version > (or use default 0) the version is not provided for an application target, > instead of skipping the create-image step. (See MYNEWT-694) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (MYNEWT-649) "newt target set" allows random variable to be set; should allow only valid variable settings.
[ https://issues.apache.org/jira/browse/MYNEWT-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025702#comment-16025702 ] Wanda Chiu edited comment on MYNEWT-649 at 5/26/17 2:20 AM: Discussed with Aditi and decided newt vals command does not need to support variables: syscfg, loader, aflags, cflags, lflags. PR to validate the variables is: https://github.com/apache/incubator-mynewt-newt/pull/65. was (Author: cwanda): Discuss with Aditi and decided newt vals command does not need to support variables: syscfg, loader, aflags, cflags, lflags. PR to validate the variables is: https://github.com/apache/incubator-mynewt-newt/pull/65. > "newt target set" allows random variable to be set; should allow only valid > variable settings. > -- > > Key: MYNEWT-649 > URL: https://issues.apache.org/jira/browse/MYNEWT-649 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Aditi Hilbert >Assignee: Wanda Chiu > Fix For: v1_1_0_rel > > > The "newt target set" command should have a check for allowed settings. > For example, I can set the variable "bogus" with a value and target.bogus > will be added to the target.yml file. Do we have a list of all the valid > variables so we can add the validation to the command? What I have listed as > valid variables in the `newt target set" command documentation are: app, bsp, > loader, build_profile, cflags, aflags, lflags, syscfg. > We should make sure the "newt vals" command also covers this set of valid > target variables to make things consistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-649) "newt target set" allows random variable to be set; should allow only valid variable settings.
[ https://issues.apache.org/jira/browse/MYNEWT-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025702#comment-16025702 ] Wanda Chiu commented on MYNEWT-649: --- Discuss with Aditi and decided newt vals command does not need to support variables: syscfg, loader, aflags, cflags, lflags. PR to validate the variables is: https://github.com/apache/incubator-mynewt-newt/pull/65. > "newt target set" allows random variable to be set; should allow only valid > variable settings. > -- > > Key: MYNEWT-649 > URL: https://issues.apache.org/jira/browse/MYNEWT-649 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Aditi Hilbert >Assignee: Wanda Chiu > Fix For: v1_1_0_rel > > > The "newt target set" command should have a check for allowed settings. > For example, I can set the variable "bogus" with a value and target.bogus > will be added to the target.yml file. Do we have a list of all the valid > variables so we can add the validation to the command? What I have listed as > valid variables in the `newt target set" command documentation are: app, bsp, > loader, build_profile, cflags, aflags, lflags, syscfg. > We should make sure the "newt vals" command also covers this set of valid > target variables to make things consistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-640) Add an newt target "append" feature to change or append target variable values
[
https://issues.apache.org/jira/browse/MYNEWT-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025682#comment-16025682
]
Wanda Chiu commented on MYNEWT-640:
---
Closed the previous PR. Open this one:
https://github.com/apache/incubator-mynewt-newt/pull/64
Added the *newt target amend* command to add, change, or delete values for
multi-value target variables, such as syscfg, cflags etc. It supports the -d
flag to delete values.
This addresses concerns raised in MYNEWT-543
> Add an newt target "append" feature to change or append target variable
> values
> ---
>
> Key: MYNEWT-640
> URL: https://issues.apache.org/jira/browse/MYNEWT-640
> Project: Mynewt
> Issue Type: Improvement
> Security Level: Public(Viewable by anyone)
>Affects Versions: v1_0_0_beta2
>Reporter: Wanda Chiu
>Assignee: Wanda Chiu
>Priority: Minor
> Fix For: v1_1_0_rel
>
>
> This is a feature enhancement request (for post 1.0) to support an "append"
> feature that allows a user to change or append to current target variable
> values:
> The *newt target set* sets a variable value with the value
> specified in the command. It overrides the variable's previous values. For
> example, the eventq_nordic target has the follow syscfg.yml content:
> {code}
> ### Package: targets/eventq_nordic
> syscfg.vals:
> CONFIG_NEWTMGR: 1
> LOG_NEWTMGR: 1
> SHELL_TASK: 1
> {code}
> Run *newt target set eventq_nordic syscfg=LOG_NEWTMGR=0* and the syscfg.yml
> file changes to:
> {code}
> ### Package: targets/eventq_nordic
> syscfg.vals:
> LOG_NEWTMGR: 0
> {code}
> Currently users can't append or change specific values for a variable and
> without overriding all values. This support would be useful for target
> variables other than the *syscfg* variable, e.g *cflags*, *lflags*, etc
> (See MYNEWT-543)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (MYNEWT-764) Update Doc for newt run command
[ https://issues.apache.org/jira/browse/MYNEWT-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu reassigned MYNEWT-764: - Assignee: Wanda Chiu (was: Aditi Hilbert) > Update Doc for newt run command > --- > > Key: MYNEWT-764 > URL: https://issues.apache.org/jira/browse/MYNEWT-764 > Project: Mynewt > Issue Type: Task > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to document that *newt run* command now queries the user for a version > (or use default 0) the version is not provided for an application target, > instead of skipping the create-image step. (See MYNEWT-694) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-694) newt run command should query user for version number instead of skipping create image step
[ https://issues.apache.org/jira/browse/MYNEWT-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020644#comment-16020644 ] Wanda Chiu commented on MYNEWT-694: --- Fix in https://github.com/apache/incubator-mynewt-newt/pull/63. Command now asks the user for a version (or use the default value 0) when the target is an application target, instead of skipping the create image step. > newt run command should query user for version number instead of skipping > create image step > --- > > Key: MYNEWT-694 > URL: https://issues.apache.org/jira/browse/MYNEWT-694 > Project: Mynewt > Issue Type: Improvement > Components: Newt >Affects Versions: v1_0_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > The *newt run* command currently skips the create image step if the user does > not provide a version number for the command. It would be useful to have the > command query the user for a version number and to let the user know that the > command will use default version 0 if one is not provided. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MYNEWT-764) Update Doc for newt run command
Wanda Chiu created MYNEWT-764: - Summary: Update Doc for newt run command Key: MYNEWT-764 URL: https://issues.apache.org/jira/browse/MYNEWT-764 Project: Mynewt Issue Type: Task Components: Documentation Affects Versions: v1_1_0_rel Reporter: Wanda Chiu Assignee: Aditi Hilbert Priority: Minor Fix For: v1_1_0_rel Need to document that *newt run* command now queries the user for a version (or use default 0) the version is not provided for an application target, instead of skipping the create-image step. (See MYNEWT-694) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (MYNEWT-693) newtmgr conn add command needs better error checking
[
https://issues.apache.org/jira/browse/MYNEWT-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wanda Chiu resolved MYNEWT-693.
---
Resolution: Fixed
> newtmgr conn add command needs better error checking
>
>
> Key: MYNEWT-693
> URL: https://issues.apache.org/jira/browse/MYNEWT-693
> Project: Mynewt
> Issue Type: Bug
> Components: Newtmgr
>Affects Versions: v1_0_0_rel
>Reporter: Wanda Chiu
>Assignee: Wanda Chiu
>Priority: Minor
> Fix For: v1_1_0_rel
>
>
> The *newtmgr conn add* command currently only checks that the user provides a
> connection profile name for a command argument. It does not require the user
> to specify arguments such as *type* and *connstring*. For example:
> {code}
> newtmgr conn add myprofile
> Connection profile myprofile successfully added
> {code}
> The command needs better error checking and , minimally, should require the
> user to specify the *type* and *connstring* arguments.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (MYNEWT-694) newt run command should query user for version number instead of skipping create image step
[ https://issues.apache.org/jira/browse/MYNEWT-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu reassigned MYNEWT-694: - Assignee: Wanda Chiu > newt run command should query user for version number instead of skipping > create image step > --- > > Key: MYNEWT-694 > URL: https://issues.apache.org/jira/browse/MYNEWT-694 > Project: Mynewt > Issue Type: Improvement > Components: Newt >Affects Versions: v1_0_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > The *newt run* command currently skips the create image step if the user does > not provide a version number for the command. It would be useful to have the > command query the user for a version number and to let the user know that the > command will use default version 0 if one is not provided. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-649) "newt target set" allows random variable to be set; should allow only valid variable settings.
[ https://issues.apache.org/jira/browse/MYNEWT-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020272#comment-16020272 ] Wanda Chiu commented on MYNEWT-649: --- Need some clarifications: 1) Valid variables for newt target set are: app, bsp, loader, build_profile, cflags, lflags, aflags, syscfg. Are there other variables that *newt target set* can set? 2) In regard to making sure that the "newt vals" command also covers this set of valid target variables, I want to discuss the desire behavior before adding a bunch of code that might not be needed. Currently the *newt vals* command shows values for the following variables: *api, app, bsp, build_profile, compiler, lib, sdk, target*, and does not show values for *syscfg, loader, aflags, cflags, lflags*. I am not sure whether we need to or we can include values for all these variables. Here are the reasons: * syscfg - user can use newt target config show to see all the values. Do we need to show with *newt vals*? * loader - There isn't a way to desginate that an app can be either an app or a loader. All apps have pkg.type=app. To designate that an app can be either a loader or an app, we will probably need to add another field such as pkg.loader=true * aflags, cflags, and lflags - I am not sure how useful it would be to print these values out? I guess it could be useful to print out the values for each compiler so the user will know if they need to add more aflags, cflags, and lflags for their target. If we decide to print out the values, I am thinking: ** For aflags and lflags: We would printout the flags for each compiler. ** For cflags: We would printout the flags used for the each build profile :base, default, optimized, and debug and for each compiler. > "newt target set" allows random variable to be set; should allow only valid > variable settings. > -- > > Key: MYNEWT-649 > URL: https://issues.apache.org/jira/browse/MYNEWT-649 > Project: Mynewt > Issue Type: Bug >Reporter: Aditi Hilbert >Assignee: Wanda Chiu > Fix For: v1_1_0_rel > > > The "newt target set" command should have a check for allowed settings. > For example, I can set the variable "bogus" with a value and target.bogus > will be added to the target.yml file. Do we have a list of all the valid > variables so we can add the validation to the command? What I have listed as > valid variables in the `newt target set" command documentation are: app, bsp, > loader, build_profile, cflags, aflags, lflags, syscfg. > We should make sure the "newt vals" command also covers this set of valid > target variables to make things consistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MYNEWT-763) Add documentation for newt target append command
Wanda Chiu created MYNEWT-763: - Summary: Add documentation for newt target append command Key: MYNEWT-763 URL: https://issues.apache.org/jira/browse/MYNEWT-763 Project: Mynewt Issue Type: Task Components: Documentation Affects Versions: v1_1_0_rel Reporter: Wanda Chiu Assignee: Wanda Chiu Priority: Minor Fix For: v1_1_0_rel Need to add documentation for *newt target append* command (MYNEWT-640) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-640) Add an newt target "append" feature to change or append target variable values
[
https://issues.apache.org/jira/browse/MYNEWT-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019683#comment-16019683
]
Wanda Chiu commented on MYNEWT-640:
---
Support added in https://github.com/apache/incubator-mynewt-newt/pull/61.
Please see discussion on how we might want to handle "deleting" a value.
> Add an newt target "append" feature to change or append target variable
> values
> ---
>
> Key: MYNEWT-640
> URL: https://issues.apache.org/jira/browse/MYNEWT-640
> Project: Mynewt
> Issue Type: Improvement
>Affects Versions: v1_0_0_beta2
>Reporter: Wanda Chiu
>Assignee: Wanda Chiu
>Priority: Minor
> Fix For: v1_1_0_rel
>
>
> This is a feature enhancement request (for post 1.0) to support an "append"
> feature that allows a user to change or append to current target variable
> values:
> The *newt target set* sets a variable value with the value
> specified in the command. It overrides the variable's previous values. For
> example, the eventq_nordic target has the follow syscfg.yml content:
> {code}
> ### Package: targets/eventq_nordic
> syscfg.vals:
> CONFIG_NEWTMGR: 1
> LOG_NEWTMGR: 1
> SHELL_TASK: 1
> {code}
> Run *newt target set eventq_nordic syscfg=LOG_NEWTMGR=0* and the syscfg.yml
> file changes to:
> {code}
> ### Package: targets/eventq_nordic
> syscfg.vals:
> LOG_NEWTMGR: 0
> {code}
> Currently users can't append or change specific values for a variable and
> without overriding all values. This support would be useful for target
> variables other than the *syscfg* variable, e.g *cflags*, *lflags*, etc
> (See MYNEWT-543)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (MYNEWT-693) newtmgr conn add command needs better error checking
[
https://issues.apache.org/jira/browse/MYNEWT-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019570#comment-16019570
]
Wanda Chiu edited comment on MYNEWT-693 at 5/22/17 1:29 PM:
Fix in https://github.com/apache/incubator-mynewt-newtmgr/pull/1.
It looks like the additional **addr** and *addrtype** parameters for type ble
are no longer valid parameters for the command in 1.1. Opened MYNEWT-762 to
update this in the command guide for 1.1 documentation.
was (Author: cwanda):
Fix in https://github.com/apache/incubator-mynewt-newtmgr/pull/1.
It looks like the additional **addr** and *addrtype** parameters for type ble
are longer valid parameters for the command in 1.1. Opened MYNEWT-762 to
update this in the command guide for 1.1 documentation.
> newtmgr conn add command needs better error checking
>
>
> Key: MYNEWT-693
> URL: https://issues.apache.org/jira/browse/MYNEWT-693
> Project: Mynewt
> Issue Type: Bug
> Components: Newtmgr
>Affects Versions: v1_0_0_rel
>Reporter: Wanda Chiu
>Assignee: Wanda Chiu
>Priority: Minor
> Fix For: v1_1_0_rel
>
>
> The *newtmgr conn add* command currently only checks that the user provides a
> connection profile name for a command argument. It does not require the user
> to specify arguments such as *type* and *connstring*. For example:
> {code}
> newtmgr conn add myprofile
> Connection profile myprofile successfully added
> {code}
> The command needs better error checking and , minimally, should require the
> user to specify the *type* and *connstring* arguments.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (MYNEWT-693) newtmgr conn add command needs better error checking
[
https://issues.apache.org/jira/browse/MYNEWT-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019570#comment-16019570
]
Wanda Chiu edited comment on MYNEWT-693 at 5/22/17 1:28 PM:
Fix in https://github.com/apache/incubator-mynewt-newtmgr/pull/1.
It looks like the additional **addr** and *addrtype** parameters for type ble
are longer valid parameters for the command in 1.1. Opened MYNEWT-762 to
update this in the command guide for 1.1 documentation.
was (Author: cwanda):
Fix in https://github.com/apache/incubator-mynewt-newtmgr/pull/1.
It looks like the additional **addr** and *addrtype** for type ble are longer
valid parameters for the command. Opened MYNEWT-762 to track this.
> newtmgr conn add command needs better error checking
>
>
> Key: MYNEWT-693
> URL: https://issues.apache.org/jira/browse/MYNEWT-693
> Project: Mynewt
> Issue Type: Bug
> Components: Newtmgr
>Affects Versions: v1_0_0_rel
>Reporter: Wanda Chiu
>Assignee: Wanda Chiu
>Priority: Minor
> Fix For: v1_1_0_rel
>
>
> The *newtmgr conn add* command currently only checks that the user provides a
> connection profile name for a command argument. It does not require the user
> to specify arguments such as *type* and *connstring*. For example:
> {code}
> newtmgr conn add myprofile
> Connection profile myprofile successfully added
> {code}
> The command needs better error checking and , minimally, should require the
> user to specify the *type* and *connstring* arguments.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MYNEWT-762) addr and addrtype are no longer valid parameters for newtmgr conn add
[ https://issues.apache.org/jira/browse/MYNEWT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu updated MYNEWT-762: -- Description: Need to update 1.1 documentation for **newtmgr conn add** and remove **addr** and **addrtype** as valid parameters. (was: Need to update newtmgr conn add command documentation and remove **addr** and **addrtype** as valid parameters. ) > addr and addrtype are no longer valid parameters for newtmgr conn add > - > > Key: MYNEWT-762 > URL: https://issues.apache.org/jira/browse/MYNEWT-762 > Project: Mynewt > Issue Type: Task > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to update 1.1 documentation for **newtmgr conn add** and remove > **addr** and **addrtype** as valid parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (MYNEWT-762) addr and addrtype are no longer valid parameters for newtmgr conn add
[ https://issues.apache.org/jira/browse/MYNEWT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu reassigned MYNEWT-762: - Assignee: Wanda Chiu (was: Aditi Hilbert) > addr and addrtype are no longer valid parameters for newtmgr conn add > - > > Key: MYNEWT-762 > URL: https://issues.apache.org/jira/browse/MYNEWT-762 > Project: Mynewt > Issue Type: Task > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to update newtmgr conn add command documentation and remove **addr** and > **addrtype** as valid parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-693) newtmgr conn add command needs better error checking
[
https://issues.apache.org/jira/browse/MYNEWT-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019570#comment-16019570
]
Wanda Chiu commented on MYNEWT-693:
---
Fix in https://github.com/apache/incubator-mynewt-newtmgr/pull/1.
It looks like the additional **addr** and *addrtype** for type ble are longer
valid parameters for the command. Opened MYNEWT-762 to track this.
> newtmgr conn add command needs better error checking
>
>
> Key: MYNEWT-693
> URL: https://issues.apache.org/jira/browse/MYNEWT-693
> Project: Mynewt
> Issue Type: Bug
> Components: Newtmgr
>Affects Versions: v1_0_0_rel
>Reporter: Wanda Chiu
>Assignee: Wanda Chiu
>Priority: Minor
> Fix For: v1_1_0_rel
>
>
> The *newtmgr conn add* command currently only checks that the user provides a
> connection profile name for a command argument. It does not require the user
> to specify arguments such as *type* and *connstring*. For example:
> {code}
> newtmgr conn add myprofile
> Connection profile myprofile successfully added
> {code}
> The command needs better error checking and , minimally, should require the
> user to specify the *type* and *connstring* arguments.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (MYNEWT-762) addr and addrtype are no longer valid parameters for newtmgr conn add
Wanda Chiu created MYNEWT-762: - Summary: addr and addrtype are no longer valid parameters for newtmgr conn add Key: MYNEWT-762 URL: https://issues.apache.org/jira/browse/MYNEWT-762 Project: Mynewt Issue Type: Task Components: Documentation Affects Versions: v1_1_0_rel Reporter: Wanda Chiu Assignee: Aditi Hilbert Priority: Minor Fix For: v1_1_0_rel Need to update newtmgr conn add command documentation and remove **addr** and **addrtype** as valid parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MYNEWT-640) Add an newt target "append" feature to change or append target variable values
[
https://issues.apache.org/jira/browse/MYNEWT-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wanda Chiu updated MYNEWT-640:
--
Fix Version/s: v1_1_0_rel
> Add an newt target "append" feature to change or append target variable
> values
> ---
>
> Key: MYNEWT-640
> URL: https://issues.apache.org/jira/browse/MYNEWT-640
> Project: Mynewt
> Issue Type: Improvement
>Affects Versions: v1_0_0_beta2
>Reporter: Wanda Chiu
>Assignee: Wanda Chiu
>Priority: Minor
> Fix For: v1_1_0_rel
>
>
> This is a feature enhancement request (for post 1.0) to support an "append"
> feature that allows a user to change or append to current target variable
> values:
> The *newt target set* sets a variable value with the value
> specified in the command. It overrides the variable's previous values. For
> example, the eventq_nordic target has the follow syscfg.yml content:
> {code}
> ### Package: targets/eventq_nordic
> syscfg.vals:
> CONFIG_NEWTMGR: 1
> LOG_NEWTMGR: 1
> SHELL_TASK: 1
> {code}
> Run *newt target set eventq_nordic syscfg=LOG_NEWTMGR=0* and the syscfg.yml
> file changes to:
> {code}
> ### Package: targets/eventq_nordic
> syscfg.vals:
> LOG_NEWTMGR: 0
> {code}
> Currently users can't append or change specific values for a variable and
> without overriding all values. This support would be useful for target
> variables other than the *syscfg* variable, e.g *cflags*, *lflags*, etc
> (See MYNEWT-543)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (MYNEWT-640) Add an newt target "append" feature to change or append target variable values
[
https://issues.apache.org/jira/browse/MYNEWT-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wanda Chiu reassigned MYNEWT-640:
-
Assignee: Wanda Chiu
> Add an newt target "append" feature to change or append target variable
> values
> ---
>
> Key: MYNEWT-640
> URL: https://issues.apache.org/jira/browse/MYNEWT-640
> Project: Mynewt
> Issue Type: Improvement
>Affects Versions: v1_0_0_beta2
>Reporter: Wanda Chiu
>Assignee: Wanda Chiu
>Priority: Minor
> Fix For: v1_1_0_rel
>
>
> This is a feature enhancement request (for post 1.0) to support an "append"
> feature that allows a user to change or append to current target variable
> values:
> The *newt target set* sets a variable value with the value
> specified in the command. It overrides the variable's previous values. For
> example, the eventq_nordic target has the follow syscfg.yml content:
> {code}
> ### Package: targets/eventq_nordic
> syscfg.vals:
> CONFIG_NEWTMGR: 1
> LOG_NEWTMGR: 1
> SHELL_TASK: 1
> {code}
> Run *newt target set eventq_nordic syscfg=LOG_NEWTMGR=0* and the syscfg.yml
> file changes to:
> {code}
> ### Package: targets/eventq_nordic
> syscfg.vals:
> LOG_NEWTMGR: 0
> {code}
> Currently users can't append or change specific values for a variable and
> without overriding all values. This support would be useful for target
> variables other than the *syscfg* variable, e.g *cflags*, *lflags*, etc
> (See MYNEWT-543)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (MYNEWT-761) 1.1 Documentation needs to be updated for newtmgr "mpstats" and "taststats" command
Wanda Chiu created MYNEWT-761: - Summary: 1.1 Documentation needs to be updated for newtmgr "mpstats" and "taststats" command Key: MYNEWT-761 URL: https://issues.apache.org/jira/browse/MYNEWT-761 Project: Mynewt Issue Type: Task Components: Documentation Reporter: Wanda Chiu Assignee: Wanda Chiu Priority: Minor Fix For: v1_1_0_rel *newtmgr mpstats* and *newtmgr taskstats* commands have been changed to *newtmgr mpstat* and *newtmgr taskstat* (singular instead of plural) post 1.0. The command guide and tutorials need to be updated to use the new version for 1.1 documentation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-695) Arduino Zero with Wifi Shield 101 failing on wifi start
[
https://issues.apache.org/jira/browse/MYNEWT-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008608#comment-16008608
]
Wanda Chiu commented on MYNEWT-695:
---
Note that the
tutorial:https://mynewt.apache.org/latest/os/tutorials/wi-fi_on_arduino/ has
been updated to use the arduino_mk1000 wifi instead of the arduino wifi shield
instead of the arduino wifi shield. The tutorial for the arduino_mk1000 works.
> Arduino Zero with Wifi Shield 101 failing on wifi start
> ---
>
> Key: MYNEWT-695
> URL: https://issues.apache.org/jira/browse/MYNEWT-695
> Project: Mynewt
> Issue Type: Bug
> Components: BSP
>Affects Versions: v1_0_0_rel
>Reporter: Wanda Chiu
>Assignee: William San Filippo
> Fix For: v1_1_0_rel
>
> Attachments: zero.patch
>
>
> *wifi start* is failing when using arduino zero with arduino Wifi Shield 101
> (See steps in tutorial:
> https://mynewt.apache.org/latest/os/tutorials/wi-fi_on_arduino/)
> {code}
> wifi start
> wifi_init : -6
>
> 151416:(APP)(ERR)[nm_drv_init][293][nmi start]: fail init bus
> ...
> {code}
> Marko looked into this and found that hw/bsp/arduino_zero/syscfg.yml is
> missing the following sysconfig definitions (see attached zero.patch).:
>
> * *SPI_2*,
> * *SPI_2_TYPE*,
> * *SPI_3*
> * *SPI_3_TYPE*
> Applying the attached zero.patch fixes the *wifi_init:-6* error, but
> wifi_init seems to hang after that.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (MYNEWT-724) mynewt, build on ubuntu
[ https://issues.apache.org/jira/browse/MYNEWT-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008542#comment-16008542 ] Wanda Chiu edited comment on MYNEWT-724 at 5/12/17 7:06 PM: We have added a note in the installation instructions that newt 1.0.0 does not build on 32 bit platforms. Please see bug: MYNEWT-718 and the fix: https://github.com/apache/incubator-mynewt-newt/commit/409f7d307fb09d22a529891cfb3efd21123e0d57. You should be able to apply the patch to the 1.0.0 source. was (Author: cwanda): This is a known bug in newt 1.0.0. It has been documented in the installation instructions that newt 1.0.0 does not build on 32 bit platform. Please see bug: MYNEWT-718 and the fix: https://github.com/apache/incubator-mynewt-newt/commit/409f7d307fb09d22a529891cfb3efd21123e0d57. You should be able to apply the match to the 1.0.0 source. > mynewt, build on ubuntu > --- > > Key: MYNEWT-724 > URL: https://issues.apache.org/jira/browse/MYNEWT-724 > Project: Mynewt > Issue Type: Bug >Affects Versions: v1_0_0_rel > Environment: Linux Version: > lsb_release -a > Distributor ID: Ubuntu > Description: Ubuntu 14.04.4 LTS > Release: 14.04 > Codename: trusty > Go version: > go version > go version go1.7 linux/386 >Reporter: Filipe >Assignee: Wanda Chiu >Priority: Minor > > when building the mynewt on ubuntu I have an error on go builder: > syscfg/syscfg.go:965: constant 4294967295 overflows int > Seems that the SYSCFG_INTERRUPT_PRIO_MAX is too big for the variable "int" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-724) mynewt, build on ubuntu
[ https://issues.apache.org/jira/browse/MYNEWT-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008542#comment-16008542 ] Wanda Chiu commented on MYNEWT-724: --- This is a known bug in newt 1.0.0. It has been documented in the installation instructions that newt 1.0.0 does not build on 32 bit platform. Please see bug: MYNEWT-718 and the fix: https://github.com/apache/incubator-mynewt-newt/commit/409f7d307fb09d22a529891cfb3efd21123e0d57. You should be able to apply the match to the 1.0.0 source. > mynewt, build on ubuntu > --- > > Key: MYNEWT-724 > URL: https://issues.apache.org/jira/browse/MYNEWT-724 > Project: Mynewt > Issue Type: Bug >Affects Versions: v1_0_0_rel > Environment: Linux Version: > lsb_release -a > Distributor ID: Ubuntu > Description: Ubuntu 14.04.4 LTS > Release: 14.04 > Codename: trusty > Go version: > go version > go version go1.7 linux/386 >Reporter: Filipe >Assignee: Wanda Chiu >Priority: Minor > > when building the mynewt on ubuntu I have an error on go builder: > syscfg/syscfg.go:965: constant 4294967295 overflows int > Seems that the SYSCFG_INTERRUPT_PRIO_MAX is too big for the variable "int" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MYNEWT-719) Newtmgr fails to build on 32 bit for Mac OS
Wanda Chiu created MYNEWT-719:
-
Summary: Newtmgr fails to build on 32 bit for Mac OS
Key: MYNEWT-719
URL: https://issues.apache.org/jira/browse/MYNEWT-719
Project: Mynewt
Issue Type: Bug
Affects Versions: v1_1_0_rel
Environment: Mac OS
Reporter: Wanda Chiu
Go cross compile of Newtmgr fails to build for Mac OS/32 bit. Set GOARCH=386
and build on Mac OS (GOOS can take on default or set to darwin).
Note: Newtmgr builds successfully for Linux 32 bits(GOOS=Linux GOARCH=386).
The build has the following errors on vendor code:
{code}
mynewt.apache.org/newt/newtmgr/vendor/github.com/tarm/serial
vendor/github.com/tarm/serial/serial.go:128: undefined: Port
vendor/github.com/tarm/serial/serial.go:139: undefined: openPort
# mynewt.apache.org/newt/newtmgr/vendor/github.com/runtimeco/gatt
vendor/github.com/runtimeco/gatt/device_darwin.go:35: undefined: xpc.XPC
vendor/github.com/runtimeco/gatt/peripheral_darwin.go:222: undefined: xpc.Dict
vendor/github.com/runtimeco/gatt/peripheral_darwin.go:223: undefined: xpc.Dict
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MYNEWT-695) Arduino Zero with Wifi Shield 101 failing on wifi start
[
https://issues.apache.org/jira/browse/MYNEWT-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wanda Chiu updated MYNEWT-695:
--
Description:
*wifi start* is failing when using arduino zero with arduino Wifi Shield 101
(See steps in tutorial:
https://mynewt.apache.org/latest/os/tutorials/wi-fi_on_arduino/)
{code}
wifi start
wifi_init : -6
151416:(APP)(ERR)[nm_drv_init][293][nmi start]: fail init bus
...
{code}
Marko looked into this and found that hw/bsp/arduino_zero/syscfg.yml is
missing the following sysconfig definitions (see attached zero.patch).:
* *SPI_2*,
* *SPI_2_TYPE*,
* *SPI_3*
* *SPI_3_TYPE*
Applying the attached zero.patch fixes the *wifi_init:-6* error, but wifi_init
seems to hang after that.
was:
*wifi start* is failing when using arduino zero with arduino Wifi Shield 101
(See steps in tutorial:
https://mynewt.apache.org/latest/os/tutorials/wi-fi_on_arduino/
{code}
wifi start
wifi_init : -6
151416:(APP)(ERR)[nm_drv_init][293][nmi start]: fail init bus
...
{code}
Marko looked into this and found that hw/bsp/arduino_zero/syscfg.yml is
missing the following sysconfig definitions (see attached zero.patch).:
* *SPI_2*,
* *SPI_2_TYPE*,
* *SPI_3*
* *SPI_3_TYPE*
Applying the attached zero.patch fixes the *wifi_init:-6* error, but wifi_init
seems to hang after that.
> Arduino Zero with Wifi Shield 101 failing on wifi start
> ---
>
> Key: MYNEWT-695
> URL: https://issues.apache.org/jira/browse/MYNEWT-695
> Project: Mynewt
> Issue Type: Bug
> Components: BSP
>Affects Versions: v1_0_0_rel
>Reporter: Wanda Chiu
>Assignee: William San Filippo
> Attachments: zero.patch
>
>
> *wifi start* is failing when using arduino zero with arduino Wifi Shield 101
> (See steps in tutorial:
> https://mynewt.apache.org/latest/os/tutorials/wi-fi_on_arduino/)
> {code}
> wifi start
> wifi_init : -6
>
> 151416:(APP)(ERR)[nm_drv_init][293][nmi start]: fail init bus
> ...
> {code}
> Marko looked into this and found that hw/bsp/arduino_zero/syscfg.yml is
> missing the following sysconfig definitions (see attached zero.patch).:
>
> * *SPI_2*,
> * *SPI_2_TYPE*,
> * *SPI_3*
> * *SPI_3_TYPE*
> Applying the attached zero.patch fixes the *wifi_init:-6* error, but
> wifi_init seems to hang after that.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (MYNEWT-695) Arduino Zero with Wifi Shield 101 failing on wifi start
Wanda Chiu created MYNEWT-695:
-
Summary: Arduino Zero with Wifi Shield 101 failing on wifi start
Key: MYNEWT-695
URL: https://issues.apache.org/jira/browse/MYNEWT-695
Project: Mynewt
Issue Type: Bug
Components: BSP
Affects Versions: v1_0_0_rel
Reporter: Wanda Chiu
Assignee: William San Filippo
Attachments: zero.patch
*wifi start* is failing when using arduino zero with arduino Wifi Shield 101
(See steps in tutorial:
https://mynewt.apache.org/latest/os/tutorials/wi-fi_on_arduino/
{code}
wifi start
wifi_init : -6
151416:(APP)(ERR)[nm_drv_init][293][nmi start]: fail init bus
...
{code}
Marko looked into this and found that hw/bsp/arduino_zero/syscfg.yml is
missing the following sysconfig definitions (see attached zero.patch).:
* *SPI_2*,
* *SPI_2_TYPE*,
* *SPI_3*
* *SPI_3_TYPE*
Applying the attached zero.patch fixes the *wifi_init:-6* error, but wifi_init
seems to hang after that.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (MYNEWT-694) newt run command should query user for version number instead of skipping create image step
Wanda Chiu created MYNEWT-694: - Summary: newt run command should query user for version number instead of skipping create image step Key: MYNEWT-694 URL: https://issues.apache.org/jira/browse/MYNEWT-694 Project: Mynewt Issue Type: Improvement Components: Newt Affects Versions: v1_0_0_rel Reporter: Wanda Chiu Priority: Minor Fix For: v1_1_0_rel The *newt run* command currently skips the create image step if the user does not provide a version number for the command. It would be useful to have the command query the user for a version number and to let the user know that the command will use default version 0 if one is not provided. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (MYNEWT-693) newtmgr conn add command needs better error checking
[
https://issues.apache.org/jira/browse/MYNEWT-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wanda Chiu reassigned MYNEWT-693:
-
Assignee: Wanda Chiu (was: Sterling Hughes)
> newtmgr conn add command needs better error checking
>
>
> Key: MYNEWT-693
> URL: https://issues.apache.org/jira/browse/MYNEWT-693
> Project: Mynewt
> Issue Type: Bug
> Components: Newtmgr
>Affects Versions: v1_0_0_rel
>Reporter: Wanda Chiu
>Assignee: Wanda Chiu
>Priority: Minor
> Fix For: v1_1_0_rel
>
>
> The *newtmgr conn add* command currently only checks that the user provides a
> connection profile name for a command argument. It does not require the user
> to specify arguments such as *type* and *connstring*. For example:
> {code}
> newtmgr conn add myprofile
> Connection profile myprofile successfully added
> {code}
> The command needs better error checking and , minimally, should require the
> user to specify the *type* and *connstring* arguments.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (MYNEWT-693) newtmgr conn add command needs better error checking
Wanda Chiu created MYNEWT-693:
-
Summary: newtmgr conn add command needs better error checking
Key: MYNEWT-693
URL: https://issues.apache.org/jira/browse/MYNEWT-693
Project: Mynewt
Issue Type: Bug
Components: Newtmgr
Affects Versions: v1_0_0_rel
Reporter: Wanda Chiu
Assignee: Sterling Hughes
Priority: Minor
Fix For: v1_1_0_rel
The *newtmgr conn add* command currently only checks that the user provides a
connection profile name for a command argument. It does not require the user to
specify arguments such as *type* and *connstring*. For example:
{code}
newtmgr conn add myprofile
Connection profile myprofile successfully added
{code}
The command needs better error checking and , minimally, should require the
user to specify the *type* and *connstring* arguments.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (MYNEWT-639) newt pkg new command does not error check or show in help text that package location is needed as an argument.
[
https://issues.apache.org/jira/browse/MYNEWT-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wanda Chiu closed MYNEWT-639.
-
PR merged
> newt pkg new command does not error check or show in help text that package
> location is needed as an argument.
> --
>
> Key: MYNEWT-639
> URL: https://issues.apache.org/jira/browse/MYNEWT-639
> Project: Mynewt
> Issue Type: Bug
> Components: Newt
>Affects Versions: v1_0_0_beta2
>Reporter: Wanda Chiu
>Assignee: Wanda Chiu
>Priority: Minor
> Fix For: v1_0_0_rel
>
>
> 1) The current "newt pkg new" command help text does not indicate package
> location as an input parameter:
> {code}
> newt pkg new -h
> Create a new package, from a template
> Usage:
> newt pkg new [flags]
> Flags:
> -t, --type string Type of package to create: pkg, bsp, sdk. Default pkg.
> (default "pkg")
> {code}
> 2) The command does not error check whether the location is specified and
> assumes one is provided. " newt pkg new" causes a go runtime error.
> {code}
> panic: runtime error: index out of range
> goroutine 1 [running]:
> panic(0x40edc0, 0xc4200120d0)
> /usr/local/Cellar/go/1.7.4_2/libexec/src/runtime/panic.go:500 +0x1a1
> mynewt.apache.org/newt/newt/cli.pkgNewCmd(0xc42014eb40, 0x6aa9a8, 0x0, 0x0)
>
> /Users/wanda/mydev/go/src/mynewt.apache.org/newt/newt/cli/pkg_cmds.go:43
> +0x125
> mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra.(*Command).execute(0xc42014eb40,
> 0x6aa9a8, 0x0, 0x0, 0xc42014eb40, 0x6aa9a8)
>
> /Users/wanda/mydev/go/src/mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra/command.go:636
> +0x443
> mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xc4200a1200,
> 0x, 0x3, 0x47cc01)
>
> /Users/wanda/mydev/go/src/mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra/command.go:722
> +0x367
> mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra.(*Command).Execute(0xc4200a1200,
> 0x47cc01, 0x3)
>
> /Users/wanda/mydev/go/src/mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra/command.go:681
> +0x2b
> main.main()
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MYNEWT-293) Newt should make it easier to make custom packages
[ https://issues.apache.org/jira/browse/MYNEWT-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15887455#comment-15887455 ] Wanda Chiu commented on MYNEWT-293: --- Saw that Sterling agreed with the change from clone to copy, so I made the change in this PR:https://github.com/apache/incubator-mynewt-newt/pull/42, along with some newt help changes. The document has been updated as well. > Newt should make it easier to make custom packages > -- > > Key: MYNEWT-293 > URL: https://issues.apache.org/jira/browse/MYNEWT-293 > Project: Mynewt > Issue Type: Improvement > Components: Newt >Affects Versions: v1_0_0_beta1 >Reporter: Sterling Hughes >Assignee: Fabio Utzig > Fix For: v1_0_0_rel > > > There are a few issues with current newt package creation: > - It's opaque as to how to create a local package in a project. > - Need to add two options: > - newt pkg new : create a new package in the current directory, > with a basic template > - newt pkg clone : Clone an existing package > into the currnet directory. > - Currently, there must be an exact match on repository descriptor, or the > newt tool will barf. This should be smarter -- > - If it can't resolve a dependency in the local project, it should look at > the current project/workspace, and try to resolve the package > - It should issue a warning if it can't find the package. > - Currently pkg.name and the name of the package directory can not match, and > the pkg.name will be taken over the pkg directory. There should be a warning > issued if the package directory does not match the package name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-543) setting sys cfg values via newt erases old settings
[ https://issues.apache.org/jira/browse/MYNEWT-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15886140#comment-15886140 ] Wanda Chiu commented on MYNEWT-543: --- Hi david, I agree with your usage pattern and understand that the syscfg works differently than the other variables because of the multiple configuration settings. Originally, I had a PR with changes that would allow user to set syscfg variable with settings and not erase the other setting value. We ( Chris, Aditi, and I) discuss this and decided that it might be useful to extend this functionality for other variables (cflags etc) with an "append" enhancement feature (MYNEWT-640) for post release 1.0 since we are so close to the release. Perhaps we can re-open the PR to get this fix in for now? > setting sys cfg values via newt erases old settings > --- > > Key: MYNEWT-543 > URL: https://issues.apache.org/jira/browse/MYNEWT-543 > Project: Mynewt > Issue Type: Bug > Components: Newt >Affects Versions: v1_0_0_beta1 > Environment: Mac OS X >Reporter: David G. Simmons >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_0_0_rel > > > DSimmons-Pro:myproj dsimmons$ cat targets/air_q/syscfg.yml > \### Package: targets/air_q > syscfg.vals: > OPENOCD_DEBUG: 1 > \# Enable the shell task. > SHELL_TASK: 1 > STATS_CLI: 1 > CONSOLE_TICKS: 1 > CONSOLE_PROMPT: 1 > DSimmons-Pro:myproj dsimmons$ newt target set air_q syscfg=OPENOCD_DEBUG=0 > Target targets/air_q successfully set target.syscfg to OPENOCD_DEBUG=0 > DSimmons-Pro:myproj dsimmons$ cat targets/air_q/syscfg.yml > \### Package: targets/air_q > syscfg.vals: > OPENOCD_DEBUG: 0 > DSimmons-Pro:myproj dsimmons$ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-543) setting sys cfg values via newt erases old settings
[ https://issues.apache.org/jira/browse/MYNEWT-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884285#comment-15884285 ] Wanda Chiu commented on MYNEWT-543: --- Hi David, The behavior that you report is expected behavior and consistent with how all the other target variables are set. That is, the set command overrides the previous variable values. The set command is meant for an user to quickly set up a target with some values. We recognize that it would be useful for users to change some variable settings without overriding all values, and have a feature enhancement JIRA for this (MYNEWT-640). We will update the documentation (and help text) to indicate that the *newt target set * command will override the previous variable values. For now, the workaround is to use the "newt target set" command to create a target syscfg.yml file with some initial setting values for your target, and then edit the target syscfg.yml to change or add setting values. > setting sys cfg values via newt erases old settings > --- > > Key: MYNEWT-543 > URL: https://issues.apache.org/jira/browse/MYNEWT-543 > Project: Mynewt > Issue Type: Bug > Components: Newt >Affects Versions: v1_0_0_beta1 > Environment: Mac OS X >Reporter: David G. Simmons >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_0_0_rel > > > DSimmons-Pro:myproj dsimmons$ cat targets/air_q/syscfg.yml > \### Package: targets/air_q > syscfg.vals: > OPENOCD_DEBUG: 1 > \# Enable the shell task. > SHELL_TASK: 1 > STATS_CLI: 1 > CONSOLE_TICKS: 1 > CONSOLE_PROMPT: 1 > DSimmons-Pro:myproj dsimmons$ newt target set air_q syscfg=OPENOCD_DEBUG=0 > Target targets/air_q successfully set target.syscfg to OPENOCD_DEBUG=0 > DSimmons-Pro:myproj dsimmons$ cat targets/air_q/syscfg.yml > \### Package: targets/air_q > syscfg.vals: > OPENOCD_DEBUG: 0 > DSimmons-Pro:myproj dsimmons$ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MYNEWT-640) Add an newt target "append" feature to change or append target variable values
Wanda Chiu created MYNEWT-640:
-
Summary: Add an newt target "append" feature to change or append
target variable values
Key: MYNEWT-640
URL: https://issues.apache.org/jira/browse/MYNEWT-640
Project: Mynewt
Issue Type: Improvement
Affects Versions: v1_0_0_beta2
Reporter: Wanda Chiu
Priority: Minor
This is a feature enhancement request (for post 1.0) to support an "append"
feature that allows a user to change or append to current target variable
values:
The *newt target set* sets a variable value with the value
specified in the command. It overrides the variable's previous values. For
example, the eventq_nordic target has the follow syscfg.yml content:
{code}
### Package: targets/eventq_nordic
syscfg.vals:
CONFIG_NEWTMGR: 1
LOG_NEWTMGR: 1
SHELL_TASK: 1
{code}
Run *newt target set eventq_nordic syscfg=LOG_NEWTMGR=0* and the syscfg.yml
file changes to:
{code}
### Package: targets/eventq_nordic
syscfg.vals:
LOG_NEWTMGR: 0
{code}
Currently users can't append or change specific values for a variable and
without overriding all values. This support would be useful for target
variables other than the *syscfg* variable, e.g *cflags*, *lflags*, etc
(See MYNEWT-543)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MYNEWT-543) setting sys cfg values via newt erases old settings
[ https://issues.apache.org/jira/browse/MYNEWT-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu updated MYNEWT-543: -- Fix Version/s: v1_0_0_rel > setting sys cfg values via newt erases old settings > --- > > Key: MYNEWT-543 > URL: https://issues.apache.org/jira/browse/MYNEWT-543 > Project: Mynewt > Issue Type: Bug > Components: Newt >Affects Versions: v1_0_0_beta1 > Environment: Mac OS X >Reporter: David G. Simmons >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_0_0_rel > > > DSimmons-Pro:myproj dsimmons$ cat targets/air_q/syscfg.yml > \### Package: targets/air_q > syscfg.vals: > OPENOCD_DEBUG: 1 > \# Enable the shell task. > SHELL_TASK: 1 > STATS_CLI: 1 > CONSOLE_TICKS: 1 > CONSOLE_PROMPT: 1 > DSimmons-Pro:myproj dsimmons$ newt target set air_q syscfg=OPENOCD_DEBUG=0 > Target targets/air_q successfully set target.syscfg to OPENOCD_DEBUG=0 > DSimmons-Pro:myproj dsimmons$ cat targets/air_q/syscfg.yml > \### Package: targets/air_q > syscfg.vals: > OPENOCD_DEBUG: 0 > DSimmons-Pro:myproj dsimmons$ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MYNEWT-543) setting sys cfg values via newt erases old settings
[ https://issues.apache.org/jira/browse/MYNEWT-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu updated MYNEWT-543: -- Priority: Minor (was: Major) > setting sys cfg values via newt erases old settings > --- > > Key: MYNEWT-543 > URL: https://issues.apache.org/jira/browse/MYNEWT-543 > Project: Mynewt > Issue Type: Bug > Components: Newt >Affects Versions: v1_0_0_beta1 > Environment: Mac OS X >Reporter: David G. Simmons >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_0_0_rel > > > DSimmons-Pro:myproj dsimmons$ cat targets/air_q/syscfg.yml > \### Package: targets/air_q > syscfg.vals: > OPENOCD_DEBUG: 1 > \# Enable the shell task. > SHELL_TASK: 1 > STATS_CLI: 1 > CONSOLE_TICKS: 1 > CONSOLE_PROMPT: 1 > DSimmons-Pro:myproj dsimmons$ newt target set air_q syscfg=OPENOCD_DEBUG=0 > Target targets/air_q successfully set target.syscfg to OPENOCD_DEBUG=0 > DSimmons-Pro:myproj dsimmons$ cat targets/air_q/syscfg.yml > \### Package: targets/air_q > syscfg.vals: > OPENOCD_DEBUG: 0 > DSimmons-Pro:myproj dsimmons$ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (MYNEWT-639) newt pkg new command does not error check or show in help text that package location is needed as an argument.
[
https://issues.apache.org/jira/browse/MYNEWT-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wanda Chiu resolved MYNEWT-639.
---
Resolution: Fixed
> newt pkg new command does not error check or show in help text that package
> location is needed as an argument.
> --
>
> Key: MYNEWT-639
> URL: https://issues.apache.org/jira/browse/MYNEWT-639
> Project: Mynewt
> Issue Type: Bug
> Components: Newt
>Affects Versions: v1_0_0_beta2
>Reporter: Wanda Chiu
>Assignee: Wanda Chiu
>Priority: Minor
> Fix For: v1_0_0_rel
>
>
> 1) The current "newt pkg new" command help text does not indicate package
> location as an input parameter:
> {code}
> newt pkg new -h
> Create a new package, from a template
> Usage:
> newt pkg new [flags]
> Flags:
> -t, --type string Type of package to create: pkg, bsp, sdk. Default pkg.
> (default "pkg")
> {code}
> 2) The command does not error check whether the location is specified and
> assumes one is provided. " newt pkg new" causes a go runtime error.
> {code}
> panic: runtime error: index out of range
> goroutine 1 [running]:
> panic(0x40edc0, 0xc4200120d0)
> /usr/local/Cellar/go/1.7.4_2/libexec/src/runtime/panic.go:500 +0x1a1
> mynewt.apache.org/newt/newt/cli.pkgNewCmd(0xc42014eb40, 0x6aa9a8, 0x0, 0x0)
>
> /Users/wanda/mydev/go/src/mynewt.apache.org/newt/newt/cli/pkg_cmds.go:43
> +0x125
> mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra.(*Command).execute(0xc42014eb40,
> 0x6aa9a8, 0x0, 0x0, 0xc42014eb40, 0x6aa9a8)
>
> /Users/wanda/mydev/go/src/mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra/command.go:636
> +0x443
> mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xc4200a1200,
> 0x, 0x3, 0x47cc01)
>
> /Users/wanda/mydev/go/src/mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra/command.go:722
> +0x367
> mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra.(*Command).Execute(0xc4200a1200,
> 0x47cc01, 0x3)
>
> /Users/wanda/mydev/go/src/mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra/command.go:681
> +0x2b
> main.main()
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MYNEWT-639) newt pkg new command does not error check or show in help text that package location is needed as an argument.
[
https://issues.apache.org/jira/browse/MYNEWT-639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884072#comment-15884072
]
Wanda Chiu commented on MYNEWT-639:
---
Fix in PR: https://github.com/apache/incubator-mynewt-newt/pull/40
> newt pkg new command does not error check or show in help text that package
> location is needed as an argument.
> --
>
> Key: MYNEWT-639
> URL: https://issues.apache.org/jira/browse/MYNEWT-639
> Project: Mynewt
> Issue Type: Bug
> Components: Newt
>Affects Versions: v1_0_0_beta2
>Reporter: Wanda Chiu
>Assignee: Wanda Chiu
>Priority: Minor
> Fix For: v1_0_0_rel
>
>
> 1) The current "newt pkg new" command help text does not indicate package
> location as an input parameter:
> {code}
> newt pkg new -h
> Create a new package, from a template
> Usage:
> newt pkg new [flags]
> Flags:
> -t, --type string Type of package to create: pkg, bsp, sdk. Default pkg.
> (default "pkg")
> {code}
> 2) The command does not error check whether the location is specified and
> assumes one is provided. " newt pkg new" causes a go runtime error.
> {code}
> panic: runtime error: index out of range
> goroutine 1 [running]:
> panic(0x40edc0, 0xc4200120d0)
> /usr/local/Cellar/go/1.7.4_2/libexec/src/runtime/panic.go:500 +0x1a1
> mynewt.apache.org/newt/newt/cli.pkgNewCmd(0xc42014eb40, 0x6aa9a8, 0x0, 0x0)
>
> /Users/wanda/mydev/go/src/mynewt.apache.org/newt/newt/cli/pkg_cmds.go:43
> +0x125
> mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra.(*Command).execute(0xc42014eb40,
> 0x6aa9a8, 0x0, 0x0, 0xc42014eb40, 0x6aa9a8)
>
> /Users/wanda/mydev/go/src/mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra/command.go:636
> +0x443
> mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xc4200a1200,
> 0x, 0x3, 0x47cc01)
>
> /Users/wanda/mydev/go/src/mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra/command.go:722
> +0x367
> mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra.(*Command).Execute(0xc4200a1200,
> 0x47cc01, 0x3)
>
> /Users/wanda/mydev/go/src/mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra/command.go:681
> +0x2b
> main.main()
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (MYNEWT-639) newt pkg new command does not error check or show in help text that package location is needed as an argument.
Wanda Chiu created MYNEWT-639:
-
Summary: newt pkg new command does not error check or show in help
text that package location is needed as an argument.
Key: MYNEWT-639
URL: https://issues.apache.org/jira/browse/MYNEWT-639
Project: Mynewt
Issue Type: Bug
Components: Newt
Affects Versions: v1_0_0_beta2
Reporter: Wanda Chiu
Assignee: Wanda Chiu
Priority: Minor
Fix For: v1_0_0_rel
1) The current "newt pkg new" command help text does not indicate package
location as an input parameter:
{code}
newt pkg new -h
Create a new package, from a template
Usage:
newt pkg new [flags]
Flags:
-t, --type string Type of package to create: pkg, bsp, sdk. Default pkg.
(default "pkg")
{code}
2) The command does not error check whether the location is specified and
assumes one is provided. " newt pkg new" causes a go runtime error.
{code}
panic: runtime error: index out of range
goroutine 1 [running]:
panic(0x40edc0, 0xc4200120d0)
/usr/local/Cellar/go/1.7.4_2/libexec/src/runtime/panic.go:500 +0x1a1
mynewt.apache.org/newt/newt/cli.pkgNewCmd(0xc42014eb40, 0x6aa9a8, 0x0, 0x0)
/Users/wanda/mydev/go/src/mynewt.apache.org/newt/newt/cli/pkg_cmds.go:43 +0x125
mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra.(*Command).execute(0xc42014eb40,
0x6aa9a8, 0x0, 0x0, 0xc42014eb40, 0x6aa9a8)
/Users/wanda/mydev/go/src/mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra/command.go:636
+0x443
mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xc4200a1200,
0x, 0x3, 0x47cc01)
/Users/wanda/mydev/go/src/mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra/command.go:722
+0x367
mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra.(*Command).Execute(0xc4200a1200,
0x47cc01, 0x3)
/Users/wanda/mydev/go/src/mynewt.apache.org/newt/newt/vendor/github.com/spf13/cobra/command.go:681
+0x2b
main.main()
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (MYNEWT-543) setting sys cfg values via newt erases old settings
[ https://issues.apache.org/jira/browse/MYNEWT-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu reassigned MYNEWT-543: - Assignee: Wanda Chiu (was: Sterling Hughes) > setting sys cfg values via newt erases old settings > --- > > Key: MYNEWT-543 > URL: https://issues.apache.org/jira/browse/MYNEWT-543 > Project: Mynewt > Issue Type: Bug > Components: Newt >Affects Versions: v1_0_0_beta1 > Environment: Mac OS X >Reporter: David G. Simmons >Assignee: Wanda Chiu > > DSimmons-Pro:myproj dsimmons$ cat targets/air_q/syscfg.yml > \### Package: targets/air_q > syscfg.vals: > OPENOCD_DEBUG: 1 > \# Enable the shell task. > SHELL_TASK: 1 > STATS_CLI: 1 > CONSOLE_TICKS: 1 > CONSOLE_PROMPT: 1 > DSimmons-Pro:myproj dsimmons$ newt target set air_q syscfg=OPENOCD_DEBUG=0 > Target targets/air_q successfully set target.syscfg to OPENOCD_DEBUG=0 > DSimmons-Pro:myproj dsimmons$ cat targets/air_q/syscfg.yml > \### Package: targets/air_q > syscfg.vals: > OPENOCD_DEBUG: 0 > DSimmons-Pro:myproj dsimmons$ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-557) Newt build command does not print out a warning when overriding an undefined configuration setting
[ https://issues.apache.org/jira/browse/MYNEWT-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15852408#comment-15852408 ] Wanda Chiu commented on MYNEWT-557: --- Fix in PR:https://github.com/apache/incubator-mynewt-newt/pull/35 > Newt build command does not print out a warning when overriding an undefined > configuration setting > -- > > Key: MYNEWT-557 > URL: https://issues.apache.org/jira/browse/MYNEWT-557 > Project: Mynewt > Issue Type: Bug > Components: Newt >Affects Versions: v1_0_0_beta1 >Reporter: Wanda Chiu >Assignee: Wanda Chiu > Fix For: v1_0_0_rel > > > The newt build command ignores overriding an undefined configuration setting. > There should be a warning message to let the user know because the error may > be caused by typo with the configuration setting name. This can create > unexpected behavior because the user thinks the override was successful. Note > that the newt target config command does output a warning message. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MYNEWT-575) newt tool does not enforce "value" as a required field in a setting definition
[ https://issues.apache.org/jira/browse/MYNEWT-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu closed MYNEWT-575. - Resolution: Fixed Fix merged into develop branch > newt tool does not enforce "value" as a required field in a setting definition > -- > > Key: MYNEWT-575 > URL: https://issues.apache.org/jira/browse/MYNEWT-575 > Project: Mynewt > Issue Type: Bug > Components: Newt >Affects Versions: v1_0_0_beta1 >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_0_0_rel > > > Newt tool does not check that "value" is a required field for configuration > setting definition. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MYNEWT-556) The newt tool does not generate an error for priority violations of configuration setting overrides
[ https://issues.apache.org/jira/browse/MYNEWT-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu closed MYNEWT-556. - Resolution: Fixed Fixed merged into develop branch > The newt tool does not generate an error for priority violations of > configuration setting overrides > --- > > Key: MYNEWT-556 > URL: https://issues.apache.org/jira/browse/MYNEWT-556 > Project: Mynewt > Issue Type: Bug > Components: Newt >Affects Versions: v1_0_0_beta1 >Reporter: Wanda Chiu >Assignee: Wanda Chiu > Fix For: v1_0_0_rel > > > When a package of the same or lower priority package overrides a setting > defined by a higher priority package, newt silently ignores the overrides. > Newt should generate a priority violation error. > newt only checks for Lateral violations (lib packages overriding a setting > defined by another lib packages). This is a special case of priority > violation and should be treated as a priority violation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MYNEWT-563) Compilation Error when Enabling all Newt Manager commands for bletiny app
[ https://issues.apache.org/jira/browse/MYNEWT-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu closed MYNEWT-563. - Resolution: Fixed Fix merged into develop branch. > Compilation Error when Enabling all Newt Manager commands for bletiny app > - > > Key: MYNEWT-563 > URL: https://issues.apache.org/jira/browse/MYNEWT-563 > Project: Mynewt > Issue Type: Bug >Affects Versions: v1_0_0_beta1 >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_0_0_rel > > > In the "Enabling Newt Manager in any app" Tutorial, we show the user how to > add all Newt Manager Commands to the bletiny app. We get two compilation > errors when compiling the app to test against the documentation: > 1) Adding to bletiny/src/main.c results in duplicate >#define STR(x) error, as it is defined in both and main.c. > Need to add a #ifndef around the #define in main.c > 2) Adding test/runtest package gets error when compiling runtest_nmgr.c > because it cannot find "testutil/testutil.h". Need to add test/testutil > package to test/runtest pkg.yml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MYNEWT-575) newt tool does not enforce "value" as a required field in a setting definition
[ https://issues.apache.org/jira/browse/MYNEWT-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15844196#comment-15844196 ] Wanda Chiu commented on MYNEWT-575: --- Fixed in PR: https://github.com/apache/incubator-mynewt-newt/pull/34 > newt tool does not enforce "value" as a required field in a setting definition > -- > > Key: MYNEWT-575 > URL: https://issues.apache.org/jira/browse/MYNEWT-575 > Project: Mynewt > Issue Type: Bug > Components: Newt >Affects Versions: v1_0_0_beta1 >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_0_0_rel > > > Newt tool does not check that "value" is a required field for configuration > setting definition. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MYNEWT-576) Update apps that use newtmgr framework to explicitly set the event queue with mgmt
[ https://issues.apache.org/jira/browse/MYNEWT-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu reassigned MYNEWT-576: - Assignee: Wanda Chiu (was: Sterling Hughes) > Update apps that use newtmgr framework to explicitly set the event queue with > mgmt > --- > > Key: MYNEWT-576 > URL: https://issues.apache.org/jira/browse/MYNEWT-576 > Project: Mynewt > Issue Type: Bug > Components: Misc >Affects Versions: v1_0_0_beta1 >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Trivial > Fix For: v1_0_0_rel > > > The tutorial to enable Newt Manager in Any App indicates that the app must > call the mgmt_evq_set to specify the event queue that mgmt uses to receive > newtmgr request events. We need to update the apps that use the newtmgr > framework to make this call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MYNEWT-576) Update apps that use newtmgr framework to explicitly set the event queue with mgmt
Wanda Chiu created MYNEWT-576: - Summary: Update apps that use newtmgr framework to explicitly set the event queue with mgmt Key: MYNEWT-576 URL: https://issues.apache.org/jira/browse/MYNEWT-576 Project: Mynewt Issue Type: Bug Components: Misc Affects Versions: v1_0_0_beta1 Reporter: Wanda Chiu Assignee: Sterling Hughes Priority: Trivial Fix For: v1_0_0_rel The tutorial to enable Newt Manager in Any App indicates that the app must call the mgmt_evq_set to specify the event queue that mgmt uses to receive newtmgr request events. We need to update the apps that use the newtmgr framework to make this call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MYNEWT-575) newt tool does not enforce "value" as a required field in a setting definition
Wanda Chiu created MYNEWT-575: - Summary: newt tool does not enforce "value" as a required field in a setting definition Key: MYNEWT-575 URL: https://issues.apache.org/jira/browse/MYNEWT-575 Project: Mynewt Issue Type: Bug Components: Newt Affects Versions: v1_0_0_beta1 Reporter: Wanda Chiu Assignee: Wanda Chiu Priority: Minor Fix For: v1_0_0_rel Newt tool does not check that "value" is a required field for configuration setting definition. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MYNEWT-563) Compilation Error when Enabling all Newt Manager commands for bletiny app
[ https://issues.apache.org/jira/browse/MYNEWT-563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839098#comment-15839098 ] Wanda Chiu commented on MYNEWT-563: --- Fixed in PR: https://github.com/apache/incubator-mynewt-core/pull/167 > Compilation Error when Enabling all Newt Manager commands for bletiny app > - > > Key: MYNEWT-563 > URL: https://issues.apache.org/jira/browse/MYNEWT-563 > Project: Mynewt > Issue Type: Bug >Affects Versions: v1_0_0_beta1 >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_0_0_rel > > > In the "Enabling Newt Manager in any app" Tutorial, we show the user how to > add all Newt Manager Commands to the bletiny app. We get two compilation > errors when compiling the app to test against the documentation: > 1) Adding to bletiny/src/main.c results in duplicate >#define STR(x) error, as it is defined in both and main.c. > Need to add a #ifndef around the #define in main.c > 2) Adding test/runtest package gets error when compiling runtest_nmgr.c > because it cannot find "testutil/testutil.h". Need to add test/testutil > package to test/runtest pkg.yml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MYNEWT-563) Compilation Error when Enabling all Newt Manager commands for bletiny app
[ https://issues.apache.org/jira/browse/MYNEWT-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu updated MYNEWT-563: -- Description: In the "Enabling Newt Manager in any app" Tutorial, we show the user how to add all Newt Manager Commands to the bletiny app. We get two compilation errors when compiling the app to test against the documentation: 1) Adding to bletiny/src/main.c results in duplicate #define STR(x) error, as it is defined in both and main.c. Need to add a #ifndef around the #define in main.c 2) Adding test/runtest package gets error when compiling runtest_nmgr.c because it cannot find "testutil/testutil.h". Need to add test/testutil package to test/runtest pkg.yml was: In the "Enabling Newt Manager in any app" Tutorial, we show the user how to add all Newt Manager Commands to the bletiny app. We get two compilation errors when compiling the app to test against the documentation: 1) Adding to bletiny/src/main.c results in duplicate #define STR(x) error, as it is defined in both and main.c. main.c does not use STR so can be removed from main.c 2) Adding test/runtest package gets error when compiling runtest_nmgr.c because it cannot find "testutil/testutil.h". Need to add test/testutil package to test/runtest pkg.yml > Compilation Error when Enabling all Newt Manager commands for bletiny app > - > > Key: MYNEWT-563 > URL: https://issues.apache.org/jira/browse/MYNEWT-563 > Project: Mynewt > Issue Type: Bug >Affects Versions: v1_0_0_beta1 >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_0_0_rel > > > In the "Enabling Newt Manager in any app" Tutorial, we show the user how to > add all Newt Manager Commands to the bletiny app. We get two compilation > errors when compiling the app to test against the documentation: > 1) Adding to bletiny/src/main.c results in duplicate >#define STR(x) error, as it is defined in both and main.c. > Need to add a #ifndef around the #define in main.c > 2) Adding test/runtest package gets error when compiling runtest_nmgr.c > because it cannot find "testutil/testutil.h". Need to add test/testutil > package to test/runtest pkg.yml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MYNEWT-563) Compilation Error when Enabling all Newt Manager commands for bletiny app
Wanda Chiu created MYNEWT-563: - Summary: Compilation Error when Enabling all Newt Manager commands for bletiny app Key: MYNEWT-563 URL: https://issues.apache.org/jira/browse/MYNEWT-563 Project: Mynewt Issue Type: Bug Affects Versions: v1_0_0_beta1 Reporter: Wanda Chiu Assignee: Wanda Chiu Priority: Minor Fix For: v1_0_0_rel In the "Enabling Newt Manager in any app" Tutorial, we show the user how to add all Newt Manager Commands to the bletiny app. We get two compilation errors when compiling the app to test against the documentation: 1) Adding to bletiny/src/main.c results in duplicate #define STR(x) error, as it is defined in both and main.c. main.c does not use STR so can be removed from main.c 2) Adding test/runtest package gets error when compiling runtest_nmgr.c because it cannot find "testutil/testutil.h". Need to add test/testutil package to test/runtest pkg.yml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MYNEWT-556) The newt tool does not generate an error for priority violations of configuration setting overrides
[ https://issues.apache.org/jira/browse/MYNEWT-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838081#comment-15838081 ] Wanda Chiu commented on MYNEWT-556: --- PR for fix: https://github.com/apache/incubator-mynewt-newt/pull/32 > The newt tool does not generate an error for priority violations of > configuration setting overrides > --- > > Key: MYNEWT-556 > URL: https://issues.apache.org/jira/browse/MYNEWT-556 > Project: Mynewt > Issue Type: Bug > Components: Newt >Affects Versions: v1_0_0_beta1 >Reporter: Wanda Chiu >Assignee: Wanda Chiu > Fix For: v1_0_0_rel > > > When a package of the same or lower priority package overrides a setting > defined by a higher priority package, newt silently ignores the overrides. > Newt should generate a priority violation error. > newt only checks for Lateral violations (lib packages overriding a setting > defined by another lib packages). This is a special case of priority > violation and should be treated as a priority violation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MYNEWT-557) Newt build command does not print out a warning when overriding an undefined configuration setting
[ https://issues.apache.org/jira/browse/MYNEWT-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu updated MYNEWT-557: -- Component/s: Newt > Newt build command does not print out a warning when overriding an undefined > configuration setting > -- > > Key: MYNEWT-557 > URL: https://issues.apache.org/jira/browse/MYNEWT-557 > Project: Mynewt > Issue Type: Bug > Components: Newt >Affects Versions: v1_0_0_rel >Reporter: Wanda Chiu > > The newt build command ignores overriding an undefined configuration setting. > There should be a warning message to let the user know because the error may > be caused by typo with the configuration setting name. This can create > unexpected behavior because the user thinks the override was successful. Note > that the newt target config command does output a warning message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MYNEWT-557) Newt build command does not print out a warning when overriding an undefined configuration setting
[ https://issues.apache.org/jira/browse/MYNEWT-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu updated MYNEWT-557: -- Affects Version/s: v1_0_0_rel > Newt build command does not print out a warning when overriding an undefined > configuration setting > -- > > Key: MYNEWT-557 > URL: https://issues.apache.org/jira/browse/MYNEWT-557 > Project: Mynewt > Issue Type: Bug > Components: Newt >Affects Versions: v1_0_0_rel >Reporter: Wanda Chiu > > The newt build command ignores overriding an undefined configuration setting. > There should be a warning message to let the user know because the error may > be caused by typo with the configuration setting name. This can create > unexpected behavior because the user thinks the override was successful. Note > that the newt target config command does output a warning message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MYNEWT-557) Newt build command does not print out a warning when overriding an undefined configuration setting
Wanda Chiu created MYNEWT-557: - Summary: Newt build command does not print out a warning when overriding an undefined configuration setting Key: MYNEWT-557 URL: https://issues.apache.org/jira/browse/MYNEWT-557 Project: Mynewt Issue Type: Bug Reporter: Wanda Chiu The newt build command ignores overriding an undefined configuration setting. There should be a warning message to let the user know because the error may be caused by typo with the configuration setting name. This can create unexpected behavior because the user thinks the override was successful. Note that the newt target config command does output a warning message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MYNEWT-556) The newt tool does not generate an error for priority violations of configuration setting overrides
Wanda Chiu created MYNEWT-556: - Summary: The newt tool does not generate an error for priority violations of configuration setting overrides Key: MYNEWT-556 URL: https://issues.apache.org/jira/browse/MYNEWT-556 Project: Mynewt Issue Type: Bug Components: Newt Affects Versions: v1_0_0_rel Reporter: Wanda Chiu Assignee: Sterling Hughes When a package of the same or lower priority package overrides a setting defined by a higher priority package, newt silently ignores the overrides. Newt should generate a priority violation error. newt only checks for Lateral violations (lib packages overriding a setting defined by another lib packages). This is a special case of priority violation and should be treated as a priority violation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
