Copy Data from Cosmos to Cosmos NO SQL - Modify the record values for few fields before sending to Target

Azure documentation issue guidance
Thanks for opening an issue in the Azure technical documentation repository.
We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation.
Creating an issue
We prefer that you create documentation feedback issues using the Feedback link on the published article - the feedback control on the doc page creates an issue that contains all the article details so you can focus on the feedback part.
You can also create a feedback issue here in the repo. If you do this, please make sure your issue lists:

[ ] The relevant Azure service or technology.
[ ] A link to the published documentation article that you have feedback about.
[ ] Clear, specific feedback that the author can act on.

Pull requests and article contributions
If you know the change that is needed in an article, we encourage you to submit the changes directly using a pull request. If the change is large, or if you want to contribute an entire article, follow these guidelines:

[ ] Don't surprise us with a big pull request or a pull request with a new article! Submit an issue that describes the details of the proposed large change or new article.
[ ] Include the service or technology area.

We'll route the issue to the appropriate content team for review and discussion.
Tech support and product feedback
If you would like to contact Microsoft about other things, such as product feedback or tech support, please review these guidelines:

If you need technical support using Azure, the paid and free support options are described here: https://azure.microsoft.com/support/options/.

Each article in the Azure technical documentation contains a product feedback button - it's best to submit product feedback directly from a relevant article. Otherwise, you can submit product feedback for most Azure products in the following product feedback forum: https://feedback.azure.com/forums/34192--general-feedback.

Hi Team ,
Scenario - Cosmos to Comos data copy .
We have a scenario of transforming few fields before sending to target cosmos and can you guide us where  to change the code . Is that C:\xyz\Source\azure-documentdb-datamigrationtool-master\DocumentDb\Microsoft.DataTransfer.DocumentDb\Transformation ?  Is there any document or sample provided for this kind of scenario's . Thank You. Regards,Srirama

@sriramaszone, Please help with the link of document on which above document feedback request is created.
In case your query in not related to document content, open a new forum thread in MSDN forum or Stack Overflow as it could be better place to get help on your scenario. These forum community members could provide their expert guidance on your scenario based on their experience. Thanks.

Hi Yaswanth, Here is the  idea proposed and the URL .
https://feedback.azure.com/forums/270578-data-factory/suggestions/37425853-azure-data-factory-cosmos-to-cosmos-data-copy
I see many of them raised this concern in Azure Data factory .  Let me know if there is some other I need to open a new thread in  another forum.

@sriramaszone Thank you for submitting your feedback.
The features are usually prioritized based on the number of users requesting it and built into the product.

We will proceed to close this thread now.
If there are further questions regarding this matter, please comment and we will gladly continue the discussion.

Hi Kalyan, The feedback I provided is about Azure data factory but the question I raised here is on Azure Cosmos DB database migration tool. Can you provide any suggestions regarding the database migration tool. Thank You.

@sriramaszone If you need help for your specific use case, request you to open a new forum thread in  Stack Overflow or MSDN

Hi @KalyanChanumolu-MSFT
I explained here now .
https://social.msdn.microsoft.com/Forums/en-US/1dd2e1df-d213-4c47-9be1-13b100940812/azure-cosmos-db-data-migration-tool-copy-data-from-cosmos-to-cosmos-no-sql-modify-the-record?forum=azurecosmosdb
Thank You.


Update Pod

Hey Daniel,
Could you please release a new patch on CocoaPods containing the fix at #10? My build on Travis is failing because of that :)
Thanks!

Yep, will do a release today.

Yep, will do a release today.

Done!

Done!


new: Select layout

layout added to Select widget
Returns rows with predefined number of buttons.
Select with layout=(1, 2, 3) returns the same as:

Row(buttons[:1]),
Row(buttons[1:3]),
Row(buttons[3:6])

'layout' value should be defined in getter.

Let's transform it to separate widget like Group, so it could be used with any buttons


Django 3.2 please bump release to support it (TextFields db_collation)

Django 3.2 was released.  The main branch has a fix (f5ffdd55a) for TextField support.
Could we please get a 2.12.1 release to support this.

@treyhunner @rossmechanic , just a nudge -- you're the Jazzband project leads who can make a release, right?

Head's up that we've got an incoming PR to prepare the next release https://github.com/jazzband/django-simple-history/pull/819

This is now released on pypi!


Debug logging

Initial PR, to see what Travis and CI report.

Coverage remained the same at 97.561% when pulling c55bde7336c7532d48ee0af8133c472fda9f3f40 on pervazea:debug_logging into 9b98142ab04b679bacca98d0815d8b42a12ad850 on cmu-db:master.

clang-tidy should be ignoring the third_party folder, but it isn't. This is causing Travis to fail.
It looks like HeaderFilterRegex in the .clang-tidy file is what we should be modifying, but I have not been able to appease it yet. I'll keep trying.

#95 should fix third_party CI issues.

Feedback I gave in person but don't want to forget: I think the logger instantiation methods are small enough that we can put their definitions in the headers. The .cpp files are pretty sparse. As far as actually instantiating these, I think we'll need to have them in a Google Test harness so we can log in Google Test. Instantiating loggers in the main() function doesn't help us for Google Tests. We'll have to verify that the proposed harness solution works.

To summarize most recent changes:

Log to console (rather than a file)
Add class for the tests to use, that initializes the logger(s)
Add wiki page with short description of how to use and how to add modules

Wiki page is here for reference:
https://github.com/cmu-db/terrier/wiki/Using-debug-logging

How much did we end up changing the spdlog code (if any) from the master repo? Is it easy to summarize those changes in case we want to bring in a newer version in the future?

The changes to spdlog were small in number and localized, so should be easy to bring in new versions.


build with go >= 1.4.3 to resolve CVE in net/http

The CVE and updates were announced at
https://groups.google.com/forum/#!topic/golang-announce/iSIyW4lM4hY

The issues were reported in Go's net/http package. They affect
programs using that package to proxy HTTP requests. We recommend
that all users upgrade to Go 1.5, which fixes these issues. For
users unable to upgrade to Go 1.5, we have released version 1.4.3,
which is based on Go 1.4.2 plus fixes for these issues. Affected
Go programs—those that use the net/http package as a proxy
server—must be recompiled with Go 1.5 or Go 1.4.3 to receive
the fixes.

The CVE issue descriptions and fixes are linked below.
CVE-2015-5739
"Content Length" treated as valid header:
https://go-review.googlesource.com/#/c/11772/
CVE-2015-5740
Double content-length headers does not return 400 error:
https://go-review.googlesource.com/#/c/11810/
CVE-2015-5741
Additional hardening, not sending Content-Length w/Transfer-Encoding,
Closing connections:
https://go-review.googlesource.com/#/c/11810/
https://go-review.googlesource.com/#/c/12865/
https://go-review.googlesource.com/#/c/13148/

https://circleci.com/gh/jumanjihouse/docker-caddy/37 is clean
:ship:


dist folder missing in package version 0.1.9

I've just upgraded to the latest version and I think the build step was missed when publishing, because he dist folder appears to be missing, which prevents the module from working.

Sorry for that. released 0.1.10

Please Let me know if you have any issues with 0.1.10

0.1.10 appears to work fine. Thank you!


Update rpmbuild files and patches for Go 1.22

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/test

/test all

/lgtm

/approve


PIO Core Call Error: "[WinError 2] The system cannot find the file specified"

Type: Bug
I have Googled this extensively and can come up with no solution.  I've uninstalled my antivirus.  All I'm trying to do is create a project and I get:
PIO Core Call Error: "[WinError 2] The system cannot find the file specified"
I've run as administrator.  I've turned off Windows Defender.  I've deleted the .platformio folder.  I've installed the system VSCode.  I've installed the User VSCode.  I've manually changed permissions on the executable.  Absolutely nothing I do has worked.  What in the heck do I need to do to be able to just create a project??
VS Code version: Code 1.71.0 (784b0177c56c607789f9638da7b6bf3230d47a8c, 2022-09-01T07:36:10.600Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
AMD Ryzen 9 3900X 12-Core Processor             (24 x 3800)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
31.95GB (19.85GB free)

Process Argv
--crash-reporter-id 6b18a9b0-62a5-4d26-8ebb-24a3d072c57f

Screen Reader
no

VM
0%

Extensions (20)

Extension
Author (truncated)
Version

doxdocgen
csc
1.4.0

gc-excelviewer
Gra
4.2.55

latex-workshop
Jam
8.29.0

better-cpp-syntax
jef
1.15.19

bash-ide-vscode
mad
1.14.0

vscode-docker
ms-
1.22.1

csharp
ms-
1.25.0

python
ms-
2022.14.0

vscode-pylance
ms-
2022.9.10

jupyter
ms-
2022.8.1002431955

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.9

remote-containers
ms-
0.251.0

cmake-tools
ms-
1.12.26

cpptools
ms-
1.12.4

cpptools-extension-pack
ms-
1.3.0

platformio-ide
pla
2.5.4

bash-debug
rog
0.3.9

bash-beautify
sha
0.1.1

cmake
twx
0.0.17

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30557514
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
pylanb8912:30545647
vsclangdc:30486549
c4g48928:30535728
hb751961:30553087
dsvsc012:30540252
azure-dev_surveyone:30548225
2144e591:30553903

This looks like an issue with the Platform IO extension. Please file an issue for that. Thanks.

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. If you don't know which extension is causing the problem, you can run Help: Start extension bisect from the command palette (F1) to help identify the problem extension.
Happy Coding!


Update Puppeteer dependencies in Docker image and publish to aws-azure-login repo instead of sportradar

These updates are to get a new official image with the fix for #266.

Updated the runtime dependencies for Puppeteer according to here
Updated the GitHub Actions release workflow to publish to aws-azure-login namespace instead of sportradar
Updated README.md and docker-launch.sh to use aws-azure-login namespace instead of sportradar

thanks for merging @Naicigam28. I saw it failed on credentials. I guess this project needs DOCKER_USERNAME and DOCKER_PASSWORD secrets defined.

@jghal Apologies but I don't have access to set the credentials. This is an ongoing headache for me. Still trying to get in touch with the previous maintainer to resolve this issue


Detect short power outages

Power has not been steady at the airport i previous years.  We can add a check for line power on the APC UPS with a serial cable that looks like Ethernet -> USB A.  Works on Harper's UPS at home and produces an alert from mac exporter when line power fails.

Prometheus may miss short power outages
Figure out how to post a log alert or something so we don't miss and have record of outages.

Bought proper USB -> Serial cables for the UPS's.  They're in the tower container.   Tested on my UPS which is the same unit and we get alerts for when the wall line power goes off.  Power out alerts are logged in Prometheus time series database.  We can plot power in Grafana when we get to it.


revert 1.31 tag to v1.31.0-beta.0

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


Bump urllib3 from 1.25.3 to 1.25.6

Bumps urllib3 from 1.25.3 to 1.25.6.

Release notes
Changelog
Commits

Signed-off-by: dependabot-preview[bot]<EMAIL_ADDRESS>

What is this? It doesn't look like a valid @dependbot or @dependabot-preview Pull Request...
Is this a masquerade attempt?

@tawannacab87 thanks for your Pull Request. it appears to be a duplicate of #6701, which was created by an automated bot configured on this repository.
It's not necessary to create new Pull Requests for these updates.


51 refactoring

@rultor merge

@rultor merge

@doldrums OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@doldrums Oops, I failed. You can see the full log here (spent 7min)
Installing sassc-rails 2.1.2
Fetching sass-rails 6.0.0
Installing sass-rails 6.0.0
Fetching http 5.0.4
Installing http 5.0.4
Fetching simplecov-json 0.2.3
Installing simplecov-json 0.2.3
Bundle complete! 25 Gemfile dependencies, 95 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
Post-install message from rubyzip:
RubyZip 3.0 is coming!
**********************

The public API of some Rubyzip classes has been modernized to use named
parameters for optional arguments. Please check your usage of the
following classes:
  * `Zip::File`
  * `Zip::Entry`
  * `Zip::InputStream`
  * `Zip::OutputStream`

Please ensure that your Gemfiles and .gemspecs are suitably restrictive
to avoid an unexpected breakage when 3.0 is released (e.g. ~> 2.3.0).
See https://github.com/rubyzip/rubyzip for details.  Done

Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 50%

Building dependency tree... 50%

Building dependency tree

Reading state information... 0%

Reading state information... 0%

Reading state information... Done

90 packages can be upgraded. Run 'apt list --upgradable' to see them.
+ set -e
+ pdd -f /dev/null
\u001b[33mWarning: the running version of Bundler (2.1.2) is older than the version that created the lockfile (2.3.24). We suggest you to upgrade to the version that created the lockfile by running `gem install bundler:2.3.24`.
\u001b[0m+ bundle exec rubocop
\u001b[31mbundler: command not found: rubocop\u001b[0m
\u001b[33mInstall missing gem executables with `bundle install`\u001b[0m
container c0a85e009d2bda2161867572c37109c6ac3c20345d361df23d95d1190efcce01 is dead
Mon 07 Nov 2022 12:15:07 AM CET

@rultor merge

@rultor merge

@doldrums OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@doldrums Oops, I failed. You can see the full log here (spent 7min)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
\u001b[36mdb/migrate/20220526085038_creating_github_radar_seed.rb\u001b[0m:3:1: \u001b[33mC\u001b[0m: Style/Documentation: Missing top-level documentation comment for \u001b[33mclass CreatingGithubRadarSeed\u001b[0m.
class CreatingGithubRadarSeed < ActiveRecord::Migration[6.1]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
\u001b[36mdb/migrate/20220526085038_creating_github_radar_seed.rb\u001b[0m:4:3: \u001b[33mC\u001b[0m: Metrics/MethodLength: Method has too many lines. [23/10]
  def up \u001b[33m...\u001b[0m
  ^^^^^^
\u001b[36mdb/migrate/20220606103515_create_tom_pr_comments.rb\u001b[0m:3:1: \u001b[33mC\u001b[0m: Style/Documentation: Missing top-level documentation comment for \u001b[33mclass CreateTomPrComments\u001b[0m.
class CreateTomPrComments < ActiveRecord::Migration[6.1]
^^^^^^^^^^^^^^^^^^^^^^^^^
\u001b[36mdb/migrate/20220606103515_create_tom_pr_comments.rb\u001b[0m:4:3: \u001b[33mC\u001b[0m: Metrics/MethodLength: Method has too many lines. [13/10]
  def change \u001b[33m...\u001b[0m
  ^^^^^^^^^^
\u001b[36mdb/migrate/20220606103552_create_tom_issues_comments.rb\u001b[0m:3:1: \u001b[33mC\u001b[0m: Style/Documentation: Missing top-level documentation comment for \u001b[33mclass CreateTomIssuesComments\u001b[0m.
class CreateTomIssuesComments < ActiveRecord::Migration[6.1]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
\u001b[36mdb/migrate/20220606103552_create_tom_issues_comments.rb\u001b[0m:4:3: \u001b[33mC\u001b[0m: Metrics/MethodLength: Method has too many lines. [13/10]
  def change \u001b[33m...\u001b[0m
  ^^^^^^^^^^
\u001b[36mdb/migrate/20220617084859_adding_archived_flag.rb\u001b[0m:3:1: \u001b[33mC\u001b[0m: Style/Documentation: Missing top-level documentation comment for \u001b[33mclass AddingArchivedFlag\u001b[0m.
class AddingArchivedFlag < ActiveRecord::Migration[6.1]
^^^^^^^^^^^^^^^^^^^^^^^^
\u001b[36mdb/schema.rb\u001b[0m:15:1: \u001b[33mC\u001b[0m: Metrics/BlockLength: Block has too many lines. [452/25]
ActiveRecord::Schema.define(version: 20_220_617_084_859) do \u001b[33m...\u001b[0m
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
\u001b[36mdb/schema.rb\u001b[0m:163:3: \u001b[33mC\u001b[0m: Metrics/BlockLength: Block has too many lines. [84/25]
  create_table 'tom_project_metrics', force: :cascade do |t| \u001b[33m...\u001b[0m
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
\u001b[36mdb/schema.rb\u001b[0m:250:3: \u001b[33mC\u001b[0m: Metrics/BlockLength: Block has too many lines. [84/25]
  create_table 'tom_project_metrics_trains', force: :cascade do |t| \u001b[33m...\u001b[0m
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
\u001b[36mdb/schema.rb\u001b[0m:361:3: \u001b[33mC\u001b[0m: Metrics/BlockLength: Block has too many lines. [27/25]
  create_table 'tom_pull_infos', force: :cascade do |t| \u001b[33m...\u001b[0m
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
\u001b[36mdb/schema.rb\u001b[0m:434:3: \u001b[33mC\u001b[0m: Metrics/BlockLength: Block has too many lines. [26/25]
  create_table 'tom_settings', force: :cascade do |t| \u001b[33m...\u001b[0m
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
\u001b[36mlib/tasks/db.rake\u001b[0m:2:1: \u001b[33mC\u001b[0m: \u001b[33m[Correctable] \u001b[0mLayout/EmptyLineAfterMagicComment: Add an empty line after magic comments.
namespace :db do
^
\u001b[36mlib/tasks/db.rake\u001b[0m:6:7: \u001b[33mC\u001b[0m: \u001b[33m[Correctable] \u001b[0mStyle/RedundantBegin: Redundant \u001b[33mbegin\u001b[0m block detected.
      begin
      ^^^^^
\u001b[36mlib/tasks/db.rake\u001b[0m:20:59: \u001b[33mC\u001b[0m: \u001b[33m[Correctable] \u001b[0mStyle/StringLiterals: Prefer single-quoted strings when you don't need string interpolation or special symbols.
    secret_key = ActiveRecord::Base.connection.select_one("select * from tom_settings")
                                                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
\u001b[36mlib/tasks/db.rake\u001b[0m:25:4: \u001b[33mC\u001b[0m: \u001b[33m[Correctable] \u001b[0mLayout/TrailingEmptyLines: Final newline missing.
end

122 files inspected, \u001b[31m692 offenses\u001b[0m detected, \u001b[33m14 offenses\u001b[0m autocorrectable

Tip: Based on detected gems, the following RuboCop extension libraries might be helpful:
  * rubocop-rails (https://rubygems.org/gems/rubocop-rails)

You can opt out of this message by adding the following to your config (see https://docs.rubocop.org/rubocop/extensions.html#extension-suggestions for more options):
  AllCops:
    SuggestExtensions: false
container 7fc2f899829a3edca1177d71863c7af0418f00fe67b95036697fd1bcef9cb8dd is dead
Mon 07 Nov 2022 12:31:17 AM CET

@rultor merge

@rultor merge

@doldrums We failed, sorry, try again:
 in 'string', line 40, column 3:
      script: |-
      ^
expected <block end>, but found '<scalar>'
 in 'string', line 44, column 5:
        bundle exec bundle-audit check — ...
        ^

	at com.rultor.profiles.YamlXML.get(YamlXML.java:82)
	at com.rultor.profiles.GithubProfile.read(GithubProfile.java:130)
	at com.rultor.agents.github.qtn.QnByArchitect.understand(QnByArchitect.java:106)
	at com.rultor.agents.github.qtn.QnAlone.understand(QnAlone.java:96)
	at com.rultor.agents.github.qtn.QnIfCollaborator.understand(QnIfCollaborator.java:84)
	at com.rultor.agents.github.qtn.QnFirstOf.understand(QnFirstOf.java:81)
	at com.rultor.agents.github.qtn.QnFollow.understand(QnFollow.java:85)
	at com.rultor.agents.github.qtn.QnWithAuthor.understand(QnWithAuthor.java:72)
	at com.rultor.agents.github.qtn.QnParametrized.understand(QnParametrized.java:89)
	at com.rultor.agents.github.qtn.QnReaction.understand(QnReaction.java:96)
	at com.rultor.agents.github.qtn.QnReferredTo.understand(QnReferredTo.java:104)
	at com.rultor.agents.github.qtn.QnNotSelf.understand(QnNotSelf.java:75)
	at com.rultor.agents.github.qtn.QnSince.understand(QnSince.java:79)
	at com.rultor.agents.github.qtn.QnSafe.understand(QnSafe.java:75)
	at com.rultor.agents.github.Understands.parse(Understands.java:197)
	at com.rultor.agents.github.Understands.process(Understands.java:131)
	at com.rultor.agents.AbstractAgent.execute(AbstractAgent.java:70)
	at com.rultor.spi.Agent$Iterative.execute(Agent.java:84)
	at com.rultor.Routine.process(Routine.java:202)
	at com.rultor.Routine.unsafe_aroundBody0(Routine.java:180)
	at com.rultor.Routine$AjcClosure1.run(Routine.java:1)
	at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:179)
	at com.jcabi.aspects.aj.MethodInterrupter.wrap(MethodInterrupter.java:108)
	at com.rultor.Routine.unsafe(Routine.java:175)
	at com.rultor.Routine.run(Routine.java:142)
	at com.jcabi.log.VerboseRunnable.run(VerboseRunnable.java:190)
	at com.jcabi.aspects.aj.MethodScheduler$Service.lambda$0(MethodScheduler.java:194)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
	at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at com.jcabi.log.VerboseThreads$Wrap.run(VerboseThreads.java:222)
	at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: while parsing a block mapping
 in 'string', line 40, column 3:
      script: |-
      ^
expected <block end>, but found '<scalar>'
 in 'string', line 44, column 5:
        bundle exec bundle-audit check — ...
        ^

	at org.yaml.snakeyaml.parser.ParserImpl$ParseBlockMappingKey.produce(ParserImpl.java:679)
	at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:185)
	at org.yaml.snakeyaml.comments.CommentEventsCollector$1.peek(CommentEventsCollector.java:57)
	at org.yaml.snakeyaml.comments.CommentEventsCollector$1.peek(CommentEventsCollector.java:43)
	at org.yaml.snakeyaml.comments.CommentEventsCollector.collectEvents(CommentEventsCollector.java:136)
	at org.yaml.snakeyaml.comments.CommentEventsCollector.collectEvents(CommentEventsCollector.java:116)
	at org.yaml.snakeyaml.composer.Composer.composeScalarNode(Composer.java:239)
	at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:208)
	at org.yaml.snakeyaml.composer.Composer.composeValueNode(Composer.java:357)
	at org.yaml.snakeyaml.composer.Composer.composeMappingChildren(Composer.java:336)
	at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:311)
	at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:212)
	at org.yaml.snakeyaml.composer.Composer.composeValueNode(Composer.java:357)
	at org.yaml.snakeyaml.composer.Composer.composeMappingChildren(Composer.java:336)
	at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:311)
	at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:212)
	at org.yaml.snakeyaml.composer.Composer.getNode(Composer.java:134)
	at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:160)
	at org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:184)
	at org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:477)
	at org.yaml.snakeyaml.Yaml.load(Yaml.java:406)
	at com.rultor.profiles.YamlXML.get(YamlXML.java:80)
	... 33 more

@rultor merge

@rultor merge

@doldrums OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@doldrums Oops, I failed. You can see the full log here (spent 7min)
Fetching rubocop 1.38.0
Fetching simplecov-json 0.2.3
Installing simplecov-json 0.2.3
Installing rubocop 1.38.0
GemWrappers: Can not wrap missing file: rubocop
GemWrappers: Can not wrap missing file: rubocop
Bundle complete! 26 Gemfile dependencies, 103 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
Post-install message from rubyzip:
RubyZip 3.0 is coming!
**********************

The public API of some Rubyzip classes has been modernized to use named
parameters for optional arguments. Please check your usage of the
following classes:
  * `Zip::File`
  * `Zip::Entry`
  * `Zip::InputStream`
  * `Zip::OutputStream`

Please ensure that your Gemfiles and .gemspecs are suitably restrictive
to avoid an unexpected breakage when 3.0 is released (e.g. ~> 2.3.0).
See https://github.com/rubyzip/rubyzip for details.  Done

Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 50%

Building dependency tree... 50%

Building dependency tree

Reading state information... 0%

Reading state information... 0%

Reading state information... Done

90 packages can be upgraded. Run 'apt list --upgradable' to see them.
+ set -e
+ pdd -f /dev/null
\u001b[33mWarning: the running version of Bundler (2.1.2) is older than the version that created the lockfile (2.3.22). We suggest you to upgrade to the version that created the lockfile by running `gem install bundler:2.3.22`.
\u001b[0mResolving dependencies...
+ bundle exec bundle-audit check — update
\u001b[31mbundler: command not found: bundle-audit\u001b[0m
\u001b[33mInstall missing gem executables with `bundle install`\u001b[0m
container 38fbb1a2d9087971aa75cd51bc49a16dcede89f002bc70600b5832c804e4d4ea is dead
Mon 07 Nov 2022 06:17:22 AM CET

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@doldrums @yegor256 Oops, I failed. You can see the full log here (spent 7min)
Fetching simplecov-json 0.2.3
Fetching rubocop 1.38.0
Installing simplecov-json 0.2.3
Installing rubocop 1.38.0
GemWrappers: Can not wrap missing file: rubocop
GemWrappers: Can not wrap missing file: rubocop
Bundle complete! 26 Gemfile dependencies, 103 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
Post-install message from rubyzip:
RubyZip 3.0 is coming!
**********************

The public API of some Rubyzip classes has been modernized to use named
parameters for optional arguments. Please check your usage of the
following classes:
  * `Zip::File`
  * `Zip::Entry`
  * `Zip::InputStream`
  * `Zip::OutputStream`

Please ensure that your Gemfiles and .gemspecs are suitably restrictive
to avoid an unexpected breakage when 3.0 is released (e.g. ~> 2.3.0).
See https://github.com/rubyzip/rubyzip for details.  Done

Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 50%

Building dependency tree... 50%

Building dependency tree

Reading state information... 0%

Reading state information... 0%

Reading state information... Done

90 packages can be upgraded. Run 'apt list --upgradable' to see them.
+ set -e
+ pdd -f /dev/null
\u001b[33mWarning: the running version of Bundler (2.1.2) is older than the version that created the lockfile (2.3.22). We suggest you to upgrade to the version that created the lockfile by running `gem install bundler:2.3.22`.
\u001b[0mResolving dependencies...
+ bundle exec bundle-audit check — update
\u001b[31mbundler: command not found: bundle-audit\u001b[0m
\u001b[33mInstall missing gem executables with `bundle install`\u001b[0m
container f447110dbb06466cf8c8f9042856972b25e65d35831764954061494d86b9f512 is dead
Mon 07 Nov 2022 09:24:20 AM CET

@rultor merge

@rultor merge

@doldrums OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@doldrums Oops, I failed.  You can see the full log here (spent 30min)
Installing http 5.0.4
Fetching sassc-rails 2.1.2
Installing sassc-rails 2.1.2
Fetching sass-rails 6.0.0
Installing sass-rails 6.0.0
Fetching rubocop 1.38.0
Fetching simplecov-json 0.2.3
Installing simplecov-json 0.2.3
Installing rubocop 1.38.0
GemWrappers: Can not wrap missing file: rubocop
GemWrappers: Can not wrap missing file: rubocop
Bundle complete! 26 Gemfile dependencies, 103 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
Post-install message from rubyzip:
RubyZip 3.0 is coming!
**********************

The public API of some Rubyzip classes has been modernized to use named
parameters for optional arguments. Please check your usage of the
following classes:
  * `Zip::File`
  * `Zip::Entry`
  * `Zip::InputStream`
  * `Zip::OutputStream`

Please ensure that your Gemfiles and .gemspecs are suitably restrictive
to avoid an unexpected breakage when 3.0 is released (e.g. ~> 2.3.0).
See https://github.com/rubyzip/rubyzip for details.  Done

Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 50%

Building dependency tree... 50%

Building dependency tree

Reading state information... 0%

Reading state information... 0%

Reading state information... Done

13 packages can be upgraded. Run 'apt list --upgradable' to see them.
+ set -e
+ pdd -f /dev/null
\u001b[33mWarning: the running version of Bundler (2.1.2) is older than the version that created the lockfile (2.3.25). We suggest you to upgrade to the version that created the lockfile by running `gem install bundler:2.3.25`.
\u001b[0mResolving dependencies...
+ service postgresql restart
 * Restarting PostgreSQL 12 database server       \u001b[80G  \u001b[31m*\u001b[39;49m Error: You must run this program as the cluster owner (postgres) or root

\u001b[74G[\u001b[31mfail\u001b[39;49m]
container 5968c7c02a0dc2504bb41ee36e9fd24221331552e0c9db172002d3388fdc3430 is dead
Thu 10 Nov 2022 04:27:08 PM CET

@rultor merge

@rultor merge

@doldrums OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@doldrums Oops, I failed. You can see the full log here (spent 7min)
Using jbuilder 2.11.5
Using json 2.6.1
Using narray <IP_ADDRESS>
Using kmeans-clusterer 0.11.4
Using method_source 1.0.0
Using parallel 1.22.1
Using parser <IP_ADDRESS>
Using pg 1.3.0
Using pivot_table 1.0.0
Using puma 5.6.1
Using rack-mini-profiler 2.3.3
Using rack-proxy 0.7.2
Using thor 1.2.1
Using railties <IP_ADDRESS>
Using sprockets 4.0.2
Using sprockets-rails 3.4.2
Using rails <IP_ADDRESS>
Using rainbow 3.1.1
Using require_all 3.0.0
Using rexml 3.2.5
Using rubocop-ast 1.23.0
Using ruby-progressbar 1.11.0
Using unicode-display_width 2.3.0
Using rubocop 1.38.0
Using rubyzip 2.3.2
Using sassc 2.4.0
Using tilt 2.0.10
Using sassc-rails 2.1.2
Using sass-rails 6.0.0
Using selenium-webdriver 4.1.0
Using semantic_range 3.0.0
Using simplecov-html 0.12.3
Using simplecov_json_formatter 0.1.3
Using simplecov 0.21.2
Using simplecov-json 0.2.3
Using time 0.2.0
Using turbolinks-source 5.2.0
Using turbolinks 5.2.1
Using web-console 4.2.0
Using webdrivers 5.0.0
Using webpacker 5.4.3
\u001b[32mBundle complete! 26 Gemfile dependencies, 103 gems now installed.\u001b[0m
\u001b[32mUse `bundle info [gemname]` to see where a bundled gem is installed.\u001b[0m
+ bundle exec rails db:create:all
Rails couldn't infer whether you are using multiple databases from your database.yml and can't generate the tasks for the non-primary databases. If you'd like to use this feature, please simplify your ERB.
+ bundle exec rails db:migrate
Rails couldn't infer whether you are using multiple databases from your database.yml and can't generate the tasks for the non-primary databases. If you'd like to use this feature, please simplify your ERB.
/home/r/.ruby/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/postgresql_adapter.rb:78: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call
/home/r/.ruby/gems/pg-1.3.0/lib/pg.rb:66: warning: The called method `connect' is defined here
rails aborted!
ActiveRecord::ConnectionNotEstablished: FATAL:  Peer authentication failed for user "rultor"
/home/r/repo/lib/tasks/db.rake:20:in `block (2 levels) in <main>'

Caused by:
PG::ConnectionBad: FATAL:  Peer authentication failed for user "rultor"
/home/r/repo/lib/tasks/db.rake:20:in `block (2 levels) in <main>'
Tasks: TOP => db:migrate => db:pre_migration_check
(See full trace by running task with --trace)
container 5ee78e994d4fa4afcecc21ebd12eaa54cd0319d2394827a46eab3bd01543bdec is dead
Fri 11 Nov 2022 03:10:08 PM CET

@Doldrums I think the problem is related to the fact that you are not using rultor database, but instead a default one. I think you should somewhere in your configs mention the name of the database.

@rultor merge

@rultor merge

@doldrums OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@doldrums Oops, I failed. You can see the full log here (spent 7min)
Using jbuilder 2.11.5
Using json 2.6.1
Using narray <IP_ADDRESS>
Using kmeans-clusterer 0.11.4
Using method_source 1.0.0
Using parallel 1.22.1
Using parser <IP_ADDRESS>
Using pg 1.3.0
Using pivot_table 1.0.0
Using puma 5.6.1
Using rack-mini-profiler 2.3.3
Using rack-proxy 0.7.2
Using thor 1.2.1
Using railties <IP_ADDRESS>
Using sprockets 4.0.2
Using sprockets-rails 3.4.2
Using rails <IP_ADDRESS>
Using rainbow 3.1.1
Using require_all 3.0.0
Using rexml 3.2.5
Using rubocop-ast 1.23.0
Using ruby-progressbar 1.11.0
Using unicode-display_width 2.3.0
Using rubocop 1.39.0
Using rubyzip 2.3.2
Using sassc 2.4.0
Using tilt 2.0.10
Using sassc-rails 2.1.2
Using sass-rails 6.0.0
Using selenium-webdriver 4.1.0
Using semantic_range 3.0.0
Using simplecov-html 0.12.3
Using simplecov_json_formatter 0.1.3
Using simplecov 0.21.2
Using simplecov-json 0.2.3
Using time 0.2.0
Using turbolinks-source 5.2.0
Using turbolinks 5.2.1
Using web-console 4.2.0
Using webdrivers 5.0.0
Using webpacker 5.4.3
\u001b[32mBundle complete! 26 Gemfile dependencies, 103 gems now installed.\u001b[0m
\u001b[32mUse `bundle info [gemname]` to see where a bundled gem is installed.\u001b[0m
+ bundle exec rails db:create:all
Rails couldn't infer whether you are using multiple databases from your database.yml and can't generate the tasks for the non-primary databases. If you'd like to use this feature, please simplify your ERB.
/home/r/.ruby/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/postgresql_adapter.rb:78: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call
/home/r/.ruby/gems/pg-1.3.0/lib/pg.rb:66: warning: The called method `connect' is defined here
FATAL:  Peer authentication failed for user "rultor"
Couldn't create 'rultor' database. Please check your configuration.
rails aborted!
ActiveRecord::ConnectionNotEstablished: FATAL:  Peer authentication failed for user "rultor"

Caused by:
PG::ConnectionBad: FATAL:  Peer authentication failed for user "rultor"

Tasks: TOP => db:create:all
(See full trace by running task with --trace)
container c81427b76ad83d72d1453380d04b861162f182e254136412eb24d1581e9407ce is dead
Tue 15 Nov 2022 11:55:06 AM CET

@Doldrums you have full access to Dockerfile :) You can test is locally, reproduce the error, then fix it either in your build or in the Dockerfile.


[Snyk] Security upgrade antd from 4.19.1 to 5.0.1

Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):

packages/jmix-front-generator/src/generators/react-typescript/app/template/package.json
packages/jmix-front-generator/src/generators/react-typescript/app/template/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Regular Expression Denial of Service (ReDoS) SNYK-JS-MOMENT-2944238
  696

Directory Traversal SNYK-JS-MOMENT-2440688
  589

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Directory Traversal
🦉 Regular Expression Denial of Service (ReDoS)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Refs #24227 -- Removed ManyToManyField special casing in model_to_dict().

See https://code.djangoproject.com/ticket/24227#comment:17

This change makes sense to me. I suppose the instance.pk check is not necessary anymore because the ORM is smart enough not to execute a query in this case?

No, but the coverage report indicates the removed if instance.pk is None line never evaluates to True.

LGTM

Nice, yeah, I'm hoping this doesn't cause other backwards compatibility issues, but I think this is good long-term. :)


Delete virtual machine returns None if succeed

Trying to use the newest version to delete a virtual machine
compute_client = create_compute_client(credentials, subscription_id)
deletion_result = compute_client.virtual_machines.delete(group_name, name)
return deletion_result.result()

After debugging, deletion_result._polling_method._operation.resource is None. Should this return some info about deletion status?

@zechenjiang, I believe this is likely occurring because the async operation has not completed yet. Could you try adding the following line before attempting to view the results:
deletion_result.wait()

@Drewm3 I tried your suggestion and still got None. This only happens when calling deletion api but I can get correct result for creating vm.

Also at least for me it seems that result() function won't return until deletion has been completed.

Thanks @zechenjiang for your feedback. I will identify someone who has more details on the Python SDK to look into this issue.

Hi @zechenjiang, through my initial discussions with development the person I spoke with told me that he believes that None is the standard result for a successful delete. I am following-up with another expert to confirm this belief is correct.

Hi @Drewm3 Thanks so much for the update. Using None as standard result for a successful delete could be misleading and this contradicts the comments in deletion function. Also, may I ask if Azure uses unique error code? network_client.subnets.get() returns "NotFound" as error code while  network_client.virtual_networks.get() return "ResourceNotFound" as error code. Is this design intended? There is no documentation for error code and this makes it difficult for developers to use.

Adding @zikalino to investigate why a response is not being returned here.

@Drewm3 i have ben busy a bit, but I am checking this issue right now

@zikalino agreed to investigate this issue as an issue in the SDK.

the response content and code is determined by service team and the defined swagger. Add "Service Attention" label to include service team to comment on the proper response expected. thanks.


opt delete idToStoragePolicy from PartitionInfo.java

Proposed changes
Issue Number: close #xxx
The partitions' storage policy is saved in both  idToStoragePolicy and idToDataProperty, but idToStoragePolicy will not be written to editLog, this PR deletes the redundant info idToStoragePolicy to simplify partition info.

run buildall

run feut

run feut

run feut

run feut

run feut

run buildall

run feut

run feut


Flyway SQL Server database migration failed using statement delimiter GO

What version of Flyway are you using?
3.2.1 and 4.2.0
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin, SBT plugin, ANT tasks)
ANT tasks
What database are you using (type & version)?
SQL Server 2014. My jdbc SQLServer driver version is 6.0.
What operating system are you using?
Windows 7 64-bit
What did you do?
(Please include the content causing the issue, any relevant configuration settings, and the command you ran)
Put some statements separated with GO delimiter in a single SQL file and wanted to execute it.
What did you expect to see?
That the script should be executed successfully.
What did you see instead?
com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near 'GO'.
The same problem described also here: https://stackoverflow.com/questions/27107498/flyway-sql-server-database-migration-failed-using-statement-delimiter-go

Please include  the smallest possible set of statements that causes this to fail.

e.g.
INSERT INTO TAB_A (A_ID) VALUES (1)
GO
SELECT * FROM TAB_A
But also any other DML or DDL statements (create table, procedure etc.).
The only working case is for instance:
SELECT * FROM TAB_A
GO
SELECT * FROM TAB_B

@axelfontaine
The reason was, that we had set "@" as a delimiter for the described scripts in an ant task runner. As soon as we used "@" to separate the statements everything started working like a charm. The same happened when we switched to MySQL, so it's just our oversight and it's a platform independent problem.
Sorry for the inconvenience.
Kind regards,
Mateusz


Docs improvements for minLines/maxLines

There was confusion over whether minLines and maxLines affect the number of lines of text that can be entered vs. the number of lines visible.  This updates the docs to clarify this.
Docs change only, no tests.
Potential fix for https://github.com/flutter/flutter/issues/80133

test-exempt: only affects comments
btw you typically need a newline before a bullet in our markdown variant, so after landing this please check the output and see if it's what you expect

Thanks all!
I'll write myself a note to check the output.  Hopefully it's ok in the way that it combines with the macro...

✅  All docs output looks correct (e.g. https://master-api.flutter.dev/flutter/material/TextField/minLines.html).


AttributeError when library called from embedded Python (missing sys.argv)

When the library is used with embedded Python (e.g. Postgres extension written in C calling Python, like Multicorn), sys.argv is not defined, which makes the library misbehave, see below.
      File "/usr/local/lib/python2.7/dist-packages/oauth2client/tools.py", line 83, in _CreateArgumentParser
        parser = argparse.ArgumentParser(add_help=False)

      File "/usr/lib/python2.7/argparse.py", line 1575, in __init__
        prog = _os.path.basename(_sys.argv[0])

    AttributeError: 'module' object has no attribute 'argv'

Workaround is to start embedded script with:
import sys

if not hasattr(sys, 'argv'):
    sys.argv  = ['']

Thank you for creating this issue, however, this project is deprecatedand we will only be addressing critical security issues. You can read moreabout this deprecation here.
If you need support or help using this library, we recommend that you ask yourquestion on StackOverflow.
If you still think this issue is relevant and should be addressed, pleasecomment and let us know!


Unable to run dispatch refresh against multiple bot files from same directory

Tool
Name: Dispatch
Version: 1.2.2
OS: Windows 10 Version 1803 (Build 17314.472
Describe the bug
If I run a dispatch refresh command against a bot file everything works great.   If I from that same directory call a dispatch refresh against a different bot file the dispatch model does not get updated.   I believe the reason for this is the first run creates some files (data folder, summary.html, json file and a dispatch file).   When you run it a second time it does not create a new dispatch file and I believe uses the dispatch file from the previous (1st run) as its connection for importing, training, and publishing the dispatch file at the end of the operation.   So it will do the export process against the correct bot file, but then when it does the import process it uses the existing dispatch file which was for a previous run.
To Reproduce
Steps to reproduce the behavior:

Have two different bot files connecting to two different environments in a folder (C:\DispatchError).
Run this command  dispatch refresh --bot C:\DispatchError\Botfile1.bot --secret BOTFIle1_SECRET
Don't remove any of the files or folders that were created in that directory
Run this command dispatch refresh --bot C:\DispatchError\Botfile2.bot --secret BOTFILE2_SECRET
Notice that the dispatch in BotFile2 doesnt get updated and that when the command was running it looked something like this

Exporting services for dispatch...
Exporting BOT2_General LUIS application...
Exporting FAQ QnA kb...
Exporting ChitChat QnA kb...
Creating dispatch LUIS model json...
Creating training data...
Updating BOT1_Dispatch model...
Importing BOT1_Dispatch model...
Training BOT1_Dispatch model...

Expected behavior
I would expect that when I ran the refresh command for Bot2 that it would update the dispatch in the Bot2.bot file.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
[bug]

update published to npmjs.org.


Orbitrap data crash

I tried to read the imzML from a instrument called "MALDI/ESI Injector (Spectroglyph) coupled to Thermo's  Orbitrap Q Exactive Plus." Parsing crashes without any error message. To avoid memory problems I also tried to parse the data on a cluster with 1TB of RAM but it still crashes.
The error code I get from VSCode is roughly connected to a memory heap problem.
Is there a known fix?

Hi Kawue,
how big are the imzml and ibd files?
Did you try to measure the memory usage (with any GUI tool or with htop on LInux) while reading those files?

Hey intsco,
my tested ibd is around 700MB in 32bit precision and 1,4GB in 64bit, the respective imzML is around 38MB, with ~27.000 spectrum entries (unbinned). This is the smallest one that I currently have. I have also bigger ones up to 3.5GB.
I tried to print the memory usage via psutil during the loop where everything crashes, which is the xml loop in __iter_read_spectrum_meta() but it always stood below 100MB. I tried to debug, but the loop just crashes at some point (always the same point).
If I reduce the imzml to ~740 spectras, simply by deleting them it works fine. I also tried to delete from the beginning, the end and around this 740 point to exclude data set problems.
While the VSCode error is related to a heap problem or a heap overflow (local 64bit Windows machine with 32GB RAM) the cluster responded with "corrupted size vs. prev_size", which is a 64bit Linux machine with a maximal RAM usage of 400GB / 1TB.
This is everything I tried so far and every information I have. If you need more information or if I have to execute some specific tests, just tell me.

The file sizes don't look huge. On metaspace2020.eu we have got more than 3k datasets read by pyimzML. I suspect there might be something to do with a particular file or the imzml export software.
Ideally, you'd need to share with us the smallest dataset that still crashes pyimzML so we can reproduce this behaviour.

Feel free to use any cloud storage like Dropbox or Amazon S3. Just send me a link via email

There is something wrong with memory allocation inside Python interpreter. I couldn't figure out if it's a bug in the pyimzML or in the imzml files.
So far, I can offer only a workaround. Installing pyimzMV with Python>=3.6 solved the problem, in my case at least.

Now, as you write memory allocation I remember that somewhere I got that error too.
My former tests were all in Python 3.7. I tested Python 3.6 and 3.5 now and it works as intended. So I guess you meant Python<=3.6.
As long as this problem still exists you may want to include a compatibility note in your readme.
Thanks a lot for your help!

Same error appears again. This time I tried Python 3.5, 3.6 and 3.7. I tested two orbitrap data sets and it appears for both. I am still not sure if it is a data set or a pyimzML problem.

Hi @Kawue ,
Just to double check, you are able to import these imzML files into some other software and can browse the data, right?

I only tried the vendor software and it works there. Every other software I currently use relies on your package.
My colleagues of the biological department tried rMSI, imzMLValidator and msiQuant without success. They will try cardinal today as well.

The newest version of cardinal works.

@Kawue to reproduce the issue we'll need to have some data. Would you mind sharing with us the smallest dataset you have?

It would also be useful to know if you can read the files with https://msireader.wordpress.ncsu.edu/

Although it tells me there is an UUID problem MSiReader is able to read the imzML.
I will send you the smallest test data set via mail.

I did a few tests and it seems to work. Thanks for you help!


fix: add proper version control to deps

Summary

Package tmp release new version 0.2.2 which changes the minimum node version from >=8.17.0 to >=14 which caused any packages that dependent to tmp may broken. This commit lock the tmp version to safe version which would not break any application that depends to<EMAIL_ADDRESS>but running in older NodeJS version (<14).
Test plan
Normal CI/CD test, but on NodeJS <14
Related to source code (for typings update)
Nothing

I really hope you're not using such an old version of NodeJS in a production environment. Version 8 hasn't had any fixes for four years. https://endoflife.date/nodejs
Please update to a newer version (e.g. 18 or 20). You are at risk of security vulnerabilities.


Build and archive problem

It works fine in Simulator,When trying to build and archive with generic ios device,it's giving the following error
Could not find module 'LoadingButtons' for target 'arm64-apple-ios'; found: x86_64-apple-ios-simulator, x86_64.Added x86_64 in valid architectures but it's not working

It's import issue,it's resolved


Input lag in raw input mode (Windows 10)

On a Windows 10 PC, I ran into an odd behavior: when both mouse and keyboard are used simultaneously while RGFW_window_mouseHold() is active, and frame takes a sufficiently long time (e.g. over 30 ms), the while (RGFW_window_checkEvent(win)) loop seems to exit before all events are actually processed, resulting in an accumulating "backlog" of events and manifesting as "lagging input".
I found that it could be mitigated by running the event processing loop twice per frame, but I think this is not actually supposed to happen. Most likely a Windows-specific issue, since it did not occur when testing on Linux.
Here's a small test-case program for easier reproduction of the quirk:
main.txt

@dairin0d Thank you for filing this issue.

while RGFW_window_mouseHold() is active,

RGFW_window_mouseHold enables raw mouse input. This is probably a part of what's causing the problem, so it's important to note.

@dairin0d I personally don't notice the lag. Could you possibly send a video?

@ColleagueRiley Sure! Here's my attempt at recording it:
https://github.com/user-attachments/assets/2a2a9699-9a42-48b8-9b3f-7e3794b28673

@dairin0d Okay, I actually notice it on my system too.
I think the problem might be raw input events also accepting raw key events. Then when raw key events are ignored, it also ignores regular key events.
That's just a theory though and it might be wrong.

@dairin0d I think I was wrong about the raw mouse events also accepting keyboard events.
After looking into this issue I noticed a few problems:

Some mouse event inputs are sent to WM_MOUSEMOVE. X11 does something similar and what I have to do is handle both raw mouse events and regular mouse events ('translating' them to raw movement).

There's a special case for handling mouse events that GLFW handles that I do not handle.

I've updated RGFW to fix both of these problems, but I don't know if they fix this specific issue. (With this (https://github.com/ColleagueRiley/RGFW/commit/f2111d450d89fd4d0de574344d2811cf4bcd4454) commit)
Another problem I noticed is with the example code you sent. In your code you have the line.
RGFW_sleep(50);

This is causing also causing event lag, because and is causing the FPS to be extremely low.
I would suggest you use something like
RGFW_window_checkFPS(win, 60);

In order to wait enough time to slow the program to 60 FPS.

Sorry, got around to taking a look at it only now,
I tried to use the commit you mentioned, and the next after that, and also the current version of RGFW.h in the main branch. Unfortunately, not only do they not fix the original problem (the "backlog of events" still builds up), they also introduce additional weird behavior (I attached below an attempt to record it in my actual project), which seems to manifest as:

sudden big jumps in camera zoom (zoom is controlled by mouse scroll, so normally one wheel tick would change the zoom by a fixed relative amount; but now one wheel tick seems to generate multiple scroll events, so zoom gets incremented many times in the same frame)
"stubborn" camera insisting on returning to a certain angle (camera is controlled by mouse movement in raw input mode)
the app "hanging" for a few seconds when attempting to close the window
possibly other issues that I couldn't single out
I think it would be much better to revert those changes, since the original version seemed to work very well aside from the "event backlog" problem.
https://github.com/user-attachments/assets/a5c126ce-30db-465d-a418-7b5ff5726a3a
Since the project is a CPU-based octree renderer which can take 30 milliseconds on average to render one frame in that scene, the use of RGFW_sleep(50) in the test program was very much deliberate :-)

I decided to take a closer look at the Windows implementation of RGFW_window_checkEvent(), and I think I found the actual culprit of the problem I reported originally: in the switch (msg.message) statement, the default case (unrecognized/unsupported message type) sets win->event.type to 0, and further down the function returns NULL if win->event.type is 0. However, in this case it doesn't mean that the event queue has no messages left to process -- so in the case of unrecognized/unsupported message type, the PeekMessageA() should actually be reattempted again.
When I modified RGFW_window_checkEvent() like shown below, the "accumulating event backlog" indeed stopped from occurring:
peek_message:; // added line

if (PeekMessageA(&msg, win->src.window, 0u, 0u, PM_REMOVE)) {
    switch (msg.message) {
    ...
    default:
        win->event.type = 0;
        break;
    }

    TranslateMessage(&msg);
    DispatchMessageA(&msg);

    // If unsupported message type: message queue might not be exhausted yet, so we need to try peeking the next message
    if (win->event.type == 0) goto peek_message; // added line
}

Hope this would be of some help in solving the issue 🙂

An update: it turns out, the new problems with that commit (https://github.com/ColleagueRiley/RGFW/commit/f2111d450d89fd4d0de574344d2811cf4bcd4454) that I experienced were due to two reasons:

Mouse wheel sending multiple scroll events, and the app "hanging" for a few seconds upon pressing the "close" button, were caused by the line const RAWINPUTDEVICE id = { 0x01, 0x02, 0, NULL };. I got curious what RIDEV_REMOVE does, and it seems that it's required to actually stop receiving messages from an input device. When I reverted that line to the original version, those problems went away.
"Stubborn" camera behavior was caused by the changes in the case WM_MOUSEMOVE: block, which you have mostly reverted in the subsequent commit. so when I applied the same changes to my local version, camera stopped being "stubborn".

The rest of the changes in that commit do not appear to be causing any immediate problems, as far as I can tell from my limited use-case -- so it should be enough to leave the current version as-is, and just add back RIDEV_REMOVE and add proper handling of unrecognized messages. Sorry for getting a bit alarmist earlier 😅

add proper handling of unrecognized messages
What would you suggest for that?

I guess it would depend on your architectural preference for this library:

If you want RGFW_window_checkEvent() to always return either a valid event or NULL, then you'd need to use a loop of some sort, to peek messages until either a recognized one is encountered, or the message queue is empty.
If you want to prioritize users' ability to exit the event-checking loop as soon as they wish, you'd need to return non-NULL if the message was unrecognized. I.e., add a variable (for example, is_unknown_message) that gets set to true when encountering an unrecognized message (the default case), and in the end of RGFW_window_checkEvent() return &win->event if either win->event.type or is_unknown_message are non-zero. Since the users will likely be checking for specific event types anyway and ignoring the rest, encountering a "dummy" event with invalid type code (0) might not even get noticed.

Personally, I'd probably go with the 1st approach, since its behavior would look slightly less odd to the user, and its hypothetical weak point (encountering a sudden huge queue of unrecognized messages) is very unlikely to happen in practice.

@dairin0d

then you'd need to use a loop of some sort, to peek messages until either a recognized one is encountered

This is pretty much what the switch already does. If there is no event NULL is returned. If there is an unrecognized event, it would run the function again, making is so it loops until there is a recognized event or no events.

Oops! Sorry, didn't notice the commit https://github.com/ColleagueRiley/RGFW/commit/e0830f5f362d29cc1734fc3d09efa3b5a1d525d2 you made around the time I was writing the last message, which solves the issue via recursion.
I downloaded the current version of RGFW.h from the main branch and ran into a compilation error (it complains about the line return &win->event.type; returning a wrong type, which was introduced in the commit https://github.com/ColleagueRiley/RGFW/commit/57ced279a7261e411098de1ef16dc876dba26b6d).
I locally fixed it by removing the .type at the end, and after that my program compiled and did not appear to have any problems on Windows. Technically, this issue can now be closed, though I'd prefer to do it once the compilation error is fixed too :-)

Oops, I'm not sure why this didn't send an error to me when I tested it.. Everything should be fixed now! Thanks for filing these issues!

Indeed, everything now works as expected. Glad to be of help!


Revit: add ceiling conversions for 2022

Oops, this is already added to the Revit additional conversions issue


Docker 1.10.3 won't start with dm.no_warn_on_loop_devices option set on SLES 12.1

Output of docker version:
mesos01:/home/fb/DCOS # docker version
Client:
 Version:      1.10.3
 API version:  1.22
 Go version:   go1.5.4
 Git commit:   9e83765
 Built:
 OS/Arch:      linux/amd64
Cannot connect to the Docker daemon. Is the docker daemon running on this host?

Output of docker info:
mesos01:/home/fb/DCOS # docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 2
Server Version: 1.10.3
Storage Driver: devicemapper
 Pool Name: docker-254:5-214680-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 857.7 MB
 Data Space Total: 107.4 GB
 Data Space Available: 2.908 GB
 Metadata Space Used: 1.249 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.146 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Either use `--storage-opt dm.thinpooldev` or use `--storage-opt dm.no_warn_on_loop_devices=true` to suppress this warning.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.03.01 (2015-05-15)
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: host bridge null
Kernel Version: 3.12.59-60.41-default
Operating System: SUSE Linux Enterprise Server 12 SP1
OSType: linux
Architecture: x86_64
CPUs: 32
Total Memory: 31.45 GiB
Name: mesos01
ID: CTEY:KSA7:RH4O:PKSJ:YA6Z:DJ46:ZC6Z:VIJF:7BKD:5DX6:RQZL:XO6K
WARNING: No swap limit support

Additional environment details (AWS, VirtualBox, physical, etc.):
Docker is running on SLES 12.1 VM
mesos01:/home/fb/DCOS # uname -a
Linux mesos01 3.12.59-60.41-default #1 SMP Wed Jun 8 16:11:37 UTC 2016 (22a2799) x86_64 x86_64 x86_64 GNU/Linux

Steps to reproduce the issue:

run

docker daemon  -D -s devicemapper --storage-opt dm.no_warn_on_loop_devices=true

Describe the results you received:
Once apply the --storage-opt dm.no_warn_on_loop_devices=true option to docker,  it won't start.
mesos01:/home/fb/DCOS # docker daemon  -D -s devicemapper --storage-opt dm.no_warn_on_loop_devices=true
DEBU[0000] docker group found. gid: 487
DEBU[0000] Server created for HTTP on unix (/var/run/docker.sock)
DEBU[0000] Using default logging driver json-file
DEBU[0000] [graphdriver] trying provided driver "devicemapper"
DEBU[0000] Cleaning up old shm/mqueue mounts: start.
FATA[0000] Error starting daemon: error initializing graphdriver: devmapper: Unknown option dm.no_warn_on_loop_devices

Any one has a clue? I am running DC/OS installation and get stuck here.

@r0c  Actually, I think we don't handle the dm.no_warn_on_loop_devices  option at all, search the code and git history, I didn't found any code to handle dm.no_warn_on_loop_devices.
Have you ever worked with --storage-opt dm.no_warn_on_loop_devices=true?

That option looks to be only present in the Red Hat fork of Docker, and not in the official build https://github.com/projectatomic/docker/commit/09696bfd68d65a84ee23cba7e4b76386ef8c7b06
However, the warning output we have does contain a message referring to that option, but the pull request adding that message only contained the warning, but not the option; https://github.com/docker/docker/pull/18564.
we should update that warning to remove the reference to that option.


fix: outbound escrow accounting

good job

on the right track, great

great....!!!

Everything seems to have been fixed, and I feel like that's a great thing.

I think this is the best of the layer2 projects I know

✋

🙏

✅

Hello


interactive_marker_twist_server: 2.1.0-1 in 'iron/distribution.yaml' [bloom]

Increasing version of package(s) in repository interactive_marker_twist_server to 2.1.0-1:

upstream repository: https://github.com/ros-visualization/interactive_marker_twist_server.git
release repository: https://github.com/ros-gbp/interactive_marker_twist_server-release.git
distro file: iron/distribution.yaml
bloom version: 0.11.2
previous version for package: null

interactive_marker_twist_server
* Updated CI for Humble.
* fix error for tf2_geometry_msgs
* Add CI workflow
* Reorder imports to pass flake8 linter checks
* Contributors: Byeong-Kyu Ahn, Joey Yang, Tony Baltovski

Holding for Iron sync


[SPARK-33092][SQL] Support subexpression elimination in ProjectExec

What changes were proposed in this pull request?

This patch proposes to add subexpression elimination support into ProjectExec. It can be controlled by spark.sql.subexpressionElimination.enabled config.
Before this change:
val df = spark.read.option("header", true).csv("/tmp/test.csv")
 df.withColumn("my_map", expr("str_to_map(foo, '&', '=')")).select(col("my_map")("foo"), col("my_map")("bar"), col("my_map")("baz")).debugCodegen

L27-40: first str_to_map.
L68:81: second str_to_map.
L109-122: third str_to_map.
/* 024 */   private void project_doConsume_0(InternalRow inputadapter_row_0, UTF8String project_expr_0_0, boolean project_exprIsNull_0_0) throws java.io.IOException {
/* 025 */     boolean project_isNull_0 = true;
/* 026 */     UTF8String project_value_0 = null;
/* 027 */     boolean project_isNull_1 = true;
/* 028 */     MapData project_value_1 = null;
/* 029 */
/* 030 */     if (!project_exprIsNull_0_0) {
/* 031 */       project_isNull_1 = false; // resultCode could change nullability.
/* 032 */
/* 033 */       UTF8String[] project_kvs_0 = project_expr_0_0.split(((UTF8String) references[1] /* literal */), -1);
/* 034 */       for(UTF8String kvEntry: project_kvs_0) {
/* 035 */         UTF8String[] kv = kvEntry.split(((UTF8String) references[2] /* literal */), 2);
/* 036 */         ((org.apache.spark.sql.catalyst.util.ArrayBasedMapBuilder) references[0] /* mapBuilder */).put(kv[0], kv.length == 2 ? kv[1] : null);
/* 037 */       }
/* 038 */       project_value_1 = ((org.apache.spark.sql.catalyst.util.ArrayBasedMapBuilder) references[0] /* mapBuilder */).build();
/* 039 */
/* 040 */     }
/* 041 */     if (!project_isNull_1) {
/* 042 */       project_isNull_0 = false; // resultCode could change nullability.
/* 043 */
/* 044 */       final int project_length_0 = project_value_1.numElements();
/* 045 */       final ArrayData project_keys_0 = project_value_1.keyArray();
/* 046 */       final ArrayData project_values_0 = project_value_1.valueArray();
/* 047 */
/* 048 */       int project_index_0 = 0;
/* 049 */       boolean project_found_0 = false;
/* 050 */       while (project_index_0 < project_length_0 && !project_found_0) {
/* 051 */         final UTF8String project_key_0 = project_keys_0.getUTF8String(project_index_0);
/* 052 */         if (project_key_0.equals(((UTF8String) references[3] /* literal */))) {
/* 053 */           project_found_0 = true;
/* 054 */         } else {
/* 055 */           project_index_0++;
/* 056 */         }
/* 057 */       }
/* 058 */
/* 059 */       if (!project_found_0 || project_values_0.isNullAt(project_index_0)) {
/* 060 */         project_isNull_0 = true;
/* 061 */       } else {
/* 062 */         project_value_0 = project_values_0.getUTF8String(project_index_0);
/* 063 */       }
/* 064 */
/* 065 */     }
/* 066 */     boolean project_isNull_6 = true;
/* 067 */     UTF8String project_value_6 = null;
/* 068 */     boolean project_isNull_7 = true;
/* 069 */     MapData project_value_7 = null;
/* 070 */
/* 071 */     if (!project_exprIsNull_0_0) {
/* 072 */       project_isNull_7 = false; // resultCode could change nullability.
/* 073 */
/* 074 */       UTF8String[] project_kvs_1 = project_expr_0_0.split(((UTF8String) references[5] /* literal */), -1);
/* 075 */       for(UTF8String kvEntry: project_kvs_1) {
/* 076 */         UTF8String[] kv = kvEntry.split(((UTF8String) references[6] /* literal */), 2);
/* 077 */         ((org.apache.spark.sql.catalyst.util.ArrayBasedMapBuilder) references[4] /* mapBuilder */).put(kv[0], kv.length == 2 ? kv[1] : null);
/* 078 */       }
/* 079 */       project_value_7 = ((org.apache.spark.sql.catalyst.util.ArrayBasedMapBuilder) references[4] /* mapBuilder */).build();
/* 080 */
/* 081 */     }
/* 082 */     if (!project_isNull_7) {
/* 083 */       project_isNull_6 = false; // resultCode could change nullability.
/* 084 */
/* 085 */       final int project_length_1 = project_value_7.numElements();
/* 086 */       final ArrayData project_keys_1 = project_value_7.keyArray();
/* 087 */       final ArrayData project_values_1 = project_value_7.valueArray();
/* 088 */
/* 089 */       int project_index_1 = 0;
/* 090 */       boolean project_found_1 = false;
/* 091 */       while (project_index_1 < project_length_1 && !project_found_1) {
/* 092 */         final UTF8String project_key_1 = project_keys_1.getUTF8String(project_index_1);
/* 093 */         if (project_key_1.equals(((UTF8String) references[7] /* literal */))) {
/* 094 */           project_found_1 = true;
/* 095 */         } else {
/* 096 */           project_index_1++;
/* 097 */         }
/* 098 */       }
/* 099 */
/* 100 */       if (!project_found_1 || project_values_1.isNullAt(project_index_1)) {
/* 101 */         project_isNull_6 = true;
/* 102 */       } else {
/* 103 */         project_value_6 = project_values_1.getUTF8String(project_index_1);
/* 104 */       }
/* 105 */
/* 106 */     }
/* 107 */     boolean project_isNull_12 = true;
/* 108 */     UTF8String project_value_12 = null;
/* 109 */     boolean project_isNull_13 = true;
/* 110 */     MapData project_value_13 = null;
/* 111 */
/* 112 */     if (!project_exprIsNull_0_0) {
/* 113 */       project_isNull_13 = false; // resultCode could change nullability.
/* 114 */
/* 115 */       UTF8String[] project_kvs_2 = project_expr_0_0.split(((UTF8String) references[9] /* literal */), -1);
/* 116 */       for(UTF8String kvEntry: project_kvs_2) {
/* 117 */         UTF8String[] kv = kvEntry.split(((UTF8String) references[10] /* literal */), 2);
/* 118 */         ((org.apache.spark.sql.catalyst.util.ArrayBasedMapBuilder) references[8] /* mapBuilder */).put(kv[0], kv.length == 2 ? kv[1] : null);
/* 119 */       }
/* 120 */       project_value_13 = ((org.apache.spark.sql.catalyst.util.ArrayBasedMapBuilder) references[8] /* mapBuilder */).build();
/* 121 */
/* 122 */     }
...

After this change:
L27-40 evaluates the common map variable.
/* 024 */   private void project_doConsume_0(InternalRow inputadapter_row_0, UTF8String project_expr_0_0, boolean project_exprIsNull_0_0) throws java.io.IOException {
/* 025 */     // common sub-expressions
/* 026 */
/* 027 */     boolean project_isNull_0 = true;
/* 028 */     MapData project_value_0 = null;
/* 029 */
/* 030 */     if (!project_exprIsNull_0_0) {
/* 031 */       project_isNull_0 = false; // resultCode could change nullability.
/* 032 */
/* 033 */       UTF8String[] project_kvs_0 = project_expr_0_0.split(((UTF8String) references[1] /* literal */), -1);
/* 034 */       for(UTF8String kvEntry: project_kvs_0) {
/* 035 */         UTF8String[] kv = kvEntry.split(((UTF8String) references[2] /* literal */), 2);
/* 036 */         ((org.apache.spark.sql.catalyst.util.ArrayBasedMapBuilder) references[0] /* mapBuilder */).put(kv[0], kv.length == 2 ? kv[1] : null);
/* 037 */       }
/* 038 */       project_value_0 = ((org.apache.spark.sql.catalyst.util.ArrayBasedMapBuilder) references[0] /* mapBuilder */).build();
/* 039 */
/* 040 */     }
/* 041 */
/* 042 */     boolean project_isNull_4 = true;
/* 043 */     UTF8String project_value_4 = null;
/* 044 */
/* 045 */     if (!project_isNull_0) {
/* 046 */       project_isNull_4 = false; // resultCode could change nullability.
/* 047 */
/* 048 */       final int project_length_0 = project_value_0.numElements();
/* 049 */       final ArrayData project_keys_0 = project_value_0.keyArray();
/* 050 */       final ArrayData project_values_0 = project_value_0.valueArray();
/* 051 */
/* 052 */       int project_index_0 = 0;
/* 053 */       boolean project_found_0 = false;
/* 054 */       while (project_index_0 < project_length_0 && !project_found_0) {
/* 055 */         final UTF8String project_key_0 = project_keys_0.getUTF8String(project_index_0);
/* 056 */         if (project_key_0.equals(((UTF8String) references[3] /* literal */))) {
/* 057 */           project_found_0 = true;
/* 058 */         } else {
/* 059 */           project_index_0++;
/* 060 */         }
/* 061 */       }
/* 062 */
/* 063 */       if (!project_found_0 || project_values_0.isNullAt(project_index_0)) {
/* 064 */         project_isNull_4 = true;
/* 065 */       } else {
/* 066 */         project_value_4 = project_values_0.getUTF8String(project_index_0);
/* 067 */       }
/* 068 */
/* 069 */     }
/* 070 */     boolean project_isNull_6 = true;
/* 071 */     UTF8String project_value_6 = null;
/* 072 */
/* 073 */     if (!project_isNull_0) {
/* 074 */       project_isNull_6 = false; // resultCode could change nullability.
/* 075 */
/* 076 */       final int project_length_1 = project_value_0.numElements();
/* 077 */       final ArrayData project_keys_1 = project_value_0.keyArray();
/* 078 */       final ArrayData project_values_1 = project_value_0.valueArray();
/* 079 */
/* 080 */       int project_index_1 = 0;
/* 081 */       boolean project_found_1 = false;
/* 082 */       while (project_index_1 < project_length_1 && !project_found_1) {
/* 083 */         final UTF8String project_key_1 = project_keys_1.getUTF8String(project_index_1);
/* 084 */         if (project_key_1.equals(((UTF8String) references[4] /* literal */))) {
/* 085 */           project_found_1 = true;
/* 086 */         } else {
/* 087 */           project_index_1++;
/* 088 */         }
/* 089 */       }
/* 090 */
/* 091 */       if (!project_found_1 || project_values_1.isNullAt(project_index_1)) {
/* 092 */         project_isNull_6 = true;
/* 093 */       } else {
/* 094 */         project_value_6 = project_values_1.getUTF8String(project_index_1);
/* 095 */       }
/* 096 */
/* 097 */     }
/* 098 */     boolean project_isNull_8 = true;
/* 099 */     UTF8String project_value_8 = null;
/* 100 */
...

When the code is split into separated method:
/* 026 */   private void project_doConsume_0(InternalRow inputadapter_row_0, UTF8String project_expr_0_0, boolean project_exprIsNull_0_0) throws java.io.IOException {
/* 027 */     // common sub-expressions
/* 028 */
/* 029 */     MapData project_subExprValue_0 = project_subExpr_0(project_exprIsNull_0_0, project_expr_0_0);
/* 030 */
...
/* 140 */   private MapData project_subExpr_0(boolean project_exprIsNull_0_0, org.apache.spark.unsafe.types.UTF8String project_expr_0_0) {
/* 141 */     boolean project_isNull_0 = true;
/* 142 */     MapData project_value_0 = null;
/* 143 */
/* 144 */     if (!project_exprIsNull_0_0) {
/* 145 */       project_isNull_0 = false; // resultCode could change nullability.
/* 146 */
/* 147 */       UTF8String[] project_kvs_0 = project_expr_0_0.split(((UTF8String) references[1] /* literal */), -1);
/* 148 */       for(UTF8String kvEntry: project_kvs_0) {
/* 149 */         UTF8String[] kv = kvEntry.split(((UTF8String) references[2] /* literal */), 2);
/* 150 */         ((org.apache.spark.sql.catalyst.util.ArrayBasedMapBuilder) references[0] /* mapBuilder */).put(kv[0], kv.length == 2 ? kv[1] : null);
/* 151 */       }
/* 152 */       project_value_0 = ((org.apache.spark.sql.catalyst.util.ArrayBasedMapBuilder) references[0] /* mapBuilder */).build();
/* 153 */
/* 154 */     }
/* 155 */     project_subExprIsNull_0 = project_isNull_0;
/* 156 */     return project_value_0;
/* 157 */   }

Why are the changes needed?

Users occasionally write repeated expression in projection. It is also possibly that query optimizer optimizes a query to evaluate same expression many times in a Project. Currently in ProjectExec, we don't support subexpression elimination in Whole-stage codegen. We can support it to reduce redundant evaluation.
Does this PR introduce any user-facing change?

No
How was this patch tested?

spark.sql.subexpressionElimination.enabled is enabled by default. So that's said we should pass all tests with this change.

cc @cloud-fan @maropu @dongjoon-hyun

Test build #129543 has started for PR 29975 at commit 34c1164.

Test build #129545 has started for PR 29975 at commit 59e3ee3.

sorry for my bad memory, is it an existing issue that subexpression elimination can cause perf regression because of the eager execution?

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34150/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34151/

Test build #129545 has finished for PR 29975 at commit 59e3ee3.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Test build #129543 has finished for PR 29975 at commit 34c1164.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/129543/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/129545/
Test FAILed.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34150/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/34150/
Test PASSed.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34151/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/34151/
Test PASSed.

retest this please

Test build #129549 has started for PR 29975 at commit 59e3ee3.

(To check the running time of Jenkins jobs...)

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34155/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34155/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/34155/
Test PASSed.

Test build #129549 has finished for PR 29975 at commit 59e3ee3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/129549/
Test FAILed.

https://github.com/apache/spark/pull/29975#issuecomment-705356435

sorry for my bad memory, is it an existing issue that subexpression elimination can cause perf regression because of the eager execution? e.g. an expression is inside a condition branch (e.g. CASE WHEN) and may not be evaluated.

It's possible to cause performance regression, but I don't think conditional expressions are going to be an issue. From the latest Spark master: https://github.com/apache/spark/blob/5effa8ea261ba59214afedc2853d1b248b330ca6/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/EquivalentExpressions.scala#L81-L97
You can see that CSE excludes the conditional branches from conditional expressions, so you won't have expressions accidentally hoisted from those branches.

This PR looks good to me in general, thanks for making this change!

Test build #129567 has started for PR 29975 at commit 0d958e9.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34173/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34173/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/34173/
Test PASSed.

Test build #129567 has finished for PR 29975 at commit 0d958e9.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class SubExprCodes(

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/129567/
Test FAILed.

Test build #129577 has started for PR 29975 at commit fe92bfe.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34182/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34182/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/34182/
Test PASSed.

Test build #129577 has finished for PR 29975 at commit fe92bfe.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/129577/
Test FAILed.

retest this please

Test build #129584 has started for PR 29975 at commit fe92bfe.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34189/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34189/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/34189/
Test PASSed.

Test build #129584 has finished for PR 29975 at commit fe92bfe.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/129584/
Test PASSed.

Test build #129650 has started for PR 29975 at commit 2414bb0.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34254/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34254/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/34254/
Test PASSed.

Test build #129650 has finished for PR 29975 at commit 2414bb0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/129650/
Test PASSed.

Thanks! Merged to master.

NOTE: I also resolved SPARK-32989 with Fix Version/s=3.1.0, too.

Thanks all!


🐛 BUG: Module Dependencies non-relative URL

Quick checklist

[X] I am using the latest version of Snowpack and all plugins.

What package manager are you using?
npm
What operating system are you using?
Linux
Describe the bug
When I run npx snowpack build, my if any of my modules e.g. Bootstrap have dependencies, the path is correct in the import.
However, if I run npx snowpack build --watch, the dependencies don't use relative imports. e.g.
In the bootstrap.v5.0.0-beta3.js file, I see:
import * as Popper from<EMAIL_ADDRESS>This 404s as the file can't be found. If I modify the cached file and change the file path to:
import * as Popper from<EMAIL_ADDRESS>The import works. The other imports all work, it's just the npm modules that need to import other modules.
My config is just running on defaults, but I can't understand why it wouldn't be running the same as npx snowpack build.
Steps to reproduce

npx snowpack build --watch

Link to minimal reproducible example (optional)
No response

After reading this comment in Chart.js plugin GitHub page, I downgraded my Snowpack to 2.10.1 and the import path is correct. Interesting, as this is also a interpackage import.

Weirdly, after a bit of testing, this works on the first compile in 2.10.1, then on change, the above Chart.js imports are broken.

I used a temporal workaround here: https://github.com/FredKSchott/snowpack/pull/3597#issuecomment-1126872074


Update embedded-canvas-app-properties-actions.md

Added important note on OnDataRefresh save scenario

@ericregnier - thanks for your feedback. After a few internal discussions members of the Power Apps engineering team, we decided to expand on your pull request to better clarify saving data in an embedded canvas app. That rework will be published in a few hours and notice the link from this article for more information about saving data in an embedded canvas app.
Closing issue without merging.


Fix due to sleuth sampler property change

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Francesco Fazzini seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Additional text regarding peers

Reminder to take advantage of peers to get assistance when needed

[x] I have read freeCodeCamp's contribution guidelines.
[ ] 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.
[ ] 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

reminder to take advantage of peers added to the last sentence of the article


Exception: Friendship class can not be instanciated directly!

2020-06-04 09:40:40,051 - Wechaty - INFO - receive  event <EventFriendshipPayload(friendship_id='4358696816800085475')>
2020-06-04 09:40:40 INFO wechaty.py <friendship_listener> receive  event <EventFriendshipPayload(friendship_id='4358696816800085475')>
2020-06-04 09:40:40,051 - FriendShip - INFO - Friendship constructor<PHONE_NUMBER>800085475
2020-06-04 09:40:40 INFO friendship.py <init> Friendship constructor<PHONE_NUMBER>800085475
2020-06-04 09:40:40 ERROR base_events.py <default_exception_handler> Exception in callback AsyncIOEventEmitter._emit_run.._callback(<Task finishe...d directly!')>) at /usr/local/lib/python3.7/site-packages/pyee/_asyncio.py:55
handle: <Handle AsyncIOEventEmitter._emit_run.._callback(<Task finishe...d directly!')>) at /usr/local/lib/python3.7/site-packages/pyee/_asyncio.py:55>
Traceback (most recent call last):
File "/usr/local/lib/python3.7/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/local/lib/python3.7/site-packages/pyee/_asyncio.py", line 62, in _callback
self.emit('error', exc)
File "/usr/local/lib/python3.7/site-packages/pyee/_base.py", line 111, in emit
self._emit_handle_potential_error(event, args[0] if args else None)
File "/usr/local/lib/python3.7/site-packages/pyee/_base.py", line 83, in _emit_handle_potential_error
raise error
File "/usr/local/lib/python3.7/site-packages/wechaty/wechaty.py", line 389, in friendship_listener
friendship = self.Friendship.load(payload.friendship_id)
File "/usr/local/lib/python3.7/site-packages/wechaty/user/friendship.py", line 81, in load
return cls(friendship_id)
File "/usr/local/lib/python3.7/site-packages/wechaty/user/friendship.py", line 69, in init
'Friendship class can not be instanciated directly!')
Exception: Friendship class can not be instanciated directly!

This is a known bug in python-wechaty,  please keep eye on new version.  Thank you for your issue.

@why2lyj this bug is fixed now. You can install the latest python-wechaty version. If you have no question, I will close this issue in one day.

@why2lyj this bug is fixed now. You can install the latest python-wechaty version. If you have no question, I will close this issue in one day.

let's close this issue, it wont happen after using new version, but I will still keep eyes on it.

The bug still exists.
Below is my bot code:
class DingDongBot(Wechaty):
    # ...
    async def on_friendship(self, friendship: Friendship):
        print(friendship)
        print(friendship.type()

async def main():
    bot = DingDongBot()
    await bot.start()

And when I make a add friendship request to the bot user, the below error occured:

And then, I comment out the below lines under friendship.py:
def __init__(self, friendship_id: str):
        """
        initialization constructor for friendship
        """
        self.friendship_id = friendship_id
        self._payload: Optional[FriendshipPayload] = None

        log.info('Friendship constructor %s', friendship_id)

        # if self.__class__ is Friendship:
        #     raise Exception(
        #         'Friendship class can not be instanciated directly!')
        if self.puppet is None:
            raise Exception(
                'Friendship class can not be instanciated without a puppet!')

And then retry to make a friendship request to the bot user, another error occured:
INFO:FriendShip:Friendship constructor<PHONE_NUMBER>800708622
Friendship
/home/alfred/app/python-wechaty-getting-started/python-wechaty/src/wechaty/user/friendship.py:128: RuntimeWarning: coroutine 'Friendship.ready' was never awaited
  self.ready()
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
2020-06-25 10:20:32,019 - Wechaty - ERROR - internal error <can"t load friendship payload>
ERROR:Wechaty:internal error <can"t load friendship payload>

Finally the above issue is fixed in python-wecahty-puppet-hostie, and the main problem this issue is because the Friendship.is_ready function is incorrect. I've fixed them and here comes the PR.


Fixed error codes according to Kafka Sources

Some errors have not been mapped correctly or at all compared to
https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/common/protocol/Errors.java
https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/common/ErrorMapping.scala
I corrected/added them.

Pull request seem to be stale, assigning @PragmaticCypher as the responsible developer.


Is this compatible with Sonoff 4CHR3?

Is this compatible with Sonoff 4CHR3?
https://sonoff.tech/product/wifi-diy-smart-switches/4chr3-4chpror3

I just ordered one Sonoff 4CHR3 so I will answer the question myself, yes it is compatible


BUG - Campaign Lifetime Budget Updates Does Not Send List

Describe the bug
The Lifetime Budget update fails because it does not wrap the CampaignUpdateRequest in a list like the Daily Budget update.
If a Life time budget update is attempted we receive the following error:
Invalid type for variable 'campaign_update_request'. Required value type is list and passed type was CampaignUpdateRequest at ['campaign_update_request']
To Reproduce
Steps to reproduce the behavior:

The model/class with an issue is  pinterest/ads/Campaigns.py
The function with an issue is set_lifetime_budget(self, new_spend_cap:int)
The arguments passed to the model/function are any positive integer value
The error thrown is 'Invalid type for variable 'campaign_update_request'. Required value type is list and passed type was CampaignUpdateRequest at ['campaign_update_request']

Expected behavior
I would expect the CampaignUpdateRequest object to be wrapped in a list object like the set_daily_budget function in the same class.
Screenshots

Additional Details (please complete the following information):

OS and Version: MacOS and Windows
SDK Version [all versions]

Additional Context
n/a

Fixed in #140
Made a new release. Available in pinterest-api-sdk==0.2.4


Add version: LuaLS.lua-language-server version 2.6.7

Pull request has been created with Komac v1.9.1 :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/116135&drop=dogfoodAlpha

@wingetbot waivers Add Validation-Executable-Error


Document pluralization order

Knowing the delimiter is "||||" is useful, but to format our translations correctly it's also useful to know the order of:

"zero"
"one"
"two"
"few"
"many"
"other"

Why us '||||' as the delimiter?  Why not use an array or object which are more natural structures in JavaScript?

@hekevintran the |||| is an artifact of the Airbnb translation system.  It could be possible to allow Polyglot to also support a different data structure, like an object or array.

:+1: for a documentation on this :)

:+1: for a documentation on this :)

:+1: for docs

A good example: http://i18njs.com/#pluralisation

http://i18njs.com/#pluralisation


Recreate Table 2 in the 2018 GOATOOLS publication

Currently, I wish to use the biological process groupings in the D1 Alias column of Table 2. However, I've had some trouble getting my counts to match.
My issues may be due to the (potentially depreciated?) goslim_generic file, but I cannot tell for sure. For instance, I get 12k terms in the cellular process group A instead of 19k shown in Table 2. Would you be able to share source code for Table 2? I would like to ensure my groupings are correct so that I can use this function

I have created a script and added it to the GOATOOLS tests directory, tests/wr_tbl2_goatools_d1.py.
This script will exactly match the numbers in Table 2 if you use go-basic.obo that we used to generate the tables, located in the goatools_simulation repo. I removed many D1 GO terms so the table would fit for publication, but still transmit the idea that the depth-01 have highly skewed numbers of descendants.
It is likely that your difference of seeing 12k terms vs our 19k terms for cellular process is due to not using optional relationships, like part_of. We tried grouping with and without relationships and found that it worked much better and was far less laborious to create a sections file if we always use relationships for grouping.


prusa-slicer: 2.6.0 -> 2.6.1

Description of changes
Update to latest version. Updating to the new release built and works without hitch.
Upstream release: https://github.com/prusa3d/PrusaSlicer/releases/tag/version_2.6.1
Release log recorded in the 2.6.1-RC1 and 2.6.1-RC2 releases.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1099


Tried resolving issue 4256. Made text changes for PyPI-specific langu…

…age.
Made two documentation changes regarding feedback section, so that users know it should relate to PyPI only.
Fixes #4256.

Thanks @soulbliss!

My pleasure!


Update terraform/aws to support terraform version 0.7.x

supersedes #171
/cc @enxebre

@enxebre I've granted permission for you to commit to this branch in my repo, if you'd prefer to make any further edits.
Also suggest checking out github's "Squash & Merge" option if you'd like to keep the commit history clean.

Hey @tamsky thanks for the suggestion! I'm sorry if my last comment here https://github.com/Capgemini/kubeform/pull/172/commits/bea178174958845c1aba0a274efcd40c13d6a4b8 was confuse, the bit that we should remove is terraform apply -target=null_resource.etcd_discovery_url
We don't need that step.
The file is already in the repo, so "${file(var.etcd_discovery_url_file)}" won't complain when creating the resource graph.
Then the null resource will populate the file with the right value right before creating the new vm at execution time.
Don't you agree?
After that we can merge!

Just tested now.

Don't you agree?

I agree!
Squash & merge away.

I have updated the private-cloud tree with the changes I was able to identify.
terraform plan now runs cleanly.
Also found this syntax/typo that probably should have been caught before by any test that ran terraform plan.
Given that there is no README for this directory, I'm not testing terraform apply
@enxebre please test private-cloud if your org is still using that directory.
Thanks!

@enxebre also, what do you want to do regarding the outputs that exist in private-cloud but are missing from public-cloud:
https://github.com/tamsky/kubeform/blob/terraform-0.7.x/terraform/aws/private-cloud/main.tf#L80-L95

@tamsky this is good to go. thanks for contributing!