Provider produced an unexpected new value: Root resource was present, but now absent.

Describe the bug
We are having the following error trying to apply our infra for creating a configcat_setting_value resource:
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to
│ configcat_setting_value.target_clients_setting_value, provider
│ "provider[\"registry.terraform.io/configcat/configcat\"]" produced an
│ unexpected new value: Root resource was present, but now absent.
│
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.
╵

To reproduce
We are adding planning without any issue the following infra but we are having the error during the apply
resource "configcat_setting" "target_clients_flag" {
  config_id    = "config_cat_id"
  key          = "isTargetClient"
  name         = "Description"
  setting_type = "boolean"
}

resource "configcat_setting_value" "target_clients_setting_value" {
  environment_id = "config_cat_id"
  setting_id     = configcat_setting.target_clients_flag.id
  value          = "false"
  init_only      = "true"

  rollout_rules {
    comparison_attribute = "Identifier"
    comparator           = "isOneOf"
    comparison_value     = "ClientId"
    value                = "true"
  }
}

We are using the version 1.4.0 for the provider but we had the same issue with the 1.3.6
   configcat = {
      source  = "configcat/configcat"
      version = ">= 1.4"
    }

Expected behavior
The resource is created
Screenshots
If applicable, add screenshots to help explain your problem.

Hello @juanfi ,
Thanks for reaching out. I'm trying to reproduce the issue and I'll get back to you.

Hello @juanfi ,
I tried reproducing your issue, but it worked for me with your configuration.
I even deleted the feature flag on the ConfigCat Dashboard after creating it with Terraform and a new terraform run could re-create it.
Could you please send me more details about your terraform files? It would be awesome if you could create a sample repository so I can reproduce your issue.  Could you please also provide the full logs for your terraform run?

Hello @juanfi,
Do you have any updates regarding this issue?

Hi, sorry for the delay.
I'm still having the same issue and those are the only logs that I have (We run our infra with atlantis and that is the log that I have)
I'll try to replicate it in a personal project and share the repo with you if I have some free time.
Thanks.

Hello @juanfi,
Do you have any updates related this issue?
Cheers,
Lali

Hello @juanfi,
I am closing this issue as I didn't hear back from you a while ago. If you still experience the issue, please prepare a sample repository so I can reproduce the bug and try to fix it.
Cheers,
Lali


Appium Android Fixes

As far as I can tell the current Android Appium sample doesn't quite work.
Appium is a bit quirky with Android Apps because in Debug mode you have to enable 'noReset' otherwise appium will delete tthe dlls copied over with fast deployment.  I noticed in the current sample we are disabling fast deployment, but I don't think we want to do this as it makes debugs build much slower and is not the normal work flow.

Huh curious! I recall that this worked back then for all scenarios. But indeed the current state on main doesn't and this seems to fix it!

Note to self: review if the code comments make sense and if we need to add something more to the README of this project for more clarification


Dash app running on http://<IP_ADDRESS>:8050

In the 04 Explanatory Data Visualization notebook, a dash app is created from the notebook directly, but it cannot be used.
While the cells execute fine, the Dash app is not reachable from the notebook interface because it is running on localhost on a port that is not forwarded to the end user:

cc @exactlyallan

It looks like this repo contains the configuration to make it run on Binder with jupyter-server-proxy: https://github.com/plotly/jupyter-dash

Adding a cell with:
JupyterDash.infer_jupyter_proxy_config()

And switching to:
app.run_server(mode="inline")

Seems to do the trick:

Keeping:
app.run_server(debug=False)

also works, so we can leave the cell untouched and the missing cell mentioned above.


[FEATURE] - Handle FirmaTypes as an Enum instead of string

Description
This would be a breaking change, but it would be a better DX if FirmaTypes was of type Enum instead of string.

I kind of agree that it would be nice. But as of right now, the other packages makes use of strings, and changing the C# version to use enum would break the "same api in all languages" principle.
I will take it up with the other maintainers and see how they feel.

Sorry for not being more responsive on this issue. I have considered it again to see if I can figure out a good way to implement this (could probably even be done without breaking too much of the API by just adding a new property for it) and can't really see a good way to do it.
First of, the enum would probably have to either be transtlated to english, or use å, ä, ö in a lot of words (it would be really ugly).
This could probably be done, but due to the fact that multiple values are 'Övrigt', we got more issues in that.
I've considered returning the integer value instead, and allow using that as an ID with a lookup table, which I also find kinda bad (especially due to us using kind of custom values for the types).
So in the end, I can't really find a good way to implement this without it being either very ugly or kinda useless, so for now, I'll close this issue and revisit it in the future in case I figure out a good way.
Feel free to come with implementation ideas and I might reopen and implement it in the future!


error TS7006: Parameter 'T' implicitly has an 'any' type.

Hi,
I have the typescript compiler reported /lib/index.d.ts(33,31): error TS7006: Parameter 'T' implicitly has an 'any' type.
Looks like there is typo under the file lib/index.d.ts
/**
     * set the data for an existing node (will throw an Error if the node does not exist)
     * @param {string} name
     * @param data
     */
    setNodeData(name: string, T): void;

Should be like below?
/**
     * set the data for an existing node (will throw an Error if the node does not exist)
     * @param {string} name
     * @param data
     */
    setNodeData(name: string, data?: T): void;

I am new to typescript, maybe I haven't got my tsconfig.json setup properly..

You are correct! I've just pushed a fix (and released version 0.5.2)

It works fine now. Thanks and like your work!


Cannot find kernel2js compiler

Steps to Reproduce

I updated flutter to the latest master channel, and try run my app in chrome devices, then it throw me a Exception: Cannot find kernel2js compiler for packages/flutter/src/material/icon_button.dart. Compilers are avaiable for modules:  () exception. I did not change any code, so I think it might be the problem of flutter upgrade issue.
Expected results:
Run normally like a few day ago.
Actual results:
Run failed with the following errors.

However I can run it in windows device, I have not test in android.

Logs
Unhandled exception:
Exception: Cannot find kernel2js compiler for packages/flutter/src/material/icon_button.dart. Compilers are avaiable for modules:
	()
#0      FrontendCompiler.compileExpressionToJs  (package:frontend_server/frontend_server.dart:921:9)
#1      _FlutterFrontendCompiler.compileExpressionToJs  (package:flutter_frontend_server/server.dart:84:22)
#2      listenAndCompile.<anonymous closure>  (package:frontend_server/frontend_server.dart:1308:18)
<asynchronous suspension>
#3      listenAndCompile.<anonymous closure> (package:frontend_server/frontend_server.dart)
#4      _RootZone.runUnaryGuarded  (dart:async/zone.dart:1374:10)
#5      _BufferingStreamSubscription._sendData  (dart:async/stream_impl.dart:339:11)
#6      _BufferingStreamSubscription._add  (dart:async/stream_impl.dart:266:7)

#7      _SinkTransformerStreamSubscription._add  (dart:async/stream_transformers.dart:70:11)
#8      _EventSinkWrapper.add  (dart:async/stream_transformers.dart:17:11)
#9      _StringAdapterSink.add  (dart:convert/string_conversion.dart:238:11)
......

I updated the flutter, same errors.

This is an error from expression evaluations, which is not completely supported in Flutter for web yet. FYI @annagrin

I switch the IDE from vscode to android studio, then this error disappeared. It's really strange.
Even I reinstalled the flutter plugin in vscode, I still can't run it in vscode.

My mistake, it could not run in chrome in android studio with the same errors. But I can run flutter build web without errors.
I also confused about the devices chrome and web server, what's difference between them.

Looks like expression evaluation was invoked by VSCode (maybe when hovering over or a watch window, or a conditional breakpoint, or direct expression evaluation) and failed. Will see how I can make the failure not crash the frontend server.

I see it is merged to the master branch, and I upgrade the flutter, and run in vscode (add --web-enable-expression-evaluation in the Flutter Additional Args) or cmd shell via --web-enable-expression-evaluation, but I still got the same error.
D:\code\flutter\colorful_classroom_app>flutter run -d chrome --web-enable-expression-evaluation
Launching lib\main.dart on Chrome in debug mode...
Syncing files to device Chrome...
26,678ms (!)
Debug service listening on ws://<IP_ADDRESS>:53831/l66xFkailPM=

Warning: Flutter's support for web development is not stable yet and hasn't
been thoroughly tested in production environments.
For more information see https://flutter.dev/web

  To hot restart changes while running, press "r". To hot restart (and refresh the browser), press "R".
For a more detailed help message, press "h".  Looks like the expression evaluation bug is fixed, and you are only seeing the original exception. To handle it properly it might be better to open a separate issue, so you get all the notifications related to that problem. My bad for not recognizing the mixup - I was under impression the exception is expected.


Entrypoints

This PR makes it possible for third party packages to register new parser tools and operations using the standard python entrypoint / plugin system.
In particular, this means that a project that uses docetl that needs a custom parser, does not need to write the parser code inline in the yaml pipeline file, but can implement it in a normal python package and just reference it in the yaml, as long as the python package is installed using pyproject.toml or setup.py and registers the parser function there.

Awesome -- thank you!


Mono: Fix property set_value and cleanup

Fixes #20531

Now that Godot 3.1 has been released, we only plan to cherry-pick critical bug fixes to the 3.0 branch, unless there is very strong support in favor of a specific non-critical issue. Removing cherrypick label for 3.0.


Implement Belmon Ford Algorithm

Have you read the Contributing Guidelines on Pull Requests?
YES
Description
Belmon Ford Algorithm
Issue no-#45
Checklist

[x]  I've read the contribution guidelines.
[x]  I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
(Write your answer here.)

kindly review this PR @Kajol-Kumari @SKAUL05 @siddharth25pandey @iamrajiv @HarshCasper

@SKAUL05  @Kajol-Kumari
kindly review and merge this PR


Issues with helm templates

Might be out of scope for this project, but I was trying to use yamlfmt on our charts repository and it ran into all sorts of errors with the templates.
Example of error:
configuration-service/templates/postgres.yaml: yaml: did not find expected node content

