Ошибка empty result

начнем с того, что у вас вот тут очень жуткая ошибка

for i in range(0,l-1):
    if (s[i]==s[i+1] and s[i+1]!=s[i+2]):

потому что в случае, если друг за другом будут идти одинаковые элементы и условие s[i]==s[i+1] будет выполнено, то дальше будет проверено s[i+1]!=s[i+2]

и если одинаковые элементы находятся в конце списка, то будет обращение к s[i+2], а учитывая, что i доходит до len(s) - 2 включительно, то обращение будет к s[len(s)] — а это выход за диапазон и будет ошибка

IndexError: list index out of range

что легко можно проверить введя 1 1

на счет вывода ответа — ну так вроде когда находит одинаковые элементы — выводит, когда не находит — не выводит ничего, как вы и заложили в коде

А вообще можно обойтись и без сортировки

s = list(map(int, input().split()))
res = set(v for v in s if s.count(v) > 1)

и без множества

res = [s[i] for i in range(len(s)) if s[:i + 1].count(s[i]) == 2]

ну или покороче

res = [v for i, v in enumerate(s) if s[:i + 1].count(v) == 2]

или без count():

from collections import Counter
res = [v for v, c in Counter(s).items() if c > 1]

или без преобразования в целые числа, зато с регулярками

import re
res = set(re.findall(r"(\d+)(?= .*\1)", input()))

P.S.

а вот как должен выглядеть ваш алгоритм:

for i in range(1, l):
    if s[i] == s[i - 1] and (i == l - 1 or s[i] != s[i + 1]):
        print(s[i], end=" ")
print()

Moderators: Developers, Moderators

cactiuser@marlin:/usr/local/cacti/rra> python /usr/local/cacti/scripts/get_db_size.py -H shark.xyz.com -p 5443 -U plone_stats -d zodb_db1
1556.49570847
cactiuser@marlin:/usr/local/cacti/rra>

08/29/2011 02:32:01 PM - SPINE: Poller[0] Host[89] TH[1] DS[9631] SCRIPT: python /usr/local/cacti/scripts/get_db_size.py -H shark.xyz.com -p 5443 -U plone_stats -d zodb_db1, output: 0
08/29/2011 02:32:01 PM - SPINE: Poller[0] Host[89] ERROR: Empty result [shark]: 'python /usr/local/cacti/scripts/get_db_size.py -H shark.xyz.com -p 5443 -U plone_stats -d zodb_db1'

-rw-r--r-- 1 cactiuser wwwrun  92664 2011-08-29 14:34 shark_mb_9631.rrd

/usr/local/cacti-0.8.7g/scripts/get_db_size.py -H shark.xyz.com -p 5443 -U plone_stats -d zodb_db1 >>/tmp/db.log

-rw-------  1 cactiuser wwwrun    148 2011-08-17 09:30 .pgpass

which: no psql in (/usr/bin:/bin)
Traceback (most recent call last):
  File "/usr/local/cacti-0.8.7g/scripts/get_db_size.py", line 74, in ?
    main(sys.argv[1:])
  File "/usr/local/cacti-0.8.7g/scripts/get_db_size.py", line 60, in main
    command_output = Popen(cmd_args, stdout=PIPE).communicate()[0]
  File "/usr/lib64/python2.4/subprocess.py", line 542, in __init__
    errread, errwrite)
  File "/usr/lib64/python2.4/subprocess.py", line 975, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory

Flutter is a popular open-source mobile app development framework that allows developers to create high-performance and visually appealing mobile apps for Android and iOS platforms. When developing a Flutter app, one may encounter the runJavascriptReturningResult error, which occurs when the result returned by the JavaScript code is empty. This article will guide you through how to troubleshoot this issue.

Understand the runJavascriptReturningResult method

Before diving into troubleshooting, it’s essential to understand what the runJavascriptReturningResult method does. This method executes a JavaScript string in a Flutter web view and returns the result as a string. For example, in the following code snippet, we execute a simple JavaScript program and return the result.

final result = await controller.runJavascriptReturningResult("""
  function add(a, b) {
    return a + b;
  }
  add(2, 3)
""");
print(result); // 5

Possible causes of the empty result error

The runJavascriptReturningResult error occurs when the JavaScript code executed by the method fails to produce any result. This may happen due to several reasons, some of which are:

• Syntax errors in the JavaScript code.
• Invalid code or undefined variables used in the JavaScript code.
• Incorrectly formatted or invalid input values passed to the JavaScript code.

Troubleshooting the empty result error

To troubleshoot the empty result error, follow these steps:

1. Check for syntax errors: Review the JavaScript code to ensure that it is free of syntax errors or other issues that could cause the code to fail. If your JavaScript code generates an error, it may fail silently, resulting in an empty result.

2. Use console logs to debug: You can use print() statements or console.log() statements inside the JavaScript code to debug any issues that may be causing the empty result error. These statements can help identify the root cause of the error.

final result = await controller.runJavascriptReturningResult("""
  function add(a, b) {
    console.log('Adding', a, b);
    return a + b;
  }
  add(2, 3)
""");
print(result); // 5

1. Test with different input values: Test the JavaScript code with different input values to determine if the issue is related to the input itself.

final result = await controller.runJavascriptReturningResult("""
  function square(num) {
    if (typeof num === "number") {
      return num * num;
    } else {
      console.log("Expected a number, but received", typeof num);
      return undefined;
    }
  }
  square(5)
""");
print(result); // 25

