SAP Community - DJ Adams

Bugtoberfest Wrap Up!

2024-10-21T15:00:00.066000+02:00

Posting on @MichelleMoudy 's behalf.

Bugtoberfest is officially over! I hope everyone who wanted to participate was able to complete the tutorials and find all the bugs! As the week is officially over, those of us who wrote these bug hunts wanted to share the intended bugs we wrote into them so y'all had an opportunity to check your work.

By the way, while Bugtoberfest is over, Spooktoberfest is this week's Fun Friday event - check out the details in the Spooktoberfest 2024 blog post!

But before getting to that, I wanted to share a bit about the origin of the name bug used for coding errors. While most believe the origin comes from a real moth getting comfy in a relay in the Mark II at Harvard in 1947, the word actually comes from the terms bugbear or bugaboo. The term bug as used to describe an issue or error in engineering and can be seen in use by Thomas Edison in 1878, well before it was used to describe software or hardware faults.

As a fun aside, us developer advocates had a debate to the origin of the term at a dinner during TechEd Virtual and I ruined many evenings by sharing this fun fact with everyone. I even had to read aloud an article to prove that it didn't originate from the Harvard moth (which was shared as folks found it really funny a bug was caused by a real bug), as I was met with such disbelief. As a result, I was told I had to include this "fun" fact and story somewhere in relation to Bugtoberfest.

For proof that I am in fact correct on the origin of the term bug, see here for more details and links to sources.

Now that everyone is aware of the origin of bugs, check out each of the sections below to see the bugs we purposefully wrote into our individual bug hunts.

ABAP

Easy

CLASS ztest
 DEFINITION
  PUBLIC
  FINAL
  CREATE PUBLIC .
  PUBLIC SECTION.
    METHODS test_value.
    METHODS test_value1.
  PROTECTED SECTION.
  PRIVATE SECTION.
ENDCLASS.

CLASS ztest
 IMPLEMENTATION.
  METHOD test_value2.
  ENDMETHOD.
  METHOD test_value1
  ENDCLASS.

Intended bugs:

Spoiler

Bug 1: At line 17, missing full stop `.` after `METHOD test_value1`.
Bug 2: At line 18, missing `ENDMETHOD` for `test_value1 METHOD`.
Bug 3: At line 15, implemented Wrong Method `test_value2` instead of `test_value`.

Bug 1: At line 17, missing full stop `.` after `METHOD test_value1`.Bug 2: At line 18, missing `ENDMETHOD` for `test_value1 METHOD`.Bug 3: At line 15, implemented Wrong Method `test_value2` instead of `test_value`.

Medium

@AccessControl.authorizationCheck: #NOT_REQUIRED
@EndUserText.label: 'Carrier View - CDS Data Model'
@Search.searchable: true
define view entity ZTest
  as selectfrom /dmo/flight as Flight
  association [1] to /DMO/I_Carrier as _Airline 
{
      @UI.lineItem: [ { position: 10, label: 'Airline'} ]
      @Search.defaultSearchElement: true
      @Search.fuzzinessThreshold: 0.7
      @ObjectModel.text.association: '_Airline'
  key Flight.carrier_id     as AirlineID,
      @UI.lineItem: [ { position: 20, label: 'Connection Number' } ]
  key Flight.connection_id  as ConnectionID,
      @UI.lineItem: [ { position: 30, label: 'Flight Date' } ]
  key Flight.flight_date    as FlightDate,
      @UI.lineItem: [ { position: 40, label: 'Price' } ]
      @Semantics.amount.currencyCode: 'CurrencyCode'
      Flight.price          as Price,
      Flight.currency_code  as CurrencyCode,
      @Semantics.amount.currencyCode: 'CurrencyCode'
      case
       when price <= 1000 or price is initial
        then cast(price as /dmo/flight_price preserving type)
       else
         cast( 1000 + (cast(price as abap.numc(16,2)) - 1000 ) * 
division(9,10,2) as /dmo/flight_price)
       end as

  /* Associations */
      _Airline
}

Intended bugs:

Spoiler

Bug 1: At line 5, `select` from written as `selectfrom`.

Bug 2: At line 6, association statement is incomplete, should have `on $projection.AirlineID = _Airline.AirlineID` after `_Airline`.

Bug 3: At line 28, `end as` Variable Name missing and comma (,) missing after Variable name.

Bug 4: At line 26, `abap.numc` is a wrong data type, it should be `abap.dec`.

Bug 1: At line 5, `select` from written as `selectfrom`.Bug 2: At line 6, association statement is incomplete, should have `on $projection.AirlineID = _Airline.AirlineID` after `_Airline`.Bug 3: At line 28, `end as` Variable Name missing and comma (,) missing after Variable name.Bug 4: At line 26, `abap.numc` is a wrong data type, it should be `abap.dec`.

Hard