Hi @inssein thanks for opening an issue. Admittedly I'm very outside of the Kubernetes world so I can't say confidently why this wouldn't work. I don't know much about helm charting.
I think it's in scope for the project, I would really love it to work because helm charts are such a heavy spot where people use lots of yaml.
It would be a big help if you could post an example of a helm chart that failed (with any info redacted of course) so I could look into it and see if it's something that's fixable. Perhaps helm charts use a different yaml syntax or something that I don't know about.

@braydonk for sure, here is an example I took from our repository:
apiVersion: v1
kind: ConfigMap
metadata:
  name: ratelimiter-config
  labels:
    {{- include "chart.labels" . | nindent 4 }}
data:
  config.yaml: |
    ---
    domain: test
    descriptors:
      - key: foo
        rate_limit:
          unit: minute
          requests_per_unit:<PHONE_NUMBER>

When I run this file through yamlfmt, I get:
2023/05/15 10:03:03 encountered the following formatting errors:
[redacted]/configmap-ratelimiter.yaml: yaml: line 5: did not find expected node content

Ah I see. It's the templating language. Those aren't valid yaml, so the yaml parser is complaining about that. I think it would be very challenging to support this, except for potentially making a whole new formatter that instead parses helm chart templates. If that exists it potentially could be done, but as it is those template files won't work with yamlfmt today.
Are there any helm files that are not templates that also fail in some way?

I haven't come across any other failures yet.
I guess one improvement I can see right away is that when there is an error, no formatting is done to any of the other files. Would be good to skip over the templating files that error out and still get the rest of the files in the interim.

Yeah I think that's a simple change that I should have done a while ago, and I'll put it on my list. I always put it off because one of the original usages of the tool when I first made it was to fail if there was any invalid YAML by design. The way I handle it right now is not very elegant though, I can make it much nicer.
In the meantime, if you exclude the templates directory, would the tool work on everything else? Just so you might be unblocked and able to use the tool until I get it working a bit nicer.

I took a look at it, and I think it would be at the moment infeasible for me to implement support for Helm chart templates. Most of the functionality of this tool relies on being able to parse something as valid YAML and output the same valid YAML. It might be possible for this to be implemented, but it would unfortunately require basically reimplementing the YAML parser to also recognize the Go templating language that Helm uses mixed in with YAML. It's not impossible, but I am probably not going to be able to add support for it any time soon.
I definitely will include the continuing on error functionality, so that the whole program doesn't fail upon a single file being incorrect.

I added the functionality you suggested where yamlfmt can continue and format the rest of the files even if some are invalid. I don't have an ETA just yet for the next release since I have a couple other small bugs I want to get in before I make it.
I think I'm going to close this for now due to helm charts being very difficult to include at this time, although I would like to support them some day I probably won't be able to address it any time soon. Thank you for your help with examples and feedback!

Thank you @braydonk. Best open source interaction in a while :)

Thank you @inssein that means a lot!


[ HELP ] - VW Golf 7

Hello,
Yesterday my Golf 7 (late 2015) popped up saying that car play, bluetooth etc was not working and that I needed to enter an activation code.
Current software version MHI2_ER_VWG11_S2103
Will this project work for me to achieve unlocking of all services?
Alternatively, what tool should I use?
Thank you all very much. I will then support the project financially if necessary.
Thank you
Robert

What you are asking for is not part of this project...
https://github.com/jilleb/mib2-toolbox/blob/master/FAQ.md


Update setup-guides-for-microsoft-365.md

Added Viva Amplify, Viva Glint and Viva Pulse to the setup guide.

@kelleyvice-msft Added Viva Amplify, Viva Glint and Viva Pulse to the setup guide.


feat: moved overlay-byocni-up target to tagged ip

Reason for Change:
As part of the security sprint, we are updating all public IPs created to use IPs from Service Tags. Currently the Service Tag our team has requested is still pending, so this PR uses a temporary tag provided for testing: /TestTagging-O365.
This PR changes the standalone cluster ARM template to use a bicep file, mainly due to more readable syntax and implementation (especially when adding resource dependencies). The new bicep file will provision the AKS cluster as well as a public IP using a Service Tag, which will be used by the AKS cluster as an outbound IP. This prevents the default cluster creation from creating its own public outbound IP (which doesn't have a Service Tag)
Issue Fixed:
Pipeline CNI LSG calls Makefile to create cluster.


Changes ode default step size to PIDController

Constant steps are often far from optimal.
This sets the default to be variable step length with tolerance default matching those of other integrators.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.399%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
725

Relevant Lines:
802

💛  - Coveralls


Need to provide an option to close all other open stackblocks when a new stackblock is opened in StackView

Select one ...  (check one with "x")
[ ] bug
[X] feature request

Expected behavior
Need to provide a way for users to close all other stack blocks when a new stack block gets opened so the stack view acts as an accordion. This will not be the default option, it will be an additional feature that a user can turn on.
Actual behavior
Right now the default and only behavior is to allow as many stack blocks to be open within a stack view.
Reproduction of behavior
N/A
Environment details

Angular version: 2.0.X
2.1.0

Clarity version:
0.6.1

Browser:
all

@yenmade this needs some UX input. The point of a stackview is progressive disclosure but my concern is that this makes a stackview an accordion and might encourage that pattern as a recommended pattern by Clarity. It seems to me that if you want to close other stackblocks as you open new ones then maybe a stackview is not what you're looking for because you could many of other options (tabs for example). That said, I'd like to make sure we do further research on this before we make a call to not go forward with it as an option.

Agreed, I'll add this to the UX backlog to further research before making a call.

Do not make this the default
Do make it a configurable option on StackView

Needs API work to define contributions. Needs plunkr to mark for workaround.

Here is how to do it on the app side for now, until the feature is implemented: https://plnkr.co/edit/UdrYdIhCpVI9PAUhWc7n?p=preview

This issue is stale with little activity in the past months, and it is also possible for applications to handle this on their end. Closing this as we try to clean up the backlog, and a new issue can be created for it if it becomes a need.


cargo check/schema on contract issues error when the contract use GlobalApi

After https://github.com/line/cosmwasm/pull/212, we expose GlobalApi only to the wasm target. It causes an error when cargo check or cargo schema.
And, unit tests cannot use GlobalApi. It is related with #213

closed via #220


Update azure-pipelines-release.yml

added batch processing

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 81.62%. Comparing base (10c2cd0) to head (d19c983).
Report is 189 commits behind head on release.

Additional details and impacted files
@@           Coverage Diff            @@
##           release      #53   +/-   ##
========================================
  Coverage    81.62%   81.62%
========================================
  Files           43       43
  Lines          936      936
  Branches        88       88
========================================
  Hits           764      764
  Misses         141      141
  Partials        31       31

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


Stuck on "ssh" or "user session is ready for ssh"

Description
I'm basically experiencing what is described in #18 but I prefer to open a new issue because it's been a long time. Plus it's happening with vz which is still considered experimental.
I'm using Lima as a replacement for Docker Desktop on macOS 13.1. Here's the configuration I use.
Everything works fine for a while but after some time I get stuck connecting to the VM, possibly after the laptop goes to sleep, waiting for requirement 1 or 2. It is worth mentioning that a factory-reset solves the issue. It was also reproduced by coworkers so unlikely to be specific to my computer. I have a feeling it might be related to our VPN configuration messing with the network configuration Lima is setting up, but that's hard to say.
I'm attaching logs:

ha.stderr.log
ha.stdout.log
serial.log

Sorry for the lack of details on my side. I'll try to collect any correlation I can make as we go.

@warrenseine
Could you give a try with default vz example. See if that works ??
From serial.log, i could see vm started successfully. So like you said something happening with network configuration only

I also have the same problem with vz.
After putting the laptop to sleep for a while, I sometimes get a connection error in the limactl shell.
In that case, limactl stop -f may fix it, and in other cases, it can't be fixed without factory reset.
I was able to reproduce the same issue with the vz default config.
❯ lima -v
limactl version 0.14.2

❯ sw_vers
ProductName:		macOS
ProductVersion:		13.0.1
BuildVersion:		22A400

me too

@thr3a
Sure thanks for the info. Will try to reproduce this.
If possible when this happens could you check ha.stderr.log and see if it has some helpful error (check before doing stop -f and error when trying limactl shell)

Yes, most of the time stop -f does the job, but I agree with @thr3a, in some cases a factory-reset is still needed. Maybe these are 2 separate issues.
Thank you for the feature request to vz. Let's hope this will unlock a fix for the first case already!

@thr3a / @warrenseine
Could you try the following and share the serial.log only for cases when stop -f didn't work.
Note: The below steps is purely for debugging purpose only

Goto your instance folder
Edit lima.yaml

change vmType to qemu
remove mountType, rossetta  or any vz specific properties

start the vm using limactl start

Share the current serial.log

Hello @balajiv113, this has just happened, and I'm stuck in a Waiting for the essential requirement 1 of 3: "ssh" loop after a limactl stop -f && limactl start. Here are the log files before I changed the vm type:

ha.stderr.log
ha.stdout.log
serial.log
lima.yaml.txt

And here are the ones after:

ha.stderr.log
ha.stdout.log
serial.log
lima.yaml.txt

It looks like it's still stuck after switching to qemu. And as usual, a factory reset works.

Thanks for this logs.
Looks like a case of disk corruption only. Mount of root filesystem is what didn't happen here.
Maybe after #1315 is merged. We can try again to see if this happens after that.

I've tested again with 0.15 and the issue is still present (can't SSH, still seeing kex_exchange_identification: read: Connection reset by peer in ha.stderr.log). I was not able to find any additional relevant information in the logs.
I'll factory reset and update this issue if something changes.

I've tested Colima for the past week and I still have the same problem of losing the VM, requiring a restart, but the good news is that I never have to factory reset the VM, so it must be doing something.

