Closing, configuration issue

I have the Slack configuration correctly configured as per the documentation, and the bot created and integrated with the channel. When attempting to create an incident with slack-conversation and slack-contact enabled, I get the following failure:

File "/usr/local/lib/python3.8/site-packages/slack_sdk/web/slack_response.py", line 201, in validate raise e.SlackApiError(message=msg, response=self) slack_sdk.errors.SlackApiError: The request to the Slack API failed. The server responded with: {'ok': False, 'error': 'users_not_found'}

I have the following env variables correctly configured (as per the documentation) for Slack:

SLACK_API_BOT_TOKEN DISPATCH_HELP_SLACK_CHANNEL SLACK_SIGNING_SECRET SLACK_SOCKET_MODE_APP_TOKEN SLACK_APP_USER_SLUG SLACK_WORKSPACE_NAME

However the incident does not complete creation, and the above error message appears in the logs.

I have followed the Slack configuration as described here: https://hawkins.gitbook.io/dispatch/administration-guide/incident/plugins/configuring-slack

The same problem on "httpClient.tcpConfiguration"

Deprecated
Use the other methods exposed by HttpClient to achieve the same configurations. This method will be removed in version 1.1.0.

Pull Request type

• [x] Feature
• [x] Build related changes

Changes in this PR

es7-persistence module migration from Conductor v.2.30+ to v.3.0+ with basic auth. Elasticsearch 7 support with basic auth added to Conductor v.3.0+, which is based on Spring Boot.

Alternatives considered

ES7-persistence already exists but wasn't migrated from Conductor v.2.30+ to v.3.0+.

FYI, in an interesting twist, the ALPN methods were backported as of JDK 8u251. From release 1.69, the BCJSSE provider adds runtime checks to support those methods when they are present in JDK 8, in addition to the multi-release jar support in JDK 9+.

Closes #414

Currently, if an R user specifies a step with a name that isn't a valid Python identifier, they're met with an obscure error:

library(metaflow)
library(magrittr)

metaflow("test_flow") %>%
  step(step = "start", next_step = "bad-step-name") %>% 
  step(step = "bad-step-name", r_function = function(self) NULL, next_step = "end") %>% 
  step(step = "end") %>% 
  run()

# Error in py_call_impl(callable, dots$args, dots$keywords) : 
#   SyntaxError: invalid syntax (metaflowR.uppq6x7d, line 12)
# 
# Detailed traceback: 
#   File "/home/mdneuzerling/anaconda3/lib/python3.8/site-packages/metaflow/R.py", line 93, in run
#     module = imp.load_source('metaflowR', tmp.name)
#   File "/home/mdneuzerling/anaconda3/lib/python3.8/imp.py", line 171, in load_source
#     module = _load(spec)
#   File "<frozen importlib._bootstrap>", line 702, in _load
#   File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
#   File "<frozen importlib._bootstrap_external>", line 779, in exec_module
#   File "<frozen importlib._bootstrap_external>", line 916, in get_code
#   File "<frozen importlib._bootstrap_external>", line 846, in source_to_code
#   File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
# Calls: <Anonymous> -> py_call_impl
# Execution halted

This PR introduces three internal utility functions:

• is_valid_python_identifier_py2
• is_valid_python_identifier_py3
• is_valid_python_identifier (which calls one of the above based on reticulate::py_version())

The step function now validates the step name using is_valid_python_identifier. The result is a significantly more helpful error message:

library(metaflow)
library(magrittr)

metaflow("test_flow") %>%
  step(step = "start", next_step = "bad-step-name") %>% 
  step(step = "bad-step-name", r_function = function(self) NULL, next_step = "end") %>% 
  step(step = "end") %>% 
  run()

# Error in step(., step = "bad-step-name", r_function = function(self) NULL,  : 
#   bad-step-name is not a valid step name. Step names must be valid Python
# identifiers; they can contain letters, numbers, and underscores, although they
# cannot begin with a number.

It appears that step names must be valid Python variable names. I tripped on this a few times while trying to give steps names with hyphens. It's not an onerous restriction, except the error message that returns is not very helpful (see below). Is it possible to validate step names before or during metaflow::run?

