Peer certificate cannot be authenticated with given CA certificates

I am getting the following error with an HTML agent:
Peer certificate cannot be authenticated with given CA certificates
I am running huginn in Docker, just for information.
[00:00:00] INFO -- : Dry Run started
[00:00:00] INFO -- : Fetching https://vacature.beta.tudelft.nl/vacaturesite?functiontype=&discipline=&domain=38&level=&lang=en
[00:00:00] ERROR -- : Error when fetching url: Peer certificate cannot be authenticated with given CA certificates
/app/vendor/bundle/ruby/2.5.0/gems/typhoeus-1.3.1/lib/typhoeus/adapters/faraday.rb:106:in `block in request'
/app/vendor/bundle/ruby/2.5.0/gems/typhoeus-1.3.1/lib/typhoeus/request/callbacks.rb:146:in `block in execute_callbacks'
/app/vendor/bundle/ruby/2.5.0/gems/typhoeus-1.3.1/lib/typhoeus/request/callbacks.rb:145:in `each'
/app/vendor/bundle/ruby/2.5.0/gems/typhoeus-1.3.1/lib/typhoeus/request/callbacks.rb:145:in `execute_callbacks'
/app/vendor/bundle/ruby/2.5.0/gems/typhoeus-1.3.1/lib/typhoeus/request/operations.rb:35:in `finish'
/app/vendor/bundle/ruby/2.5.0/gems/typhoeus-1.3.1/lib/typhoeus/easy_factory.rb:164:in `block in set_callback'
/app/vendor/bundle/ruby/2.5.0/gems/ethon-0.12.0/lib/ethon/easy/response_callbacks.rb:68:in `block in complete'
/app/vendor/bundle/ruby/2.5.0/gems/ethon-0.12.0/lib/ethon/easy/response_callbacks.rb:68:in `each'
/app/vendor/bundle/ruby/2.5.0/gems/ethon-0.12.0/lib/ethon/easy/response_callbacks.rb:68:in `complete'
/app/vendor/bundle/ruby/2.5.0/gems/ethon-0.12.0/lib/ethon/easy/operations.rb:33:in `perform'
/app/vendor/bundle/ruby/2.5.0/gems/typhoeus-1.3.1/lib/typhoeus/request/operations.rb:16:in `run'
/app/vendor/bundle/ruby/2.5.0/gems/typhoeus-1.3.1/lib/typhoeus/request/cacheable.rb:18:in `run'
/app/vendor/bundle/ruby/2.5.0/gems/typhoeus-1.3.1/lib/typhoeus/request/block_connection.rb:31:in `run'
/app/vendor/bundle/ruby/2.5.0/gems/typhoeus-1.3.1/lib/typhoeus/request/stubbable.rb:25:in `run'
/app/vendor/bundle/ruby/2.5.0/gems/typhoeus-1.3.1/lib/typhoeus/request/before.rb:26:in `run'
/app/vendor/bundle/ruby/2.5.0/gems/typhoeus-1.3.1/lib/typhoeus/adapters/faraday.rb:82:in `perform_request'
/app/vendor/bundle/ruby/2.5.0/gems/typhoeus-1.3.1/lib/typhoeus/adapters/faraday.rb:72:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/faraday_middleware-0.12.2/lib/faraday_middleware/gzip.rb:24:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/faraday-0.12.1/lib/faraday/request/url_encoded.rb:15:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/faraday-0.12.1/lib/faraday/request/multipart.rb:15:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/faraday_middleware-0.12.2/lib/faraday_middleware/response/follow_redirects.rb:78:in `perform_with_redirection'
/app/vendor/bundle/ruby/2.5.0/gems/faraday_middleware-0.12.2/lib/faraday_middleware/response/follow_redirects.rb:66:in `call'
/app/app/concerns/web_request_concern.rb:26:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/faraday-0.12.1/lib/faraday/rack_builder.rb:139:in `build_response'
/app/vendor/bundle/ruby/2.5.0/gems/faraday-0.12.1/lib/faraday/connection.rb:386:in `run_request'
/app/vendor/bundle/ruby/2.5.0/gems/faraday-0.12.1/lib/faraday/connection.rb:149:in `get'
/app/app/models/agents/website_agent.rb:397:in `check_url'
/app/app/models/agents/website_agent.rb:386:in `block in check_urls'
/app/app/models/agents/website_agent.rb:385:in `each'
/app/app/models/agents/website_agent.rb:385:in `check_urls'
/app/app/models/agents/website_agent.rb:379:in `check'
/app/app/concerns/sortable_events.rb:92:in `check'
/app/app/concerns/dry_runnable.rb:31:in `dry_run!'
/app/app/controllers/agents/dry_runs_controller.rb:41:in `create'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/basic_implicit_render.rb:6:in `send_action'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/base.rb:194:in `process_action'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rendering.rb:30:in `process_action'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/callbacks.rb:42:in `block in process_action'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:132:in `run_callbacks'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/callbacks.rb:41:in `process_action'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rescue.rb:22:in `process_action'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:34:in `block in process_action'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:168:in `block in instrument'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:23:in `instrument'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:168:in `instrument'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:32:in `process_action'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/params_wrapper.rb:256:in `process_action'
/app/vendor/bundle/ruby/2.5.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/railties/controller_runtime.rb:24:in `process_action'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/base.rb:134:in `process'
/app/vendor/bundle/ruby/2.5.0/gems/actionview-<IP_ADDRESS>/lib/action_view/rendering.rb:32:in `process'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal.rb:191:in `dispatch'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal.rb:252:in `dispatch'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:52:in `dispatch'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:34:in `serve'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/journey/router.rb:52:in `block in serve'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/journey/router.rb:35:in `each'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/journey/router.rb:35:in `serve'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:840:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/warden-1.2.8/lib/warden/manager.rb:36:in `block in call'
/app/vendor/bundle/ruby/2.5.0/gems/warden-1.2.8/lib/warden/manager.rb:34:in `catch'
/app/vendor/bundle/ruby/2.5.0/gems/warden-1.2.8/lib/warden/manager.rb:34:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/rack-2.0.6/lib/rack/tempfile_reaper.rb:15:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/rack-2.0.6/lib/rack/etag.rb:25:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/rack-2.0.6/lib/rack/conditional_get.rb:38:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/rack-2.0.6/lib/rack/head.rb:12:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/http/content_security_policy.rb:18:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/rack-2.0.6/lib/rack/session/abstract/id.rb:232:in `context'
/app/vendor/bundle/ruby/2.5.0/gems/rack-2.0.6/lib/rack/session/abstract/id.rb:226:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/cookies.rb:670:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/callbacks.rb:28:in `block in call'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:98:in `run_callbacks'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/callbacks.rb:26:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/debug_exceptions.rb:61:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/show_exceptions.rb:33:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/railties-<IP_ADDRESS>/lib/rails/rack/logger.rb:38:in `call_app'
/app/vendor/bundle/ruby/2.5.0/gems/railties-<IP_ADDRESS>/lib/rails/rack/logger.rb:26:in `block in call'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:71:in `block in tagged'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:28:in `tagged'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:71:in `tagged'
/app/vendor/bundle/ruby/2.5.0/gems/railties-<IP_ADDRESS>/lib/rails/rack/logger.rb:26:in `call'
/app/config/initializers/silence_worker_status_logger.rb:3:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/remote_ip.rb:81:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/request_id.rb:27:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/rack-2.0.6/lib/rack/method_override.rb:22:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/rack-2.0.6/lib/rack/runtime.rb:22:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/executor.rb:14:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/static.rb:127:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/rack-2.0.6/lib/rack/sendfile.rb:111:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/railties-<IP_ADDRESS>/lib/rails/engine.rb:524:in `call'
/app/vendor/bundle/ruby/2.5.0/gems/rack-2.0.6/lib/rack/handler/webrick.rb:86:in `service'
/usr/lib/ruby/2.5.0/webrick/httpserver.rb:140:in `service'
/usr/lib/ruby/2.5.0/webrick/httpserver.rb:96:in `run'
/usr/lib/ruby/2.5.0/webrick/server.rb:307:in `block in start_thread'
[00:00:00] INFO -- : Dry Run finished

I have no idea why this is happening lately, the certificate is invalid on all linux machines I tested, but works fine on OSX.
You can set disable_ssl_verification: true as a option for the WebsiteAgent to disable the certificate verification.


fix: increase iceberg retries in integration tests

Description
The iceberg retries integration test is the most problematic. Sometimes, it passes, and sometimes, it does not.
Currently the test dues 10 parallel inserts. The idea of this PR is to increase num_iceberg_retries to a value big enough, to allow the test to pass.
Checklist

[ ] You followed contributing section
[ ] You kept your Pull Request small and focused on a single feature or bug fix.
[ ] You added unit testing when necessary
[ ] You added functional testing when necessary

@mikealfare @colin-rogers-dbt FYI.

Input required and not supplied: aws-region
Integration tests seems failing because there is a missing region @mikealfare

Input required and not supplied: aws-region

Integration tests seem to be failing because there is a missing region @mikealfare
I believe that the issue is because here, my user (and every other user that contribute) don't have access to the variable. If the variable is set on your organization level, I cannot certenly use it. But if the variable is set on the repo level, I should be able to use it - as it used to be in the old dbt-athena repo.

The region is there. This looks like it's related to the aws-creds action. It started failing for me after last night for v2, but v4 passes. I have another PR that was affectd that has that fix. So when I get that merged in, I'll sync this PR and all should be fine

@mikealfare any updates here? Integrations tests seems still not working, even after merging the latest from master

Turning it off and on again


Release the mutex also when no dict results from analysis.

I have added a test that made the test hang before the change to the native code.
The modification of the cover.c code changes the abrupt return in the bad-case into just not storing the dict and returning through the same cleanup as the good case uses. The test then no longer gets stuck.
I hit this in production from trying to make a dict from too little entropy it seems.(?)

Codecov Report

Merging #108 into master will increase coverage by 0.37%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #108      +/-   ##
============================================
+ Coverage     61.92%   62.29%   +0.37%
- Complexity      150      151       +1
============================================
  Files            14       14
  Lines           801      801
  Branches        124      124
============================================
+ Hits            496      499       +3
+ Misses          182      180       -2
+ Partials        123      122       -1

This is fixed upstream: https://github.com/facebook/zstd/blob/dev/lib/dictBuilder/cover.c#L922 in the same way. So it will not be burden to maintain in the future.


Check entity relevance for rendering

Solves #2412.
As stated in the linked issue, I was looking for a way to always render an entity's mesh, given that the entity is always relevant. Therefore, I changed the render check to include the relevance of the entity.
With this change, an entity that holds MeshComponent and LocationComponent with alwaysRelevant being false is handled like before, i.e., the mesh is only renderd when the chunk around it is loaded.
Setting alwaysRelevant to true will cause the mesh to be rendered at the given location, regardless whether the chunk around is loaded or not.
Pinging @immortius @flo @msteiger @Josharias @emanuele3d for quick review.

Hooray Jenkins reported success with all tests good!

Hooray Jenkins reported success with all tests good!

@flo any remaining comments before we merge this? Referencing #2412
@emanuele3d & @tdgunes - also a last reference ping, just in case :-)

The change is fine by me

It's good to have it fixed

Merged then :-)
Tested in Light & Shadow, although not thoroughly (kept spawning inside or near the dome this time).
While testing I discovered had to bump the ItemRendering dependency across a few modules, as it recently went from v.0.1 to v0.2. IIRC despite only being a minor version bump on IR since it is still below v1.0.0 the minor effectively counts as major for in-game compatibility checking. Actual compilation was fine, the issue only appeared at runtime.

Is the strict version checking intended? The patch to ItemRendering just added some constructor variants and convenience methods, thus it was backwards-compatible.

Now that modules other than Core are far more active with more version bumps like this it might either be time to readdress again or just push for releasing more modules at v1.0.0 since then regular SemVer will apply :-)

Alright, sounds very reasonable. Let's try to push some modules to a proper 1.0.0 release then :)


Recommendation 3.8: No spaces should be inserted for horizontal alignment

Horizontal alignment - is a practice to add additional spaces in the code, to align code blocks on the same level with previous code blocks.

It always takes time to format and support such code and fix alignment for new developers in case they need to change something in aligned code.
Long identifier names will break the alignment and will make the code less presentable.
The disadvantages of alignment are greater than the benefits; in order to reduce maintenance costs and not cause trouble, misalignment is the best choice.

Recommendation: the only exception where it can look good is enum class, where you can use alignment (in table format) to make code more readable:
enum class Warnings(private val id: Int, private val canBeAutoCorrected: Boolean, private val warn: String) : Rule {
    PACKAGE_NAME_MISSING         (1, true,  "no package name declared in a file"),
    PACKAGE_NAME_INCORRECT_CASE  (2, true,  "package name should be completely in a lower case"),
    PACKAGE_NAME_INCORRECT_PREFIX(3, false, "package name should start from company's domain")
    ;
}

Recommended examples：
private val nr: Int // no alignment, but looks fine
private var color: Color // no alignment

Not recommended：
private val    nr: Int    // aligned comment with extra spaces
private val color: Color  // alignment for a comment and alignment for identifier name

You should: support check (warning) and autofix rule that will replace multiple spaces with one space

https://github.com/cqfn/diKTat/issues/152 :)


az network bastion create fails

Describe the bug
#/bin/bash
RG='azcy001'
source conf/config.cfg
echo "Creating Public IP in resource group: $RG "
az network public-ip create --resource-group $RG --name $RG-bastion-ip --sku Standard --location westeurope -o table
echo ""
echo -e "Creating Bastion in $RG with "
az network bastion create --name $RG-bastion --public-ip-address $RG-bastion-ip --resource-group $RG --vnet-name per001-vn001 --location westeurope -o table
echo ""
Fails with the following issues
/providers/Microsoft.Network/virtualNetworks/PER001-VN001
For som reason az network bastion, creates the request in all CAPS for the VNet name and the resource group.
Related command
RG='azcy001'
az network bastion create --name $RG-bastion --public-ip-address $RG-bastion-ip --resource-group $RG --vnet-name per001-vn001 --location westeurope -o table
Errors
(InvalidResourceReference) Resource /subscriptions/removed/resourceGroups/AZCY001/providers/Microsoft.Network/virtualNetworks/PER001-VN001 referenced by resource /subscriptions/removed/resourceGroups/azcy001/providers/Microsoft.Network/bastionHosts/azcy001-bastion was not found. Please make sure that the referenced resource exists, and that both resources are in the same region.
Code: InvalidResourceReference
Message: Resource /subscriptions/removed/resourceGroups/AZCY001/providers/Microsoft.Network/virtualNetworks/PER001-VN001 referenced by resource /subscriptions/removed/resourceGroups/azcy001/providers/Microsoft.Network/bastionHosts/azcy001-bastion was not found. Please make sure that the referenced resource exists, and that both resources are in the same region.
Exception Details:      (NotFound) Resource /subscriptions/removed/resourceGroups/AZCY001/providers/Microsoft.Network/virtualNetworks/PER001-VN001 not found.
Code: NotFound
Message: Resource /subscriptions/removed/resourceGroups/AZCY001/providers/Microsoft.Network/virtualNetworks**/PER001-VN001 n**ot found.
Issue script & Debug output
RG='azcy001'
az network bastion create --name $RG-bastion --public-ip-address $RG-bastion-ip --resource-group $RG --vnet-name per001-vn001 --location westeurope -o table
Expected behavior
That resource group and vnet does not get all caps when running the command
Environment Summary
azure-cli                         2.49.0
core                              2.49.0
telemetry                          1.0.8
Extensions:
bastion                            0.2.4
Dependencies:
msal                              1.20.0
azure-mgmt-resource               22.0.0
Additional context
No response

Thank you for opening this issue, we will look into it.

Adding Service team to look into this.


is the video format is the only option for generated output?

This project is awesome!
I would like to ask if the output can be in the format of.obj or .glb or any other 3D model format rather than videos?Thank you.

You can use the output video to reconstruct the scene with 3DGS. In our paper, we utilize DUSt3R and 3DGS optimization to reconstruct the 3D scene. We plan to open-source our 3DGS optimization code in the future.


Queryable behaviour

Context
In order for Ecto.Repo to be fully operational with: [Repo.all/1, Repo.update_all, Repo.delete_all/3]
We must implement the Queryable behaviour on our side, which consists of adding functionalities to prepare/2 and execute/5 both will work on receiving the Query data, processing it, executing it into the database.
Scenario
We need to create a Query module to run cyphers programmatically.
For example:
match(:user)->where(github: "WLSF")

How would it be a better fit for us?
Suggestion
We could implement the Queryable behaviour to support old fashion queries, just like:
from(u in User, where: u.github == "WLSF")

Since the current Ecto.Query has a robust struct that exposes wheres, from, select, etc... We would be able to create a DSL with Macros for building a Ecto.Query struct by using Neo4j Cypher syntax, just like the example above with match/1

I guess implementing the Queryable module to support Ecto.Query will give us an advantage, by using the Query struct to create our own DSL with Macros.


Created 'beatrizsmerino.json' file

What type of PR is this? (check all applicable)

[x] 🚀 Added Details
[ ] 🌟 stared the repo
[ ] 🐛 Grammatical Error
[ ] 📝 Documentation Update
[ ] 🚩 Other

Description
Added user profile
Add Link of GitHub Profile
https://github.com/beatrizsmerino

Hi !!
Can you merge this branch, please?


[cxx-interop] Add CxxOptional protocol for std::optional ergonomics

This adds a protocol to the C++ standard library overlay which will improve the ergonomics of std::optional when used from Swift code.
As of now, the overlay adds an initializer of Swift.Optional that takes an instance of CxxOptional as a parameter.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test macOS


Fix Decorator Selection Drawable

This fixes #72 by 'cloning' the custom drawable set via decorators. It also adds an example in the sample app for custom selectors.

Why did you put the drawables in mipmap folders? I thought those were mostly for launcher icons.

Also, why aren't you using the prolific code style for this project?

There wasn't really a reason for using mipmap, so I changed it.
For code styling, the best reason I have is because I want to make it easier for people to contribute, since Android Studio uses 4 spaces by default. But I also started the project on my home machine, which doesn't have the Prolific style setup.

@ireneduke is this good to merge?

:+1:


Sharp With Electron - Uncaught Error: /lib/x86_64-linux-gnu/libz.so.1: version `ZLIB_1.2.9'