@warrenseine @balajiv113
Hello. I came across this issue when I was creating my own podman template, so I thought I'd comment.
In conclusion, it seems that this problem is less likely to be affected by disk corruption when booting from an iso image.
Colima seems to be using the alpine image, but this one is based on an iso image:
https://github.com/abiosoft/colima/blob/ed49fef4ad63ec48055b4b230ecbad00c54f5417/environment/vm/lima/yaml.go#L56-L57
With iso images, directories like /usr, /bin, /lib, and /sbin are provided by tmpfs, so it seems to start from a clean state upon reboot. (Reference: https://github.com/lima-vm/lima/issues/255#issuecomment-922538119)


Add Homebrew installation details

What type of PR is this:

/kind documentation
What does this PR do / why we need it:
Adds documentation on how to install via brew.
Which issue(s) this PR fixes:

Fixes https://github.com/redhat-developer/odo/issues/5801
PR acceptance criteria:

[X] Documentation

How to test changes / Special notes to the reviewer:
Signed-off-by: Charlie Drage<EMAIL_ADDRESS>

/override OpenShift Integration tests/OpenShift Integration tests
Doc only

/approve


spi: move set_format to all states

There are other drivers in the wild (uboot, zephyr) that set the format without disabling the peripheral, so we’ll assume it is fine to do so.

LGTM. Just needs a format.


fix: Take a deep copy of circuit inputs for proving

Please read contributing guidelines and remove this line.

#5777  👈
master

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

Join @PhilWindle and the rest of your teammates on  Graphite

Benchmark results
Metrics with a significant change:

circuit_simulation_time_in_ms (base-rollup): 16,143 (+30%)
circuit_simulation_time_in_ms (merge-rollup): 8.67 (-36%)
l2_block_building_time_in_ms (8): 13,088 (+35%)
l2_block_building_time_in_ms (32): 51,043 (+35%)
l2_block_building_time_in_ms (64): 102,726 (+35%)
l2_block_rollup_simulation_time_in_ms (8): 12,899 (+36%)
l2_block_rollup_simulation_time_in_ms (32): 50,366 (+35%)
l2_block_rollup_simulation_time_in_ms (64): 101,399 (+35%)
l2_block_processing_time_in_ms (64): 9,801 (-19%)
note_trial_decrypting_time_in_ms (64): 82.7 (+252%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
772
772
772

l1_rollup_calldata_gas
6,808 (+1%)
6,784
6,796

l1_rollup_execution_gas
587,289
587,265
587,277

l2_block_processing_time_in_ms
1,360 (-6%)
5,046 (-2%)
:warning: 9,801 (-19%)

note_successful_decrypting_time_in_ms
220 (+1%)
510 (-2%)
966 (+7%)

note_trial_decrypting_time_in_ms
19.1 (+1%)
15.8 (-41%)
:warning: 82.7 (+252%)

l2_block_building_time_in_ms
:warning: 13,088 (+35%)
:warning: 51,043 (+35%)
:warning: 102,726 (+35%)

l2_block_rollup_simulation_time_in_ms
:warning: 12,899 (+36%)
:warning: 50,366 (+35%)
:warning: 101,399 (+35%)

l2_block_public_tx_process_time_in_ms
5,522 (+4%)
21,456 (+3%)
43,163 (+3%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
15,053 (+2%)
28,325 (-2%)

note_history_successful_decrypting_time_in_ms
1,172 (+4%)
2,228

note_history_trial_decrypting_time_in_ms
46.3 (+11%)
76.0 (-4%)

node_database_size_in_bytes
18,677,840
35,033,168

pxe_database_size_in_bytes
29,859
59,414

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
148 (-1%)
44,561
26,424

private-kernel-inner
160 (+3%)
72,188
26,424

private-kernel-ordering
111 (+3%)
51,090
39,297

base-parity
48.3 (-7%)
128
311

root-parity
9.40 (-6%)
1,244
311

base-rollup
:warning: 16,143 (+30%)
110,820
957

root-rollup
48.4
4,551
821

public-kernel-app-logic
86.7 (+7%)
48,151
40,933

public-kernel-tail
124 (+2%)
60,044 (+12%)
7,385

merge-rollup
:warning: 8.67 (-36%)
2,760
957

public-kernel-teardown
82.8 (+6%)
48,151
40,933

public-kernel-setup
81.5 (+5%)
48,151
40,933

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.3 (-7%)
16.5 (-7%)
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.6
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.597 (-7%)
0.511 (-7%)
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
47.9 (-7%)
75.5 (-10%)
244 (-6%)
468 (-7%)
919 (-6%)
1,825 (-10%)
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
96.0
159
543
1,055
2,079
4,127
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.490 (-8%)
0.465 (-10%)
0.444 (-6%)
0.437 (-7%)
0.435 (-6%)
0.436 (-10%)
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
56.3 (-6%)
112 (-7%)
354 (-5%)
689 (-7%)
1,371 (-6%)
2,740 (-6%)
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
105
207
691
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.497 (-7%)
0.504 (-8%)
0.478 (-6%)
0.474 (-7%)
0.475 (-6%)
0.475 (-7%)
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
63.0 (-7%)

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
109

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.550 (-7%)

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
41,005
528,889

Transaction size based on fee payment method

Metric
native fee payment method
fpc_public fee payment method
fpc_private fee payment method

tx_with_fee_size_in_bytes
905
1,161
1,377

Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes
2 new note hashes

tx_pxe_processing_time_ms
1,178 (+2%)
790 (+1%)
3,425 (+1%)

Metric
1 public data writes
2 public data writes
3 public data writes
4 public data writes
5 public data writes
8 public data writes

tx_sequencer_processing_time_ms
482 (+6%)
326 (+6%)
866 (+6%)
413 (+5%)
1,429 (+5%)
480 (+3%)

Looks good, but I'm curious what was the issue that required the clone. Were we modifying the input args?

To be honest I didn't find the exact cause. If we don't take a copy of the inputs then by the time they are used in the prover the call stack is no longer consistent. It fails saying that the public inputs hash is not the same as that at the top of the stack.
The public processor really owns all this data and is modifying it as it needs so I figured the most reasonable thing to do is to take a snapshot of the inputs needed by the prover.


chore: add CI check for #guard in Mathlib

Hopefully will fail until #10772 is merged.

These checks mean that #guard(_msgs) can't even appear in a code block in a comment, right?
I know that commands do register info trees -- could this be a linter instead?
Also, I think the general rule for mathlib has been "no commands starting with # in library files"

Hmm, how do we not already have not already have a linter for "commands starting with #".
This test didn't catch what it was meant to catch anyway. I'm going to close this and let someone else take care of it. :-)


I am unable to install my shopify app on other live stores ,

### I am getting this issue when i try to install this in live store .

**###

And also got this error in my development stores.

**

Please help me its urgent..

I am getting this issue

Please use template.


fixes a problem where calling init.bat /v would not work correctly

This seems to fix a problem where calling init.bat /v directly from any directory would fail to set the %CMDER_ROOT% variable if %ConEmuDir% is also not set (e.g. not using ConEmu with Cmder.)

@daxgames would you also reviw this PR too?

@DRSDavidSoft I cannot duplicate the issue we saw when you ran it, so not sure what happened.  I made additional changes last night.  I now differentiate between verbose "/v" and debug "/d"output.  Could you try again with my code base without your changes and test with both switches.

@daxgames I can not confirm that calling init.bat with /v passed work on my machine, and the reason is quite obvious – the %0 points out to the /v or /d somehow on my machine. (IMO, it's related to the shift making the arguments order go out of the required order.)
This patch fixes the problem though :)
BTW, how to reproduce:

Put init.bat in C:\somedir\cmder\vendor\init.bat
Win+R → cmd and issue: cd /d "D:\Path\to\another\drive\With Spaces\etc"
Issue exactly this command:
C:\somedir\cmder\vendor\init.bat /v

...and you can see the problem.
Note that if you issue C:\somedir\cmder\vendor\init.bat first before issuing C:\somedir\cmder\vendor\init.bat /v, the %CMDER_ROOT% is already defined, so it won't bother with the %~dp0\.. variable.
I hope I've provided an in-depth analysis, let me know if managed to reproduce this with the current commit of init.bat.

@DRSDavidSoft So you are testing the execution if init.bat /d outside cmder.exe and outside conemu.exe.  I was able to reproduce with your steps.
I would have never tested execution of init.bat outside cmder,exe or conemu.exe as it was never designed to be run this way.  You are correct the shift is affecting the setting of cmder_root so I am simply going to move the setting of cmder_root above the command line parsing code which is where it should be anyway.
I am rejecting this PR since it will work by just reordering the original code.

@daxgames thanks for verifying and reordering the  logic, honestly it makes more sense that my patch.
But I want to point out that many resources instruct users to call cmd /c init.bat to run Cmder within VSCode, or other integrated terminals than ConEmu. I personally love Maximus' work, but Cmder technically works just as awesomely with other terminal emulators.
However, the main point is if init.bat works on its own, and we can order it to not have issues with arguments passed, IMHO it's more elegant to have it too.
Thanks for your help!

@DRSDavidSoft Good to know about those other uses.  I have never tried to run it separately.  THanks for being persistent!


S3 promotion: support anonymous authentication

If we don't have AWS credentials (or don't want to use them), we need
to actively specify that rather than attempt credential discovery
which then fails with an error.
Reuse the --use-service-acccount=false flag for this meaning.

When --use-service-account=false (which is the default), we will issue anonymous requests to AWS and ignore any AWS credentials.  This should be sufficient for dry-run, and ensures that dry-run is safe even if manifests are hostile.

/retest
I'm wondering if I ran concurrent e2e jobs, as the failure looks very unrelated


CIV-11929 mediation notification no sanctions

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/CIV-12165
Change description

Added Notify Defendant LR

Before/On Master

After/PR:

Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

https://github.com/hmcts/civil-ccd-definition/pull/3989
combined pr is passing


Fix/multi target

Description
Added back the support for multi-target /scrape endpoint
Fixes #339
Type of change
Please delete options that are not relevant.

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

can anyone fix this? multi target can be a very useful feature...
thanks

can anyone fix this? multi target can be a very useful feature... thanks

Multi target should work on the fork, please try once, we are still testing few things before raising PR to back to main repo

I tested it, it seems to work.

does DSN need to be in the same format as the environment variable? ie. /scrape?target=oracle://user:password@myhost:1521/service
I'm not having luck running mulit target with this currently, it only shows metrics from the primary target

I tested it, it seems to work.

I need to take it back ...

I run the exporter without setting any DSN variable. accessing to /metrics shows as expected oracledb_up = 0
I access http://localhost:9161/scrape?target=oracle://otel@localhost:1521/ORCLPDB1?WALLET=wal and that shows some metrics
I access again /metrics , suddenly this also shows same metrics
I access a dummy /scrape?target=something and this one shows same metrics

so it seems metrics are somehow hijacked by the first instance that works

@lucian-vanghele maybe it is happening because the metrics does not have a database identifier
Testing changes here: #2
Maybe that should solve the issue

I tried it .. seems to work now. However, wouldn't be better to just revert the original code (which by mistake was removed in release 0.5.0)? or the changes were too big? (I must say I didn't check)