@AbapCatalog.viewEnhancementCategory: [#NONE]
@abapcatalog.sqlViewName: 'ZTESt1'
@AccessControl.authorizationCheck: '#NOT_REQUIRED'
@EndUserText.label: 'Test'
@Metadata.ignorePropagatedAnnotations: true
@ObjectModel.usageType:{
   serviceQuality: #X,
   sizeCategory: #S,
   dataClass: #MIXED
}
define view entity ZTest!
  with parameters
    P_Currency :/dmo/currency_code
  as select from /dmo/travel
  association [0] to /DMO/I_Overall_Status_VH_Text as _Status on $projection.Status = _Status.OverallStatus
{
  key travel_id                 as TravelId,
      description               as Description,
      total_price               as TotalPrice,
      currency_code             as CurrencyCode,
      concat_with_space(cast(total_price as abap.char( 20) ),
      $parameters.P_Curency,1) as AmountInCurrency,
      @Consumption.valueHelpDefinition: [{ element: { name:
      '/DMO/I_Overall_Status_VH',entity: 'OverallStatus' } }]
      status                    as Status,
      _Status.Text              as OverallStatus,
}

Intended bugs:

Spoiler

Bug 1: At line 21, name of view entity should be corrected to `ZTest`.

Bug 2: At line 3, unwanted `‘ ‘` for `#NOT_REQUIRED`.

Bug 3: At line 26, unwanted `,` after `OverallStatus`.

Bug 4: At line 15, association cardinality should be [1] instead of [0].

Bug 5: At line 23, in Syntax of `@Consumption.valueHelpDefinition` `element` instead of `entity` written.

Bug 6: At line 24, in Syntax of `@Consumption.valueHelpDefinition` `entity` instead of `element` written.

Bug 7: At line 22, in the syntax of `concat_with_space` there is a type at `$parameters.P_Curency,1)`.

Bug 8: At line 19, missing annotation for `Total_price` field.

Bug 9: At line 2, `@abapcatalog.sqlViewName` is not allowed in view entities.

Bug 1: At line 21, name of view entity should be corrected to `ZTest`.Bug 2: At line 3, unwanted `‘ ‘` for `#NOT_REQUIRED`.Bug 3: At line 26, unwanted `,` after `OverallStatus`. Bug 4: At line 15, association cardinality should be [1] instead of [0].Bug 5: At line 23, in Syntax of `@Consumption.valueHelpDefinition` `element` instead of `entity` written.Bug 6: At line 24, in Syntax of `@Consumption.valueHelpDefinition` `entity` instead of `element` written.Bug 7: At line 22, in the syntax of `concat_with_space` there is a type at `$parameters.P_Curency,1)`.Bug 8: At line 19, missing annotation for `Total_price` field.Bug 9: At line 2, `@abapcatalog.sqlViewName` is not allowed in view entities.

Bash

Easy

#!/usr/bin/env bash

read -p 'Enter your name: '
$answer = $REPLY
echo 'Thank you. You entered $answer.'

Intended bugs:

Spoiler

Bug 1: At line 4, in the assignment of `$REPLY` to `answer`, `answer` should not be prefixed with `$`. (this is not Perl!)

Bug 2: At line 4, in the assignment, no spaces are allowed either before or after the equals symbol `=`.

Bug 3: At line 5, inside single quotes, variables like `$answer` are not expanded (double quotes are needed here).

Bug 1: At line 4, in the assignment of `$REPLY` to `answer`, `answer` should not be prefixed with `$`. (this is not Perl!)Bug 2: At line 4, in the assignment, no spaces are allowed either before or after the equals symbol `=`.Bug 3: At line 5, inside single quotes, variables like `$answer` are not expanded (double quotes are needed here).

Medium

#!/usr/bin/env bash

set -e
set pipefail

main {

  local account="${1:?No account specified}"

  # Cause script to abend if no account data stored
  pass "btp/$account" > dev/null

  cf login
    -a "$(pass "btp/$account/cfapiendpoint")" \
    -u "$(pass "btp/$account/user")" \
    -p "$(pass "btp/$account/password")"

  echo <<EOF
Thank you.
Logged in successfully.
EOF

}

main "$@"

Intended bugs:

Spoiler

Bug 1: At line 4, `pipefail` is an option that you need to set using the `-o` option of `set`.

Bug 2: At line 6, functions can be declared with the `function` keyword like this: `function main { ... }` or without the `function` keyword (as here), but parentheses are needed before the code block, like this: `main () { ... }`.

Bug 3: At line 11, `dev/null` is relative, not absolute (i.e. there's no leading `/`) so this is not really what you want (to cleanly suppress `STDOUT`, output it must be sent to `/dev/null`).

Bug 4: At line 13, the newline at the end of `cf login` is not escaped (with a `\`) so this `cf` command execution is not valid.

Bug 5: At line 18, echo does not read from STDIN so we can't use a heredoc (<<); instead, `cat` could be used (or `printf`).

Bug 1: At line 4, `pipefail` is an option that you need to set using the `-o` option of `set`.Bug 2: At line 6, functions can be declared with the `function` keyword like this: `function main { ... }` or without the `function` keyword (as here), but parentheses are needed before the code block, like this: `main () { ... }`.Bug 3: At line 11, `dev/null` is relative, not absolute (i.e. there's no leading `/`) so this is not really what you want (to cleanly suppress `STDOUT`, output it must be sent to `/dev/null`).Bug 4: At line 13, the newline at the end of `cf login` is not escaped (with a `\`) so this `cf` command execution is not valid.Bug 5: At line 18, echo does not read from STDIN so we can't use a heredoc (<<); instead, `cat` could be used (or `printf`).

Hard

#!/usr/bin/env bash

read -p 'Enter a color: ' color

if [ $color == 'black' ]; then
    echo "Black is not a color, it is the absence of color"
fi

if [ $color =~ ^(red|green|blue)$ ]; then
    echo "You chose a primary color"
fi

cd colors
touch "$color.txt"

Intended bugs:

Spoiler

Bug 1: At line 3, using `read` without `-r` will mangle backslashes (shellcheck Informational).

Bug 2: At line 5 & 9, it's usually a very bad idea to not quote your variables, especially in a `[` construct.

Bug 3: At line 9, to use the regular expression operator `=~` you need the Bash-specific `[[ ... ]]` construct, and not the `[` command - see https://mywiki.wooledge.org/BashFAQ/031 and The open square bracket [ is an executable.

Bug 4: At line 13, not checking the success (or otherwise) of a `cd` command is dangerous, and could result in the script creating, changing or deleting files in a place you didn't expect!

Bug 1: At line 3, using `read` without `-r` will mangle backslashes (shellcheck Informational).Bug 2: At line 5 & 9, it's usually a very bad idea to not quote your variables, especially in a `[` construct.Bug 3: At line 9, to use the regular expression operator `=~` you need the Bash-specific `[[ ... ]]` construct, and not the `[` command - see https://mywiki.wooledge.org/BashFAQ/031 and The open square bracket [ is an executable.Bug 4: At line 13, not checking the success (or otherwise) of a `cd` command is dangerous, and could result in the script creating, changing or deleting files in a place you didn't expect!

jq

Easy

We want a simple list of products and the categories they're in. The output should look like this:

Chai is in the Beverages category
Chang is in the Beverages category
Aniseed Syrup is in the Condiments category
Chef Anton's Cajun Seasoning is in the Condiments category
...

The invocation of the jq script (including bugs) to produce this looks like this:

jq --raw \
  '.()|"(.ProductName) is in the \(Category.CategoryName) category" \
  products.json

and on its own, with extra whitespace, the (buggy) jq filter looks like this:

.()
| "(.ProductName) is in the \(Category.CategoryName) category"

Intended bugs:

Spoiler

Bug 1: At line 1 in the jq filter, the array iterator is `[]`, not `()` (Array Object Value Iterator).

Bug 2: At line 2 of the jq filter, the string interpolation construct is `\( ... )` so there's a backslash missing in the first instance (String Interpolation)

Bug 3: At line 2 of the jq filter, in the second instance of an expression being inserted into the string, the identity filter `.` is missing - it should be `.Category.CategoryName` (Identity)

The correct filter should be:

.[]|"\(.ProductName) is in the \(.Category.CategoryName) category"

Bug 1: At line 1 in the jq filter, the array iterator is `[]`, not `()` (Array Object Value Iterator).Bug 2: At line 2 of the jq filter, the string interpolation construct is `\( ... )` so there's a backslash missing in the first instance (String Interpolation)Bug 3: At line 2 of the jq filter, in the second instance of an expression being inserted into the string, the identity filter `.` is missing - it should be `.Category.CategoryName` (Identity)The correct filter should be:.[]|"\(.ProductName) is in the \(.Category.CategoryName) category"

Medium

We want to know how many products are still being sold, i.e. not discontinued. The answer should be a simple numeric value, like this (8 of the 77 total products in this data set are discontinued, so the value here is correct):

The invocation of the jq script (including bugs) to produce this looks like this:

jq --raw \
  'select(.Discontinued)|length' \
  products.json

and on its own, with extra whitespace, the (buggy) jq filter looks like this:

select(.Discontinued)
| length

Intended bugs:

Spoiler

Bug 1: At line 1 of the jq filter, the outermost element in the data set is an array, so we must use map to iterate over and call `select` (Map).

Bug 2: At line 2 of the jq filter, we're after a count of the products that are not discontinued, so we need to negate the boolean expression inside the select (Select).

The correct filter should be:

map(select(.Discontinued|not))|length

Bug 1: At line 1 of the jq filter, the outermost element in the data set is an array, so we must use map to iterate over and call `select` (Map).Bug 2: At line 2 of the jq filter, we're after a count of the products that are not discontinued, so we need to negate the boolean expression inside the select (Select).The correct filter should be:map(select(.Discontinued|not))|length

Hard

Based on the data set, we want a summary of categories with the total number of units of stock for each of those categories. The output should look like this:

{
  "Beverages": 559,
  "Condiments": 507,
  "Confections": 386,
  "Dairy Products": 393,
  "Grains/Cereals": 308,
  "Meat/Poultry": 165,
  "Produce": 100,
  "Seafood": 701
}

The invocation of the jq script (including bugs) to produce this looks like this:

jq --raw \
  'group(.Category.CategoryID)|map({first|Category.CategoryName:map(.UnitsInStock)|+})|sum' \
  products.json

and on its own, with extra whitespace, the (buggy) jq filter looks like this:

group(.Category.CategoryID)
| map({
    first|Category.CategoryName:
    map(.UnitsInStock)
    | +
  })
| sum

Intended bugs:

Spoiler

Bug 1: At line 1 of the jq filter, the `group` function, which takes a path expression, is `group_by`, not `group` (Group By).

Bug 2: At line 3 of the jq filter, while `first` (which is just syntactic sugar for .[0] (Built Ins - first)) can be followed by a pipe, it can also be followed directly by the identity filter, which is missing here (should be `first.Category.CategoryName`, or `first|.Category.CategoryName` but not `first|Category.CategoryName`) (First Last Nth).

Bug 3: At line 3 of the jq filter, to use an expression as a key in a property literal, you need to wrap it in parentheses, i.e. `{(first.Category.CategoryName): ... }`, not `{first.Category.CategoryName: ...}`.

Bug 4: At line 5 of the jq filter, while `+` is valid in jq (it's an operator), it's not valid in the position it is here; the `add` filter is needed to add values in an array (Add).

Bug 5: At line 7 of the jq filter, `sum` is not a valid filter in jq, it's `add`.

The correct filter should be:

group_by(.Category.CategoryID)
| map({
    (first.Category.CategoryName):
    map(.UnitsInStock)
    | add
  })
| add

Bug 1: At line 1 of the jq filter, the `group` function, which takes a path expression, is `group_by`, not `group` (Group By).Bug 2: At line 3 of the jq filter, while `first` (which is just syntactic sugar for .[0] (Built Ins - first)) can be followed by a pipe, it can also be followed directly by the identity filter, which is missing here (should be `first.Category.CategoryName`, or `first|.Category.CategoryName` but not `first|Category.CategoryName`) (First Last Nth).Bug 3: At line 3 of the jq filter, to use an expression as a key in a property literal, you need to wrap it in parentheses, i.e. `{(first.Category.CategoryName): ... }`, not `{first.Category.CategoryName: ...}`.Bug 4: At line 5 of the jq filter, while `+` is valid in jq (it's an operator), it's not valid in the position it is here; the `add` filter is needed to add values in an array (Add).Bug 5: At line 7 of the jq filter, `sum` is not a valid filter in jq, it's `add`.The correct filter should be:group_by(.Category.CategoryID) | map({ (first.Category.CategoryName): map(.UnitsInStock) | add }) | add

JavaScript

Easy

const bugFunc = (areThereBugs) -> {
  if (areThereBags) {
    console.log('Quick! Call an exterminator!);
  } else {
    console.log('Are you sure there aren't any bugs?');
  } else {
    console.log('No bugs here! Thank god.');
  }
}

Intended bugs:

Spoiler

Bug 1: At line 1, arrow function syntax is wrong. It should be `=>`, not `->`.

Bug 2: At line 2, variable `areThereBugs` is misspelled to `areThereBags`.

Bug 3: At line 3, There is a missing quote at the end of the string in first console.log.

Bug 4: At line 5, The `'` in `aren't` hasn't been escaped in the second console.log.

Bug 5: At line 6, There's an extra `else` that will never be called. To fix this, line 4 should either be an `else if` or the second `else` should be removed.

Bug 1: At line 1, arrow function syntax is wrong. It should be `=>`, not `->`.Bug 2: At line 2, variable `areThereBugs` is misspelled to `areThereBags`. Bug 3: At line 3, There is a missing quote at the end of the string in first console.log.Bug 4: At line 5, The `'` in `aren't` hasn't been escaped in the second console.log.Bug 5: At line 6, There's an extra `else` that will never be called. To fix this, line 4 should either be an `else if` or the second `else` should be removed.

Medium

for (let i = 0: i < 5: i++) {
  console.log(looped {i} times);
}

Intended bugs:

Spoiler

Bug 1: At line 1, for loop condition is using `:` instead of `;` between parameters.

Bug 2: At line 2, in the console.log statement, there are missing quotes. The correct quotes to be used are backticks `\`` for the template literal so the `i` variable is correctly updated within the string.

Bug 3: At line 2, in the console.log statement, there is a missing `$` in front of the variable curly braces `{}`.

Bug 1: At line 1, for loop condition is using `:` instead of `;` between parameters.Bug 2: At line 2, in the console.log statement, there are missing quotes. The correct quotes to be used are backticks `\`` for the template literal so the `i` variable is correctly updated within the string.Bug 3: At line 2, in the console.log statement, there is a missing `$` in front of the variable curly braces `{}`.

Hard

For the last JavaScript bug hunt, "bug" identification is the name of the game. What most people call bugs or insects are actually several different classifications of the phylum arthropods.

The goal of the function in this bug hunt is to take in an object of an unidentified "bug" and determine if it is a part of the class Insecta or Arachnids, and if Insecta, further identify if it is a true bug in the order Hemiptera. To make things simple, the function should return one of the three values, "Arachnid", "Insect", or "True Bug".

Please note that some of this data might not technically be correct, entomology wise. For example, there are some arachnids with less than 8 legs. This does not count as a bug. To simplify things, the objects below are going to be used as the source of truth for arthropod classification. They should be used to determine if the function `isArachnidInsectOrBug` will return the correct output.

Arachnid

{
    antennae: false,
    wingPairs: false,
    bodySegments: 2,
    legs: 8
}

Insect

{
    antennae: true,
    wingPairs: [0, 2],
    mouthType: [
      "sponging",
      "siphoning",
      "chewing",
      "piercing/sucking flexible",
      "piercing/sucking rigid"
    ],
    bodySegments: 3,
    legs: 6
}

True Bug

{
    antennae: true,
    wingPairs: [0, 2],
    mouthType: "piercing/sucking rigid",
    bodySegments: 3,
    legs: 6
}

Hint: Keep these classification objects in mind when looking at the functions in the bug hunt.

Below are examples of potential input to the function `IsArachnidInsectOrBug`. In order to determine what is what, they need to match the values in the classification objects above. Keep in mind that all true bugs are insects but not all insects are true bugs and arachnids are neither. No coding bugs will be about the data itself being wrong.

Assume only one value in the classification object parameters with arrays will be chosen for the input object. For example, in Insect, `wingPairs` would equal either `0` or `2`, not `[0]` or `[0, 2]`. You can see this in input example 2.

Example of what could be sent into the function and expected output:

Arthropod Input Example 1

{
    antennae: false,
    wingPairs : false,
    bodySegments: 2,
    legs: 8
}

Expected Output: "Arachnid"

Arthropod Input Example 2

{
    antennae: false,
    wingPairs : false,
    mouthType: "piercing/sucking flexible",
    bodySegments: 3,
    legs: 6
}

Expected Output: "Insect"

Remember, best practices is not a justification for a bug. If the code will run and output the expected result, it does not count as a bug. Also keep in mind that the point is to count the bugs, not how to fix the bugs. One fix might take care of several bugs but should not be counted as only one bug.

These are complex bugs so look carefully.

Find the bugs in the following code:

function isArachnidInsectOrBug (arthropod) {
    let bugType = isInsectOrBug(arthropod);

    if (!bugType) {
        return isArachnid(arthropod);
    }
}

function isInsectOrBug(arthropod) {
    let bugType = "";
    switch (arthropod.mouthType) {
        case "sponging":
        case "siphoning":
        case "chewing":
        case "piercing/sucking flexible": {
            bugType = "Insect";
        }
        case "piercing/sucking rigid": {
            bugType = "True Bug";
        }
    }
}

function isArachnid ({antennae, wingPairs, bodySegments, legs}) {
    if (!antennae || !wingPairs || bodySegments === 2 || legs ===  {
        return true;
    }
}

Intended bugs:

Spoiler

Bug 2: At line 16, in the switch statement in `isInsectOrBug`, doesn't have a break statement and will always cause `bugType` to be "True Bug".

Bug 3: At line 9, `isInsectOrBug` does not have a return statement.

Bug 4: At line 25, `isArachnid` is using the wrong boolean operators to test if arthropods is an arachnid. If any of those are correct, the function will return true. This will cause certain insects to return as Arachnid and is not correct.
Bug 5: At line 27, `isArachnid` does not return anything if bug isn't an arachnid. This could cause an error as the returned value will be null. This could be handled in the `isArachnidInsectOrBug` due to truthy values but can cause unexpected errors so returning false is the best option.

Bug 6: At line 5, `isArachnidInsectOrBug` is expecting isArachnid to return the string "Arachnid" but is instead getting a boolean. This will cause isArachnidInsectOrBug to return a boolean rather than one of the three expected strings. To fix this, `isArachnidInsectOrBug` should use the value to return either "Arachnid" or further check for insect or true bug.

Bug 7: At line 5, `isArachnidInsectOrBug` will only return if bug is an arachnid. It should return the results of `isInsectOrBug` if not an empty string and otherwise throw an error if insect is none of the three expected results.

Without bugs, this is what the function could look like (without accounting for best practices and shortening code):

function isArachnidInsectOrBug (arthropod) {
    let bugType = "";

    if (isArachnid(arthropod)) {
        bugType = "Arachnid";
    } else {
        bugType = isInsectOrBug(arthropod);
    }

    if (bugType !== "") {
        return bugType;
    } else {
        throw new Error({
            arthropod: arthropod,
            err: "Arthropod is not an Arachnid, Insect, or True Bug."
        })
    }
}

function isInsectOrBug(arthropod) {
    let bugType = "";
    switch (arthropod.mouthType) {
        case "sponging":
        case "siphoning":
        case "chewing":
        case "piercing/sucking flexible": {
            // Alternatively, the string could be returned here instead of using the break statement and the bugType variable.
            bugType = "Insect";
            break;
        }
        case "piercing/sucking rigid": {
            bugType = "True Bug";
            break;
        }
    }
    return bugType;
}

function isArachnid ({antennae, wingPairs, bodySegments, legs}) {
    // Alternatively, the result of the boolean statement in the if statement could be returned directly.
    // EX. `return (!antennae && !wingPairs && bodySegments === 2 && legs === 8);`
    if (!antennae && !wingPairs && bodySegments === 2 && legs ===  {
        return true;
    } else {
        return false;
    }
}

Bug 1: At line 2, calling `isInsectOrBug` first will throw an error if the arthropod is an Arachnid as the arachnid object does not have the `mouthType` parameter. To fix this, call `isArachnid` first and return `Arachnid` before checking if the arthropod is an insect or true bug.Bug 2: At line 16, in the switch statement in `isInsectOrBug`, doesn't have a break statement and will always cause `bugType` to be "True Bug".Bug 3: At line 9, `isInsectOrBug` does not have a return statement.Bug 4: At line 25, `isArachnid` is using the wrong boolean operators to test if arthropods is an arachnid. If any of those are correct, the function will return true. This will cause certain insects to return as Arachnid and is not correct.Bug 5: At line 27, `isArachnid` does not return anything if bug isn't an arachnid. This could cause an error as the returned value will be null. This could be handled in the `isArachnidInsectOrBug` due to truthy values but can cause unexpected errors so returning false is the best option.Bug 6: At line 5, `isArachnidInsectOrBug` is expecting isArachnid to return the string "Arachnid" but is instead getting a boolean. This will cause isArachnidInsectOrBug to return a boolean rather than one of the three expected strings. To fix this, `isArachnidInsectOrBug` should use the value to return either "Arachnid" or further check for insect or true bug.Bug 7: At line 5, `isArachnidInsectOrBug` will only return if bug is an arachnid. It should return the results of `isInsectOrBug` if not an empty string and otherwise throw an error if insect is none of the three expected results.Without bugs, this is what the function could look like (without accounting for best practices and shortening code):function isArachnidInsectOrBug (arthropod) { let bugType = ""; if (isArachnid(arthropod)) { bugType = "Arachnid"; } else { bugType = isInsectOrBug(arthropod); } if (bugType !== "") { return bugType; } else { throw new Error({ arthropod: arthropod, err: "Arthropod is not an Arachnid, Insect, or True Bug." }) } } function isInsectOrBug(arthropod) { let bugType = ""; switch (arthropod.mouthType) { case "sponging": case "siphoning": case "chewing": case "piercing/sucking flexible": { // Alternatively, the string could be returned here instead of using the break statement and the bugType variable. bugType = "Insect"; break; } case "piercing/sucking rigid": { bugType = "True Bug"; break; } } return bugType; } function isArachnid ({antennae, wingPairs, bodySegments, legs}) { // Alternatively, the result of the boolean statement in the if statement could be returned directly. // EX. `return (!antennae && !wingPairs && bodySegments === 2 && legs === 8);` if (!antennae && !wingPairs && bodySegments === 2 && legs === { return true; } else { return false; } }

Python

Easy

def hello_world();
print "Hello, World!"

hello_world()

Intended bugs:

Spoiler

Bug 1: At line 1, `;` should be `:`.

Bug 2: At line 2, the print statement should be indented after the function definition on line 1.

Bug 3: At line 2, The string "Hello, World!" should be wrapped in parentheses in call to `print`.

Bug 1: At line 1, `;` should be `:`.Bug 2: At line 2, the print statement should be indented after the function definition on line 1.Bug 3: At line 2, The string "Hello, World!" should be wrapped in parentheses in call to `print`.

Medium

from typing import Final

#Store integers 1, 2 and 3 in variables `ONE`, `TWO`, `THREE`
ONE, TWO, THREE = range(1, 3)
ZERO : Final = 0

def check_number (x : int) -> str:
    if x <= ONE:
        result='smaller than or equal to 1'
    elif x = TWO:
        result='equal to 2'
    then:
        result='equal to or greater than 3'

    returns result

a=input("Input the integer number: ")

print(f"{a} is {check_number(a)}")

Intended bugs:

Spoiler

Bug 1: At line 10, boolean operator '==' should be used instead of '='.

Bug 2: At line 12, `then` should be `else`.

Bug 3: At line 15, there is an extra `s` on `returns`. It should be `return result`.

Bug 4: At line 4, `range(1, 3)` will only provide values `1` and `2`, which is not enough values for the number of variables provided. Instead, it should be `range(1, 4)`.

Bug 5: At line 8 and 17, `<=` is not supported between instances of `str` (`a`) and `int` (`x`). To fix this, on line 17, it should be `a=int(input("Input the integer number: "))` to convert a string to an integer.

Bug 1: At line 10, boolean operator '==' should be used instead of '='. Bug 2: At line 12, `then` should be `else`.Bug 3: At line 15, there is an extra `s` on `returns`. It should be `return result`.Bug 4: At line 4, `range(1, 3)` will only provide values `1` and `2`, which is not enough values for the number of variables provided. Instead, it should be `range(1, 4)`. Bug 5: At line 8 and 17, `<=` is not supported between instances of `str` (`a`) and `int` (`x`). To fix this, on line 17, it should be `a=int(input("Input the integer number: "))` to convert a string to an integer.

Hard

from dataclass import dataclass

class PointInTime:
    year : int
    month: int
    day  : int

point = PointInTime(1974, 12, 23)
print(point)  # Output should be: PointInTime(year=1974, month=12, day=23)

Intended bugs:

Spoiler

Bug 1: At line 1, there is no module named 'dataclass'. Instead, it should be `from dataclasses import dataclass`.

Bug 2: At line 2, before the class `PointInTime`, there needs to be a decorator, `@dataClass` as `PointInTime()` takes no arguments without the decorator.

Bug 1: At line 1, there is no module named 'dataclass'. Instead, it should be `from dataclasses import dataclass`.Bug 2: At line 2, before the class `PointInTime`, there needs to be a decorator, `@dataClass` as `PointInTime()` takes no arguments without the decorator.

Wrap Up

I hope everyone had fun. Let us know in the comments if you enjoyed this and want to bring it back next year. Also feel free to share bugs you found that you were proud of or bugs you struggled with.

While Bugtoberfest might be over, Devtoberfest isn't and there's one more week of content, and another Fun Friday event left!

CAP Node.js Plugins (1 of 3) - How things work

2024-10-29T09:56:40.007000+01:00

Hands-on SAP Dev is back! Now that the Devtoberfest and SAP Teched Virtual events are over, it's time to kick off with more live stream episodes, full of curosity-driven learning-by-doing, as is our tradition, right?

We're going to start off with a three part series that is based on the short live session at SAP TechEd Virtual: DEV100B | Developer keynote [deconstructed]: Keeping the promise. In this part, we'll recap and go a little deeper and slower into what we looked at in that DEV100B session. And you can as always ask questions and provide your comments and opinions in the live chat as we go. This will then set us up for the second part, where we'll roll our sleeves up in the REPL and introspect the service. But more on that next time.

See the series post CAP Node.js plugins for more details and links to all the related resources.

The Art and Science of CAP (part 2) with Daniel Hutzel

2024-11-18T08:55:26.072000+01:00

Daniel presented a session at this year's #Devtoberfest titled "The Art and Science of CAP", in which he started to take us on a deep dive, with special background insights, into key design aspects and enduring influential software patterns & philosophies that have shaped CAP. This is the first live follow-up episode to that inaugural one.

See the blog post The Art and Science of CAP for all details, notes, previous episodes, links and more.

To be best prepared for this event, you may wish to watch the first part: 🟢 The Art & Science of CAP.

You may also be interested in TASC Notes - Part 2, a summary of this episode, with links.

In addition, you may want to read the following short blog posts, which explain various gems of insight from that first episode:

See you on Friday!

#SAPCAP #TASC

The Art and Science of CAP (part 3) with Daniel Hutzel

2024-11-25T20:00:13.985000+01:00

Daniel Hutzel continues on his exploration of The Art and Science of CAP, sharing insights and ideas from the origins, philosophy and magic of the SAP Cloud Application Programming Model. #SAPCAP #TASC

See the blog post The Art and Science of CAP for all details, notes, previous episodes, links and more.

The Art and Science of CAP (part 4) with Daniel Hutzel

2024-11-29T12:33:43.843000+01:00

See the blog post The Art and Science of CAP for all details, notes, previous episodes, links and more.

The Art and Science of CAP (part 5) with Daniel Hutzel

2024-12-06T14:39:44.782000+01:00

See the blog post The Art and Science of CAP for all details, notes, previous episodes, links and more.

The Art and Science of CAP (part 6) with Daniel Hutzel (Holiday Season edition)

2024-12-13T17:13:59.266000+01:00

See the blog post The Art and Science of CAP for all details, notes, previous episodes, links and more.

CAP Node.js Plugins (2 of 3) - Using the REPL

2024-12-30T13:53:24.827000+01:00

In this second of a three part series we use the cds REPL to introspect the running service, and explore the entities, elements and annotations, so that we know enough for the third part where we'll write our own plugin. See the series post CAP Node.js plugins for more details and links to all the related resources.

CAP Node.js Plugins (3 of 3) - Writing our own

2024-12-30T13:57:55.493000+01:00

In this third of a three part series, having understood how plugins work (in part 1) and learned how to use the cds REPL to explore entities, elements and annotations of a running service (in part 2), we now know enough to write our own plugin which we'll do in this last part. See the series post CAP Node.js plugins for more details and links to all the related resources.

Re: My CAP Projects Toolbox

2025-01-07T09:02:08.404000+01:00

Hi @vvdries , nice post!

You were looking for some input on the use of the `cds.odata` functions `urlify` and `parse`. While they both don't begin with an underscore (a conventional way of signifying something is off-limits, as I'm sure you know), they are not explicitly documented in Capire* and are therefore deemed to be not for external use. Of course, digging in to the source code and learning about these functions (and how they work, and perhaps more importantly how they also help to clarify the relationship between CQN and the OData protocol adapter, in this example) is great.

*There is one reference, as far as I can find, but it's just in passing and only in a release note entry

HTH!

Re: Error: NoAppDetectedError - An app was not successful...

2025-01-25T07:43:28.118000+01:00

Are you sure you zipped up the files as described? This message sounds like you might still have the app within the ZIP file ... but within a folder within it. Did you follow the warning in the earlier step, which states:

Be sure not to include the containing folder in the zip file – you must explicitly select only the contents of the cf-sample-app-nodejs-main folder and not that folder itself.

Ensure you don't have a top level enclosing folder in the ZIP file and give it another go. Good luck!

The Art and Science of CAP (part 7) with Daniel Hutzel

2025-01-27T15:55:15.307000+01:00

Back by popular demand! We join Daniel Hutzel again as he continues on his exploration of The Art and Science of CAP, sharing insights and ideas from the origins, philosophy and magic of the SAP Cloud Application Programming Model. #SAPCAP #TASC

See the blog post The Art and Science of CAP for all details, notes, previous episodes, links and more.

The Art and Science of CAP (part 8) with Daniel Hutzel

2025-02-10T14:53:01.104000+01:00

We are delighted to host Daniel Hutzel again as he continues on his exploration of The Art and Science of CAP, sharing insights and ideas from the origins, philosophy and magic of the SAP Cloud Application Programming Model. #SAPCAP #TASC

See the blog post The Art and Science of CAP for all details, notes & replays for all previous episodes.

The Art and Science of CAP (part 9) with Daniel Hutzel

2025-02-17T12:05:36.081000+01:00

Join Daniel Hutzel, hosted by DJ Adams, live on their exploration of The Art and Science of CAP, sharing insights and ideas from the origins, philosophy and magic of the SAP Cloud Application Programming Model. #SAPCAP #TASC

See the series blog post The Art and Science of CAP for details, notes, links, other episodes and more.

Re: Devtoberfest Winners Revealed

2025-02-17T17:51:18.940000+01:00

Well done to every participant, and especially to the winners! 🎉

The Art and Science of CAP (part 10) with Daniel Hutzel

2025-02-25T11:09:31.873000+01:00

See the series blog post The Art and Science of CAP for details, notes, links, other episodes and more.

🇳🇱 SAP CodeJam: Service Integration with CAP ('s-Hertogenbosch, NL)

2025-03-03T13:10:00.276000+01:00

This SAP CodeJam introduces attendees to service integration with the SAP Cloud Application Programming Model (CAP). Specifically, the Node.js flavor of CAP is used.

During this event, you'll become acquainted with how external services can be integrated and consumed from within a CAP project. In working through the exercises you'll also become comfortable with various facilities that CDS offers for declaring, relating and exposing entities, and familiar with how the SAP Cloud SDK covers connectivity and destinations, supporting such integration scenarios with CAP.

This is an in-person event only (not virtual) and is planned for Fri 23 May 2025 in 's-Hertogenbosch, NL. It is being kindly hosted by the lovely folks at newFounders - the CodeJam will take place in their offices. Thanks!

The instructor is Developer Advocate DJ Adams.

There are essential prerequisites that must be completed by every attendee, before arriving at the event location. They are documented here: https://github.com/SAP-samples/cap-service-integration-codejam/blob/main/prerequisites.md.

If you wish to attend, please indicate that using the "I'm attending" facility on this page. Please note that spaces are limited - we can only accommodate 25 attendees for this event. In that context, if you indicate that you're attending and later realise you can't, please remove your name so that others get a chance instead. Thanks!

For more information on SAP CodeJam events, to ask questions, and to chat with your fellow attendees, head over to the SAP CodeJam group.

Re: Connect with SAP Community at SAP Sapphire and Share Your Special SAP Event Moment!

2025-05-15T07:11:53.018000+02:00

Gosh, I have many memories from some great SAP events. From attending TechEd in Hamburg in 2000 with my good friend Piers Harding (I'd made a custom tshirt to celebrate R/3 on Linux)

to hanging out with my heroes (here with Brian "BSP" McKellar) at the community lounge at TechEd 2004 in Munich:

to hanging out with fellow SAP Mentors at TechEd 2011 Madrid (including Dick, Twan, Aslan, and very young looking Rich and Tom):

to the celebration board at TechEd Amsterdam in 2013:

to a panel at TechEd Barcelona in 2019:

to a group photo at Inside Track Riga in 2019:

and some of the lovely community folks at TechEd Bengaluru also in 2019 (with my good friend Max):

🇵🇱 Hands-on with the btp CLI and APIs (Wrocław, PL)

2025-05-19T13:59:32.556000+02:00

This SAP CodeJam BTP event is on the Core Service APIs for SAP BTP and also the command line interface tool for SAP BTP, otherwise known as the btp CLI.

This is an in-person event only (not virtual) and is planned for Fri 06 Jun in Wrocław, PL at the WSB Merito University (Building G, Fabryczna 14G, 2nd floor, room 220). The event is kindly being organized by Capgemini Poland and WSB Merito University in Wrocław, thank you! Note that this is the day before the SAP Inside Track event on Sat 07 Jun in the same building.

The instructor is Developer Advocate DJ Adams.

There are essential prerequisites that must be completed by every attendee, before arriving at the event location. They are documented here: https://github.com/SAP-samples/cloud-btp-cli-api-codejam/blob/main/prerequisites.md

If you wish to attend, please indicate that using the "I'm attending" facility on this page. Please note that spaces are limited to a maximum of 35 participants. If you indicate that you're attending, and later realise you're unable to, please remove your name so that others get a chance instead. Thanks!

For more information on SAP CodeJam BTP events, to ask questions, and to chat with your fellow attendees, head over to the SAP CodeJam group.

Re: Task 0 - Server and service provisioning (July Developer Challenge - "Reverse APIs")

2025-06-11T08:19:07.266000+02:00

Hello Hemanth - did you watch the video that covers this (link at the top of this thread), and did you follow the steps? If so, and you're still getting an error, you'll need to help us to help you, by giving much more detail here. What did you do? What are the details? What about screenshots? What else did you try? Thanks. DJ