Search Keyboard Shortcuts

Summary
Add keyboard shortcuts pertinent to search; pressing Enter now automatically submits the first result returned by fuzzy search, and pressing Backspace or Escape in the results view goes back to the search view without the user needing to click on "back."
Test Plan

Pressing Enter when focused on the search bar submits the first result in the dropdown and triggers a search, as if the user had selected the first result themselves.
Pressing Backspace or Escape when in the course listing pane returns the user to the search pane.
Any keyboard input outside of these scenarios does not do anything.

NB: I didn't include the parsing improvements as part of this test plan, since it's not on npmjs yet, and I've already tested it with the driver before pushing. If you really wanted to test it with AntAlmanac you could pull the latest version from websoc-fuzzy-search and get npm to use that instead.
Issues
Closes #357.

Not sure if this is intentional but I still don't have merge permissions so we need Chase to look at this one.

I've updated permissions. Can you try again @EricPedley?


Too many calls to blockchain

Summary
it looks like bee is doing too many calls to blockchain.
My 25 Million api calls is over within a week.
And infura's daily limit of 100K is becoming peanut for my cluster.

Steps to reproduce
let it run for few days. Then do a cashout once every day.
Expected behavior

Actual behavior

What version are you running?

@Eknir bee 0.5.2 on Ubuntu 20.04. Roughly 20 of my nodes use this particular infura endpoint.

Below is the usage of compute units of two alchemy accounts that i use. Both have 50M compute units capacity (roughly 2M eth_calls). They got exhausted in few days, just like that.

Hm, I think the traffic might just be the result of a lot of cheque traffic. The node needs to verify balances every time it sends or receives cheque. For now I will add some metrics so we can actually track how many cheques a node sends or receives so we can confirm if this is the reason.

how many nodes are in your cluster?


NPE with AWS Lambda and SpringBoot starting multiple times

Framework version: XX
Implementations:   Spring Boot / Lambda
Scenario
NPE when invoking Lambda Function in AWS Lambda Console and Spring Boot starting multiple times
Expected behavior
Should be inserting and fetching records from database when Lambda is invoked
Actual behavior
Throws below error, when Lambda is executed by using AWS Lambda Test Events
Full log output
Error Message on AWS Lambda Cosole :
{
  "statusCode": 404,
  "multiValueHeaders": {
    "Content-Type": [
      "application/json;charset=UTF-8"
    ]
  },
  "body": "{\"timestamp\":\"2019-10-08T13:49:39.550+0000\",\"status\":404,\"error\":\"Not Found\",\"message\":\"No message available\",\"path\":\"/loggingServiceAPI/viewLogs\"}",
  "isBase64Encoded": false
}

Full log output on Cloud Watch
06:15:38.615 [main] INFO com.amazonaws.serverless.proxy.internal.LambdaContainerHandler - Starting Lambda Container Handler
06:15:39.071 [main] INFO com.amazonaws.serverless.proxy.internal.servlet.AwsServletContext - 1 Spring WebApplicationInitializers detected on classpath
2019-10-08 06:15:42.633 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration' of type [org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration$$EnhancerBySpringCGLIB$$c65caf6b] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

. ____ _ __ _ _
/\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
\\/ ___)| |_)| | | | | || (_| | ) ) ) )
' |____| .__|_| |_|_| |_\__, | / / / /
=========|_|==============|___/=/_/_/_/
:: Spring Boot ::

2019-10-08 06:15:45.072 INFO 1 --- [ main] c.d.lambda.Configuration.AwsSsmConfig : Retrieving configuration details from AWS parameter store
2019-10-08 06:15:46.510 INFO 1 --- [ main] c.d.lambda.Configuration.AwsSsmConfig : Found jdf-recordretention-ndl-devl-appid SecureString
2019-10-08 06:15:46.527 INFO 1 --- [ main] c.d.lambda.Configuration.AwsSsmConfig : Found jdf-recordretention-ndl-devl-password SecureString
2019-10-08 06:15:46.527 INFO 1 --- [ main] b.c.PropertySourceBootstrapConfiguration : Located property source: MapPropertySource {name='aws-ssm'}
2019-10-08 06:15:46.594 INFO 1 --- [ main] com.deere.lambda.LoggingServiceConfig : No active profile set, falling back to default profiles: default
START RequestId: 4c27b1a6-b153-4fa0-aa78-6cb612f4819a Version: $LATEST
06:15:49.529 [main] INFO com.amazonaws.serverless.proxy.internal.LambdaContainerHandler - Starting Lambda Container Handler
06:15:50.451 [main] INFO com.amazonaws.serverless.proxy.internal.servlet.AwsServletContext - 1 Spring WebApplicationInitializers detected on classpath
2019-10-08 06:15:57.291 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration' of type [org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration$$EnhancerBySpringCGLIB$$c83c3ffd] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

. ____ _ __ _ _
/\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
\\/ ___)| |_)| | | | | || (_| | ) ) ) )
' |____| .__|_| |_|_| |_\__, | / / / /
=========|_|==============|___/=/_/_/_/
:: Spring Boot ::