Works for me too, although only when using usernames/passwords without special characters.
If I use a container/common user 'C##TESTUSER' and use the same URL encoding as I would for the DATA_SOURCE_NAME C%23%23TESTUSER it doesn't work, same issue if there are special characters in the password.

I didn't try anything special. instead of password I used wallet ..

I didn't try anything special. instead of password I used wallet ..

can u tell me how it dose work? i run in release 0.6.0 with DSN, the Multi target should work just on the fork not in iamseth ,right?

Although I got it to work, I found that too many multi target requests from prometheus crashed the exporter service.
For the databases which I can't install a dedicated exporter on I instead fetch the metrics over a database link and store in a database which has an exporter. I've modified the default exporter SQL so each database is identifiable.

Although I got it to work, I found that too many multi target requests from prometheus crashed the exporter service.
For the databases which I can't install a dedicated exporter on I instead fetch the metrics over a database link and store in a database which has an exporter. I've modified the default exporter SQL so each database is identifiable.

how to go each database is identifiable can u share for me ？

another feature which is no longer working in the iamseth repo is this one which is useful in a dataguard setup.  see 334

I've written some plsql which runs a slightly modified version of the
default metric sql over each database link owned by my prometheus schema.
The sql joins db_unique_name from v$database to identify each database.
Ive created a table and materialized  view to hold each metric result. The
plsql truncates the table, loops through each database link inserting the
result into the table and then refreshes the materialized view. The
exporter then queries each MV (I've edited the default metric file)
On Wed, 3 Jul 2024, 08:19 dragon-jet, @.***> wrote:

Although I got it to work, I found that too many multi target requests
from prometheus crashed the exporter service.
For the databases which I can't install a dedicated exporter on I instead
fetch the metrics over a database link and store in a database which has an
exporter. I've modified the default exporter SQL so each database is
identifiable.
how to go each database is identifiable can u share for me ？
—
Reply to this email directly, view it on GitHub
https://github.com/truemark/oracledb_exporter/pull/1#issuecomment-2205268825,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOBW5DM3EIHY4OGMXYTBGTTZKOQXFAVCNFSM6AAAAABBU5PDQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBVGI3DQOBSGU
.
You are receiving this because you commented.Message ID:
@.***>

another feature which is no longer working in the iamseth repo is this one which is useful in a dataguard setup. see 334

Is this feature including the ASM not available so far  in the iamseth repo?

I tried it .. seems to work now. However, wouldn't be better to just revert the original code (which by mistake was removed in release 0.5.0)? or the changes were too big? (I must say I didn't check)

how did u make it work with any cmd or config？

I tried it .. seems to work now. However, wouldn't be better to just revert the original code (which by mistake was removed in release 0.5.0)? or the changes were too big? (I must say I didn't check)

how did u make it work with any cmd or config？

it is about this fork and the issues I was mentioning here

how dose the issue have been resolved ？however, i access by /metrics or /scrape but also shows same metrics... is that any wrong with it ?
i use one container docker run --env-file,  specific the DSN is about that:
DATA_SOURCE_NAME=oracle://user:pwd@ip:1521/sid
DATA_SOURCE_NAME=oracle://user:pwd@ip:1521/sid
......
my  prom_jobs config  is about that:

job_name: oracledb-exporter
metrics_path: /scrape
static_configs:

targets: ["db1"]
labels:
db1: orcale:://USER:PWS@IP:1521/SID

targets: ["db2"]
labels:
db2: oracle:://USER:PWS@IP:1521/SID
relabel_configs:

source_labels: [address]
target_label: __param_target
target_label: address
replacement: IP:9162

I tried it .. seems to work now. However, wouldn't be better to just revert the original code (which by mistake was removed in release 0.5.0)? or the changes were too big? (I must say I didn't check)

how did u make it work with any cmd or config？

it is about this fork and the issues I was mentioning here

how dose the issue have been resolved ？however, i access by /metrics or /scrape but also shows same metrics... is that any wrong with it ? i use one container docker run --env-file, specific the DSN is about that: DATA_SOURCE_NAME=oracle://user:pwd@ip:1521/sid DATA_SOURCE_NAME=oracle://user:pwd@ip:1521/sid ...... my prom_jobs config is about that:

job_name: oracledb-exporter
metrics_path: /scrape
static_configs:

targets: ["db1"]
labels:
db1: orcale:://USER:PWS@IP:1521/SID

targets: ["db2"]
labels:
db2: oracle:://USER:PWS@IP:1521/SID
relabel_configs:

source_labels: [address]
target_label: __param_target
target_label: address
replacement: IP:9162

Finally，it works now！but the default metrics some sql was incorrect....


Error #01: context canceled

Could you help with the timeout issue, please?
Logs:
2024/01/17 11:24:25 KRAKEND ERROR: [ENDPOINT: /api/endpoint] context canceled
[GIN] 2024/01/01 - 10:00:25 | 500 |          1m0s |        *.*.*.* | POST     "/api/endpoint"
Error #01: context canceled

Timeout in the krakend.json config file:
"timeout": "180s"

It means that the connection has been closed (by the client or by the network). You should check the timeouts on your clients and routers/load balancers

It means that the connection has been closed (by the client or by the network). You should check the timeouts on your clients and routers/load balancers

Thank you very much. We will be check it.


customizing dashboard views

Love the product but to make use of it in a production tool that I'd hand to a client I will need to customize the way the dashboard looks.
I could fork/hack on your Engine and edit it there or through the downloaded gem or maybe try to write in overrides into my app.
I was wondering what is the preferred way you guys do it? Is there a way to pull in the dashboard views into my app? And is there a way to pull in your dashboard scss?

@GrilloPress - glad to hear you're interested in using Storytime. Couple of thoughts:
-Overriding the views would be pretty easy. E.g. to override the post#edit action, you could just stick a file in your host app at: app/views/storytime/dashboard/posts/edit.html.erb. You could do that with any view in the dashboard pretty easily. If necessary, we could add something to our install generator to copy over dashboard views.
-You should be able to override styles in a similar manner. E.g. if you want to override admin styles, you could put a file in your host app at: app/assets/stylesheets/storytime/admin.css.scss and do whatever you want in there. If you want to just tweak minor things, you could copy the source for that file into your host app and make changes.
In order to make the stylesheet override work in development, you'll probably need to have a local copy of the storytime source:
cd /wherever/you/want/storytime/source
git clone git@github.com:FlyoverWorks/storytime.git
bundle config local.storytime /wherever/you/want/storytime/source

I think going with the override route would be much easier/cleaner than forking and changing. Plus, it will be much easier to stay up to date with future releases.
It's also worth noting that we're actively working on a 2.0 release right now. One of the major features is going to be a major overhaul of the dashboard UI. Going to be professionally designed and mobile responsive -- should turn out great.
If you run into any snags with the overrides, feel free to respond here and I'm happy to help out.

thanks for the advice @bcroesch I think i'll go the override route. It did always seem the most sensible approach.
Once again. Lovely product. Really looking forward to seeing it shape up.
I'd love an install generator for the dashboard views and scss. It really aligns with my philosophy of a great Engine. For those learning and using your product for the first few times, let them see it in their app before their eyes. When they get a good grounding in your code and flow, let them keep it out of the app and let them declutter.
That said, i'm just one guy so on the product roadmap I doubt there is much urgent need there :)  and the dashboard redesign I think is a good strategic move for adoption.
I look forward to seeing 2.0

Agree that an install generator is a good idea. Something similar to Devise's rails generate devise:views would make a lot of sense. We'll stick it on the 2.0 roadmap.
Thanks again for checking out Storytime and ping us with any questions/issues!


Update setup.py

Summary of Changes
Update the version.
Tests
What tests did you add or modify and why? If no tests were added or modified, explain why. Remove this line
Documentation
What documentation did you add or modify and why? Add any relevant links then remove this line
CheckList
Make sure you have checked all steps below to ensure a timely review.

[x] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[x] PR includes a summary of changes, including screenshots of any UI changes.
[ ] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public python functions and the classes in the PR contain docstrings that explain what it does

[ ] PR passes all tests documented in the developer guide
[ ] I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message"

Codecov Report

Merging #149 into master will decrease coverage by 10.51%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master     #149       +/-   ##
===========================================
- Coverage   53.13%   42.61%   -10.52%
===========================================
  Files         106       86       -20
  Lines        2650     1760      -890
  Branches      273      197       -76
===========================================
- Hits         1408      750      -658
+ Misses       1213     1007      -206
+ Partials       29        3       -26

Impacted Files
Coverage Δ

amundsen_application/api/mail/v0.py

amundsen_application/api/search/v0.py

amundsen_application/models/announcements.py

amundsen_application/api/announcements/v0.py

amundsen_application/log/action_log_callback.py

amundsen_application/base/base_mail_client.py

amundsen_application/api/__init__.py

amundsen_application/base/base_preview_client.py

amundsen_application/api/log/v0.py

amundsen_application/api/utils/request_utils.py

... and 10 more

Continue to review full report at Codecov.

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


Setup parameters validation range error

Hello,
the validation ranges for the setup parameters are not correct :

SP_SetpointPressurePsi            the range should be 1.0 to 5.5 (instead of 0.1 - 0.6)
RP_PressureFallToRestartPsi     the range should be 0.1 to 1.0 (instead of 0.0 - 0.1)

So these 2 values cannot be updated in Home Assistant.
Can you please check ?