library(metaflow)
#> Metaflow (R) 2.2.0 loaded
#> Metaflow (Python) 2.2.3 loaded
#> 
#> Attaching package: 'metaflow'
#> The following object is masked from 'package:stats':
#> 
#>     step
library(magrittr)

metaflow("test_flow") %>%
  step(step = "start", next_step = "bad-step-name") %>% 
  step(step = "bad-step-name", r_function = function(self) NULL, next_step = "end") %>% 
  step(step = "end") %>% 
  run()

# Error in py_call_impl(callable, dots$args, dots$keywords) : 
#   SyntaxError: invalid syntax (metaflowR.uppq6x7d, line 12)
# 
# Detailed traceback: 
#   File "/home/mdneuzerling/anaconda3/lib/python3.8/site-packages/metaflow/R.py", line 93, in run
#     module = imp.load_source('metaflowR', tmp.name)
#   File "/home/mdneuzerling/anaconda3/lib/python3.8/imp.py", line 171, in load_source
#     module = _load(spec)
#   File "<frozen importlib._bootstrap>", line 702, in _load
#   File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
#   File "<frozen importlib._bootstrap_external>", line 779, in exec_module
#   File "<frozen importlib._bootstrap_external>", line 916, in get_code
#   File "<frozen importlib._bootstrap_external>", line 846, in source_to_code
#   File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
# Calls: <Anonymous> -> py_call_impl
# Execution halted

^{Created on 2021-01-10 by the reprex package (v0.3.0)}

<details>

<summary>

Session info

</summary>

devtools::session_info()
#> ─ Session info ───────────────────────────────────────────────────────────────
#>  setting  value                       
#>  version  R version 4.0.2 (2020-06-22)
#>  os       Ubuntu 20.04.1 LTS          
#>  system   x86_64, linux-gnu           
#>  ui       X11                         
#>  language en_AU:en                    
#>  collate  en_AU.UTF-8                 
#>  ctype    en_AU.UTF-8                 
#>  tz       Australia/Melbourne         
#>  date     2021-01-10                  
#> 
#> ─ Packages ───────────────────────────────────────────────────────────────────
#>  ! package     * version    date       lib source                           
#>  P assertthat    0.2.1      2019-03-21 [?] CRAN (R 4.0.0)                   
#>    callr         3.5.1      2020-10-13 [1] CRAN (R 4.0.2)                   
#>    cli           2.2.0      2020-11-20 [1] CRAN (R 4.0.2)                   
#>  P crayon        1.3.4      2017-09-16 [?] CRAN (R 4.0.0)                   
#>  P desc          1.2.0      2018-05-01 [?] CRAN (R 4.0.0)                   
#>  P devtools      2.3.2      2020-09-18 [?] CRAN (R 4.0.2)                   
#>    digest        0.6.27     2020-10-24 [1] CRAN (R 4.0.2)                   
#>  P ellipsis      0.3.1      2020-05-15 [?] CRAN (R 4.0.0)                   
#>  P evaluate      0.14       2019-05-28 [?] CRAN (R 4.0.0)                   
#>  P fansi         0.4.1      2020-01-08 [?] CRAN (R 4.0.0)                   
#>  P fs            1.5.0      2020-07-31 [?] CRAN (R 4.0.0)                   
#>  P glue          1.4.2      2020-08-27 [?] CRAN (R 4.0.0)                   
#>  P highr         0.8        2019-03-20 [?] CRAN (R 4.0.0)                   
#>  P htmltools     0.5.0      2020-06-16 [?] CRAN (R 4.0.0)                   
#>    jsonlite      1.7.2      2020-12-09 [1] CRAN (R 4.0.2)                   
#>  P knitr         1.30       2020-09-22 [?] CRAN (R 4.0.0)                   
#>  P lattice       0.20-41    2020-04-02 [?] CRAN (R 4.0.0)                   
#>  P lifecycle     0.2.0      2020-03-06 [?] CRAN (R 4.0.0)                   
#>    magrittr    * 2.0.1      2020-11-17 [1] CRAN (R 4.0.2)                   
#>  P Matrix        1.2-18     2019-11-27 [?] CRAN (R 4.0.0)                   
#>  P memoise       1.1.0.9000 2020-05-09 [?] Github (hadley/memoise@4aefd9f)  
#>    metaflow    * 2.2.0      2020-12-19 [1] Github (netflix/metaflow@09ccb92)
#>    pkgbuild      1.2.0      2020-12-15 [1] CRAN (R 4.0.2)                   
#>  P pkgload       1.1.0      2020-05-29 [?] CRAN (R 4.0.0)                   
#>  P prettyunits   1.1.1      2020-01-24 [?] CRAN (R 4.0.0)                   
#>    processx      3.4.5      2020-11-30 [1] CRAN (R 4.0.2)                   
#>    ps            1.5.0      2020-12-05 [1] CRAN (R 4.0.2)                   
#>  P purrr         0.3.4      2020-04-17 [?] CRAN (R 4.0.0)                   
#>    R6            2.5.0      2020-10-28 [1] CRAN (R 4.0.2)                   
#>  P Rcpp          1.0.5      2020-07-06 [?] CRAN (R 4.0.0)                   
#>  P remotes       2.2.0      2020-07-21 [?] CRAN (R 4.0.0)                   
#>  P renv          0.12.3     2020-11-25 [?] CRAN (R 4.0.2)                   
#>    reticulate    1.18       2020-10-25 [1] CRAN (R 4.0.2)                   
#>    rlang         0.4.9      2020-11-26 [1] CRAN (R 4.0.2)                   
#>  P rmarkdown     2.6        2020-12-14 [?] CRAN (R 4.0.2)                   
#>    rprojroot     2.0.2      2020-11-15 [1] CRAN (R 4.0.2)                   
#>  P sessioninfo   1.1.1      2018-11-05 [?] CRAN (R 4.0.0)                   
#>  P stringi       1.5.3      2020-09-09 [?] CRAN (R 4.0.0)                   
#>  P stringr       1.4.0      2019-02-10 [?] CRAN (R 4.0.0)                   
#>    testthat      3.0.1      2020-12-17 [1] CRAN (R 4.0.2)                   
#>    usethis       2.0.0.9000 2020-12-20 [1] Github (r-lib/usethis@c1e8ed6)   
#>  P withr         2.3.0      2020-09-22 [?] CRAN (R 4.0.0)                   
#>  P xfun          0.19       2020-10-30 [?] CRAN (R 4.0.2)                   
#>  P yaml          2.2.1      2020-02-01 [?] CRAN (R 4.0.0)                   
#> 
#> [1] /[TRUNCATED]/renv/library/R-4.0/x86_64-pc-linux-gnu
#> [2] /tmp/RtmpRhwoxA/renv-system-library
#> [3] /tmp/Rtmpot7VVI/renv-system-library
#> 
#>  P ── Loaded and on-disk path mismatch.

</details>

You can go for asynchronous commit

https://flake8.pycqa.org/en/latest/user/error-codes.html

On the flake8 test selection, this PR does not focus on "style violations" (the majority of flake8 error codes that psf/black can autocorrect). Instead these tests focus on runtime safety and correctness:

• E9 tests are about Python syntax errors usually raised because flake8 can not build an Abstract Syntax Tree (AST). Often these issues are a sign of unused code or code that has not been ported to Python 3. These would be compile-time errors in a compiled language but in a dynamic language like Python they result in the script halting/crashing on the user.
• F63 tests are usually about the confusion between identity and equality in Python. Use ==/!= to compare str, bytes, and int literals is the classic case. These are areas where a == b is True but a is b is False (or vice versa). Python >= 3.8 will raise SyntaxWarnings on these instances.
• F7 tests logic errors and syntax errors in type hints
• F82 tests are almost always undefined names which are usually a sign of a typo, missing imports, or code that has not been ported to Python 3. These also would be compile-time errors in a compiled language but in Python a NameError is raised which will halt/crash the script on the user.

We can only help with spring cloud sleuth integration with lettuce. You'll need to find help elsewhere.

I have been stuck with this error and the only closest thing which i could find was this post, and the errors being faced here matches with mine since its coming from the exact same line in the lettuce module.