2019-10-08 06:16:02.070 INFO 1 --- [ main] c.d.lambda.Configuration.AwsSsmConfig : Retrieving configuration details from AWS parameter store
2019-10-08 06:16:04.768 INFO 1 --- [ main] c.d.lambda.Configuration.AwsSsmConfig : Found jdf-recordretention-ndl-devl-appid SecureString
2019-10-08 06:16:04.769 INFO 1 --- [ main] c.d.lambda.Configuration.AwsSsmConfig : Found jdf-recordretention-ndl-devl-password SecureString
2019-10-08 06:16:04.769 INFO 1 --- [ main] b.c.PropertySourceBootstrapConfiguration : Located property source: MapPropertySource {name='aws-ssm'}
2019-10-08 06:16:04.868 INFO 1 --- [ main] com.deere.lambda.LoggingServiceConfig : No active profile set, falling back to default profiles: default
2019-10-08 06:16:08.588 INFO 1 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data repositories in DEFAULT mode.
2019-10-08 06:16:09.254 INFO 1 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 566ms. Found 1 repository interfaces.
2019-10-08 06:16:12.111 INFO 1 --- [ main] o.s.cloud.context.scope.GenericScope : BeanFactory id=3039cc2d-19a8-3ae1-855a-155f642fa6d3
2019-10-08 06:16:13.147 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration' of type [org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration$$EnhancerBySpringCGLIB$$ac223d00] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2019-10-08 06:16:13.372 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration' of type [org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration$$EnhancerBySpringCGLIB$$c83c3ffd] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2019-10-08 06:16:13.391 INFO 1 --- [ main] c.a.s.p.i.servlet.AwsServletContext : Initializing Spring embedded WebApplicationContext
2019-10-08 06:16:13.391 INFO 1 --- [ main] o.s.web.context.ContextLoader : Root WebApplicationContext: initialization completed in 8461 ms
2019-10-08 06:16:15.189 INFO 1 --- [ main] c.a.s.p.i.servlet.AwsServletContext : Initializing Spring DispatcherServlet 'dispatcherServlet'
2019-10-08 06:16:15.189 INFO 1 --- [ main] o.s.web.servlet.DispatcherServlet : Initializing Servlet 'dispatcherServlet'
2019-10-08 06:16:16.810 WARN 1 --- [ main] aWebConfiguration$JpaWebMvcConfiguration : spring.jpa.open-in-view is enabled by default. Therefore, database queries may be performed during view rendering. Explicitly configure spring.jpa.open-in-view to disable this warning
2019-10-08 06:16:18.828 INFO 1 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Starting...
2019-10-08 06:16:19.729 INFO 1 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Start completed.
2019-10-08 06:16:20.432 INFO 1 --- [ main] o.hibernate.jpa.internal.util.LogHelper : HHH000204: Processing PersistenceUnitInfo [
name: default
...]
2019-10-08 06:16:20.987 INFO 1 --- [ main] org.hibernate.Version : HHH000412: Hibernate Core {[WORKING]}
2019-10-08 06:16:20.990 INFO 1 --- [ main] org.hibernate.cfg.Environment : HHH000206: hibernate.properties not found
2019-10-08 06:16:21.654 INFO 1 --- [ main] o.hibernate.annotations.common.Version : HCANN000001: Hibernate Commons Annotations {5.0.4.Final}
2019-10-08 06:16:30.290 INFO 1 --- [ main] org.hibernate.dialect.Dialect : HHH000400: Using dialect: org.hibernate.dialect.PostgreSQLDialect
2019-10-08 06:16:30.793 INFO 1 --- [ main] o.h.e.j.e.i.LobCreatorBuilderImpl : HHH000424: Disabling contextual LOB creation as createClob() method threw error : java.lang.reflect.InvocationTargetException
2019-10-08 06:16:30.810 INFO 1 --- [ main] org.hibernate.type.BasicTypeRegistry : HHH000270: Type registration [java.util.UUID] overrides previous : org.hibernate.type.UUIDBinaryType@331acdad
2019-10-08 06:16:32.392 INFO 1 --- [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default'
2019-10-08 06:16:36.413 INFO 1 --- [ main] o.s.s.concurrent.ThreadPoolTaskExecutor : Initializing ExecutorService 'applicationTaskExecutor'
2019-10-08 06:16:36.668 INFO 1 --- [ main] o.s.web.servlet.DispatcherServlet : Completed initialization in 21479 ms
2019-10-08 06:16:38.787 INFO 1 --- [ main] com.deere.lambda.LoggingServiceConfig : Started LoggingServiceConfig in 47.663 seconds (JVM running for 50.756)
2019-10-08 06:16:38.854 ERROR 1 --- [ main] c.a.s.p.internal.LambdaContainerHandler : Error while handling request

java.lang.NullPointerException: null
at com.amazonaws.serverless.proxy.internal.servlet.AwsProxyHttpServletRequestReader.readRequest(AwsProxyHttpServletRequestReader.java:48)
at com.amazonaws.serverless.proxy.internal.servlet.AwsProxyHttpServletRequestReader.readRequest(AwsProxyHttpServletRequestReader.java:28)
at com.amazonaws.serverless.proxy.internal.LambdaContainerHandler.proxy(LambdaContainerHandler.java:174)
at com.amazonaws.serverless.proxy.internal.LambdaContainerHandler.proxyStream(LambdaContainerHandler.java:209)
at com.deere.lambda.LambdaHandler.LoggingServiceLambdaHandler.handleRequest(LoggingServiceLambdaHandler.java:30)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

AWS POM Dependencies
 <dependency>
            <groupId>com.amazonaws</groupId>
            <artifactId>aws-lambda-java-core</artifactId>
            <version>1.2.0</version>
        </dependency>

        <dependency>
            <groupId>com.amazonaws.serverless</groupId>
            <artifactId>aws-serverless-java-container-spring</artifactId>
            <version>1.3</version>
        </dependency>

SpringBoot Lambda Handler Class
public class LambdaHandler implements RequestHandler<AwsProxyRequest, AwsProxyResponse> {

    private static SpringBootLambdaContainerHandler<AwsProxyRequest, AwsProxyResponse> handler;

    static {
        try {
            handler = SpringBootLambdaContainerHandler.getAwsProxyHandler(SpringBootApplication.class);
        } catch (ContainerInitializationException e) {
            // if we fail here. We re-throw the exception to force another cold start
            e.printStackTrace();
            throw new RuntimeException("Could not initialize Spring Boot Application", e);
        }
    }

    @Override
    public AwsProxyResponse handleRequest(AwsProxyRequest awsProxyRequest, Context context) {
        return handler.proxy(awsProxyRequest, context);
    }
}

Application class
 public class SpringBootApplication {
        public static void main(String[] args) {
            SpringApplication.run(SpringBootApplication.class, args);
        }
}

Test Data in JSON for LAMBDA-PROXY event. Is there any other Test Event format that I can use to test AWS Lambda Function on AWS Lambda Console
{
  "resource": "/path/resource",
  "path": "/path/resource",
  "httpMethod": "POST",
  "headers": {
      "Accept" : "application/json",
       "content-type": "application/json"
  }
  "multiValueHeaders": {},
  "queryStringParameters": null,
  "multiValueQueryStringParameters": null,
  "pathParameters": null,
  "stageVariables": null,
  "requestContext": {
    "resourcePath": "/path/resource",
    "httpMethod": "POST",
    "path": "//path/resource",
    "accountId": "accountIdNumber",
    "protocol": "HTTP/1.1",
    "stage": "test-invoke-stage",
    "domainPrefix": "testPrefix",
    "identity": {
      "cognitoIdentityPoolId": null,
      "cognitoIdentityId": null,
      "apiKey": "test-invoke-api-key",
      "principalOrgId": null,
      "cognitoAuthenticationType": null,
      "userArn": "actual arn with my userid",
      "apiKeyId": "test-invoke-api-key-id"
    }
  },
  "body": "{ \"Key1\": \"Value1\", \"Key2\": \"Value2\", \"Key3\": \"Vaue3\" }",
  "isBase64Encoded": "false"
}

This message also displays on CloudWatch, despite of giving headers
2019-10-08 14:38:44.255 ERROR 1 --- [           main] c.a.s.p.i.s.AwsProxyHttpServletRequest   : Called set character encoding to UTF-8 on a request without a content type. Character encoding will not be set
2019-10-08 14:38:44.279  INFO 1 --- [           main] c.a.s.p.internal.LambdaContainerHandler  : null arn value [01/01/1970:00:00:00Z] "POST /error HTTP/1.1" 404 147 "-" "-" combined
END RequestId: 6b16c329-d34a-446c-bfbc-03cdce672731

@sapessi Can you please help me with this issue

Hi @MounicaRamini, couple of things that could be going on:

For the NPE, can you switch to the latest version of the framework (1.4). For Spring Boot 1.5.x use aws-serverless-java-container-spring. For Spring Boot 2.x use aws-serverless-java-container-springboot2
For the multiple starts, you may be running afoul of the 10 seconds init timeout (see issue #210). This was also solved in the latest release of the framework with the new asynchronous initialization.

Hope this helps.

@sapessi  What does the below error mean ?
2019-10-08 14:38:44.279  INFO 1 --- [           main] c.a.s.p.internal.LambdaContainerHandler  : null arn value
The arn value had assumed role with my empid at the end. Does that mean, am not allowed to perform anything there ? What does null mean here ?

It's not an error, just an INFO log. Having said that, I can't seem to find that log line anywhere in the code. Can you share a few log lines around it?

Hi @sapessi I haven't added anywhere in the code to log that INFO. It must be from internal jars. I have taken that request format while triggering API Gateway, and started to test it out in AWS Lambda Console to check the solution because of API timeout issues.
Also, at the end of errors, I see it forming an endpoint in the format , Is is correct ?
START RequestId: 0c87477e-334e-4722-a402-ccb142a4b794 Version: $LATEST
2019-10-08 17:34:32.450  INFO 1 --- [           main] c.a.s.p.internal.LambdaContainerHandler  : null - [08/10/2019:17:34:32Z] **"POST /path/resourceHTTP/1.1"** 404 - "-" "-" combined
END RequestId: 0c87477e-334e-4722-a402-ccb142a4b794

But on API gateway, the way endpoint is /path/resource
So, just curious if it's hitting the correct endpoint, because I see below error where body is empty and response is 404
{
  "statusCode": 404,
  "multiValueHeaders": {},
  "body": "",
  "isBase64Encoded": false
}

The first null in the log line is because your test event does not include a remote address. The path being merged with the protocol is definitely funky, there is clearly a space between the two in the log formatter. Can you make sure you don't have bad characters in the path you are passing in through the test event? Perhaps re-type it in manually.

Could you please share me a sample event to test please

It should look something like this (make sure to adjust path/method/headers to something that suites your app):
{
    "resource":"/helloworld",
    "path":"/helloworld",
    "httpMethod":"GET",
    "headers": {
        "Accept":"*/*",
        "content-type":"application/json",
        "Host":"r275xc9bmd.execute-api.us-east-1.amazonaws.com",
        "User-Agent":"curl/7.64.0",
        "X-Amzn-Trace-Id":"Root=1-1a2b3c4d-a1b2c3d4e5f6a1b2c3d4e5f6",
        "X-Forwarded-For":"<IP_ADDRESS>",
        "X-Forwarded-Port":"443",
        "X-Forwarded-Proto":"https"
    },
    "multiValueHeaders":{
        "Accept":["*/*"],
        "content-type":["application/json"],
        "Host":["r275xc9bmd.execute-api.us-east-1.amazonaws.com"],
        "User-Agent":["curl/0.0.0"],
        "X-Amzn-Trace-Id":["Root=1-1a2b3c4d-a1b2c3d4e5f6a1b2c3d4e5f6"],
        "X-Forwarded-For":["11.22.333.44"],
        "X-Forwarded-Port":["443"],
        "X-Forwarded-Proto":["https"]
    },
    "queryStringParameters":{
        "city":"Seattle",
        "name":"John"
  },
  "multiValueQueryStringParameters":{
    "city":["Seattle"],
    "name":["John"]
  },
  "pathParameters":null,
  "stageVariables":null,
  "requestContext":{
    "resourceId":"3htbry",
    "resourcePath":"/helloworld",
    "httpMethod":"POST",
    "extendedRequestId":"a1b2c3d4e5f6g7h=",
    "requestTime":"20/Mar/2019:20:38:30 +0000",
    "path":"/test/helloworld",
    "accountId":"123456789012",
    "protocol":"HTTP/1.1",
    "stage":"test",
    "domainPrefix":"r275xc9bmd",
    "requestTimeEpoch":1553114310423,
    "requestId":"test-invoke-request",
    "identity":{
      "cognitoIdentityPoolId":null,
      "accountId":null,
      "cognitoIdentityId":null,
      "caller":null,
      "sourceIp":"test-invoke-source-ip",
      "accessKey":null,
      "cognitoAuthenticationType":null,
      "cognitoAuthenticationProvider":null,
      "userArn":null,
      "userAgent":"curl/0.0.0","user":null
    },
    "domainName":"r275xc9bmd.execute-api.us-east-1.amazonaws.com",
    "apiId":"r275xc9bmd"
  },
  "body": null,
  "isBase64Encoded":false
  }

If you are building unit tests, we include a request builder object. Check our examples here

@sapessi Thank You so much for patiently answering everything. It worked, I did make changes to Request Format.It brings up records now
thank you so much

The event you were sending was correct in structure since the library was able to read it. However, there seem to be something broken in the value of the path property of the event - the log line without a space between the path and the protocol suggested there was a hidden character in the path that should not have been there, perhaps a \b.


Governance Transition Timeline

On recent transitional Jupyter Executive Council calls, we have been working on the timeline for the transition. Please find our current timeline below.

Transitional Executive Council weekly call and office hours...

EC working call: Mondays 9-10am Pacific Time
EC office hours: Mondays 10-11am Pacific Time
Join: jovyan zoom (pwd: c0JZTHlNdS9Sek9vdzR3aTJ4SzFTQT09)

Date
Description

Fri 12 Aug 2022
Overview document written and merged

Fri 12 Aug 2022
Clarification of the role of SSC reps and that an SSC rep can represent multiple projects with multiple votes (see https://github.com/jupyterhub/team-compass/issues/544) PR: https://github.com/jupyter/governance/pull/133

Tue 20 Sep 2022
Open an issue in governance repo with timeline

Mon 03 Oct 2022
Subproject Councils formed

Mon 03 Oct 2022
Subprojects pick Software Steering Council (SSC) representatives

Mon 03 Oct 2022
List of eligible voters (UofC) is compiled and email list created

Mon 10 Oct 2022
Create EC candidate Statement of Interest Template

Mon 10 Oct 2022
Voting mechanics are decided and implemented

Mon 10 Oct 2022
Communicate nomination call and instructions to the UofC

Mon 31 Oct 2022
Nomination deadline

Mon 07 Nov 2022
Nomination statements compiled and sent out

Mon 14 Nov 2022
UoC vote - November 14 to 21st (week before Thanksgiving)

Mon 28 Nov 2022
EC Vote: Monday the 28th of November to Sunday December 4 (week after Thanksgiving)

Mon 05 Dec 2022
Fernando/Current SC steps down as BDFL/Official transition happens to EC

?
SSC meets for the first time

?
EC team-compass repo + minutes issue

?
Choose meeting time + office hours time

?
EC meets for the first time

?
Update github/jupyter/governance to show only relevant docs

?
Change the standing committee doc to remove the requirement that all SCs have an SSC rep

?
Update the language on the Distinguished Contributors document to mirror the paragraph in the overview

?
Establishing the Standing Committees (DEI, CoC response, Community Advisory, Conflict of Interest)

cc: @jupyter/steeringcouncil


Fix links.

Proposed changes

fix links to "Reserve memory or CPUs for a service"
Unreleased project version (optional)

Related issues (optional)

Deploy preview for docsdocker ready!
Built with commit 5bde184abd86434c718912d183a02045de4f69c0
https://deploy-preview-8463--docsdocker.netlify.com


Added colorado.edu

The University of Colorado

@jweatherley I am sorry, the domain colorado.edu is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


Fixed #26889 -- Fixed missing PostgreSQL index in SchemaEditor.add_field().

https://code.djangoproject.com/ticket/26889

If we apply the similar reasoning as ticket #25412, we might consider this a data loss issue worthy of backporting to 1.8/1.9. Any thoughts?  In that case, I wonder if the schema editor changes might be a bit too invasive for a stable release (concerned about breaking a third-party database backend).

I have created an alternative version of the patch that is less invasive and only involves the PostgreSQL backend. You can view it be viewing the full diff, not just the last commit. If you prefer the 2nd version I will squash the commits.
I think I like the original better as it offers a single hook to backends to inject indexes on fields (instead of adding the same index in multiple places). But ultimately both work and I am happy with either. I do see your point wrt backporting the change, so whatever makes that work easier is no problem.
Thanks. All feedback welcome.

Looks good. We can merge this approach and then follow up with a refactoring on master for the other approach. I'm not sure the SlugField test is needed (or all other subclasses of CharField).

Made requested changes and squashed commits. Thanks.


The Error like this?

please provide more context.

Closing. If you still have issues, feel free to reopen.

Closing. If you still have issues, feel free to reopen.

i have complete this problem.thanks!


[[FIX]] Correct token reported by singleGroups

This should resolve gh-2067.

Warnings emitted due to the singleGroups option should be in terms of
the opening parenthesis token of the offending grouping operator.

Coverage remained the same at 94.75% when pulling bc857f3e839a32f214c66ef0e5b3d2b97cd49ad8 on jugglinmike:single-groups-error-token into 2dc713a2eac387feb62debf5ff4f0c1fa467244a on jshint:master.


Kotlin formatter

We can't reformat our code. Maybe we can use ktlint
There is no document formatter for 'kotlin'-files installed.

This will be added in a future release. (A pull request would be really awesome too, if you are interested in contributing)
To add some other notable reference implementations (of Kotlin formatters):

https://github.com/JetBrains/kotlin-eclipse/tree/master/kotlin-eclipse-ui/src/org/jetbrains/kotlin/ui/formatter
https://github.com/JetBrains/kotlin/tree/master/idea/formatter/src/org/jetbrains/kotlin/idea

Where in the code will this linter need to be integrated?

@Tadaboody Essentially, this function would need to be implemented:
https://github.com/fwcd/KotlinLanguageServer/blob/116589a325f6ca7799a8a84df90c1f4a9110dd05/src/main/kotlin/org/javacs/kt/KotlinTextDocumentService.kt#L89
It might be a good idea to move all formatting code into a separate subpackage of org.javacs.kt (as with the other features).

Great job 👍


Bump flax version in manifest and update flax patch

subsumed by https://github.com/NVIDIA/JAX-Toolbox/commit/57693e4d8290afc812c660e8aaab88570d82e9ba


Issue in float_active_app.sh - Nothing happens in Ubuntu 14.04 LTS

After I run the script float_active_app.sh, nothing happens and the active icons don't float on the top.

Hello , nshankar !  Thank you for the comment.  Can you please clarify  : you mean your Unity Launcher is not changing its order , correct ?  I am assuming that you're running Ubuntu with Unity environment because that's what this script is written for. I've been running this script in 16.04 and it still works there perfectly fine.  I'll ask a few friends to test as well.  Would be also nice to know example of script running with set -x option added to the top of the script .

I'm currently setting up a Ubuntu Trusty (64 bit) VM with Vagrant, using the ubuntu-desktop package.
When I have more information (whether reproducible or not) on 14 and 16.04, I'll update this comment with more information.

Serg,
Sorry to call in late. I will run it with -x and get back to you. Any updates in the meantime?

I tried with this command - sudo ./float_active_app.sh -x
it hangs and needs to be killed with ^c (ctrl-c). Please let us know if I am missing something.

@nshankar  you're not supposed to run it with sudo, just run as regular user.

I tried to run it sithout sudo as well.
The terminal hangs. Need ctrl-c to take it to life

@nshankar  what's your Ubuntu version ? are you using Unity desktop ? also, set -x part was wrong. You need to add it inside the script.

I am using Ubuntu 16.04 Desktop with Unity.
---- You need to add it inside the script.

Please, can you tell me how I

would do this?

Thank you.

@nshankar  OK, open the script file. Where you see
ARGV0="$0"
ARGC=$#

Change it to
set -x
ARGV0="$0"
ARGC=$#

Save, close, and run the script


Uf 4581 fix charset nullpointer issue

Defaulting to UTF-8 charset when incoming contentType attribute lacks
charset information
A warning log is created when filter can't be applied

Acted on PR comments


[dv/rstmgr] Review coverage exclusions

This is to document the exclusions for rstgr.
There are three kinds of exclusions:
cm_hier exclusions
We exclude rstmgr_cnsty_chk module since it has its own separate environment. This is well understood.
Hjson CSR exclusions

The exclusions of reset_req and sw_rst_ctrl_n are for full chip only, and can be disabled at IP level. See https://github.com/lowRISC/opentitan/issues/11140.
The exclusions for *info_attr are related to not having a mechanism to set their reset value correctly. These are read only and constant value registers so it seems okay to keep the exclusion.

UNR exclusions
This results in a large number of exclusions, which can become a drag since they will need to be reviewed for V2, V2S, and V3. We decided to create a specialized rstmgr_leaf_rst that has no sw_rst input, and use that for the resets that have no software reset, which is the majority of resets This will simplify the code and will remove a large number of exclusions. We expectation is that the resulting UNR will be much smaller and easier to deal with.

The UNR exclusions became unnecessary because of the specialization of the rstmgr_leaf_chk module for non-sw_rst cases. The removal of exclusions for chip level triggered a bug in sw_rst_regwen/sw_rst_ctrl_n, tracked separately in https://github.com/lowRISC/opentitan/issues/11457.
Closing this as we just need to track https://github.com/lowRISC/opentitan/issues/11457.


Missing method in the Typescript declaration file.

The UIManager method

measureLayoutRelativeToParent

is not present in the index.d.ts file.
I'm not sure if this issue should be reported here, since I didn't find the file itself in this repo, but is the file that comes in node_modules with react-native:

Thanks

@diego-caceres  Thank you for reaching out. The TypeScript definitions are maintained at https://github.com/DefinitelyTyped/DefinitelyTyped.
You can find the specific definitions here: https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react-native
It would be awesome if you can create a Pull Request to help make the React Native TypeScript definitions better!

Yes, great, I'll head there then.
Thank you for the guidance.


cli.go:25: Implement `store-card ...

The puzzle 3-18477983 from #3 has to be resolved:
https://github.com/kerelape/gophkeeper/blob/c9dfb7269754649812961cf4a543a59ec2dc54de/internal/cli/cli.go#L25-L25
The puzzle was created by kerelape on 08-Sep-23.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 3-18477983 has disappeared from the source code, that's why I closed this issue.


fix: prepend 'ibm-' to rule ids

PR summary
This commit modifies the ruleset so that each rule's name (rule id) starts with 'ibm-'.
Some of the rules will be undergoing other changes and their rule id's might change again, but it was easier to just make a pass through all the rules and add "ibm-" to the beginning of their rule id's in various places.
PR Checklist
General checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)
[ ] Dependencies have been updated as needed
[ ] .secrets.baseline updated as needed?

Checklist for adding a new validation rule:

[ ] Added new validation rule definition (packages/ruleset/src/rules/*.js, index.js)
[ ] If necessary, added new validation rule implementation (packages/ruleset/src/functions/*.js, updated index.js)
[ ] Added new rule to default configuration (packages/ruleset/src/ibm-oas.js)
[ ] Added tests for new rule (packages/ruleset/test/*.test.js)
[ ] Added docs for new rule (docs/ibm-cloud-rules.md)

:tada: This PR is included in version 0.0.2-rc.1 :tada:
The release is available on npm package (@v1-rc dist-tag)
Your semantic-release bot :package::rocket:


Programming exercises: Fix submission policy not enforced

Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Server

[ ] Important: I implemented the changes with a very good performance and prevented too many (unnecessary) database calls.
[ ] I followed the coding and design guidelines.
[ ] I added multiple integration tests (Spring) related to the features (with a high test coverage).
[ ] I added pre-authorization annotations according to the guidelines and checked the course groups for all new REST Calls (security).
[ ] I documented the Java code using JavaDoc style.

Client

[ ] Important: I implemented the changes with a very good performance, prevented too many (unnecessary) REST calls and made sure the UI is responsive, even with large data.
[ ] I followed the coding and design guidelines.
[ ] Following the theming guidelines, I specified colors only in the theming variable files and checked that the changes look consistent in both the light and the dark theme.
[ ] I added multiple integration tests (Jest) related to the features (with a high test coverage), while following the test guidelines.
[ ] I added authorities to all new routes and checked the course groups for displaying navigation elements (links, buttons).
[ ] I documented the TypeScript code using JSDoc style.
[ ] I added multiple screenshots/screencasts of my UI changes.
[ ] I translated all newly inserted strings into English and German.

Changes affecting Programming Exercises

[ ] I tested all changes and their related features with all corresponding user types on Test Server 1 (Atlassian Suite).
[ ] I tested all changes and their related features with all corresponding user types on Test Server 2 (Jenkins and Gitlab).

Motivation and Context

Description

Steps for Testing

Prerequisites:

1 Instructor
2 Students
1 Programming Exercise with Complaints enabled

Log in to Artemis
Navigate to Course Administration
...

Exam Mode Testing

Prerequisites:

1 Instructor
2 Students
1 Exam with a Programming Exercise

Log in to Artemis
Participate in the exam as a student
Make sure that the UI of the programming exercise in the exam mode stays unchanged. You can use the exam mode documentation as reference.
...

Review Progress

Performance Review

[ ] I confirm that the client changes (in particular related to REST calls and UI responsiveness) are implemented with a very good performance
[ ] I confirm that the server changes (in particular related to database calls) are implemented with a very good performance

Code Review

[ ] Code Review 1
[ ] Code Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Exam Mode Test

[ ] Test 1
[ ] Test 2

Test Coverage

Screenshots

Codecov Report

Merging #6518 (4860382) into develop (2b2fe95) will increase coverage by 4.00%.
The diff coverage is 100.00%.

:exclamation: Current head 4860382 differs from pull request most recent head 7a8321c. Consider uploading reports for the commit 7a8321c to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@              Coverage Diff              @@
##             develop    #6518      +/-   ##
=============================================
+ Coverage      76.51%   80.51%   +4.00%
- Complexity         0    13183   +13183
=============================================
  Files           1261     2344    +1083
  Lines          47410    89970   +42560
  Branches        8857    13286    +4429
=============================================
+ Hits           36275    72439   +36164
- Misses          5696     9639    +3943
- Partials        5439     7892    +2453

Impacted Files
Coverage Δ

...itoryProgrammingExerciseParticipationResource.java
72.11% <100.00%> (ø)

... and 1083 files with indirect coverage changes

Flag
Coverage Δ

client
76.51% <ø> (-0.01%)
:arrow_down:

server
84.97% <100.00%> (?)

Continue to review full report in Codecov by Sentry.

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


[BUG] WebSocket stops responding unexpectedly

Describe the bug
The websocket stops responding (incognito session fixes it).
The websocket times out after working successfully multiple times. The only way I have to restore connection is to open a new incognito session. Working on Chrome
WebSocket connection to '' failed: WebSocket is closed before the connection is established.
index-e0da01c4.js:942 WebSocket connection to 'wss://HOST/socket.io/?EIO=4&transport=websocket' failed: WebSocket is closed before the connection is established.

Dont think its Flowise related, maybe a cache on browser that mess it up?

I think it has to do with connection disposal, how often does Flowise closes the connection if it does not receive the ping?

I think it has to do with connection disposal, how often does Flowise closes the connection if it does not receive the ping?

that is the default socketIO config, in Flowise we didnt specify any configuration for timeout


"peak_start is not defined" error

Started getting this error for these inputs:
First Time: Yes
Previous Pattern: Unknown
Sunday: 100
Week Prices: 43, 38, 100, 84, 150

I am also getting this error. In my case it's when loading the page with URL parameters like this https://turnipprophet.io/index.html?prices=<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.0

Almost certainly related to the refactor that was merged shortly before these reports.
Investigating...

It could be here:
https://github.com/mikebryant/ac-nh-turnip-prices/blob/8f4988224596830c5c4526765ebb40bdc214426c/js/predictions.js#L165-L182
The peak_start variable is used in an if statement without being declared for the function on line 176.

Well that's what happen when you partially revert a PR... :facepalm:
All my fault, I didn't check the intermediate commit that carefully.

Sorry about that!


Add "© Copyright 2015, 2016, 2017 Mattermost, Inc." to copyright notice in docs repo

Small polish ticket for anyone interested.

Fixed via https://github.com/mattermost/docs/commit/4062aaa062df8eef98ab1935a2914ed148036aa2


Momentary double render of Tooltip

I see the Tooltip rendering momentarily in double, then reverting to proper single rendering automatically. This only happens sometimes, on certain components. In most other locations it works flawlessly.
Any suggestions? See attached

If your use case is the same as mine what is happening is:

You added a
You are using that Component more than once.

Since the tooltip binds to the data-for attribute, its binding multiple tooltips to multiple triggers. Same thing happening to me.
A solution to this would be pretty cool. Like injecting a random hash to the data-for attribute or somehting.

Yes the issue was non-unique data-for attributes in large lists. Once I added unique values there this issue cleared up. Also the tooltips seem snappier now. Thanks!

BTW A solution I came up with is creating the component as a stateful component. Set a uniqueID in the state object and update it with a random value onComponentWillMount(), use that value for your data-for attribute. That way every instance of your component gets a different ID. Hope it helps!


Add CODEOWNERS file to manage commit rights

Add a GitHub CODEOWNERS file to support disaggregating commit rights.
Allows the Committer process in the Community Membership docs to be
implemented.
Signed-off-by: Daniel Farrell<EMAIL_ADDRESS>

Interesting failure in CI:
[00:03:27.012249] --- FAIL: TestSyncer (9.95s)
[00:03:27.012260]     testing.go:853: race detected during execution of test
[00:03:27.012515] FAIL

Same failure again after re-running. Any idea @tpantelis?

Same failure again after re-running. Any idea @tpantelis?

This is fixed by https://github.com/submariner-io/admiral/pull/49/commits/56bb35c358eee21260d7624d257ee93942e8375e.  We  can merge this as its docs only.


Add C++ library

As a C++ developer I would like to use libraries in my C++ code. The guide now uses a header only library (deps/nlohmann/json.hpp) in the CGI script chapter, but I would also like to know how to use a normal library with *.so or *.a files.

The Newton-Raphson root algorithm is implemented in boost::math and gsl.


Launcher shows blank page

https://perkeep.org/launch/ shows a blank page when visited. Upon further investigation it shows a little html but stops at the go-import meta tag in the head.
https://github.com/camlistore/camlistore/blob/c45893a69b93f240ce75af410d18331872321777/website/tmpl/page.html#L19
It seems that the domain variable is causing an error and not allowing the entire page to be loaded.

thanks, looking into it.

https://camlistore-review.googlesource.com/#/c/camlistore/+/12206


Mapping attribute to bypass extauth service

I have an endpoint on my authentication service that provides users info about themselves. Currently, there are two ways I've found to implement this and neither are great:

Status code hacks: I'm rewriting my 200 responses to other 2xx codes (201, 202, 207). Only works for requests without bodies. This breaks HTTP semantics, but is simple and effective
Overlay endpoints: set up the auth service as both authentication and regular service, do some weird hacks with rewrites, provide endpoints for auth and then a mirror of those endpoints that returns the real responses. In this case, a request to the user info endpoint hits the auth service twice. This is really messy and makes both perf and security compromises.

I don't like either of these options. It would be great if I could set an option on that mapping to have it skip the extauth service entirely.

Supported with bypass_auth now

can we use bypass_auth for spesific IP ? like whitelist IP


Add warning to store:dispatch docs

Coverage remained the same at 99.351% when pulling dc373ffb63d1348a5b56f6d8e9107c23b40239bd on Jaguar-515:master into efda50fa7059b2c9538e5d846ace296e13598398 on Roblox:master.

Could you explain in the description what situations this addresses? The way this is worded now doesn't seem accurate to me.

Apologizes for the late reply. I was busy with a lot of things at the time.
This addresses a situation where you intend to add an array/dictionary of values to an existing state without using any middleware.

Do you mean to say that arrays of values will overwrite each other instead of merging? Doesn't that depend on how your actions and reducers are written?

I did mean to say that.

I suspect this may be just a misunderstanding! When you dispatch an action, Rodux processes it via the reducers that you wrote. If you have a reducer that handles an action with a list of items, the reducer can be implemented in whatever way is useful.
The first example here in the docs demonstrates this; friendsReducer  outputs a new list that appends the new items from the action to the existing state.


A way to get current ABI name

Hi,
Can you add in gradle a way to we get current ABI name?
Example:
defaultConfig {
    minSdk 16
    targetSdk 33
    testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    consumerProguardFiles "consumer-rules.pro"
    externalNativeBuild {
        cmake {
            arguments "-DCMAKE_TOOLCHAIN_FILE=build/kotlin/${currentABI}/toolchain.cmake"
        }
    }
}

You can add a variable like ${currentABI} to represent the current ABI.
Thanks.

Thank you for your interest in Gradle!
This is an issue with the Android Gradle Plugin which is developed by Google and cannot be addressed in the Gradle Build Tool project.
Please open such Android-related issues on the Android Issue Tracker at https://source.android.com/docs/setup/contribute/report-bugs#filing-a-bug


Always require SNAT

After discussing with Mario Lopez (Private Endpoints PM) and the Networking GBB team we have decided to prescribe to use Azure Firewall Application rules for HTTPS and MSSQL private endpoints and to always implement SNAT when using an NVA or when using Azure Firewall Network Rules.

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL: https://github.com/MicrosoftDocs/azure-docs
Private repo URL: https://github.com/MicrosoftDocs/azure-docs-pr
We have closed this pull request. Please resubmit the updates through the private repo. For more information, [see the contributor guide].(https://docs.microsoft.com/en-us/contribute/)


PATCH request received as POST

Bug Report
Description
When sending a PATCH request to the API server it receives a POST request instead. However, when executing the generated curl command then the request is successful.
To Reproduce
Steps to reproduce the behavior:

Start Grafana docker run --rm -p 3000:3000 -e GF_SECURITY_ADMIN_USER=admin -e GF_SECURITY_ADMIN_PASSWORD=admin grafana/grafana:8.2.5
Execute the Kotlin code below
Grafana logs POST request with status 404 t=2021-12-02T08:28:47+0000 lvl=info msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=POST path=/api/orgs/1/users/1 status=404 remote_addr=<IP_ADDRESS> time_ms=30 size=24 referer=
The curl command generated by Fuel however works: curl -i -X PATCH -d "{\"role\":\"Admin\"}" -H "Content-Type:application/json" -H "Authorization:Basic YWRtaW46YWRtaW4=" http://localhost:3000/api/orgs/1/users/1

// using Kotlin 1.6.0 with Java 17 and latest Fuel 2.3.1

import com.github.kittinunf.fuel.core.FuelManager
import com.github.kittinunf.fuel.core.extensions.authentication
import com.github.kittinunf.fuel.core.extensions.jsonBody
import com.github.kittinunf.fuel.core.interceptors.LogRequestAsCurlInterceptor
import com.github.kittinunf.fuel.core.interceptors.LogResponseInterceptor
import com.github.kittinunf.fuel.httpPatch

object Main {
    @JvmStatic
    fun main(args: Array<String>) {
        FuelManager.instance.addRequestInterceptor(LogRequestAsCurlInterceptor)
        FuelManager.instance.addResponseInterceptor(LogResponseInterceptor)

        val (req, res, data) = "http://localhost:3000/api/orgs/1/users/1"
            .httpPatch()
            .authentication().basic("admin", "admin")
            .jsonBody("""{"role":"Admin"}""")
            .response()
    }
}

Expected behavior
PATCH request actually sends a PATCH request and not a POST.
Development Machine

OS: Arch Linux
IDE: IntelliJ
Fuel version: 2.3.1
Kotlin version: 1.6.0
Java version: 17

Smartphone or Emulator

Device: -
OS: -

This issue appears architectural design and may not have any sort of fix on Fuel's end, and requires work to be done on the server-side if possible, that or the use of another library.
A quote from Baeldung:

Fuel supports all HTTP verbs except for PATCH. The reason is that Fuel’s HttpClient is a wrapper over java.net.HttpUrlConnection which doesn’t support PATCH.
To side-step the problem, the HttpClient converts PATCH requests to a POST request and adds an X-HTTP-Method-Override: PATCH header, so we’ll need to make sure our APIs are configured to accept this header by default.

To get around this myself, I used Square's okhttp4 to send the PATCH request.

@gnarledrootsystems is correct.

Thanks for the clarification!


Research about the generation of OS packages (rpm, deb)

Description
We need to investigate how to produce production packages in rpm and deb formats.
Currently, we only generate production packages in tar.gz format. See #46.
Additional info
These are the tools used by CI/CD:

https://github.com/wazuh/wazuh-packages/tree/master/stack/indexer/rpm
https://github.com/wazuh/wazuh-packages/tree/master/stack/indexer/deb
https://github.com/wazuh/wazuh-packages/tree/master/stack/dashboard/rpm
https://github.com/wazuh/wazuh-packages/tree/master/stack/dashboard/deb

Research
Currently the main repo of Opensearch Dashboards contains scripts to generate deb and rpm packages. Testing it in my local machine, it fails with some error.
Researching on that, I found several issues with the same error:

https://github.com/opensearch-project/OpenSearch-Dashboards/issues/1748

https://github.com/opensearch-project/opensearch-build/issues/1887

It seems to be an error related to a tool called fpm, that happens only to some users. In my research, I found comments suggesting different tools to replace it. I will continue researching and testing.

I've been looking at the Opensearch Build repo, as it is mentioned in  https://github.com/opensearch-project/opensearch-build/issues/1545 that it uses rpmbuild instead of fpm due to some errors with fpm.

I've been looking at the tools used by CI/CD and was able to generate packages (from the Opensearch repo). Then I started modifying the tools locally to make them match our requirements in order to generate packages of our own repository.

I was able to generate a functional deb package based on our fork, and tested it in a VM.
The tools used by CI/CD consists in 3 parts:

Base: this generates a .tar.gz based on the Opensearch's own, but modifying the desired files for Wazuh.
Deb: this runs the base first, and then generates a deb package based on it.
RPM: this runs the base first, and then generates a deb package based on it.

To generate the deb package, I modified the base's builder.sh and generate_base.sh files, to allow the script to read a local file and also to remove the unnecessary steps that are already done on the fork.
Then I generated a .tar.gz with the normal yarn build --release --skip-os-packages from our fork, and a build from our security plugin that the script will install.
I was not able to generate a rpm package due to an error with some dependency of the Dockerfile:
ERROR [4/8] RUN yum install -y https://repo.ius.io/ius-release-el$(rpm -E '%{rhel}').rpm

I was able to generate a functional rpm package based on our fork, and tested it in a VM.
Additionally to the previously modified files, I also modified rpm's wazuh-dashboard.spec and Dockerfile, then from stack/dashboard/rpm ran ./build_package.sh --app-url https://packages-dev.wazuh.com/pre-release/ui/dashboard/wazuh-4.4.1-1.zip

Blocked by https://github.com/wazuh/wazuh-dashboard/issues/58, as it uses code generated in that issue.

Reviewed int https://github.com/wazuh/wazuh-dashboard/issues/72


Newsletter-198: Add Czech translation

Translation of Newsletter 198 into Czech language, first of its kind. Hope more will follow.
In the absence of translations of topics, I appended a Glossary section to the newsletter where I briefly explain some of the terms, for which there would otherwise be a dedicated topic page.

@nechteme wow, thank you for this! Ive built locally and checked the links.
I think the footnotes are a good short explanation. What do you think of adding a link in each footnote to the English topic for readers that wish to learn more?

adding a link in each footnote to the English topic

Good idea! I added links to topics and BIPs.

Yes, please. Went through the text once more and it is ready.

Lightly tested ACK. Reviewed the diff, built the site locally, skimmed the google translate of the newsletter and added index pages.  It all looks good to me, thanks so much @nechteme !


[Bug]: Integ test script for the SQL plugin is not compatible with Windows platform.

Describe the bug
Coming from opensearch-project/opensearch-build#2885, the SQL plugin added their customized integ test scripts to add catalog.json for the integ tests to run.
However, the script is not windows compatible and the error context is:
C:\Users\ADMINI~1\AppData\Local\Temp\2\tmpy7pqz4eh\sql\scripts\integtest.sh: line 102: /bin/opensearch-keystore: No such file or directory

To reproduce
Running integ test from our build repo for SQL on Windows platform.

@vamsi-amazon, I think you can fix this in scope of #1383


Publish timestamps for each test

At the moment we aren't publishing any timestamps, just test durations. It would be great to have support for timestamps.
One issue is that the JUnit format doesn't support timestamp in testcase elements, only in testsuite elements. This means that we'll probably have to wrap each testcase in its own testsuite. Note that testsuite elements can be nested.

Allure's JUnit XML plugin has some implementation details: https://github.com/allure-framework/allure2/blob/master/plugins/junit-xml-plugin/src/main/java/io/qameta/allure/junitxml/JunitXmlPlugin.java#L192-L196

This was done in #54: testcase elements now have a timestamp in them, as do flakyFailure, flakyError, retryFailure and retryError elements. All of these are extensions to the JUnit standard but seem to be justifiable ones in this context.


Generated project does not compile

Hi! First of all thanks for working on developing a tooling around AsyncAPI 😃
The following report is almost identical of the one I've just opened here: https://github.com/asyncapi/java-spring-cloud-stream-template/issues/58
Describe the bug
When using the example reference AsyncAPI definition (https://bit.ly/asyncapi) which is using camelCase for schemas, the generated project is not Java compliant and hence does not build.
The generated model classes (the schemas) are in a file named in camelCase.java whilst the class definition itself is in PascalCase.
The above example results in:

File name: dimLightPayload.java
Class definition: public class DimLightPayload

Here is the console output:
$ gradle compileJava

> Task :compileJava
.../src/main/java/com/asyncapi/model/dimLight.java:6: error: class DimLight is public, should be declared in a file named DimLight.java
public class DimLight {
       ^
.../src/main/java/com/asyncapi/model/dimLightPayload.java:14: error: class DimLightPayload is public, should be declared in a file named DimLightPayload.java
public class DimLightPayload {
       ^
.../src/main/java/com/asyncapi/model/lightMeasured.java:6:
error: class LightMeasured is public, should be declared in a file named LightMeasured.java
public class LightMeasured {
       ^
.../src/main/java/com/asyncapi/model/lightMeasuredPayload.java:14: error: class LightMeasuredPayload is public, should be declared in a file named LightMeasuredPayload.java
public class LightMeasuredPayload {
       ^
.../src/main/java/com/asyncapi/model/turnOnOff.java:6: error: class TurnOnOff is public, should be declared in a file named TurnOnOff.java
public class TurnOnOff {
       ^
.../src/main/java/com/asyncapi/model/turnOnOffPayload.java:14: error: class TurnOnOffPayload is public, should be declared in a file named TurnOnOffPayload.java
public class TurnOnOffPayload {
       ^
6 errors

> Task :compileJava FAILED

So the file name should be always switched to PascalCase as its being done with the class name itself (following Java conventions).
I've also find the problem in the section of messages:
  messages:
    LightMeasured:
      name: lightMeasured

where the name: of the message is in camelCase and also generates files and classes in the same incorrect way.
One should argue that the definition of the official sample API could be updated to turn schema names into PascalCase to help align conventions. In my personal guideline I always define schemas in PascalCase and parameters in camelCase, which semantically maps to classes (or data models) and arguments of a function respectively (I guess in Java and probably many other languages). What do you think @fmvilas ?
But giving the above thought aside, the Java/Spring generator should handle the casing properly 😁
How to Reproduce
npm install -g @asyncapi/generator
ag https://bit.ly/asyncapi @asyncapi/java-spring-template
gradle compileJava

Expected behavior
Let the generated code to compile out-of-the-box.
Thanks! 🙏 😃

You got me crazy here. I was looking at this issue and thought it was the other one, so was wondering where the heck is my comment 😄
Similarly, I think this should be fixed on the template. Would you mind opening PRs?

I'm not very sure if I will have time to inspect this in detail as to open a PR. For now I'm just testing the tooling and I faced this. Even I need to understand better the tech stack behind them. But in case I can have more spare time to invest or research in it I would like to do it. But honestly I don't think in this moment :-S

No problem, Gerard. Let us know if you start working on it. Just so we don't overlap. Thanks!

Hi @gerardbosch
Could you please check one more time?
I run generation:
docker run --rm -it -v $pwd/output:/app/output asyncapi/generator -o ./output https://bit.ly/asyncapi @asyncapi/java-spring-template --force-write
and all files starts with capital leter:

Hi @Tenischev, I've just tried again and it works now! I'm not very sure what happened when I first tried or which template version was running.
I think you can close the issue :)


Tesla Stock Price Prediction using Prophet

I want to create a prophet machine learning model that can predict the tesla stock price for future 30 days.
Assign me this issue
I am working under GSSOC'24

Hi, i got busy with leaderboard launch, assigned this issue to you


Incomplete list of Unread posts

 Issue by 00alis
Wednesday Oct 22, 2014 at 10:14 GMT
Originally opened as https://github.com/arduino/forum2/issues/52

The unread posts button does not seem to be returning the unread posts, only a very small handful.
This is not like it was before where you could see all the posts you had not read and even order them so that you could pick out the ones with no replies.
for reference
https://basecamp.com/2546761/projects/6328288/messages/32602572

Hello, is this still an issue?

The unread topics now appear to display correctly. However if you mark them "read" (there is a button) and then click the "-" sign next to that part of the forum you get:

No unread topics found since your last visit. Click here to try all unread topics.

If you "click here" then you get:

Database Error
Please try again. If you come back to this error screen, report the error to an administrator.

That last thing it's a duplicate of #154


initialize variables in wlr_surface.c

This fixes the following warnings/errors with -Werror set (default):
ninja: Entering directory `build'
[26/47] Compiling C object libwlroots.so.7.p/types_wlr_surface.c.o
FAILED: libwlroots.so.7.p/types_wlr_surface.c.o
cc -Ilibwlroots.so.7.p -I. -I.. -Iinclude -I../include -Iprotocol -I../protocol -I/usr/include/libdrm -I/usr/include/pixman-1 -I/usr/include/uuid -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O3 -DWLR_USE_UNSTABLE -Wundef -Wlogical-op -Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self -Wstrict-prototypes -Wimplicit-fallthrough=2 -Wendif-labels -Wstrict-aliasing=2 -Woverflow -Wmissing-prototypes -Wno-missing-braces -Wno-missing-field-initializers -Wno-unused-parameter -fmacro-prefix-map=../= -DHAS_LIBUUID=1 '-DICONDIR="/usr/share/icons"' -fPIC -MD -MQ libwlroots.so.7.p/types_wlr_surface.c.o -MF libwlroots.so.7.p/types_wlr_surface.c.o.d -o libwlroots.so.7.p/types_wlr_surface.c.o -c ../types/wlr_surface.c
../types/wlr_surface.c: In function ‘surface_commit_pending’:
../types/wlr_surface.c:235:55: error: ‘src_width’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
  235 |    float scale_x = (float)pending->viewport.dst_width / src_width;
      |                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~
../types/wlr_surface.c:233:8: note: ‘src_width’ was declared here
  233 |    int src_width, src_height;
      |        ^~~~~~~~~
../types/wlr_surface.c:236:56: error: ‘src_height’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
  236 |    float scale_y = (float)pending->viewport.dst_height / src_height;
      |                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~
../types/wlr_surface.c:233:19: note: ‘src_height’ was declared here
  233 |    int src_width, src_height;
      |                   ^~~~~~~~~~
../types/wlr_surface.c: In function ‘wlr_surface_get_effective_damage’:
../types/wlr_surface.c:1293:62: error: ‘src_width’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
 1293 |   float scale_x = (float)surface->current.viewport.dst_width / src_width;
      |                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~
../types/wlr_surface.c:1294:63: error: ‘src_height’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
 1294 |   float scale_y = (float)surface->current.viewport.dst_height / src_height;
      |                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.

Maybe it is not a good idea to initialize to 0?

Hm, this will just cause a division by zero in case the buffer size is not divisible by the scale.
I wonder if we should keep the scale check in surface_state_viewport_src_size. Maybe we should move it out of the function into surface_state_finalize.

I wonder if we should keep the scale check in surface_state_viewport_src_size. Maybe we should move it out of the function into surface_state_finalize.

This would have to be answered by someone else I am afraid as I do not know how it all fits together.

This is preventing wlroots-git from building in the AUR.
FWIW I think the warning is just wrong here, initializing these variables is pointless, and one should disable the warning, e.g., by using the proper pragma to turn it off locally here.
Because of warnings with false-positives / incorrect diagnostics, it makes little sense to use -Werror as a default for everybody.
I think -Werror should be optional, and instead CI should always turn it on to catch these things.

If you want to initialize this variables to something, initialize them to some invalid value, e.g., 0 or -1, and after calling the API, check that this value has changed.

I think -Werror should be optional, and instead CI should always turn it on to catch these things.

NACK. See https://github.com/swaywm/wlroots/wiki/Packaging-recommendations.

See the first commit in https://github.com/swaywm/wlroots/pull/2742.

fixed with #2742


Distance should be validated to be numbers only

When I enter a distance on an offer, I shouldn't be able to type text like "5 miles". It should restrict to numbers only

Change label to "Distance (mi):"


Instructions for building Goggle Emulator on host.

Thank you @SumolX
I specifically added the libsdl2-dev package from default Ubuntu repo.
Emulator usage notes:
a = right button press
w = wheel up
s = wheel down
d = wheel center press
F11 to toggle full screen (where applicable)
Other items of note:
-simulated analog preview is not resized to fit 1080 screen?
-add ability to set goggle batch (1/2) to allow simulation of analog module power option?

Thank you @SumolX
I specifically added the libsdl2-dev package from default Ubuntu repo.
Emulator usage notes: a = right button press w = wheel up s = wheel down d = wheel center press F11 to toggle full screen (where applicable)
Other items of note: -simulated analog preview is not resized to fit 1080 screen? -add ability to set goggle batch (1/2) to allow simulation of analog module power option?

Let's discuss in discord but as for live view I have a PR already submitted which fixes this issue.


Add ability to disable automated sync when new commit merged

What would you like to be added:
Some developers may want to disable the auto-sync when a new commit was merged. The deployment will be triggered only by clicking Sync button on the web UI.
Why is this needed:

Resolved.
/close


Dialog is break

Yeah, and I personally can't even get it to load the backdrop for me when I try to run it in my local project. I've done the CLI installation, but dialog__backdrop doesn't appear to be getting generated by panda, even after running prepare. Something feels just plain off about the implementation of Dialog.

It seems an issue just with demo.
The buttons should not have width=full here in demo https://github.com/cschroeter/park-ui/blob/main/components/react/src/demos/dialog.demo.tsx#L21C1-L28C21
by removing this works fine.
in case it should have flex: 1 to make both buttons full width inside dialog.


Blade directive making textarea hidden

Basically when I call the @ckeditor my textarea becomes hidden, nothing else changes, if I remove the directive all is normal, does anyone have an idea how to fix this?

You might not have applied the ID element to your textarea? Do you see any javascript errors in the console?


Require authentication for safekeeper/pageserver metrics

Currently endpoint::make_router() exposes /metrics without any checks. However, it may contain relatively sensitive information like tenant/timeline IDs. We should require a managemental token instead.
Careful: not to break Grafana.
Careful: implement after #1856 is merged, otherwise there is not much auth in Safekeeper.
Careful: do not merge until #1856 is correctly configured on staging/prod, requires configuration updates. Even then, coordinate with SREs.

we don't need to auth metrics, as they contain aggregated info and anonymized ids only
it makes much more sense to clean up logs first


Brazilian Flags

closes #4304

Can you insert the following lines?
"ksp_version": "any",
"comment": "flagmod",

Merging, will fix the flagmod stuff later. Thanks!


Save the ppt in browser

Hi guys,
How do I do to send the generated power point to the client side ?
Thanks in advance

@xksusha , save the file in a temporary location on the server, then in your controller send it through send_data:
http://api.rubyonrails.org/classes/ActionController/DataStreaming.html#method-i-send_file


Document libraries layout in contribution guide.

As we complete MicrosoftDocs/quantum-docs-pr#355, we should ensure that we document somewhere the way that we use files, folders, and namespaces, so that contributors can more easily fit their work into our existing structures.

Hi @cgranade, I'm looking at your suggestion. Would you be able to expand a bit on what exactly you had in mind?
I'm assuming you want to document this repository: https://github.com/microsoft/QuantumLibraries
Would the layout not be better documented in the repository readmes where the reader can immediately see and interact with the file/folder structure?
I guess information on namespaces would indeed be better located in the contribution guide. If so, what do you think of adding a page to the contribution guide titled 'Contributing to Libraries'?

Thank you very much for your comments, these will be helpful in updating the contribution guide!
Closing this issue as this item has been entered into the backlog.


Same background fill color rendered differently by Compose and Swing / Java2D

Run this under the latest alpha build:
import androidx.compose.foundation.background
import androidx.compose.foundation.layout.Column
import androidx.compose.foundation.layout.Row
import androidx.compose.foundation.layout.fillMaxSize
import androidx.compose.foundation.layout.fillMaxWidth
import androidx.compose.ui.Alignment
import androidx.compose.ui.Modifier
import androidx.compose.ui.awt.SwingPanel
import androidx.compose.ui.unit.dp
import androidx.compose.ui.window.*
import javax.swing.JPanel

fun main() = application {
    val state = rememberWindowState(
        placement = WindowPlacement.Floating,
        position = WindowPosition.Aligned(Alignment.Center),
        size = WindowSize(200.dp, 180.dp)
    )

    Window(
        title = "Panels",
        state = state,
        undecorated = true,
        onCloseRequest = ::exitApplication,
    ) {
        Column(modifier = Modifier.fillMaxSize()) {
            // This is Compose content
            Row(
                modifier = Modifier.fillMaxWidth().weight(0.5f)
                    .background(androidx.compose.ui.graphics.Color(0xfff9be84))
            ) {}

            // This is Swing content
            SwingPanel(
                modifier = Modifier.fillMaxWidth().weight(0.5f),
                factory = {
                    JPanel().apply {
                        background = java.awt.Color(0xf9be84)
                    }
                }
            )
        }
    }
}

See the difference in how the same color #F9BE84 is rendered.

Top half rendered by Compose, bottom half rendered by Swing. There is a noticeable difference in vibrancy / saturation.

I compared the colors with the default macOs Pages application - the color is the same as in Compose.
Probably Swing doesn't apply color correction which is set in the system settings.
In that case, the color correction should be applied manually to the Swing component, via skiko converters somehow (don't know yet how exactly).
Another option is to provide API to change color correction. Something like ComposeWindow.setColorSpace(ColorSpace?), but it is not easy, and probably will be inconsistent with the rest of the system.
P.S. on Windows colors are the same.

The real-world interop examples are going to be more complex than this, with multiple Swing components painted by the installed look-and-feel, so it might not be easy to go in and tweak every single background / foreground color on the Swing side.
When I run "Digital Color Meter" app and compare the colors, I see:

The requested color F9BE84 is red=249, green=190, blue=132
Swing paints red=245, green=190, blue=132
Compose paints red=240, green=191, blue=140

Swing is not exactly what was "requested", but much closer. I can't say which one is the "right" one, but this is going to be problematic for interop.

Yes, it is definitely an issue for interop.
On one thing I am certain - we should be close to the colors which are dictated by OS.
I wish there was a method in Swing that allows us to change the color space of the Swing Component. If we won't find such method, all we can do is to provide a helper method to convert colors, or method to change color space for Compose.

That's certainly something that I can plug into Radiance on the Swing side. Some sort of a Color -> Color mapping that, when present, is applied on all colors supplied by the look-and-feel, as well as by the application code set on core Swing components like panels, etc.
There's still going to be direct painting with paintComponent drawing directly on Graphics2D, so it might not fully solve it without changing that application code.

When using "Digital Color Meter", select "Display in sRGB" from the drop down to see the original values you've specified. I suspect what might be happening is that either Swing or Compose is not tagging its backing window as sRGB at the OS level. Using your screenshot, it seems Compose is doing the right thing, but Swing is not (a problem I had to fix in Android Studio for exactly the same reasons btw; my fix was to tag the backing window as sRGB).

Is there an API to do this on AWT Window or Compose's ComposeWindow?

Not that I know of no.

Now this looks like a job for Skiko :)

Alternatively Skiko could convert all colors to the display gamut :)

Whichever magic way that treats the same RGB values to create the same final color on the screen (even if technically it might be "off" in one of the color meter modes) is fine with me

Color spaces are already there - https://github.com/JetBrains/skiko/blob/master/skiko/src/commonMain/kotlin/org/jetbrains/skia/ColorSpace.kt

-ish :p

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


font-family property not used in typeset mixin

Hi there!
I've been digging into MegaType and noticed that the font-family property of the font maps as defined in the _config.scss file (see below):
$sans: (     font-family: '"Helvetica Neue", Arial, sans-serif',     regular: normal,     bold: bold,     cap-height: 0.71 );
are never utilized in the typeset() mixin to actually set the font-family property on the selector.
I believe this can be resolved by adding the following lines to the typeset() mixin in the _typography.scss file:
font-family: font-family-fallback-of($font);
font-family: font-family-of($font);
I'm happy to make a pull request if you agree that this was an oversight. However, if I'm not utilizing the mixin appropriately, could you help me understand what I'm missing?

Adding some conditional checks would be a good idea as well:
@if map-get($font, font-family-fallback) != null {
    font-family: font-family-fallback-of($font);
}

@if map-get($font, font-family) != null {
    font-family: font-family-of($font);
}

Hi bbelix,
Although this might seem counterintuitive at first, for optimisation reasons it's not intended that the typeset mixin would directly output the font-family property. When you consider that the typeset mixin is intended for use at subsequent breakpoints, it makes sense not to repeat the output of this property. For example, consider the following:
@include typeset($sans, 14px, 1, 0, 1);
font-family: font-family-of($sans);

@include min-width(1) {
    @include typeset($sans, 16px, 1, 0, 2);
}

@include min-width(2) {
    @include typeset($sans, 18px, 1, 0, 2);
}

In this example, the font-family property currently only gets output where we declare it explicitly. If we were to output it with the typeset mixin, it would be output 3 times, and the latter 2 would be redundant.
However we do need to still feed in the font variable to this mixin so that we can retrieve it's stored cap-height for use in rhythm math.


Product Categories with multiple tags aren't displayed in the marketplace

Any product category with multiple tags is not displayed, an example of this in the demo data is the Storage product category that has the storage and cdn tag.

This is working as intended. Closing as a duplicate of #1049


Release 4.2.0

A bunch of new stuff has gone in, we should release a new version once the few pieces of in-flight work are done:

[x] https://github.com/alexa-js/alexa-app/pull/276
[x] The questions in https://github.com/alexa-js/alexa-app/pull/271 (end-to-end testing, and what the type definitions should be for getSession())
[x] Any more type definition discrepancies that shake out as a result of aforementioned new tests

I'll cut the release, really just leaving this as a note for myself.

Done!

Thans @lazerwalker !


⚠ ClamAV has degraded performance

In 1476709, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 72 ms

Resolved: ClamAV performance has improved in 5774233.


Doc: Understanding the impact of CO-events

Close issue 303.
What?
Correct the statistical inference statement.
Why?
A user applying the suggested logic, with a different sample,
would very likely draw an incorrect inference.
The statement makes sense only because we know a CO-event
took place.  Generally the issue is more subtle.
How?
Provide a note indicating testing for changes in
sample distributions is out of scope for Goose.
However, we provide some guidance for the novice user
that is not an unreasonable starting point.
Signed-off-by: Begley Brothers Inc<EMAIL_ADDRESS>

Can you re-roll w/o the unrelated white space cleanups? It makes it difficult to review the actual intended changes. (Ideal submit the white-space cleanup as it's own PR.)


Proper path handling and fix xpsnr for windows

Fix xpsnr for windows for real this time
Allow spacing to be flexible for regex, and ignore cases (assuming that linux has different output for xpsnr, not because maybe the script was made using an older version of xpsnr that might have a different output)
Hopefully this works on Linux

We'll have to do the regex thing in stage 3 differently, this implementation causes a "division by 0" error, implying the regex failed for every for loop. Stage 1 and 2 seems to be functionning fine on Linux.

Hi can you check again?

No there's something going on with 2.5 at large, the current version of the script also has the ZeroDivisionError: division by zero error on avg_weighted = sum_weighted / count

I just tried the script via ArchWSL, and I don't know why it doesn't work for you, are you using ffmpeg 7.1? If you're using custom ffmpeg 7.0 with xpsnr, can you show me one of the lines of xpsnr.log?

I just tried the script in this PR via ArchWSL, and I don't know why it doesn't work for you. Are you using ffmpeg 7.1?
If you're using custom ffmpeg 7.0 with xpsnr, can you show me one of the lines of xpsnr.log?

In fact, I'm running ffmpeg 6.0 compiled with xpsnr support.
This is what a line of log file looks like:
n:    1  XPSNR Y: inf  XPSNR U: inf  XPSNR V: inf

Your commits seems to have more or less fixed the issue on my end, except for the fact that some frames (pure black backgrounds) sometimes have an inf score in both chroma planes which obviously makes the script fail.


fixed warnings in time_histogram function

The fix is rather easy: rely on advanced BinnedSpikeTrain rounding error routine.

Coverage increased (+0.01%) to 89.912% when pulling 0736681b55d32ca798dd82ae25c5bd2162eba1be on INM-6:fix/time_histogram_warn into 13be6fb9b047e165d4db3a9a87f51a4db141a09c on NeuralEnsemble:master.


Cassandra triggers - Support for Set dataType

Codecov Report

Merging #581 into cassandra-triggers will not change coverage.
The diff coverage is n/a.

@@                  Coverage Diff                  @@
##             cassandra-triggers     #581   +/-   ##
=====================================================
  Coverage                 31.99%   31.99%
  Complexity                 1210     1210
=====================================================
  Files                       172      172
  Lines                     15116    15116
  Branches                   2396     2396
=====================================================
  Hits                       4836     4836
  Misses                     9557     9557
  Partials                    723      723

Continue to review full report at Codecov.

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


simplify module config UX via automatic sparse loading of required files

Goals

Simplify module loading further by just always defaulting the "context" to the root of the git repo

for the local case, we find-up a .git and otherwise default to the source root path specified so everything stays sandboxed
users no longer need to think about running dagger init in the right place, there's no root/root-for/etc. settings, etc.
the tradeoff is we need to be much more intelligent about only sparsely loading exactly the files/dirs we need based on local deps, local custom sdks, files that are required by the SDKs in use and custom include/exclude settings provided by the user. This also needs to apply recursively to any deps/sdks/files needed in the whole context

Add support for dagger init --source <path> and dagger develop --source <path> for customizing the subdirs at which actual module source code is located

if not specified --source defaults to dagger/. See this discord thread for discussion on the default value.

Example Usage
--source usage
One of the primary use cases --source as an arg to init/develop enables is putting dagger.json in the root of a repo without necessarily polluting the root with SDK source files, e.g.

from root of local git repo clone, run dagger init --name foo

dagger.json is created in your cwd by default, so in this case it's in the root of the repo

run dagger install to add some deps
decide you want to start writing some code, so run dagger develop --sdk=go --source=some/subdir

you'll now see main.go and other go sdk files at under some/subdir in the repo
dagger.json is also updated to set "source": "some/subdir"
If --source hadn't been specified, it would have defaulted dagger/go (with the last element always being set to the name of the sdk)
--source=. is valid too still, just not the default

Your module is still the default one when in the root of repo, so you can do e.g. dagger call foofunc ... from the root

This also applies to anyone else git clone'ing your daggerized repo for the first time
It also applies to anyone invoking/installing your module from its remote git ref, e.g. dagger install github./com/org/repo is enough since they just need to point to the root of the repo

This is just one use case, generally speaking the goal here is to be flexible while retaining sane defaults and sandboxing everything to the .git context.
Terminology

Context

this is the dir that is loaded into the engine and provided to SDKs for codegen. End modules don't get implicit access to the whole context; it's only used to support modules that use go.mod/package.json/etc. from parent dirs and to load any deps/custom sdks/etc. local to the module
For local modules, this is a sparsely loaded directory rooted at the nearest parent dir containing .git (or the dir containing dagger.json as a fallback)
For git modules, this is just the git repo. As noted in the code, support for sparsely loading from git remotes is a TODO and will require https://github.com/dagger/dagger/issues/6292)

Source Root Path

this is the dir under Context (or the same as it) that contains dagger.json for a module.
it's important in that if you specify a module ref, it should point to this dir. e.g. dagger call -m github.com/foo/bar/the/sourceroot ...

Source Path

this is the dir that contains the actual module source implementation (i.e. main.go, src/index.ts, src/main.py, etc.)
It can be set via --source and defaults to dagger/ (see above sections for more usage details)

Implementation notes

SDKs now have an additional method RequireFiles that allows them to specify which files they need in order to load (i.e. go.mod is one required by the go SDK)

This is currently a bit barebones in that it's just a flat list of glob patterns. Better would be if this method was given the ModuleSource arg and used it to determine very precisely what's needed (i.e. right now we require **/go.mod but really we only needs ones that are in parent dirs or are referenced by those in parent dirs). But saving that optimization for the future.

The sparse loading of local dirs uses the filesync API to first walk the whole DAG of local deps and read dagger.json from each one. Code

Once that's done, we collect all the include/exclude values and invoke all the SDKs encountered to determine which files they strictly require and finally do a single local import of everything we need. Code
This required adding an extra method for just stat'ing paths, which enabled the find-up of .git from the engine code. Code

This effort required another iteration on the Module/ModuleSource API, though it amounted to mostly re-arranging rather than anything new besides the sparse loading logic

The biggest rearrangement is the WithName/WithSDK/WithDependencies moved from Module to ModuleSource. This was required because those apis can actually change what is required from the context and trying to later re-load those files from their original source while also keeping source IDs pure was practically speaking not really possible.
The idea is essentially that all the configuration happens on ModuleSource and once AsModule is called it's immutable
I actually think all the code around this ended up even cleaner than before somehow even though it was only changed to get things working for this feature 🤷♂🎉

It can be set via --source and defaults to dagger/<sdk name>

What's the arguments/use cases for this default?

It can be set via --source and defaults to dagger/<sdk name>

What's the arguments/use cases for this default?

@helderco mentioned in the PR description briefly but just updated that with more details, let me know if it makes sense

Hm, I have to agree with @helderco - I think dagger/ by itself is a reasonable default. I don't think it's particularly common to have lots of different sdks in one repo. And even if there are, having them all named just by their sdk isn't great - I'm going to want to rename these to dagger/main, dagger/helper, etc, and actually describe their purpose, not the language they're written in.
Actually, the most "expected" option for me as a user would be to default to . - but error out if the current directory has contents, and require the user to use --source. This is familiar to a lot of init tools, like git, or hugo.
That said, I'm also happy with dagger or ci or any variation of the above honestly - as long as we don't have the SDK in there, I can't see why I'd ever want to use the default in that case (I'd just always specify --source for my own use).

One thing to clarify is that it's still completely valid to put modules all over the place as it was previously.

Yes, I said it took "getting used to" because of the change in defaults. Felt more "distributed" and now it feels more "centralized". 🙂
I'll still want to add --source=. on one hand, but no longer need --name on the other (at least in most cases). 🙂
Being able to set the target dir is great! 🙌 Really disliked all the mkdir && cd && init.
But if --source becomes relative to the workdir for consistency, and I provide a target path, as long as I still prefer putting the sources in ".", I'll have to repeat it:
dagger init --sdk=python --source=some/sub/dir some/sub/dir

But if --source becomes relative to the workdir for consistency, and I provide a target path, as long as I still prefer putting the sources in ".", I'll have to repeat it:

This is true, but I still feel pretty strongly that it's worth being consistent here even if it can result in more verbosity for situations like that. All this path arithmetic is a huge headache to think about and easy to mess up so I'd rather we just have a consistent model of "paths are relative to your cwd". Also works better with tab shell completion since that also has the same assumption.

This is true, but I still feel pretty strongly that it's worth being consistent here even if it can result in more verbosity for situations like that.

Of course, I agree.

Thank you everyone for the reviews! I am making updates discussed above about having --source always be relative cwd (lots of fun corner cases), but very small change. After that I'll update based on the rest of the comments and merge 🚢


[script] fix bug preventing script/build from calling script/build_example_apps

https://github.com/openthread/ot-efr32/blob/1f12e7364adbd126f984bed45ebfea6057dff0df/script/build#L329-L335
The assignment above causes the if below to always evaluate to false, causing the silabs apps to always be skipped. This PR fixes the issue
https://github.com/openthread/ot-efr32/blob/1f12e7364adbd126f984bed45ebfea6057dff0df/script/build#L370

@jwhui please review this when you get a chance. Thanks!


Update silx-view mime type association

Closes #1549

I still have problem with this PR
No idea how to create the default association. Everything looks fine but nautilus dont fine any default application.
$ sudo cp package/desktop/org.silx.SilxView.desktop /usr/share/applications/
$ sudo cp package/desktop/silx.xml /usr/share/mime/packages/

# update the database
$ sudo update-mime-database /usr/share/mime
$ sudo update-desktop-database

Here the associations looks fine:
$ more /usr/share/applications/mimeinfo.cache | grep -i silx
application/x-hdf=hdfview.desktop;org.silx.SilxView.desktop;
application/x-silx-hdf5=org.silx.SilxView.desktop;
application/x-silx-nexus=org.silx.SilxView.desktop;
application/x-silx-specfile=org.silx.SilxView.desktop;
image/tiff=display-im6.q16.desktop;display-im6.desktop;evince.desktop;gimp.desktop;evince-previewer.desktop;rawtherapee.desktop;eog.desktop;org.silx.SilxView.desktop;
image/x-silx-cbf=org.silx.SilxView.desktop;
image/x-silx-edf=org.silx.SilxView.desktop;
image/x-silx-marccd=org.silx.SilxView.desktop;
image/x-silx-numpy=org.silx.SilxView.desktop;

But no default application is found
$ xdg-mime query default image/png  # it works for a PNG file
eog.desktop
$ xdg-mime query default image/x-silx-edf  # No output
$ xdg-mime query default application/x-hdf  # No output for the default hdfviewer

The custom mimetype is right, but the association with the application is not found:
$ xdg-mime query filetype ../data/edf/medipix.edf
image/x-silx-edf
$ xdg-open ../data/edf/medipix.edf
gvfs-open: ../data/edf/medipix.edf: error opening location: No application is registered as handling this file

I try to create a /usr/share/applications/silx/mimeapps.list contains default associations, but while /usr/share/applications/mimeinfo.cache is fine, i dont really understand why we should duplicate this informations. Maybe we have to call xdg-mime default <application> <mimetype> at the post installation of the scripts?
Do you have any idea @picca? Some hint can be very useful.

I have never done this by myself, sorry, but on my stretch I have this
picca@diffabs6:~/hkl$ xdg-mime query default application/x-hdf
hdfview.desktop
Maybe somethig else is done during the installation of the package...

Here the files of the hdfview package.
/.
/usr
/usr/bin
/usr/bin/hdfview
/usr/share
/usr/share/applications
/usr/share/applications/hdfview.desktop
/usr/share/doc
/usr/share/doc/hdfview
/usr/share/doc/hdfview/changelog.Debian.amd64.gz
/usr/share/doc/hdfview/changelog.Debian.gz
/usr/share/doc/hdfview/copyright
/usr/share/icons
/usr/share/icons/hicolor
/usr/share/icons/hicolor/16x16
/usr/share/icons/hicolor/16x16/apps
/usr/share/icons/hicolor/16x16/apps/hdfview.png
/usr/share/icons/hicolor/16x16/mimetypes
/usr/share/icons/hicolor/16x16/mimetypes/application-x-hdf.png
/usr/share/icons/hicolor/22x22
/usr/share/icons/hicolor/22x22/apps
/usr/share/icons/hicolor/22x22/apps/hdfview.png
/usr/share/icons/hicolor/22x22/mimetypes
/usr/share/icons/hicolor/22x22/mimetypes/application-x-hdf.png
/usr/share/icons/hicolor/24x24
/usr/share/icons/hicolor/24x24/apps
/usr/share/icons/hicolor/24x24/apps/hdfview.png
/usr/share/icons/hicolor/24x24/mimetypes
/usr/share/icons/hicolor/24x24/mimetypes/application-x-hdf.png
/usr/share/icons/hicolor/32x32
/usr/share/icons/hicolor/32x32/apps
/usr/share/icons/hicolor/32x32/apps/hdfview.png
/usr/share/icons/hicolor/32x32/mimetypes
/usr/share/icons/hicolor/32x32/mimetypes/application-x-hdf.png
/usr/share/icons/hicolor/48x48
/usr/share/icons/hicolor/48x48/apps
/usr/share/icons/hicolor/48x48/apps/hdfview.png
/usr/share/icons/hicolor/48x48/mimetypes
/usr/share/icons/hicolor/48x48/mimetypes/application-x-hdf.png
/usr/share/icons/hicolor/64x64
/usr/share/icons/hicolor/64x64/apps
/usr/share/icons/hicolor/64x64/apps/hdfview.png
/usr/share/icons/hicolor/64x64/mimetypes
/usr/share/icons/hicolor/64x64/mimetypes/application-x-hdf.png
/usr/share/icons/hicolor/96x96
/usr/share/icons/hicolor/96x96/apps
/usr/share/icons/hicolor/96x96/apps/hdfview.png
/usr/share/icons/hicolor/96x96/mimetypes
/usr/share/icons/hicolor/96x96/mimetypes/application-x-hdf.png
/usr/share/java
/usr/share/java/jhdfview.jar

Here the desktop file
[Desktop Entry]
Exec=/usr/bin/hdfview %F
MimeType=application/x-hdf;
Name=hdfview
Name[de]=hdfview
Name[en]=hdfview
Comment=HDF4/5 Data Browser
Comment[DE]=HDF4/5 Daten Browser
Comment[EN]=HDF4/5 Data Browser
Terminal=false
Type=Application
X-MultipleArgs=true
Categories=Science;Physics;DataVisualization;Education;
Icon=hdfview

So it seems that this is enought.
Maybe just let this like this and  we will see if it works for the next silx package :))

Thanks, i will try it.
Maybe it works cause application/x-hdf is already defined.

Thanks a lot. My .local was polluted.
Then it was working.
You will be able to open h5, edf, cbf, tif, spec and few others with a double click.

alleluia :))