Was already looking into it, as these values have no min or max value specified on my pump (ESybox).
For an ESybox Mini3 I see the following config definition from DAB Pumps:
{
"name": "SP_SetpointPressureBar",
"type": "measure",
"family": "tachimeter",
"group": "Setpoint",
...
"unit": "bar",
"weight": 0.1,
"min": 1,
"max": 5.5,
"groupApp": "Setpoint",
"groupPosApp": 10
},
{
"name": "RP_PressureFallToRestartBar",
"type": "measure",
"family": "graph",
"group": "Setpoint",
...
"unit": "bar",
"weight": 0.1,
"min": 0.1,
"max": 1,
"groupApp": "Advanced",
"groupPosApp": 30
},
So I need to allow the code to work in case there is no min and max specified, but also I might have misinterpreted how min and max work (on the displayed value, not the value corrected with weigt, 5.5 bar is stored as value 55)

Should be fixed now in v2024.05.2
Please let me know if you run into any other issues


AUI-1871 Adding HISTORY.md entry

Just started reviewing :) :octocat: Sent from GH.

Thanks! Pull request merged into liferay/master.


[Improve] refactor clickhouse connector, using Factory to create source/sink

Purpose of this pull request
refactor clickhouse connector, using Factory to create source/sink

Does this PR introduce any user-facing change?
no

How was this patch tested?
using existing test

Check list

[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

Close when this pr merges  https://github.com/apache/seatunnel/pull/6416

good job

@Carl-Zhou-CN PTAL when you have time

@liunaijie , any plan to merge this PR soon? I also noticed your branch name is clickhouse-savemode but it seems that save mode of ClickHouse sink is not in the PR. Look forward to the multi-table sink and auto-create-table in the clickhouse sink

@liunaijie , any plan to merge this PR soon? I also noticed your branch name is clickhouse-savemode but it seems that save mode of ClickHouse sink is not in the PR. Look forward to the multi-table sink and auto-create-table in the clickhouse sink

Hi, this pr has some test cast not pass due to the clickhouse-file connector, and i tested it in my desktop, find this connector has some issue when upgrade clickhouse version.
For the savemode feature, i will continue working on it and ignore the clickhouse-file connector, focus on clickhouse connector

Cool. BTW, based on this clickhouser connector, I created a timeplus-connector for seatunnel and added the basic multi-table and auto-schema-create https://github.com/jovezhong/seatunnel/blob/timeplus/seatunnel-connectors-v2/connector-timeplus/src/main/java/org/apache/seatunnel/connectors/seatunnel/timeplus/sink/client/TimeplusSink.java
The code is not clean enough but works in the happy path.

close it and there has a new pr only update the clickhouse connector not update the file related class https://github.com/apache/seatunnel/pull/7946


Migrate the underlying test framework from kuttl to chainsaw

Description of your changes
This PR migrates the underlying test framework from kuttl to chainsaw. For further details about the design one pager about migration, please see: https://github.com/crossplane/uptest/blob/main/design/one-pager-considerations-for-changing-test-framework-of-uptest.md
This pull request updates our project's testing framework to align with the latest best practices for Kubernetes configurations and resource management. By transitioning from kuttl to chainsaw, we embrace a strategic shift toward advanced testing functionalities. This change requires updates across our configuration and templating setups to optimize our new testing framework.
Updated Testing Files, Templates, and Structure

Transition from kuttl to chainsaw:

Previously, the Apply, Update, Import, and Delete operations were part of a single end-to-end test in kuttl. Now, each operation is treated as a separate test in chainsaw, improving management and isolation. Each test consists of distinct steps, simplifying log tracking. Here’s the new test and step hierarchy:

Apply Test

Run Setup Script
Apply Resources
Assert Status Conditions

Update Test

Update Root Resource
Assert Updated Resource Status

Import Test

Remove State
Assert Status Conditions and IDs

Delete Test

Delete Resources
Assert Resource Deletion

Revamp of Test Templates:

Updated YAML templates to align with chainsaw requirements, ensuring compatibility with the framework’s features.
Removed outdated kuttl specific templates and references, decluttering the test setup.
Merged operation and assertion steps into single files in chainsaw, streamlining test execution.

Directory and Terminology Updates:

Renamed the test directory from kuttl to chainsaw to reflect the new testing framework.

Configuration and Execution Enhancements

New Flags Introduced:

log-collect-interval to set specific intervals for log collection during tests, enhancing debugging and monitoring capabilities.
render-only to render test configurations without execution, useful for verifying setups without running full tests.

Modified Timeout Settings:

Changed the default timeout flag to use Duration type, aligning with Go’s handling of timed durations for improved reliability in test execution timing.

Robust Condition Checks and Cleanup:

Enhanced condition checks and resource cleanup processes to be more robust and error-aware, promoting cleaner and safer test executions.

Logging Improvements

Updated Logging Practices:

Shifted from using kubectl get managed/claim to crossplane beta trace for logging, better integrating with the crossplane ecosystem and providing clearer logs.
The log-collect-interval now defaults to 30 seconds, allowing for flexible and effective log management during tests.

This comprehensive update not only refines our testing processes but also sets a new standard for future developments within our project’s testing practices.
I have:

[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested
Tested locally.

Would it be useful if Uptest supported both KUTTL and Chainsaw for a couple of months to allow users a migration period after a proper announcement?

I personally feel it's okay to break things in this PR as the PR is replacing the underlying framework. We had better release the chainsaw support with a major version bump with proper announcement. My main motivation for suggesting that we don't keep supporting kuttle as an alternative engine in parallel to chainsaw is to keep things simple.

Hi @sergenyalcin,
Could you please include an example uptest invocation with the assumptions about its environment (e.g., crossplane CLI & chainsaw being installed, etc.) in the PR description?

@ulucinar thank you for your detailed review, this is ready for the second cycle.


Breaks without go mod

Since v4, the project is not compiling without go modules, i.e. with the classic GOPATH.
Would be of interest to have it fixed.

I second this...

Is there a way around this?
I assume it's the reason this doesn't work:
import (
	"github.com/aaaton/golem"
	"github.com/aaaton/golem/v4/dicts/en"
)

var lem *golem.Lemmatizer

func init() {
	var err error
	lem, err = golem.New(en.New())
	if err != nil {
		panic(err)
	}
}

and outputs: "panic: language en is not valid".


Separate sync root and web root

At the moment Warden syncs the value of WARDEN_WEB_ROOT into the container. However, what if your project's web root is one level deeper than your project root?
To give an example, I've got an OpenMage installation with the following structure:
.env
vendor
src/app/etc/local.xml

My web root is src, but my project root is /.
If I specify src as the WARDEN_WEB_ROOT, vendor falls outside of it, and I cannot use Composer.
If I specify / as the WARDEN_WEB_ROOT, my base URL needs to become the following: https://app.mysite.test/src/ which is problematic.
--
If this is by design, and the best way to solve this is to include a custom Nginx config, then this would be good to add into the documentation.

Thank you @davidalger for the fast and insightful reply!
In case it's useful for others:
I created a new file .warden/warden-env.yml which is merged with the main docker-compose.yml file (visible by running warden env config). I simply added NGINX_ROOT: /var/www/html/src to the Nginx environment. In the Dockerfile, this is then picked up by the envsubst command that adds the environment variables to a template and outputs it in the final nginx config location.


python:3.9.6-slim

Codecov Report

Merging #62 (4e124f0) into main (662c062) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #62   +/-   ##
=======================================
  Coverage   89.58%   89.58%
=======================================
  Files           7        7
  Lines         787      787
=======================================
  Hits          705      705
  Misses         82       82

Flag
Coverage Δ

unittests
89.58% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


Makefile missing in repository

The Makefile is missing in the repository. Unable to build plugin.

Adopted an overly aggressive .gitignore file, fixed now


new auth token handling

This PR updates authenticated requests. I feel it is important to deprecate AuthenticatedUserRequest because it is misleading. It extracted the email address and user id from the access token which are not alway correct.
It is important to separate the use cases that only need an access token from those that actually need user information from sam. Querying sam for every request is a waste of electricity and is bad for the environment as the majority of api calls don't need that detail.
TokenAuthenticatedRequest example
SamUserAuthenticatedRequest example

While most services should never need to check enabled themselves, I do worry that now SAM clients need to think about if they need to or not. But I see your point that every service will need to check at some point if the user is authorized for an operation or not, and that will (typically) require talking to SAM.

@pshapiro4broad I don't believe thinking is required. Almost all cases ask Sam if a user can do a thing or need to know who the user is in order to operate on some user-private resource. If your use cases are different then certainly follow the least error prone path.

It extracted the email address and user id from the access token which are not alway correct.
AuthenticatedUserRequest.java does not have this assumption. It just presents an authenticated user(e.g. already authenticated by proxy).

The fact that AuthenticatedUserRequest contains user id and email as required fields is an assumption that they are always present. The way we use the existing factory is wrong but I don't want to blindly swap it out for a factory that calls sam when that information is not usually needed. Deprecating the old approach is a good forcing function.

"a factory that calls sam when that information is not usually needed" what is the factory? I don't think ProxyAuthFactory makes SAM call. Is that a new factory we need to add after deprecating opendj?

query is made by Apache proxy

This is part of ongoing work to deprecate opendj and remove these calls from the proxy.
I don't have enough context on this ongoing work(and I don't have access to that doc). After removing that doc, how would Terra force all services to verify user enabled status? Is the new principle: 1: If the service make SAM calls, then SAM will take care of this check 2: Otherwise, the service use SamUserAuthenticatedRequest to check user status themself?

For the case that I want to use user email or id but I don't want to invoke SAM call, shall I still use SamUserAuthenticatedRequest?

yes
In this case, I feel I'd like to use ProxyAuthenticatedUserRequest.

@yonghaoy the ProxyAuthenticatedUserRequest may give wrong information because the email and id may be for a pet and not the user. That is why I deprecated it. Any code that relies on this method is open to bugs where pet service accounts cannot be used to make api calls.
@ddietterich

... the majority of api calls don't need that detail ...
How does this relate to the plan to remove OpenDJ? If the proxy is not verifying that the incoming user is a registered Terra user, then I would think the majority of API calls will need to use the SamUserAuthenticatedRequest version. Do I understand that correctly?

there are 2 main classes of requests: 1) performs some action and asks sam if the user is permitted to do that action or 2) performs some user-private action that does not require a sam check but needs to know who the user is. In the case of 1 the sam permission check will ensure the user is active. In the case of 2 the SamUserAuthenticatedRequest should be used.
This is related to the plan to remove OpenDJ by correcting existing patterns for getting a user's id and email and creating common code to ensure a user is enabled


