LedgerIndexBound constraint is too strict

This constraint on LedgerIndexBound is too strict. For example, some responses to the account_tx method will return a response like this:
{"account":"r9m6MwViR4GnUNqoGXGa8eroBrZ9FAPHFS","marker":{"ledger":61363309,"seq":2},"ledger_index_max":61391079,"ledger_index_min":0,"transactions":[],"validated":true,"status":"success"}

This is a bug in the clio node powering s2.ripple.com. This bug will be fixed via https://github.com/XRPLF/clio/issues/148


Using 4.2.2  error in provider assignment oci.home = oci.home

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version and Provider Version

4.2.2
Affected Resource(s)

oci provider
Terraform Configuration Files

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file.
# Please remove any sensitive information from configuration files before sharing them.

In provider.tf
provider "oci" {
fingerprint      = var.api_fingerprint
private_key_path = var.api_private_key_path
region           = var.region
tenancy_ocid     = var.tenancy_id
user_ocid        = var.user_id
}
provider "oci" {
fingerprint      = var.api_fingerprint
private_key_path = var.api_private_key_path
region           = var.home_region
tenancy_ocid     = var.tenancy_id
user_ocid        = var.user_id
alias            = "home"
}
In main.tf
providers = {
oci.home = oci.home

}
Debug Output

Panic Output

Expected Behavior

providers downloaded/installed
Actual Behavior

]$ terraform init
Initializing modules...
There are some problems with the configuration, described below.
The Terraform configuration must be valid before initialization so that
Terraform can determine which modules and providers need to be installed.
â•·
â”‚ Error: Invalid type for provider module.oke.provider["registry.terraform.io/oracle/oci"].home
â”‚
â”‚   on main.tf line 42, in module "oke":
â”‚   42:      oci.home = oci.home
â”‚
â”‚ Cannot use configuration from provider["registry.terraform.io/hashicorp/oci"].home for module.oke.provider["registry.terraform.io/oracle/oci"].home. The given provider configuration is for a different provider type.
â•µ
Steps to Reproduce

Important Factoids

I am moving from version 4.1.6 (refers to old oci provider location, so it does not work anymore)
to version 4.2.2 (where I get this issue).
References

If you are using it as a remote module, then you need to set the OCI provider namespace like this:
terraform {
  required_providers {
    oci = {
      source                = "oracle/oci"
      configuration_aliases = [oci.home]
      version               = ">= 4.67.3"
    }
  }
  required_version = ">= 1.0.0"
}

Hello, thanks a lot.
But I don't know where to put this, and what does it replace.
I think the documentation section "Provision using the HashiCorp registry module" should be updated

We'll add this in the documentation


New version: Tencent.QiDian version <IP_ADDRESS>62

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.5 schema?

Microsoft Reviewers: Open in CodeFlow

@wingetbot waivers Add Validation-Domain


[flawhud] Issue with Mode Selection

There's a weird bug in the mode selection menu. When it's set to default, the options are misaligned, and with the old selection they're just non-existent. I have a 1900 x 1200 resolution and an 6:10 aspect ratio, but changing them didn't seem to fix the problem.
I don't know, nor if I checked, if this is an issue with TF2HudEditor or the Hud itself, but I'd like to see this fixed.

Alright, thanks.  Thanks man!

Alternatively, you can try the preview build: https://github.com/CriticalFlaw/TF2HUD.Editor/releases/tag/3.4.2


Show total orders for customer in customers list

The problem is that you cannot query for totals until you know the customer ids you want to show, so you need to fetch those from the registry first, and then have other services compose their data into the page.
Is this PR a good solution?
Currently I have a couple of issues with it myself:

The customersController now needs to execute 2 queries. It does both of them via the backendCompositionService, but I might as well do the first one directly since no other service can (and should) probably provide the list of customers.
This solution doesn't particularly scale well: what if I need to compose in more data based on the results from customers-list-details. Making the customersController aware of this all creates coupling, thereby bypassing the value of backendCompositionService. I think Udi talks about raising events that a particular piece of data is available, and other services can subscribe to this and do their work. I might try to cook something like that up later.

Interested in your thoughts!

Hey @FreekPaans first of all sorry for the long delay, vacation and a lot of work.
The problem you are highlighting is an obvious problem the arises immediately if you try to apply the technique illustrated in the sample to something real-world and it is really similar to the select N+1 issue.
Back to your questions, before diving into to what I have in mind:

The customersController now needs to execute 2 queries. It does both of them via the backendCompositionService, but I might as well do the first one directly since no other service can (and should) probably provide the list of customers.

That's a good point, I agree with the statement I might as well do the first one directly since no other service can, I decided originally to go through the backendCompositionService to achieve to goals:

Use the same API everywhere to issue queries from the client to the back-end(s)

Hide the complexity of the client side model composition allowing the composition strategy to change over time or to be transparently adapted to multiple different scenarios

This solution doesn't particularly scale well: what if I need to compose in more data based on the results from customers-list-details. Making the customersController aware of this all creates coupling, thereby bypassing the value of backendCompositionService.

Good point once again, the solution as-is does not scale, if you need to list 10 products you are going to issue 1 request to retrieve the 10 ids and then 10 queries to retrieve descriptions, and 10 to get prices...and more..and more... select N+1.

I think Udi talks about raising events that a particular piece of data is available, and other services can subscribe to this and do their work. I might try to cook something like that up later.

Events can be the a solution but in my opinion solve a different problem (We are actually discussing various approaches internally, stay tuned :smile:). The real solution is to batch requests and the backendCompositionService can do that:

the client wants the products-list|top:10:

backendCompositionService.execute( 'products-list', 'top:10' )
    .then( function( composedResults ){
      //bind the results or do something interesting :-)
    } );

Now as you highlighted there just one single service that can answer the above question the productsService, all the others actors are simple servants that need the list of ids in order to answer the question.

Can we say then that given a logical client query (the products-list in the above sample sample) in order to solve the request we need?

a query owner
zero or more query handlers that may integrate owner results

If we agree on the above then we can say that composing some data is at least a 2 steps process:

get master data (at minimum the ids)
get the all the others :smile:

The above 2 steps process can be all solved by the backendCompositionService as in the above sample or as you highlighted can be solved using 2 explicit steps:
productsService.listProducts( 'top:10' )
   .then( function( productIds ) {

      backendCompositionService.compose( 'products-list', productIds )
       .then( function( composedResults ){
         //bind the results or do something interesting :-)
       } );

   } )

I do prefer the first approach, but it is just a technical detail.
Imagine now that the composed data that we need to show are framed as:
product-id (from the productsService)
      product-highlights (from the marketingService)
      product-price (from the pricingService or salesServices)

Using the above technique the problem is solved, or should be, if the composed ViewModel has data coming from 5 different services you end up with 6 requests.
There is still 1 potential issue that we need to face, now...the above starts from one assumption: there will be a templating engine that will passively accept the composed data and simply bind them to visualize something on the user screen.
But it is not always the case. Events to the rescue.
I imagine the following information flow

the user clicks on a link in order to visualize a list of products (top 10)
the actual screen transitions to the products-list-view
the products-list-controller will query its own productsService
the products-list-controller will raise a client event broadcasting products-list-ready along with the retrieved ids
anyone interested in that event will chime in and issue its own queries

This second approach is more UI driven since is the shape of the UI that is causing someone to react to the event where on the contrary the first one is more data driven since the UI is generated by what is found in the composite structure.
In all the cases what we want to avoid is to start binding data and let the binding engine trigger the data fetch process, all the data must be fetched before binding anything to the UI other wise the select N+1 problem will screw everything up. Imagine a scenario where:

the list of ids is retrieved
the list of ids is bound to the UI causing (in the above sample) 10 elements to be generated
10 views with 10 controllers will start fetchting data from the services