Use log_static() for constant data in DNA example.

What
Just a tiny little thing that was bugging me: the DNA example now uses log_static() for all the non-animated data logged at the beginning. This gives better results when viewing with a time range query — otherwise the left, right, and scaffolding always disappear if the time range doesn’t include the beginning of the recording.
Here is the new appearance with a 0.5 second time range; previously, only the gray points would be visible:

Checklist

[X] I have read and agree to Contributor Guide and the Code of Conduct
[X] I've included a screenshot or gif (if applicable)
[ ] I have tested the web demo (if applicable):

Using examples from latest main build: rerun.io/viewer
Using full set of examples from nightly build: rerun.io/viewer

[X] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[X] If applicable, add a new check to the release checklist!
[X] If have noted any breaking changes to the log API in CHANGELOG.md and the migration guide

PR Build Summary
Recent benchmark results
Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

Nice -- I've been meaning to do that for a while.
log_static is deprecated though, lemme fix that.

(marking as draft to relax the review queue til then)

taking this over, I too want this too :)

✅  tested C++ & Python manually (you never know, weirder things have broken...)

ci:

known rust failure, fix is up
C++ runner running out of space. okay. 🤦


Cannot add Wait task to release pipeline

Have just donwloaded this release pipeline extension, but it does not allow me to add it as a task as it does not show the Add button.

