404 while access the swagger UI

io.springfox
springfox-boot-starter
3.0.0-SNAPSHOT

While deploying i am getting warning  like
2020-06-27 14:32:02.791 Apples-MacBook-Pro-7.local  WARN67287 --- [           main] d.s.r.o.OperationImplicitParameterReader :Unable to interpret the implicit parameter configuration with dataType: , dataTypeClass: class java.lang.Void
2020-06-27 14:32:02.807 Apples-MacBook-Pro-7.local  WARN67287 --- [           main] Validator                                :ERROR [ModelSpecification.spec] At least one type of specification is required
2020-06-27 14:32:02.809 Apples-MacBook-Pro-7.local  WARN67287 --- [           main] d.s.r.o.OperationImplicitParameterReader :Unable to interpret the implicit parameter configuration with dataType: , dataTypeClass: class java.lang.Void
2020-06-27 14:32:02.809 Apples-MacBook-Pro-7.local  WARN67287 --- [           main] Validator                                :ERROR [ModelSpecification.spec] At least one type of specification is required
2020-06-27 14:32:02.809 Apples-MacBook-Pro-7.local  WARN67287 --- [           main] d.s.r.o.OperationImplicitParameterReader :Unable to interpret the implicit parameter configuration with dataType: , dataTypeClass: class java.lang.Void
2020-06-27 14:32:02.809 Apples-MacBook-Pro-7.local  WARN67287 --- [           main] Validator                                :ERROR [ModelSpecification.spec] At least one type of specification is required
2020-06-27 14:32:03.229 Apples-MacBook-Pro-7.local  WARN67287 --- [           main] d.s.r.o.OperationImplicitParameterReader :Unable to interpret the implicit parameter configuration with dataType: , dataTypeClass: class java.lang.Void
2020-06-27 14:32:03.229 Apples-MacBook-Pro-7.
And while accessing the swagger link below error is coming.
org.springframework.web.server.ResponseStatusException: 404 NOT_FOUND
at org.springframework.web.reactive.resource.ResourceWebHandler.lambda$handle$0(ResourceWebHandler.java:325) ~[spring-webflux-5.1.7.RELEASE.jar:5.1.7.RELEASE]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:44) [reactor-core-3.2.9.RELEASE.jar:3.2.9.RELEASE]
at reactor.core.publisher.MonoLift.subscribe(MonoLift.java:45) [reactor-core-3.2.9.RELEASE.jar:3.2.9.RELEASE]
at reactor.core.publisher.Mono.subscribe(Mono.java:3710) [reactor-core-3.2.9.RELEASE.jar:3.2.9.RELEASE]
at reactor.core.publisher.FluxSwitchIfEmpty$SwitchIfEmptySubscriber.onComplete(FluxSwitchIfEmpty.java:75) [reactor-core-3.2.9.RELEASE.jar:3.2.9.RELEASE]
at org.springframework.cloud.sleuth.instrument.reactor.ScopePassingSpanSubscriber.onComplete(ScopePassingSpanSubscriber.java:112) [spring-cloud-sleuth-core-2.1.1.RELEASE.jar:2.1.1.RELEASE]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onComplete(MonoFlatMap.java:174) [reactor-core-3.2.9.RELEASE.jar:3.2.9.RELEASE]
at org.springframework.cloud.sleuth.instrument.reactor.ScopePassingSpanSubscriber.onComplete(ScopePassingSpanSubscriber.java:112) [spring-cloud-sleuth-core-2.1.1.RELEASE.jar:2.1.1.RELEASE]
at reactor.core.publisher.MonoNext$NextSubscriber.onComplete(MonoNext.java:96) [reactor-core-3.2.9.RELEASE.jar:3.2.9.RELEASE]
at org.springframework.cloud.sleuth.instrument.reactor.ScopePassingSpanSubscriber.onComplete(ScopePassingSpanSubscriber.java:112) [spring-cloud-sleuth-core-2.1.1.RELEASE.jar:2.1.1.RELEASE]
at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.drain(FluxConcatMap.java:360) [reactor-core-3.2.9.RELEASE.jar:3.2.9.RELEASE]
at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onComplete(FluxConcatMap.java:269) [reactor-core-3.2.9.RELEASE.jar:3.2.9.RELEASE]
at org.springframework.cloud.sleuth.instrument.reactor.ScopePassingSpanSubscriber.onComplete(ScopePassingSpanSubscriber.java:112) [spring-cloud-sleuth-core-2.1.1.RELEASE.jar:2.1.1.RELEASE]
at reactor.core.publisher.FluxIterable$IterableSubscription.slowPath(FluxIterable.java:265) [reactor-core-3.2.9.RELEASE.jar:3.2.9.RELEASE]
at reactor.core.publisher.FluxIterable$IterableSubscription.request(FluxIterable.java:201) [reactor-core-3.2.9.RELEASE.jar:3.2.9.RELEASE]
at org.springframework.cloud.sleuth.instrument.reactor.ScopePassingSpanSubscriber.request(ScopePassingSpanSubscriber.java:79) [spring-cloud-sleuth-core-2.1.1.RELEASE.jar:2.1.1.RELEASE]
at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onSubscribe(FluxConcatMap.java:229) [reactor-core-3.2.9.RELEASE.jar:3.2.9.RELEASE]
at org.springframework.cloud.sleuth.instrument.reactor.ScopePassingSpanSubscriber.onSubscribe(Sc

@ashutoshnayanmishra
You can access /swagger-ui/index.html insteading of /swagger-ui.html due to springfox.boot.starter.autoconfigure.SwaggerUiWebMvcConfigurer#addResourceHandlers

Thanks @NaccOll
it worked.
I am getting the this warnings
2020-06-27 14:32:02.791 Apples-MacBook-Pro-7.local WARN67287 --- [ main] d.s.r.o.OperationImplicitParameterReader :Unable to interpret the implicit parameter configuration with dataType: , dataTypeClass: class java.lang.Void
2020-06-27 14:32:02.807 Apples-MacBook-Pro-7.local WARN67287 --- [ main] Validator :ERROR [ModelSpecification.spec] At least one type of specification is required
Am I missing something?

@NaccOll Thank you for answering that @NaccOll. Yes reworked the swagger-ui so that it is more friendly to being auto configured and less buggy.

Thanks for replying.
But this warnings I am getting. Am I missing something?
2020-06-27 14:32:02.791 Apples-MacBook-Pro-7.local WARN67287 --- [ main] d.s.r.o.OperationImplicitParameterReader :Unable to interpret the implicit parameter configuration with dataType: , dataTypeClass: class java.lang.Void
2020-06-27 14:32:02.807 Apples-MacBook-Pro-7.local WARN67287 --- [ main] Validator :ERROR [ModelSpecification.spec] At least one type of specification is required

Are you seeing what you expect in the API? Those are asserts to help iron out bugs.

We are using 3.0 snapshot and enabled webflux, start from  today's build both 'swagger-ui.html' and 'swagger-ui/index.html' cannot be accessed. (404  error)
Any workarounds for springfox webflux?

@xiongjia Are you using the springfox-boot-starter dependency? If not you should be. Remove explicit dependencies on the ...-swagger2, ..swagger-ui libraries and remove the @Enable... annotations.

I switched to springfox-boot-starter dependencies, but started to see 'java.lang.ClassNotFoundException: org.springframework.data.rest.core.config.RepositoryRestConfiguration' error. I do not use Spring Data Rest.

I temporary added dependency on Spring Data Rest to be able to proceed. Any advise how to resolve this issue?

org.springframework.boot
spring-boot-starter-data-rest

Hmmm that shouldnt be the case. The spring data rest configuration shouldn't load if you dont use spring data rest. Also the the demos don't require it to start up.

@dilipkrish I am having  a similar issue as well. I am failing to access
http://localhost:8080/springfox/swagger-ui.html
@Configuration
@EnableOpenApi
public class WebConfig implements WebMvcConfigurer {

  @Bean
  public Docket petApi() {
    return new Docket(DocumentationType.OAS_30)
        .groupName("full-petstore-api")
        .apiInfo(apiInfo())
        .select()
        .build();
  }

  private ApiInfo apiInfo() {
    return new ApiInfoBuilder()
        .title("Springfox petstore API")
        .description(
            "Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum "
                + "has been the industry's standard dummy text ever since the 1500s, when an unknown printer "
                + "took a "
                + "galley of type and scrambled it to make a type specimen book. It has survived not only five "
                + "centuries, but also the leap into electronic typesetting, remaining essentially unchanged. "
                + "It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum "
                + "passages, and more recently with desktop publishing software like Aldus PageMaker including "
                + "versions of Lorem Ipsum.")
        .termsOfServiceUrl("http://springfox.io")
        .contact(new Contact("springfox", "", ""))
        .license("Apache License Version 2.0")
        .licenseUrl("https://github.com/springfox/springfox/blob/master/LICENSE")
        .version("2.0")
        .build();
  }
}

@dilipkrish Is there a simple open api demo?

@atkawa7 the demos the boot-webmvc and boot-webflux are as basic as they get.

Hi,
In my case even after removing @EnableSwagger2WebFlux, it's not working. I am getting 404 from last 2 days.
@Configuration
@EnableSwagger2WebFlux
public class SwaggerConfiguration {

  private TypeResolver typeResolver = new TypeResolver();

  @Bean
  public Docket api() {
    return new Docket(DocumentationType.SWAGGER_2)
        .host("")
        .produces(Collections.singleton(MediaType.APPLICATION_JSON_VALUE))

It works after adding
  <dependency>       <groupId>io.springfox</groupId>       <artifactId>springfox-boot-starter</artifactId>       <version>3.0.0-SNAPSHOT</version>     </dependency>
but earlier this dependency was not required. Is it mandatory to use this dependency now?
I was using springfox-swagger2, springfox-spring-webflux, springfox-swagger-ui, and springfox-schema and my swagger-ui was working fine.

Thanks @dilipkrish. Its working now

@asuri3 If you're using a boot app. It is best to let the boot starter do all the configuration for you. Nothing is mandatory, its just sets up your project with the right settings.

@asuri3 If you're using a boot app. It is best to let the boot starter do all the configuration for you. Nothing is mandatory, its just sets up your project with the right settings. Also it simplifies your dependencies to one dependency

ok thanks @dilipkrish

which repository using for obtain springfox-boot-starter, please?

Please see the docs

@dilipkrish Going back to my comment about the following error "I switched to springfox-boot-starter dependencies, but started to see 'java.lang.ClassNotFoundException: org.springframework.data.rest.core.config.RepositoryRestConfiguration' error. I do not use Spring Data Rest.". I debugged it a bit and found BasePathAwareServicesProvider class which is annotated with Component, which instance of the class is created automatically. RepositoryRestConfiguration is autowired in constructor. This component needs to be conditional on Spring Data Rest

@dilipkrish The same issue exists for EntityServicesProvider class as well. It is annotated as Component

@ashutoshnayanmishra
You can access /swagger-ui/index.html insteading of /swagger-ui.html due to springfox.boot.starter.autoconfigure.SwaggerUiWebMvcConfigurer#addResourceHandlers

this works for me. this issue blocked me several days...

@vpylypenko2 That is because its auto configured based on the existence of @ConditionalOnClass(RepositoryRestConfiguration.class) causing SpringDataRestConfiguration to light up. Open to ideas on how best to determine if the spring data rest support be auto configured.

@dilipkrish We need @ConditionalOnClass(RepositoryRestConfiguration.class) for BasePathAwareServicesProvider and EntityServicesProvider classes as well. Another alternative is to define bean creation for those two classes in SpringDataRestConfiguration

I dont follow. The component scan should only happen when SpringDataRestConfiguration is active right?

@dilipkrish You are right. I debugged it a bit more and found @ComponentScan(basePackages = {"springfox.documentation", ... in our project code. The code was created long time. It needs to change. Thanks for the quick response and the hint

It works after adding

  <groupId>io.springfox</groupId>
  <artifactId>springfox-boot-starter</artifactId>
  <version>3.0.0-SNAPSHOT</version>
</dependency>

but earlier this dependency was not required. Is it mandatory to use this dependency now?
I was using springfox-swagger2, springfox-spring-webflux, springfox-swagger-ui, and springfox-schema and my swagger-ui was working fine.

It worked for me using springfox-boot-starter and swagger-ui/index.html


How to pass external libraries to functions

Ho to pass external libraries like mysql jar files while submitting functions.

You have 2 options here:

Package an uberjar
Configure your context with run-options="--packages "

Thanks, can I have sample for option 2.
I have tried providing jar files separated by commas which are available in local path where mist is running but it is not picking.
/localpath/mysql.jar

A local path won't work, you should specify mvn dependency here (e.g mysql:mysql-connector-java:5.1.6)

sorry to bother you, these packages downloaded from mvn repository? if that is the case in restricted environment how this will work? by any chance we keep the libraries in hdfs path.

Basically run-options appended to your spark-submit come, so you can read spark docs for managing dependencies for your spark job

You can either host your own Nexus for that and define it in run-options too or define hdfs path to your dependency in --packages

Feel free to ask this kind of question in our gitter room


Python Version

More of a suggestion than an issue.
OneCompiler reports Python sys.version as:
3.8.10 (default, Jun 22 2022, 20:18:18)
[GCC 9.4.0]

This is quite old, and doesn't include match which is commonly used in recent code golfing.

Yes, you are right. It seems like OneCompiler supports only Python 3.8.10. I'll have a look to other online compilers that have an API which support newer Python versions. @dah33  do you have any recommendation which one to use? I found now mycompiler.io, which seems to use at least Python 3.11.4.

I don't know online interpreters that well. I would wait until you've got more users and see what other feedback is like. I would think Python would be quite popular, but actually a lot of the early submissions are Kotlin.

I would appreciate 3.9+ as well! math.lcm is relatively new in Python and quite useful for golfing. Thank you!
I looked at a couple others, like ideone.com which was a bit older as well (3.9) or repl.it which seems overkill. So, mycompiler.io seems promising.

Good news! OneCompiler has updated the python version. Now Golfcoder supports Python 3.12.3 (main, Sep 11 2024, 14:17:37) [GCC 13.2.0]


Revert "[2556] - CourseSerializer Cleanup"

Context
This reverts commit 58027d9aaf40e0714ebcddbe4467ae1254cc6738.
Checklist

[ ] Make sure all information from the Trello card is in here
[ ] Attach to Trello card
[ ] Rebased master
[ ] Cleaned commit history
[ ] Tested by running locally

We rolled-forward so don't need this any more.


How to section on PI download with MS Edge

Related to Particular/DeveloperEducation/issues/1313
This PR introduces guidance how to workaround Platform Installer download problems with Microsoft Edge.

@adamralph this is ready for review.


feat: support CRLF

Fixes #108

Codecov Report

Merging #110 into master will not change coverage.
The diff coverage is 100%.

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


Mobile view of crowding graph

Crowding display is compressed too far.
┆Issue is synchronized with this Trello card by Unito

Some notes as I play around with this:
with .canvasContainer set to:
.canvasContainer {
  width: 100%;
  height: 100%;
}


$.ajax() does not seem to deal properly with JSON data

Even when the API returns contentType = application/json I need to parse the response with JSON.parse to be able to access it. From jQuery I'm used to specify a dataType property for the $.ajax() method.

Figured this out; I was ignorant of "xhr.responseType" ... if you git checkout the "topic-ajax" branch, you can see the update - now you can add a "dataType" option in your $.ajax options.
Let me know if this works for you before I merge the change into master and bump the fix version :)

Pretty sure this is taken care of, after plenty of testing.  The data in our response is matching the dataType I'm telling it to in the tests.
Please let me know if you experience any other issues.

Sorry, was busy this week with work =), playing with grindstone for some petprojects, might be able to test it out this weekend, thanks anyways for the fast replies and fixes!!

No worries ... FYI I'm going to be busy myself coming up with the holidays and everything approaching, but I'll continue to respond as quickly as I can if more issues arise.  Thanks gain for taking an interest and helping improve the library :)


Scaling enables dynamic loading of K-lines

Question
Firstly, thank you very much for your open-source code. I have a small need to consult, could you please help me see how to implement it when you have time.

If I want to obtain the current number of candlesticks, how can I dynamically load more candlesticks by zooming out with the mouse wheel until the interface appears blank?
Is there any related tutorial to see?
Thank you again!

Code example
No response

Use the range_change event https://lightweight-charts-python.readthedocs.io/en/latest/reference/events.html

@95ge  in relation to your question
1 you could simple the get the lenght of you df,
import pandas as pd

df = pd.DataFrame({
    'A': [1, 2, 3],
    'B': [4, 5, 6]
})

# Get the number of rows
length = len(df)
print(length)  # Output will be 3

1.1. how can I dynamically load more candlesticks by zooming out with the mouse wheel until the interface appears blank, i belive this this part of the lib so far, but if what you are looking for is to increase the amount of candles as you scroll your mouse wheel, you need to add an event listener to on the bundle.js file, to track the mouse wheel so that you can add more candles at the beggining of the chart ... also keep in mind the limitation of the lib about the max number of candles that can be handle.

here you are for the mouse wheel event listener
pandas len


Marquee 2.0.1 stopped running on Vue 3.2.33/Node 16.14.2

I recently upgraded to the mentioned newest Vue 3 and Node level, and marquee stopped running. It shows the text , but is paused even with paused prop absent or set to true. Means the text is displayed, but not moved from right to left. No errors in logs.

@mickey58github
I have just tested it with the version<EMAIL_ADDRESS>It runs without problems, unfortunately I don't notice anything?

hmm, in my case it is embedded in a larger application, so I don't have a simpler testcase.  It doesn't show any errors in the log, the text is just paused since the upgrade. As a workaround, I replaced it by https://github.com/megasanjay/vue3-marquee which works on my Vue 3/Node combination. It is a very strange error, maybe related to my setup, not the component itself.

@mickey58github okay then I will close the ticket.
All the best.

@EvodiaAut - yes, right now I see no other option. Thanks for your help.


Monograph 2 tui

The text here looks good.  Once we potentially look at the other comment I had, I'd be fine with merging both


Account Naming and Multi Address Fixes

Critical Changes
Changes
Issues Closed
New Metadata
Unpackaged Metadata
Deleted Metadata
Testing Notes

Reverted the Label Change to acctNamingOther as it is used as a hard configuration value.
Accounted for space splitting to pull legacy multiaddress values

QA Passed. Requested merge from RelEng.


Contextual lexer matching terminal that can't be reached in context

I think this is a bug, but it may be possible I'm misunderstanding how the contextual lexer works.
The grammar I have has tokens based on the context, but until now it seemed to work ok using lalr with the contextual lexer, but after I added the return_stmt it seems it started to do some wrong choices on how to lex the code.
In this case, where the grammar should parse a NAME_CONT it's parsing a DEC_NUMBER.
Let me give some more info:
The grammar is trying to match the code:
*** Functions ***
My Function 1
    While var 2
        var 3

and it's matching the 1 from My Function 1 as a DEC_NUMBER instead of a NAME_CONT (even though a DEC_NUMBER isn't valid at that context and a NAME_CONT is (the identifier rule is: identifier: NAME  (NAME|NAME_CONT|WS)* and it matched the NAME for My and NAME_CONT for Function, yet it then failed to match the 1 as NAME_CONT and ended up matching as a DEC_NUMBER, which isn't valid in the context.
The place where the rules should be matching is at the func_name -- i.e.:
file_input: (_NEWLINE | root_stmt)*
?root_stmt: func_block
func_block: func_header WS? _NEWLINE (func_stmt)*
func_header: BLOCK_START "functions"i  BLOCK_END
func_stmt: func_name func_suite
func_name: identifier
?identifier: NAME  (NAME|NAME_CONT|WS)*
NAME: /[^\d\W]\w*/
NAME_CONT: /\w+/
WS: /\s+/

That alone works, but it fails in the actual grammar:
test_lark_contextual_lexer_issue.py.txt
This happened right after I added the return_stmt!
So, in that same grammar just removing the return_stmt the lexer seems to do the right thing -- I'm not sure why though...
The docs say that:
The contextual lexer communicates with the parser, and uses the parser's lookahead prediction to narrow its choice of tokens. So at each point, the lexer only matches the subgroup of terminals that are legal at that parser state, instead of all of the terminals.
Given that, I think it's a bug in that the lexer is not considering the context as it should in this case -- otherwise, I'm probably misunderstanding the approach on how it decides how to lex based on the context or the grammar can reach a DEC_NUMBER through some means that I can't see (as far as I see it the func_suite needs a _NEWLINE to start, so, it should not be possible to get to a DEC_NUMBER from there).

Well, 1 is not a valid NAME. That DEC_NUMBER is appearing in the error message is because the Contextual Lexer tests whether it knows any Terminal that could match the encountered illegal sequence, even if the Terminal is not valid right now.

Yes, it's not a valid NAME (it should match NAME_CONT and not NAME at that place).

(and it did match NAME_CONT until I added the return_stmt at that same grammar)

In this case, where the grammar should parse a NAME_CONT it's parsing a DEC_NUMBER

Is it actually parsing it as DEC_NUMBER, or only saying so in the UnexpectedToken error?

I am currently confused as to how this ever worked: identifier consumes all \w and \s. This includes newlines.
(And yes, apperantly it is actually parsed as DEC_NUMBER)

In this case, where the grammar should parse a NAME_CONT it's parsing a DEC_NUMBER

Is it actually parsing it as DEC_NUMBER, or only saying so in the UnexpectedToken error?

It's actually parsing as a DEC_NUMBER.
The full exception trace is:
Traceback (most recent call last):
  File "X:\lark\lark\parsers\lalr_parser.py", line 86, in feed_token
    action, arg = states[state][token.type]
KeyError: 'DEC_NUMBER'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "X:\vscode-robot\rflang\tests\rflang_tests\test_lark_contextual_lexer_issue.py", line 97, in <module>
    parse(
  File "X:\vscode-robot\rflang\tests\rflang_tests\test_lark_contextual_lexer_issue.py", line 87, in parse
    tree = lark_spec.parse(source_code)
  File "X:\lark\lark\lark.py", line 493, in parse
    return self.parser.parse(text, start=start)
  File "X:\lark\lark\parser_frontends.py", line 138, in parse
    return self._parse(start, self.make_lexer(text))
  File "X:\lark\lark\parser_frontends.py", line 73, in _parse
    return self.parser.parse(input, start, *args)
  File "X:\lark\lark\parsers\lalr_parser.py", line 35, in parse
    return self.parser.parse(*args)
  File "X:\lark\lark\parsers\lalr_parser.py", line 129, in parse
    return self.parse_from_state(parser_state)
  File "X:\lark\lark\parsers\lalr_parser.py", line 145, in parse_from_state
    raise e
  File "X:\lark\lark\parsers\lalr_parser.py", line 136, in parse_from_state
    state.feed_token(token)
  File "X:\lark\lark\parsers\lalr_parser.py", line 89, in feed_token
    raise UnexpectedToken(token, expected, state=state, puppet=None)
lark.exceptions.UnexpectedToken: Unexpected token Token('DEC_NUMBER', '1') at line 3, column 13.
Expected one of:
	* WS
	* _NEWLINE
	* NAME
	* NAME_CONT

I am currently confused as to how this ever worked: identifier consumes all \w and \s. This includes newlines.
(And yes, apperantly it is actually parsed as DEC_NUMBER)

Changing WS to WS: / /+ so that it only consumes spaces has the same result (in that it will work if return_stmt is removed and will fail when it's present) -- my bad, I thought that \s would only get whitespaces.

The problem is somewhere in here:
WARNING:root:Shift/Reduce conflict for terminal NAME: (resolving as shift)
WARNING:root: * <identifier : NAME __identifier_star_6>
WARNING:root:Shift/Reduce conflict for terminal WS: (resolving as shift)
WARNING:root: * <identifier : NAME __identifier_star_6>
WARNING:root:Shift/Reduce conflict for terminal NAME: (resolving as shift)
WARNING:root: * <call_expr : arguments WS identifier __call_expr_star_4>
WARNING:root:Shift/Reduce conflict for terminal LPAR: (resolving as shift)
WARNING:root: * <call_expr : arguments WS identifier __call_expr_star_4>
WARNING:root:Shift/Reduce conflict for terminal LPAR: (resolving as shift)
WARNING:root: * <name_expr : identifier>
WARNING:root:Shift/Reduce conflict for terminal NAME: (resolving as shift)
WARNING:root: * <call_expr : arguments WS identifier>
WARNING:root:Shift/Reduce conflict for terminal LPAR: (resolving as shift)
WARNING:root: * <call_expr : arguments WS identifier>
WARNING:root:Shift/Reduce conflict for terminal NAME: (resolving as shift)
WARNING:root: * <call_expr : arguments identifier __call_expr_star_4>
WARNING:root:Shift/Reduce conflict for terminal LPAR: (resolving as shift)
WARNING:root: * <call_expr : arguments identifier __call_expr_star_4>
WARNING:root:Shift/Reduce conflict for terminal NAME: (resolving as shift)
WARNING:root: * <call_expr : arguments identifier>
WARNING:root:Shift/Reduce conflict for terminal LPAR: (resolving as shift)
WARNING:root: * <call_expr : arguments identifier>
WARNING:root:Shift/Reduce conflict for terminal NAME: (resolving as shift)
WARNING:root: * <call_expr : identifier arguments>
WARNING:root:Shift/Reduce conflict for terminal LPAR: (resolving as shift)
WARNING:root: * <call_expr : identifier arguments>
WARNING:root:Shift/Reduce conflict for terminal NAME: (resolving as shift)
WARNING:root: * <identifier : NAME>
WARNING:root:Shift/Reduce conflict for terminal WS: (resolving as shift)
WARNING:root: * <identifier : NAME>
WARNING:root:Shift/Reduce conflict for terminal NAME: (resolving as shift)
WARNING:root: * <call_expr : identifier arguments __call_expr_star_5>
WARNING:root:Shift/Reduce conflict for terminal LPAR: (resolving as shift)
WARNING:root: * <call_expr : identifier arguments __call_expr_star_5>

That is the log output when debug=True. That many Shift/Reduce conflicts can't be good.

That is the log output when debug=True. That many Shift/Reduce conflicts can't be good.

Is that debug=True to the Lark constructor? I can't seem to get that log setting debug=True there (even adding a logger):
i.e.: code:
test_lark_contextual_lexer_issue.py.txt
(I'm trying with the master version)

I've simplified the grammar a bit more so hopefully it's easier to debug (while still having the same error -- which doesn't happen if the return_stmt is removed -- and I can't see any message reported with debug=True with the master version):
test_lark_contextual_lexer_issue.py.txt

In the master (and maybe even in 10.0) we changed the logging system to use lark.logger instead of the root logger. The output I posted was with the 0.9 version.

In the last version I sent (in https://github.com/lark-parser/lark/issues/742#issuecomment-720630825) I see the following messages:
Unused terminals: ['COMMENT']
Shift/Reduce conflict for terminal NAME: (resolving as shift)
 * <identifier : NAME __identifier_star_3>
Shift/Reduce conflict for terminal NAME: (resolving as shift)
 * <identifier : NAME>

It seems related to:
?identifier: NAME  (NAME|NAME_CONT|WS)*
changing it to:
identifier: NAME  (NAME_CONT|WS)*
fixes the warnings (but parsing still fails) -- but it now fails because it finds a Function in My Function 1 as a NAME when it should find it as NAME_CONT, so, it's still an error in determining how the lexer works in a given context.
This version (which doesn't have any warnings) is:
test_lark_contextual_lexer_issue.py.txt
As in others, removing the return_stmt makes everything work.

I took a look at your example, and I'll try to explain what happens.
Basically the LALR parser performs two functions: shift, and reduce. Shift takes in the next token. Reduce happens when a rule is complete.
In your case, identifier could be reduced in two situations: Either it's inside func_stmt, and then the following terminal is _NEWLINE, or it's inside test, which means it's also inside return_stmt and then the following rule can be another test, which means the next token can be DEC_NUMBER (among others).
Only after reducing, the shift learns it's not in the middle of a return_stmt after all. In theory, I could try to make the LALR(1) parser clever enough to know it before reducing. But all it will give you is a better error, because your text is obviously incorrect for the grammar.
Tbh, I'm not sure that a better error is worth it. Is there anything I could say in this situation which would help you solve it faster? (that doesn't involve grammar analysis, ofc)

Right now the contextual lexer only looks at the next action, and in this case it sees a legal reduce for DEC_NUMBER. I can make it also look into the shift operations afterward, but that would mean extra computation for each token. I don't think it's worth it, just so you will instead get the exact same error from the lexer.

Ok, I think I understand now. Let me try to rephrase to see if this is it:
The issue is that the contextual lexer on lark sees the current construct and all other possible reachable states from that construct (even if invalid in the actual parse state) when determining the next token in the lexer, so, even though at func_stmt/identifier/NAME only a NAME_CONT/WS/_ENDLINE is valid it may end up creating tokens reachable from stmt/test/identifier (so, it's an improvement over yacc/bison but the grammar must be constructed to have unique rules to overcome that limitation -- indeed if I don't reuse the identifier rule and create an identifier_func with a NAME_FUNC it seems to recognize it properly at that specific place).
So, it seems I was really overestimating the parser lookahead capabilities.
Personally, I think that given that it was inside the identifier and it already matched the NAME, I think it should try to tokenize the next words using the remainder of the identifier construct (NAME_CONT|WS) and then the tokens based on rules that can happen at that context (which in that sample grammar would be just _NEWLINE) -- this doesn't seem like an issue in how LALR(1) works, but rather on the (unique) approach used to do the lexing based on the parse state.
If it did that I believe the grammar would be valid and it would probably handle some ambiguity in the grammar better (closer to what PEGs do).
Anyways, thanks for the explanation, I think I understand better the limitations now to try to work around them.
Feel free to close if you don't plan on changing how the tokenization works based on the parse state lookahead (I guess this would be a feature request).

Alternatively, you could fix your grammar: return_stmt should require a _NEWLINE at the end. Adding that fixes this error.
This was by the way a true ambiguity in your grammar.
return var 1 1
could have been parsed as
return_stmt
    identifier
        var
        1
        1

(which is probably what you wanted)
or, incorrectly as
return_stmt
    identifier
        var
        1
test
    number_expr
        1

Sorry that it took me this long to discover this.

Alternatively, you could fix your grammar: return_stmt should require a _NEWLINE at the end. Adding that fixes this error.

Agreed, that's the proper fix -- thank you for spotting it (I should've spotted it myself, but I guess I got sidetracked by how the error was expressed, I should've known better... on the bright side, now I have more knowledge in what I can expect from lark).

Sorry that it took me this long to discover this.

I must say that the response seemed quite speedy and high quality, so, thank you very much for the really nice support given by the lark team, it's much appreciated! (I know how much effort goes into supporting a high quality open source project)

I think it should try to tokenize the next words using the remainder of the identifier construct (NAME_CONT|WS) and then the tokens based on rules that can happen at that context

That may be possible, but it is an extraneous complication just to shift the error from one place to another, that will have real performance implications. So, I don't plan to do it. But I appreciate the suggestion.


Add Safari 13

Thank you for this helpful lib! This adds the newest Safari version to the client-side check.

Thank you for the PR!
Does everything still work as expected with this version ?


ARROW-11675: [CI][C++] Resolve ctest failures on VS 2019 builds

@github-actions crossbow submit test-build-vcpkg-win

Wow, the build took two hours. Is there a way to make it shorter?

@github-actions crossbow submit test-build-vcpkg-win

@github-actions crossbow submit test-build-vcpkg-win

@github-actions crossbow submit test-build-vcpkg-win

@pitrou the manifest file cpp/vcpkg.json specifies which Arrow library build dependencies to install when ARROW_DEPENDENCY_SOURCE=VCPKG, as described in the Building Arrow C++ and Developing on Windows docs, so if you're making changes to that file, please keep in mind that it serves a general purpose beyond what this CI job tests.

Yawn. When I added some logging calls inside the inner routines, the bug disappeared. Looks like a compiler bug of sorts :-(

TODO: perhaps add Spaced tests and specialization

@github-actions crossbow submit test-build-vcpkg-win

@github-actions crossbow submit test-build-vcpkg-win

Thanks for working on this! The boost changes in cpp/vcpkg.json look good 👍

@github-actions crossbow submit test-build-vcpkg-win

CI failures are unrelated, I'll merge.


Animation.on_complete does not fire when Window arg is parsed into Animation.start

Versions

Python: 3.6.5
OS: Windows 10
Kivy: 1.10.0
Kivy installation method: wheels

Description
The Animation.on_complete does not fire when Window is parsed into the Animation.start method. On other widgets I have not encountered with this issue.
Code and Logs
anim = Animation(size=(300, 300), transition='out_expo')
anim.on_complete = lambda: print('completed')
anim.start(Window)

You could try using self.animation.bind(on_complete=self.clear_color).
Which is found from this issue

I can't reproduce here.
from kivy.app import App
from kivy.core.window import Window
from kivy.animation import Animation
from kivy.uix.button import Button

class WApp(App):
    def build(self):
        return Button(on_press=self.start_anim)

    def start_anim(self, *args):
        anim = Animation(size=(300, 300), transition='out_expo')
        anim.on_complete = lambda: print('completed')
        anim.start(Window)

if __name__ == '__main__':
    WApp().run()

i get:
 Traceback (most recent call last):
   File "/tmp/test_an Traceback (most recent call last):
   File "/tmp/test_anim.py", line 18, in <module>
     WApp().run()
   File "/home/gabriel/dev/kivy/kivy/app.py", line 826, in run
     runTouchApp()
   File "/home/gabriel/dev/kivy/kivy/base.py", line 502, in runTouchApp
     EventLoop.window.mainloop()
   File "/home/gabriel/dev/kivy/kivy/core/window/window_sdl2.py", line 727, in mainloop
     self._mainloop()
   File "/home/gabriel/dev/kivy/kivy/core/window/window_sdl2.py", line 460, in _mainloop
     EventLoop.idle()
   File "/home/gabriel/dev/kivy/kivy/base.py", line 337, in idle
     Clock.tick()
   File "/home/gabriel/dev/kivy/kivy/clock.py", line 581, in tick
     self._process_events()
   File "kivy/_clock.pyx", line 384, in kivy._clock.CyClockBase._process_events
   File "kivy/_clock.pyx", line 414, in kivy._clock.CyClockBase._process_events
   File "kivy/_clock.pyx", line 412, in kivy._clock.CyClockBase._process_events
   File "kivy/_clock.pyx", line 167, in kivy._clock.ClockEvent.tick
   File "/home/gabriel/dev/kivy/kivy/animation.py", line 352, in _update
     self.stop(widget)
   File "/home/gabriel/dev/kivy/kivy/animation.py", line 217, in stop
     self.dispatch('on_complete', widget)
   File "kivy/_event.pyx", line 707, in kivy._event.EventDispatcher.dispatch
 TypeError: <lambda>() takes 0 positional arguments but 1 was givenim.py", line 18, in <module>
     WApp().run()
   File "/home/gabriel/dev/kivy/kivy/app.py", line 826, in run
     runTouchApp()
   File "/home/gabriel/dev/kivy/kivy/base.py", line 502, in runTouchApp
     EventLoop.window.mainloop()
   File "/home/gabriel/dev/kivy/kivy/core/window/window_sdl2.py", line 727, in mainloop
     self._mainloop()
   File "/home/gabriel/dev/kivy/kivy/core/window/window_sdl2.py", line 460, in _mainloop
     EventLoop.idle()
   File "/home/gabriel/dev/kivy/kivy/base.py", line 337, in idle
     Clock.tick()
   File "/home/gabriel/dev/kivy/kivy/clock.py", line 581, in tick
     self._process_events()
   File "kivy/_clock.pyx", line 384, in kivy._clock.CyClockBase._process_events
   File "kivy/_clock.pyx", line 414, in kivy._clock.CyClockBase._process_events
   File "kivy/_clock.pyx", line 412, in kivy._clock.CyClockBase._process_events
   File "kivy/_clock.pyx", line 167, in kivy._clock.ClockEvent.tick
   File "/home/gabriel/dev/kivy/kivy/animation.py", line 352, in _update
     self.stop(widget)
   File "/home/gabriel/dev/kivy/kivy/animation.py", line 217, in stop
     self.dispatch('on_complete', widget)
   File "kivy/_event.pyx", line 707, in kivy._event.EventDispatcher.dispatch
 TypeError: <lambda>() takes 0 positional arguments but 1 was given

at the end of the animation, which is proof that the lambda was called.
But yes, as @kuzeyron this is not how you should bind a function to an event, use bind.
Please give a more complete test case if you still have the error.

I still have the problem.
Maybe Config.set('graphics', 'multisamples', 0) is the problem. I have set it like that because I am experiencing the issue with OpenGL version detection.
If I do anim.bind('on_complete', fn) I get an error saying TypeError: bind() takes exactly 0 positional arguments (2 given).

The syntax is anim.bind(on_complete=fn) or alternativelay anim.fbind('on_complete', fn) both versions works the same for me. I don't think the multisample level will have any effect on that (but i tested anyway, no change for me).
However, i just saw you had the issue on 1.10.0 so i checked it, and i can reproduce the issue there, so it's been fixed since, and the next release will contain the fix.

Is there some way I can fix that myself? I know that pre-releases can be pretty unstable.

Actually, i think it would be a lot better for you to try the latest master, we are really nearing a release and things are quite smooth now, the actual release (due "soon") might not be very different.
Alternatively, since we have a known test, one could use git bisect to find which commit fixed it and you could apply it manually, but i do think it's more trouble than it's worth.


Hack for detecting many Android devices description or model number

Hack to detect description or model number for Android devices.
There are so so many Android devices it's impracticle to list them all.
For example the Alcatel U5 shows in userAgent as just "5047D", however Alcatel has an insane amount of other models see for example here https://uae.souq.com/ae-en/mobile-phone/alcatel/a-7/l/  and that's just one manufacturer.

This looks great. Thank you @BdR76! Yes, please update the tests.

will this be merged?


Appstudio update mvp-test-component

Pipelines as Code configuration proposal

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
10 seconds
init

✅ Succeeded
14 seconds
clone-repository

✅ Succeeded
2 minutes
build-container

✅ Succeeded
26 seconds
sanity-inspect-image

✅ Succeeded
28 seconds
deprecated-base-image-check

✅ Succeeded
45 seconds
clair-scan

✅ Succeeded
2 minutes
clamav-scan

✅ Succeeded
20 seconds
sbom-json-check

✅ Succeeded
14 seconds
sanity-label-check

✅ Succeeded
14 seconds
sanity-optional-label-check

✅ Succeeded
7 seconds
show-summary


Demo missing from the following link

http://www.openfl.org/blog/2016/10/13/improved-support-for-starling/
Direct link:
http://www.openfl.org/samples/starling/html5/

Thanks for the heads-up!
It should be fixed now :smile:


Problem with cat-sam-a, 1-shot training results

The training result（based on cat-sam-a, 1-shot，whu） for running on my own was 84，but the result mentioned in paper is 88.2?

Hi @WILSON10111 ,
Thank you for your interest in our work.
We have noticed the randomness according to this issue. We are thinking of incorporating some ways to reduce the randomness and improve the determinism of the code. Please also refer to the checkpoint for the results.
Best regards,


Padding fix in scale_to_freq

#113

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.07%. Comparing base (fa4c720) to head (6a5db59).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #114   +/-   ##
=======================================
  Coverage   92.07%   92.07%
=======================================
  Files          17       17
  Lines        3519     3519
=======================================
  Hits         3240     3240
  Misses        279      279

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add the flash driver itself.

At the moment, it only supports write operations. Erases should be easy to implement (the smart program state machine already supports them, we just need to add the interface methods and some constants).
Commits new to this PR:

Add the flash driver itself.

----------------------
`make prtest` summary:
----------------------
git rev-parse HEAD
e491e72c4ed694ccbbb6b6c744c3c65c8ac6805f
git status
On branch flash-driver-export
Your branch is up to date with 'origin/flash-driver-export'.

nothing to commit, working tree clean

Updated.
----------------------
`make prtest` summary:
----------------------
git rev-parse HEAD
1af0469dba942ccfd5f4b377dc5481f3af63336c
git status
On branch flash-driver-export
Your branch is up to date with 'origin/flash-driver-export'.

nothing to commit, working tree clean


Update versions according to the one in qiskit/qiskit_sphinx_theme

Summary
This PR updates the versions.html template override to sync it with the changes introduced in Qiskit/qiskit_sphinx_theme#23 Merge only after Qiskit/qiskit_sphinx_theme#23!
Details and comments

Now Qiskit/qiskit_sphinx_theme#23 is merged, we can merge this too so the language selector is correctly displayed.

That was fast, @SooluThomas !!


Gene-level summary of ClinVar data

Show a breakdown of the number of ClinVar variants in each clinical significance category in each consequence category.

Discussion at browser meeting: make it look like the HGMD table.


Updated codeload.github.com's TLS certificate.

This just updates the certificate, unfortunately it doesn't get recognized as valid certificate by botan, as such the SFMLInstaller currently doesn't work.
Since you know botan a bit better, you might be able to figure out what's going wrong.

There was nothing wrong with the certificate itself. Verification failed because the CN in the certificate (*.github.com) didn't match the FQDN of the server (codeload.github.com). SFNUL currently is not able to do wildcard matching and requires string equality. This is why I added a way to explicitly specify a CN that differs from the remote hostname in a recent commit of SFNUL.
I added the expected CN in 572e111b206077bd9e52dd8e449c34f9920f65ff and it works for me again :wink:.

Can you also push that SFNUL change, since it doesn't seem to work for me:

Installer.cpp:38:19: error: no matching function for call to 'sfn::HTTPClient::LoadCertificate(const char[20], sfn::TlsCertificate::Ptr, const char [12])'), "*github.com" );


There's already a "Laravel Folio"

Folio Version
1.0.0
Laravel Version
10.4.1
PHP Version
8.1.4
Description
You may want to reach out to this developer:
https://github.com/nonoesp/laravel-folio
Steps To Reproduce
N/A

Hey there - I own the trademark to "Laravel".


Run RustPython with ThreadSanitizer

I think there's a bug with threading, so I want to turn ThreadSanitizer on. Right now, this requires rebuilding std.
This is blocked by test_array falling over with a debug version of std -- and it appears that this is a real bug.

To run:
TSAN_OPTIONS="suppressions=tsan.supp" RUSTFLAGS=“-Zsanitizer=address” cargo run -Zbuild-std --target x86_64-unknown-linux-gnu cargo run — -m test


Could not load plugin

I have been using a previous version of the plugin for two years (really nice work by the way) with no issue. It seems there is a missing WPF dll (Or maybe it is a mitmaching .NET version), Anyway, Im using simhub 8.2.0 and version 0.10.0 of this plugin *The latest release, the one from September 13),
These are the simhub logs:
[2022-12-17 20:15:03,678] INFO - Loading plugins controls
[2022-12-17 20:15:03,738] ERROR - An error occured while loading plugin settings control for SLI Plugin: System.Windows.Markup.XamlParseException: Could not load file or assembly 'WpfAutoGrid, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified. ---> System.IO.FileNotFoundException: Could not load file or assembly 'WpfAutoGrid, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
   at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.Assembly.Load(AssemblyName assemblyRef)
   at System.Windows.Baml2006.Baml2006SchemaContext.ResolveAssembly(BamlAssembly bamlAssembly)
   at System.Windows.Baml2006.Baml2006SchemaContext.ResolveBamlTypeToType(BamlType bamlType)
   at System.Windows.Baml2006.Baml2006SchemaContext.ResolveBamlType(BamlType bamlType, Int16 typeId)
   at System.Windows.Baml2006.Baml2006SchemaContext.GetXamlType(Int16 typeId)
   at System.Windows.Baml2006.Baml2006Reader.Process_ElementStart()
   at System.Windows.Baml2006.Baml2006Reader.Process_OneBamlRecord()
   at System.Windows.Baml2006.Baml2006Reader.Process_BamlRecords()
   at System.Windows.Baml2006.Baml2006Reader.Read()
   at System.Windows.Markup.WpfXamlLoader.TransformNodes(XamlReader xamlReader, XamlObjectWriter xamlWriter, Boolean onlyLoadOneNode, Boolean skipJournaledProperties, Boolean shouldPassLineNumberInfo, IXamlLineInfo xamlLineInfo, IXamlLineInfoConsumer xamlLineInfoConsumer, XamlContextStack`1 stack, IStyleConnector styleConnector)
   at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
   --- End of inner exception stack trace ---
   at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
   at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
   at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
   at System.Windows.Application.LoadComponent(Object component, Uri resourceLocator)
   at SimElation.Simhub.SliPlugin.SliPluginControl.InitializeComponent()
   at SimElation.Simhub.SliPlugin.SliPlugin.GetWPFSettingsControl(PluginManager pluginManager)
   at SimHubWPF.MainWindow.<>c__DisplayClass56_0.<LoadPluginsControls>b__0()

OK thanks, haven't upgraded to 8.2.0 so will do and see what the problem is...

Quick hack fix: https://github.com/simelation/simhub-plugins/releases/tag/%40simelation%2Fsimhub-sli-plugin%400.11.0
Longer term I should probably stop using WpfAutoGrid.
Thanks!

It's working again. Thank you.


use new Source.queue to avoid memory leak

Motivation
the legacy usage of Source.queue has a memory leak issue, see: https://github.com/akka/akka/issues/25798, the newest API has been solved that.
This PR should cherry-pick to 1.0.x ?

@Roiocam I was sending the same pr to https://github.com/SwissBorg/pekko-persistence-postgres/pull/32
I think we should check other pekko persistence plugins too.

@Roiocam I was sending the same pr to SwissBorg/pekko-persistence-postgres#32
I think we should check other pekko persistence plugins too.

I just checked and it seems that other plugins do not use queues for batching operations at writing events.

@Roiocam yes, please squash merge and cherry pick to 1.0.x thanks.

Oops, it should be merged with squash...

https://github.com/search?q=org%3Aapache SourceQueueWithComplete&type=code -- there is other Pekko code that uses SourceQueueWithComplete. Should that be rewritten too? Even if most of it is in tests, those tests can be viewed as a form of documentation of the code.

If it's been used with dropNew strategy ,then it can be updated with the new implementation by @jrudolph

https://github.com/search?q=org%3Aapache SourceQueueWithComplete&type=code -- there is other Pekko code that uses SourceQueueWithComplete. Should that be rewritten too? Even if most of it is in tests, those tests can be viewed as a form of documentation of how to use the code.

like He-pin says, only dropNew has this issue, but I will check it when I am free.

https://github.com/search?q=org%3Aapache SourceQueueWithComplete&type=code -- there is other Pekko code that uses SourceQueueWithComplete. Should that be rewritten too? Even if most of it is in tests, those tests can be viewed as a form of documentation of how to use the code.

like He-pin says, only dropNew has this issue, but I will check it when I am free.

I checked that already,  it was backpresure strategy in other cases, which the current new source.queue doesn't support.


The latest transaction record cannot be retrieved

The latest transaction record cannot be retrieved

Any detail ?

Caused by not support v2 transaction, now has been fixed.


Noob question here - "[X] Ooops!!!: It's True, the series 'close' was not found in time"

Hi there,
First of all sorry for my ignorance.
I have this dataframe:

I want to plot it along side with it alot of indicators.
I can do this manually for example:

But I'm not able to use a strategy..

How do I specify which one is my "target" column. I seems it defaults to "close".

Hello @mcpeixoto,
No worries. You need to specify the replacement column to use for close.

Let me know if this works for you. Thanks for trying Pandas TA!
Kind Regards,
KJ

Thank you so much for the patience and kind response. It works :)

@mcpeixoto,
No worries. Thanks for prompt response that the solution works for you. 😎
Thanks,
KJ


release: v3.12.1

About this change—what it does

releases v3.12.1

Why this way

to have it :)

LGTM


[Feature Request] REI plugin compatibility

Could you please add REI plugin compatibility? It should greatly improve compatibility with most of the mods available.
However, it can be seen that it would be a hard work to finish. I don't know much about such mod compatibility, but I think the JEI compatibility layer of REI is a good example.

What if a mod which both supports rei and emi?

REI's api is massive and doesn't cleanly map to EMI. Systems such as the recipe tree wouldn't even be able to function properly were this done. I'm not going to discourage the development of this by a third party, but I will not be doing this first party, unfortunately, it would take too much dev time that could be better spent on fixing bugs and adding features.


Create Response#ok to return if status is in the 200 range

200 OK
201 Created
204 No Content

Is this still relevant? What would be the difference between Response#ok and Response#success?

I think it's still valid since success considers redirects; it just improves the developer experience a bit.


timetrap: 1.10.0 -> 1.15.1

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build timetrap

Success on aarch64-linux (full log)
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/x8lnv8kw6fw05f68mg0gfxznnv9wvbpm-ruby2.4.3-timetrap-1.15.1
patching script interpreter paths in /nix/store/x8lnv8kw6fw05f68mg0gfxznnv9wvbpm-ruby2.4.3-timetrap-1.15.1
/nix/store/x8lnv8kw6fw05f68mg0gfxznnv9wvbpm-ruby2.4.3-timetrap-1.15.1/lib/ruby/gems/2.4.0/gems/timetrap-1.15.1/completions/bash/timetrap-autocomplete.bash: interpreter directive changed from "/bin/bash" to "/nix/store/lnws52qanbi5vz8qg24v4ym57nznfndg-bash-4.4-p12/bin/bash"
/nix/store/x8lnv8kw6fw05f68mg0gfxznnv9wvbpm-ruby2.4.3-timetrap-1.15.1/lib/ruby/gems/2.4.0/gems/timetrap-1.15.1/bin/timetrap: interpreter directive changed from "/usr/bin/env ruby" to "/nix/store/6hx1p4ci13bdg9ska62m1az888bz29sz-ruby-2.4.3/bin/ruby"
/nix/store/x8lnv8kw6fw05f68mg0gfxznnv9wvbpm-ruby2.4.3-timetrap-1.15.1/lib/ruby/gems/2.4.0/gems/timetrap-1.15.1/bin/t: interpreter directive changed from "/usr/bin/env ruby" to "/nix/store/6hx1p4ci13bdg9ska62m1az888bz29sz-ruby-2.4.3/bin/ruby"
/nix/store/x8lnv8kw6fw05f68mg0gfxznnv9wvbpm-ruby2.4.3-timetrap-1.15.1/lib/ruby/gems/2.4.0/gems/timetrap-1.15.1/bin/dev_t: interpreter directive changed from "/usr/bin/env ruby" to "/nix/store/6hx1p4ci13bdg9ska62m1az888bz29sz-ruby-2.4.3/bin/ruby"
checking for references to /build in /nix/store/x8lnv8kw6fw05f68mg0gfxznnv9wvbpm-ruby2.4.3-timetrap-1.15.1...
building '/nix/store/wfw4iz3vrsbfs2acj4w1ca2dkrcpxdmf-timetrap-1.15.1.drv'...
created 23 symlinks in user environment
/nix/store/lrpivdlarzqs073fizz5j20cq1llk987-timetrap-1.15.1

Success on x86_64-linux (full log)
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/gygp1m5xbg8fp0w3vgm5mvkfjpn31hn0-ruby2.4.3-timetrap-1.15.1
patching script interpreter paths in /nix/store/gygp1m5xbg8fp0w3vgm5mvkfjpn31hn0-ruby2.4.3-timetrap-1.15.1
/nix/store/gygp1m5xbg8fp0w3vgm5mvkfjpn31hn0-ruby2.4.3-timetrap-1.15.1/lib/ruby/gems/2.4.0/gems/timetrap-1.15.1/bin/t: interpreter directive changed from "/usr/bin/env ruby" to "/nix/store/dns77vf9frhd2s2xvcdd47rs2l08nqin-ruby-2.4.3/bin/ruby"
/nix/store/gygp1m5xbg8fp0w3vgm5mvkfjpn31hn0-ruby2.4.3-timetrap-1.15.1/lib/ruby/gems/2.4.0/gems/timetrap-1.15.1/bin/timetrap: interpreter directive changed from "/usr/bin/env ruby" to "/nix/store/dns77vf9frhd2s2xvcdd47rs2l08nqin-ruby-2.4.3/bin/ruby"
/nix/store/gygp1m5xbg8fp0w3vgm5mvkfjpn31hn0-ruby2.4.3-timetrap-1.15.1/lib/ruby/gems/2.4.0/gems/timetrap-1.15.1/bin/dev_t: interpreter directive changed from "/usr/bin/env ruby" to "/nix/store/dns77vf9frhd2s2xvcdd47rs2l08nqin-ruby-2.4.3/bin/ruby"
/nix/store/gygp1m5xbg8fp0w3vgm5mvkfjpn31hn0-ruby2.4.3-timetrap-1.15.1/lib/ruby/gems/2.4.0/gems/timetrap-1.15.1/completions/bash/timetrap-autocomplete.bash: interpreter directive changed from "/bin/bash" to "/nix/store/zqh3l3lyw32q1ayb15bnvg9f24j5v2p0-bash-4.4-p12/bin/bash"
checking for references to /tmp/nix-build-ruby2.4.3-timetrap-1.15.1.drv-0 in /nix/store/gygp1m5xbg8fp0w3vgm5mvkfjpn31hn0-ruby2.4.3-timetrap-1.15.1...
building path(s) ‘/nix/store/rw15v3rnlsha38wzqbp6j9rmxha4bppr-timetrap-1.15.1’
created 23 symlinks in user environment
/nix/store/rw15v3rnlsha38wzqbp6j9rmxha4bppr-timetrap-1.15.1

Success on x86_64-darwin (full log)
Partial log (click to expand)
1 gem installed
post-installation fixup
patching script interpreter paths in /nix/store/cpcv3pb070kx92xgjknhp0az4zwbfdry-ruby2.4.3-timetrap-1.15.1
/nix/store/cpcv3pb070kx92xgjknhp0az4zwbfdry-ruby2.4.3-timetrap-1.15.1/lib/ruby/gems/2.4.0/gems/timetrap-1.15.1/bin/dev_t: interpreter directive changed from "/usr/bin/env ruby" to "/nix/store/x67rsi7x2hhj9jx7yji0w2jfxjrksjl3-ruby-2.4.3/bin/ruby"
/nix/store/cpcv3pb070kx92xgjknhp0az4zwbfdry-ruby2.4.3-timetrap-1.15.1/lib/ruby/gems/2.4.0/gems/timetrap-1.15.1/bin/t: interpreter directive changed from "/usr/bin/env ruby" to "/nix/store/x67rsi7x2hhj9jx7yji0w2jfxjrksjl3-ruby-2.4.3/bin/ruby"
/nix/store/cpcv3pb070kx92xgjknhp0az4zwbfdry-ruby2.4.3-timetrap-1.15.1/lib/ruby/gems/2.4.0/gems/timetrap-1.15.1/bin/timetrap: interpreter directive changed from "/usr/bin/env ruby" to "/nix/store/x67rsi7x2hhj9jx7yji0w2jfxjrksjl3-ruby-2.4.3/bin/ruby"
/nix/store/cpcv3pb070kx92xgjknhp0az4zwbfdry-ruby2.4.3-timetrap-1.15.1/lib/ruby/gems/2.4.0/gems/timetrap-1.15.1/completions/bash/timetrap-autocomplete.bash: interpreter directive changed from "/bin/bash" to "/nix/store/pkjmwq7sqrvjg7cjiph6hq0khsmfl6p8-bash-4.4-p12/bin/bash"
building '/nix/store/17n1v9h6kfg4i2vnzxd35z3ksq57zlr6-timetrap-1.15.1.drv'...
created 23 symlinks in user environment
/nix/store/673b1pvjjin6xfv8np14dnhcba3g9s3k-timetrap-1.15.1


Consolidate design documents

Description

Project maintainers have decided to maintain the current and future architecture and design documents of the various OpenEBS engines/features in a single location in the current repository. Most of the component and feature design docs are scattered in individual repositories and some of them are missing. This effort is to consolidate all of them into a common location.
Example folder structure:
openebs / designs / replicated-pv / mayastor
openebs / designs / local-pv / hostpath | lvm | zfs | rawfile

Going with the suggested design. Thanks
openebs / designs / replicated-pv / mayastor
openebs / designs / local-pv / hostpath | lvm | zfs | rawfile

@avishnu @orville-wright @tiagolobocastro What about the design docs in the openebs/openebs repo, they seem to be very old and most them are for the deprecated engines? How about the below?
openebs / legacy(deprecated)/<here goes the dump?>

IMO, we should move the legacy docs to another folder in one of the archive org repos. Maybe "community" repo in the archive org.

Do we want to have an 'openebs' directory inside the openebs/openebs repo? Maybe we go with the suggested directory layout while stripping away the openebs prefix? E.g.:

designs/replicated-pv/mayastor
designs/local-pv/hostpath

On the legacy design docs. Maybe they should be moved to the openebs-archive org?

Do we want to have an 'openebs' directory inside the openebs/openebs repo? Maybe we go with the suggested directory layout while stripping away the openebs prefix? E.g.:

designs/replicated-pv/mayastor
designs/local-pv/hostpath

On the legacy design docs, IMO they should be moved to the openebs-archive org.

By openebs we meant the openebs repo.

Design documents for the Local PV engines have been updated. Pending for Mayastor.

Migration of confluence docs to mardown will be tracked in a separate ticket


Return type of useClient is not correct with default

Firstly, thank you very much for this awesome module!
Expected (like built-in useFetch)
// type of data is ref<Data[] | null>
const { data } =useFetch<Data[]>(url)

// type of data is ref<Data[]>
const { data } =useFetch<Data[]>(url, {default: ()=>[] }) // return type of default need to be compatible with Data[]

Actual Behavior with nuxt-open-fetch
// type of data is ref<Data[] | never[]>
const { data } =useClient(url, {default: ()=>[] })

Hi @kingyue737, thank you!
By default data will have union type of OpenAPI response type and the type from the default.
For example if you create /server/api/foo.ts handler:
export default defineEventHandler(async () => {
  return {
    bar: 'Hello',
  }
})

then you will see that the data is a union type of Nitro response and the type from the default:
// type of data is  Ref<never[] | { bar: string }>
const { data } = useFetch('/api/foo', {
  default: () => []
})

I think useFetch behaviour is incorrect :).
For example, if you add transform callback, it will also complain that it's return type should be Data[]. But in this case the transform is useless, because the whole point of transform is to change the data.
const { data } = useFetch<Data[]>(url, {
  transform: () => [],
  default: () => []
})

I think it makes sense to open an issue in Nuxt, because NuxtOpenFetch uses UseFetchOptions type from Nuxt and doesn't modify the logic of default/transform.

On the other hand, it is controversial whether default should be the same type as the OpenAPI/Nitro response type.

For example, if you add transform callback, it will also complain that it's return type should be Data[]. But in this case the transform is useless, because the whole point of transform is to change the data.

Agree. It's strange that return type of transform should be Data[].
However, in my opinion, default should be the same type as the OpenAPI/Nitro response type (or the type from the transform if it exists). Not only useFetch of Nuxt, but useAsyncState of Vueuse also forces default to be the same as response type. Aligning with Nuxt and Vueuse can ease the migration to nuxt-open-fetch.
Currrently, is it possible to wrap useClient in the user end to make it return ref<Data[] instead of ref<Data[] | never[]>? We used {default: ()=>[]} almost everywhere in our projects.


How could I understand the workload

Hi there, I have a question on understanding the workloads with different portions. I'm curious about the meaning of recordcount and operationcount. Such as for workloadb:
# Yahoo! Cloud System Benchmark
# Workload B: Read mostly workload
#   Application example: photo tagging; add a tag is an update, but most operations are to read tags
#
#   Read/update ratio: 95/5
#   Default data size: 1 KB records (10 fields, 100 bytes each, plus key)
#   Request distribution: zipfian

recordcount=1000
operationcount=1000
workload=com.yahoo.ycsb.workloads.CoreWorkload

readallfields=true

readproportion=0.95
updateproportion=0.05
scanproportion=0
insertproportion=0

requestdistribution=zipfian

Here the read/update portion should be 0.95/0.05. But why the readcount and operationcount are set to the same, should they be different, with portion same as 0.95/0.05?
Thanks!
Jun

hi @wuxiaomin98 - first off I edited your posting to improve readability.
The recordcount property is how many records will be 1) inserted into your database during the load and 2) how many records will be considered during the run.
The operationcount property is how many operations will be performed during the run.
All of the proportion properties effect how many of each type of operation is performed during the run. So, for your example read/update of 0.95/0.05, if you have a operationcount=100 then you will have approximately 95 read operations and 5 update operations. I say approximate because the proportions are not exact they are just odds.
You can read more about the properties in the wiki: https://github.com/brianfrankcooper/YCSB/wiki/Core-Properties.

Thank you so much! @kruthar
That makes much more sense. I do appreciate it!


Fixed config of vn_146_lv_small

Resolves #290

Ok upon inspection of the results that we get from this grid I realized there are no system participants connected whatsoever, so there is no power flow happening and we get no output that one could use for anything.
Given this fact @t-ober and I decided that it would probably be best to just remove this sample grid from the SIMONA code base alltogether, which will reduce overall maintenance needs. So could you please just delete the whole vn_146 grid directory and commit? Thanks!


Send error on invalid unsubscribe request

Right now, if we send an invalid subscribe request (request without dbType) via space-api-js, then Space Cloud sends an ack true even though it did not find any such subscription object. This gives a false indication that unsubscribe operation was successful even though it was not. Sending an invalid subscribe request is a bug of client API. However, Space Cloud should send error on such invalid requests rather than silently ignoring such errors and sending positive ack so that such problems can be detected and solved earlier.

Done


🔖(patch) bump release to 1.2.1

[1.2.1] - 2024-03-18
Added:

Enable email lookup for Keycloak-OAuth

Wooopsie, I forgot everything, I wasn't focused


Sync doc with integration core repo

Since we are now pulling content from the doc, here are all the information that were on the documentation integration pages but not on the readme page.

Are we losing images here?

@irabinovitch we are losing no images either here or on the doc. when we can import images directly with an URL images will be displayed on this repo too (now they are only displayed on the doc)
LGTM ?

I'm not sure why we can't include images here now? But I wont block merging on it.


updated

Fixes Issue

Changes proposed

Screenshots

Note to reviewers

Code of Conduct

[ ] By submitting this pull request, I confirm I've read and complied with the CoC 🖖

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

You can also join our Discord community.
Feel free to check out other cool repositories of the Thecyberworld.
Join the Thecyberworld GitHub Organisation by raising an issue (you will be sent an invitation).

done


Non-root user not able to start w3svc service in docker

I'm working with the docker image mcr.microsoft.com/dotnet/framework/aspnet:4.8-windowsservercore-ltsc2019. I've noticed that the default user for windowsservercore is ContainerAdministrator.
If I try to run the image with the user ContainerUser docker run -u ContainerUser mcr.microsoft.com/dotnet/framework/aspnet:4.8-windowsservercore-ltsc2019 I get the following error:

ERROR: Failed to stop or query status of service 'w3svc' error [80070005

]. I think that the error is related to the permissions that the user needs to run ServiceMonitor. So, first of all, is it correct to assume that windowsservercore images must run with ContainerAdministrator and cannot run with ContainerUser?
If the assumption above is correct I would like to confirm if running the container with ContainerAdministrator can expose the container to a security issue. As far as I understand even if the ServiceMonitor.exe is started with ContainerAdministrator the external-facing process is the IIS Windows service, which runs under a local account in  IIS_IUSRS group. So even if an attacker could compromise the application it will not have administrator access to the container. Can anyone confirm if this is correct?
Dockerfile:
# escape=`

FROM mcr.microsoft.com/dotnet/framework/aspnet:4.8-windowsservercore-ltsc2019

ENV website-name=WebApp

WORKDIR /

RUN mkdir C:\WebApp

COPY WebApp/ /WebApp

RUN powershell -Command  `
    New-Website -Name 'WebApp' -IPAddress '*' -Port 443 -PhysicalPath C:\WebApp -ApplicationPool 'DefaultAppPool' -Ssl -SslFlags 0; `

USER ContainerUser

ENTRYPOINT ["C:\ServiceMonitor.exe", "w3svc"]

Hi,
Do we have any workaround or guidelines around using IIS with a non-root user (ContainerUser) inside the containers?
Any help would be highly appreciated.

+1 - Any update??

+1 - Any update??


Looking for clarification on how this sharing setting affects guest users and external members

What is the definition of the term "in-tenant users" in this statement?

The whiteboard is also shared with any in-tenant users in the meeting

Said differently, are guest user objects created via Entra ID's B2B capabilities considered as "in-tenant" or not? Are external member objects created via Entra ID Cross-Tenant Sync "in-tenant" or not?
The setting name that is activated in SPO via the Set-SPOTenant cmdlet seems to only apply to anonymous users who do not have any kind of an object in the host Entra ID tenant for the Teams meeting, but there are other references in this article that I feel could also include B2B guests and/or CTS external members as not being "in-tenant" users.
Can someone help clarify this please?
Thank you,
John

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: f09002ff-a559-6874-bfd8-a953babc86df
Version Independent ID: f09002ff-a559-6874-bfd8-a953babc86df
Content: Manage sharing for Microsoft Whiteboard
Content Source: microsoft-365/whiteboard/manage-sharing-organizations.md
Service: microsoft-365-enterprise
GitHub Login: @johnddeweese
Microsoft Alias: alexfaulkner

@alexsfaulkner

@tiburd Please assign this issue to Alex as it is not showing up in assignee field. Thanks

In-tenant users in this instance does not include guest users. Just users that are a part of said tenant. we currently do not have sharing capabilities with guest users.

@alexsfaulkner Thank you very much for sharing this explanation. @ferringer Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


HR Zones settings missing in manifest

The HR zone settings (zone min max HR) as can be set on the TomTom website are missing in the manifest, at least in manifest_0001073e.txt
You can add following:
hrzone/easy/min,255,i,1,bpm,,
hrzone/easy/max,256,i,1,bpm,,
hrzone/fatburn/min,257,i,1,bpm,,
hrzone/fatburn/max,258,i,1,bpm,,
hrzone/cardio/min,259,i,1,bpm,,
hrzone/cardio/max,260,i,1,bpm,,
hrzone/perform/min,261,i,1,bpm,,
hrzone/perform/max,262,i,1,bpm,,
hrzone/peak/min,263,i,1,bpm,,
hrzone/peak/max,264,i,1,bpm,,
Typical values from my watch:
253 unknown                                            35651584
254 unknown                                            1
255 hrzone/easy/min                                    87
256 hrzone/easy/max                                    104
257 hrzone/fatburn/min                                 105
258 hrzone/fatburn/max                                 122
259 hrzone/cardio/min                                  123
260 hrzone/cardio/max                                  139
261 hrzone/perform/min                                 140
262 hrzone/perform/max                                 157
263 hrzone/peak/min                                    158
264 hrzone/peak/max                                    174
265 running/training/zones/heart/custom/low            110
The percentages as mentioned with the settings on the TomTom MySports site with the HR values do not appear in the settings list. When I change them no alterations appear when I connect the watch to the MySports application.

Thanks. I've added them to the manifest file.


refactor: correct typos and standardize capitalization in Cargo.toml

#5063  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite


Update the servicebus binder samples.

Update the samples of servicebus-queue-binder, servicebus-queue-multibinders and servicebus-topic-binder.

Let's combine the directory of azure-spring-cloud-stream-binder-servicebus-queue and azure-spring-cloud-stream-binder-servicebus-topic into one directory as spring-cloud-azure-stream-binder-servicebus, also don't forget to change the link in each readme.


Why Is --workspace-folder Required. Can we default to $PWD?

I found it odd that this parameter was required when using devcontainer up and was wondering why and if that was intentional. Not sure if it is also required in other commands ( just learning here ) but did want to share it felt odd to do this.
$ devcontainer up --workspace-folder .

Even more confusing is the devcontainer build [path] which still require --workspace-folder, seems like a bug, either path or workspace-folder but not both please.

Having to type --workspace-folder . all the time is crazy annoying. Please default to $PWD.

Having to type --workspace-folder . all the time is crazy annoying. Please default to $PWD.

And add support to specify using an ENV variable as well, DEVCONTAINER_WORKSPACE_FOLDER or whatever.

I've created a PR #425, with a basic check if a .devcontainer directory exists in your cwd. I would be pretty easy to add an ENV variable to it, by adding it to the findWorkspaceFolder Function.
@hpe-ykoehler Currently, I'm not convinced if an ENV variable is needed. Do you have a use case for that?

@MunsMan no, but convention is that config option can be controlled by cli argument, env or config file in that order of priority.  Agree env may appears less useful, but devcontainer should use a CLI framework that handles all those details (such as Cobra if written in Go) no?

I'd suggest not to add the environment variable support unless someone asks.

I added this function to my .zshrc, which does not solve the problem, but reduces the pain:
function dev() {
     devcontainer $1 --workspace-folder . ${@: 2}
 }

Now I can just call dev up or dev exec ls
Maybe it helps someone while the Issue exists.

I added this function to my .zshrc, which does not solve the problem, but reduces the pain:
function dev() {
     devcontainer $1 --workspace-folder . ${@: 2}
 }

Now I can just call dev up or dev exec ls
Maybe it helps someone while the Issue exists.

I did something similar that also takes an optional environment var.  The following will set --workspace-folder to  $WORKSPACE_FOLDER if it is set, defaulting to the present working directory ($PWD).
function dev {

workspace_folder=${WORKSPACE_FOLDER:-$PWD}

case $1 in
'up' | 'build' | 'run-user-commands' | 'read-configuration' | 'exec')
  # specify the workspace folder to commands that need it
  dev_cmd=$1
  shift 1
  devcontainer "$dev_cmd" --workspace-folder "$workspace_folder" "$@"
  ;;
*)
  # directly run everything else
  devcontainer "$@"
esac
}

That said, please don't take my contribution of a robust BASH warpper as any indication that this isn't an issue.  Things like may seem small, but are problematic for the ergonomics of this CLI tool.

We should be able to pick this up soon

Polite ping :)
I see three people have attempted to do this in a smart way (recursing up parent directories looking for either .devcontainer or .devcontainer.json) and all ended up either abandoned or in review hell; perhaps it's worth doing the dumb and simple thing of just "set the default to '.'" in order to satisfy the most common use-case, and the fancy recursion can be added as a backwards compatible enhancement later?


Bugs in Colored Markers Step 2

Describe the Issue
I am able to pass this step by completely removing all HTML from the editor. I am also able to pass this step if I add the correct head and body elements but delete everything else. Finally, I am able to pass this test if I add the body element before the head element.
Affected Page
https://www.freecodecamp.org/learn/2022/responsive-web-design/learn-css-colors-by-building-a-set-of-colored-markers/step-2
Your code
Described above.
Expected behavior
I'm not sure how many of these bugs absolutely need fixing but I would think the empty editor bug should be fixed for sure. And since the instructions ask that the body element be added after the head element we should probably fix that one as well.
Screenshots
No response
System
Confirmed with newest versions of both Chrome and Firefox.
Additional context
No response

The querySelector tests can be tricked by the fact that some things are automatically added by the browser.
But all these, how can these pass if the code is empty?
https://github.com/freeCodeCamp/freeCodeCamp/blob/428de4154dbb41576bacc34ed31d7639a9a0d9d7/curriculum/challenges/english/14-responsive-web-design-22/learn-css-colors-by-building-a-set-of-colored-markers/61695ab9f6ffe951c16d03dd.md?plain=1#L17
https://github.com/freeCodeCamp/freeCodeCamp/blob/428de4154dbb41576bacc34ed31d7639a9a0d9d7/curriculum/challenges/english/14-responsive-web-design-22/learn-css-colors-by-building-a-set-of-colored-markers/61695ab9f6ffe951c16d03dd.md?plain=1#L23
https://github.com/freeCodeCamp/freeCodeCamp/blob/428de4154dbb41576bacc34ed31d7639a9a0d9d7/curriculum/challenges/english/14-responsive-web-design-22/learn-css-colors-by-building-a-set-of-colored-markers/61695ab9f6ffe951c16d03dd.md?plain=1#L29
https://github.com/freeCodeCamp/freeCodeCamp/blob/428de4154dbb41576bacc34ed31d7639a9a0d9d7/curriculum/challenges/english/14-responsive-web-design-22/learn-css-colors-by-building-a-set-of-colored-markers/61695ab9f6ffe951c16d03dd.md?plain=1#L35
this the file
https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/challenges/english/14-responsive-web-design-22/learn-css-colors-by-building-a-set-of-colored-markers/61695ab9f6ffe951c16d03dd.md

I stuck a console.log(code) in the first test and when there is no content in the editor code equals . I don't know enough about how this works to know why that's the case, but that explains why it is passing when there is no content in the editor.

@ojeytonwilliams ???

Opening again. Someone in the forums just discovered that the following will pass this step:

It also passes

And probably other variations as well. This is with FF 100 on linux. I think browsers are just too good at fixing bad HTML :smile:


Golint'ing the code

Fixes some suggestions from golint.

No functional changes introduced here, getting this in.


"Report number" field is incorrectly translated into the "issue" field when importing a techreport from a .bib file

Debug log ID
6JFT6T6Q-refs-euc/6.7.143-6
Expected behaviour
I want to import a .bib file in Zotero, which contains only reports ("@techreport" entries). Each one of them has a "number" field, that I expect to become a "Report Number" field once imported in Zotero.
The import does behave as expected when Zotero Better Bibtex is disabled:  the "number" field is indeed used to populate the "Report Number" field in Zotero.
Actual behaviour
However, when Zotero Better Bibtex is enabled, the "number" field is saved as an "Issue" in the "Extra" attributes of Zotero. For instance, importing the following entry from a .bib file produces the result pictured in the screenshot here below:
@techreport{customCitationKey,
  title = {What a Great Report},
  author = {{A very well-known and serious institution}},
  year = {1995},
  month = jan,
  number = {my\_precious\_report\_number},
  pages = {6},
  langid = {english}
}

Source of the issue
While trying to find where the problem comes from, I have found that the BibTeX translator used by Zotero specifically addresses the case of techreports through a "fix" (as commented). Lines 398 through 400 are reproduced below:
else if (field == "number") { // fix for techreport
		if (item.itemType == "report") {
			item.reportNumber = value;

I wanted to check whether the Better Bibtex translators were also taking this specific case into account, but it does not seem to be the case. In bibtex.ts, line 943, the "number" attribute is defined as such:
protected $number(_value: string): boolean {
    let field = 'issue'
    let numbers = (this.bibtex.fields.number || []).map(n => `${n}`)
    const issues = (this.bibtex.fields.issue || []).map(n => `${n}`)

    if (this.item.itemType === 'patent') {
      field = 'number'
      if (this.patentNumberPrefix) {
        const patentNumberPrefix = this.patentNumberPrefix.toLowerCase()
        numbers = numbers.map(n => n.toLowerCase().startsWith(patentNumberPrefix) ? n : `${this.patentNumberPrefix}${n}`)
      }
    }

    return this.set(field, numbers.concat(issues).join(', '), [field])
  }

Here, let field = 'issue' does seem to define "issue" as the default field for the number attribute. An exception is made for patents below. I may very well be mistaken and maybe other files are involved, but I guess that this part of the code should be changed to take into accounts the "report" itemType and add another exception. If you can confirm that it would indeed fix the problem, I can try and submit a pull request.

Thank you for reporting this. Build 5634 fixes it. If you can confirm that this does what you need, I can cut a new release.

I would like to suggest more item types besides report. The following is a list of Zotero item types that have number fields (taken from https://github.com/zotero/zotero-schema/blob/master/schema.json by searching : "number").

Zotero item type
number field name
biblatex entry type

bill
billNumber
legislation (Non-standard type)

case
docketNumber
jurisdiction (Non-standard type)

dataset
number
dataset

hearing
documentNumber
-

patent
patentNumber
patent

podcast
episodeNumber
audio (Not specified but used in biblatex-apa)

preprint
archiveID
-

radioBroadcast
episodeNumber
audio (The most suitable type I guess.)

report
reportNumber
report

standard
number
standard (Non-standard type)

statute
publicLawNumber
legislation (Non-standard type)

tvBroadcast
episodeNumber
video (Not specified but used in biblatex-apa)

Don't know how I missed that. A new build is incoming. I haven't changed video and audio entry types though. I don't think mapping @video to tvBroadcast and @audio to radioBroadcast is warranted.

Thank you very much for this very quick fix, it works exactly as expected with test build <IP_ADDRESS>52.5634. And thank you for this add-on in general, it is incredibly useful!

That implements all the changes outlined above


2023-08-07 meeting

I think I got this right? There was some extra postponing and stuff that the script didn't totally capture correctly, so I could use some double checking around that. Also I think CA-14 was just pulled, is that correct?

Looks good to me. I like the background color-coding. Is this new or did I just not notice previously?

@ivancich been that way almost since day one!


Make it easier to use in-cluster configurations

New method to create an env with an in-cluster config
New method to create a Config with an in-cluster config
New method MustClient(t) to return the client without worrying
about error handling every time.
New example for simple_API tests that utilize an in-cluster config

Partially addresses: #54
Fixes: #58
Signed-off-by: John Schnake<EMAIL_ADDRESS>

/ok-to-test

/test

I removed a section of code that was deleting the kubeconfig entirely as I suspected that was causing an issue. Locally I was able to repro the issue and this did fix it; now its still happening in CI. TBD.

/retest

I don't expect the next set of tests to pass but I'm trying to figure out whats going on in the test invocations on the host. Just filed a few other issues #67 #66

After updating to gexe 0.1.1, got a green test run. Trying again to ensure its not a fluke. See https://github.com/vladimirvivien/gexe/issues/41


"Most recently fetched config is already activated" after remote config activate() call

[REQUIRED] Step 2: Describe your environment

Xcode version: 10.3
Firebase SDK version: 6.6.0
Firebase Component: Remote Config
Component version: 4.2.1

[REQUIRED] Step 3: Describe the problem
We fetch and activate remote config with the following code:
let expirationDuration: TimeInterval
#if DEBUG
expirationDuration = 0
#else
expirationDuration = 3600
#endif
firebaseRemoteConfig.fetch(withExpirationDuration: expirationDuration) { [unowned self] (status, error) in
    if status == .success {
        log.info("Remote Config fetched")
        self.firebaseRemoteConfig.activate(completionHandler: { (error) in
            if let error = error {
                log.error(error)
            }
        })
    } else {
        log.error("Remote Config could not be fetched. \(String(describing: error))")
    }
}

We call this part of the code only one, in AppDelegate during didFinishLaunchingWithOptions
In the wild, we see lots of Remote config errors reported, they're pretty straightforward:

ActivationFailureReason: Most recently fetched config is already activated
Code: 8003

Is it an error to try to activate fetched config when it's the same as active one? If yes, which approach should we take?
We can't use the fetchAndActivate since it doesn't have the expirationDuration parameter.

If your goal is to make sure the values in RemoteConfig are up-to-date, this code will work and you can ignore the error.
@dmandar is this intentional? If we have an error that we recommend users ignore, can we downgrade the error to an info/debug log instead?

The error object always contains a value when activation cannot succeed. In this case, the already fetched config (present in the cache) is also already activated and no new activation can take place.  If you prefer, you can use fetchAndActivate by pre-configuring the fetchInterval in the configSettings at initialization time which returns more granular status regarding whether both remote fetch and activate succeeded.

Thanks for the feedback. We are working on improving the return status of the existing API. In the meantime,  if appropriate, please use the new fetchAndActivate API which should have more granular status.

There is already a warning logged at https://github.com/firebase/firebase-ios-sdk/blob/master/FirebaseRemoteConfig/Sources/FIRRemoteConfig.m#L298.
Why not pass nil to the completion handler at https://github.com/firebase/firebase-ios-sdk/blob/master/FirebaseRemoteConfig/Sources/FIRRemoteConfig.m#L308?
The functionality should be exactly the same as the success case.

Fwiw, On Android, it seems like we have a bool that indicates whether it was already activated
https://github.com/firebase/firebase-android-sdk/blob/2d3b7c25070d21f2058c5471c1831f7d8ac065fd/firebase-config/src/main/java/com/google/firebase/remoteconfig/FirebaseRemoteConfig.java#L233


Radial plot update

Fixes:

Problems with small values fixed (actually all values were wrong earlier due to a scaling issue).
Plot does not fail if there is only one group entry/few entries overall.

picked up on pull request #19


Could you share a copy of dataset for training and testing?

Our training dataset is the same as eSL-Net, as our method only need gray-scale images in training procedure. For testing dataset, we only regenerate the RGB blurry image, you can obtain them described in our supplementary material.


Support protobuf encoding for MQTT source

Is your feature request related to a problem? Please describe.
I want to consume Sparkplug messages which the payload is a protobuf spec over standard mqtt. Not all industrial sensors/protocols natively support mqtt, sparkplug bridges this gap.
Supporting protobuf will enable use cases like this and users who prefer protobuf over json for efficiency.
https://www.hivemq.com/solutions/technology/mqtt-sparkplug/
https://www.hivemq.com/blog/strong-adoption-of-mqtt-in-iiot/
Describe the solution you'd like
Just like Kafka, nats and rest add a protobuf encoding with file and/or other schema location.
This will also add more consistency to the encoding options over all message queues.
Describe alternatives you've considered
No alternative available.
Additional context
No response

The MQTT source was done by the community #15388. Welcome for contribution!


Add LGTM code quality badges

Hi there!
I thought you might be interested in adding these code quality badges to your project. They will indicate a very high code quality to potential users and contributors.
To get an idea of the analyses reflected by these grades, check the alerts discovered by LGTM.
N.B.: I am on the team behind LGTM.com, I'd appreciate your feedback on this initiative, whether you're interested or not, if you find time to drop me a line. Thanks.

We're going to pass on this PR for now but thanks for alerting us to LGTM. We're using it on Aurelia vNext 😃

Hi @EisenbergEffect
Indeed, I know Aurelia is a user of LGTM :-)
Thanks for this
Note that our recommendation is to activate automated code review, to ensure that all your PRs are analysed immediately. This is a one click operation, and free for open source, as you already know
Best


Implement change trie for child trie.

This PR is an attempt to fix #2622.
It makes changes trie handle child trie content.
It makes a few choice, so it is only a proposal and things can be change:

a third change trie input node type: a child trie node containing the root of the child change trie.
An alternate way of doing things would be to directly put child changes content into the top change trie with another new node (index build over encoding of block, encoded child trie key, child trie content key).
those new change trie child nodes are not used in digest (it would be very straightforward to implement), digest nodes are still only build with former existing nodes.
child trie node change of root do not see its extrinsics registered as previously (the information being the sum of the change child trie extrinsics) : this can be restored from former code (a hashset keeping trace of change globally in overerlaychange), or build at the time child trie root is calculated.

It also will also need some changes after #2209, main question being do we refer to child trie keyspace or parent address, in this case parent address seems to be right addressing.
I also wonder if removing block number info from change trie keys could be a good idea?
cc/ @svyatonik
It would requires prefixing memorydb key with encoded block number, and pruning could be done by directly removing all keys starting with this block number prefix (no need for trie parsing).
Similarly change trie child content could be prefixed by a unique id such as its storage path to be able to isolate its key values without trie parsing (but I got no direct use case except for being able to export change child trie without trie parsing).

I'm still not sure - why separate tries are better than one trie for both top + all children tries. Do you have an opinion on this?

Flattening child trie in the parent trie seems doable (putting optional child storage key in the input keys).
So indead it will skip one hash per child trie and will certainly be more efficient for construction (plus code will be simpler I believe).
For what it is worth there may be some possible quicker access for multiple child trie content (the parent trie query/proof can be shared). But this can also be achieved with flattened child trie by basing the triedb on an middle branch node corresponding to the common encoded key bytes of all child trie nodes (plus possible partial for key).
In my opinion, what could justify the use of child trie is only wether we want to split change trie or not.
If we want to be able to revert some child trie to a previous state, we could use the former child trie to, but I do not think this would really make sense (pushing some special info in change trie seems more relevant).
So splitting change trie could only make sense if we want to move child trie state between chains, then the accompanying child trie part can be move, but here again it does not make much sense unless if we want to rebuild some child trie history (we need to keep header and a child trie root inclusion proof) with related change trie.
This only works cleanly if child trie get some prefix (similar to #2209) to fetch their key in the collection (currently no prefix are use on child trie).

if there are no strong requirements for using separate tries, I'd prefer to do some benches before merging this PR. Like - given the same set of changes how faster/slower is maintaining multiple tries vs big single

Hypothetical, the usage of child trie in digest may lead to skip some trie access (but the common child trie path would be cached in case of a big single trie). I don't have any idea if it can make for the added indirection level on creation.

OK - you must be talking mostly about #2832, right (I mean reverting changes trie to previous state)? So the only advantage is potential boost of a revert-to-block performance. But imo it doesn't make sense. Like if you are going to revert to block#500 when you're at the block#1000, then changes trie for block#500 isn't the changes trie you want to duplicate for block#1000. Changes trie contains state difference between current and previous blocks. Example:

at block#499 there's only one key in storage: [key1 => Some(value1)];
at block#500 another key is inserted (key2 => Some(value2)) => changes trie for block#500 will contain these keys: [key2];
at block#600 another key is inserted (key3 => Some(value3));
when at block#1000 you want to revert to state of block#500, then the changes trie for block#1000 must have keys: [key3], not the [key2] as changes trie for block#500. That's because only key3 has been changed in 500...1000, and key1 + key2 were staying the same.

Or have I misunderstood something? So imo we must build changes trie from the scratch as we normally do in the case of revert-to-block operation.
I'd also summon @gavofyork here - maybe he has a strong opinion on whether we need one-changes-trie-per-child-trie, or not.

About reverting, I ended up with the same conclusion as you (does not make sense for change trie).
When considering extracting a child trie globally from a chain, I did see a possible interesting thing (keeping change trie history, but for similar reason it may not be that useful).

@svyatonik , if you wish to bench a bit, I did a quick implementation of flattened child trie here:
https://github.com/paritytech/substrate/compare/master...cheme:ch-ch-trie2?expand=1
(tested only over substrate-state-machine and with low code quality).

Ah, I've also started that :) Nvm - will use your version, thanks! :)

Okay, I've got some bench results. And actually this implementation works faster than implementation from ch-ch-trie2. Here's the test that  I've used and results. Measured time is execution time of build_changes_trie() call, though I've also measured total time of trie.insert()-s and again it is better for this PR. Since performance has been my only concern, I think better to stick with separate changes tries, as you've suggested. Thanks for your help!

That is not really what I expected, it comes probably from the trie reading being split. I would say trie.insert can be improve a bit by using algo such as 'iter_build' in https://github.com/paritytech/trie/pull/11 , but for build_changes_trie it would change nothing.

@cheme Is this still "A3-inprogress"? :)

Oh, I forgot to switch the tag, thanks.


Texture Canvas examples do not work in 5.0

https://doc.babylonjs.com/extensions/textureCanvas links to two Playground examples which do not seem to work in 5.0.0 but do work in 4.2.0 , for me (Chrome, webgl2, linux).
So this may be more of a TextureCanvas extension issue than a documentation issue. But for now the documentation could link to a 4.2.0 playground (if possible) to avoid confusion.

I ping @poolminer there as he is the maintainer for the TextureCanvas so lets see if he is available to help :-)
cc @RaananW and @PirateJC for the follow up.

Since Texture Canvas is a community supported feature, until it is updated to work with 5.0, I'll add a note in the doc that makes it clear that the feature should be used with 4.2 and below.

Addressed in this PR: https://github.com/BabylonJS/Documentation/pull/663


e2e test for heterogenous cluster

Issue link

https://issues.redhat.com/browse/RHOAIENG-13430
What changes have been made

Added new e2e test for heterogenous cluster
Verification steps

Needs kueue with this change https://github.com/opendatahub-io/kueue/pull/52
Checks

[x] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[ ] Manual tests
[ ] Testing is not required for this change

@Ygnas we may need e2e test for heterogenous cluster to support for openshift clusters aswell to run on downstream testing


Change external_id to id

The documents API is changing to be just 'id' instead of 'external_id'.
These changes adhere to the new requirement.
Bumped to version 3.0.0 since this is a breaking change.

I tested these and the changes look good, just make that change i suggested and you'll be 👌.


module: gem5stats: enable asynchronous origins in gem5 stats file

Currently, reset_origin() in the gem5stats module enables to virtually
truncate the existing dumps from the gem5 statistics file so that any
subsequent match() calls will apply only on new dumps. However, the
current implementation resets the origin of the stats file unilaterally,
without other clients knowing about it, hence leading to data being
lost.
This commits removes the reset_origin() method and provides a different
API to handle virtual truncatures in the stats file. Namely, the match()
method now takes a base_dump parameter letting clients specifiying from
which dump they want match() to apply. This feature could also be usefull
if someone wanted to add off-line processing features for statistics
files.

Fixed commit message typo, docstrings and removed unecessary \.

Anything left preventing from merging ?

Since this is gem5-related, I'd like ether @Sticklyman1936 or @avanlaer  to OK this before merging.

This looks good to me. Seems like a nice way to deal with this issue. Would be interesting to see how well this sort of approach will work if we ever figure out how to deal with the gzipped stats files. However, this seems perfect for the time being. Thanks a lot for doing this!