In such a scenario the only solution is to be able to batch request, the issue is that since you have no control on who is involved the only viable approach (and if you can come up with something better I'd love to hear from you) is batch based on time, you can then collect outgoing HTTP requests and issue them batched if for a certain amount of time there is no other requests (or similar logic). Somewhat fragile IMO.
Comments? Thoughts?

productsService.listProducts( 'top:10' )
   .then( function( productIds ) {

      backendCompositionService.compose( 'products-list', productIds )
       .then( function( composedResults ){
         //bind the results or do something interesting :-)
       } );

   } )

The above comes with an interesting advantage: it removes entirely the need to define a query owner since all what the backendCompositionService is doing will be done using what I defined as servants so the order in which they are executed is not relevant.
Removing the owner, although, removes the option to have multiple levels of details:

product

description
price
related-products [list]

description
price

Wow, a lot of answers, thanks.

Good point once again, the solution as-is does not scale, if you need to list 10 products you are going to issue 1 request to retrieve the 10 ids and then 10 queries to retrieve descriptions, and 10 to get prices...and more..and more... select N+1.

I was initially concerned with two kinds of scaling: performance and coupling. The performance problem is indeed select N+1, I solved that in my PR by indeed fetching the totals for all Id's at once (and not issue a request per Id). I think if you keep that strategy, you're gonna need at most 1 query per service.
A larger problem is that my current solution can't handle the case where you need to 'join' in additional (multi-level) data based on a 'servant' result, such as your later example with the related products, without letting the customersController know about the other services, which is what you want to avoid.
What I'm afraid is going to happen is that you need to define all kinds of thing such as product-list-ids-ready, product-list-descriptions-ready, product-list-related-ready, etc.  Don't really see how to solve that, yet.
I'm not exactly sure in what way your flow with the backendCompositionService differs from the event flow: they both seem to raise events (product-list and product-list-ready respectively). Is it because you're composing the returned data into a common object? I'm not sure if that makes a fundamental difference (you could choose to not put anything in the composedResults and directly update views from the query handler).

This second approach is more UI driven since is the shape of the UI that is causing someone to react to the event where on the contrary the first one is more data driven since the UI is generated by what is found in the composite structure.

I'm not sure what you mean by shape in here, and how that relates to being UI or data-driven, could you elaborate?

In such a scenario the only solution is to be able to batch request, the issue is that since you have no control on who is involved the only viable approach

That makes sense, I think.

Somewhat fragile IMO.

Feels a bit fragile indeed (although JS' single-threadedness probably helps). As long as everything is synchronous (except the requests themselves), you can probably capture every outgoing request from a given query handler, and use that to batch stuff.
I think my biggest concern ATM is how handle multi-level data, without compromising decoupling or introducing a lot of events/query-results-notifications that are very specific to a given initial query.
I'm gonna think about it a bit more :)

it's been a long time 😄 The work on ViewModel Composition continues and it's now tracked in a few different places:

ViewModel Composition series on my blog with man articles detailing all the aspects.
Talks on the subject demos:

Designing a UI for Microservices
All our Aggregates are Wrong

ServiceComposer an implementation of a ViewModel Composition API Gateway. Used in the aforementioned demos.

Take a look at articles about composing lists, I guess they'll answer your concerns @FreekPaans:

Into the darkness of ViewModels Lists Composition
The ViewModels Lists Composition Dance

I'm closing this PR, as the repo is meant to be frozen due to the fact that it's only meant to demo the concepts expressed in The secret of better UI composition blog post. Feel free to get in touch to further discuss by raising issues or by using the contact form on my blog.


sqrl_acorn (cle-215+) support

I successfully got a basic thing running with a single core, no FPU, and BBL this morning. Now I'm trying to make a maxed out version with 4 cores, an fpu, and running at 100MHz. I'll post dts and bitstream and other bins here when I get it all working.

Basic config for now since I'm struggling to get crossover uart working on --cpu-variant=full4d
acorn_cle_215.zip

Here's everything I have for the full4d, including a boot.bin and initramfs for debian, dts, busybox boot.bin, bitstream, and driver folders. https://nextcloud.paulsajna.com/index.php/s/qi4oDSyXdSPQPE2

closing, since sqrl acorn support was added with commit b9b92a5bf79334f100ad808df7827f1f326307c1


Why ml_create_dummy_variables does not omit reference variable in sparklyr

I need to omit the reference dummy to avoid multicollinearity. I understand I should put the reference argument. As an example, I have a variable called "cnae2" with 5 levels where level 4 should be the reference and therefore should not appear a vector called cnae2_4.
load("~/bf_fe.RData") #dataframe R
bf_fe$cnae2=factor(bf_fe$cnae)
levels(bf_fe$cnae2)=c("1","2","3","4","5")

bf <- copy_to(sc,bf_fe) #spark dataframe
z=select(bf,cnae2,esc)

x=ml_create_dummy_variables(z,"cnae2",reference="4")

x
Source:   query [2.821e+06 x 7]
Database: spark connection master=local[8] app=sparklyr local=TRUE

Source:   query [2.821e+06 x 7]
Database: spark connection master=local[8] app=sparklyr local=TRUE

   cnae2   esc cnae2_1 cnae2_2 cnae2_3 cnae2_4 cnae2_5
   <chr> <chr>   <dbl>   <dbl>   <dbl>   <dbl>   <dbl>
1      4     4       0       0       0       1       0
2      4     3       0       0       0       1       0
3      4     3       0       0       0       1       0
4      4     4       0       0       0       1       0
5      4     3       0       0       0       1       0
6      4     4       0       0       0       1       0
7      4     3       0       0       0       1       0
8      4     3       0       0       0       1       0
9      4     4       0       0       0       1       0
10     4     3       0       0       0       1       0
# ... with 2.821e+06 more rows

Thanks! This appears to be a bug -- sparklyr should indeed drop the reference column when explicitly specified. As a workaround for now, you might just explicitly drop that column, e.g.
x = select(x, -cnae2_4)

Thank for reply! For now I'll use it. But if I have many factor variables to turn into dummies? Does not this function allow put more than one vector? For example:
d=c("cnae","esc","uf","cbo")
x=ml_create_dummy_variables(z,d)

Right, the function currently only accepts a single column name. As an alternative, you could just call this function repeatedly for each column you want to split:
columns <- c("cnae","esc","uf","cbo")
for (column in columns)
  x <- ml_create_dummy_variables(x, column)

Hello, i apreciate your help.
I followed your tip. My problem is that I have an id_worker vector with total of 169,099 and id_firm with total of 7,245, plus other variables. After creating these dummies I have spark.data.frame of 1,860,089 rows by 176.407 columns. Without the use of sparklyr, the only way to get this dataframe was with  sparse matrix, however when estimation of a lasso with cv.glmnet the pc stopped, it gave memory allocation problem, so I chose to use Sparklyr.
My big question is in the process of generating dummies that take about 8 hours and when it ends I can't access almost anything, the memory is totally occupied by a java process. I would like to know if there is anything I can configure at the beginning, in connection with spark, to speed up the process and not take up too much memory.
Please apologize for the lack of use of technical terms, my knowledge about programming is very limited.
Thanks for any help.
rm(list=ls(all=TRUE))
gc()
load("~/bf_fe.RData")

library(sparklyr)

 config <- spark_config()
 config$`sparklyr.shell.driver-memory` <- "64G"
 config$`sparklyr.shell.executor-memory` <- "64G"
 config$`spark.yarn.executor.memoryOverhead` <- "64G"

  config$`spark.driver.cores` <- 8
  config$`spark.executor.cores` <- 8
  config$`spark.executor.instances` <- 8
  config$`sparklyr.cores.local`<- 32
  config$`spark.sql.shuffle.partitions.local`<-32

  sc <- spark_connect(master = "local[8]", config = config)
  bf <- copy_to(sc,bf_fe)
 columns<-c("id_firm","uf","esc","cbo","estrang","branco","id_worker")

   for (column in columns)
     bf <- ml_create_dummy_variables(bf, column)

bf_d = dplyr::select(bf, -c(uf_11,esc_1,cbo_1,estrang_0,branco_0,id_worker_1,id_firm_1))

I need do this:
#lasso regression
    #formula

z<-c(colnames(bf_d[,c(3:5,27:ncol(bf_d))]))
  z<-paste(z,collapse = "+")
  fz <- as.formula(paste("ln_w","~",z))

lasso=ml_linear_regression(bf_d, fz, intercept = TRUE, alpha = 1, lambda = 10)

But, i can't.   z    take long time.

@celina-oliv string indexing and one-hot encoding should be taken care of automatically when you call ml_linear_regression() if the column is a character (you may have to do something like mutate(bf_fe, cnae2 = as.character(cnae2)). The reference level is chosen by Spark (to be the most populated level) and there's no way to change it as of Spark 2.2.


[BEAM-11791] Fixing FnApiRunner Microbenchmarks to export to influxDB

Restructuring the file to copy job_LoadTests_Combine_Python.groovy
The reason influxdb export was not working is that we were not adding additionalPipelineOptions to the job options, and thus the export did not include the InfluxDB instance.
See sample run logs are missing influx_db_host:
00:00:27.176 [src] $ /home/jenkins/jenkins-slave/workspace/beam_Python_LoadTests_FnApiRunner_Microbenchmark/src/gradlew -PloadTest.mainClass=apache_beam.testing.load_tests.microbenchmarks_test -Prunner=DirectRunner -PwithDataflowWorkerJar=false "-PloadTest.args=--publish_to_big_query=true --influx_measurement=python_microbenchmarks --project=apache-beam-testing --metrics_dataset=load_test --metrics_table=python_direct_microbenchmarks --input_options='{}' --runner=DirectRunner" -PpythonVersion=3.7 --continue --max-****s=12 -Dorg.gradle.jvmargs=-Xms2g -Dorg.gradle.jvmargs=-Xmx4g -Pdocker-pull-licenses :sdks:python:apache_beam:testing:load_tests:run

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Seed Job

Run Seed Job

Run Seed Job

an instance of the job running with appropriate influxdb config: https://ci-beam.apache.org/job/beam_Python_LoadTests_FnApiRunner_Microbenchmark/33/console

First data point in grafana: http://metrics.beam.apache.org/d/1cnwVDkGk/fnapirunner-micro-benchmarks?orgId=1

r: @tysonjh


Image alt text missing from SDK

Hey! 👋
Image alt texts that are added in Notion are not parsed by the SDK. It looks like alt texts are a relatively new feature in Notion - are there plans to add support to the SDK?
I have a workaround where I use the caption field, but as I have other data in the caption it's quickly turning into a mess 😭
Thanks!

I hope it will be added too


我在vultr上买了云主机，系统ubuntu20.04 docker-compose方式部署，启动完访问提示invalid_api_key Incorrect API key provided: undefined.

Describe the bug
我在vultr上买了云主机，系统ubuntu20.04 docker-compose方式部署，启动完访问，并发送请求后提示
invalid_api_key Incorrect API key provided: undefined.
invalid_api_key
Incorrect API key provided: undefined. You can find your API key at https://platform.openai.com/account/api-keys.
Reproduction
1
System Info
invalid_api_key Incorrect API key provided: undefined.
invalid_api_key
Incorrect API key provided: undefined. You can find your API key at https://platform.openai.com/account/api-keys.

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

#297

Docker version 20.10.21, build 20.10.21-0ubuntu1~20.04.1 docker-compose version 1.25.0, build unknown

我在执行
docker-compose build .
输出错误：
ERROR: No such service: .
我就把 . 去掉了可以执行成功。不知道这句命令是否有影响。


[incubator/docker-registry] Use storageClassName for docker-registry.

Fixed docker-registry for #1869
/cc @prydonius

/lgtm


Update c-with-rust.md

Add the --use-core flag for folks using the bindgen binary

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @therealprof (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.


No 'Access-Control-Allow-Origin' header when uploading to Azure Blob Storage

I am receiving the following error when I call the Upload.upload angularjs call: Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://<IP_ADDRESS>:10000/devstoreaccount1/file.mp4?sv=version&sr=c&sig=signature&sp=w. (Reason: CORS header 'Access-Control-Allow-Origin' missing).  I am trying to upload a file to azure blob storage emulator to test the functionality before adding the code to the cloud instance.  What do I need to set on the storage emulator to properly test this functionality under azure?

You should ask this on Azure Blob Storage forum or StackOverflow.


chore: fix comment

Codecov Report
Base: 100.00% // Head: 99.50% // Decreases project coverage by -0.49% :warning:

Coverage data is based on head (87eb927) compared to base (bd8085a).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff             @@
##              main       #5      +/-   ##
===========================================
- Coverage   100.00%   99.50%   -0.50%
===========================================
  Files           38       38
  Lines         1601     1601
===========================================
- Hits          1601     1593       -8
- Misses           0        7       +7
- Partials         0        1       +1

Impacted Files
Coverage Δ

pkg/jose/jwk/jwk.go
100.00% <ø> (ø)

...d/authentication_request/authentication_request.go
100.00% <ø> (ø)

pkg/jose/jws/jws.go
100.00% <100.00%> (ø)

pkg/openid/pkce/pkce.go
100.00% <100.00%> (ø)

pkg/runtime/mstats.go
76.47% <0.00%> (-23.53%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


试了好几次现在根本就连不上了

2016/06/16 14:34:44 [ERR] yamux: keepalive failed: i/o deadline reached
2016/06/16 14:34:44 [ERR] yamux: Failed to read header: broken pipe
2016/06/16 14:34:44 stream closed

最好分别提供服务端、客户端的参数以及提示的信息

服务端 ./server_linux_386 -l ":29912" -t "<IP_ADDRESS>:8883" --key "123" -mtu 1400 -sndwnd 2048 -rcvwnd 2048 --mode "fast2" > log 2>&1 &
客户端  start /b client_windows_amd64.exe -l ":2000" -r "<IP_ADDRESS>:29912" --key "123" -mtu 1400 -sndwnd 2048 -rcvwnd 2048 --mode "fast2" > log 2>&1
服务端
2016/06/16 02:36:00 stream opened
2016/06/16 02:36:00 stream closed
2016/06/16 02:36:00 [ERR] yamux: keepalive failed: i/o deadline reached
2016/06/16 02:36:00 [ERR] yamux: Failed to read header: broken pipe
2016/06/16 02:36:00 keepalive timeout
2016/06/16 02:36:10 stream closed
2016/06/16 02:37:00 [ERR] yamux: keepalive failed: i/o deadline reached
2016/06/16 02:37:00 [ERR] yamux: Failed to read header: broken pipe
2016/06/16 02:37:00 keepalive timeout
2016/06/16 02:38:00 remote address: <IP_ADDRESS>:42691
2016/06/16 02:38:00 stream opened
2016/06/16 02:38:00 stream opened
2016/06/16 02:38:00 stream closed
2016/06/16 02:38:10 stream closed
2016/06/16 02:39:00 [ERR] yamux: keepalive failed: i/o deadline reached
2016/06/16 02:39:00 [ERR] yamux: Failed to read header: broken pipe
2016/06/16 02:39:00 keepalive timeout
客户端
2016/06/16 14:37:21 stream closed
2016/06/16 14:37:23 stream closed
2016/06/16 14:37:29 stream closed
2016/06/16 14:37:32 stream opened
2016/06/16 14:37:33 stream opened
2016/06/16 14:37:35 stream opened
2016/06/16 14:37:37 stream closed
2016/06/16 14:37:38 stream opened
2016/06/16 14:37:39 stream opened
2016/06/16 14:37:44 [ERR] yamux: keepalive failed: i/o deadline reached
2016/06/16 14:37:44 [ERR] yamux: Failed to read header: broken pipe
2016/06/16 14:37:44 stream closed
2016/06/16 14:37:44 stream closed
2016/06/16 14:37:44 stream closed
2016/06/16 14:37:44 stream closed
2016/06/16 14:37:44 stream closed
2016/06/16 14:37:44 session shutdown
2016/06/16 14:37:44 stream opened
2016/06/16 14:37:44 stream opened

我只能猜测，校园网对udp非常不友好， 你可以尝试把服务器端口换为8000/4000/53/554/443/80这几个端口试试，另外client的 -sndwnd 256就够了

都试过了 还是连不上 就刚开始配置好上了一会挺快的
服务端
2016/06/16 03:05:48 remote address: <IP_ADDRESS>:3015
2016/06/16 03:05:48 stream opened
2016/06/16 03:06:48 [ERR] yamux: keepalive failed: i/o deadline reached
2016/06/16 03:06:48 [ERR] yamux: Failed to read header: broken pipe
2016/06/16 03:06:48 keepalive timeout
2016/06/16 03:06:48 stream closed
看着像是udp 被封了

你先把 -sndwnd -rcvwnd 都降到128

和你的问题一样，换成SNMP Millstone Version就好了，6月15号的新版本好像有问题。

SNMP Millstone Version  在哪下载
换了机房 换了端口 还是不行 已累了

点开release 最底下那个

校验过md5么？ 是官方release么？

MD我智障了，忘了校验直接下了
不过的确是从你这下的

嗯，review了一下，确实发现了一个问题，这个问题和-conn参数有关

对了，xtaci大大，服务器和客户端的版本必须要一致么？

SNMP milestone之后的，都可以兼容， 等下提交新的release

包括SNMP milestone吧？

包括， 但还是建议两端都更新到最新版本。

嗯，谢谢你的程序，很好用。

还是依旧连上不，整了一天该干工作了  等等后面版本再说吧  很期待后面的版本好整  效果还是很好的

@voq 可以试一下我刚修正的0616版本

thank you all!

试了默认的端口29900,554,1755都用不了，近乎绝望时试了一下443豁然开朗。。。

good story


Document the default value for $NodeDeallocationOption

The default value for $NodeDeallocationOption is requeue; this can catch out users who expect the default to allow tasks to run to completion.

@theunrepentantgeek : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks for the PR, @theunrepentantgeek! I just submitted a PR internally that includes this change and a few others. Updated content should be live in 1-2 hours.
#please-close


PHP Artsan command not recognised as URI

Windows Terminal version
1.20.11381.0
Windows build number
Version 22H2 (OS Build 19045.4412)
Other Software
No response
Steps to reproduce

Navigate to a Laravel project
run php artisan serve
ctrl + click the link

Expected Behavior
A new window should load in the browser
Actual Behavior
A pop up notification is shown.

It seems to be including the the closing ] as part of the URL
Hovering over the link says
Invalid URI

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #17323 for more discussion.
/dup #17323


Twig Runtime Error (IE 11 and Edge 42)

Error Message: An exception has been thrown during the rendering of a template ("Template "modular/3-columns.txt.twig" is not defined."). The html.twig template with the same name is definitely there.
You can test this here:
https://www.aepfelundkonsorten.org/home
Site working in Chrome, FF and Edge 42. Not in Edge 41.16, IE 11.

I have the same Issue.
Start happening after upgrading to 1.6.0-rc2

So the issue seams to be related to modular pages. All my other Pages are working just fine.

My landingpage.md
`---
title: Landingpage
slug: /
content:
items<EMAIL_ADDRESS>order:
custom:
- _hero
- _featured
- _getstarted
- _products
- _news
---`
my templates:

I'm pretty sure my site worked before in IE11.
Since I have everything in git, i checkout at the pre-rc releases and the bug was also present. So forget about my comment above.

php -S localhost:8000 system/router.php   works just fine
maybe it's a htaccess problems? Any Ideas @rhukster  ?

It's something with your webserver configuration, it's not setting the php mimetype correctly when the page is requested, and it's falling back to text because it's looking for modular/featured_coherence.txt.twig when it should be looking for modular/featured_coherence.html.twig.
The fact that it works with built-in webserver means it's not related to your content, configuration, or Grav itself, it has to be the webserver.
We probably did 'fix' something in the newer versions of Grav to ensure the mimetype was honored properly, and this is now exposing a setup issue for you.

What you can try is to look at the request itself with the devtools.  It might shed some light on the matter.

Also you might want to look at content negotiation in your apache config: https://httpd.apache.org/docs/2.4/content-negotiation.html

Ok, i was able to replicate this on my windows machine!  I will investigate it!

Ok, it did it one time, but after a refresh, it works every time.  Grr.. very tricky to track this down if i can't reliably replicate it.

Same here, we tested on a bunch machines now. Still got the error
What IE11 Version are you using @rhukster
you can check my test site
http://gidrm.tbodev.de/en  (this is the landingpage with 3 modular elements)

Found it! ok, not sure how this happens, but the order of the page types must be wrong.  I had txt first, and it should be html.  If you edit your user/config/system.yaml file... look for system.pages.types and change that array to:
  types:
    - html
    - htm
    - xml
    - txt
    - json
    - rss
    - atom

This fixed it for me.

maybe thats why Utils::getExtensionByMime($mimetype); always returned text/plain
and because I have different configs for stage/test/prod  the extension order was different on each server and i couldn't figure out why it was working on stage.

Fixed! Thank you so much!

Did also fix it for me! Thanks guys for looking into it again.

@rhukster Didn't you fix this already?

seems not, i need to update the defaults in system.yaml

Now done..

The re-ordering of the page types helped me also on Google index, since I got 5xx error every time I tried to reindex the page

This fix is now in 1.6 release.

sorry for reopening, but there might be a new side effect (mainly for custom themes):
when missing favicon image file, grav points favicon tag to web root
<link rel="icon" type="image/png" href="/" />
which makes browser request start page with Accept: image/webp,image/apng,image/* header.
And this request makes modular pages being rendered with .txt.twig insterad of .html.twig templates.
This happens in all browsers and changing the order of page types does not help.
Since faulty href and src tags, causing browser to load website once again, are pretty common problem, probably grav should stick to first/default page type here instead of forcing txt?
It was kind of misleading In my case, since grav tried to render txt.twig template instead of just loading exactly the same page once again.

@vanilla-thunder Could you please create a new issue on this? Also, could you provide a minimal example of what to install to reproduce this issue, it would save some time if some themes work and some not.


Allow Reading Secrets from Files

As discussed in #2498 , it would be nice to be able to read secrets from files. It's a rainy day here, so in this PR we introduce that support for all secrets in the global and individual notifier configs, based on the existing support for this in the SlackAPIKeyFile config var.
On a sort of personal node: This is useful for any alertmanager deployed in K8s as you can now use Kubernetes Secrets to manage individual config components rather than the whole config file
Comments/Criticism welcome - It's been a really interesting traipse around the codebase

Note that I mimicked the Slack precedent for this that loads the secret at notify time - in high turn over alertmanager instances this feels like overkill for a value that might never change. We should probably make this load the secrets at config unmarshal time and handle reloads nicely

The values should be read from file every time they are used. I wonder if we really need to have all this custom code or if we can pass http client credentials to achieve a lot of them.
I will have a look, but it will take a long time. What about we split this pull request per receiver? Maybe start with one to see if we have the right approach?

Happy to close this and reopen with just one notifier. Probably Pagerduty because that's the one I care about the most. It seems that most every provider handles Auth differently, so as much as we can hope for a unified solution I don't think it's going to be that easy (as much as I would love to add a bearer token and call this done)


Convert kernel ROM chiplet into a lookup table

The current kernel ROM chiplet was designed with the assumption that it would be proved using a running product column (i.e. a "vanilla multiset check"). Specifically, if a program makes 10 syscalls to the same kernel procedure, we will add 10 entries to the kernel ROM (with the same addr).
After we've switched to LogUp-GKR, we could make this a simple lookup table, where the s0 and addr columns are converted to a single multiplicity column.
The "kernel lookup table" would have 5 columns:
| multiplicity | root0 | root1 | root2 | root3 |

Each kernel procedure (whether it's called or not) would be added exactly once to the table, with multiplicity = 0 for all kernel procedures that were not called during a program so that the kernel virtual table can account for them.

I think this approach would work for regular LogUp as well.


Fixed bug in getting column names for metadata & edited limitation document

Summary
Fixed bug in getting column names for metadata & edited limitation document
Description
Getting column names from a specific table in MetadataCache.java was using a string contains logic, which for a table name (e.g. table "ABC") it would grab the columns in all table that contains the given name (e.g., tables "ABC", "ABC1", and "ABC2"). This is problematic when a column not in the desired table is grabbed, which may lead to Error parsing with a CalciteContextException: Column 'y' not found in table 'x' in BI tools that rely on the received column names to generate queries. Now changed to an equality check with equals.
Added Custom SQL in Tableau to SQL driver limitations.
Related Issue
Likely related to the bug reported in #148.
Additional Reviewers
@birschick-bq
@lyndonb-bq
@xiazcy
@simonz-bq
@alexey-temnikov
@kylepbit

I would prefer this to be split into 2 PRs - one updating the license headers and the other fixing the bug. As is, you cannot determine the noise (license header update) from the function (bug fix). Too many files are changed.

Makes sense, I will open another PR with the license header, and rebase this one after. Thanks Kyle!

There should be a unit test demonstrating this fix.

Thanks for adding the test Yang. Looks good.


operator: Fix use of Resource.Events() in CEC controller

The commit "resource: Refactor the API for simplified usage" was tested against older master, before the commit "cli: Add configuration flag for service LB" which used the older API, causing the build to fail.
This updates StartCECController() to use the new Resource.Events method.
Fixes: f3a9b0ac7181 ("resource: Refactor the API for simplified usage")

Relevant tests pass showing that the build is fixed (conformance, image builds, go lint), merging.


Improve IMAGE SLIDER

Improve the image slider.
Take help from these sources:

https://codepen.io/panfilov/full/GogJVy/
https://codepen.io/MergimUjkani/full/awONge/
https://codepen.io/tylernj42/full/LEKedz/
https://codepen.io/mrspok407/full/bwLwvL/
https://codepen.io/suez/full/WvaKpy/
https://codepen.io/alexnoz/full/brazWd/
https://codepen.io/digistate/full/aEqzBB/
https://codepen.io/johnblazek/full/nxgVPR/

Take inspiration from these sliders and try to implement them

Done bro


New version: Alibaba.AlibabaCloudCLI version 3.0.223

Created by 🥟 Dumplings in workflow run #8223.

Log
Updated: 3.0.222 → 3.0.223
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -1978335187
2024-09-21 06:00:08.762 [FAIL] Installer failed security check. Url: https://github.com/aliyun/aliyun-cli/releases/download/v3.0.223/aliyun-cli-windows-3.0.223-amd64.zip Result: 0x80004005

Automated error analysis suggests -1978335187 may mean Installer failed security check. Another script should retry this every 18 hours.
Automated error analysis suggests 80004005 may mean Resource missing
(Automated response - build 896.)


Does it support specifying branches/commit hashes?

Yup, I see that it does!

For example, https://minhaskamal.github.io/DownGit/#/home?url=https:%2F%2Fgithub.com%2Fmightyiam%2Fcyclejs%2Ftree%2Ff585ec0da005cbf51c7cb0350cd23c5cf943c0b1%2Fhttp


JSONDecodeError on running dolly repo with review dataset.

Hi,
Started running dolly repo in my workspace repo, i prepared a custom dataset with classification task of 6k records. When i am running the deepspeed code in repo, i am ending up with json decoder error and this error is repeating when i am using another dataset also on the same line mentioned in below output.
Output of deepspeed code:

deepspeed code:

deepspeed config:
{
"bf16": {
"enabled": "auto"
},
"optimizer": {
"type": "AdamW",
"params": {
"lr": "auto",
"betas": "auto",
"eps": "auto",
"weight_decay": "auto"
}
},
"scheduler": {
"type": "WarmupLR",
"params": {
"warmup_min_lr": "auto",
"warmup_max_lr": "auto",
"warmup_num_steps": "auto"
}
},
"zero_optimization": {
"stage": 2,
"offload_optimizer": {
         "device": "cpu",
         "pin_memory": true
      },
"overlap_comm": true,
"contiguous_gradients": true,
"sub_group_size": 1e9,
"reduce_bucket_size": "auto",
"stage3_prefetch_bucket_size": "auto",
"stage3_param_persistence_threshold": "auto",
"stage3_max_live_parameters": 1e9,
"stage3_max_reuse_distance": 1e9,
"stage3_gather_16bit_weights_on_model_save": true
},
"gradient_accumulation_steps": "auto",
"gradient_clipping": "auto",
"steps_per_print": 2000,
"train_batch_size": "auto",
"train_micro_batch_size_per_gpu": "auto",
"wall_clock_breakdown": false
}
Databricks Cluster configurations:
12.2 LTS ML runtime.
Standard_NC8as_T4_v3 - 56 GB memory 1 GPU.
Issue:
I am facing the problem when running deepspeed code, it is throwing json decoder error on line 25 for another data also.
please let me know what is my issue and how can figure it out.
Thank you in advance.

It pretty much tells you the error. You have a syntax error in your deepspeed JSON config. I don't immediately see a problem there, but double check your actual config file is valid around that line.

Thank you @srowen it worked for me.


Adjust support policies

As a developer integrating Pillarbox and Letterbox I want to clearly understand the respective support policies so that I can better plan migration from Letterbox to Pillarbox.
Acceptance criteria

The support policies are documented for all platforms.

Tasks

[x] The support policy for Apple platforms is documented.
[x] The support policy for the Android platform is documented.
[ ] The support policy for the web is documented.

The Apple policy has been updated to account for recent decisions.

The web policy has been updated as well.


Make Nanosecond represent time < 1 Millisecond

I think that this should close #9, in that doing this means that we don't need smart constructors.

@natefaubion I think this mitigates the need for a smart constructor, doesn't it?

Oh yes, if Nanos is only sub millis, then we don't need a smart constructor.

@natefaubion do you think this also addresses https://github.com/awakesecurity/purescript-precise-datetime/issues/8?

@natefaubion we might still want a smart constructor to enforce that invariant

@themattchan I think that's already enforced by the changes in this PR.

@paulyoung It seems like it would address #8 by truncation, yes.


fix: saving stable diffusion model error in dreambooth training

Description
Downgrade pytorch version from 2.0.1 to 2.0.0. Fix saving stable diffusion model error in dreambooth training.
Add debug log in sagemaker training image.
PS: training with default mixed precision setting (no) will fail in g5 instance, because of the cuda library version.
Fixes # (issue)
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

please raise to dev branch and pass the check (viperlight), close for now


No answer from to microsoft server

Hi,
Is there any changes on Microsoft Server lately ?
I receive messages, send message back but nothing appear on WebChat console

tested on one of my new bot
someone on my team test it too on an other server with an other bot instance

21 Feb 20:11:08 - [info] Message outgoing:{"type":"message","agent":"botbuilder","text":"Hello World","address":{"id":"KIaS4EHveqw|0000002","channelId":"webchat","user":{"id":"G72qvjbhNze","name":"You"},"conversation":{"id":"KIaS4EHveqw"},"bot":{"id":"ViseoD5@jrBg3gPsI98","name":"VISEO Demo 5"},"serviceUrl":"https://webchat.botframework.com/","useAuth":true},"source":"webchat"}

This log has been generated using bot.on('send', ...)
Thanks

Fixed on one of my server, config file error.


Missing icons at stable branch

Steps to Reproduce
Copy and paste the sample minimal code to  https://dartpad.dev/ (or your favorite IDE,with flutter stable branch)
Actual results:
A sword icon is shown. Or nothing. But not Apple's icon.

Code sample

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const ShowAppleIconScreen(),
    );
  }
}

class ShowAppleIconScreen extends StatefulWidget {
  static String routeName = '/birthday_onboarding';

  const ShowAppleIconScreen({Key? key}) : super(key: key);

  @override
  _ShowAppleIconScreenState createState() =>
      _ShowAppleIconScreenState();
}

class _ShowAppleIconScreenState extends State<ShowAppleIconScreen> {

  @override
  Widget build(BuildContext context) {

    return SafeArea(
      child: Scaffold(
        body: Icon(Icons.apple)
      ),
    );
  }
}

Logs
The output is clearly irrelevant as the issue can be reproduced at dartpad.

Additional details:
This issue also manifests itself as "Codepoint 983768 not found in font, aborting." for many different codepoints when trying to build the app via flutter build apk, at the stable branch.
In master for some reason it does work (but then there are other,more serious, issues).
Need to remove unsupported codepoints, or clarify what's going on at documentation or here.
Previous issues (for example #64334) concluded in a "switch to a different branch" or "--no-tree-shake-icons" patchy/hacky "solutions".

Duplicate of #97767


Issue 1037

#1037 Simple fix to make it possible to instantiate an empty connection pool. For cases where you still want the webapp to load, e.g. you want a service to be able to start and show an error page when a DB isn't available.
Includes tests. Please ignore the changes to travis.yml

Coverage remained the same at 80.9% when pulling 8f7eb5820fcb0d7a47aa4e6118641a9ff238576d on arienkock:issue-1037 into f0a23767f5b02e3806c52e4a0eae58415ea465e2 on dropwizard:master.

In case it was lost in the exchange: the travis config on my branch was reverted as suggested.

This looks good. There are a few suggestions in the code review that should be applied.
Do you also have a link to documentation on this behavior for tomcat's jdbc pool for future reference?

Sure. From the Javadoc of the ConnectionPool constructor: Instantiate a connection pool. This will create connections if initialSize is larger than 0.
Just pushed changes w.r.t. code review.

Coverage increased (+0.02%) to 80.923% when pulling b001e2594a0579e992621533bf3182ddb7e18bac on arienkock:issue-1037 into f0a23767f5b02e3806c52e4a0eae58415ea465e2 on dropwizard:master.

Did you miss one of the code review items?

In the last commit I removed the try catch and code comment before the unit test.

And just so I understand clearly, those that are using Dropwizard and JDBI -- the DBIHealthCheck, which needs a connection to the database, will fail, and this is the desired result. The application will still start, but will essentially be in an unhealthy state.

Correct, the argument being that if the app can run without a DB (and be in an unhealthy state) why would it not be able to start. Useful in cases where you know a DB connection is of bad quality and you don't want a deployment to fail.

I just removed the other try-catch from the unit test

Coverage increased (+0.02%) to 80.923% when pulling 5313d4c6a0f298a45a852c025467f9b2c81948e1 on arienkock:issue-1037 into f0a23767f5b02e3806c52e4a0eae58415ea465e2 on dropwizard:master.


add stSTARS gauge for STRD externals

May be worth remaking this branch from master. It's very out of date @JohnnyWyles

My bad, thought I'd done a fresh copy.  I'll re-download and make the changes, probably easier that way.


Restricted user names

For security. Stuff that could be room for social engineering abuse, collision, or confusion. E.g., prohibit stuff like:

admin
administrator
info
information
twelvecash
account
etc.

Here is a first list of possible usernames that are not allowed:
Administrative/User Roles:

admin
administrator
root
sysadmin
superuser
operator
support
helpdesk
webmaster
mod
moderator
manager
boss
owner

Company/Service Names:

twelve
twelvecash
twelvecashsupport
twelvecashhelp
twelvecashadmin
company
service
official
supporttwelve
twelvecustomer
twelvestaff

Contact Information:

info
information
contact
support
help
billing
sales
inquiries
no-reply
noreply

Security/Authority:

adminuser
master
security
secure
policy
terms
privacy
compliance
legal
law
police
officer

System/Default Names:

system
guest
anonymous
unknown
default
test
user
public
undefined
rootuser
testuser

Phishing-Related Names:

login
signin
signup
forgotpassword
resetpassword
recover
verification
confirm
authenticate

Social Media Handles:

facebook
twitter
instagram
linkedin
snapchat
youtube
tiktok
social
media

@paulosacramento I agree this seems like a pretty comprehensive list. This seem like a good place to start, then we can add more names in the future if needed.

For @chdwlch, myself, or any other coder who wants to take this issue, here is a sketch of how I see this working:

Create and export a const prohibitedNames:string[] = ["admin", "administrator", etc...] containing Paulo's list of names.
In any API endpoint that handles name creation or checking if a name available to claim/buy, import prohibitedNames
Validate that the user's desired strong is not contained inside of prohibitedNames


[Event Request] Codeunit 90 Purch.-Post - OnAfterDeleteApprovalEntries

Hi, would it be possible to get an event OnAfterDeleteApprovalEntries in Codeunit 90 Purch.-Post in procedure FinalizePosting, like this :

OnAfterDeleteApprovalEntries(PurchHeader,IsHandled);
    [IntegrationEvent(false, false)]
    local procedure OnAfterDeleteApprovalEntries(var PurchaseHeader: Record "Purchase Header"; var IsHandled : Boolean )
    begin
    end;

?
Thanks

You can use existing event OnBeforeDeleteAfterPosting()

You can use existing event OnBeforeDeleteAfterPosting()


Reconnection problem

Reported by @madmalkav here
Working for me on EndeavourOS (Archlinux derivative). I see the speaker icon on my Plasma taskbar but I don't seem to have any volume control; the output goes to the remote computer OK. If I disconnect and connect again, the sound stops working and the speaker icon in the taskbar appears crossed by a red line.

I can reproduce this on Ubuntu 22.10 now.


Limit workers to max partitions

If there's only 3 partitions to process, don't create 24 workers. Will come up with incremental exports.

Implemented


Feature/subscription pretty name

What do you think of this idea?
Lindsey was asking about a "lookup table" for counties and categories so that the subscription list page was more useful to her and I thought something like this might be a better approach. I'm not super attached to it, so feel free to disagree.


Can't to import Google/SignIn into bridge file

Hi,
I have faced with an issue that when I try to make
#import <Google/SignIn.h>

and can't to figure out how to resolve it.
I have installed it via cocoa pods
pod 'Google/SignIn'

Are you opening the the xcworkspace file, and does the Google pod appear in the pods project?

Update pod in Google SignIn folder and try again. If problem repeat try clean project "Product -> Clean".

It was automatically fixed after I had update my cocoa pods (gem install cocoapods)


Combinatorial skip feature

It could be useful for e.g. #423 to slice the combinatorial prompt space with a start and stop offset.
Originally posted by @akx in https://github.com/adieyal/sd-dynamic-prompts/issues/423#issuecomment-1596135147

+1


SSR CSP global nonce is not per-request

(Apologies for deleting the issue template, but I couldn't make this issue fit very well into the template)
#1022 (and #1043) introduced using global.__webpack_nonce__ to configure nonces for <style> tags when doing SSR:
https://github.com/styled-components/styled-components/blob/34d18292e6cc97b508b7adb572f1d357232bccd5/src/utils/nonce.js#L6-L7
But nonces should be randomly generated per-request, and using a global variable opens the possibility of nonces leaking between requests, if global.__webpack_nonce__ is set again before the current request finishes:

request A generates nonce Na
global.__webpack_nonce__ is set to Na
React starts rendering response for A
request B generates nonce Nb
global.__webpack_nonce__ is set to Nb
A rendering starts using Nb for nonce instead of Na

I don't know enough of the details about whether styled-components can be interrupted by another request (apparently React's renderToString is synchronous, but renderToNodeStream may be asynchronous?) but perhaps one way to avoid this would be to accept the nonce as a parameter on one of ServerStyleSheet, collectStyles or getStyleTags.

This can be worked around on SSR by adding the nonce to the React elements by hand:
sheet.getStyleElement().map(e => React.cloneElement(e, { nonce }));

(But then I run into separate problems with Next.js's nonce handling, which make it hard to trouble-shoot Styled-components...)

Yeah webpack nonces are not set up to be generated dynamically, sorry. It’s
a flaw in the bundler setup. s-c just implements a solution against the
current setup.
On Tue, Jun 12, 2018 at 9:55 PM Bodhi<EMAIL_ADDRESS>wrote:

(Apologies for deleting the issue template, but I couldn't make this issue
fit very well into the template)
#1022 https://github.com/styled-components/styled-components/pull/1022
(and #1043
https://github.com/styled-components/styled-components/pull/1043)
introduced using global.webpack_nonce to configure nonces for

same problem.

I think it'd make sense for ServerStyleSheet to accept a unique nonce prop to avoid the nonce leaking between streaming requests. I'm not sure how webpack handles that case though, how do they have unique nonces then?

I passed __webpack_nonce__ to the client, but it does not hook on the styled-components side.
<script
  dangerouslySetInnerHTML={{
    __html: `__webpack_nonce__ = '${nonce}';`,
  }}
  nonce={nonce}
/>

Is something wrong?
If __webpack_nonce__ is global.__ webpack_nonce__ or window.__ webpack_nonce__, styled-components can hook the client's nonce.

I want to generate a nonce on the server side, not from webpack's DefinePlugin.

global.__webpack_nonce__ needs to be set in the server.

sorry, i can not tell you well.
https://github.com/styled-components/styled-components/blob/0aa3170c255a49cd41c3fbeb2b8051b5d132f229/src/utils/nonce.js#L6
On the client __webpack_nonce__ becomes undefined.
How can I pass a value to __webpack_nonce__ in the above file?
I think that __webpack_nonce__ should be window.__ webpack_nonce__ or global.__ webpack_nonce__.

// server/index.js
import express from 'express';
import { ServerStyleSheet } from 'styled-components';

app.use('*', (req, res, next) => {
  global.__webpack_nonce__ = uuid();
  // ...
  const styleSheet = new ServerStyleSheet();
  // ...
  const html = ReactDOMServer.renderToString(styleSheet.collectStyles(<App />));
  // ...
});

Closing due to age, inactivity, missing reproduction, or lack of details.


Add Million Token (wormholebridge v2)

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address: https://explorer.solana.com/address/2PoF4gqWg97yjJk276yUYaGVkkASE7tqAU7H5faEBkeC
Token Name: Million
Token Symbol: MM
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>) https://raw.githubusercontent.com/solana-labs/token-list/main/assets/mainnet/2PoF4gqWg97yjJk276yUYaGVkkASE7tqAU7H5faEBkeC/logo.svg
Link to the official homepage of token: http://milliontoken.org/
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_): https://www.coingecko.com/en/coins/million

We will have to do something to differentiate v1 and v2, otherwise we won't be able to know which token is being traded in Raydium, they don't show the address there, just the ticker and logo. It will look like this:

One option would be to remove the v1 token from the token list, we would just see the address for v1, and then encourage v2 migration.

Removed v1, in favor of v2.

@techleadhd , The website shows the V2 address on "View Contract (Solana)", but at the bottom of the page, in the Solana logo, it still points to the V1 address. They say it can take up to 2 weeks for it to be merged, but it's 23 days already.

Resolved


Make st2-self-check aware of missing modules

SUMMARY
The self-test script tries to run mistral tests despite mistral not being setup / installed.
ISSUE TYPE

Bug Report

STACKSTORM VERSION
$ st2 --version
st2 2.8.1, on Python 2.7.5

without mistral workflow engine
OS / ENVIRONMENT / INSTALL METHOD
Up to date centos 7
$ cat /etc/redhat-release
CentOS Linux release 7.5.1804 (Core)

STEPS TO REPRODUCE
sudo st2-self-check

EXPECTED RESULTS
Not running (and failing) mistral-related tests
ACTUAL RESULTS
[...]
Attempting Test tests.test_inquiry_mistral... ERROR!
Attempting Example examples.mistral_examples... ERROR!
Attempting Example examples.orchestra-examples... ERROR!

[...]
I think the orchestra thing is a similar issue...

I am -1 on automatically bypassing checks if Mistral is not installed. If the user does not have Mistral installed, it is misleading to get a successful result from st2-self-check, since their system is not set up correctly.
I think it would be better to off CLI options for bypassing Mistral and/or Orquesta checks. Those checks are a separate section in the code, so it should be easy to add a way to bypass that section.
Want to start a PR?

This commit https://github.com/StackStorm/st2/commit/667b301f93c0480679f978b2a5ea72fc8f778eb5 provides CLI flags for skipping Orquesta and/or Mistral tests.
I'm not happy with the way it works though. The default is to skip Windows, but to run Orquesta & Mistral workflows (since that is the current default). Sort of feels like the CLI flag names are wrong. Thoughts on a nicer way to do this? Or just not worry much about it?

I'd do all such flags in the same way, either as skip-something or do-something. Whichever you prefer, but keep a consistent UI.

The problem is that I don’t want to change the current behavior. The default should be to run the Orquesta and Mistral tests, but not to run Windows tests


Add PWA functionality

Make the game a real PWA (add manifest+sw). Probably this one goes together with adding real build chains etc.

I would like to ask some questions about this issue, just to make sure that I understand it correctly:

Adding a SW shouldn't be too much of a problem, but what features of the PWA do we want to implement? A2HS seems to be useful, but e.g. "offline mode" or "advanced caching" is not, is it?
Should we implement workbox, or just a plain SW?
We would need some icons that can be referenced in the manifest file. Any preferences for the icon(s)? The sprite of the spaceship looks like a good candidate? Can we use that?

Just now seeing that you assigned this - sorry for missing it. I added a very basic default sw - not autogenerated, not optimized, but gives green PWA score in Lighthouse. Feel free to work from there or replace as needed!

Closing for now, as PWA basics work somewhat well so far.


How to make the length and width of the window fixed ？

Flutter version

Flutter 1.2.1 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 8661d8aecd (10 weeks ago) • 2019-02-14 19:19:53 -0800
Engine • revision 3757390fa4
Tools • Dart 2.1.2 (build 2.1.2-dev.0.0 0a7dcf17eb)

I want to know how to set the length and width fixed.  It seems flutter have no such api. (；′⌒`)

For this and similar requests read: GLFW Plugin example

After consideration, @Drakirus and I have decided to indeed implement this feature in the go-flutter package as Option. PR comming soon :tm:

Please add min width and min height bound only .Not bound for Max height and width in flutter.WindowInitialDimensions() function. Which must be optional parameter for minium bounded height and width.

Glfw uses 4 parameters in SetSizeLimits https://www.glfw.org/docs/latest/group__window.html#gac314fa6cec7d2d307be9963e2709cc90
Use glfw.DontCare as the glfw says


[Request for External] page 232 "Apply Customer Entries" - Protected variables

Hello, we need the following currently global variable/-s to be set as protected. Can you please check this? Thank you!
protected var
   CustEntryApplID: Code[50];

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 42571.


API: user login doesn't support cart merge doesn't work

It does work if I use laravel portal but not as API call
Event::fire('customer.after.login', $request->input('email'));

@accountmine Please use the given format. And provide necessary proofs.

@prashant-webkul updated

Hi @accountmine
Issue has been fixed, you pull from master or wait for release.

Framework version v 0.1.8
issue fixed


Transfer URIs instead of platform-dependent file paths

Partially fixes https://github.com/flutter/flutter/issues/8502, but the calls in vmservice.dart still only take file paths instead of URIs.
/cc @johnmccutchan

LGTM


Updated libary to work with the Heroku Cedar stack. Fixes #2

I looked into it myself.  Only a few lines had to be changed.  Tell me what you think.

Any reason this hasn't been looked at?

This update works for me on the Cedar stack. It would be great if this could be merged in. Maybe for backwards compatibility, there could be another configuration option to set the stack name?

Actually are you sure it works?  I tried using @ekosz's branch recently, and it worked for a moment and then wouldn't process another job all of the sudden.  I ended up coding something based on some blog posts I found myself (it isn't a lot of code anyways).

Sorry, the Heroku gem has changed a lot since I created this pull and I haven't worked on it since.  I can take another look if people are interested.

@lucisferre Yeah, it worked several times for me with no problems. However, I didn't try it with multiple workers.
@ekosz Let me know if you need any help with any testing or development if you look at it some more.

I have one worker but multiple jobs. I didn't spend a ton of time debugging into it. It is a hard thing to debug too.

Any news about this?


Improve indexed access lookups and handling of getters/setters/methods in mapped types

Codecov Report

Merging #425 (9cb0bc8) into main (32517cb) will increase coverage by 0.06%.
The diff coverage is 60.93%.

@@            Coverage Diff             @@
##             main     #425      +/-   ##
==========================================
+ Coverage   79.72%   79.78%   +0.06%
==========================================
  Files          58       58
  Lines       19536    19664     +128
==========================================
+ Hits        15575    15689     +114
- Misses       3961     3975      +14

Impacted Files
Coverage Δ

crates/crochet_infer/src/expand_type.rs
61.75% <53.96%> (+1.94%)
:arrow_up:

crates/crochet_dts/tests/integration_test.rs
90.35% <67.92%> (+0.93%)
:arrow_up:

crates/crochet_infer/src/infer_class.rs
78.09% <100.00%> (+0.64%)
:arrow_up:

crates/crochet_infer/src/lib.rs
86.24% <100.00%> (ø)

crates/crochet_parser/src/lib.rs
76.32% <0.00%> (-0.05%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Resolve code generation command pathway

We need to decide whether we should have go generate comment directives per package or per repository. Also, we may want to add a gsm generate command that allows you to effectively generate code for multiple packages/repositories at once.

We will continue to have go:generate core generate comment directives per package, as that is good practice and ensures that core generate integrates well with the other generate commands we use. Also, gsm generate is no longer needed with our new monorepo approach; you can just run go generate ./... in the the root of the repository.


Provide ability to install with upstream container images

Added quickstart script to automatically build and run upstream. This needs to be merged after #32

Testing
[csibbitt@laptop deploy (qsupstream) ]$ oc delete project sa-telemetry
[csibbitt@laptop deploy (qsupstream) ]$ ./quicktest_upstream.sh
[...]
NAME                                      READY     STATUS    RESTARTS   AGE
alertmanager-sa-0                         2/2       Running   0          1m
prometheus-operator-1-kk4gn               1/1       Running   0          1m
prometheus-white-0                        3/3       Running   1          1m
qdr-operator-7c785c455d-pbk6h             1/1       Running   0          1m
qdr-white-6fb67d46d6-czqnr                1/1       Running   0          1m
smart-gateway-operator-5c96899578-dxptk   1/1       Running   0          1m
white-smartgateway-1-bn5jd                1/1       Running   0          1m

No other functional testing (I'm working on figuring out a lightweight way to smoke test SAF, hopefully coming "soon")

OK everything has been updated to something resembling sanity in the import-upstream.sh script. I've also ran the SmokeTest which worked successfully with these new images!

 Implement import-upstream.sh script for telemetry-framework


lint: fix golangci-lint

@NagaTulasi can you target main branch and then upstream it onto v2.x

@NagaTulasi can you target main branch and then upstream it onto v2.x

@anilcse I've updated the changes to main, can you review and merge this PR so I can raise a backport PR for releases/v2.x branch.


docker: switch to planetscale wolfi images

closes #23

hrmm... not sure why ci workflow did not run. Need that to run to verify we can pull the image


A simple Completer for MinestomTerminal & Fix LineReader visual issue

Need testing & reviewing before merging

I've created a custom Writer to fix an issue with LineReader being overridden when other threads log messages.
https://user-images.githubusercontent.com/25300232/169654680-a051075e-ff62-4c22-9c48-824b5301080d.mp4
Should be enough to review and then merge @TheMode


Index.Attribute throws error for sortable fields

NRedisStack Version: 0.12.0
Redis Stack Version:

Description:
For sorted attributes , index.Attributes throws  request.System.IndexOutOfRangeException: Index was outside the bounds of the array.

This is how i add text field:
schema.AddTextField(item.Key, sortable: true);
This is how index is created
var ftCreateParams = new FTCreateParams().On(IndexDataType.HASH)
.Temporary(expiryTime)
.Prefix(payloadPrefix);
note that , almost all of the fields are marked as sortable
This issue does not happen when i mark the fields false for sortable.
Please help !

Hi @ivanjt-srai , I'm on it 👍

@ivanjt-srai this PR should solve it, LMK what you think.

sure @shacharPash , when can I expect the fix to be available to use?

@ivanjt-srai In the next few days we will merge it to master

do we have any update on this @shacharPash ?

do we have any update on this @shacharPash ?

@atakavci

@ivanjt-srai The fix has been merged into the main branch.


Remove error handler calls from hoofs

Pre-Review Checklist for the PR Author

[x] Code follows the coding style of CONTRIBUTING.md
[x] Tests follow the best practice for testing
[x] Changelog updated in the unreleased section including API breaking changes
[x] Branch follows the naming format (iox-#123-this-is-a-branch)
[x] Commits messages are according to this guideline

[x] Commit messages have the issue ID (iox-#123 commit text)
[x] Commit messages are signed (git commit -s)
[x] Commit author matches Eclipse Contributor Agreement (and ECA is signed)

[x] Update the PR title

Follow the same conventions as for commit messages
Link to the relevant issue

[x] Relevant issues are linked
[x] Add sensible notes for the reviewer
[ ] All checks have passed (except task-list-completed)
[x] Assign PR to reviewer

Notes for Reviewer

Templatize ErrorHandler to prepare usage in different modules (see #1028 )
Remove all errorHandler() calls from hoofs as described in the error handling document

Checklist for the PR Reviewer

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code according to our coding style and naming conventions
[ ] Unit tests have been written for new behavior

[ ] Each unit test case has a unique UUID

[ ] Public API changes are documented via doxygen
[ ] Copyright owner are updated in the changed files
[ ] PR title describes the changes

Post-review Checklist for the PR Author

[ ] All open points are addressed and tracked via issues

References

Closes #590

From a quick view I think the approach is fine and in the scope well-defined. It is important that the error handling semantics will not be changed for now, only the syntax and organization of the code.
I.e. we check for the same conditions as before and react in the same way, just use different code. In other words there is no regression and also no new handling introduced.
This is a first step to allow individual error-handling for different modules. Changes of the overall concept should indeed be postponed and require more discussion. We will not have any overall concept change in iceoryx 2.0.
NB: this is just a first impression, I will have a closer look tomorrow.

@elfenpiff

Can we please keep this PR on hold until we figured out how the overall error concept in iceoryx looks like. To call terminate is most likely not an option for ASIL D and we may have to make this either configurable or that some user can define custom callbacks to notify maybe some kind of watchdog or even throw an exception.
In those cases an error handler may is the more viable solution.

Thanks for the remark, got your point. As we're not 100% sure how the final concept will look like, I would suggest to take an iterative approach here. My proposal is to get step by step to the full blown concept. Two goals are reached in #1027 and #1028:

Cleaner architecture: hoofs is independent from both posh and C binding
We are able to detect based on the enum type which module reported the error

As @MatthiasKillat pointed out, there is no semantic change. A next step towards the final design could be adding hooks to report and persistently save all errors from any module. This would enable reading them e.g. via UDS (both in Expects/Ensures and errorHandler).

@elfenpiff @MatthiasKillat @mossmaurice
I also don't think this should be kept on hold. Like already said, it is a small iterative step and does not change the concept by much. I wouldn't call the cxx::Expects in the error handler though but the other way around. The cxx::Expects should call the errror handler. At one point we have to delegate the error code to a 3rd party and cxx::Expects cannot do this since the error value is already erased. So after some thinking about this, I would keep the calls to the error handler in hoofs but create separate enums for each component. The cxx::Expects should also have an entry in this enum, e.g. EXPECTS_CONDITION_FAILED.
I felt asleep on the keyboard and when I woke up I had a PoC of a refactored logger on my laptop. @elfenpiff told me that it also happens to him at times. Might be a virus and seems contagious.
I think the same concept could be used to make the error handler more ergonomic and provide a hook for a 3rd party framework. I'll create a design document draft for the logger refactoring and then we can discuss if this would also be an option for the error handler. Small teaser, I envision something like this
iox_error(FATAL, HoofsError::POSIX_SEMAPHORE_FOO) << "what the heck: " << 42 \
    << "! This is not supposed to happen";

Btw, I'm wondering for what the custom error callback is good for? Do we need it? Can we remove it?
I had a quick grep over the codebase and we never provide a callback but I had some fun on #861 because it was accidentally used. We should kill it with fire but not in this PR.

I retracted my approval because I am not sure whether we can get rid of the template argument in
class ErrorHandler```
I would like to, if possible (as would @elBoberido ). I ust to not fully understand all implications and goals.

The template argument has the advantage the we actually enforce what kind or error this particular handler can handle at compile time (in contrast to providing a template method where the type is variable). This is only partially possible with template methods (would need `enable_if` which gets out of hand quickly)

This is closely related to the usage like ```auto errorHandlerGuard = iox::ErrorHandler<iox::Error>::setTemporaryErrorHandler ... ```. Here would like to somehow define it in a way that enforces to automatically call the correct error handler in the whole posh namespace etc. with the right error handler, maybe with a `using` directive in the module namespace. This alias will need to be called explicitly though

Sorry, this is not fully thought out on my side, I need to think this through over the weekend.
It is mainly a usage problem and I am not fully aware whether the goal is to actually enforce that some handler can only handle specific error types. Functionally it is all fine.

@elBoberido Thanks for the review.

The cxx::Expects should call the errror handler. At one point we have to delegate the error code to a 3rd party and cxx::Expects cannot do this since the error value is already erased.
I think you mixed something up. Probably you meant the FileReader? This is a bit misleading to see in the code, but this is not the error mode of the ErrorHandler but of the FileReader itself. Hence, I completely agree with The cxx::Expects should call the errror handler. :heavy_check_mark:

The cxx::Expects should also have an entry in this enum, e.g. EXPECTS_CONDITION_FAILED.

Will be implemented by #1035

Btw, I'm wondering for what the custom error callback is good for? Do we need it? Can we remove it?

That's true indeed :+1: Not in this PR.

I don't see a reason to create the template.

Well, setTemporaryErrorHandler is the reason I templatized, but you're right it's possible to erase the type and just use the underlying integer value. I'll give it a try.

I'll ask the heretical question, is this relevant for v2? The code freeze is not that far away and it binds resources on the reviewer side and on developer fixing merge conflicts due to breaking API changes. If we have too many of this side topics I fear we might run out of time at the end of February :/ This is not only related to your PR but in general to all PRs we currently have.

I understand what you mean. First prio are definitely the features #415 and #27. However, as this PR solves the last "illegal" dependency from iceoryx_hoofs to iceoryx_posh, I'd appreciate it a lot if we can merge it before v2.0. A clean architecture will enable us faster development in future. I have several other things in mind for v2.0 that are on the board.


Enhancement: add jsconfig when vite-aliases run

@Subwaytime could you please review this ?
I have difficulty on the logic so i don't think it's quite efficient. However, the basic idea is :

Check if vite has write access to the folder.
If true, then check if file exists using pathConfig option
If file exists then skip this step, otherwise create the file. ( still need to find out tsconfig.json default config )
check if paths exists.
check if paths has the same value from paths generated by vite-aliases.
If false, merge current paths with the paths derived from vite-aliases. ( if there's no paths then we just create the paths )

Oh please don't accept it yet.. if you like the PR, i have more questions about improving this.

Atm i am pretty busy due to another Project and World Vue Summit.
Will check this in some days!
I am also currently working on a "rewrite" in the dev branch..
Ive got the jsconfig/tsconfig Feature almost finished but not commited, due to some issues.. so maybe your pr can help! ;)

will be waiting for the "rewrite" but since the idea is quite awesome, i think i will finish the PR and help you with the "rewrite" if you want.
I also think that vite-aliases can grow into somekind of small ecosystem of plugins ? ( Is that a correct term to say ? ) For example :

Auto generate folder based / file based routing.
Content handling / file parsing based on the content of the folders.
etc.

Anyway, thanks for the amazing plugin. will finish the PR soon.

Hey there! Sorry for the late response..
So overall i think it would be better to keep vite-aliases as it is with the current feature set, due to the ones that you mentioned already exist! Ive been working on some other Plugins, that are WIP atm, but get released soon.
The Dev branch is almost finished now, with the upcoming JSConfig/TSConfig Feature Set and a Watcher.

ah ok...  waiting for it then.


Update Changelog with release date 2023-04-11

Description
Updated changelog to reflect release date of current release 2023-04-11
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


Add Filter

Add Filter On Active Event , Inactive Event , Upcoming Event

Please assign this to me.

/assign
@TejasNasre

/assign @TejasNasre

Started working bro

@TejasNasre this issue is assigned to me.


Update AboutUs and create skeletal PPP

Updated the AboutUs as well as included my image
Created a skeletal PPP

Codecov Report
Base: 72.15% // Head: 72.15% // No change to project coverage :thumbsup:

Coverage data is based on head (9669c7f) compared to base (cc2d303).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master      #34   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Update OOB to be a single protocol with a single message

Given the evolution of the OOB invitation message, this proposal eliminates the two messages in favour of one that handles both purposes, plus a third where both a connection is established and a request is made for use after the connection is established.

LGTM

Applied feedback from the Aries WG --notably the change from "setup_protocols" to "handshake_protocols". Added some more on using both lists at once in a message -- notably that reuse of the connection should be on the request~attach.
Suggest we merge this and then get more in a separate PR on the URL shortening.

@llorllale -- please add a review vs. just a comment.


Check for fanotify support before selecting it

When using the hook-mode auto, we were only checking that runc was present, but not that they system had fanotify  capabilities. In systems without CONFIG_FANOTIFY enabled, this would cause the Gadget Tracer Manager to fail to start.
This change checks that fanotify_init returns successfully before selecting it when in hook mode auto.
It also improves the error message when starting the tracer manager fails, and avoids adding the fallback podinformer when the auto hook mode selected podinformer, thus avoiding unnecessary warning messages.
How to use / Testing done
I deployed the modified container to a minikube instance using the kvm driver (which was failing to start before, as explained in #612), and verified that it correctly selected the podinformer and -after fixing the fallback selection- didn't log warnings.
I then deployed against a minikube instance using the docker driver, and hook mode auto, and in this case it selected fanotify with podinformer as the fallback.
Fixes #612

This is fixing a bug so I think we can merge before next release.


Exclude com.adobe.aem.wcm.site.manager.config.SiteConfig from PagePersistenceStrategy

If io.wcm.caconfig.extensions.persistence.impl.PagePersistenceStrategy is enabled, then for OOTB Ca Config com.adobe.aem.wcm.site.manager.config.SiteConfig all the properties are saved to the underlying jcr:content node.
When developing for a new Site Theme and you want to set a new frontend pipeline for it, you need to set the themePackageName for it in the SiteConfig.
However, in the implementation (com.adobe.aem.wcm.frontend.manager.impl.SiteThemeUpdateFrontendCodeDeploymentEventListener#findSiteConfigsUsingPackage) it performs a query to look for this property on the SiteConfig itself, not on the jcr:content underneath.
Either the PagePersistenceStrategy osgi config should be more flexible, or the SiteConfig should be excluded and never saved as a cq:Page.

yes, this is sadly true. using a JCR query they bypass the persistence abstraction of context-aware configuration and assume the property is always stored in the same node. i would call this a bug in AEM, but it's unlikely to be fixed anytime soon i suppose.
so we have to think about a workaround on our side.

@stefanseifert  A possible workaround that I see is making the PagePersistenceStrategy osgi config more flexible.
Instead of making it a true/false value, this could be made a regex just like with the AbsoluteParentContextPathStrategy.

my proposal would be to add something like a "configNameDenyList" property to the OSGi configuration of the AEM page persistence strategy. it allows full string or regex to match against configuration names - and we would put "com.adobe.aem.wcm.site.manager.config.SiteConfig" as a default value into this list.
any configuration name matching one of these is handled the AEM page persistence strategy skips it's processing.


Dbus-serial battery driver no longer recognized

Describe the problem
dbus-serial battery driver has stopped working and is no longer seen by the GX under Device list.

Driver version
v1.4.20240928
Venus OS device type
Cerbo GX
Venus OS version
v3.30
BMS type
JKBMS / Heltec BMS
Cell count
16
Battery count
1
Connection type
Serial USB adapter to RS485
Config file
BMS_TYPE = Jkbms
LOGGING = INFO

MAX_BATTERY_CHARGE_CURRENT = 140
MAX_BATTERY_DISCHARGE_CURRENT = 100

; --------- Cell Voltages ---------
; Description: Cell min/max voltages which are used to calculate the min/max ba                                                                             >
; Example: 16 cells * 3.45V/cell = 55.2V max charge voltage. 16 cells * 2.90V =                                                                             >
MIN_CELL_VOLTAGE   = 2.900
; Max voltage (can seen as absorption voltage)
MAX_CELL_VOLTAGE   = 3.450
; Float voltage (can be seen as resting voltage)
FLOAT_CELL_VOLTAGE = 3.350

; --------- SOC reset voltage ---------
SOC_RESET_VOLTAGE = 3.620

; --------- SOC calculation ---------
SOC_CALCULATION = TRUE
SOC_RESET_CURRENT = 7
SOC_RESET_TIME = 60
SOC_CALC_CURRENT_REPORTED_BY_BMS  = -300, 300
SOC_CALC_CURRENT_MEASURED_BY_USER = -300, 300

; Temperature sensor 1 name
TEMP_1_NAME = Temp Cells 4|5

; Temperature sensor 2 name
TEMP_2_NAME = Temp Cells 12|13

LINEAR_LIMITATION_ENABLE = True

CVCM_ENABLE = True
CCCM_CV_ENABLE = True
DCCM_CV_ENABLE = True
CCCM_T_ENABLE = True
DCCM_T_ENABLE = True

; --------- Cell Voltage limitation (affecting CVL) ---------
CVL_ICONTROLLER_MODE = True
CVL_ICONTROLLER_FACTOR = 0.2

Relevant log output
root@einstein:~# tail -F -n 100 /data/log/dbus-serialbattery.ttyUSB0/current | tai64nlocal
2024-10-11 22:52:22.317767500   File "/opt/victronenergy/dbus-serialbattery/utils.py", line 44, in <module>
2024-10-11 22:52:22.327047500     config.read([default_config_file_path, custom_config_file_path])
2024-10-11 22:52:22.327056500   File "/usr/lib/python3.8/configparser.py", line 697, in read
2024-10-11 22:52:22.327060500     self._read(fp, filename)
2024-10-11 22:52:22.327062500   File "/usr/lib/python3.8/configparser.py", line 1082, in _read
2024-10-11 22:52:22.327065500     raise MissingSectionHeaderError(fpname, lineno, line)
2024-10-11 22:52:22.327244500 configparser.MissingSectionHeaderError: File contains no section headers.
2024-10-11 22:52:22.327249500 file: '/opt/victronenergy/dbus-serialbattery/config.ini', line: 1
2024-10-11 22:52:22.327252500 'BMS_TYPE = Jkbms\n'
2024-10-11 22:52:58.015947500 Traceback (most recent call last):
2024-10-11 22:52:58.015957500   File "/opt/victronenergy/dbus-serialbattery/dbus-serialbattery.py", line 16, in <module>
2024-10-11 22:52:58.015960500     from dbushelper import DbusHelper
2024-10-11 22:52:58.015963500   File "/opt/victronenergy/dbus-serialbattery/dbushelper.py", line 8, in <module>
2024-10-11 22:52:58.015966500     from utils import logger, publish_config_variables
2024-10-11 22:52:58.015969500   File "/opt/victronenergy/dbus-serialbattery/utils.py", line 44, in <module>
2024-10-11 22:52:58.016159500     config.read([default_config_file_path, custom_config_file_path])
2024-10-11 22:52:58.016164500   File "/usr/lib/python3.8/configparser.py", line 697, in read
2024-10-11 22:52:58.016167500     self._read(fp, filename)
2024-10-11 22:52:58.016169500   File "/usr/lib/python3.8/configparser.py", line 1082, in _read
2024-10-11 22:52:58.016172500     raise MissingSectionHeaderError(fpname, lineno, line)
2024-10-11 22:52:58.016213500 configparser.MissingSectionHeaderError: File contains no section headers.
2024-10-11 22:52:58.016216500 file: '/opt/victronenergy/dbus-serialbattery/config.ini', line: 1
2024-10-11 22:52:58.016219500 'BMS_TYPE = Jkbms\n'
2024-10-11 22:53:36.537783500 Traceback (most recent call last):
2024-10-11 22:53:36.537792500   File "/opt/victronenergy/dbus-serialbattery/dbus-serialbattery.py", line 16, in <module>
2024-10-11 22:53:36.537796500     from dbushelper import DbusHelper
2024-10-11 22:53:36.537798500   File "/opt/victronenergy/dbus-serialbattery/dbushelper.py", line 8, in <module>
2024-10-11 22:53:36.537802500     from utils import logger, publish_config_variables
2024-10-11 22:53:36.537804500   File "/opt/victronenergy/dbus-serialbattery/utils.py", line 44, in <module>
2024-10-11 22:53:36.537963500     config.read([default_config_file_path, custom_config_file_path])
2024-10-11 22:53:36.537966500   File "/usr/lib/python3.8/configparser.py", line 697, in read
2024-10-11 22:53:36.537970500     self._read(fp, filename)
2024-10-11 22:53:36.537971500   File "/usr/lib/python3.8/configparser.py", line 1082, in _read
2024-10-11 22:53:36.537974500     raise MissingSectionHeaderError(fpname, lineno, line)
2024-10-11 22:53:36.538003500 configparser.MissingSectionHeaderError: File contains no section headers.
2024-10-11 22:53:36.538007500 file: '/opt/victronenergy/dbus-serialbattery/config.ini', line: 1
2024-10-11 22:53:36.538010500 'BMS_TYPE = Jkbms\n'
2024-10-11 22:54:13.576974500 Traceback (most recent call last):
2024-10-11 22:54:13.576983500   File "/opt/victronenergy/dbus-serialbattery/dbus-serialbattery.py", line 16, in <module>
2024-10-11 22:54:13.576986500     from dbushelper import DbusHelper
2024-10-11 22:54:13.576989500   File "/opt/victronenergy/dbus-serialbattery/dbushelper.py", line 8, in <module>
2024-10-11 22:54:13.576992500     from utils import logger, publish_config_variables
2024-10-11 22:54:13.576995500   File "/opt/victronenergy/dbus-serialbattery/utils.py", line 44, in <module>
2024-10-11 22:54:13.577149500     config.read([default_config_file_path, custom_config_file_path])
2024-10-11 22:54:13.577153500   File "/usr/lib/python3.8/configparser.py", line 697, in read
2024-10-11 22:54:13.577156500     self._read(fp, filename)
2024-10-11 22:54:13.577158500   File "/usr/lib/python3.8/configparser.py", line 1082, in _read
2024-10-11 22:54:13.577161500     raise MissingSectionHeaderError(fpname, lineno, line)
2024-10-11 22:54:13.577193500 configparser.MissingSectionHeaderError: File contains no section headers.
2024-10-11 22:54:13.577196500 file: '/opt/victronenergy/dbus-serialbattery/config.ini', line: 1
2024-10-11 22:54:13.577199500 'BMS_TYPE = Jkbms\n'
^C
root@einstein:~# tail -F -n 100 /data/log/serial-starter/current | grep dbus-serialbattery | tai64nlocal
^C
root@einstein:~# tail -F /data/log/serial-starter/current | tai64nlocal
2024-10-11 22:58:03.127628500 INFO: Start service dbus-modbus-client.serial.ttyUSB0 once
2024-10-11 22:58:10.961858500 INFO: Start service dbus-serialbattery.ttyUSB0 once
2024-10-11 22:58:14.222418500 INFO: Start service gps-dbus.ttyUSB0 once
2024-10-11 22:58:23.698973500 INFO: Start service vedirect-interface.ttyUSB0 once
2024-10-11 22:58:29.099725500 INFO: Start service dbus-cgwacs.ttyUSB0 once
2024-10-11 22:58:34.475991500 INFO: Start service dbus-fzsonick-48tl.ttyUSB0 once
2024-10-11 22:58:39.838659500 INFO: Start service dbus-imt-si-rs485tc.ttyUSB0 once
2024-10-11 22:58:43.197819500 INFO: Start service dbus-modbus-client.serial.ttyUSB0 once
2024-10-11 22:58:51.019007500 INFO: Start service dbus-serialbattery.ttyUSB0 once
2024-10-11 22:58:54.340318500 INFO: Start service gps-dbus.ttyUSB0 once
2024-10-11 22:59:03.729310500 INFO: Start service vedirect-interface.ttyUSB0 once
^C
root@einstein:~# tail -F /data/log/serial-starter/current | tai64nlocal
2024-10-11 22:58:34.475991500 INFO: Start service dbus-fzsonick-48tl.ttyUSB0 once
2024-10-11 22:58:39.838659500 INFO: Start service dbus-imt-si-rs485tc.ttyUSB0 once
2024-10-11 22:58:43.197819500 INFO: Start service dbus-modbus-client.serial.ttyUSB0 once
2024-10-11 22:58:51.019007500 INFO: Start service dbus-serialbattery.ttyUSB0 once
2024-10-11 22:58:54.340318500 INFO: Start service gps-dbus.ttyUSB0 once
2024-10-11 22:59:03.729310500 INFO: Start service vedirect-interface.ttyUSB0 once
2024-10-11 22:59:09.085770500 INFO: Start service dbus-cgwacs.ttyUSB0 once
2024-10-11 22:59:14.429160500 INFO: Start service dbus-fzsonick-48tl.ttyUSB0 once
2024-10-11 22:59:19.808347500 INFO: Start service dbus-imt-si-rs485tc.ttyUSB0 once
2024-10-11 22:59:25.173176500 INFO: Start service dbus-modbus-client.serial.ttyUSB0 once
2024-10-11 22:59:32.653279500 INFO: Start service dbus-serialbattery.ttyUSB0 once
2024-10-11 22:59:36.043245500 INFO: Start service gps-dbus.ttyUSB0 once
2024-10-11 22:59:43.387008500 INFO: Start service vedirect-interface.ttyUSB0 once
^C
root@einstein:~# ls -l /dev/ttyUSB*
ls: /dev/ttyUSB*: No such file or directory
root@einstein:~# ls -l /dev/ttyUSB0
ls: /dev/ttyUSB0: No such file or directory
root@einstein:~# ls -l /dev/ttyUSB*
ls: /dev/ttyUSB*: No such file or directory
root@einstein:~# ls -l /dev/ttyUSB*
crw-rw----    1 root     dialout   188,   0 Oct 11 23:01 /dev/ttyUSB0
root@einstein:~# ls -l /dev/ttyUSB*
crw-rw----    1 root     dialout   188,   0 Oct 11 23:01 /dev/ttyUSB0
root@einstein:~# ls -l /dev/ttyUSB0
crw-rw----    1 root     dialout   188,   0 Oct 11 23:01 /dev/ttyUSB0
root@einstein:~# rter/*
-sh: rter/*: No such file or directory
root@einstein:~# rter/*
-sh: rter/*: No such file or directory
root@einstein:~# head /data/var/lib/serial-starter/*
==> /data/var/lib/serial-starter/ttyS4 <==
mkx

==> /data/var/lib/serial-starter/ttyS5 <==
vedirect

==> /data/var/lib/serial-starter/ttyS6 <==
vedirect

==> /data/var/lib/serial-starter/ttyS7 <==
vedirect

==> /data/var/lib/serial-starter/ttyUSB0 <==
imt
root@einstein:~# tail -F /data/log/dbus-serialbattery.ttyUSB0/current | tai64nlocal
2024-10-11 23:02:47.876498500     from utils import logger, publish_config_variables
2024-10-11 23:02:47.876501500   File "/opt/victronenergy/dbus-serialbattery/utils.py", line 44, in <module>
2024-10-11 23:02:47.876669500     config.read([default_config_file_path, custom_config_file_path])
2024-10-11 23:02:47.876673500   File "/usr/lib/python3.8/configparser.py", line 697, in read
2024-10-11 23:02:47.876676500     self._read(fp, filename)
2024-10-11 23:02:47.876678500   File "/usr/lib/python3.8/configparser.py", line 1082, in _read
2024-10-11 23:02:47.876681500     raise MissingSectionHeaderError(fpname, lineno, line)
2024-10-11 23:02:47.876714500 configparser.MissingSectionHeaderError: File contains no section headers.
2024-10-11 23:02:47.876719500 file: '/opt/victronenergy/dbus-serialbattery/config.ini', line: 1
2024-10-11 23:02:47.876722500 'BMS_TYPE = Jkbms\n'
2024-10-11 23:03:27.782967500 Traceback (most recent call last):
2024-10-11 23:03:27.782975500   File "/opt/victronenergy/dbus-serialbattery/dbus-serialbattery.py", line 16, in <module>
2024-10-11 23:03:27.782979500     from dbushelper import DbusHelper
2024-10-11 23:03:27.782982500   File "/opt/victronenergy/dbus-serialbattery/dbushelper.py", line 8, in <module>
2024-10-11 23:03:27.782985500     from utils import logger, publish_config_variables
2024-10-11 23:03:27.782988500   File "/opt/victronenergy/dbus-serialbattery/utils.py", line 44, in <module>
2024-10-11 23:03:27.783191500     config.read([default_config_file_path, custom_config_file_path])
2024-10-11 23:03:27.783195500   File "/usr/lib/python3.8/configparser.py", line 697, in read
2024-10-11 23:03:27.783198500     self._read(fp, filename)
2024-10-11 23:03:27.783200500   File "/usr/lib/python3.8/configparser.py", line 1082, in _read
2024-10-11 23:03:27.783203500     raise MissingSectionHeaderError(fpname, lineno, line)
2024-10-11 23:03:27.783237500 configparser.MissingSectionHeaderError: File contains no section headers.
2024-10-11 23:03:27.783240500 file: '/opt/victronenergy/dbus-serialbattery/config.ini', line: 1
2024-10-11 23:03:27.783243500 'BMS_TYPE = Jkbms\n'
2024-10-11 23:04:07.814195500 Traceback (most recent call last):
2024-10-11 23:04:07.814205500   File "/opt/victronenergy/dbus-serialbattery/dbus-serialbattery.py", line 16, in <module>
2024-10-11 23:04:07.814209500     from dbushelper import DbusHelper
2024-10-11 23:04:07.814211500   File "/opt/victronenergy/dbus-serialbattery/dbushelper.py", line 8, in <module>
2024-10-11 23:04:07.814214500     from utils import logger, publish_config_variables
2024-10-11 23:04:07.814217500   File "/opt/victronenergy/dbus-serialbattery/utils.py", line 44, in <module>
2024-10-11 23:04:07.814402500     config.read([default_config_file_path, custom_config_file_path])
2024-10-11 23:04:07.814407500   File "/usr/lib/python3.8/configparser.py", line 697, in read
2024-10-11 23:04:07.814410500     self._read(fp, filename)
2024-10-11 23:04:07.814412500   File "/usr/lib/python3.8/configparser.py", line 1082, in _read
2024-10-11 23:04:07.814415500     raise MissingSectionHeaderError(fpname, lineno, line)
2024-10-11 23:04:07.814533500 configparser.MissingSectionHeaderError: File contains no section headers.
2024-10-11 23:04:07.814538500 file: '/opt/victronenergy/dbus-serialbattery/config.ini', line: 1
2024-10-11 23:04:07.814541500 'BMS_TYPE = Jkbms\n'
^C
root@einstein:~# svstat /service/dbus-serialbattery.tty*
/service/dbus-serialbattery.ttyUSB0: down 8 seconds, normally up
root@einstein:~#

Any other information that may be helpful
The driver was installed and working perfectly for many months alongside GUI mods on Venus OS 3.30 Large (I am using a flow to control Grafana on raspberry PI).
I was using an older version of the driver (v1.2.202404xx) and started having some issue where CVL was limited to float voltage well before 100% SOC. I tried to update remotely via Tailscale to v1.4.20240928 and was somewhat successful. The new drive showed up under Device list and Remote Console. After several remote reboots I lost connection to the driver.
I am now at the location and tried to reflash the driver, as well follow all troubleshooting. It seems like there is a problem with the software on the Cerbo GX that does not allow data from the USB port. I tried swapping USB ports but no luck.
I have a spare Cerbo GX that has the driver flashed and it recognized SerialBattery in Device list right away so I can definitely rule out any cabling issues.

configparser.MissingSectionHeaderError: File contains no section headers.

 Add it again and it should work:
https://github.com/Louisvdw/dbus-serialbattery/blob/fd0fc1a193427df6ca0fadd141aa57826f761819/etc/dbus-serialbattery/config.default.ini#L1

Yeah, something happened and my complete config file was empty so I copy and pasted my config from a backup file. Must have missed that first line. Everything works now. Thank you 😀