1. Debug using a debugger: Use a debugger to step through the JavaScript code and identify any issues that could be causing the empty result error.

Conclusion

The runJavascriptReturningResult error occurs when the JavaScript code executed by the method fails to return a result. There are several possible reasons for this, including syntax errors in the JavaScript code, invalid code or undefined variables used in the JavaScript code, or incorrectly formatted or invalid input values passed to the JavaScript code. By following the troubleshooting steps outlined in this article, you can easily identify and fix the issue, allowing you to continue developing your Flutter app with ease.

Terraform Version — 1.0.11
AWS Provider — 3.66.0

We are getting intermittent errors like following when working with terraform for AWS Infrastructure Provisioning:

==============
╷
│ Error: error updating Security Group (sg-0a73d418ae947fe09): couldn’t find resource
│
│ with module.security_groups.aws_security_group.default[«CIOPS-MS-Redis-SG»],
│ on ../../modules/Stack/SecurityGroups/main.tf line 1, in resource «aws_security_group» «default»:
│ 1: resource «aws_security_group» «default» {
│
╵
╷
│ Error: error updating Security Group (sg-0348f9cfa61f16235): couldn’t find resource
│
│ with module.security_groups.aws_security_group.default[«CIOPS-MySQL-SG»],
│ on ../../modules/Stack/SecurityGroups/main.tf line 1, in resource «aws_security_group» «default»:
│ 1: resource «aws_security_group» «default» {
│
╵
╷
│ Error: error reading Route Table (rtb-0fc9e07acc59ca7eb): couldn’t find resource
│
│ with module.data_vpc.aws_route_table.public_route_table[«us-east-1a»],
│ on ../../modules/Stack/VPC/main.tf line 92, in resource «aws_route_table» «public_route_table»:
│ 92: resource «aws_route_table» «public_route_table» {
│
╵

╷
│ Error: error reading Route in Route Table (rtb-0061e7bf9ed9458d7) with destination (10.110.64.0/20): couldn’t find resource
│
│ with module.routing_extapp_data.aws_route.source[«CIOPS-ExtApp-Private-Routing-1b»],
│ on ../../modules/Stack/Routing/main.tf line 13, in resource «aws_route» «source»:
│ 13: resource «aws_route» «source» {
│

╷
│ Error: error reading Route Table (rtb-03178c1f7809c539c): couldn’t find resource
│
│ with module.extapp_vpc.aws_route_table.public_route_table[«us-east-1a»],
│ on ../../modules/Stack/VPC/main.tf line 92, in resource «aws_route_table» «public_route_table»:
│ 92: resource «aws_route_table» «public_route_table» {
│
╵
╷
│ Error: error reading Route Table Association (rtbassoc-09e721baf95da7d6f): empty result
│
│ with module.extapp_vpc.aws_route_table_association.default_private[«CIOPS-ExtApp-ELB-Private-Subnet-1a»],
│ on ../../modules/Stack/VPC/main.tf line 266, in resource «aws_route_table_association» «default_private»:
│ 266: resource «aws_route_table_association» «default_private» {
│
╵

NOTE — The Errors are not static but intermittent. We got the error 3-4 times in about 100 executions done over a period of 48 hours.

==========================

Procedure to reproduce issue
Pre-requisites:

1. Use Region us-east-1 only
2. IAM role attached to EC2 instance on which terraform will be executed with account administrator access.
3. One VPC , it’s CIDR . The VPC should have 2 private route table and one public route table . Keep their route table entires , VPC ID and CIDR handy.
4. Second VPC , it’s CIDR . The VPC should have 2 private route table and one public route table . Keep their route table entires , VPC ID and CIDR handy.
5. One S3 bucket with folder names State-Files and FlowLogs in us-east-1

Steps to follow

1. Go to Folder Path Scripts/Terraform/Reinvent/StackLdapPeering

2. Edit File for following fields
   => Replace AWS Account ID

   ldap_vpc_access_role => Set to IAM role ARN from pre-requisutes 2.

   ldap_ops_vpc_id = Set to VPC ID from pre-requisutes 3.
   ldap_ops_vpc_cidr = Set to VPC CIDR from pre-requisutes 3.
   <Private route table ID 1 for VPC Alpha> => Replace with one private Route Table ID from pre-requisutes 3.
   <Private route table ID 2 for VPC Alpha> => Replace with second private Route Table ID from pre-requisutes 3.
   => Replace with public Route Table ID from pre-requisutes 3.

   ops_vpc_id = Set to VPC ID from pre-requisutes 4.
   ops_vpc_cidr = Set to VPC CIDR from pre-requisutes 4.
   <Private route table ID 1 for VPC Beta> => Replace with one private Route Table ID from pre-requisutes 4.
   <Private route table ID 2 for VPC Beta> => Replace with second private Route Table ID from pre-requisutes 4.

   => Replace the string with S3 bucket from pre-requisutes 5.

3. Execute Commands as follows:
   => export AWS_DEFAULT_REGION=»us-east-1″

   => terraform init -reconfigure -input=false -backend-config=»encrypt=true» -backend-config=»max_retries=100″ -backend-config=»bucket=<Valid S3 Bucket Name from pre req 5>/State-Files/» -backend-config=»region=us-east-1″ -backend-config=»key=CIOPS-test.tfstate»

   =>terraform get

=>terraform plan -input=false -var-file=CIOPS.tfvars
This will show 761 resources to be created

=> terraform apply -auto-approve -input=false -var-file=CIOPS.tfvars

Terraform Configuration :
Scripts.zip