Test Thread-Safety of add_or_update_normal_file

Description: Write tests that simulate multiple threads calling the add_or_update_normal_file function concurrently. Ensure that the normalStore maintains consistency under concurrent access.
Resources: Use the pytest guide to write tests for thread-safety and locking mechanisms.
Path: twinTrim/dataStructures/fileMetadata.py
Note: Ensure to maintain the file structure as per the existing files and tests, and add these tests.

@Kota-Karthik I would like to work on it. Assign me under GSSOC2024 ext and hacktoberfest.

@tarunkumar2005
Yes,
make sure to create a separate branch before making the necessary changes and retain the folder structure.

@Kota-Karthik there already exists a file on the path you defined :- twinTrim/dataStructures/fileMetadata.py

@tarunkumar2005
That is where the code exists and you need to write tests in a new file named fileMetadata in tests folder

@Kota-Karthik I have completed the tests check i have created the pull request Review it and add labels to the request :- gssoc ext and hacktoberfest.


radare2: 5.1.1 -> 5.2.0

Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 120035 at 20759ed9 run on x86_64-linux 1

3 packages built successfully:

python38Packages.r2pipe
python39Packages.r2pipe
radare2


feat(agent): add browser fingerprint label to http metrics

Description:
This PR adds browser fingerprint label to HTTP metrics

Alternatives Considered (optional):
Link to existing ADR (Architecture Decision Record), if any. If relevant, describe other approaches explored and the selected approach. Documenting why the methods were not selected will create a knowledge base for future reference, helping prevent others from revisiting less optimal ideas.
Checklist:

[ ] My PR follows the contribution guidelines of this project
[ ] My PR is free of third-party dependencies that don't comply with the Allowlist
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked the PR title to follow the conventional commit specification

If it's just for analytic purpose, maybe you can just decode the raw JWT header directly. No need to actually verify token. The sub claim should represent the account in keycloak.


Dropdown component issue - overlapped by other components if close by

components: Dropdown
reactstrap version #7.1.0
import method import {Dropdown, DropdownToggle, DropdownMenu, DropdownItem } from 'reactstrap';
react version #16.4.0
bootstrap version #4.3.1

What is happening?
When I use the dropdown component, it's overlapped by another component if it's close by.
See screenshot:

What should be happening?
The dropdown should not be overlapped by other component.
Steps to reproduce issue

Have components close to where the dropdown is
press dropdown and see how the dropdown overlaps.

Could not reproduce given the reproduction steps provided: https://stackblitz.com/edit/reactstrap-v7-7otafu?file=Example.js
Can you provide more information or minimal sample code showcasing the issue.

Thanks for getting back. I just figured out what the issue was based on your response that it's working on your side. It was another plugin/component that's causing the issue. I will investigate to resolve or contact the plugin owner if I can't resolve.
Closing this issue now.


Tour Step names not updating in the editor window

Our assistant found another minor but annoying issue with the tour editor.
Essentially, the step names are not being toggled in the step customiser section of the editor window. Even after the name has been updated manually. See the screen cast video for a demo of the issue.
https://github.com/user-attachments/assets/e5dd87e4-e63e-4c14-94b1-27f4a8dd52b2

Fixed in v0.43.0


DOC: switch to the "any" role as default role

While I'm at it, I've also added intersphinx support: f34ce213966eb25bbd2e5db7691296d42bd94548

Much improved, thank you very much!
All those :meth: and :class: prefixes had bothered me right from the beginning, but I never ventured deeply enough into Sphinx to figure out a better way of doing things. Thank you for cleaning it up!
Merge when you're ready.

Merge when you're ready.

I don't have the necessary rights to do that, can you please merge it?

I see. Sorry about that.


[BUG/ENHANCEMENT] Coverage tests for HAT/HATR and bug fixes

This PR fixes #154.
Besides, it corrects some typos in the adaptive split nodes where node identifiers were accessed, rather than their content. Incorrect variable naming is also fixed.
Finally, I changed the way Hoeffding Adaptive Tree Regressor monitors its errors using ADWIN. Previously, the errors were calculated using normalized target values and predictions (using the z-score approach, as usually done by the tree regressors). However, as stated in ADWIN's paper, a bounded error metric (w.r.t. its range) is expected. For that reason, I implemented a mechanism to incrementally normalize the monitored error metrics in the [0,1] range.
Thanks, @jacobmontiel, for the suggestion.
Changes proposed in this pull request:

Fix typos and bugs in HAT/HATR.
Make HATR monitor normalized error metrics with ADWIN.
Fixes #154.

Checklist

[x] Code complies with PEP-8 and is consistent with the framework.
[x] Code is properly documented.
[x] Tests are included for new functionality or updated accordingly.
[x] Travis CI build passes with no errors.
[x] Test Coverage is maintained (threshold is -0.2%).
[x] Files changed (update, add, delete) are in the PR's scope (no extra files are included).

Hi @jacobmontiel, thanks for the suggestions. I implemented the required changes. Moreover, I extended the standardization of the constants to the Hoeffding Tree regressors. Let me know if any other changes are required.

Thanks for looking into this @smastelini
The PR is ready.


[WIP] Add BaseAgent class

Added BaseAgent Class as of now. Will add code that will similar to all agents. I just created the basic structure for the class as of now.

@Sharad24 for collect_rollouts() method in VPG, PPO, etc the 2048 number should be replaced by rollout_size right?

Yes, I missed that in my PR. Thanks!

On 24-Jun-2020, at 12:55 PM, Het Shah<EMAIL_ADDRESS>wrote:
@Sharad24 https://github.com/Sharad24 for collect_rollouts() method in VPG, PPO, etc the 2048 number should be replaced by rollout_size right?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/SforAiDl/genrl/pull/178#issuecomment-648645289, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH72FJ44IYE5MMD2WRSEYM3RYGS7HANCNFSM4OFVW2KQ.

Cool I'll make the change in this PR.

Should be changed to batch size.

On 24-Jun-2020, at 1:12 PM, Het Shah<EMAIL_ADDRESS>wrote:
@Het-Shah commented on this pull request.
In genrl/deep/agents/vpg/vpg.py https://github.com/SforAiDl/genrl/pull/178#discussion_r444704664:

   # what  is 256

     for rollout in self.rollout.get(256):

what is this 256? Is it the update interval?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/SforAiDl/genrl/pull/178#pullrequestreview-436399651, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH72FJZS3PODB5BMQBBTO5TRYGU6HANCNFSM4OFVW2KQ.

Is it actor_batch_size?

@Sharad24 Can you check the ppo and vpg implementation once. I can't think of any other stuff that we can abstract.

OnPolicy is done majorly. It passes tests as well. Will move to OffPolicy.

Also, were you thinking about doing #152 ? If not, I guess the issue can be closed ig.

Added **kwargs. Check if it is fine @Sharad24 @ajaysub110

Codeclimate Issues are more or less fixed now.

@ajaysub110 Do you have time to review once?