So why are you commenting on a sleuth lettuce integration issue in a sleuth project that depends on boot is you're neither using sleuth nor boot?

You have not provided which version of cloud, boot and sleuth you're using. Please update to the latest versions and try again

I am not using these two in my project.

You have not provided which version of cloud, boot and sleuth you're using. Please update to the latest versions and try again

I am getting similar error when trying to connect to redis from spring boot application, from the private static final StatefulRedisConnection<String, String> connection = redisClientNew.connect(); line.

@Component
@RequiredArgsConstructor
public class RedisCacheClient {

    private static final SpectraLogger logger = OlympusSpectra.getLogger(RedisCacheClient.class);
    private static final RedisURI redisURI = RedisURI.builder().withSentinel("localhost", 26379).withSentinelMasterId("mymaster").build();
    private static final RedisClient redisClientNew = RedisClient.create(redisURI);
    private static final StatefulRedisConnection<String, String> connection = redisClientNew.connect();
    private static final RedisAsyncCommands<String, String> async = connection.async();
    private static final Gson gson = new Gson();
    private static final Long KEY_EXIST = 1L;

Spring boot console log stuck after these two messages:

2021-06-19 16:02:44,704 8253 [main] INFO  [i.l.c.EpollProvider] {{clusterName,default}{appResourceId,ss@dev}} - Starting without optional epoll library 
2021-06-19 16:02:44,707 8256 [main] INFO  [i.l.c.KqueueProvider] {{clusterName,default}{appResourceId,ss@dev}} - Starting without optional kqueue library 

The error is coming from io.lettuce.core.AbstractRedisClient return connectionFuture.get(); inside the try block.

    protected <T> T getConnection(ConnectionFuture<T> connectionFuture) {
        try {
            return connectionFuture.get();
        } catch (InterruptedException var3) {
            Thread.currentThread().interrupt();
            throw RedisConnectionException.create(connectionFuture.getRemoteAddress(), var3);
        } catch (Exception var4) {
            if (var4 instanceof ExecutionException) {
                throw RedisConnectionException.create(connectionFuture.getRemoteAddress(), var4.getCause());
            } else {
                throw RedisConnectionException.create(connectionFuture.getRemoteAddress(), var4);
            }
        }
    }

Please let me know if this is the same issue and how can i proceed further.

pom.xml