Is there something addional I need to do?

Found the answer: had to restart Azure DevOps portal


All-NaN slice encountered

Hi,  I encountered the following problems when testing example.When I convert the model from'bhac15'to' parsec ', the returned results are all null  values
els_file='els.txt'
els_obj=SampleObject(els_file,id_type='EDR3',verbose=0,ext_map='leike') result=els_obj.get_params('parsec',age_range=[1,300],n_try=200,save_maps=True)
/home/yang/anaconda3/envs/madys/lib/python3.7/site-packages/madys/madys.py:3299: RuntimeWarning: All-NaN slice encountered
if np.nanmin(np.abs(iso_data_r[use_i,w[h]]-ph))<0.2: b[h]=True #if the best theor. match is more than 0.2 mag away, discards it

Hi! The problem lies in the fact that in the alpha release I have not made available the full PARSEC grids. As mentioned at the beginning of the notebook, for the moment only ages between [500, 7000] Myr are available for PARSEC models. That's why an age_range between 1 Myr and 300 Myr results in a full-nan slice. In any case, I will soon make public a beta version with the full set of models :)

Hi! The problem lies in the fact that in the alpha release I have not made available the full PARSEC grids. As mentioned at the beginning of the notebook, for the moment only ages between [500, 7000] Myr are available for PARSEC models. That's why an age_range between 1 Myr and 300 Myr results in a full-nan slice. In any case, I will soon make public a beta version with the full set of models :)