Sorry to create a new issue for this, but all previous threads are locked and the preferred method to attempt to solve this is still unclear. Could you please point me in the right direction on this?
I'm using Electron 1.8.4, but have also tried Electron 2.0.0. Is it possible with either of the two methods to package a working application including Sharp? I'm running Linux Mint 18.3 x64.  I've also tried Linux Mint 17.3 x64
Using: LD_PRELOAD=./node_modules/sharp/vendor/lib/libz.so
Results in: ERROR: ld.so: object './node_modules/sharp/vendor/lib/libz.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
Thanks very much for any advice you can offer.
From #892

so there's nothing sharp can do here. Two possible options are:

Upgrade the system libz from the vulnerable v1.2.8 to the latest v1.2.11
Use LD_PRELOAD=/path/to/node_modules/sharp/vendor/lib/libz.so electron ... so the system will use the sharp-provided v1.2.11 instead of its own v1.2.8.

LD_PRELOAD is relative to (I think) LD_LIBRARY_PATH rather than the current working directory, so you'll need to use absolute paths.
See also my comment about requesting that Electron ship with its own libz, plus my final comment about rolling your own bundle. https://github.com/lovell/sharp/issues/892#issuecomment-360901007

Actually as soon as I stepped away from the computer I realized I had the wrong path... Silly mistake... I am going to see how far I can get with this solution. Thanks very much for your (insanely fast) reply!

