(python): Allow for Props classes to be passed into construct constructors

In other languages, the properties for an L2 construct are encapsulated in a Props class, and passed into the constructor of that class.
For example, to create a lambda Function you pass in an instance of FunctionProps.
However for Python, the constructor for Function takes all the properties as named parameters. In the generated source code, an instance of FunctionProps is constructed from those named parameters. However it is not possible to use an instance of FunctionProps to construct a Function.
Allowing for props to be provided either using the current method, or by providing an instance of the Props class would unlock some use cases.
Use Case
My use case is that I'm trying to build a library of standard constructs for my team's use. In particular, I am creating standard Cloudwatch definitions for use across our applications.
I want our alarms to be generated based on the attributes of the constructs being monitored. For example, for Lambda's, I want an alarm that fires if execution durations are reaching 90% of the handler timeout. For Elasticsearch domains, I want to know the EBS volume size so I can know when disk space is less than 5% of the volume size.
The actual CDK constructs themselves, aws_lambda.Function, aws_elasticsearch.Domain and so on, are not suitable for this because they do not expose all their properties to be publicly read.
The Props classes would be ideal for this. I could configure my CDK construct with an instance of a Props class, and then also pass that into my custom constructs.
I could use this solution today with another language; this limitation only exists in Python.
Proposed Solution
Because the Python classes are generated, it shouldn't be too difficult to add an overload in a backwards compatible fashion. Simply generate an additional keyword argument called props for every CDK L2 construct, and allow construction either using the existing keyword argument, or by providing a Props class to props. I see usage looking like:
        lambda_function_props = aws_lambda.FunctionProps(
            handler="index.handler",
            runtime=aws_lambda.Runtime.PYTHON_3_9,
            code=aws_lambda.Code.asset("lambdas/module"),
        )
        lambda_function = aws_lambda.Function(
            scope=self,
            id="ElasticsearchIndexManagerFunction",
            props=lambda_function_props,
        )

Which would then allow my reuse of the properties elsewhere.
        lambda_alarming = CustomLambdaAlarmingConstruct(
            scope=self,
            id="CustomLambdaAlarmingConstruct",
            lambda_function_props = lambda_function_props,
            alarm_topic= alarm_topic,
        )

Other
The one potential issue I see here is that there'd need to be no conflicts with the props keyword within the Props classes; hopefully that's a reserved word as scope and id clearly must be.

[ ] :wave: I may be able to implement this feature request
[ ] :warning: This feature might incur a breaking change

This is a :rocket: Feature Request

This would be very helpful.  We internally implemented the idea of secure properties from this RFC. I realized this too late because I hadn't tried it in Python until adoption was already pretty high internally.  The usage for Python isn't ideal:
compliance_queue_props: QueueProps = Sqs.queue(self)
queue = Queue(self, "Resource", **compliance_queue_props._values)

It's been a while, but IIRC, you have to use ._values otherwise it'll pass in other fields that aren't properties of Queue.  This all works fine though in TypeScript since properties are just interfaces/objects.


correct xrefs in pr-template.md

After https://github.com/keptn/lifecycle-toolkit/pull/1906 is merged, need to modify the .github/PULL_REQUEST_TEMPLATE/pr-template.md file to link to the Contrib Guide rather than the CONTRIBUTING.md file.

Please assign this task to me. I would like to work on it

i'd like to work on this.


Model,JSON and request

 Quality gate: Failed
49 Issues

 2 Vulnerabilities
 12 Code issues
 35 Anti-patterns

Details


Improvement datepicker

For choosing not a exact date, but only a year, the button at the top has to be pressed.  It should also be possible to type it in manually.

Thank you! The datepicker was listening to the wrong event. Should be fixed in https://github.com/KorAP/Kalamar/commit/d5620d4b1563e52956eadf7cd468d609e07ae49b .


Java bindings: make final jar publishable

This will allow to run ./sbt publish-local to get latest version of enry-java with native dependencies and JNI installed on local machine.

Can not add reviewers in Github UI
\cc @abeaumont @erizocosmico for a review

History re-written, review addressed in b73364d

Thanks @bzz !

Thank you for the prompt feedback!


implement explainable.ops.consequent_differs

Before soft_eq and soft_neq are implemented, tested, experimented with, the original functionality of consequent_differs needs to be refactored into the new explainable module, to reach the stage at which notebooks can be merged and be in presentable shape even before further moves with the soft version are made.

@rfl-urbaniak are you going to create new issues for implementing soft_neq and updating consequent_differs, or should I leave this one open?

@eb8680,  I opened a new one, #455 , so I'm closing this one.


fix for returning incorrect builder in hybrid relations

@jenssegers @Tucker-Eric
Commit 266305caeed70cf8ee787bcd0140c9fca2f0bcd6 introduced a bug when using HybridRelations in combination with e.g. raw methods. The newEloquentBuilder method always returned a Illuminate\Database\Eloquent\Builder but for Jenssegers\Mongodb\Eloquent\Model models it should return a Jenssegers\Mongodb\Eloquent\Builder.

@jenssegers Sorry for the failed test, I have fixed the CI and now it passes. I would be obliged if you could merge this :)


CPU Usage Constantly High

VS Code Version: 1.53.1
OS Version: CentOS Linux release 7.9.2009 (Core) (Linux x64 3.10.0-1160.15.2.el7.x86_64)

Steps to Reproduce:

Launch Code
Monitor CPU usage

Does this issue occur when all extensions are disabled?: Yes

Never noticed this before, but within the last few weeks, CPU usage on a code process is constantly around 104%.  Uninstalled all extensions, run with extensions disabled.  Launch the app with nothing open, and the process instantly pegs.
PID points back to process:
code --inspect-port=0 /usr/share/code/resources/app/out/bootstrap-fork --type=extensionHost
code --status:
(electron) Sending uncompressed crash reports is deprecated and will be removed in a future version of Electron. Set { compress: true } to opt-in to the new behavior. Crash reports will be uploaded gzipped, which most crash reporting servers support.
[14269:0210/132134.727935:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
Version:          Code 1.53.1 (5d424b828ada08e1eb9f95d6cb41120234ef57c7, 2021-02-08T23:30:54.166Z)
OS Version:       Linux x64 3.10.0-1160.15.2.el7.x86_64
CPUs:             Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12 x 4099)
Memory (System):  31.09GB (3.61GB free)
Load (avg):       1, 2, 2
VM:               0%
Screen Reader:    no
Process Argv:     --disable-extensions --no-sandbox --crash-reporter-id 59f1f730-4354-4020-9f88-fded6772a546
GPU Status:       2d_canvas:                  enabled
                  gpu_compositing:            enabled
                  multiple_raster_threads:    enabled_on
                  oop_rasterization:          disabled_off
                  opengl:                     enabled_on
                  protected_video_decode:     unavailable_off
                  rasterization:              disabled_software
                  skia_renderer:              enabled_on
                  video_decode:               disabled_software
                  vulkan:                     disabled_off
                  webgl:                      enabled
                  webgl2:                     enabled

CPU %	Mem MB	   PID	Process
    0	    64	 12548	code main
    0	     0	 12570	   zygote
    0	    32	 12620	     gpu-process
    0	     0	 12571	   zygote
    0	    32	 12635	   utility
    0	    95	 12646	   window (Welcome - Visual Studio Code)
    0	    64	 12720	   shared-process

Thanks in advance!

Can you provide the output of code --verbose

code-verbose.txt

Error: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /usr/share/code/resources/app/node_modules.asar.unpacked/vscode-sqlite3/build/Release/sqlite.node)
    at process.func [as dlopen] (electron/js2c/asar_bundle.js:5:1812)

This is side-effect of drop in support for your OS with 1.53 more details in https://github.com/microsoft/vscode/issues/115784 and workarounds are also mentioned there to get these native modules working again.

Got it, thank you!


[Bug] [Zeta] java.lang.NumberFormatException: For input string

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
When reading and deserializing a data file, it can’t  split based on the delimiter.
SeaTunnel Version
seatunnel 2.3.3
hive 2.3.9
hadoop3
SeaTunnel Config
source {

  Hive {
    table_name = "tpch.test2"
    metastore_uri = "thrift://xxx:9083"
    hdfs_site_path = "/usr/local/apache-seatunnel-2.3.3/hadoop_config/hdfs-site.xml"
    hive_site_path = "/usr/local/apache-seatunnel-2.3.3/hadoop_config/hive-site.xml"
    kerberos_principal = "hdfs/xx@TEST"
    kerberos_keytab_path = "/etc/security/keytabs/hdfs.keytab"
  }

sink {

  Doris {
    fenodes = "localhost:8031"
    username = root
    password = "xxx"
    table.identifier = "seatunnel.test2"
    sink.label-prefix = "hive-doris"
    #sink.enable-2pc = "true"
    sink.enable-delete = "true"
    doris.config {
      format = "csv"
      column_separator = ","
    }
  }

Running Command
bin/seatunnel.sh -c config/hive2doris.config -e local

Error Exception
Exception in thread "main" org.apache.seatunnel.core.starter.exception.CommandExecuteException: SeaTunnel job executed failed
	at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.execute(ClientExecuteCommand.java:191)
	at org.apache.seatunnel.core.starter.SeaTunnel.run(SeaTunnel.java:40)
	at org.apache.seatunnel.core.starter.seatunnel.SeaTunnelClient.main(SeaTunnelClient.java:34)
Caused by: org.apache.seatunnel.engine.common.exception.SeaTunnelEngineException: org.apache.seatunnel.connectors.seatunnel.file.exception.FileConnectorException: ErrorCode:[COMMON-01], ErrorDescription:[File operation failed, such as (read,list,write,move,copy,sync) etc...] - Read data from this file [hdfs://managed/hiveseatunnel/tpch.db/test2/testcsv.csv] failed
	at org.apache.seatunnel.connectors.seatunnel.file.source.BaseFileSourceReader.pollNext(BaseFileSourceReader.java:70)
	at org.apache.seatunnel.engine.server.task.flow.SourceFlowLifeCycle.collect(SourceFlowLifeCycle.java:150)
	at org.apache.seatunnel.engine.server.task.SourceSeaTunnelTask.collect(SourceSeaTunnelTask.java:95)
	at org.apache.seatunnel.engine.server.task.SeaTunnelTask.stateProcess(SeaTunnelTask.java:168)
	at org.apache.seatunnel.engine.server.task.SourceSeaTunnelTask.call(SourceSeaTunnelTask.java:100)
	at org.apache.seatunnel.engine.server.TaskExecutionService$BlockingWorker.run(TaskExecutionService.java:613)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:750)
Caused by: java.lang.NumberFormatException: For input string: "1,ding"
	at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
	at java.lang.Integer.parseInt(Integer.java:580)
	at java.lang.Integer.parseInt(Integer.java:615)
	at org.apache.seatunnel.format.text.TextDeserializationSchema.convert(TextDeserializationSchema.java:204)

Zeta or Flink or Spark Version
No response
Java or Scala Version
java1.8
Screenshots
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

hi @codeDing18   Can you provide more information, such as ddl of hive table

hi @codeDing18 Can you provide more information, such as ddl of hive table
thx for reply.I have solved the problem. Just need add delimiter="\\|" to Hive.

hi @codeDing18 Can you provide more information, such as ddl of hive table

thx for reply.I have solved the problem. Just need add delimiter="\\|" to Hive.

Can you elaborate? Because we had a similar problem before

link #5140

hi @codeDing18 Can you provide more information, such as ddl of hive table

thx for reply.I have solved the problem. Just need add delimiter="\\|" to Hive.

Can you elaborate? Because we had a similar problem before

the ddl of hive table is below:
create table lineitem (
  l_orderkey int,
  l_partkey int,
  l_suppkey int,
  l_linenumber int,
  l_quantity double,
  l_extendedprice double,
  l_discount double,
  l_tax double,
  l_returnflag string,
  l_linestatus string,
  l_shipdate string,
  l_commitdate string,
  l_receiptdate string,
  l_shipinstruct string,
  l_shipmode string,
  l_comment string)
row format delimited
fields terminated by '|'
stored as textfile;

the delimiter of the table's data is '|'.So I need to specify the delimiiter in the config.
the seatunnel config is below:
source {

  Hive {
    table_name = "tpch.linetem"
    metastore_uri = "thrift://xxx:9083"
    hdfs_site_path = "/usr/local/apache-seatunnel-2.3.3/hadoop_config/hdfs-site.xml"
    hive_site_path = "/usr/local/apache-seatunnel-2.3.3/hadoop_config/hive-site.xml"
    kerberos_principal = "hdfs/xx@TEST"
    kerberos_keytab_path = "/etc/security/keytabs/hdfs.keytab"
    delimiter="\\|"
  }

sink {

  Doris {
    fenodes = "localhost:8031"
    username = root
    password = "xxx"
    table.identifier = "seatunnel.test2"
    sink.label-prefix = "hive-doris"
    sink.enable-delete = "true"
    doris.config {
      format="json"
      read_json_by_line="true"
    }
  }

Thank you for your feedback. It seems to be missing the ability to automatically detect the delimiter.

hi @codeDing18 Can you provide more information, such as ddl of hive table

thx for reply.I have solved the problem. Just need add delimiter="\\|" to Hive.

Can you elaborate? Because we had a similar problem before

the ddl of hive table is below:
create table lineitem (
  l_orderkey int,
  l_partkey int,
  l_suppkey int,
  l_linenumber int,
  l_quantity double,
  l_extendedprice double,
  l_discount double,
  l_tax double,
  l_returnflag string,
  l_linestatus string,
  l_shipdate string,
  l_commitdate string,
  l_receiptdate string,
  l_shipinstruct string,
  l_shipmode string,
  l_comment string)
row format delimited
fields terminated by '|'
stored as textfile;

the delimiter of the table's data is '|'.So I need to specify the delimiiter in the config. the seatunnel config is below:
source {

  Hive {
    table_name = "tpch.linetem"
    metastore_uri = "thrift://xxx:9083"
    hdfs_site_path = "/usr/local/apache-seatunnel-2.3.3/hadoop_config/hdfs-site.xml"
    hive_site_path = "/usr/local/apache-seatunnel-2.3.3/hadoop_config/hive-site.xml"
    kerberos_principal = "hdfs/xx@TEST"
    kerberos_keytab_path = "/etc/security/keytabs/hdfs.keytab"
    delimiter="\\|"
  }

sink {

  Doris {
    fenodes = "localhost:8031"
    username = root
    password = "xxx"
    table.identifier = "seatunnel.test2"
    sink.label-prefix = "hive-doris"
    sink.enable-delete = "true"
    doris.config {
      format="json"
      read_json_by_line="true"
    }
  }


latest with jdk17 & almalinux

What feature do you want to see added?
Since jdk11 is going to no longer be supported,  when will an image with lastest jenkins, jdk17 and almalinux be available?
Upstream changes
No response

There are no current plans for it.
These are what we are providing for now:
https://github.com/jenkinsci/docker/tree/master/17

As stated by @timja, there is no plan to move almalinux to Java 17.  Switch to use the UBI container image that includes Java 17.


FormData object support

I am unable to parse a FormData objects containing form information.
The received data is in the following format:
------WebKitFormBoundary05dwgxFHZcnKtx42
Content-Disposition: form-data; name="name"
John
------WebKitFormBoundary05dwgxFHZcnKtx42

Hi rosenbjerg. That looks like a malformed multipart. The final boundary in a multipart must end with --. For your example I believe it should look like so:
------WebKitFormBoundary05dwgxFHZcnKtx42
Content-Disposition: form-data; name="name"

John
------WebKitFormBoundary05dwgxFHZcnKtx42--

Sorry, my fault, this was just a bit of the full data. The last boundary does end with
------WebKitFormBoundary05dwgxFHZcnKtx42--
The problem was that i was sending a file using the FormData object, but i get 'Unexpected end of stream'-exception when trying to parse and save it the drive.
Other than that problem, the StreamingMultipartFormDataParser has been of good use to me :)

Ahh I see. So the error was caused by having file data in something marked as form data.
Yeah if we try and read a file like it's form-data we'll definitely run into issue.

Yes. I followed this guide to upload a file using the FormData object. But when using the StreamingMultipartFormDataParser to parse the request body, it throws the 'Unexpected end of stream'-exception

@rosenbjerg I know it's been three years since you raised this issue but I recently took over stewardship of this project and I'm trying to address outstanding issues. If this is still a problem, I'd like to take a look at it and try to find a solution. Let me know if this is still a problem (FYI: I published a few releases in the last months so make sure to upgrade to the latest.)
Thanks

It's no longer a problem for as I've moved to aspnet core and the inbuilt form parser.
So you can just close this issue :)

Ok. Thanks for letting me know. I appreciate it.


MINIFICPP-1117 - minifi::Exception is now nothrow copyable

Implemented in terms of std::runtime_error
Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[x] If applicable, have you updated the LICENSE file?
[x] If applicable, have you updated the NOTICE file?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

I've added some boilerplate for string joining. I can remove it at some performance cost (extra std::string allocations) or additional dependency (boost::algorithm::join)

update:

fix ProcessorTests
move string utilities to StringUtils and generalize them
add unit test to cover the new StringUtils::join_pack
Moving the utilities from a private namespace to StringUtils means that they need to be more general IMO. I've extended them to work with any character type and do SFINAE checking on the string types.
This means quite some template code, which may not be welcome in this codebase. Suggestions are welcome.


test PR with Github API

Please pull this in!

Docs Build status updates of commit 4ec2d36:
:warning: Validation status: warnings

File
Status
Preview URL
Details
Dependent Files

sdp-test/page-model-documents/Tutorial.yml
:warning:Warning

Details

sdp-test/page-model-documents/Tutorial.yml

[Warning] Unable to find uid "challenge-uid".

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit bf5c76a:
:warning: Validation status: warnings

File
Status
Preview URL
Details
Dependent Files

sdp-test/page-model-documents/Tutorial.yml
:warning:Warning

Details

sdp-test/page-model-documents/Tutorial.yml

[Warning] Unable to find uid "challenge-uid".

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 73b930b:
:warning: Validation status: warnings

File
Status
Preview URL
Details
Dependent Files

sdp-test/page-model-documents/Tutorial.yml
:warning:Warning

Details

sdp-test/page-model-documents/Tutorial.yml

[Warning] Unable to find uid "challenge-uid".

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


fix typehints PEP0484

see https://www.python.org/dev/peps/pep-0484/#arbitrary-argument-lists-and-default-argument-values

Codecov Report

Merging #507 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #507   +/-   ##
=======================================
  Coverage   80.24%   80.24%
=======================================
  Files         101      101
  Lines       10650    10650
=======================================
  Hits         8546     8546
  Misses       2104     2104

Impacted Files
Coverage Δ

pysb/core.py
88.73% <ø> (ø)

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 fe2c0e4...c888e69. Read the comment docs.

Seems OK. Does this help given that all the downstream places these kwargs get passed are still only hinted as dict?

This fixes the syntax highlighting in PyCharm when specifying Parameters. Downstream usage doesn't matter but could also be fixed, could  be helpful for developers.


Adding Eastland Junior-Senior High School

@RobertHana You might miss my previous comment. Please react.


Fixes #159 - Update all the TS code to comply with linter

Update functional tests to work with new list-item-entry component. They were failing.

@michaelkleinhenz @ldimaggi Can you please review this PR. The 2nd commit is to fix a problem with the merger of the code you both submitted. I didn't realize @michaelkleinhenz had not rebased to include @ldimaggi new tests. Please check the fix I did to the tests and confirm is it correct.
To run the linter use: npm run lint

Works and tests ok. Do we really have a lint rule that requires { } around one line blocks? :-/


wrong async tests with disabled timeout

Let's consider the following test:
var assert = require('assert');

describe('suite', function () {
  it('should be unfinished', function (done) {
  });
  it('should be passed', function () {
    assert.equal(1, 1);
  });
});

Test should be unfinished is wrong, because done callback  isn't called.
Running the test with mocha --timeout 0 test/ outputs nothing.
Expected behavior: should be unfinished should be reported as failed and should be passed as passed.

closing as old

https://github.com/mochajs/mocha/issues/1027#issuecomment-28661588
^-- was the problem described above actually fixed? Possibly using an approach like @Schoonology was trying? If not, I don't think this should be closed, its still an open bug, and easy to repro.

Can we reopen the issue as the problem is not fixed? Passing --timeout <big number> to workaround the issue looks a bit strange as any large magic number looks suspicious.


Suppress sporadic exceptions from JumpList creation code

PR Summary
Closes #9295
Catch sporadic exceptions from JumpList creation code. Once the jumplist is registered, it persists, therefore no problem to swallow the occasional exception.
Comment here suggest that this fix improves it.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[ ] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

I think we can merge the small change and watch some time.

Comment here suggest that this fix improves it, therefore changing PR state from draft to published.

Since this hasn't repro'd for anyone on the PowerShell team, and the change itself is not risky, I agree we should take this for Preview.2 and watch the feedback.

@PoshChan Please remind me in 12 hours

@iSazonov, this is the reminder you requested 12 hours ago

I would love we figure out the root cause and understand why this change fixed the issue. The exception should be captured by the task and save in the Exception property, so theoretically, exception shouldn't be a problem unless it's fatal (e.g. AccessViolationException)

@daxian-dbw Is your request to write the exception to log?

@iSazonov That would be helpful to understand what is actually happening.

@bergmeister Could you please address @daxian-dbw comment?

When you say 'write to log', do you mean write to console host?

@bergmeister EventLog would be better.  Writing the the console would be disruptive.


Added ItemID.DRAGONSTONE_BRACELET to the Unenchanted dragonstone jewe…

Added ItemID.DRAGONSTONE_BRACELET to the Unenchanted dragonstone jewelry step for elite clues.

What even is a DRAGON_BRACELET? :thinking:


64-bit Charm message sizes

Original issue: https://charm.cs.illinois.edu/redmine/issues/1378

Currently, PUP supports 64bit sizes, sizes of chares are 64bit, the GNI/Isomalloc mempool uses 64bit sizes, but Charm message envelopes use ints as sizes. So messaging anything with size greater than an int will currently fail. The messages sizes will need to be fixed throughout the runtime, in all machine layers for all messaging types.
I think that first we should add checks in message constructors to fail when trying to allocate something larger than the size of an int.

Original date: 2017-01-24 20:59:36

Also, note that AMPI has a patch in gerrit for MPI-3 large count support, which should work once this Charm message size issue is fixed: https://charm.cs.illinois.edu/redmine/issues/1105

Original date: 2017-01-25 00:18:17

Previously merged, related patches:
Use size_t instead of int for all PUP interfaces:  ~~https://charm.cs.illinois.edu/gerrit/#/c/1873/~~ https://github.com/UIUC-PPL/charm/commit/053d2aa45c6ad9d2d590e409cd3b4de87ec9887e
Make sizes of chares and readonlies size_t instead of int:  ~~https://charm.cs.illinois.edu/gerrit/#/c/1903/~~ https://github.com/UIUC-PPL/charm/commit/01b69b0f41ed6ec8d988a5d929bbb85407c71a51
Convert thread data sizes to size_t instead of int:  ~~https://charm.cs.illinois.edu/gerrit/#/c/1913/~~ https://github.com/UIUC-PPL/charm/commit/d12bdc10e9716c48255ef6710356b349d6ff21d9
Convert GNI/Isomalloc mempool to use size_t instead of int for sizes:  ~~https://charm.cs.illinois.edu/gerrit/#/c/1912/~~ https://github.com/UIUC-PPL/charm/commit/0d2d67b8d08885bdf6b13637c8134833d7e0579c
Convert CharmDebug to use 64-bit sizes for chares and readonlies: ~~https://charm.cs.illinois.edu/gerrit/#/c/2356/~~ https://github.com/UIUC-PPL/charm/commit/d3c7bc69f6eefd07cbf084a41775cf4aeb30f84b

Original date: 2017-04-06 13:45:02

I have a half-baked implementation on multicore builds. Some of the machine layers already support 64 bit message sizes (PAMI, maybe others), and some will require small changes. The main changes are in Charm, Converse, and LRTS interfaces.
Note that this will require changes to CharmDebug (and possibly many other things).

Original date: 2017-04-13 21:11:23

Here's a first pass at the netlrts/multicore/smp build. This builds and passes the tests/examples, but no attempt has been made for CharmDebug or any non-standard build options: https://charm.cs.illinois.edu/gerrit/#/c/2395/
We can probably make this more backwards compatible, but I didn't attempt that here yet.

Original date: 2017-04-21 00:22:34

Abort before trying to migrate a chare with size greater than a message can hold: ~~https://charm.cs.illinois.edu/gerrit/#/c/2425/~~ https://github.com/UIUC-PPL/charm/commit/823e316b40202f18f9af703a99348a06f232a8cb
A next step for this would be to pipeline chares that are bigger than INT_MAX in multiple chunks that are up to INT_MAX bytes in size.

Original date: 2018-03-05 17:17:30

I disagree with lowering the priority on this.  The next round of machines is going to be fewer nodes with much larger memory footprint.  Therefore, we are more likely to see very large messages in a variety of contexts.

Original date: 2018-03-05 17:24:08

I have implemented the basic support for this in netlrts and multicore builds here: https://charm.cs.illinois.edu/gerrit/#/c/2395/
That needs to be rebased, to have a test added for large messages, and other network layers would need development. I'm not sure if all network layers even support 64-bit messages. The MPI standard added some support for it to point-to-point messages in MPI-3.0. But perhaps we shouldn't even expose this to the network layers. Instead we can just pipeline messages with size > INT_MAX.

Original date: 2018-03-26 22:35:19

I don't think we want to expand to support 64bit sizes for all messages.
That would pointlessly blow up the size field for the 99% of messages that fit under uint32.
But we do want to support sending data that is larger than uint32.
That could be handled by pipelining.  Or by having a different message header and different handlers for very large data.  Or both.


Display color issue

Please check the following snapshot in iterm2 of Macbook; The middle color is black;

And what do you expect it to be? Default value of BULLETTRAIN_CONTEXT_BG is black

Yep, got it. I was new to this, not familiar with all the settings. Thanks.


failed to load config from vite.config.js

Description
Failed to load config when building.
Reproduction
yarn create @vitejs/app failed-to-load-config --template svelte-ts
cd failed-to-load-config
yarn
yarn dev

Error:
failed to load config from /tmp/failed-to-load-config/vite.config.js
error when starting dev server:

unfortunately the lastest breaking change in vite-plugin-svelte required an update to vites template. that was merged but not released
see this PR on how to update your project locally
https://github.com/vitejs/vite/pull/3760
more info:
https://github.com/sveltejs/vite-plugin-svelte/blob/main/packages/vite-plugin-svelte/CHANGELOG.md#sveltejsvite-plugin-svelte

import { svelte } from '@sveltejs/vite-plugin-svelte';

Works wellm thanks

FYI, @vitejs/create-app v2.4.3 was just released including https://github.com/vitejs/vite/pull/3760

check your node version, it must be greater than v14.

I have node v16.17.1 but am still getting this error. I noticed @lapwat posted "import { svelte } from '@sveltejs/vite-plugin-svelte';" as a solution of some kind but even after looking at the links provided I'm not sure where to put this or what to do next. It seems strange that I'm getting this error in an out of the box Laravel 9 install with everything up to date.

See https://github.com/sveltejs/vite-plugin-svelte#usage
Please note that this issue was raised a long time ago. Make sure you use the latest version of vite-plugin-svelte.
For questions how to integrate/use vite-plugin-svelte please use https://svelte.dev/chat #questions.It will be helpful if you provide a link to a repo with your setup when asking there.

@Zephni

you can put that in your vite.config.js

I have this issue because a try to setup a monorepo, but i don't pay attention a don't o have the same node version to my root package.json and in one of my package/workspace.
Pay attention to the versions of node you are using


around-all: Add characteristics to better-define behaviors, and clean up existing characteristics

This commit is a follow-up from 660bd3f; since I added it I felt like I should do a bit of cleanup.  I added some behavioral test coverage with after-all interaction and cleaned up the with-all interaction characteristics.

Merged manually due to major code changes.  Looks good.  Thanks!


Navigating the found keywords in Notebook Find is hard to follow

Is your feature request related to a problem? Please describe.
When a "paragraph" finds a number of instances of the found keyword (using Notebook find), it's hard to know which one the arrow / navigation is up to.

Describe the solution or feature you'd like
Perhaps the current keyword that is activated by the arrow has a darker color or a different color to make it easier to distinguish.
Describe alternatives you've considered
none.
Additional context
Found this as a usability issue during Livesite discussion.

@MsSQLGirl I think can follow what we have for MD files:

Current match is highlighted in orange
All other matches are highlighted in yellow

@MsSQLGirl I think can follow what we have for MD files:

Current match is highlighted in orange
All other matches are highlighted in yellow

This is a good one. Hopefully a quick fix on our side.

This is a good one. Hopefully a quick fix on our side.

Agreed. Thank you!

Agreed. Thank you!

@radentonev @yualan I have a fix that highlights the correct term one by one instead of highlight all results and then use different highlight color for the current one. Do you think there is added value to the latter way? (It's relatively easy for me to make that change as well) So asking for your opinions here.
Also @chlafreniere  your thoughts as well?

@radentonev @yualan I have a fix that highlights the correct term one by one instead of highlight all results and then use different highlight color for the current one. Do you think there is added value to the latter way? (It's relatively easy for me to make that change as well) So asking for your opinions here.
Also @chlafreniere  your thoughts as well?


Lazy-loaded <style is="custom-style"> should trigger Polymer.updateStyles

Description
Lazy-loaded <style is="custom-style"> should trigger global updateStyles.  If you currently async load an import that contains a top-level custom-style (or more likely, an element that depends on a custom-style, such as paper-card), although the custom-style gets registered and the global Polymer.StyleDefaults properties get updated, they do not cascade down the tree.
Live Demo
Works (paper-card loaded sync): http://jsbin.com/raboji/edit?html,output
Fails (paper-card loaded on demand): http://jsbin.com/ruhuqo/edit?html,output
Steps to Reproduce
See failing example above.  Note, it's important to have a host element that consumes custom properties between the lazy-loaded element consuming lazy-loaded styles and the root, otherwise the custom property styles are chained lazily back up to the root and it will work.
Expected Results
Styles applied by global <style is="custom-style"> should apply after being lazy-loaded.
Actual Results
Styles applied by global <style is="custom-style"> do not apply after being lazy-loaded.
Browsers Affected

[X] Chrome

Versions

Polymer: v1.5.0
webcomponents: n/a

This also affects the use iron-flex and iron-flex-alignment within an element.
<dom-module id="my-element">
    <template>
        <style include="iron-flex iron-flex-alignment">
            :host {
                display: block;
            }

For exposure, we've recently seen bugs reported on this underlying behavior in the polymer-cli & app-drawer-template repos


Image not responding when call #next on an empty AtomicSharedPriorityQueue

Hello,
I have a question about the project Bloc. I ask it here because the project Bloc doesn't have any issues page.
Running AtomicSharedPriorityQueue new next makes the Pharo image not responding.
Is it a bug?
Pharo version:
Pharo 8.0.0
Build information: Pharo-8.0.0+build.1124.sha.0932da82f08175e906b0e2a8052120c823374e9f (64 Bit)

Bloc version:
Commit: [6e03d80] 6e03d80b67f4e96e734dc5b1a972e55c903412af

Hi @mabdi:
Executing AtomicSharedPriorityQueue new next is like executing Semaphore new wait. The semaphore will wait forever for a aSemaphore signal call. In case of AtomicSharedPriorityQueue new next, it will wait forever for a new item added to the queue.
Since code snippets are executed in a UI process, it blogs the whole program (UI, image) forever.
You can use other non-blocking methods, e.g., nextIfNone: , nextOrNil, and nextOrNilSuchThat:.
@mabdi, if you are satisfied with the response, please, close the issue.

Thank you. Yes, I'm satisfied.
This call sequence was generated automatically by a tool (SmallAmp: tries to generate new test methods to increase the coverage). And I wanted to be sure that the sequence is a valid sequence.

I am glad it was solved.


Multisig. Creation flow. Can't change signatory name if that address has in Address book

Description
Name field is read only in multisig creation flow, if that address has in Address Book. User should be able to change it, while create a multisig
Example:
https://github.com/user-attachments/assets/0f8cd430-5eaf-4605-955c-678e90958189
Steps to Reproduce

Add any address in Address book
Go to Multisig creation flow
Add signatory from the address book
Try to update the name

Expected Behavior
User should be able to change signatory name, even if it comes from the Address Book
Actual Behavior
Can't change name while create multisig
Environment
https://github.com/novasamatech/nova-spektr/commit/53c448e24a584dfd10867e6805e68d557fa5bda8

Status verification: ⏳
What has been verified:

Change name

https://github.com/novasamatech/nova-spektr/issues/2673

Status verification: ❌
What has been verified:

Contact's name will change if put another name in signatory

https://github.com/user-attachments/assets/4d05d4ca-f743-45dc-9f86-bb11b3888dbe
Case:

Go to multisig creation flow
Choose as a signatory one address from address book
Change signatory name
Create multisig

Expected result:
Contact's name will change on a new one
Actual result:
Contact's name won't change

Status verification: ✅


Unable to open czi line-scan kymographs - missing raw frame(t) pixel data

First, thanks for working on this critical package. I understand and appreciate how complex opening proprietary binary file formats can be. I followed the package from aicsimageio to its new home at bioio and am excited to get this working!
Describe the Bug
I would like to open 'line scan' czi files using bioio. When I do this, some image data is missing, it does not include the correct number of frames(t). In both cases below, I get only one (1) frame whereas I expect 1000 and 10000 in my two example files (see below).
Background. Lines scans are where you perform, well, a line scan over and over. With something like 1000 or 10000 repeated scans of a line. You then make a 2D image of all the pixel data by constructing a 2D image where each line scan is one row in the image. What results is referred to as a kymograph or space/time image. For example, each line scan might be 1024 pixels and it is repeatedly acquired 1000 times. You then make a kymograph image from all the raw pixel data and it has a pixel size/shape of 1000 x 1024 (or visa-versa).
Problem is, when I open with bioio, I am only getting one line-scan, e.g. one frame(t), rather than the expected 1000 or 10000.
Expected Behavior
I would expect all the raw pixel data would be available and it is not. It seems to be missing frames(t), with 1 when I expect 1000 or 1000
Reproduction
Here are two sample files

CO2.czi with 512 pixels per line and 10000 repeated line scans.
Image 14.czi with 1024 pixels per line and 1000 repeated line scans.

In this example, bioio got the pixels per line correct (e.g. 1024) but there is no raw pixel data corresponding to the repeated line-scans. In all case frames(T) is just 1. I expect some dimension to represent the repeated line scans, e.g. 1000.
import os
from bioio import BioImage
#from aicspylibczi import CziFile  # tried this too but same bug/behavior

path = 'path/to/my/example/file/Image 14.czi'
print(f'loading {os.path.split(path)[1]}')

img = BioImage(path)

print('img.data.shape:', img.data.shape)  # (1, 2, 1, 1, 1024)

print('=== xarray_data:')
print(img.xarray_data)  # <xarray.DataArray (T: 1, C: 2, Z: 1, Y: 1, X: 1024)>

print('dims:', img.dims)  # <Dimensions [T: 1, C: 2, Z: 1, Y: 1, X: 1024]>
print('dims.order:', img.dims.order)  # TCZYX
print('dims.X:', img.dims.X)  # 1024
print('dims.Y:', img.dims.Y)  # 1
print('dims.T:', img.dims.T)  # 1
print('img.shape:', img.shape)  # (1, 2, 1, 1, 1024)

# returns the X dimension pixel size as found in the metadata
print('physical_pixel_sizes.X:', img.physical_pixel_sizes.X)

Results in this output
loading Image 14.czi
img.data.shape: (1, 2, 1, 1, 1024)
=== xarray_data:
<xarray.DataArray (T: 1, C: 2, Z: 1, Y: 1, X: 1024)>
array([[[[[ 0,  0,  0, ...,  0,  0,  0]]],
        [[[39, 66,  0, ...,  0,  0,  0]]]]], dtype=uint8)
Coordinates:
  * C        (C) <U6 'NDD R1' 'NDD R4'
  * Z        (Z) float64 0.0
  * Y        (Y) float64 0.0
  * X        (X) float64 0.0 0.06599 0.132 0.198 ... 67.31 67.37 67.44 67.5
Dimensions without coordinates: T
Attributes:
    unprocessed:  <Element 'ImageDocument' at 0x14fe8ae80>
dims: <Dimensions [T: 1, C: 2, Z: 1, Y: 1, X: 1024]>
dims.order: TCZYX
dims.X: 1024
dims.Y: 1
dims.T: 1
img.shape: (1, 2, 1, 1, 1024)

physical_pixel_sizes.X: 0.06598669529504321

Ideas
Idea 1) There are recent updates from Zeiss on a different/newer package called pylibCZIrw
I see bioio is using aicspylibczi which is a fork of elhuhdron/pylibczi.
I also see another version of pylibczi coming directly from zeiss (no github) but can download source from PyPi pylibCZIrw. This has very recent updates (Dec 4, 2023). I am not able to install this because I haven't been able to build the wheels on a macOS machine with apple silicon (M2) CPU (afaik). The email contact there is<EMAIL_ADDRESS>Idea 2) I can open these czi files using Fiji/Bio-Formats importer and get all the pixel data
Fiji environment is
Fiji: 2.14.0/1.54f (2023-07-07)
Bio-Formats Plugins for ImageJ 7.0.1 (2023-10-16)

File image 14.czi
Each line (image) is (1024, 1)
Channels (c): 2
Slices(z): 1
Frames(t): 1000
physical pixel size: 0.066
manually saved as tif and openend with tifffile yields a good shape of (1000, 1, 1024)
File CO2.czi
Each line (image) is (512,1)
Channels (c): 2
Slices(z): 1
Frames(t): 10000
physical pixel size: 0.0175789
manually saved as tif and openend with tifffile yields a good shape of (10000, 1, 512)
Environment
macOS 13.3.1 (a)
Python 3.11.5
bioio 1.0.1.dev2+gf594aa5
bioio-base 1.0.1.dev1+g1003511
bioio-czi 1.0.1.dev0+gcb2ed27.d20231212
p.s. I am actually using the bioio branch `fix/resolution-level from a recent issue and pull request.

Thank you for the thorough issue writeup!!  And thanks for trying bioio so early.  #30 has now been merged to main.
We'll look into this CZI issue but many people are on vacation soon so it may not be till 2024.  Also we might want to move this ticket into bioio-czi since it may be specific to that reader.
Making a new czi reader to use pylibCZIrw is a longer project which we won't take on in the near term.  More likely we can see if there are changes to aicspylibczi that would fix this.


refactor: cleanup docker SKUs from weekly yaml

What type of PR is this?

What this PR does / why we need it:
This PR cleans up the docker SKUs we no longer build from the weekly build pipeline, reducing clutter.
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall first build on amaheshwari/cleaupSKU at 61.817%

Totals

Change from base Build<PHONE_NUMBER>:
61.8%

Covered Lines:
2524

Relevant Lines:
4083

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall first build on amaheshwari/cleaupSKU at 61.817%

Totals

Change from base Build<PHONE_NUMBER>:
61.8%

Covered Lines:
2524

Relevant Lines:
4083

💛  - Coveralls


Update sbt-coveralls to 1.3.5

Updates org.scoverage:sbt-coveralls from 1.3.2 to 1.3.5.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scoverage", artifactId = "sbt-coveralls" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scoverage", artifactId = "sbt-coveralls" }
}]

labels: sbt-plugin-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #59.


Yet another attempt to fix test timeouts

Yet another attempt to fix test timeouts due to an infinite loop on the finalizer thread.

👍


pyftmerge error when merging some Not fonts

I’m trying to merge Noto Serif into Noto Naskh Arabic, but pyftmerge NotoNaskhArabic-Regular.ttf NotoSerif-Regular.ttf  fails with:
Traceback (most recent call last):
  File "pyftmerge", line 9, in <module>
    load_entry_point('fonttools==2.5', 'console_scripts', 'pyftmerge')()
  File "/fonttools/Lib/fontTools/merge.py", line 940, in main
    font = merger.merge(args)
  File "/fonttools/Lib/fontTools/merge.py", line 770, in merge
    table = clazz(tag).merge(self, tables)
  File "/fonttools/Lib/fontTools/merge.py", line 374, in merge
    assert m.duplicateGlyphsPerFont[fontIdx].get(oldgid, gid) == gid
AssertionError

But if I reverse the order, i.e. pyftmerge NotoSerif-Regular.ttf NotoNaskhArabic-Regular.ttf, it works just fine.

I also found this when working with a myanmar/Latin pair, in
github.com/khmertype/Gantgaw
On Jul 21, 2015 9:55 PM, "Khaled Hosny"<EMAIL_ADDRESS>wrote:

I’m trying to merge Noto Serif into Noto Naskh Arabic, but pyftmerge
NotoNaskhArabic-Regular.ttf NotoSerif-Regular.ttf fails with:
Traceback (most recent call last):
File "pyftmerge", line 9, in
load_entry_point('fonttools==2.5', 'console_scripts', 'pyftmerge')()
File "/fonttools/Lib/fontTools/merge.py", line 940, in main
font = merger.merge(args)
File "/fonttools/Lib/fontTools/merge.py", line 770, in merge
table = clazz(tag).merge(self, tables)
File "/fonttools/Lib/fontTools/merge.py", line 374, in merge
assert m.duplicateGlyphsPerFont[fontIdx].get(oldgid, gid) == gid
AssertionError
But if I reverse the order, i.e. pyftmerge NotoSerif-Regular.ttf
NotoNaskhArabic-Regular.ttf, it works just fine.
—
Reply to this email directly or view it on GitHub
https://github.com/behdad/fonttools/issues/322.


docs: dfx canister request-status requires canister to be specified

It's correctly documented in the dfx cli help
Here's what that looks like:

Checklist:

[x] The title of this PR complies with Conventional Commits.
[ ] I have edited the CHANGELOG accordingly.
[ ] I have made corresponding changes to the documentation.

@ericswanson-dfinity I updated with the requested changes.
On a side note, is it not a better idea to follow the same notation for both dfx and the public docs?

@ericswanson-dfinity I updated with the requested changes.
On a side note, is it not a better idea to follow the same notation for both dfx and the public docs?

Maybe, however, a change to the docs for a single command is not the way to do that.


Enable govet linter; disable vet in make verify

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
The PR enables govet, removes vet from verify make target; fixes govet.nilness issue.
Which issue(s) this PR fixes:
Special notes for your reviewer:
govet is enabled in the https://github.com/kubernetes/kubernetes/blob/e0621034bedeeabe83383e5c300cf2d4fb616f36/hack/golangci.yaml#L136, so I've also enabled it here with all default analyzers and nilness analyzer.
So, the whole enabled govet analyzers list looks like this:
❯ GL_DEBUG=govet ./golangci-lint run
...
DEBU [govet] Enabled by config analyzers (33): [appends asmdecl assign atomic bools buildtag cgocall composites copylocks defers directive errorsas framepointer httpresponse ifaceassert loopclosure lostcancel nilfunc nilness printf shift sigchanyzer slog stdmethods stringintconv structtag testinggoroutine tests timeformat unmarshal unreachable unsafeptr unusedresult]

Note, that debug flag GL_DEBUG=govet was added to golangci-lint today and will be available with golangci-lint v1.57.0 (not yet released).
To speed up CI, the PR removes vet make target from verify. This is because running go vet ./... is equivalent to  running golangci-lint with the govet linter.
Additionally, this PR removes the unnecessary check for nil detected by the govet.nilness:
pkg/controller/jobframework/reconciler.go:297:23: nilness: tautological condition: non-nil != nil (govet)
                if err == nil && wl != nil {
                                    ^

Does this PR introduce a user-facing change?
NONE

/ok-to-test

I'm ok enabling this, given that k/k seems to be going in a similar direction.


chore(deps): update dependency jsii to v5 - abandoned

This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

jsii (source)
^1.80.0 -> ^5.3.20

Release Notes

aws/jsii-compiler
v5.3.20
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/737
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/740
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/743
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/746
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/749
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/751
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/753

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.3.18...v5.3.20
v5.3.19
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/738
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/741
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/744
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/747
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/750
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/752
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/754

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.3.17...v5.3.19
v5.3.18
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/716
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/719
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/722
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/725
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/728
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/731
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/734

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.3.15...v5.3.18
v5.3.17
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/717
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/720
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/723
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/726
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/729
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/732
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/735

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.3.14...v5.3.17
v5.3.16
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/712
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/715
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/718
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/721
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/724
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/727
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/730

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.3.13...v5.3.16
v5.3.15
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/694
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/698
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/701
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/704
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/707
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/710
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/713

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.3.12...v5.3.15
v5.3.14
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/675
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/679
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/683
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/687
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/691
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/695
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/699
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/702
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/705
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/708
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/711
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/714

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.3.10...v5.3.14
v5.3.13
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/668
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/672
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/676
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/680
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/684
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/688
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/692
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/696
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/700
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/703
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/706
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/709

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.3.8...v5.3.13
v5.3.12
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/674
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/678
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/682
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/686
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/689

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.3.11...v5.3.12
v5.3.11
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/646
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/650
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/654
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/658
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/662
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/666
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/670

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.3.7...v5.3.11
v5.3.10
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/647
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/651
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/655
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/659
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/663
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/667
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/671

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.3.6...v5.3.10
v5.3.9
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/645
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/649
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/653
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/657
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/661
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/665
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/669

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.3.5...v5.3.9
v5.3.8
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/640
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/644
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/648
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/652
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/656
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/660
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/664

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.3.4...v5.3.8
v5.3.7
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/595
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/601
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/626
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/630
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/634
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/638
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/642

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.2.42...v5.3.7
v5.3.6
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/602
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/627
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/631
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/635
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/639
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/643

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.2.44...v5.3.6
v5.3.5
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/600
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/629
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/633
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/637
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/641

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.2.43...v5.3.5
v5.3.4
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/622
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/623
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/624
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/625
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/628
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/632
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/636

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.3.3...v5.3.4
v5.3.3
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/615
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/616
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/617
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/618
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/619
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/620
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/621

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.3.2...v5.3.3
v5.3.2
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/608
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/609
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/610
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/611
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/612
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/613
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/614

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.3.1...v5.3.2
v5.3.1
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/599
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/603
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/604
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/605
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/606
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/607

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.3.0...v5.3.1
v5.3.0
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/595
feat: TypeScript 5.3 by @mrgrain in https://github.com/aws/jsii-compiler/pull/598

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.2.42...v5.3.0
v5.2.44
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/579
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/582
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/585
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/588
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/591
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/594
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/597

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.2.41...v5.2.44
v5.2.43
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/578
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/581
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/584
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/587
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/590
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/593
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/596

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.2.40...v5.2.43
v5.2.42
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/574
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/577
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/580
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/583
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/586
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/589
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/592

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.2.39...v5.2.42
v5.2.41
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/558
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/561
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/564
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/567
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/570
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/573
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/576

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.2.38...v5.2.41
v5.2.40
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/557
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/560
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/563
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/566
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/569
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/572
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/575

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.2.37...v5.2.40
v5.2.39
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/553
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/556
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/559
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/562
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/565
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/568
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/571

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.2.36...v5.2.39
v5.2.38
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/536
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/539
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/542
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/545
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/549
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/552
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/555

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.2.35...v5.2.38
v5.2.37
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/535
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/538
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/541
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/544
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/548
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/551
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/554

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.2.34...v5.2.37
v5.2.36
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/531
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/534
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/537
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/540
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/543
chore: don't build node21 by @mrgrain in https://github.com/aws/jsii-compiler/pull/546
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/547
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/550

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.2.33...v5.2.36
v5.2.35
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/515
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/518
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/521
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/524
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/527
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/530
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/533

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.2.32...v5.2.35
v5.2.34
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/514
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/517
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/520
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/523
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/526
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/529
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/532

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.2.31...v5.2.34
v5.2.33
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/510
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/513
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/516
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/519
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/522
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/525
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/528

Full Changelog: https://github.com/aws/jsii-compiler/compare/v5.2.30...v5.2.33
v5.2.32
Compare Source
What's Changed

chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/494
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/497
chore(deps): upgrade dependencies by @aws-cdk-automation in https://github.com/aws/jsii-compiler/pull/500
chore(deps): upgrade dependencies by @aws-cdk-automation in [htt

Configuration
📅 Schedule: Branch creation - "before 1am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Autoclosing Skipped
This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.


guide: (better) SSH remotes

Closes #3832
In review app: https://dvc-org-guide-remote-ss-w3dcke.herokuapp.com/doc/user-guide/data-management/remote-storage/ssh

[ ] Consider pinning this to https://discuss.dvc.org/t/how-do-i-use-dvc-with-ssh-remote/279/2 when merged?

[ ]  Consider pinning this to https://discuss.dvc.org/t/how-do-i-use-dvc-with-ssh-remote/279/2 when merged?

(Reminder)


Migrate from Modulefile to metadata.json

Modulefile is deprecated and metadata.json
is what the forge now expects.

merge when green


Make a PostgreSQL EXTENSION from OSM opening_hours type and functions?

Hi Darafei and Zverik
I'm interested in processing OpenStreetMap data and just stumbled over this OSM opening_hours code
https://github.com/gojuno/lostgis/blob/master/sql/types/type_opening_hours.sql
via
https://pgxn.org/dist/lostgis/doc/lostgis.html#opening_hours

Are there any updates on these PostgreSQL types and functions?
How about extracting these types and functions to a separate and self-contained PostgreSQL EXTENSION?

P.S. This is isn't actually only a feature request. It's also a note to you (and a bookmark to self) as I'm always looking for self-contained projects suitable for students and interns.

Hi Stefan,

Likely no. This was done to support toll cost calculation for juno backend and never aimed to be a full implementation, just a subset to support billing. It got rewritten from SQL afterwards, before the bankrupcy of Juno.

go on. most of interesting things went into PostGIS itself (the ST_Safe_* things) or Postgres itself (like the jsonb casts) or sparked discussions to get into MobilityDB. If you can save opening hours code to also be used that will be great.


Honeypot  Cloudfront integration

I have deployed "aws-waf-security-automations" Cloudformation template on our stg env. i see the  HoneyPot APIGateway created. to Add CloudFront behavior, if someone has list of honeypot URI please share with me.

Thanks for the question. You can find the honeypot URL on the Outputs tab of the CloudFormation stack: open the AWS CloudFormation console, choose the stack that you deployed, choose the Outputs tab, and then choose the value for BadBotHoneypotEndpoint.

@aijunpeng Thanks for the response, i was asking about,  list of vulnerable URI that can be monitored by Honeypot, such as
https://www.example.com/.git
https://www.example.com/admin

We don't maintain such list. In general, Honeypot can lure and deflect any attackers attempting to access it.


⚠ Bofrost.lu has degraded performance

In 1a647f0, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2263 ms

Resolved: Bofrost.lu performance has improved in 98a7dc7 after 56 minutes.


Error	MSB3644

I tried to run this project (https://github.com/MaterialDesignInXAML/MaterialDesignInXamlToolkit) I came across the error below let me know if I jumped in too early for this project.
Error	MSB3644	The reference assemblies for .NETFramework,Version=v4.6.2 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application.
You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks
MaterialDesignColors.Wpf
C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets	1229

Hi @nyendwa this is not directly related to this project.
The reason for your failure is the MaterialDesignInXamlToolkit is built targeting several versions on .NET to allow people to use it in a variety of applications. If you want to compile it from source, you will either need to install the relevant .NET frameworks (typically from the Visual Studio Installer or newer frameworks here), or you can edit the various <TargetFrameworks> elements in the projects to just have the framework(s) that you care about.

I am using a latest .NET 7 framework. Should it still give me challenges to
run it?
On Tue, Apr 11, 2023, 17:30 Kevin B @.***> wrote:

Hi @nyendwa https://github.com/nyendwa this is not directly related to
this project.
The reason for your failure is the MaterialDesignInXamlToolkit is built targeting
several versions on .NET
https://github.com/MaterialDesignInXAML/MaterialDesignInXamlToolkit/blob/master/MaterialDesignThemes.Wpf/MaterialDesignThemes.Wpf.csproj#L4
to allow people to use it in a variety of applications. If you want to
compile it from source, you will either need to install the relevant .NET
frameworks (typically from the Visual Studio Installer or newer frameworks
here https://learn.microsoft.com/dotnet/core/install/windows?tabs=net70),
or you can edit the various  elements in the projects
to just have the framework(s) that you care about.
—
Reply to this email directly, view it on GitHub
https://github.com/Keboo/XAMLTest/issues/156#issuecomment-1503617966,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKSGPIPZNC3H2OY4H3FUMVTXAV2H3ANCNFSM6AAAAAAWZVAOUU
.
You are receiving this because you were mentioned.Message ID:
@.***>

If you use the NuGet package in your app, no it should just work. But if you try to compile the code locally, it requires having all of the needed frameworks that the library targets (because when compiling it needs to build all the targets that the NuGet suports).
There is also more information on the Wiki. https://github.com/MaterialDesignInXAML/MaterialDesignInXamlToolkit/wiki/Compiling-From-Source


How to properly extract text color and formatting ?

Hi,
Until the API will be fully documented, would it be possible to explain to me how I could use this library to parse a pdf file and extract all the text in it, including its formatting and colors, please ?
I know this question has already been answered here : https://github.com/mozilla/pdf.js/issues/7895
But the answer is a bit "dry"... since getOperatorList isn't documented as well and returns a huge cryptic array...
Any detailed help on this would be appreciated ^_^
Thanks !

☝ Any comment on this?
I'm also looking for a way to get text color from TextStyle.

@timvandermeij Why was this closed? Its not available in the api. Any word on getting this?


fixed russian translation for css units

This article seems to be translated via google translate or something similar.
Made the article more human-readable.
Fixed typos.
Fixed styles.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 🎉


models.py:83-84: Move Page's const to it's ancestor And...

The puzzle SE619-5f380a04 from #SE619 has to be resolved:
https://github.com/fidals/refarm-site/blob/04e279e040811024b8721d8299875df46a00b6fa/pages/models.py#L83-L84
The puzzle was created by duker33 on 20-Dec-18.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@0pdd 3 puzzles #235, #236, #237 are still not solved.

@0pdd 2 puzzles #236, #237 are still not solved; solved: #235.


 I try to deploy the meteor example app todos, and followed the instructions from the readme, but I'm getting the following mistake. (I'm using Ubuntu 14.04 LTS Server ). Thanks for help.
Configuration file : mup.json
Settings file      : settings.json
“ Checkout Kadira!
It's the best way to monitor performance of your app.
Visit: https://kadira.io/mup ”
Meteor app path    : /home/jan/todos
Using buildOptions : {}
Currently, it is only possible to build iOS apps on an OS X system.
Started TaskList: Deploy app 'todos' (linux)
[h2544161.stratoserver.net] - Uploading bundle
[h2544161.stratoserver.net] - Uploading bundle: SUCCESS
[h2544161.stratoserver.net] - Sending environment variables
[h2544161.stratoserver.net] - Sending environment variables: SUCCESS
[h2544161.stratoserver.net] - Initializing start script
[h2544161.stratoserver.net] - Initializing start script: SUCCESS
[h2544161.stratoserver.net] - Invoking deployment process
Invoking deployment process: FAILED
    -----------------------------------STDERR-----------------------------------
    Failed to remove container (todos-frontend): Error response from daemon: No such container: todos-frontend
    docker: Error response from daemon: failed to create endpoint todos on network bridge: Error starting userland proxy: listen tcp <IP_ADDRESS>:80: bind: address already in use.
    -----------------------------------STDOUT-----------------------------------
    todos
    base: Pulling from meteorhacks/meteord
    518dc1482465: Already exists
    a3ed95caeb02: Already exists
    a3ed95caeb02: Already exists
    a3ed95caeb02: Already exists
    537c534356b6: Already exists
    b65a0e1e554b: Already exists
    a3ed95caeb02: Already exists
    a3ed95caeb02: Already exists
    Digest: sha256:b5a4f6efa98e4070792ed36d33b14385a28e6ceda691a492ee5b9f2431b1515a
    Status: Image is up to date for meteorhacks/meteord:base
    d6d192579495851d5817288ff89abb69512562d7c2a7075f965484e64583c61b

The first thing that typically resolves this is extending the deploy wait time in the settings to 120 if it works lower it to a point that still works but is quicker. Note that as you add complexity you probably need to add wait time.

Oh wait maybe this is more likely a networking problem as it can't find the front end image. No no it says it can delete it cause it wasn't found?  Permissions maybe.
Are you using mup or mupx?  If mup doesn't work for you please try the developer branch mupx. Also note this is currently being ported over at kadirahq. I would try that one too if you're already getting this error from mupx.

Okay I also see it says can't build ios. You have to remove android and is from the build targets. So PRs automates that but they never got merged.

I removed IOS and Android and change the time to 120, no difference, also used mupx and the one from kadirahq, but there i'm getiing this error
Building App Bundle Locally
Error spawn meteor ENOENT
after typing mup deploy

Okay well stick with mupx there is a migration guide in it Readme to refresh things.
Maybe you rerun the setup etc too or something. If your getting an error different with the new port I'm sure they'd be more help at kadirahq so please make a note of your errors with that version there thanks.

Sorry but when i try to delete the meteor.conf file like it's said in the read.me, i can't find the file ?
Is perhaps something wrong with my Meteor installation ?
Like i mentioned, i'm new to linux

Right it's just purging the old versions files. If it's not there no worries. Already done.
If you have a fresh instance make sure it's not already running anything that could conflict.
The previous error says the Web server port 80 already has something running there. Before deployment try accessing the webserver?
You should learn about using ssh secure shell to access the target machine and check for a webserver running etc.
Some hints at learning relative thinga: After deployment with mupx it will install docker so learn as much as you can about that. Then you can use "docker exec bash" to get access into that instance and check things there like the servers accessible with "curl" even if a port is blocked etc.
It will use docker "volume" arguments to mount the deployment machines local folder inside the docker container so when it re-launches it doesn't lose you database etc.
Alright so if you start fresh and follow the instructions you should be able to get the tudos running there are some provoder specific tutorials out there too.
Report back with full logs and configure settings, versions, providers etc., if you can't find a similar issue already resolved to help.


Athena script using the example WIP

I can't get this to run locally so I can't test the output
All queries either cause an error(, or never finish if I fill in my credentials into the awsCredentials)
query: "SHOW SCHEMAS;"
error:
    at AthenaExpress.query (/Users/enik/Documents/symptomradar/node_modules/athena-express/lib/athenaExpress.js:81:10)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

query: "SELECT * FROM responses LIMIT 3;”
error:
Error: InvalidRequestException: Unable to verify/create output bucket symptomradar-dev-storage-results
    at AthenaExpress.query (/Users/enik/Documents/symptomradar/node_modules/athena-express/lib/athenaExpress.js:81:10)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

I'll close this now that @cutepig is working on this in #230.


Add new parameter new_host_delay

Ref. https://github.com/DataDog/documentation/pull/996/files

Thanks! ❤

v0.1.6 has been released!


Filter docs not offset by doc_id

closes #1293.  The full dataset was passed to the filter object and not offset by doc_id when using accelerate.  I've made a tentative fix by using only the docs from the instances but I think a better fix would be to remove this arg altogether and  keep a clear distinction between it and process_results. Is there a backward compatibility reason not to do that? Do any other tasks other than super_glue-wsc-t5-prompt compare resps to docs in theirfilter function?

Thanks for catching this!
Hm, so we do want the filters to be able to have access to the gold standard answer in some cases, if people will use them for model-based evaluations.  The idea was that if you want to do something like run a model over all the documents, the filter apply() should permit you to load that model a single time and run over all the docs, something not currently possible with process_results().
I think that your fix is probably the right way to currently handle this as a hotfix but sympathetic to what you're saying re: keeping a distinction between process_docs(). I guess the broader change would be to: - move this WSC logic to a custom process_results() - put a deprecation warning if people try to pass docs into filters, and later fully phase it out?
(cc @dwadden who was interested in model-based evaluation in lm-eval, to make sure this change would not break anything for him, and @pminervini who this maybe also affects due to an interest in stateful process_results())

Yes, that makes sense. I guess there isn't a really a reason not to give the option other than to keep things simple. As a compromise, I've kept the Filter class as is but modified the input docs in FilterEnsemble to args.docs (this is the main entrypoint to the filter pipeline from Task). The only major change I can think of is that  the gold standard answers will be list[dict] (one for the respective row) rather than a Dataset object.
Removed some unnecessary and unused looping in task.py while parsing the filters from the config. The results remain the same for TinyLLama on gsm8k, before and after this change.
Also modified the super_glue-wsc-t5-prompt answer processing to use process_results rather than Filter. Now accuracy is the same with and w/o accelerate (0.6058 on TinyLLama)
cc: @lintangsutawika

As a compromise, I've kept the Filter class as is but modified the input docs in FilterEnsemble to args.docs (this is the main entrypoint to the filter pipeline from Task). The only major change I can think of is that the gold standard answers will be list[dict] (one for the respective row) rather than a Dataset object.

Thanks, I think this sounds great in terms of keeping backward compatibility!
This looks good to me, thanks again for chasing this down!

Thanks @baberabb @haileyschoelkopf


Cookie header not set

Steps to reproduce

Puppeteer version: 1.20.0
Platform / OS version: Ubuntu 18.04
Node.js version: 8.15 LTS

What steps will reproduce the problem?
async function makeReport(report) {
  try {

    var tmpDir ='./.tmp'

    const browser = await puppeteer.launch({ headless: false, ignoreHTTPSErrors: true, userDataDir: tmpDir })
    const page = await browser.newPage();

    await page.setRequestInterception(true);

    page.on('request', interceptedRequest => {
      if (interceptedRequest.url().indexOf("/tag/?") >= 0){
        // cookie header with session id is missing here and the session authentication fails
        console.log(interceptedRequest.headers());
        debugger
      }
    });

    await page.goto('https://localhost:' + port + '/report/' + report.id, { waitUntil: 'networkidle0' });

    // Page console log
    page.on('console', msg => {
      for (let i = 0; i < msg.args().length; ++i)
        console.log(`${i}: ${msg.args()[i]}`);
    });

    await page.waitFor(5000)

    await page.emulateMedia('screen');
    await page.pdf({ path: tmpDir + '/report' + report.id + '.pdf', format: 'A4' });

    await browser.close();

  } catch (error) {
    logger.error("Error while doing report", error.message)
  }
}

What is the expected result?
The request to have the cookie correctly set as follow:

What happens instead?
The cookie header is not present on the request and this make the request fail. This are the headers sent when using pappeteer:

@robertsLando Can you please tell me how you solved this?

I'm sorry but I don't remember what fixed the problem, I can show you how I start puppeteer now:
const browser = await puppeteer.launch({
      headless: true,
      args: ['--no-sandbox'],
      ignoreHTTPSErrors: true,
      userDataDir: tmpDir,
      executablePath: execPath
    })

@ritz078 Did you find and solution for this?

@namanisupriya55 I fixed it using this hack https://github.com/puppeteer/puppeteer/issues/4918#issuecomment-663478790