    <dependency>
      <groupId>io.lettuce</groupId>
      <artifactId>lettuce-core</artifactId>
    </dependency>
    <dependency>
      <groupId>org.springframework.boot</groupId>
      <artifactId>spring-boot-starter-data-redis</artifactId>
    </dependency>

Closes #414

Currently, if an R user specifies a step with a name that isn't a valid Python identifier, they're met with an obscure error:

library(metaflow)
library(magrittr)

metaflow("test_flow") %>%
  step(step = "start", next_step = "bad-step-name") %>% 
  step(step = "bad-step-name", r_function = function(self) NULL, next_step = "end") %>% 
  step(step = "end") %>% 
  run()

# Error in py_call_impl(callable, dots$args, dots$keywords) : 
#   SyntaxError: invalid syntax (metaflowR.uppq6x7d, line 12)
# 
# Detailed traceback: 
#   File "/home/mdneuzerling/anaconda3/lib/python3.8/site-packages/metaflow/R.py", line 93, in run
#     module = imp.load_source('metaflowR', tmp.name)
#   File "/home/mdneuzerling/anaconda3/lib/python3.8/imp.py", line 171, in load_source
#     module = _load(spec)
#   File "<frozen importlib._bootstrap>", line 702, in _load
#   File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
#   File "<frozen importlib._bootstrap_external>", line 779, in exec_module
#   File "<frozen importlib._bootstrap_external>", line 916, in get_code
#   File "<frozen importlib._bootstrap_external>", line 846, in source_to_code
#   File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
# Calls: <Anonymous> -> py_call_impl
# Execution halted

This PR introduces three internal utility functions:

• is_valid_python_identifier_py2
• is_valid_python_identifier_py3
• is_valid_python_identifier (which calls one of the above based on reticulate::py_version())

The step function now validates the step name using is_valid_python_identifier. The result is a significantly more helpful error message:

library(metaflow)
library(magrittr)

metaflow("test_flow") %>%
  step(step = "start", next_step = "bad-step-name") %>% 
  step(step = "bad-step-name", r_function = function(self) NULL, next_step = "end") %>% 
  step(step = "end") %>% 
  run()

# Error in step(., step = "bad-step-name", r_function = function(self) NULL,  : 
#   bad-step-name is not a valid step name. Step names must be valid Python
# identifiers; they can contain letters, numbers, and underscores, although they
# cannot begin with a number.

I have a schema like this:

interface Error {
   message: String
}

interface SpecializedError implements Error {
   messsage: String
   specializedError: String
}

type ValidationError implements SpecializedError, Error {
   message: String
   specializedError: String
}

type TestPayload {
   errors: [Error!]
   result: ResultType
}

type ResultType {
   success: Boolean!
}

Expected behavior

I want the generated interface SpecializedError to extend Error so that my TestPayload error field can contain both ValidationError and other error types that implement Error directly.

Actual behavior

Interfaces do not extend other interfaces. However, concrete classes implement multiple interfaces.

Steps to reproduce

Generate code from the schema above and view its output. This is using the Java codegen.

Let me know if I can assist with more information.

public class ServerHandler extends ChannelInboundHandlerAdapter {

public void channelRead(ChannelHandlerContext ctx, Object msg) throws Exception { //todo }

}

Netty version

4

how to create a connection property? how to check that there is a property? How do I get the value of a property? how to remove a property?

what need to store:

enum hostType; // worker, client Double healthStatus

Discussed in https://github.com/Netflix/dgs-framework/discussions/370

<div type='discussions-op-text'>

^{Originally posted by anderssandven May 28, 2021} I have a schema like this:

type Mutation {
	one: One
}

type One {
	two(three: Three!): Two
}

type Two {
	test: String
}

input Three {
	test3: String
}

When doing code generation I expect to get multiple queries generated. The queries generated are: OneGraphQLQuery.java
OneProjectionRoot.java
OneTwoProjection.java

I expect to get a OneTwoGraphlQuery aswell because I cannot supply any arguments through OneGraphqlQuery.

Am I misunderstanding how this works?</div>

When using the client API, I think it should get the same result in the GraphiQL UI. The serialization and deserialization are dependent on Jackson.

You can try to return a String type of the execution result, and use json path to read the result. The String type result should be a JSON String.

Followed the steps of the discussion posts, I tried to add a simple uppercase directive in mysample project, but it does not work as expected.

The uppercase directive wring class.

public class UppercaseDirectiveWiring implements SchemaDirectiveWiring {
    @Override
    public GraphQLFieldDefinition onField(SchemaDirectiveWiringEnvironment<GraphQLFieldDefinition> env) {

        var field = env.getElement();
        var parentType = env.getFieldsContainer();

        var originalDataFetcher = env.getCodeRegistry().getDataFetcher(parentType, field);
        var dataFetcher = DataFetcherFactories.wrapDataFetcher(originalDataFetcher,
                (dataFetchingEnvironment, value) -> {
                    if (value instanceof String s) {
                        return s.toUpperCase();
                    }
                    return value;
                }
        );

        env.getCodeRegistry().dataFetcher(parentType, field, dataFetcher);
        return field;
    }
}

And I created a bean @DgsRuntimeWiring in the data fetchers.

@DgsComponent
public class PostsDataFetcher {

    @DgsRuntimeWiring
    RuntimeWiring.Builder runtimeWiring(RuntimeWiring.Builder builder) {
        return builder.directive("uppercase", new UppercaseDirectiveWiring());
    }

When running the application, and test it on Graphiql, but it does not work. Not sure where is wrong.

This directive is working with my other Graphql example written in GraphQL Java and Spring Graphql.

Check: https://github.com/hantsy/spring-graphql-sample/tree/master/graphql-java/src/main/java/com/example/demo/gql/directives

Hope add a @DgsDirective and apply on the UppercaseDirectiveWiring to register a directive.