Thank you for your answer. This program is  helpful to my research, so I hope you can complete it smoothly. Looking forward to the release of the beta version :)

Thank you very much! I'm so glad to hear that my tool is helpful for your research :) You'll find the beta version here in a few days, hopefully!


Log the value of LogWhat when it is decided

What does this PR do?
(another merge into #12440)
Adds debug logging of LogWhat.
Motivation
Help debugging both in QA and in support cases (where, for example, we might wonder why the agent chose to log from socket instead of files)
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the config template has been updated.

Looks like I mixed up the cherry-pick, yeah.

fixed!


Updated NPSP Automation Scripts

Critical Changes
Added Creating HouseHold with an Email
Added Creating HouseHold with an Address (Via Google Search)
NPSP Tests Row#12
@dashattuck @jessingrass
Changes
Issues Closed
New Metadata
Deleted Metadata

Thank You @dashattuck


feat: Add Dependabot support

Should automatically update the Node.js packages. For example, the latest version of ajv compatible with package.json is 6.12.6, released 11 Oct 2020, while the latest version is https://github.com/ajv-validator/ajv/releases/tag/v8.8.1.

Thanks. I'm not 100% sure about this. What does it do? Does it notify me about changes (e.g. create PRs) or does it automatically upgrade the package.json? The latter would not be a good idea as it could break things and we can't really tell whether it's breaking or not without a human checking because this package has no tests (as it was meant to be a proof of concept and doesn't have a lot of dev resources assigned, but obviously is used more now).

Thanks. I'm not 100% sure about this. What does it do? Does it notify me about changes (e.g. create PRs) or does it automatically upgrade the package.json? The latter would not be a good idea as it could break things and we can't really tell whether it's breaking or not without a human checking because this package has no tests (as it was meant to be a proof of concept and doesn't have a lot of dev resources assigned, but obviously is used more now).

It creates PRs which include things like the change log and a link to a diff, so it's a super handy way to keep up to date.
Adding more automated tests to make sure this doesn't break anything would be great. I might have time to help out with that, since we're pretty strongly dependent on this validator for our STAC extensions already.

Alright, I'm fine with PRs. Do I still need to enable something in the repo settings or so?
Happy to accept PRs for tests! :-)

Alright, I'm fine with PRs. Do I still need to enable something in the repo settings or so?

I believe Dependabot is enabled by default in GitHub. But we'll see tomorrow :grin:

Happy to accept PRs for tests! :-)

Cool, I'll keep that in mind.

First PRs have already been merged, works!