@lovell Electron 2 & Electron 3 are using<EMAIL_ADDRESS>am I mistaken to believe I should not be getting this message anymore, about not being able to find 1.2.9?
Uncaught Error: /lib/x86_64-linux-gnu/libz.so.1: version ZLIB_1.2.9' not found (required by /home/user/projects/myApp/app/node_modules/sharp/build/Release/../../vendor/lib/libpng16.so.16)
at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:172:20)`

Electron relies on the system zlib shared library even though Node provides a static zlib.
Please see my comment https://github.com/lovell/sharp/issues/892#issuecomment-357422744 in "Electron beta appears to use system zlib".

"You might want to make an upstream request that the electron binaries link and ship with the latest libz, which will involve a change somewhere around here https://github.com/electron/electron/blob/fce84fbe99b3ea726297bb6de0d811173ffb6dea/electron.gyp#L211"

So even in if from Electron process.versions.libz returns 1.2.11, this version will not available to Sharp?

Correct, process.versions.libz is the version of libz statically linked to at Node build time. Electron treats Node as a shared library, so can't use Node's libz, hence my suggestion that Electron could be modified to ship with its own libz as a shared library (as it already ships with its own libffmpeg as a shared library).

Thanks for the clarification @lovell. Always appreciate your help. I'd love if they'd do this. I guess it's back to the custom libvips route.


Load dynamically linked UDF libraries at runtime

Build a wrapper library for each UDF that gets loaded by the worker at runtime. The library code is generated at pipeline creation time, and the worker calls the UDF via the foreign function interface.
This change also brings back the compiler service, converting it to a library and launching the service with arroyo-bin.
A couple open questions:

[ ] We may want to rename the POST /v1/udfs/validate endpoint, or rework the flow even more.
[ ] Need to test and maybe fix the docker builds

It looks like it doesn't work out of the box running ./aroyo-bin cluster — you still need to manually pass in the compiler address.

@mwylde I've changed it to make arroyo-bin pass the compiler address to the controller


Style the loading animation.

Currently it displays in the top left corner. Should be centered. Potentially different color.

complete.

complete


Include github.com/flutter in our custom search engine

For make better search of our github and wiki from flutter.io

Done! Feedback welcome. (might take a little while to populate, but I made the change in the CSE admin panel)


Compiled ANTs very slow on Ubuntu 14.04 (but fine on OSX 10.10)

Hello!
I have two computer systems; one running Mac OSX Yosemite, the other running Ubuntu 14.04 with similar hardwares. On mac, computational speed is fine, but on linux it can take 4 hours to compute a rigid transformation. I've used the source code from github and installation intruction from https://brianavants.wordpress.com/2012/04/13/updated-ants-compile-instructions-april-12-2012/ . Is there a configuration flag to set or something similar? Thank you!

set build type to release
http://www.cmake.org/pipermail/insight-users/2009-September/032799.html
brian
On Mon, Sep 14, 2015 at 11:01 AM, michaelbernier<EMAIL_ADDRESS>wrote:

Hello!
I have two computer systems; one running Mac OSX Yosemite, the other
running Ubuntu 14.04 with similar hardwares. On mac, computational speed is
fine, but on linux it can take 4 hours to compute a rigid transformation.
I've used the source code from github and installation intruction from
https://brianavants.wordpress.com/2012/04/13/updated-ants-compile-instructions-april-12-2012/
. Is there a configuration flag to set or something similar? Thank you!
—
Reply to this email directly or view it on GitHub
https://github.com/stnava/ANTs/issues/225.

It was already set to release, but I managed to find the issue:
When using the cmake-gui, toggle the advanced configuration. The "CMAKE_C_FLAGS" were set correctly, but the "CMAKE_CXX_FLAGS" were blank on ubuntu (but filled on OSX). In other words, even if 'Release' was selected, it was compiling in debug. I've copy pasted the flags from "CMAKE_C_FLAGS", recompiled and it works fine!
(Still don't know why the flags are not set by default on my ubuntu...)


Why does my battery not discharge

Question
In my LES I have a battery connected. The battery does not seem to discharge? How can I solve this?
Information
LES.
To the "PV plant" node 3 PV plants and one large battery are connected.
The battery does charge initially, but does not seem to decharge.

cc @dennisschoenmakers

I added the label bug

@DorinevanderVlies I've been experimenting which this scenario on my own machine. While I can see the same thing, can you identify any time in the LES when the batteries are not discharging, but you expect that they should be?
It would be helpful since I could check out the behaviour each technology at that point in time, and then find out why the loads are the way they are.

I would expect my batteries to discharge during night, when there is no sun, but there is still demand.
So, an example of a point in time where I would expect my batteries to discharge is January 1, 22:00h

I'm going to use the dreaded phrase: this is a feature and not a bug. 😱
Calling it a "feature" might be too strong a term, but this is a property of our network calculator and not a mistake. Storage in ETMoses is selfish and prefers to keep energy in the endpoint to which it is attached. If there are no consumption technologies in the endpoint which want the energy, the battery will keep it for later.
The best analogy I can think of is: if you install a solar panel and battery in your house, you want to get home at night to find a full battery ready for you to use. You wouldn't be very happy if you found that your neighbour (another endpoint) had used all the energy you saved.
Perhaps we might be better calling these "Household batteries" or "Endpoint batteries"; either way I think the behaviour you are seeing is correct, at least in our current model.
@ChaelKruip What do you think about renaming the battery? Are either of those terms to your liking?
--
I created a copy of your LES which adds a P2P battery on the three main endpoints – each with a third of the capacity and volume of the original – and removed the battery from the solar PV node. There's not enough excess energy to fill all three, but if you look at the "Gebouwen" node, as the solar PV energy begins to disappear you'll see the battery discharging to meet the needs of consumption on that endpoint.


Add deno support for solid cli

This is WIP
I'll follow up on this when deno supports the npm_config_user_agent

https://github.com/denoland/deno/pull/26639

It's working now:
solid-cli on  add-deno-option-for-cli [!?] via ⬢ v22.11.0 via 🅒 base
➜ deno task deno
Task deno deno run --unstable-bare-node-builtins -A ./packages/create-solid/src/index.ts
Warning Resolving "fs/promises" as "node:fs/promises" at file:///Users/admin/repos/solid-cli/packages/commands/dist/handlers/new.mjs:1:324. If you want to use a built-in Node module, add a "node:" prefix.
Warning Resolving "path" as "node:path" at file:///Users/admin/repos/solid-cli/packages/commands/dist/handlers/new.mjs:1:372. If you want to use a built-in Node module, add a "node:" prefix.
Warning Resolving "fs" as "node:fs" at file:///Users/admin/repos/solid-cli/packages/commands/dist/handlers/new.mjs:1:475. If you want to use a built-in Node module, add a "node:" prefix.
Warning Resolving "fs/promises" as "node:fs/promises" at file:///Users/admin/repos/solid-cli/packages/utils/dist/index.mjs:1:256. If you want to use a built-in Node module, add a "node:" prefix.
Warning Resolving "os" as "node:os" at file:///Users/admin/repos/solid-cli/packages/utils/dist/index.mjs:1:306. If you want to use a built-in Node module, add a "node:" prefix.
Warning Resolving "path" as "node:path" at file:///Users/admin/repos/solid-cli/packages/utils/dist/index.mjs:1:375. If you want to use a built-in Node module, add a "node:" prefix.
Warning Resolving "util" as "node:util" at file:///Users/admin/repos/solid-cli/packages/utils/dist/index.mjs:5:158. If you want to use a built-in Node module, add a "node:" prefix.
Warning Resolving "fs/promises" as "node:fs/promises" at file:///Users/admin/repos/solid-cli/packages/utils/dist/fs/index.mjs:1:26. If you want to use a built-in Node module, add a "node:" prefix.
Warning Resolving "fs/promises" as "node:fs/promises" at file:///Users/admin/repos/solid-cli/packages/utils/dist/updates/index.mjs:1:37. If you want to use a built-in Node module, add a "node:" prefix.
┌
 Create-Solid v0.5.13
│
◇  Project Name
│  new-solid-project
│
◇  Is this a SolidStart project?
│  Yes
│
◇  Which template would you like to use?
│  basic
│
◇  Use Typescript?
│  Yes
│
◇  Project successfully created! 🎉
│
◇  To get started, run: ─╮
│                        │
│  cd new-solid-project  │
│  deno install          │
│  deno task dev         │
│                        │
├────────────────────────╯

solid-cli on  add-deno-option-for-cli [!?] via ⬢ v22.11.0 via 🅒 base took 11.3s
➜ cd new-solid-project

solid-cli/new-solid-project on  add-deno-option-for-cli [!?] via ⬢ v22.11.0 via 🅒 base
➜ deno install
Warning The following packages are deprecated:
┠─<EMAIL_ADDRESS>(Shikiji is merged back to Shiki v1.0, please migrate over to get the latest updates)
┠─<EMAIL_ADDRESS>(Shikiji is merged back to Shiki v1.0, please migrate over to get the latest updates)
┠─<EMAIL_ADDRESS>(Glob versions prior to v9 are no longer supported)
┠─<EMAIL_ADDRESS>(Glob versions prior to v9 are no longer supported)
┠─<EMAIL_ADDRESS>(This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.)
┠─<EMAIL_ADDRESS>(This package is no longer supported.)
┠─<EMAIL_ADDRESS>(Rimraf versions prior to v4 are no longer supported)
┠─<EMAIL_ADDRESS>(This package is no longer supported.)
┖─<EMAIL_ADDRESS>(This package is no longer supported.)

solid-cli/new-solid-project on  add-deno-option-for-cli [!?] via ⬢ v22.11.0 via 🅒 base
➜  deno task dev
Task dev vinxi dev
vinxi v0.4.3
vinxi starting dev server

  ➜ Local:    http://localhost:3000/
  ➜ Network:  use --host to expose

7:46:22 PM [vite] page reload vinxi/routes
7:46:22 PM [vite] page reload vinxi/routes (x2)
7:46:22 PM [vite] page reload vinxi/routes (x3)

Looks great, thanks!


Mainly added some links

@gareth-nx Could you merge this PR in your branch, please? Then my changes will also appear in the PR you opened against fortran-lang stdlib-master. Thank you.


Crash when changing layout views

Explain the bug
Files crashed when changing views from details to grid (medium)
To reproduce

Go to any directory
Change layout
See the crash

Expected behavior
Files doesn't crash.
Logfile
debug.txt
debug_fulltrust.txt
System Information

OS Version: Edition
Windows 10 Pro Insider Preview
Version	Dev
Installed on	2021-03-17
OS build	21337.1010
Experience	Windows 10 Feature Experience Pack 321.5601.0.3

App version: v<IP_ADDRESS>

Additional comment
Cannot reproduce consistently. I had done it a couple of times in a row, then I navigated to another directory and tried it there and had no issue. Will update if I can figure out any more.

The way I've been able to most reproduce the issue is in a OneDrive directory that immediately changes its format due to the "adaptive layout". If you change the layout after that, it crashes. Typically only works with directories that have folders, and once you've changed the layout, it won't crash again in the same directory.
https://user-images.githubusercontent.com/8879244/112315775-d3ad8900-8c80-11eb-9b56-c8f94151e1fe.mp4
Attached debug files again as well, as the error seems to be different.
debug.txt
debug_fulltrust.txt

Er... got another error as I was trying different things, this one I didn't need to change the layout for.
debug.txt

Can't reproduce in <IP_ADDRESS>


term: let's cut out xhr polling

websocket definitely works. we can save time by skipping the xhr polling probe

done in v2.3.0


inst_to_dict not support built-in script

Godot version
v4.0.beta7.official [0bb1e89fb]
System information
Windows10, 64bit
Issue description

Steps to reproduce
/
Minimal reproduction project
InstToDictTest.zip

Might be a duplicate of #6533?

It seems like only built-in scripts are affected because inst_to_dict doesn't recognize them as resources and failed to check for it:
(https://github.com/godotengine/godot/blob/7bffdca41ccedd22eac831e916a02b890e90bb28/modules/gdscript/gdscript_utility_functions.cpp#L305-L314)

This bug exists in the 3.x as well.
The check may be incorrect here and should be removed:
https://github.com/godotengine/godot/blob/7bffdca41ccedd22eac831e916a02b890e90bb28/modules/gdscript/gdscript_utility_functions.cpp#L305-L314

This bug exists in the 3.x as well.

I tested in 3.5 and it works.

@KoBeWi Are you sure?:

You must test it with a built-in script, run the following project in 3.5 stable version of Godot:
Test.zip

Ok I got confused, sorry.
But then if it's broken in both versions, it doesn't need 4.0 milestone.

But I think this is just a limitation. The method requires a script path to work, otherwise you won't be able to de-serialize the object. It's not possible to obtain a built-in resource from external scene (it's just not implemented. You can't preload them for the same reason).

Then I suggest adding it to the documentation of this method.


fix unit test endpoints model

removes the isSet check on a required parameter
imports smithy-aws-endpoints because the test uses the AWS region builtin

Closing in favor of #976


Set g:dein#plugin.build value in hook_post_update do not affect

Warning:  I will close the bug issue without the minimal init.vim and the reproduce ways.
Problems summary
Set g:dein#plugin.build value in hook_post_update do not affect.
But toml build key work fine.
Expected
g:dein#plugin can use in hook_*
from help
https://github.com/Shougo/dein.vim/blob/8f5fa9b0034daa3915370c3617e8ac72a8b398f7/doc/dein.txt#L603-L606
Environment Information (Required!)

dein.vim version(SHA1): 8f5fa9b0034daa3915370c3617e8ac72a8b398f7

OS: Windows 10 Pro (21H1 latest 2021/09/17)

Vim/neovim version:

VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Sep 13 2021 15:40:25)
MS-Windows 64 ビット GUI/コンソール 版 with OLE サポート
適用済パッチ: 1-3434

build in vim-tux project
Provide a minimal .vimrc with less than 50 lines (Required!)
https://github.com/tsuyoshicho/testvimrc.vim/tree/test/dein-20210917
Minimal vimrc and toml
The reproduce ways from Vim starting (Required!)

vim start 1st : fetch plugins and work build
vim start 2nd : use plugin if installed

toml build key : success

toml vimproc's build key set system specific command
vimproc file create/download success

ls cache/dein/repos/github.com/Shougo/vimproc.vim/lib/ : file exists.
:echo vimproc#version() report version

g:dein#plugin.build value in hook_post_update : failed

toml vimproc's build comment out, hook_post_update uncomment
toml vimproc's hook_post_update g:dein#plugin.build value are system specific command
vimproc file create/download failed

ls cache/dein/repos/github.com/Shougo/vimproc.vim/lib/ : file do not exists.

Screen shot (if possible)
nothing.
Upload the log messages by :redir and :message (if errored)
nothing.

Wow!  vimproc is 10 years ago plugin...

Why this plugin select reason, build command will be clear.
Fix thanks


az iot hub generate-sas-token returns error

the instructions for sas create token don't seem to work
az iot hub: 'generate-sas-token' is not in the 'az iot hub' command group. See 'az iot hub --help'.
It looks like I need to do this first - not obvious from docs
az extension add --name azure-cli-iot-ext

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

ID: e9e0abf1-d0b9-d886-c106-ae056daa47ec
Version Independent ID: 7534d5aa-8270-49e5-21d6-e9456969a60e
Content: az iot hub
Content Source: latest/docs-ref-autogen/ext/azure-cli-iot-ext/iot/hub.yml
Service: iot-hub
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

iot

@Azure/azure-iot-cli-triage

@davidahoward - Hopefully by now your issue has been resolved. I just wanted to include a data point that azure-cli-iot-ext has been long since deprecated in favor of azure-iot. Going forward, if you still run into issues with azure-iot, you can post questions/problems here for dedicated support.

@davidahoward I believe this issue has been fixed and can be closed. Please let us know.


python310Packages.deal: 4.23.4 -> 4.23.7

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.deal is: Library for design by contract (DbC) and checking values, exceptions, and side-effects
meta.homepage for python310Packages.deal is: https://github.com/life4/deal
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.23.7 with grep in /nix/store/9izvgg5065swh0sv46gwk0bqj7478nzl-python3.10-deal-4.23.7
found 4.23.7 in filename of file in /nix/store/9izvgg5065swh0sv46gwk0bqj7478nzl-python3.10-deal-4.23.7

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)

6 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.deal
python310Packages.icontract
python310Packages.pylddwrap
python311Packages.deal
python311Packages.icontract
python311Packages.pylddwrap

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9izvgg5065swh0sv46gwk0bqj7478nzl-python3.10-deal-4.23.7 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.deal https://github.com/r-ryantm/nixpkgs/archive/43359990a7c6220fb64a3923b6e4a1817ba725f5.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9izvgg5065swh0sv46gwk0bqj7478nzl-python3.10-deal-4.23.7
ls -la /nix/store/9izvgg5065swh0sv46gwk0bqj7478nzl-python3.10-deal-4.23.7/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

6 packages built:

python310Packages.deal
python310Packages.icontract
python310Packages.pylddwrap
python311Packages.deal
python311Packages.icontract
python311Packages.pylddwrap

Maintainer pings
cc @gador for testing.

Result of nixpkgs-review pr 217502 run on aarch64-darwin 1

6 packages built:

python310Packages.deal
python310Packages.icontract
python310Packages.pylddwrap
python311Packages.deal
python311Packages.icontract
python311Packages.pylddwrap


cloud function id_token not work, response 401

link:

https://github.com/GoogleCloudPlatform/php-docs-samples/blob/master/iap/src/make_iap_request.php
https://cloud.google.com/functions/docs/securing/authenticating#service-to-function

use demo code, always response 401.
i have set GOOGLE_APPLICATION_CREDENTIALS to my server account json file.
any one can tell me , why ?
and what is the client id for a cloud function ?

Its done.
Client id is the service account's client id for cloud function.

Enable G Suite Domain-wide Delegation for service account, then get a client id.
Authorization cloudfunctions.functions.call to service account.
call cloud function in back service.


added grpclb support to sockaddr resolver

reintroduces the changes reverted in https://github.com/grpc/grpc/pull/6022
This PR currently includes #6034

Looks good. Just one minor comment on adding a test case.

LGTM.

Needs resolving.

Merged.


AttributeError: module 'sparse_diffusion.utils' has no attribute 'densify_noisy_data'

When I run the command ‘python3 main.py general.name=test’, the console displays an error message:

Error executing job with overrides: ['general.name=test']
Traceback (most recent call last):
File "/Users/wzn/code/SparseDiff/sparse_diffusion/main.py", line 121, in main
dataset_infos.compute_input_dims(
File "/Users/wzn/code/SparseDiff/sparse_diffusion/datasets/abstract_dataset.py", line 204, in compute_input_dims
ex_extra_feat = extra_features(example_data)
File "/Users/wzn/code/SparseDiff/sparse_diffusion/diffusion/extra_features.py", line 52, in call
noisy_data = utils.densify_noisy_data(sparse_noisy_data)
AttributeError: module 'sparse_diffusion.utils' has no attribute 'densify_noisy_data'

And I didn't find that method in utils.py.
How should I handle it to ensure that the code can run properly?

Sorry, this function has been accidentally deleted and it has been added.
Thanks for pointing out this issue.

Sorry, this function has been accidentally deleted and it has been added. Thanks for pointing out this issue.

thank you for your reply! I'll try to reuse the code to test.


Update infra agent restart to support all service start methods

https://newrelic.atlassian.net/browse/VIRTUOSO-686

Finishing testing with non-regression testing suite, merging


incorrect template parameter

--template now supports "Http Trigger" and not "HttpTrigger"
Same for "Queue Trigger"

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

ID: b2646ad4-34b7-fc5e-dcc9-d53a061df394
Version Independent ID: bbff4fda-24e4-2b62-24b9-94cda5f53bed
Content: Develop and run Azure functions locally
Content Source: articles/azure-functions/functions-run-local.md
Service: functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@mishal153 Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@mishal153 thanks for pointing out this bug. I have a PR in the private repo to fix the string values.

No problem. Thanks for fixing real quick !


Use json output from cargo-about

Replace handlebars template and bespoke YAML munging with the --format json flag in cargo-about v0.5.6.
This significantly simplifies output parsing and also allows for the following enhancements:

Detect if crate URL is nil and fall back to homepage, repository URL, or documentation url.
Add crate description from crates.io to listing if present.
Move oniguruma and mruby external deps config to code instead of template.
Remove license text pre- and post-processing to address whitespace issues.

Deployed:

https://github.com/artichoke/docker-artichoke-nightly/pull/153
https://github.com/artichoke/nightly/pull/155


What should we do with the data? Don't understand the process

What should we do with the data? Don't understand the process

You can go to this dir "tools/data_process" for more details, thanks


Improve the Arduino library import process

Is your feature request related to a problem? Please describe.
There are libraries in a zip file in the repo. This is not a "best practice", but completely understand why/how it is the way it is.
Describe the solution you'd like
Create project files/some way to refer to other projects.
Describe alternatives you've considered
Ensure there are minimal binary/zip files in repo. Document steps to create a simple Mama/Papa from nothing (in regards to the library files)
Additional context
Looks like you can create dependencies (see https://github.com/arduino/Arduino/wiki/Library-Manager-FAQ )

Related to #9

@TimoWielink Did #29 and #32 solves this?

@Salzi yes!

Both PRs have landed. Closing.


Updated mul() and div() methods.

Reason: fix gas wasting for useless local variable, get rid of useless assertion

@sp41mer thanks for opening this PR, but I think it's not right to throw during the validation.
Notice that this change makes invalid to multiply by 0.
Also keep in mind that solidity doesn't allocate c in memory, it operates in the stack.

@sp41mer thanks for opening this PR, but I think it's not right to throw during the validation.
Notice that this change makes invalid to multiply by 0.
Also keep in mind that solidity doesn't allocate c in memory, it operates in the stack.


x/tools/gopls: using 1GB RAM with Mattermost server

What version of Go are you using (go version)?

$ go version
go version go1.13.9 linux/amd64
$ gopls version
golang.org/x/tools/gopls 0.4.0
<EMAIL_ADDRESS>h1:G4+YP9kaV4dJb79J5MobyApxX493Qa6VoiTceUmxqik=

Does this issue reproduce with the latest release?
Unknown.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/yann/.cache/go-build"
GOENV="/home/yann/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/yann/go"
GOPRIVATE=""
GOPROXY="direct"
GOROOT="/usr/lib/golang"
GOSUMDB="off"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/golang/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/yann/worldr/github/server/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build075671369=/tmp/go-build -gno-record-gcc-switches"

What did you do?
Running gopls as part of vim-go. This is is one go file open.
What did you expect to see?
A small increase in memory.
What did you see instead?
; procs gopls
 PID:▲  User │ State Nice TTY CPU  MEM   VmPeak   VmSize   VmRSS TCP UDP  Read Write │ CPU Time Start             │ Command
             │                [%]  [%]  [bytes]  [bytes] [bytes]         [B/s] [B/s] │                            │
 212834 yann │ S        0     0.0 27.5   5.203G   5.203G  4.285G []  []  0.000 0.000 │ 00:01:58 2020/05/06 15:51  │ /home/yann/go/bin/gopls serve -listen unix;/tmp/gopls-e4935e-daemon.yann -listen.timeout 1m0s -logfile auto
 215897 yann │ S        0     0.0  0.1 767.355M 767.355M 18.465M []  []  0.000 0.000 │ 00:00:00 2020/05/06 15:53  │ /home/yann/go/bin/gopls -remote=auto
 216038 yann │ S        0     0.0  0.1 831.230M 767.293M 18.000M []  []  0.000 0.000 │ 00:00:00 2020/05/06 15:53  │ gopls -remote=auto

I have to constantly close/open neovim since otherwise, my machine dies because gopls takes all the 16G of RAM I have.

What version of gopls are you using (gopls version)? If it is not v0.4.0, please upgrade by running GO111MODULE=on go get golang.org/x/tools/gopls@latest).
If you are using gopls/v0.4.0, you should see heap profiles in your temporary directory. If you find them, please upload them.

The repository is the Mattermost server.
Here is a heap profile file (I hope!): gopls.149275-1GiB-heap.pb.gz
; procs gopls
 PID:▲  User │ State Nice TTY CPU MEM   VmPeak   VmSize   VmRSS TCP UDP  Read Write │ CPU Time Start             │ Command
             │                [%] [%]  [bytes]  [bytes] [bytes]         [B/s] [B/s] │                            │
 149275 yann │ S        0     0.0 8.4   2.269G   2.269G  1.312G []  []  0.000 0.000 │ 00:00:12 2020/05/07 12:18  │ /home/yann/go/bin/gopls serve -listen unix;/tmp/gopls-cbe194-daemon.yann -listen.timeout 1m0s -logfile auto
 150361 yann │ S        0     0.0 0.1 839.297M 839.297M 16.805M []  []  0.000 0.000 │ 00:00:00 2020/05/07 12:18  │ /home/yann/go/bin/gopls -remote=auto
 150503 yann │ S        0     0.0 0.1 695.227M 695.227M 15.723M []  []  0.000 0.000 │ 00:00:00 2020/05/07 12:18  │ gopls -remote=auto

Thank you for sharing this. It looks as we'd expect, with most of the memory allocated during type checking. By the way, it looks like this heap is only 1GiB, not 16 as you saw. What are your gopls settings - do you have staticcheck enabled by any chance?
Thank you for sharing the link to the repository - we'll try to reproduce. There are number of repos that seem to cause problems with gopls (https://github.com/golang/go/issues/38752 is a similar issue, for example).

@stamblerre Thank you so much for looking into it! Much appreciated.
Yes, it's not the one that generated it. I fiddled a little with dependencies and now I only have the version that vim-go specifically request: 0.4.0, without any additional tags. It seems to behave better but still gets to 4/5G. I will upload another large file when I get one.

do you have staticcheck enabled by any chance?

I do not think so, at least not explicitly. It might be turned on by default in vim-go.

Yes, it's not the one that generated it. I fiddled a little with dependencies and now I only have the version that vim-go specifically request: 0.4.0, without any additional tags. It seems to behave better but still gets to 4/5G. I will upload another large file when I get one.

Thank you!

I do not think so, at least not explicitly. It might be turned on by default in vim-go.

I don't believe vim-go turns on staticcheck by default, and based on the profile you attached that seems to be the case.
We'll follow up here when someone from the gopls team has a chance to take a closer look.

gopls.176223-3GiB-heap.pb.gz
Here's another heap, under gopls 0.4.1…

@ygworldr I believe some changes I landed today have improved memory usage on large projects substantially. Could you try master using the instructions at https://github.com/golang/tools/blob/master/gopls/doc/user.md#unstable-versions?

@heschik I updated the version I have and opened two files in the Mattermost project: channel_test.go and channel.go in api4. This is what I got:
√ ; gopls version
golang.org/x/tools/gopls master
<EMAIL_ADDRESS>h1:+BNEvY32Dn2PtaE6qifJQQshGNIuJvcXAvYUDe6+/gc=
√ ; procs gopls
 PID:▲  User │ State Nice TTY   CPU MEM  VmPeak  VmSize    VmRSS TCP UDP  Read Write │ CPU Time Start             │ Command
             │                  [%] [%] [bytes] [bytes]  [bytes]         [B/s] [B/s] │                            │
 167625 yann │ S        0       0.0 0.1  1.242G  1.181G  16.816M []  []  0.000 0.000 │ 00:00:00 2020/06/12 13:17  │ /home/yann/go/bin/gopls -remote=auto
 167651 yann │ S        0     265.5 6.1  2.168G  2.168G 969.145M []  []  0.000 0.000 │ 00:00:08 2020/06/12 13:17  │ /home/yann/go/bin/gopls serve -listen unix;/tmp/gopls-c6d4b6-daemon.yann -listen.timeout 1m0s -logfile auto

I am afraid there was no heap file in /tmp… Do I need to do something special to generate it?

That looks like pretty good success, no? Your most recent report was 1.3G, and now it's down to 970M. Not a bad improvement.
The heaps are only generated once gopls crosses 1G so you won't have any yet.
I'm inclined to close this -- I don't see any sign that there's a specific problem with mattermost, and we've made significant progress since it was filed. Do you agree?

...assuming it doesn't grow up to 4 or 5 G again.

@heschik

I'm inclined to close this -- I don't see any sign that there's a specific problem with mattermost, and we've made significant progress since it was filed. Do you agree?

Yes, I think the improvements are great! Thank you so much for that. Your hard work is much appreciated!

@heschik, I am afraid I have some bad news… But they are not more than 3G so, maybe not so bad?

gopls.146849-1GiB-heap.pb.gz
gopls.146849-2GiB-heap.pb.gz
gopls.146849-3GiB-heap.pb.gz

That's disappointing. Some progress but we should be able to do better.
I added a new diagnostics section to the debug server that may be helpful. If you follow the troubleshooting guide to start it, /cache/1 will have a table of per-package memory usage. Could you attach it here from a gopls that's using a lot of memory?

That's disappointing. Some progress but we should be able to do better.

No worries whatsoever. I am really grateful for the work you are doing.

I added a new diagnostics section to the debug server that may be helpful. If you follow the troubleshooting guide to start it, /cache/1 will have a table of per-package memory usage. Could you attach it here from a gopls that's using a lot of memory?

I shall do as soon as is feasible.

gopls.195510-1GiB-heap.pb.gz
gopls.195510-1GiB-goroutines.txt

Sadly, the log file is empty. The server command looks like:
/home/yann/go/bin/gopls serve -listen unix;/tmp/gopls-c6d4b6-daemon.yann -listen.timeout 1m0s -logfile auto and /home/yann/go/bin/gopls -remote=auto -rpc.trace…
What am I doing wrong here?

There have been a number of memory improvements in gopls at master. If you can, please try out with the instructions on https://github.com/golang/tools/blob/master/gopls/doc/user.md#unstable-versions and let me know if that's any better.

@stamblerre I have updated just been doing lots of DevOps stuff and not much coding. This will change soon and I shall update. Thank you for your hard work!

Closing, as this has been in the WaitingForInfo state for over a month. gopls/v0.5.0 has been released, and it contains these memory improvements.


how to build ughh database?

use command midas2 database can not download uhgg database on local. Can you write a workflow show how to build uhgg database？

Hi,
Please refer to https://midas2.readthedocs.io/en/latest/download_midasdb.html for downloading MIDASDB.
We don't build UHGG ourselves, and imported from the UHGG catalog: https://www.nature.com/articles/s41587-020-0603-3
If you are interested in building custom MIDASDB, please refer to this page: https://midas2.readthedocs.io/en/latest/advanced_topics.html#build-your-own-midasdb
Chunyu


MM-30170 js to css changeCSS update

Summary
Removed changeCSS line from utils/utils.jsx and updated _emoticons.scss component

Ticket Link
Fixes https://github.com/mattermost/mattermost-server/issues/16174
https://mattermost.atlassian.net/browse/MM-30170

Related Pull Requests

Has server changes (please link here)
Has redux changes (please link here)
Has mobile changes (please link here)

Screenshots

Hello @akshaychhajed,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

Thanks @hmhealey I will review them

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @jfrerich @emilyacook

I apologize for the delay. I am working on this. I am new to scss. It's getting me a little longer to understand mattermost scss styles.

@akshaychhajed all good, thank you for the heads up! Let us know if you have any questions, or if there are any areas we can help you with :)

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @jfrerich @emilyacook

Hi @akshaychhajed. Are you still working on this? If you're stuck we can help out with resolving the conflicts and such.

@hmhealey i am working on it. I have understood the review. Just to need block out some time to go through it.

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @jfrerich @emilyacook

Hi @akshaychhajed!  Just checking in on you to see if you could use any help on finishing this PR :)

Hi @akshaychhajed - I'm helping to review stale PRs and, since we haven't heard from you in a few months, I'll close this PR for now. Please feel free to re-open if you're able to prioritize. Thanks!
I've re-added the "Up for Grabs" label on https://github.com/mattermost/mattermost-server/issues/16174
//cc @hmhealey @asaadmahmood

@lindy65 i just reviewed this. My changes are ready. May I push them here?

Hi @akshaychhajed - I'm not sure whether this branch needs updating before you apply your changes - perhaps @hmhealey can help?  I've reopened the PR in the meantime :)  Thanks for continuing with the contribution!

Ok. I will push the changes I had made to address @hmhealey's previous review.

Thanks for making those changes and following up. The PR is currently conflicting with the branch it's on, but I don't think you need to update it yet since the branch is also really out of date with master as well. I've pinged @deanwhillier to see what needs to be done on our side to fix that.

Thanks @hmhealey

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @jfrerich @emilyacook

Apologies for the delay on this. Dean's actually been out for a few weeks, and he was the one maintaining the campaign branches. I'll see if anyone else has been looking after them in the mean time.

@akshaychhajed I discussed with some other team members, and we've decided we can just merge this into the campaign branch and update that from master afterwards. Would you mind resolving the conflicts between this branch and the one its submitted against, and then we can get to reviewing the PR?

Sure. I will review conflicts and update PR.


invalid_grant on webstore upload

Hello,
I have been using the cli for sometime successfully to deploy from builds on travis.
My most recent build (it is a long time since I do not do a release) failed with the following error:
Response code 400 (Bad Request)
{
    "error": "invalid_grant",
    "error_description": "Bad Request"
}

Here is a link to the build: https://travis-ci.org/podStation/podStation/builds/641766403
I have not yet tried to reproduce it locally.
Do you know what this could be?
The error message seems related to oauth authentication flow, but bad request does not look like a recoverable error.
I am using version 1.1.1.

Thanks @fregante ,
despite the error indicating otherwise (400 for me seems like you are consuming the API in the wrong way, not that the credentials are invalid), renewing the clientId, clientSecret and refreshToken in Travis solved the problem.
I am assuming it was not a transient problem that would have disappeared in case I tried a new release, because I did not try that.


Unable to download the pbit file

Hello Team,
I am unable to download the template from the below location, is the template deprecated?
https://github.com/Azure/CCOInsights/tree/main/dashboards/CCODashboard-Infra

Hello @AishwaryaJais123,
Thank you for reaching out. The template has not been deprecated. I have been able to download it without issue. Please can you provide more detail of what happens when you try to download it ? Please also include any screenshots to help us get to the root cause. Thank you

This issue was closed because it has been open for 2 weeks no activity.


Implemented WindowsFile#exist?

It was missing and not raising an error, which caused much confusion.
See https://github.com/chef/inspec/issues/288 for more info.

Fantastic clean fix for windows! :+1:
Cheers @docwhat


Add add_store_tracks method to Mobileclient

Implements adding multiple songs to library through the trackbatch endpoint.

Nice; thanks!


Implement transfer for GCS/S3 to BigQuery

Please describe the feature you'd like to see

Add DataProvider for Bigquery - read/write methods
Add non-native transfer implementation for GCS to BigQuery
Add non-native transfer implementation for S3 to BigQuery
Add non-native transfer example DAG for BigQuery to Sqlite
Add non-native transfer example DAG for BigQuery to Snowflake
Add example DAG
Add tests with 90% coverage

Acceptance Criteria

[ ] All checks and tests in the CI should pass
[ ] Unit tests (90% code coverage or more, once available)
[ ] Integration tests (if the feature relates to a new database or external service)
[ ] Example DAG
[ ] Docstrings in reStructuredText for each of  methods, classes, functions and module-level attributes (including Example DAG on how it should be used)
[ ] Exception handling in case of errors
[ ] Logging (are we exposing useful information to the user? e.g. source and destination)
[ ] Improve the documentation (README, Sphinx, and any other relevant)
[ ] How to use Guide for the feature (example)

related-to: https://github.com/astronomer/astro-sdk/issues/1732

Added read operations for bigquery as well.

closing this as this PR https://github.com/astronomer/astro-sdk/pull/1829 will cover along with tests


add -Wno-error=implicit-function-declaration in Apple Silicon

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Made this a warning. To completely resolve we need to declare the function prototypes in the TIleDB-SQL-Py repo.

Full CI passed. Merging with build number bump to publish artifacs


Update "YORK" to pool_cluster.json

Hi, I try to add my stake pool "YORK"

Closed by #11

Closed by #11


Correlate does not work with metrics that are not named in metric_names()

At
https://github.com/autonomio/talos/blob/01fd639741167d379abc46e8e1846a2b89ea3d99/talos/commands/reporting.py#L55
When a metric name not  in the return value of metric_names() is supplied, I get a ValueError: cannot insert abracadabra, already exists
A long term solution is to allow talos to infer metric names from the history object.
But for now I would like to change
        columns = [c for c in self.data.columns if c not in metric_names()]
        out = self.data[columns]
        out.insert(0, metric, self.data[metric])

to
       columns = [c for c in self.data.columns if (c not in metric_names()) and c != metric]
       out = self.data[columns]

which allows for custom metrics.
I'll submit a merge request in a few minutes.
PS: Thanks for making this project. I really love the idea and how you structured the whole thing.

Here is a test, run with my modified version of reporting.py
https://gist.github.com/fba8417e04b1c9094bf924db0a2938ec
Here is the same test run with the original
https://gist.github.com/renxida/9e53e1307abd44b33e0984e1ec49937c

FYI: I've added this fix directly to v.0.4.9 which should make it to daily-dev today or tomorrow the latest. Thanks!
Closing here.

I didn't implement it because the fix did not work. It returned an error for any other case except custom metric. So reopening.

This is fixed in v.0.6 onwards. Closing here.


New benchmark functions

Hi Shengyang,
I wanted to try your algorithm on other benchmark functions such as Rosenbrock and I changed the code in 'bo_functions.py  as the following:
def rosenbrock(x):
    d = 4
    x = x[:, :d] [0] # This is so that if the input is high dimensional, only 4 dimensions, be effective.
    y = 0
    for i in range(d - 1):
        y += 100 * (x[i + 1] - x[i] ** 2) ** 2
        y += (x[i] - 1) ** 2
    return tf.reshape(y,[1])

class Rosenbrock(Function):
    def __init__(self, num_dims):
        self.num_dims = num_dims

    @property
    def min(self):
        return 0. * np.ones([self.num_dims], dtype=FLOAT_TYPE)

    @property
    def max(self):
        return 1. * np.ones([self.num_dims], dtype=FLOAT_TYPE)

    def func(self, x):
        return rosenbrock(x)

    @property
    def name(self):
        return 'Rosenbrock'

If I understood correctly, since the bounds for Rosenbrock is between [0,1] the class Rosenbrock should have been defined as above.
In the bayes_opt.py file also I added the following lines similar to other functions:
    if args.name == 'Rosenbrock':
        Task = Rosenbrock(num_dims=input_dim)
        dim_groups = [[id] for id in range(input_dim)]

But I get an error for it, and wanted to ask if in the first place the way I have defined these functions are correct.
Here's also a part of the error:

Epoch 1 of 100:
Traceback (most recent call last):
File "/home/ics/ranjbar/.local/share/virtualenvs/NKN_venv-V8ztIfaw/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1356, in _do_call
return fn(*args)
File "/home/ics/ranjbar/.local/share/virtualenvs/NKN_venv-V8ztIfaw/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1341, in _run_fn
options, feed_dict, fetch_list, target_list, run_metadata)
File "/home/ics/ranjbar/.local/share/virtualenvs/NKN_venv-V8ztIfaw/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1429, in _call_tf_sessionrun
run_metadata)
tensorflow.python.framework.errors_impl.InvalidArgumentError: Input matrix is not invertible.
[[{{node likelihood_1/MatrixTriangularSolve}}]]
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "exp/bayes-opt.py", line 110, in
bo_model.optimize(num_iters, 'bo/{}{}/{}{}'.format(args.name,input_dim, args.kern, args.run))
File "/home/ics/ranjbar/BO/BO_3/External_codes/Neural-Kernel-Network/bayesianOpt.py", line 122, in optimize
self._train(i)
File "/home/ics/ranjbar/BO/BO_3/External_codes/Neural-Kernel-Network/bayesianOpt.py", line 62, in _train
feed_dict={self.X_ph: self.X, self.y_ph: self.y
File "/home/ics/ranjbar/.local/share/virtualenvs/NKN_venv-V8ztIfaw/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 950, in run
run_metadata_ptr)
File "/home/ics/ranjbar/.local/share/virtualenvs/NKN_venv-V8ztIfaw/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1173, in _run
feed_dict_tensor, options, run_metadata)
File "/home/ics/ranjbar/.local/share/virtualenvs/NKN_venv-V8ztIfaw/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1350, in _do_run
run_metadata)
File "/home/ics/ranjbar/.local/share/virtualenvs/NKN_venv-V8ztIfaw/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1370, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: Input matrix is not invertible.
[[node likelihood_1/MatrixTriangularSolve (defined at /home/ics/ranjbar/BO/BO_3/External_codes/Neural-Kernel-Network/NKN_venv/GPflow-Slim/gpflowSlim/densities.py:82) ]]
Errors may have originated from an input operation.
Input Source operations connected to node likelihood_1/MatrixTriangularSolve:
likelihood_1/sub (defined at /home/ics/ranjbar/BO/BO_3/External_codes/Neural-Kernel-Network/NKN_venv/GPflow-Slim/gpflowSlim/densities.py:81)
likelihood_1/Cholesky (defined at /home/ics/ranjbar/BO/BO_3/External_codes/Neural-Kernel-Network/NKN_venv/GPflow-Slim/gpflowSlim/models/gpr.py:70)
Original stack trace for 'likelihood_1/MatrixTriangularSolve':
File "exp/bayes-opt.py", line 107, in
Task.min, Task.max, iterations=iterations)
File "/home/ics/ranjbar/BO/BO_3/External_codes/Neural-Kernel-Network/bayesianOpt.py", line 30, in init
self.init_graph()
File "/home/ics/ranjbar/BO/BO_3/External_codes/Neural-Kernel-Network/bayesianOpt.py", line 47, in init_graph
self.loss = self.model.objective
File "/home/ics/ranjbar/BO/BO_3/External_codes/Neural-Kernel-Network/NKN_venv/GPflow-Slim/gpflowSlim/models/model.py", line 70, in objective
self.likelihood_tensor,
File "/home/ics/ranjbar/BO/BO_3/External_codes/Neural-Kernel-Network/NKN_venv/GPflow-Slim/gpflowSlim/models/model.py", line 55, in likelihood_tensor
return self._build_likelihood()
File "/home/ics/ranjbar/BO/BO_3/External_codes/Neural-Kernel-Network/NKN_venv/GPflow-Slim/gpflowSlim/decors.py", line 33, in runnable
return method(*args, **kwargs)
File "/home/ics/ranjbar/BO/BO_3/External_codes/Neural-Kernel-Network/NKN_venv/GPflow-Slim/gpflowSlim/models/gpr.py", line 72, in _build_likelihood
return multivariate_normal(self.Y, m, L)
File "/home/ics/ranjbar/BO/BO_3/External_codes/Neural-Kernel-Network/NKN_venv/GPflow-Slim/gpflowSlim/densities.py", line 82, in multivariate_normal
alpha = tf.matrix_triangular_solve(L, d, lower=True)
File "/home/ics/ranjbar/.local/share/virtualenvs/NKN_venv-V8ztIfaw/lib/python3.6/site-packages/tensorflow/python/ops/gen_linalg_ops.py", line 1878, in matrix_triangular_solve
adjoint=adjoint, name=name)
File "/home/ics/ranjbar/.local/share/virtualenvs/NKN_venv-V8ztIfaw/lib/python3.6/site-packages/tensorflow/python/framework/op_def_library.py", line 788, in _apply_op_helper
op_def=op_def)
File "/home/ics/ranjbar/.local/share/virtualenvs/NKN_venv-V8ztIfaw/lib/python3.6/site-packages/tensorflow/python/util/deprecation.py", line 507, in new_func
return func(*args, **kwargs)
File "/home/ics/ranjbar/.local/share/virtualenvs/NKN_venv-V8ztIfaw/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 3616, in create_op
op_def=op_def)
File "/home/ics/ranjbar/.local/share/virtualenvs/NKN_venv-V8ztIfaw/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 2005, in init
self._traceback = tf_stack.extract_stack()

Thanks.

Hi, Alireza,
If you have tried my code with the Stybtang function, you must have found that the "Stybtang" function receives a tensor of shape [None, d] and outputs a tensor of shape [None].
However, in your implementation of the "Rosenbrock" function, you receives a tensor of shape [None, d] but outputs a scalar. The first problem I noticed is in the line x = x[:, :d] [0] , it makes no sense to have the last [0] operation.
Please have a check with this.

Hi,
So I did the following experiment:
def stybtang(x):
    if len(x.shape) == 1:
        return 0.5 * tf.reduce_sum(tf.pow(x, 4) - 16 * tf.pow(x, 2) + 5 * x)
    else:
        return 0.5 * tf.reduce_sum(tf.pow(x, 4) - 16 * tf.pow(x, 2) + 5 * x, axis=1)

x = tf.constant([2.,1., 5.])
print(stybtang(x))

sess = tf.Session()
with sess.as_default():
    print(stybtang(x).eval())

output:

Tensor("mul_29:0", shape=(), dtype=float32)
101.0

`x = tf.constant([[2.,1., 5.]])
print(Rosenbrock(x))