It is showing build canceled, because of the docs. :(

Restarted the build

Can you rename base_class.py to base.py and move it to agents/, probably makes more sense there.

Have you tried training the algos once? For onpolicy trainer, these worked for instance -

PPO w/ CartPole, Lunarlander, Acrobot
VPG w/ CartPole
A2C w/ CartPole, Acrobot

I think I can, but only a little later if that's okay.
On Jun 27 2020, at 2:43 pm, Sharad Chitlangia<EMAIL_ADDRESS>wrote:

@ajaysub110 (https://github.com/ajaysub110) Do you have time to review once?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (https://github.com/SforAiDl/genrl/pull/178#issuecomment-650528657), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AGQWIY7WUQSU6UFCPGCW4WDRYWZ4HANCNFSM4OFVW2KQ).

No problem, nature boi

On 27-Jun-2020, at 6:02 PM, Ajay Subramanian<EMAIL_ADDRESS>wrote:
I think I can, but only a little later if that's okay.
On Jun 27 2020, at 2:43 pm, Sharad Chitlangia<EMAIL_ADDRESS>wrote:

@ajaysub110 (https://github.com/ajaysub110) Do you have time to review once?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (https://github.com/SforAiDl/genrl/pull/178#issuecomment-650528657), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AGQWIY7WUQSU6UFCPGCW4WDRYWZ4HANCNFSM4OFVW2KQ).

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/SforAiDl/genrl/pull/178#issuecomment-650554658, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH72FJ65D5C4WVVSRUUG3SDRYXRGHANCNFSM4OFVW2KQ.

Can you rename base_class.py to base.py and move it to agents/, probably makes more sense there.

Yea I'll do this.

Have you tried training the algos once? For onpolicy trainer, these worked for instance -

I checked CartPole for every agent for 10 epochs. I can't really train for longer epochs though my ubuntu is a bit fucked, it hangs and I have to reboot. Can you check and let me know if it doesn't train. :(

@ajaysub110 Are you going to review?

Already had a look yesterday. Sorry, I had approved on the group

I'll resolve the merge conflicts

I did the logger thing here only wasn't a big change.

Ready to merge.

As for the max_ep_len, I think it would be better if I add it along with my PR as TimeLimit has only been implemented in that.

Yea cool. I am not making this change here then.

Awesome, merging.


Ensure relative linking works between different markdown and mdx documents

[ ] find and document examples of documents with relative links in different repos
[ ] configure markdown processing or html base tags to ensure linking works between anchor tags, img elements, etc

closing this as it's a duplicate of: https://github.com/onflow/next-docs-v1/issues/15 and https://github.com/onflow/next-docs-v1/issues/91


Shared: Add useApi hook

Hotels: Refactor HotelsContext to be functional component.
Use new useApi with dateFactory to separate checkin, checkout
logic from the render of the provider

@RobinCsl 🚀


Component: CTA - Video button is smaller compared to second button

Detailed description
URL: https://ibmdotcom-react-staging.mybluemix.net/
On iPhone - Safari & chrome browsers
Issue : Video button is smaller compared to another button
Steps to reproduce the issue

Open react staging link on iPhone and navigate to CTA
In Knobs, change button 1 to video
Now verify the button sizing.

Additional information

This bug is similar to (#3708).  Same developer may want to pick up both.


[comp:spin] loading展示异常

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Reproduction link
https://codesandbox.io/s/kiftu
Steps to reproduce
官网上的spin demo展示异常

What is expected?
展示正常
What is actually happening?
展示异常
Environment Info
 Browsers:
    Chrome: 97.0.4692.99
    Internet Explorer: 11.0.17763.1

spin 组件正在重构，参见 #740


Add warnings to the tracker selection page

need to review this when i have time, wait for me :P

glad to know :3

Made some changes to the positions of the circles (lower arms and upper legs a bit higher)

Can I commit directly @loucass003 ? You didn't change the lower arms' positions, so I can't just suggest changes on that :p

Made some changes to the positions of the circles (lower arms and upper legs a bit higher)  Can I commit directly @loucass003 ? You didn't change the lower arms' positions, so I can't just suggest changes on that :p

yes


Issue: Is it possible to use a HF LLM using Conversational Retrieval Agent?

Issue you'd like to raise.
No response
Suggestion:
No response

This PR add Hugging Face models as a new Chat Model:
https://github.com/langchain-ai/langchain/pull/10094


Hacktober-accepted label

Hello! How are you @SimonWaldherr ?
Just asking if you can later add the "hacktober-accepted" label in the merged PRs in Hacktober. Don't know if you're validating it, but just a reminder.
Best regards.

I'm fine too, thank you for asking.
Sure, i read it wrong, sorry for the trouble !
Issue done!


Fix for 'ERR max number of clients reached'  MasterListener Thread death

Fixes #1329
Added missing @Override annotations
Made the logger final static
As JDK is now 1.7 , Jedis instance is now wrapped in try-with-resources block

As JDK is now 1.7 , Jedis instance is now wrapped in try-with-resources block

master version is JDK 1.7 but keep in mind that this needs to be downmerged to 2.8 and 2.9 as well so it's better to use the old way

@sheinbergon change seems ok, but can you explain a bit what was happening to understand the scenario?. Do you think it's possible to write a test case for this fix?

@marcosnils  see my comment about jdk 1.7 in the line note

@marcosnils  the scenario in general is - every situation that produces an exception which is not JedisConnectionException in the MasterListener Thread causes it to die and the whole functionality of waiting for master changes to stop working in a live production code.  The more specific scenario is due to client connection overload ( too many cilient connect to the sentinel ) and JedisDataException is thrown).
Jedis Exceptions are unchecked by design which is a valid design method just as choosing the other way around . Should they've not been that way , this would've been avoided at code writing time :hammer:
There-for I don't think this specific scenario has a relevant test case , in a more general notion , we should make sure the MasterListener never dies ( maybe place a watch dog on top of it ) because if it does die production for whatever reason , It's bad

@sheinbergon @HeartSaVioR @xetorthio LGTM.
Once another contributor approves we can merge.

Thanks for taking care of this issue. It is important to fix it.
Now even though I like your changes, the only one relevant to fix this issue is catching JedisException instead of JedisConnectionException. I recommend splitting this PR into 2.
Another thing is the lack of testing. As you said, this is an important issue, and it deserves a test. Regardless of any design decision we made, we should try to find a way to test this. There is already a list of steps to reproduce the issue. That's a good start.

Another thing is the lack of testing. As you said, this is an important issue, and it deserves a test. Regardless of any design decision we made, we should try to find a way to test this.

This is a bit tricky to test as we need to do two things which are not easy.
1 - Force redis to return an error when MasterListener initializes
2 - Found a way to check that the MasterListener is currently down. We don't have API's for that ATM.

@xetorthio @marcosnils  I'll see what I can do about testing . I'll update here in a few more days

@marcosnils  I'll rework on this to include some tests


🔗 mdx linking best practices

Doing this (bad) v. this.

Doing [this] (bad) v. [this](https://good.com).

[this]: https://stellar.org/protocol/sep-10


no implicit conversion of nil into String (TypeError) with 1.2.0

Hi, Combustion is great. Thanks for creating it!
I just upgraded from 1.1.2 to 1.2.0 and am running into an error - no implicit conversion of nil into String (TypeError). It's happening with Rails 5.0, 5.1, 5.2, and 6.0 (haven't tested other versions). Here's the stack trace:
6: from /home/travis/.rvm/gems/ruby-2.6.3/gems/combustion-1.2.0/lib/combustion.rb:35:in `initialize!'
5: from /home/travis/.rvm/gems/ruby-2.6.3/gems/combustion-1.2.0/lib/combustion.rb:35:in `each'
4: from /home/travis/.rvm/gems/ruby-2.6.3/gems/combustion-1.2.0/lib/combustion.rb:35:in `block in initialize!'
3: from /home/travis/.rvm/gems/ruby-2.6.3/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:291:in `require'
2: from /home/travis/.rvm/gems/ruby-2.6.3/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:257:in `load_dependency'
1: from /home/travis/.rvm/gems/ruby-2.6.3/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:291:in `block in require'
/home/travis/.rvm/gems/ruby-2.6.3/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:291:in `require': no implicit conversion of nil into String (TypeError)

Ref: https://travis-ci.org/github/ankane/lockbox/jobs/677089603

Thanks for sending this through - seems like it's from you specifying active_job as one of the components to load, but Combustion hasn't had that added in (not for any good reason, just hadn't got around to it!). I'll try to get that fixed later today.

This also means that previously Combustion handled components that weren't explicitly specified, and that does feel like the right way to do things, so I'll try to have the code return to that behaviour.

Just pushed v1.3.0 which includes explicit ActiveJob support (along with ActionCable, ActionText and ActionMailbox, which also hadn't previously been explicitly loaded). Hopefully this gets your build passing again :)

1.3.0 works great - thanks for the quick response!


Monotonic Constraints - Only Partially Working

Full code can be found here .
Basically, I have two features, x_1 and x_2. I constrain x_2 to be monotonic. I take an example
(a, b) that is classified as "c".  Then I create another example, (a', b). If monotonicity works, then example (a',b) should be classified as "c" as well. But that's not necessarily the case.
I know that my "monotonic" classifier is different from an unconstrained classifier because it is more likely to output "c", but still it doesn't satisfy the above logic.
Any thoughts on what is happening here?

why should example (a',b) be classified as "c"?

You constrained x_2 to be monotonic, not x_1. So we don't know how (a, b) and (a', b) are related, since we only changed x_1.


Earley predict on complete input

An original (maybe overeager!) optimization was included with Earley parsing. If there was no remaining input text, then no more predictions from the grammar were attempted. In most cases, this saves Earley some work. But the BNF crate supports empty production rules. This invalidates this optimization, because an empty production may still be successful even with no remaining input text.
This commit only removes this optimization built on that false assumption. It would be possible to reintroduce this improvement, but only for grammars without any empty productions.
Closes #108

Coverage increased (+0.04%) to 92.873% when pulling e31217e473c0907cc0c12c076159f25bd1ee1613 on fix-empty-production-parsing into e5a894b57683d010ae6f5f69bccabd5b23bfa471 on main.


address.GenerateFullPayloadAddress deprecated

       // Generate private key
	keyString, err := internalUtils.GeneratePrivateKey(32)
	if err != nil {
		return "", "", err
	}

	systemScripts, _ := utils.NewSystemScripts(client)

	key, err := secp256k1.HexToKey(keyString)
	if err != nil {
		return "", "", err
	}

	lock, _ := key.Script(systemScripts)
	addr, _ := address.GenerateFullPayloadAddress(address.FullTypeFormat, network, lock)

What method I should change my logic to?

By GenerateBech32mFullAddress()?

@x777 Yes, use GenerateBech32mFullAddress.

Can you please ask somebody to update faucet service to support address for such format?
I tried to generate this new method address, but faucet say that this address not valid:
ckt1qzda0cr08m85hc8jlnfp3zer7xulejywt49kt2rr0vthywaa50xwsqt0kkpq6akwcnmpqzcdrql5uz6fgtnqnrgqme4tg
But with blockchain it works fine.

Sorry for delay reply. Using this method to convert it to short address, and then use it to get token from faucet.
shortAddress, err := ConvertToShortAddress("ckt1qzda0cr08m85hc8jlnfp3zer7xulejywt49kt2rr0vthywaa50xwsqt0kkpq6akwcnmpqzcdrql5uz6fgtnqnrgqme4tg")


Feature: Send out event reminders to people who volunteer for events

From this Slack post
4. Will there be reminders sent out of times that volunteers have signed up for (manual or automatically)?

The way I would try to do this is by sending out calendar event emails to volunteers automatically whenever they sign up for an event. This could integrate with their email application (Gmail, Outlook, etc) to give them reminders. Other solutions, like sending an email to volunteers a certain amount of time before an event happens, are somewhat harder to do.

Probably to be implemented using icalendar attachments. Going to try to avoid using background jobs for this at this point.

Done as of 7e47385448843fea22b3fc99405b64bf82cba08a

I think we still need to add a calendar link for iCal or GCal so that people can be reminded of their session

I spent some time trying to attach ICS files to outgoing emails, but I wasn't able to figure out how to do this through the resend API. What I'm thinking now is that we can generate files for each user's schedule of registered events, serve them off a resource route, and link to them from the emails. Not sure what this will take or if there are better ways to do this.

Marking this as P0 because this is needed to have feature parity with the old solution currently in use

This is fixed


Update Gradle wrapper to 8.8

Update Gradle wrapper to 8.8

💚 All backports created successfully

Status
Branch
Result

✅
7.17

Questions ?
Please refer to the Backport tool documentation


Blank screen when logging in

No options available when logging in.
This should probably not be empty authUI.providers = [] in presentLoginController in ProfileViewController
Fixed by adding FUIEmailAuth()
authUI.providers = [FUIEmailAuth()]
Also need to update podfile to contain pod 'FirebaseUI/Email'

Fixed in 8c432c1da4177df887871db335b4fb234430ac85.


add model tutorial

I would love to have a tutorial on how to add an existing model from candle examples.
For example, I want to add clip, starcoder and rwkv, to name a few.

I'm not exactly sure what that would involve for the general case. Kalosm is a collection of candle models and helpers on top of those models. The helpers built on top of candle models could look very different depending on the models. There is very little in common between voice activity detection and text generation
If you want to add a language model so you can use it with the structured generation utilities, you need to implement the traits from kalosm-language-model. For reference the implementation for LLama is here: https://github.com/floneum/floneum/blob/main/models/kalosm-llama/src/language_model.rs, https://github.com/floneum/floneum/blob/main/models/kalosm-llama/src/session.rs#L13-L40, https://github.com/floneum/floneum/blob/main/models/kalosm-llama/src/model.rs#L25-L71


Json schema indicates ports as number

There are a number of locations in the schema where 'number' is used rather than 'integer' in the port bindings:

service.ports.port
service.ports.targetPort
$defs.httpProbe.port

This usually doesn't show up as a problem but it might when validation allows port numbers like 33.3333 to pass validation, but may cause failures when converted into docker compose, helm, or other destination container types.
I'd like to propose that we change these to integers!

Actually this was fixed already in d5df881c86520cdfcd38ab06f7a8704185ea14b4.


Do not block synchronous hardware-generated signals in pc-linux BSP

As of OSAL 4.1, all signals are blocked during execution of the OS_Application_Startup() call, then unblocked before entering the wait loop.
There is some valid logic behind this --

By definition, a signal is directed to a process, not a thread.  In a multi-threaded process, each thread gets its own signal mask and "normal" signals may be delivered to any thread within that process that has the signal unmasked.
By masking all signals during OS_Application_Startup(), any threads created during this time will automatically inherit the mask and therefore have all signals blocked.
Signals will then be unblocked only in the original (main) thread, therefore any signals generated will be delivered only to this thread.

The issue here is that some signals on Linux are generated by the underlying hardware and the kernel forwards these (synchronously) to the specific thread that was executing on the CPU when the actual signal was triggered.
The set of hardware-generated signals: SIGSEGV, SIGILL, SIGBUS, SIGFPE should NOT be blocked at any time by any thread.
For instance, if a thread causes a segmentation fault by using a bad pointer while SIGSEGV is blocked, the thread will continue running, but results are undefined.

Imported from trac issue 28.  Created by jphickey on 2015-03-18T12:45:46, last modified: 2015-11-20T16:22:16

Trac comment by jphickey on 2015-03-18 13:28:18:
== Additional issue: Realtime signals ==
In the same realm of signal blocking/unblocking - Linux provides several realtime signals for general purpose use by RT applications.  These will never be generated by the kernel and will only be sent to a process if explicitly requested by the user or sent from another process via "kill".
The problem is: the global "unblock" which is done after OS_Application_Startup() also unblocks these RT signals from the main thread.  This prevents the intended use of these signals if the OSAL/BSP/application had actually designated a thread to receive these signals.
To allow application use of these "RT" signals, they should be blocked by default for all threads including the main thread, so that the implementation is free to unblock them in a secondary thread if desired.
It is OK to leave these blocked in all threads if nothing uses them - they are not delivered unless asked for.

Trac comment by jphickey on 2015-03-18 23:18:29:
This is ready for review, and a relatively straightforward fix.
Branch "trac-28-fix_linux_signal_blocking", commit [changeset:85f586b]
This simply unblocks the hardware-generated signals all the time, and blocks the RT signals all the time so the user-created threads can use them.

Trac comment by jphickey on 2015-04-08 17:13:16:
Setting back to in_work, as I found a problem with the signal blocking as done here when running with the posix OS timers; these are now using RT signals rather than SIGALRM as had been done in a prior OSAL version.

Trac comment by glimes on 2015-05-18 20:24:58:
Recommend accept, based on commit [changeset:ef0726a].

Trac comment by jphickey on 2015-04-14 13:10:38:
The timer issue described earlier is actually resolved as part of Trac #17 -- see commit [changeset:ad447ab] for the specific fix for this.
This commit has been rebased to the (unapproved) 2015-04-14 baseline which includes the above changeset.  With this baseline, all unit tests PASS as they should.
The new commit for review is [changeset:bd89ab0]
In addition to unblocking the signals described in the ticket summary, this also moves the unblocking logic from the BSP and into OS_API_Init().  The signal masking requirements in this case are dictated by the operating system, not the specific board.  Putting the code here has the benefit of catching all users; masking does not need to be duplicated in pc-linux, pc-cygwin, mac-osx, or the cFS PSP, and they will all be consistent.

Trac comment by acudmore on 2015-06-01 13:58:50:
Recommend accept.

Trac comment by sduran on 2015-06-01 12:09:26:
Recommend accept.  Will need to make the same changes made in bsp/pc-linux/src/bsp_start.c, in the pc-linux PSP cfe_psp_start.c file.

Trac comment by jwilmot on 2015-06-30 11:26:21:
Recommend accept

Trac comment by jphickey on 2015-06-16 16:45:39:
== CHANGE SET HAS BEEN REBASED ==
To allow this change set to move forward I have rebased it to the latest {{{development}}} branch that was just approved during the 2015-06-16 CCB meeting.
Reviews should be based on commit [changeset:3e05c66]
The prior commit (in [comment:7]) is based off a merge that included #17 but this is still in a state of flux.  Please disregard prior commit IDs listed in this thread.  Note that the //content// is identical between these commits, the only change is where it lies within the git history.

Trac comment by glimes on 2015-06-30 14:40:55:
CCB approved.


JAX implementation of emcee

Greetings!
I've ported a subset of emcee functionality to the NumPyro project under the sampler name AIES.
(For the uninitiated, NumPyro uses JAX, a library with an interface to numpy and additional features like JIT compiling and GPU support, in the backend. The upshot is that if you're using currently using emcee, switching to NumPyro may give you a dramatic inference speedup!)
I've tried my best to match the existing API. You can use either the NumPyro model specification language
import jax
import jax.numpy as jnp

import numpyro
from numpyro.infer import MCMC, AIES
import numpyro.distributions as dist

n_dim, num_chains = 5, 100
mu, sigma = jnp.zeros(n_dim), jnp.ones(n_dim)

def model(mu, sigma):
    with numpyro.plate('n_dim', n_dim):
        numpyro.sample("x", dist.Normal(mu, sigma))

kernel = AIES(model, moves={AIES.DEMove() : 0.5,
                            AIES.StretchMove() : 0.5})

mcmc = MCMC(kernel,
            num_warmup=1000,
            num_samples=2000,
            num_chains=num_chains,
            chain_method='vectorized')

mcmc.run(jax.random.PRNGKey(0), mu, sigma)
mcmc.print_summary()

or provide your own potential function.
def potential_fn(z):
    return 0.5 * jnp.sum(((z - mu) / sigma) ** 2)

kernel = AIES(potential_fn=potential_fn,
              moves={AIES.DEMove() : 0.5,
                     AIES.StretchMove() : 0.5})
mcmc = MCMC(kernel,
            num_warmup=1000,
            num_samples=2000,
            num_chains=num_chains,
            chain_method='vectorized')

init_params = jax.random.normal(jax.random.PRNGKey(0),
                                (num_chains, n_dim))

mcmc.run(jax.random.PRNGKey(1), mu, sigma, init_params=init_params)
mcmc.print_summary()

Hope this is helpful to some folks!

Very cool! Thanks for sharing.

@amifalk Do you have some idea of the speedup ?

It depends on how many chains you run, whether or not you have a gpu, the amount of native python code in your model, etc., but it can often be a few orders of magnitude faster.

@amifalk Is the functionality of emcee to calculate and store additional data for each step supported? In emcee you can return a tuple in the potential_fn, and the rest is handled mostly automatically. I found the get_extra_fields function in numpyro, but I am not sure how to generate these extra fields.

get_extra_fields currently only allows you to extract internal metadata generated by the sampler at each step. If want to access some intermediate value of your likelihood function, you can recompute it after the run.
By the way, the Pyro forum is a great place to ask these kinds of questions.


Added dependabot.yml for version updates

What
Adding base config for dependabot.yml, which enables automatic PRs for dependency version updates through Dependabot. This base config sets version updates to run on a weekly schedule, groups PRs for version updates according to major vs minor/patch updates, and sets max PRs that Dependabot can create for version updates  per package-ecosystem.
But if you would like, several config options can be added to dependabot.yml as per configuration-options-for-the-dependabot.yml-file to customize version updates, such as:

Group PRs for version updates by different criteria
Set dependency-type option in allow option to all for enabling version updates for both direct and indirect dependencies (as well as prod and dev dependencies). By default, PRs for only updating direct prod+dev dependencies versions are created.
Set reviewers for Dependabot version updates PRs
Etc.

Also, automatic PRs for security updates through Dependabot are already enabled through a global setting. PRs for security updates will be grouped as much as possible across directories and per ecosystem through the global setting (grouping-dependabot-security-updates). But dependabot.yml can also be used for more granular security updates settings in addition to version updates (some of the options in dependabot.yml are shared across security and version updates), such as:

Grouping security updates according to custom criteria: overriding-the-default-behavior-with-a-configuration-file
Only allowing automatic PRs for security updates for certain dependencies by configuring allow directive to a certain value such as production, development, direct, indirect. By default, security updates are applied to all dependencies (direct, indirect, production, development).
Etc.

Why
To enable using the latest package versions, and provide a way to customize Dependabot security updates PRs.
Known limitations
N/A

Preview is available here:http://stellar-demo-wallet-client-pr356.previews.kube001.services.stellar-ops.com/


[FLINK-13620][Tests] Update FlinkKafkaProducerMigrationTest to restore from 1.9 savepoint

##What is the purpose of the change
This pull request updates FlinkKafkaProducerMigrationTest to restore from 1.9 savepoint
Brief change log

Generated binary snapshot file
Updated migration version

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

cc @tillrohrmann

@yanghua I think we should add both versions MigrationVersion.v1_8 and MigrationVersion.v1_9 to the array list.

@tillrohrmann Sorry, my mistake. I misunderstood your first comment. Have updated the PR.