sess = tf.Session()
with sess.as_default():
    print(stybtang(x).eval())`

output:

Tensor("Reshape_6:0", shape=(1,), dtype=float32)
[101.]

Then I tried the same with the rosenbrock function I had written:
def Rosenbrock(x):
    d = 2
    if len(x.shape) == 1:
        y = 0
        for i in range(d - 1):
            y += 100 * (x[i + 1] - x[i] ** 2) ** 2
            y += (x[i] - 1) ** 2
        return y

    else:
        x = x[:,:d][0]
        y = 0
        for i in range(d - 1):
            y += 100 * (x[i + 1] - x[i] ** 2) ** 2
            y += (x[i] - 1) ** 2

        return tf.reshape(y,[1])

x = tf.constant([2.,1., 5.])
print(Rosenbrock(x))

sess = tf.Session()
with sess.as_default():
    print(Rosenbrock(x).eval())

output:

Tensor("add_29:0", shape=(), dtype=float32)
901.0

x = tf.constant([[2.,1., 5.]])
print(Rosenbrock(x))

sess = tf.Session()
with sess.as_default():
    print(Rosenbrock(x).eval())

output:

Tensor("Reshape_4:0", shape=(1,), dtype=float32)
[901.]

The inputs and outputs seems similar in shape but I still get the earlier error when I use this function.

Hi, Alireza,
The problem is that your Rosenbrock implementation doesn't support multiple xs. If you create x of shape [2, 3], you will find the problem.

Hi, Alireza,
The problem is that your Rosenbrock implementation doesn't support multiple xs. If you create x of shape [2, 3], you will find the problem.

Thank you again, your suggestion worked.


Further clarification of footnote?

The article has a footnote for certain devices:
1 Device supports dynamic emergency calling (E911) with SIP Gateway.
However, I have done some testing with different devices, and the behavior is the same for devices with the footnote (Polycom VVX501, AudioCodes 450HD) and one without (VVX410). Confirmed they are running the approved firmware version.
Making a call with any of them sends the pidflo method as "Registered" rather than "LIS". I have confirmed that the location I am testing is correctly configured for dynamic e911. (Testing with the same account on a PC with Teams application sends pidflo of LIS and correct address.)
So, the question I have is, if the device has that footnote, should it be obtaining the address dynamically and sending the pidflo method as LIS? Or will it always send as "Registered?"
Note, I have already opened a support ticket, but wanted to ask the question here, since it is specific to this footnote.
Thanks!
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 44863905-42d1-cd3f-0d97-af2570649e89
Version Independent ID: 44863905-42d1-cd3f-0d97-af2570649e89
Content: Plan SIP Gateway - Microsoft Teams
Content Source: Teams/sip-gateway-plan.md
Service: msteams
GitHub Login: @CarolynRowe
Microsoft Alias: crowe

Hi @gr0m1t1, thank you for your feedback.
Please keep us posted here on the support ticket resolution to feed whatever information you discover into the article.
@CarolynRowe @Chandranshu-Singh, maybe you can also provide some ideas. Maybe VVX410 should also be included in that footnote.

We need @Chandranshu-Singh to provide input on this issue.

Thanks @CarolynRowe for tagging me here.
Poly devices from VVX series to which this footnote applies, are currently not able to support emergency calling due to a firmware issue, which we are working to fix over the next few weeks. However, VVX 410 will not be getting this firmware update so it will never be able to support dynamic emergency calling with SIP Gateway.

Thanks @Chandranshu-Singh. Just to clarify, when you say that it will support emergency calling, does that mean that once the firmware issue is resolved, it will then be able to send the pidflo method as "LIS" and not just "Registered"? (Assuming the rest of the dynamic emergency configuration is correct, of course.)
Also, does the AudioCodes 450HD have a similar firmware issue? Because that one is also listed as being able to support dynamic emergency calling, but it was also only sending the "Registered" method.
@dariomws, regarding the support ticket I opened, have not had much progress yet. Very slow going, so far. But if anything pertinent comes up, will let you know.

Well unfortunately the ticket I had open is being closed because they are saying this is a 3rd-party device issue. But I am still unclear as to what is meant in this documentation when it states that emergency services are supported for those devices specified with the footnote.
What should the behavior be for these devices? Should the pidflo method be "LIS" (if it can be obtained) or will it always use the "Registered" address?

On some AudioCodes phones, only support LLDP in dynamic location, not subnet mask. I think the higher end phones do support subnet mask and it shouldn't just send "Registered" as pidflo.
For Poly phones, we are again rolling out the firmware change to support dynamic location, it should be done in a couple of weeks time.

Thanks for the additional information, @Chandranshu-Singh. Is there somewhere to keep an eye on to find out when the updated firmware for Poly gets released? Will it be announced in the Message Center or Service Health in the Admin Center?

It's being rolled out currently, as I said above, expect to complete it by May 22nd. We don't have an MC post on it.

Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


Bump PSReadLine from 2.1.0 to 2.2.2

PR Summary
Bump PSReadLine from 2.1.0 to 2.2.2
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

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

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

Breaking changes

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

[ ] Experimental feature name(s):

I hope to get this with Windows monthly update too :-)

@iSazonov is PSReadLine now serviced by Microsoft Update?

@iSazonov is PSReadLine now serviced by Microsoft Update?

It is a part of WMF and distributed with Windows PowerShell for years.

@doctordns I guess your question was about the MU support for PowerShell 7.2+. The answer to that is: no, the updates t PSReadLine itself doesn't get pushed through MU, but PowerShell will bundle the latest stable release and the MU for PowerShell will refresh the PSReadLine module.

@daxian. So Windows PowerShell will automatically get updated via MU while PowerShell 7 will not. PowerShell 7 will get updatgecd versions (of PSReadline) when I get an updated version of Powershell 7 (eg 7.2.2 when that ships)?? And when that happens we'll be updated by MU?

eg 7.2.2 when that ships

This PR was merged in master but not backported. I'm not sure if we are going to backport it for 7.2.2, but it sounds like a good idea :)

And when that happens we'll be updated by MU?

If we decided to backport this change to 7.2.x, then yes, you will be updated by MU.

I still don't understand about Windows PowerShell - will we get the update?

We will get updates about Windows PowerShell when there is an update to Windows PowerShell.
Be noted that, anything happens in this repo doesn't affect Windows PowerShell.

Thanks for clarify!
(Current PSRL version in Windows is too unfortunate)

@PowerShell/powershell-maintainers
We only take security fixes and regression to LTS.  This is appropriate for 7.3.  Rejecting backport.


[ALBERT] Fine-tune SQUAD, got error in convert_examples_to_features()

In particular, the error is Index Error: list index out of range in _convert_index()

Error:
in _convert_index
if index[pos] is not None:
IndexError: list index out of range

Have you fixed this problem?

meet same issue


Realigned this page to an earlier incarnation

For some weird reason someone had a field day on this table and added weird spaces, changed the implication of some explanations (to incorrect ones) and made it generally hard to know what was going on. It should be reviewed by someone who knows exactly how the regex engine of NPS works. This is the earlier incarnation of the page that I used to correct some of the failings
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc755272(v=ws.10)

 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.:x: webash sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


integration_test example Android app: migrate to Gradle KTS

After this PR is merged, all of integration_test Android gradle buildscripts will be in Kotlin.
Follow-up of https://github.com/flutter/flutter/pull/156291
Part of ongoing effort to use Gradle Kotlin DSL a bit more
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported.
[x] All existing and new tests are passing.

(PR triage): Hey @bartekpacia thanks for contributing. It looks like there are some failing checks here.

@reidbaker @gmackall do you have an idea why e.g. Mac_arm64 framework_tests_misc is failing? I run the equivalent command locally and it passes:
$ packages/integration_test/example/android
$ flutter build apk --debug
$ ./gradlew :integration_test:testDebugUnitTest --tests dev.flutter.plugins.integration_test.FlutterDeviceScreenshotTest

Updating to master and rerunning to see if the failure repetes. Looking at the past 100 or so runs I saw 2 failures but I think they were on pull requests that modified the integration test code.

It looks like the analyzer is complaining about a kotlin lint:
 Summary error count (descending) by rule:
║   standard:multiline-expression-wrapping: 1

ktlint wants this block of code:
pluginManagement {
    val flutterSdkPath = run {
        val properties = java.util.Properties()
        file("local.properties").inputStream().use { properties.load(it) }
        val flutterSdkPath = properties.getProperty("flutter.sdk")
        require(flutterSdkPath != null) { "flutter.sdk not set in local.properties" }
        flutterSdkPath
    }

    / ...
}

to look like this:
pluginManagement {
    val flutterSdkPath =
        run {
            val properties = java.util.Properties()
            file("local.properties").inputStream().use { properties.load(it) }
            val flutterSdkPath = properties.getProperty("flutter.sdk")
            require(flutterSdkPath != null) { "flutter.sdk not set in local.properties" }
            flutterSdkPath
        }
    // ...
}

which (1) I really don't like but more importantly (2) the first version has been the default for quite some time now, so I don't think we should change it.
Could we maybe disable ktlint for .kts files?

ktlint wants this block of code:
pluginManagement {
    val flutterSdkPath = run {
        val properties = java.util.Properties()
        file("local.properties").inputStream().use { properties.load(it) }
        val flutterSdkPath = properties.getProperty("flutter.sdk")
        require(flutterSdkPath != null) { "flutter.sdk not set in local.properties" }
        flutterSdkPath
    }

    // ...
}

to look like this:
pluginManagement {
    val flutterSdkPath =
        run {
            val properties = java.util.Properties()
            file("local.properties").inputStream().use { properties.load(it) }
            val flutterSdkPath = properties.getProperty("flutter.sdk")
            require(flutterSdkPath != null) { "flutter.sdk not set in local.properties" }
            flutterSdkPath
        }

    // ...
}

which (1) I really don't like but more importantly (2) the first version has been the default for quite some time now, so I don't think we should change it.
Could we maybe disable ktlint for .kts files?

@gmackall what do you think. In general I dont like debating style and lean towards any automatic formatting. This reason alone isnt enough for me to want to disable it for all kts files but I could be convinced otherwise.

ktlint wants this block of code:
pluginManagement {
    val flutterSdkPath = run {
        val properties = java.util.Properties()
        file("local.properties").inputStream().use { properties.load(it) }
        val flutterSdkPath = properties.getProperty("flutter.sdk")
        require(flutterSdkPath != null) { "flutter.sdk not set in local.properties" }
        flutterSdkPath
    }

    // ...
}

to look like this:
pluginManagement {
    val flutterSdkPath =
        run {
            val properties = java.util.Properties()
            file("local.properties").inputStream().use { properties.load(it) }
            val flutterSdkPath = properties.getProperty("flutter.sdk")
            require(flutterSdkPath != null) { "flutter.sdk not set in local.properties" }
            flutterSdkPath
        }

    // ...
}

which (1) I really don't like but more importantly (2) the first version has been the default for quite some time now, so I don't think we should change it.
Could we maybe disable ktlint for .kts files?

@gmackall what do you think. In general I dont like debating style and lean towards any automatic formatting. This reason alone isnt enough for me to want to disable it for all kts files but I could be convinced otherwise.

I am inclined to agree that unless there is a very strong argument against a specific auto formatting case, we should just accept the auto formatting wholesale (including here)


Leaving the route causes the trigger parameter to change to undefined

Please forgive me if I put the question in the wrong place.
Based on the following routing structure:
├─ pages/
│   └─ posts
│         ├─ [id].vue
│         └─ index.vue
│   │
│   ├─ index.vue
│   └─ posts.vue

App.vue:
<template>
  <Navbar :paths="['/', '/posts']" />
  <RouterView />
</template>

<script setup lang="ts">
import { RouterView } from 'vue-router/auto';
import Navbar from<EMAIL_ADDRESS></script>

<style scoped></style>

pages/posts.vue:
<template>
  <Navbar :paths="['/posts/1', '/posts/2', '/posts/3', '/posts/4']" />
  <RouterView />
</template>

<script setup lang="ts">
import { RouterView } from 'vue-router/auto';
import Navbar from<EMAIL_ADDRESS></script>

<style scoped></style>

pages/posts/index.vue:
<script setup lang="ts">
import { useFetch } from '@vueuse/core';
import type { Post } from '@/types';

const url = `${import.meta.env.VITE_BACKEND_URL}/posts`;
const { isFetching, error, data: posts } = useFetch(url).get().json<Post[]>();
</script>

pages/posts/[id].vue:
<script setup lang="ts">
import { ref, watch } from 'vue';
import { useRoute } from 'vue-router/auto';
import { useFetch } from '@vueuse/core';
import type { Post } from '@/types';

const route = useRoute('/posts/[id]');

const url = ref(`${import.meta.env.VITE_BACKEND_URL}/posts/${route.params.id}`);
const {
  isFetching,
  error,
  data: post,
} = useFetch(url, { refetch: true }).get().json<Post>();

watch(
  () => route.params.id,
  (newId) => {
    console.log(newId); // Check

    if (newId === undefined) return;
    url.value = `${import.meta.env.VITE_BACKEND_URL}/posts/${newId}`;
  },
);
</script>

When routing from /posts/2 to /posts, why is watch() in [id].vue triggered and newId will be undefined? [id].vue seems to trigger watch() again before it is destroyed. Is this the expected behavior?
related discussion: stackoverflow
main problem: why does the watch() trigger when a user has navigated away from [id].vue?
Thank you for your help!

This is relative to the router but in I couldn't reproduce it. It was a problem in the past and it got fixed so maybe you are using an outdated version?

https://github.com/vuejs/core/issues/2291

I updated the reproductions just to make sure but it seems to work. But a normal watcher shouldn't trigger in that case

@posva Thank you for your very prompt response and help!!
Minimal reproduction:

https://github.com/awdr74100/vue-router-demo

Steps to reproduce:

click /users/c button
click /users button
check the console (will show the undefined)

/users/c to / will not trigger watch(), /users/c to /users triggers watch(). It seems that watch() is triggered again before the component instance is destroyed, which seems to behave the same as the reuse component instance of /users/c to  /users/b.
Explicitly defining routes does present the same problem. I think I will raise this problem again at vuejs/router, thank you for your help!!

It's worth trying to reproduce it using only Vue. In the issue I mentioned I added reproductions with Vue. Maybe adding a nested component reproduces the problem


Support saving full model when performing LoRA training

Run
run_finetune_with_lora_save_aggregated_weights.sh and train_merged_lora.sh
to perform two stage LoRA training

@hendrydong Thanks! This feature is quite important and requires a lot of efforts to implement. Thanks for this meaningful contribution! Before merging into the main branch, we may need to fix some minor problems first, so that the main branch is still stable and friendly to other users.
requirements.txt

line 3: commit id may need to be provided, since the main branch of peft keeps changing, which may affect the functionality of our package.

I have edit the requirements.txt. BTW, the previous branch specification is incorrect and I have correct them.

scripts/run_finetune_with_lora.sh

[Question] line 32: I am wondering if zero3 optimization can be supported.

Yes. I have tested.

scripts/run_finetune_with_lora_save_aggregated_wieghts.sh

[Style] line 3-4: better removed

Done.

scripts/export_llama_state_dict_checkpoint.py

[Question] I am wondering if our users need this script. If so, I am wondering how it is used. We may need a README section in that case.

Added.

scripts/train_merged_lora.sh

[Style] line 3-4: better removed
[Question] Can we make lora's default behavior as --save_aggregated_lora 1, so that it can have the same interface as finetune.sh and don't have to create this new script (which can be a burden for our users). Better if it can support seamingless multi-stage training with LoRA and non-LoRA models.

In fact, the key issue is that we do not need the aggregated one by default. The aggregated version is reserved for those who need the full model.

[Question] I am wondering the if there is any difference between scripts/run_finetune_with_lora_save_aggregated_weights.sh and scripts/train_merged_lora.sh.

I have removed train_merged_lora.

scripts/lmflow/models/hf_decoder_model.py

[Question] line 271-272: I am wondering if the removal of those two lines is safe under all scenarios, like when we use lora but don't turn on --save_aggregated_lora.

It is safe. I know why I wrote this two line but we remove the usage now.

[Question] line 202: I am wondering if this line is necessary.

Removed (I think this is the finetuner.py).

[Style] line 241: better removed

Done.

[Architecture] line 237-244: better encapsulate this in a new model method hf_decoder_model.save(). We don't want the pipeline to know and handle the details of model management, since other contributors may not be familiar with that part.

Done.
Hi Rui,
I have upload another version. Can you check it again? Thank you very much.


[$250] Scanned receipt does not merge with virtual card expense

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:
Reproducible in staging?: needs reproduction
Reproducible in production?: Needs reproduction
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @puneetlath
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1729191531798699
Action Performed:
Precondition:
Have a virtual workspace Expensify Card

Make an expense using virtual card
Scan a receipt
I used my virtual workspace Expensify Card for the first time yesterday and it worked great in terms of charging the card. However, when I scanned the receipt as well, it didn't merge with the card transaction, so I have a duplicate now.

Expected Result:
Scanned receipt should merge with card transaction
Actual Result:
Scanned receipt didn't merge with the card transaction
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Standalone
[ ] Android: HybridApp
[ ] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021848380792425722967
Upwork Job ID:<PHONE_NUMBER>425722967
Last Price Increase: 2024-10-21

Issue OwnerCurrent Issue Owner: @abdulrahuman5196

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

Could you help with reproducing this one @abdulrahuman5196?

I have a virtual card.

But I've struggled with this step

Make an expense using virtual card

@abdulrahuman5196 Do you have an idea how can I do it?
cc @puneetlath since you was the one who reported this issue.

Ah you'd actually have to charge the card so that a transaction is created. And then scan a receipt that you would expect to merge with that.

But actually, I think this is a dupe of https://github.com/Expensify/App/issues/51250, so we should close this one. Feel free to reopen if I'm mistaken!


WebView2 ToC change - Merge both nodes and sort titles alphabetically.

Rendered TOC for review:
https://review.docs.microsoft.com/en-us/microsoft-edge/webview2/how-to/webdriver?branch=pr-en-us-1606

Docs Build status updates of commit 4dee5ad:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 1381ab3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit b0449d9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit a70bc1d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel