Not zooming

I installed the plugin, yet all it does is tilt my screen up and down, it will not allow zooming anymore and doesnt do the smoothness. Not sure what other plugin might be interfering thus its not working for me

What's your smoothing setting at in Camera Smoothing's settings? At 100%, I'd imagine you only get tilting up and down. Do you have "Smooth Zooming" and "Smooth Rotation" checked?
What camera plugins do you have installed? The main ones I'm aware of that I don't use are:

Camera Fun
Two step zoom
Zoom Extender

Please post your RuneLite default Camera plugin settings if you are using it. These are mine, for example:

Heya, bit late getting back to you, but here we go:
It never worked for me, u described it well, all others I've used last week
are
Camera Points
Two step zoom
Never used camera fun or zoom extender
Camera plugin settings:
[image: image.png]
Op do 30 jun. 2022 om 15:08 schreef ArtsicleOfficial <
@.***>:

What's your smoothing setting at in Camera Smoothing's settings? At 100%,
I'd imagine you only get tilting up and down. Do you have "Smooth Zooming"
and "Smooth Rotation" checked?
What camera plugins do you have installed? The main ones I'm aware of that
I don't use are:

Camera Fun
Two step zoom
Zoom Extender

Please post your RuneLite default Camera plugin settings if you are using
it. These are mine, for example:
[image: image]
https://user-images.githubusercontent.com/35227462/176684400-348ce8f7-0682-4d01-96fd-0a978b97871d.png
—
Reply to this email directly, view it on GitHub
https://github.com/ArtsicleOfficial/camera-smoothing/issues/3#issuecomment-1171198468,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AW3QVKQZPSJLQZHOFECZ2DDVRWL5RANCNFSM52I553OQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Heya, bit late getting back to you, but here we go: It never worked for me, u described it well, all others I've used last week are Camera Points Two step zoom Never used camera fun or zoom extender Camera plugin settings: [image: image.png] Op do 30 jun. 2022 om 15:08 schreef ArtsicleOfficial < @.***>:

Your image of the camera plugin settings is not displaying.
What is your in-game smoothing setting? Tell me what it is, and make sure it's not 100%.
Try disabling other camera plugins and see if it fixes it.

Aha, it wasn't working due to 100%, it seems to work now.. :) if that was mentioned somewhere I must have not seen it. Thank you!


pause-relay fail to get expected result

Which jobs are flaking?
DM-IT
Which test(s) are flaking?
dmctl_basic
Jenkins logs or GitHub Actions link
https://ci2.pingcap.net/blue/organizations/jenkins/dm_ghpr_integration_test/detail/dm_ghpr_integration_test/449/pipeline/133/
REASON:
we call start-relay when pause-relay in around 18:07:00, that's too adjacent so when DM-worker enable relay, it will directly see a "paused" relay stage in etcd.
https://github.com/pingcap/ticdc/blob/2569abaa3e64bc930b5cab18a0d6edaae2a41ef0/dm/dm/worker/source_worker.go#L340-L345
It's not a "running" relay stage in etcd, DM-worker will not start relay and keep relay in a "New" stage. As we are expecting DM-worker start-then-pause relay which should be a "paused" relay stage, so the declarative check of pause-relay is failed.
Anything else we need to know

Does this test exist for other branches as well?

Has there been a high frequency of failure lately?

cc @GMHDBJD @lichunzhu

maybe we can turn start-relay into a declarative command

[2022-08-03T14:19:38.872Z] [2022/08/03 22:19:37.621 +08:00] [INFO] [server.go:806] [request=PurgeRelay] [payload="filename:\"dm-integration-test-go1180-8569-nrj5p-swccn-bin.000003\" "]
...
[2022-08-03T14:19:38.873Z] [2022/08/03 22:19:37.624 +08:00] [INFO] [purger_helper.go:169] ["purging relay log file"] [component="relay purger"] [strategy="file name"] [file=/tmp/dm_test/dmctl_basic/worker1/relay_log/c0291b20-1336-11ed-82db-b6f9be75bc71.000001/dm-integration-test-go1180-8569-nrj5p-swccn-bin.000001]


[WIP] DSL Clean Up and Dependency Removal

Removing unneeded dependencies and cleaning up implementation in general.

TODO:

Add Documenter.jl documentation
Fix/rebuild unit tests properly
Reimplement mk_function GeneralizedGeneral maybe?
Tag new release


multipart/form-data as body

Hi,
Hopefully I'm not doing something extremely n00bful... I'm trying to use a lump of multipart/form-data with some JSON and an image as the body (included with @filename) but something's going wrong and I'm getting a 400 back -- any reason this shouldn't work?
Many thanks,
Dave
targets.txt:
POST https:/blah.com/still
Host: blah.com
Content-Type: multipart/form-data; boundary=Boundary+0xAbCdEfGbOuNdArY
@still-bits2.req

still-bits2.req:
--Boundary+0xAbCdEfGbOuNdArY
Content-Disposition: form-data; name="data"

{
  "status" : "live",
  "uid" : "329475.1",
  "time" : "1441380329.607740",
  "mode" : "stills",
  "session_id" :<PHONE_NUMBER>,
  "version" : "1.1.0",
  "token" : "tokenytoken",
  "type" : "StillImage"
}
--Boundary+0xAbCdEfGbOuNdArY
Content-Disposition: form-data; name="file"; filename="file.jpg"
Content-Type: image/jpeg

LOADS OF JPEG BLAH
--Boundary+0xAbCdEfGbOuNdArY--

Perhaps looking at the server logs would hint about why the requests are being rejected.

Working through that, but thought it was probably worth checking I wasn't trying to do something you knew to be unsupported. I'm not getting Bad Request on the equivalent curl call.

OK, narrowed down to a server issue. Working nicely. Thanks for the polite response :)

Great! :-)

OK, narrowed down to a server issue. Working nicely. Thanks for the polite response :)

@deyvsh, i would be interrested by your solution :)

@alkaphreak I can't remember, sorry!
For the avoidance of doubt, it was nothing to do with vegeta. Either I was constructing the request wrongly (perhaps I was using LFs instead of CRLFs for line endings? That's a classic!) or it was some detail of the server implementation where curl and vegeta appeared to be doing something subtly different (e.g. I think curl sends Expect: 100-continue). Either way, I probably identified the difference by capturing the raw request in Wireshark or dumping it on the server.
Good luck!


logger - fleet does not download and install properly

Operating System Version: win11
Deploying via (VirtualBox/VMWare/AWS/Azure/ESXi): vmware
Vagrant Version (if applicable): 2.2.19

Please verify that you are building from an updated Master branch before filing an issue.
Description of the issue:
While building the logger host, I'm running into the following error message that causes the build to stop:
    logger: [11:00:38]: Installing Fleet...
    logger: <IP_ADDRESS> logger logger
    logger: mysql: [Warning] Using a password on the command line interface can be insecure.
    logger: No URLs found in -.
    logger: No URLs found in -.
    logger: tar: fleet_*.tar.gz: Cannot open: No such file or directory
    logger: tar: Error is not recoverable: exiting now
    logger: tar: fleetctl_*.tar.gz: Cannot open: No such file or directory
    logger: tar: Error is not recoverable: exiting now
    logger: cp: cannot stat 'fleetctl_*/fleetctl': No such file or directory
    logger: cp: cannot stat 'fleet_*/fleet': No such file or directory
    logger: /tmp/vagrant-shell: line 307: fleet: command not found
    logger: Created symlink /etc/systemd/system/multi-user.target.wants/fleet.service â†’ /etc/systemd/system/
fleet.service.
    logger: [11:00:40]: Waiting for fleet service to start...

Link to Gist Containing Build Logs:

I am having the same issue. I attempted to find a way to fix the issue but haven't been able to solve it yet.

as a workaround, i just added wget and the current release download link in logger_bootstrp.sh; i commented out the curl -s lines

I created a fairly clean workaround to successfully download the latest release of Fleet and Fleetctl :
Requires jq to help parse the curl request output:
sudo apt install jq
In the logger_bootstrp.sh file, replace the original two lines (or comment out):
curl -s https://github.com/fleetdm/fleet/releases | grep _linux.tar.gz | grep href | grep -v orbit | grep -v fleetctl | cut -d '"' -f 2 | head -1 | sed 's#^#https://github.com#g'  | wget --progress=bar:force -i -
curl -s https://github.com/fleetdm/fleet/releases | grep _linux.tar.gz | grep href | grep fleetctl | cut -d '"' -f 2 | head -1 | sed 's#^#https://github.com#g' | wget --progress=bar:force -i -
with:
curl -s https://api.github.com/repos/fleetdm/fleet/releases/latest | jq '.assets[] | select(.name|match("linux.tar.gz$")) | .browser_download_url' | sed 's"//g' | grep fleet | wget -q --show-progress --progress=bar:force -i -
curl -s https://api.github.com/repos/fleetdm/fleet/releases/latest | jq '.assets[] | select(.name|match("linux.tar.gz$")) | .browser_download_url' | sed 's"//g' | grep fleetctl | wget -q --show-progress --progress=bar:force -i -
Cheers :)

Hi, I encountered the same issue as kyiori-lw.
I tried your option, GitHopper33, but I am constantly getting an "The SSH command responded with a non-zero exit status". Not sure what else to try to install the logger.

Ok thanks for the info andrepintea97.  I saw a separate ssh issue here (I don't recall the issue #) which I would typically resolve by destroying and re-creating the logger.  In some cases, I had to delete the .vagrant folder as well.
Not sure if you had a typo or not in your example above (the before string doesn't match and the after string makes me wonder - lol).  Perhaps using the "add code" option in the comment tool bar will help keep whatever you type intact (that was helpful for me to post my solution accurately).  Either way, I'm glad your approach worked!

This works -
curl -s https://api.github.com/repos/fleetdm/fleet/releases/latest | jq '.assets[] | select(.name|match("linux.tar.gz$")) | .browser_download_url' | sed 's/"//g' | grep fleet | wget -q --show-progress --progress=bar:force -i -
curl -s https://api.github.com/repos/fleetdm/fleet/releases/latest | jq '.assets[] | select(.name|match("linux.tar.gz$")) | .browser_download_url' | sed 's/"//g' | grep fleetctl | wget -q --show-progress --progress=bar:force -i -

Thanks andreipintea97 and DYarizadeh - your examples show that that sed is flexible in the escaping character.  I also found this helpful tidbit on a post elsewhere:
"The character directly after the s determines which character is the separator, which must appear three times in the s command."

Fixed in https://github.com/clong/DetectionLab/commit/b002e6115ef20324f48829477e1bae5e9fb714ca , thanks for the updated command, @DYarizadeh !


undefined method `code' for nil:NilClass (NoMethodError) in Ruby 2.4 and 2.5

I have a code like this:
require 'rest-client'
require 'vcr'

require 'webmock'
include WebMock::API

WebMock.enable!

VCR.configure do |config|
  config.cassette_library_dir = "fixtures"
  config.hook_into :webmock
end

VCR.use_cassette 'response' do
  response = RestClient.post 'https://example.com/foo', {}
  hash = CGI.parse(response)
  puts "baz: #{hash['baz']}"
end

This is Gemfile:
# frozen_string_literal: true

source "https://rubygems.org"

git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }

gem 'rest-client', '2.0.2'
gem "webmock", '3.4.1', require: false
gem "vcr", '4.0.0', require: false

I could run it in Ruby 2.3.6:
$ ruby -v
ruby 2.3.6p384 (2017-12-14 revision 61254) [x86_64-darwin17]
$ bundle exec ruby ./sample.rb
baz: ["0"]

However, it fails in Ruby 2.4 and 2.5 with undefined method `code' for nil:NilClass (NoMethodError):
$ ruby -v
ruby 2.4.4p296 (2018-03-28 revision 63013) [x86_64-darwin17]
$ bundle exec ruby ./sample.rb
/Users/jit/.rbenv/versions/2.4.4/lib/ruby/gems/2.4.0/gems/rest-client-2.0.2/lib/restclient/abstract_response.rb:16:in `code': undefined method `code' for nil:NilClass (NoMethodError)
	from /Users/jit/.rbenv/versions/2.4.4/lib/ruby/gems/2.4.0/gems/rest-client-2.0.2/lib/restclient/response.rb:38:in `inspect'
	from ./sample.rb:17:in `inspect'
	from ./sample.rb:17:in `block in <main>'
	from /Users/jit/.rbenv/versions/2.4.4/lib/ruby/gems/2.4.0/gems/vcr-4.0.0/lib/vcr/util/variable_args_block_caller.rb:9:in `call_block'
	from /Users/jit/.rbenv/versions/2.4.4/lib/ruby/gems/2.4.0/gems/vcr-4.0.0/lib/vcr.rb:188:in `use_cassette'
	from ./sample.rb:14:in `<main>'

$ ruby -v
ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin17]
$ bundle exec ruby ./sample.rb
Traceback (most recent call last):
	6: from ./sample.rb:14:in `<main>'
	5: from /Users/jit/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/vcr-4.0.0/lib/vcr.rb:188:in `use_cassette'
	4: from /Users/jit/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/vcr-4.0.0/lib/vcr/util/variable_args_block_caller.rb:9:in `call_block'
	3: from ./sample.rb:17:in `block in <main>'
	2: from ./sample.rb:17:in `inspect'
	1: from /Users/jit/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rest-client-2.0.2/lib/restclient/response.rb:38:in `inspect'
/Users/jit/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rest-client-2.0.2/lib/restclient/abstract_response.rb:16:in `code': undefined method `code' for nil:NilClass (NoMethodError)

Here is a sample app to reproduce this issue:
https://github.com/JunichiIto/rest-client-sandbox
I investigated as far as I can, but I could not find the cause. Could you solve this issue, please?

I found a workaround. Passing copied string to CGI.parse can avoid this issue:
-  hash = CGI.parse(response)
+  hash = CGI.parse(response.to_s)

But I don't know why...

I found the cause of this issue. CGI.unescape is used in CGI.parse and its behavior has changed:
$ ruby -v -rcgi/util -e 'class S < String; end; puts CGI.unescape(S.new("a")).class'

ruby 2.3.6p384 (2017-12-14 revision 61254) [x86_64-darwin17]
String

$ ruby -v -rcgi/util -e 'class S < String; end; puts CGI.unescape(S.new("a")).class'

ruby 2.4.4p296 (2018-03-28 revision 63013) [x86_64-darwin17]
S

I submitted an issue to ruby-lang:
Bug #14732: CGI.unescape returns different instance between Ruby 2.3 and 2.4 - Ruby trunk - Ruby Issue Tracking System
I close this issue because rest-client is not the cause. Thank you.


Create a proposal for how test fixtures will work

Part of #1830

What
Using the results of the spike (https://github.com/alphagov/govuk-frontend/issues/1864), the pre-release (https://github.com/alphagov/govuk-frontend/issues/1866) and the draft documentation (https://github.com/alphagov/govuk-frontend/issues/1865), create a proposal that we can share with the community to gather feedback.
Why
By gathering feedback from the community early, we can validate whether our intended approach will work for port maintainers, and identify any potential issues.

Initial draft: https://docs.google.com/document/d/10YEYal0yWZcLBNT_4f2XDFHdl-m7z_qKKhHsmXhp7hE/edit

The proposal has been posted on the original issue


Generation fails with Spring Boot Version 2.3.12.RELEASE - Minimum version needed?

Hi,
I'm trying to generate a graphql-client for a third party application that we have to integrate. It seems that out Spring Boot version is too low? Whats the minimum required version of Spring Boot.
The problem arises with the RequestExecutionSpringReactiveImpl.java class.
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.10.1:compile (default-compile) on project reporting-service: Compilation failure   [ERROR] [...]/target/generated-sources/graphql-maven-plugin/com/graphql_java_generator/client/RequestExecutionSpringReactiveImpl.java:[251,110] cannot find symbol   [ERROR]   symbol:   method isOpen()   [ERROR]   location: variable session of type org.springframework.web.reactive.socket.WebSocketSession
So the org.springframework.web.reactive.socket.WebSocketSession in our project doesn't have this method (isOpen).
We are using Spring Boot 2.3.12.RELEASE which we cannot update at the moment.
So:

What's the minimum version of Spring Boot required?
Is there a version of this plugin that supports older Spring Boot version?
Is there some kind of configuration that can be done to prevent this problem?

Thank you

I didn't check the plug-in with every available versions.
I had issues with older versions, and I fear that 2.3.12 is too old.
But AFAIR, this is only for mutations.
Do you use mutations ?
Étienne

Yes the schema I'm trying to integrate does have mutations. It seems my version of spring-webflux is just a little too low, as the needed method was implemented only a little later.
Thanks for your answer, I'll try to update the specific dependency and then move on.


Update 2.x version code?

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

I am using Jupyterlab2 with some custom front-end plugin
So I am using 2.x version jupyter-archive
But there are many bug fixes that have not been synced to version 2.x, like zip a dir named aaa.bbb, the zip file name is displayed as aaa.zip, and I found that this had been fixed in 3.x version
Do we have any updates planned for version 2.x? Maybe I can refer to the code for version 3.x to update version 2.x?
Describe alternatives you've considered

Additional context

Python package version:

Extension version:

Operating System and its version:

Feel free to open a PR that merges the master branch in 2.x. If it works, I could do a new release.

Feel free to open a PR that merges the master branch in 2.x. If it works, I could do a new release.

Okay, I will do this work when I have time

Feel free to open a PR that merges the master branch in 2.x. If it works, I could do a new release.

Not many code changes https://github.com/jupyterlab-contrib/jupyter-archive/pull/77


Accessibility Audit - Carbon Website: Components - Pagination

This epic is tied to a larger "release" that is meant to track the progress of the Accessibility Audit for the Carbon Website. We will audit all of the pages of the carbon website based on AVT 1, AVT 2, & AVT3 - which can be found here.

AVT 1: will audit the site against the IBM Accessibility Checker - browser extension

AVT 2: will audit the site against accessible keyboard interactions

AVT 3: will audit the site against screen readers

Legend:

🌶 fully audited - on all three AVT levels

:one: 🔍 AVT 1 audited
:two: 🔍 AVT 2 audited
:three: 🔍 AVT 3 audited

:boom: issues and documentation - on all three AVT levels are complete

:one: 🚨 AVT 1 issues submitted
:two: 🚨 AVT 2 issues submitted
:three: 🚨 AVT 3 issues submitted

:sparkles: tickets are triaged

Current status of this page: 1⃣ 🔍 AVT 1 audited & 🚨 AVT 1 issues submitted

Components - Pagination

Usage: 6 issues - no new issues
Style: 3 issues - no new issues
Code: 6 issues - no new issues
Accessibility: 3 issues - no new issues

Closing due to inactivity. Will reopen if/when ready to be worked on again.


Robotframework wheel creation results in only the scripts for the platform being copied on installation

Description
After building a wheel (pip wheel -w dist .) we end up with an apparent platform independent file:
robotframework-3.0.4-py2-none-any.whl
When installing this wheel on a different platform, the correct scripts (pybot, robot, rebot) are not copied into the Scripts folder.  Only the platform scripts for the build machine are copied.

Wheels built in Linux won't have scripts for Windows (robot.bat, rebot.bat, pybot.bat)
Wheels built in Windows won't have scripts for Linux (robot, rebot, pybot)

Possible fixes:

Building the wheel copies scripts for both platforms
Builds can produce platform explicit wheels (not optimal)

Version information
Robot Framework version: 3.0.4
Python 2.7.15
Operating system and its version
Windows (8/10/2016) / Linux (CentOS7)
Steps to reproduce
Linux

Build wheel  pip wheel -w dist .
  unzip -l dist/robotframework-3.0.4-py2-none-any.whl | grep scripts
   70  2018-10-12 17:55   robotframework-3.0.4.data/scripts/pybot
  192  2018-10-12 17:55   robotframework-3.0.4.data/scripts/rebot
  188  2018-10-12 17:55   robotframework-3.0.4.data/scripts/robot

Note that the respective bat files are not present, so this build won't work in Windows without an explicit "python -m robot.run".

Windows

Build wheelpip wheel -w dist .

unzip -l dist\robotframework-3.0.4-py2-none-any.whl | find "scripts"
 35  2018-09-06 16:43   robotframework-3.0.4.data/scripts/pybot.bat
 90  2018-10-12 18:33   robotframework-3.0.4.data/scripts/rebot.bat
 88  2018-10-12 18:33   robotframework-3.0.4.data/scripts/robot.bat

Note that the respective shell scripts aren't present so this build won't work in Linux without an explicit "python -m robot.run".

Please test RF 3.1 preview releases. They use wheel by default, start-up scripts are exe-files on Windows, etc.
https://github.com/robotframework/robotframework/blob/master/doc/releasenotes/rf-3.1a2.rst

Thanks, I did see that the setup had changed in the preview version but
since we're using RF in production testing, I was reluctant to try it.
Thanks for the response.
On Fri, Oct 12, 2018, 2:39 PM Pekka Klärck<EMAIL_ADDRESS>wrote:

Please test RF 3.1 preview releases. They use wheel by default, start-up
scripts are exe-files on Windows, etc.
https://github.com/robotframework/robotframework/blob/master/doc/releasenotes/rf-3.1a2.rst
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/robotframework/robotframework/issues/2983#issuecomment-429439622,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGHRlzOnT5oitIIGdHkJ_bnyeUt95ia0ks5ukO_YgaJpZM4XaAMj
.

It would be good if you could test the 3.1 preview releases to see how installation enhancements work in your environment. There's not going to be any more 3.0.x releases, and getting possible problems fixed before 3.1 final would be obviously be great.

This issue is basically a duplicate of #1734 that is now fixed will be part of RF 3.1. The reason we couldn't provide wheels earlier was that our setup.py operating system specific code what wasn't executed when using wheels. That's also the exact reason for the problems mentioned in this issue and also caused problems explained in #2529. The problems preventing wheel usage were removed by #2415 and #2818. All the problems mentioned in this issue ought to thus be fixed now. If there are still problems, new issues should be submitted about them.

Confirmed fixed in 3.1a2.  Thanks for your help!


Remove mipsel target_arches

The mipsel target_arch was introduced with the initial MIPSel support (rust-lang/rust@82ec1aef293ddc5c6373bd7f5ec323fafbdf7901), but was subsequently removed with implementation of the Flexible Target Specification (Rust RFC 0131, rust-lang/rust@3a8f4ec32a80d372db2d02c76acba0276c4effd0). Remove these to be consistent with other arches and reduce confusion.
I've very slightly formatted the deletions so as to not require a style cleanup later and obscure git blame output.

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

(I was confused by this myself, and this is why I incorrectly done #443 when, in fact, the problem was that [replace]s inside sub-Cargo.tomls (instead of the root-level one) are ignored, not picking up my changes.)

Thanks!


[it] Linear algebra

[it] translation of Linear Algebra

Thank you @aepiotti for your hard work! Now, let's start the review process.

After an in-depth review of the translation by @Fodark
I think that this is ready for production ;)

Thank you both @aepiotti and @Fodark for all your work!


x/build/release: Windows installation has misconfigured ACL: privilege escalation possible between users

The Golang msi installer in Windows install by default Go in C:\Go location.
Files and subfolders of folders created under C:\ by default can be edited, created, deleted.

PS C:\Go> icacls .
  BUILTIN\Administrators:(I)(OI)(CI)(F)
  NT AUTHORITY\SYSTEM:(I)(OI)(CI)(F)
  BUILTIN\Users:(I)(OI)(CI)(RX)
  NT AUTHORITY\Authenticated Users:(I)(M)
  NT AUTHORITY\Authenticated Users:(I)(OI)(CI)(IO)(M)

This means that in a shared Windows environment, is it possible to exploit this insecure ACL to replace/backdoor go.exe binaries, dll and so on.
Scenario Local Privilege Escalation
A Standard User backdoor go.exe, waits for an Administrator to log in and run "go ..." or another component under C:\Go to successfully execute code under the latter elevated context.
Scenario Horizontal Privilege Escalation
A Standard User can backdoor/replace any component under C:\Go and wait for another Standard User to login and run Golang environment to achieve code execution in the context of the target user.
What version of Go are you using (go version)?
Up to latest Golang version: 1.13
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?

$ go env
set GOHOSTARCH=amd64
set GOHOSTOS=windows

What did you expect to see?
I was expecting the msi installer to reconfigure after installation the C:\Go default destination folder to have an ACL hardened to allow only Administrators, Administrator, SYSTEM, TrustedInstaller to have modify, write and special permissions over the Golang components.
What did you see instead?
Authenticated Users have Modify permission over any Golang component, thus local privilege escalation is possible.

Hello, is there any patch available in the MSI package installer codebase?

cc @dmitshur @toothrot


DRILL-4280: Kerberos Authentication

I am posting these changes from review. There are four commits in this pull request. All changes squashed are in this branch. There are 4 more commits that are in the squashed branch but not in this PR (tests, client changes including C++, etc.)
The last commit (not here yet) will move forward the RPC version that will starting using SASL for authentication.
Please refer to the design doc for details.

Addressed review comments
Updated commit messages
Rebased on latest master

@sohami @laurentgo any more comments?
(I need to push one minor change in config)

Just one last comment regarding moving BitConnectionConfig file. Apart from that LGTM.
+1 from my side.

+1
Thanks for the work guys, especially the extensive review comments.

Pushed the latest changes. The only thing left is the C++ build instructions for Cyrus SASL, which, as noted previously, I will commit as another patch.
Thanks to all the reviewers!


[MINOR] Disable the MDT for flink by default

Change Logs
Disable because there are some cross-engine issues that are stil suspended.
Impact
none
Risk level (write none, low medium or high below)
none
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

Change Logs
Disable because there are some cross-engine issues that are stil suspended.
Impact
none
Risk level (write none, low medium or high below)
none
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ]  Read through contributor's guide
[ ]  Change Logs and Impact were stated clearly
[ ]  Adequate tests were added if applicable
[ ]  CI passed

Wonder whether spark engine's compatibility issue

The table written by Flink has different compaction stratgies for MDT, which can not be handled correctly by Spark.


ci: merge staging to master

This is an automatic PR generated by the pipeline CI/CD. This will be automatically fast-forward merged if successful.

Pipeline Attempt on 914222646 for 2a915c3fadd0eb8daaea71bb320b5c1e605a303f
https://gitlab.com/MatrixAI/open-source/js-errors/-/pipelines/914222646

Pipeline Succeeded on 914222646 for 2a915c3fadd0eb8daaea71bb320b5c1e605a303f
https://gitlab.com/MatrixAI/open-source/js-errors/-/pipelines/914222646


Tweak color hierachy & add hint to what "•" represents

Coverage increased (+0.006%) to 89.753% when pulling a89aeebfe321005fd7e88bdf8f7c124e08779f96 on jeremyh:develop into bcbefc4dd0642aa9d9ac4cb55c93f69d0957652d on opendatacube:develop.


Connection demo app: Connection cancelled during verification

Same as Connection cancelled modal but the primary action should return user to Verify Your Account Modal.

[ ] Tests

Didn't pass QA: "Browse as guest" should close all windows, essentially cancelling connection. At the moment the screen for the step you were on persists (e.g. verification pending screen) which the user has to close manually.


Fatal Errors in MacOS Installation

Hi,
I am continuously running into a fatal error in Dogecoin Core installation.
make: *** No targets specified and no makefile found.  Stop.
I have run:
$./autogen.sh
$./configure
$make

with several variations and fix attempts that simply do not have an effect on the outcome.

Bug Report
Current behavior:

Attempting to install Dogecoin Core via: Make
make: *** No targets specified and no makefile found.  Stop.
Expected behavior

Proper installation.
Steps to reproduce:

To reproduce follow the Installation Steps  for MacOS.
Machine specs

OS:

make is saying there is no Makefile (which is built by configure). Either make is being run from the wrong directory, or the ./configure step failed in which case the output will need to be part of the ticket to know what went wrong.

Thank you very much @donpdonp
Yes. You are correct. ./configure is failing. Here is the error:
configure: error: libdb_cxx headers missing, Dogecoin Core requires this library for wallet functionality (--disable-wallet to disable wallet functionality)

configure: error: libdb_cxx headers missing, Dogecoin Core requires this library for wallet functionality (--disable-wallet to disable wallet functionality)

Currently, the only way I have personally been able to make this work on a Mac natively is by passing --with-incompatible-bdb to ./configure and using brew bdb. The contrib/install_db5.sh does not work for me on either x86_64 or arm64 Macs, as it errors out on runtime. This is an open issue.
Note that when you use an incompatible bdb version, wallets will not be portable, so use that with caution.

configure: error: libdb_cxx headers missing, Dogecoin Core requires this library for wallet functionality (--disable-wallet to disable wallet functionality)

Currently, the only way I have personally been able to make this work on a Mac natively is by passing --with-incompatible-bdb to ./configure and using brew bdb. The contrib/install_db5.sh does not work for me on either x86_64 or arm64 Macs, as it errors out on runtime. This is an open issue.
Note that when you use an incompatible bdb version, wallets will not be portable, so use that with caution.

I ran:
./configure  --with-incompatible-bdb
And got the same error:
configure: error: libdb_cxx headers missing, Dogecoin Core requires this library for wallet functionality (--disable-wallet to disable wallet functionality)
I may try again once I am able to get a new machine. In the meantime, please feel free to share a link here if a fix is found.

./configure --with-incompatible-bdb

Yes. Thanks for your help. I just ran it:
$brew install berkeley-db@5
$./autogen.sh
$./configure

but got the same error.
configure: error: libdb_cxx headers missing, Dogecoin Core requires this library for wallet functionality (--disable-wallet to disable wallet functionality)


Subtitles

I noticed the subtitles switch is stuck on is there anywhere to fix this? Thank you in advance.

Duplicate of #23

Duplicate of #23
this has been fixed now for the next coming patch.

this has been fixed now for the next coming patch. expect it soon !


Error when settings properties for IoTEdge module

Looks like the container create options is too long when using the Azure portal wizard. At least if i add something i will exceed the 512 bytes limit.
BadRequest:{ "Message": "ErrorCode:ArgumentInvalid;Property or Tag value should be maximum 512 bytes.`

You can save a few bytes by removing the tabs/spaces from your CreationOptions JSON.
I know it's not a fix but this removed just enough characters for me to solve this issue.

I had the same issue. With the recent 1.0.4 release of IoT Edge runtime/modules this should be fixed (size is now limited to 4K).
See also https://github.com/Azure/iotedge/commit/ecfc2a0d30edced286c42d5090bd9eb953251b86

@sandervandevelde thanks for pointing this out. i have not verified it. i will also add an option to change the root directory of the certstore, then there is no need to specify locations for each store (trusted, rejected,..) separately.
I will follow-up with the portal team if they can change it to compress the JSON entered in the portal before they check the size.


Cannot connect when running on a different port than 5000

Describe the bug
I have a process already running on port 5000, so I need to start IBeam on a different port.  When changing the port, I am able to authenticate, but I am unable to connect to the gateway process.
To Reproduce
Steps to reproduce the behavior:

Add the following to docker-compose.yml:

    ports:
      - 8080:8080

or
    ports:
      - 8080:5000

Restart container
Authenticate
curl

% curl -X GET "https://localhost:8080/v1/api/portfolio/accounts" -k
curl: (35) LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to localhost:8080

Expected behavior
Non-failure
Environment
IBeam version: 0.4.0-rc7
Docker image or standalone: Docker
Python version (standalone users only):
OS: macOS 12.2.1
Additional context
I have tried to adjust IBEAM_GATEWAY_BASE_URL=https://localhost:8080 in conjunction with the various port changes, and also tried to change listenPort: 8080 in conf.yaml without any success, and some of these changes break authentication.

Hey @jlixfeld thanks for reporting your issue 👍
I've put down a guide for changing ports: https://github.com/Voyz/ibeam/wiki/IBeam-Configuration#changing-port
To reiterate:

Modify listenPort value in conf.yaml, eg: listenPort: 8000
Provide environment variable IBEAM_GATEWAY_BASE_URL with a URL modified to the port we want to set, eg: IBEAM_GATEWAY_BASE_URL=https://localhost:8000
Run IBeam, mapping the new port, eg. docker run -p 8000:8000

From your comments I'm reasoning that you've already attempted all of that - is that correct? If so, could you please attach debug logs of IBeam so we could analyse what it does once you perform that change?
Thanks! 😊 Voy

What I was trying must have been incomplete, because your complete example provided here works perfectly!
Thank you!!

Ah glad to hear @jlixfeld 😊 Happy to have helped!


{N} Android crashes on Windows with ng2-config & map operator

I'm submitting a ...  (check one with "x")
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see use [gitter](https://gitter.im/mgechev/angular2-seed) or [stackoverflow](https://stackoverflow.com/questions/tagged/angular2)

Current behavior

When trying to run start.android on Windows with the current HEAD (https://github.com/NathanWalker/angular-seed-advanced/commit/7a412db93af0606b23267b0aca4b8fca62738ce2), the following happens:
JS: ns-renderer: ERROR BOOTSTRAPPING ANGULAR
JS: ns-renderer: this.http.get(...).map is not a function
JS:
JS: TypeError: this.http.get(...).map is not a function
JS:     at t.init (/data/data/com.yourdomain.appname/files/app/tns_modules/ng2-config/bundles/ng2-config.umd.min.js:1:2270)
JS:     at Array.<anonymous> (/data/data/com.yourdomain.appname/files/app/tns_modules/ng2-config/bundles/ng2-config.umd.min.js:1:3162)
JS:     at new ApplicationInitStatus (/data/data/com.yourdomain.appname/files/app/tns_modules/nativescript-angular/node_modules/@angular/core/bundles/core.umd.js:3028:49)
JS:     at NgModuleInjector.get (/NativeModule/module.ngfactory.js:96:87)
JS:     at NgModuleInjector.NativeModuleInjector.createInternal (/NativeModule/module.ngfactory.js:393:153)
JS:     at NgModuleInjector.create (/data/data/com.yourdomain.appname/files/app/tns_modules/nativescript-angular/node_modules/@angular/core/bundles/core.umd.js:6715:80)
JS:     at NgModuleFactory.create (/data/data/com.yourdomain.appname/files/app/tns_modules/nativescript-angular/node_modules/@angular/core/bundles/core.umd.js:6700:22)
JS:     at /data/data/com.yourdomain.appname/files/app/tns_modules/nativescript-angular/node_modules/@angular/core/bundles/core.umd.js:6418:47
JS:     at ZoneDelegate.invoke (/data/data/com.yourdomain.appname/files/app/tns_modules/nativescript-angular/zone-js/dist/zone-nativescript.js:190:28)
JS:     at Object.onInvoke (/data/data/com.yourdomain.appname/files/app/tns_modules/nativescript-angular/node_modules/@angular/core/bundles/core.umd.js:5976:41)

Expected behavior

The application should run.
Minimal reproduction of the problem with instructions

Start fresh from https://github.com/NathanWalker/angular-seed-advanced/commit/7a412db93af0606b23267b0aca4b8fca62738ce2
yarn
npm run start.android (also tried cd nativescript && tns run android since I'm using Genymotion)

I figured this was a problem related to the recent addition of ng2-config, so I revert to a previous version  before it was included (https://github.com/NathanWalker/angular-seed-advanced/commit/4da2e0de2a1446b2a5bf7208ff72784117905086) and the Android app runs fine.
What is the motivation / use case for changing the behavior?

Please tell us about your environment:

npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "start.livesync.android.device"
npm ERR! node v6.4.0
npm ERR! npm  v3.10.3

Angular Seed Version: 7a412db
(as stated above at least 4da2e0d doesn't have this issue)

Node: node --version = v6.4.0

...and Merry Christmas! 🎄 😉

+1

+1

Try running npm ls rxjs in the nativescript-folder.

@m-abs it is there, and as I mentioned the problem is android only, it works fine on iOS.

+1

Ahh I see.
I think this is caused by nativescript-angular still being stuck on angular-2.2.x while this project is at angular-2.4.x.
I think you have to downgrade angular, rxjs and zone.js, until nativescript-angular gets updated, hopefully after new year when this PR is closed.
In the mean while use this package.json in the nativescript-folder:
{
  "name": "angular-seed-advanced",
  "main": "app.js",
  "version": "0.0.0",
  "nativescript": {
    "id": "com.yourdomain.appname",
    "tns-ios": {
      "version": "2.4.0"
    },
    "tns-android": {
      "version": "2.4.1"
    }
  },
  "scripts": {
    "clean": "rm -rf platforms node_modules lib hooks"
  },
  "dependencies": {
    "@angular/common": "~2.2.0",
    "@angular/compiler": "~2.2.0",
    "@angular/core": "~2.2.0",
    "@angular/forms": "~2.2.0",
    "@angular/http": "~2.2.0",
    "@angular/platform-browser": "~2.2.0",
    "@angular/platform-browser-dynamic": "~2.2.0",
    "@angular/router": "~3.2.1",
    "@ngrx/core": "^1.2.0",
    "@ngrx/effects": "^2.0.0",
    "@ngrx/store": "^2.2.1",
    "angulartics2": "^1.6.1",
    "es6-promise": "^3.0.2",
    "es6-shim": "^0.35.0",
    "lodash": "^4.16.4",
    "nativescript-angular": "next",
    "nativescript-theme-core": "^1.0.2",
    "ng2-config": "1.1.1",
    "ng2-translate": "^5.0.0",
    "ngrx-store-freeze": "0.1.0",
    "parse5": "1.3.2",
    "punycode": "1.3.2",
    "querystring": "0.2.0",
    "reflect-metadata": "^0.1.8",
    "rxjs": "5.0.0-beta.12",
    "tns-core-modules": "2.4.2",
    "url": "0.10.3"
  },
  "devDependencies": {
    "@ngrx/store-devtools": "^3.2.2",
    "@types/jasmine": "^2.5.35",
    "babel-traverse": "6.12.0",
    "babel-types": "6.11.1",
    "babylon": "6.8.4",
    "filewalker": "0.1.2",
    "lazy": "1.0.11",
    "nativescript-dev-typescript": "^0.3.2",
    "shelljs": "^0.7.0",
    "typescript": "^2.0.9",
    "zone.js": "^0.6.21"
  }
}

Unfortunately this means that web and {N} will run with different versions of those packages, this might lead to inconsistent behavior.

Updating package.json with above, in nativescript folder, still crashes android on windows for me.

@ponty7
Have you have tried running npm run clean in the nativescript-folder?
If not try that and reinstall again.
I had the same problem, I should have mentioned that a reset was needed.

although that fixes android, it'll break again when we move up to ng2 2.4.1.
the solution is for @fulls1z3 to fix ng2-config

Hi @fourctv, I have updated ng2-config to work with ng2 2.4.1 and rxjs 5.0.1. The latest version is 1.1.2 now.
I'll test the source of angular-seed-advanced with with ng2-config 1.1.2 and PR the results accordingly.

@fulls1z3 thanks, just pushed to master the new 1.1.2 ng2-config.
Runs on Android here for me but I don't think I tried with map operator, however @fourctv please pull latest master and let us know.

Just tried from a previous non-working installation with

npm run git.merge
npm install
cd nativescript
npm install
tns run android

...and the same problem remains?
Here's my npm list output in the nativescript folder (note ng2-config@1.1.2):
<EMAIL_ADDRESS>F:\dev\angular-seed-advanced\nativescript
+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | | `--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>|   `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| `-- UNMET PEER DEPENDENCY<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   `--<EMAIL_ADDRESS>|     `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | |   +--<EMAIL_ADDRESS>| | |   `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>|   `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>
I take it @m-abs's advice to downgrade angular to 2.2.4 because of nativescript-angular is still applicable?

@ghys
A minor update:
nativescript-angular@next are at angular 2.3.1 now, so you need to downgrade angular to 2.3.1 and rxjs to 5.0.0-rc.4.
I haven't tested it yet, as I'm working on #323 and it breaks webpack-bundling for now...

I experience no issues on my end, just cloned latest master, npm i, then npm start... all other build commands also work including {N} for iOS and Android. ?

@fourctv ensure you have done this:
cd nativescript
rm -rf hooks lib node_modules platforms
npm i
tns run android

I'm on node 6.9.1 and npm 3.10.9 with Mac Sierra.

Also what version of {N} do you have installed?
run: tns --version
I am on 2.4.2.
To update:
npm i -g nativescript
Then you would need to do this again:
cd nativescript
rm -rf hooks lib node_modules platforms
npm i
tns run android

@NathanWalker I am also on tns 2.4.2 and node 6.9.1. On El Captain, and npm 3.10.8.
I just downloaded a fresh seed master, ran:
npm i
npm start
npm run start.android

Web runs fine, but android fails at the exact same place: http.map...
And again, if I change nativescript/package.json and force rxjs to version 5.0.0-rc.4 and then do:
cd nativecript
npm run clean
cd ..
npm run start.android

It works, so whatever the problem is, it is related to rxjs version. It could even be something on my environment, but I cannot think of anything as we seem to be running the same versions 9except for npm)

+1

@fourctv I believe I will remove ng2-config for reasons stated here and here unless @fulls1z3 has a solution.

@NathanWalker agreed

Hi @fourctv @NathanWalker @ponty7 .
Sorry for late answer, but it seems we're all suffering just after the stability interjection as of angular 2.4.0.
If I understood correctly, we're talking about an incompability between ng2-config and rxjs 5.0.2. I'll update the ng2-config to work with the latest rxjs (5.0.2), test and share results with you shortly.
Meantime, any ideas or support is appreciated.

@ghys @fourctv ng2-config is now removed on master. Please pull in these latest changes (which reverts things back to how they were before) and lemme know if all good for you. Ensure to clean everything once again after the pull:
git fetch upstream
git merge upstream/master
rm -rf node_modules nativescript/node_modules nativescript/hooks nativescript/lib nativescript/platforms
npm i

@NathanWalker don't know if it's just me, but I'm going through dependency hell...
With an untouched nativescript/package.json from the latest changes, the graph looks like this:
+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>
and the result (at least for me) is a stack overflow:
JS: ns-renderer: ERROR BOOTSTRAPPING ANGULAR
JS: ns-renderer: Maximum call stack size exceeded
JS:
JS: RangeError: Maximum call stack size exceeded
JS:     at ScanSubscriber.Subscription (/data/data/com.yourdomain.appname/files/app/tns_modules/rxjs/Subscription.js:25:26)
JS:     at ScanSubscriber.Subscriber [as constructor] (/data/data/com.yourdomain.appname/files/app/tns_modules/rxjs/Subscriber.js:32:16)
JS:     at new ScanSubscriber (/data/data/com.yourdomain.appname/files/app/tns_modules/rxjs/operator/scan.js:79:16)
JS:     at ScanOperator.call (/data/data/com.yourdomain.appname/files/app/tns_modules/rxjs/operator/scan.js:67:33)
JS:     at AnonymousSubject.Observable.subscribe (/data/data/com.yourdomain.appname/files/app/tns_modules/nativescript-angular/node_modules/rxjs/Observable.js:42:22)
JS:     at ScanOperator.call (/data/data/com.yourdomain.appname/files/app/tns_modules/rxjs/operator/scan.js:67:23)
JS:     at AnonymousSubject.Observable.subscribe (/data/data/com.yourdomain.appname/files/app/tns_modules/nativescript-angular/node_modules/rxjs/Observable.js:42:22)
JS:     at ScanOperator.call (/data/data/com.yourdomain.appname/files/app/tns_modules/rxjs/operator/scan.js:67:23)
JS:     at AnonymousSubject.Observable.subscribe (/data/data/com.yourdomain.appname/files/app/tns_modules/nativescript-angular/node_modules/rxjs/Observable.js:42:22)
JS:     at ScanOperator.call (/data/data/com.yourdomain.appname/files/app/tns_modules/rxjs/operator/scan.js:67:23)
JS:     at AnonymousSubject.Observable.subscribe (/data/data/com.yourdomain.appname/files/app/tns_modules/nativescript-angular/node_modules/rxjs/Observable.js:42:22)

So then I downgraded Angular and rxjs to match nativescript-angular's versions (2.3.1 & 5.0.0-rc4, respectively, with the router @ ~3.3.1), and I got this instead - a problem with angulartics2:
JS: ns-renderer: ERROR BOOTSTRAPPING ANGULAR
JS: ns-renderer: router.events.filter is not a function
JS:
JS: TypeError: router.events.filter is not a function
JS:     at Angulartics2.trackLocation (/data/data/com.yourdomain.appname/files/app/tns_modules/angulartics2/dist/core/angulartics2.js:33:14)
JS:     at new Angulartics2 (/data/data/com.yourdomain.appname/files/app/tns_modules/angulartics2/dist/core/angulartics2.js:28:14)
JS:     at NgModuleInjector.get (/NativeModule/module.ngfactory.js:173:69)
JS:     at NgModuleInjector.get (/NativeModule/module.ngfactory.js:183:108)
JS:     at NgModuleInjector.get (/NativeModule/module.ngfactory.js:313:117)
JS:     at NgModuleInjector.NativeModuleInjector.createInternal (/NativeModule/module.ngfactory.js:388:101)
JS:     at NgModuleInjector.create (/data/data/com.yourdomain.appname/files/app/tns_modules/nativescript-angular/node_modules/@angular/core/bundles/core.umd.js:8897:80)
JS:     at NgModuleFactory.create (/data/data/com.yourdomain.appname/files/app/tns_modules/nativescript-angular/node_modules/@angular/core/bundles/core.umd.js:8871:22)
JS:     at /data/data/com.yourdomain.appname/files/app/tns_modules/nativescript-angular/node_modules/@angular/core/bundles/core.umd.js:8443:65
JS:     at ZoneDelegate.invoke (/data/data/com.yourdomain.appname/files/app/tns_modules/nativescript-angular/zone-js/dist/zone-nativescript.js:190:28)

I tried downgrading angulartics2 a few versions but was unsuccessful in resolving this, so as a last resort I brought everything back to<EMAIL_ADDRESS><EMAIL_ADDRESS>and<EMAIL_ADDRESS>pinned down a few packages and now have a version that seems to work.
Here's my package.json diff for the interested:
diff --git a/nativescript/package.json b/nativescript/package.json
index eb9bb18..184253a 100644
--- a/nativescript/package.json
+++ b/nativescript/package.json
@@ -15,30 +15,30 @@
     "clean": "rm -rf platforms node_modules lib hooks"
   },
   "dependencies": {
-    "@angular/common": "~2.4.0",
-    "@angular/compiler": "~2.4.0",
-    "@angular/core": "~2.4.0",
-    "@angular/forms": "~2.4.0",
-    "@angular/http": "~2.4.0",
-    "@angular/platform-browser": "~2.4.0",
-    "@angular/platform-browser-dynamic": "~2.4.0",
-    "@angular/router": "~3.4.1",
+    "@angular/common": "~2.2.3",
+    "@angular/compiler": "~2.2.3",
+    "@angular/core": "~2.2.3",
+    "@angular/forms": "~2.2.3",
+    "@angular/http": "~2.2.3",
+    "@angular/platform-browser": "~2.2.3",
+    "@angular/platform-browser-dynamic": "~2.2.3",
+    "@angular/router": "~3.2.0",
     "@ngrx/core": "^1.2.0",
     "@ngrx/effects": "^2.0.0",
     "@ngrx/store": "^2.2.1",
-    "angulartics2": "^1.6.3",
+    "angulartics2": "1.6.1",
     "es6-promise": "^3.0.2",
     "es6-shim": "^0.35.0",
     "lodash": "^4.16.4",
-    "nativescript-angular": "next",
+    "nativescript-angular": "1.3.0-2016-12-15-1167",
     "nativescript-theme-core": "^1.0.2",
-    "ng2-translate": "^5.0.0",
+    "ng2-translate": "^4.2.0",
     "ngrx-store-freeze": "0.1.0",
     "parse5": "1.3.2",
     "punycode": "1.3.2",
     "querystring": "0.2.0",
     "reflect-metadata": "^0.1.8",
-    "rxjs": "5.0.2",
+    "rxjs": "5.0.0-beta.12",
     "tns-core-modules": "2.4.4",
     "url": "0.10.3"
   },
@@ -53,6 +53,6 @@
     "nativescript-dev-typescript": "^0.3.5",
     "shelljs": "^0.7.0",
     "typescript": "^2.0.9",
-    "zone.js": "^0.7.2"
+    "zone.js": "^0.6.21"
   }
 }

I'll try updating back to the latest versions in a few weeks or once nativescript-angular and the seed target the same Angular/rxjs.
Cheers!

+1 I've wiped/cleaned nativescript folder and I get exact same errors too, on Windows 10.
tns - 2.4.2
npm - 3.10.9
node - v6.9.2

@NathanWalker I followed your steps above to pull in the latest changes, and subsequently followed the "Building with Webpack for release builds" steps. I can confirm I'm also experiencing the same call stack issue as @ghys when then running:
npm run start.android

...

Successfully deployed on device with identifier 'emulator-5554'.

Node: v6.9.4
NPM: 3.10.10
TSC: 2.1.4

@NathanWalker FYI, android now builds and runs fine, thanks for fixing that.

@fourctv Can you display all versions of you node_modules dependencies? I'm afraid because you have an older version of the seed, Android will work for you, but not for others who cloned at a later date. This is the problem you get when you don't have fixed versions in package.json, people cloning at later date get updated versions that might work at runtime. I bet if you ran 'npm update' it won't work for you either (don't do this, just saying).

Here it goes @ponty7
Running El captain 10.11.6, using VSCode 1.8.1.

Also make sure you do:
cd nativescript
npm run clean
cd ..
npm run start.android

Are you having trouble with a fresh copy of the seed? That's something I try to do when I run in trouble after a merge. Ensure that it is not my code.
Now, re-reading your post, I noticed that you're saying you're having trouble on Windows 10. But you list your versions as OSX. That confused me... I run OSX here, and the trouble I was having before on android was caused by n2-config, which was removed in the latest seed.
I can't say anything about Win 10, but OSx works like a charm.


Ui refactor

In progress. Needs to add refactor Logic as well.
Reconstructed MainWindow.java
Ignore changes made outside Ui Package

我好桑心


Allow HTML to expandableSkipLabel

Hey !
Can you allow HTML in the expandableSkipLabel option please ?
Thank you.

Added expandableHideHtml and expandableShowHtml meta, you can find info on readme.MD

tag v1.4.0
tag v2.3.0
tag v3.3.0


X-Frame-Options or 'frame-ancestors'

https://www.dareboost.com/en/report/d_15d773f2190b99843ddb4b550?reportIds=d_15d773f2190b99843ddb4b550

Server-side too, closing


Better Communicate Actions: Screen Applications

[x] Appears in primary when application has not been screened for staff, text is 'Screen application', uses primary button styling
[x] Appears in secondary and is changeable at all times for staff, matches designs below

[x] It is never visible to applicants, reviewers or partners

From #1851

@abigail-hampson this one is ready for testing

Acceptance criteria were visible and functional during test. Thank you! 💥


Goto Definition for variables

Currently I'm only providing definitions for rules. If a symbol starts with one of 4 characters, then treat it as a variable and look for the line $variable =
$, #, @, !

Reference: http://yara.readthedocs.io/en/v3.7.0/writingrules.html#conditions

I need to figure out how to bound the search to the rule. Might require

grabbing all lines defining a rule (^rule )
grabbing all lines ending a rule (^}$)
finding nearest rule start and rule end to the symbol needing defined
Running doc.getText() across that range
Performing a similar search to what the "rule" function already has

Added in 01c9a4c9b7795494488bacab20cacec9a83e67d3


add browserify transforms

This is related to #1. I decided to put the transform options into each bundle. If you're not happy with the API please bare with me.

Cool! I'll take a look at this tomorrow.


Remove now-unused Arcade content

Followup https://github.com/microsoft/go/pull/1156
For https://github.com/microsoft/go-lab/issues/52

Remove Arcade content and supporting files.

Da'Good.


unable to find policy ArrayPolicy

Pundit is unable to find class for a CollectionProxy(Array) which contains several elements of a Model inside

I think you might have a subtle security bug in your controller code. A single authorize check will determine if the controller action is valid. In your case you are calling authorize multiple times and I think your last result will determine if the action can run. Have you tested this using an array with mixed values like [true, true, false]?

@darylprickett Tried what you say and when a instance of authorize calls a raise it fails to update. To simplify the process I made a method on application_controller.rb
def authorize_many(model_collection)
    model_collection.each do |model_instance|
      authorize model_instance
    end
  end

authorize is meant to be used with a single object. I think that's well documented, and the fact that it doesn't work with an Array isn't really an "issue", so I'm closing this. Let's continue discussing this in #256 :)


feat: add Relay CONNECT adapters

Why
enable_outbound_relay() is being deprecated in favour of adapters for common HTTP clients e.g requests and aiohttp
How

Introduce new functions relay_requests_adapter() and relay_asyncio_ssl_context()
Each function works in different ways relay_asyncio_ssl_context configures requests HTTPAdapter with Relays basic auth credentials. Whereas relay_asyncio_ssl_context must configure the SSL context for the async runtime asyncio. A workaround is in place to set the SSL context of asyncio to allow CONNECT over TLS until asyncio mainlines the feature.

Code looks good but we should add a depreciation warning to the enable outbound relay function. https://pypi.org/project/Deprecated/

I had added that but removed it, enable_outbound_relay() might be the only sane way to actually use the majority of python SDK's. Most SDK's allow you to set a client as e.g requests but that then means that all traffic will flow through relay from the App as you must set the global requests session adapter to use Relay. This is because SDK's dont take an instance of requests.Session but requests itself.


[SPARK-47111][SQL][TESTS][3.4] Upgrade PostgreSQL JDBC driver to 42.7.2 and docker image to 16.2

What changes were proposed in this pull request?
This is a backport of #45191 .
This PR aims to upgrade PostgreSQL JDBC driver and docker images.

JDBC Driver: org.postgresql:postgresql to 42.7.2
Docker Image: postgres from 15.1-alpine to 16.2-alpine

Why are the changes needed?
To use the latest PostgreSQL combination in the following integration tests.

PostgresIntegrationSuite
PostgresKrbIntegrationSuite
v2/PostgresIntegrationSuite
v2/PostgresNamespaceSuite

Does this PR introduce any user-facing change?
No. This is a pure test-environment update.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.

Merged to branch-3.4 for Apache Spark 3.4.3.


Dev error

@vreuter Not sure if I'm doing something wrong but the current dev version is passing tests but fails on a real run:
looper run pconfig.yaml -d
Traceback (most recent call last):
  File "/home/ns5bc/.local/bin/looper", line 9, in <module>
    load_entry_point('looper==0.6.0.dev0', 'console_scripts', 'looper')()
  File "/share/apps/python/2.7.6/lib/python2.7/site-packages/pkg_resources/__init__.py", line 549, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/share/apps/python/2.7.6/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2542, in load_entry_point
    return ep.load()
  File "/share/apps/python/2.7.6/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2202, in load
    return self.resolve()
  File "/share/apps/python/2.7.6/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2208, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/home/ns5bc/.local/lib/python2.7/site-packages/looper/looper.py", line 29, in <module>
    from looper.models import \
ImportError: No module named models

is it working for you?

I moved a few things around and progress to this:
Command: run (Looper version: 0.6.0-dev)
Traceback (most recent call last):
  File "/home/ns5bc/.local/bin/looper", line 9, in <module>
    load_entry_point('looper==0.6.0.dev0', 'console_scripts', 'looper')()
  File "/home/ns5bc/.local/lib/python2.7/site-packages/looper/looper.py", line 749, in main
    looperenv_file=getattr(args, 'env', None))
  File "/home/ns5bc/.local/lib/python2.7/site-packages/looper/loodels.py", line 41, in __init__
    config_file, default_compute, *args, **kwargs)
TypeError: __init__() got an unexpected keyword argument 'looperenv_file'

it appears for me the looper-specific Project is broken?

Ah yeah I guess we could keep looperenv_file as the name for the looper version, but it's now renamed more genetically. While I don't think it's a good idea to change the signature to the parameter names, if you prefer we do that in this case, I'm alright with it.

This underscores some value in having a few cases run through the looper CLI API within the suite though

genetically or generically? What have you been reading lately :stuck_out_tongue: ?
I wasn't suggesting anything in particular, just trying to understand it and make it work...

A new error with this update:
Traceback (most recent call last):
  File "/home/ns5bc/.local/bin/looper", line 9, in <module>
    load_entry_point('looper==0.6.0.dev0', 'console_scripts', 'looper')()
  File "/home/ns5bc/.local/lib/python2.7/site-packages/looper/looper.py", line 772, in main
    run(prj, args, remaining_args, interface_manager=interface_manager)
  File "/home/ns5bc/.local/lib/python2.7/site-packages/looper/looper.py", line 315, in run
    argstring += prj.get_arg_string(pl_id)
  File "/home/ns5bc/.local/lib/python2.7/site-packages/looper/models.py", line 774, in get_arg_string
    default_argtext = create_argtext("default")
  File "/home/ns5bc/.local/lib/python2.7/site-packages/looper/models.py", line 770, in create_argtext
    optargs_texts = map(make_optarg_text, optargs.items())
TypeError: make_optarg_text() takes exactly 2 arguments (1 given)

you're calling the function with incorrect number of args...

This is happening for flag-like options that have no argument. so it's only passing 1 (or rather ['-arg', None]) and confusing the function.

Actually turns out there's a few different issues here, so I think we need some new test cases. I think this should fix it but we need some tests for:

pipelines with no project_config options
null (flag-like) options

Next is a logger error:
Logged from file looper.py, line 373
Traceback (most recent call last):
  File "/share/apps/python/2.7.6/lib/python2.7/logging/__init__.py", line 851, in emit
    msg = self.format(record)
  File "/share/apps/python/2.7.6/lib/python2.7/logging/__init__.py", line 724, in format
    return fmt.format(record)
  File "/share/apps/python/2.7.6/lib/python2.7/logging/__init__.py", line 464, in format
    record.message = record.getMessage()
  File "/share/apps/python/2.7.6/lib/python2.7/logging/__init__.py", line 328, in getMessage
    msg = msg % self.args
TypeError: not all arguments converted during string formatting

Not sure what's going on here, but there's now some problem with the way failures are reported.

Ok I fixed it, but this is now backwards to the way it used to be (and should be) isn't it? It shouldn't show errors sample-wise, but error-wise, with a list of samples. I'm pretty sure that's what it used to do. Now it's showing just a list of failed samples and why. It's also doubling some error messages.

This would be prevented by #38 if we get around to that.

BTW toggle is actually still not functional. adding this to the checklist...

https://github.com/epigen/looper/pull/106 addresses the first four of the tasks here (tests regarding pipeline_args and the reversion of the skip reason reporting strategy).


New step: Log File Scraper

Please include answers to these questions as part of your pull request
In the GitHub webUI, use the Write tab to modify the Markdown text that is part of the pull request. For each question simply place an X inside the square brackets, [X], that represents your answer. Make sure there are no blanks inside the brackets, otherwise MarkDown doesn't render properly. Using the Preview tab while editing this form, you can see the formatted/rendered version of the message.

Q1: Confirm that you have the right to submit the code that is being contributed. Please consider the origin of your code and confirm you have the appropriate rights to make the submission subject to the Apache 2.0 license that applies to everything in this repository of custom steps. If so, follow the instructions for the Contributor Agreement (which is based on the industry-standard Developer Certificate of Origin (DCO)).

[X] Yes, I have the right to submit the contributed code on behalf of myself, my company, or any other owner of the code. I have also attached my signed copy of the DCO to this message.
[ ] No

Q2: Confirm that your contribution does not include any personally identifiable information (PII), for example, in any examples used in your README file.

[X] My contribution does NOT include PII data
[ ] My contribution includes PII data

Q3: Confirm your contribution does not include any encryption or other export-controlled technology.

[X] My contribution does NOT contain encryption or other export-controlled technology
[ ] My contribution includes encryption or other export-controlled technology

ContributorAgreement - Remco Gooijer.txt

SAS Internal Due Diligence Review - COMPLETED on 08NOV2024

@x7rtfgj4, oOnly after performing the merge I noticed that this entry des not adhere the capitalization convention for folder names and step names. So made the following additional changes:

Renamed folder and step to use: Log File Scraper
Modified README and About tab


number prompt: default value validation

When I check a wholeNumber to true and enter a decimal for the default value, even though the app highlight the wrong default value area in red (which is cool), if I go ahead and click submit, it will allow me to go ahead and submit..
If there is a failed validation, shouldn't it pop up an error message instead of allowing the campaign to be submitted?  In this case, since there is a server bug, the campaign submission is successful which is kind of confusing..

No, the client only tries to give hints by highlighting fields that looks wrong, but does not 100% implement all xml validation logic. Only the server can determine if a submission will be accepted.


what is the di dj dk means ?

good job! thanks for your work!
I’m confused in this code in your FASNET_model.py，why the di = s1//2 ? what is this meaning?
and i'm not find it in your paper
`
       def SSR_module(x,s1,s2,s3,lambda_d):

        a = x[0][:,:,0]*0
        b = x[0][:,:,0]*0
        c = x[0][:,:,0]*0

        di = s1//2
        dj = s2//2
        dk = s3//2

        V = 99
        #lambda_d = 0.9

        for i in range(0,s1):
            a = a+(i-di+x[6])*x[0][:,:,i]
        a = a/(s1*(1+lambda_d*x[3]))

        for j in range(0,s2):
            b = b+(j-dj+x[7])*x[1][:,:,j]
        b = b/(s1*(1+lambda_d*x[3]))/(s2*(1+lambda_d*x[4]))

        for k in range(0,s3):
            c = c+(k-dk+x[8])*x[2][:,:,k]
        c = c/(s1*(1+lambda_d*x[3]))/(s2*(1+lambda_d*x[4]))/(s3*(1+lambda_d*x[5]))

        pred = (a+b+c)*V

        return pred

`

Hello @TemiLee, it is because of the nature of the angles which can be positive or negative. (di,dj,dk) are just some fixed parameter to switch the range of index "i in [0,s1]" into "i in [-s1//2,s1//2]"


Textarea for image description should grow to accommodate input

The textarea component previously did this, but this behaviour was replaced when the Markdown editor was introduced. Perhaps add an option to provide the previous behaviour for ‘normal’ textareas.

Eventually I’d like to use field-sizing. Until then, let’s just increase the number of rows shown for image descriptions.
Fixed in 1fb53ec550d29c492b70782e01fec1e9d054525c


Problems with location and address object

We have encounter an issue around how addresses and locations hang together right now. This causes issues in production and should be fixed asap.
Reproduction:

When editing a circle address, the existing linked location instance is not updated, but a new location object is created. The old one is no obsolete.

We seem to be doing a lookup on geocode query string in order to retrieve existing locations. This seems buggy and unintuitive as any tipo in an address will lead to a new location instance.

Partial entries seem to create locations

Seems like in some fields any keystroke creates a new location with a new geocode_query.

We have a series of rollbar issues reported in production around geocode lookup.

@phil-monroe There is some weird stuff going on with geocode queries around locations for addresses. Can you take a look and see if we can resolve this? It will lead to crappy data in PROD right away with new users coming in...


ARM builds for Windows (like x elite chips)

Check out .github/workflows/.
You should put the building for ARM in the build-windows.yml.

GitHub actions doesn't provide ARM runners for free.


Lists vs Arrays

While some properties are faster using NumPy arrays, others that return very small arrays can be faster if they use lists. Many other properties have very similar performance. Some examples follow.
Faster with arrays (np.fromstring/np.frombuffer):
ActiveCircuit.AllBusDistances
ActiveCircuit.AllBusVmag
ActiveCircuit.AllBusVmagPu
ActiveCircuit.AllBusVolts
ActiveCircuit.AllElementLosses
ActiveCircuit.AllNodeDistances

Faster with lists (ffi.unpack):
ActiveCircuit.ActiveBus.puVLL
ActiveCircuit.ActiveBus.puVmagAngle
ActiveCircuit.ActiveBus.puVoltages
ActiveCircuit.Lines.Cmatrix
ActiveCircuit.Lines.Rmatrix
ActiveCircuit.Lines.Xmatrix
ActiveCircuit.Lines.Yprim
ActiveCircuit.Loads.ZIPV

Returning lists in some cases would probably be undesirable since the user would probably convert the list to array anyway, like ActiveCircuit.Lines.Rmatrix. In other cases, like ActiveCircuit.Loads.ZIPV, using lists could be better.
The task is to evaluate properties that would be better when used with lists while not affecting the performance negatively.

Closing for now; I don't think a lot of properties would be better with lists.


Support ColorTypes 0.12

cc @tlnagy, required for https://github.com/JuliaPlots/PlotUtils.jl/pull/171 or https://github.com/JuliaPlots/UnicodePlots.jl/pull/388.
CI run needs to be checked before release.

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

Project coverage is 90.54%. Comparing base (1ae2d4a) to head (2baab88).

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #174      +/-   ##
==========================================
- Coverage   92.36%   90.54%   -1.83%
==========================================
  Files          14       14
  Lines        1153     1153
==========================================
- Hits         1065     1044      -21
- Misses         88      109      +21

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

Do we need to drop 1.6 support necessarily? Also, might be good to move the github workers to use the new lts label like https://github.com/JuliaGraphics/Colors.jl/pull/560

Is it possible to tag a new release? I am trying to get all the Images ecosystem deps updated to newer versions, and I think this one is holding back ColorTypes.jl and ColorVectorSpace.jl:
(@v1.11) pkg> st --outdated -m
Status `~/.julia/environments/v1.11/Manifest.toml`
⌅ [3da002f7] ColorTypes v0.11.5 (<v0.12.0): ColorVectorSpace, TiffImages
⌃ [c3611d14] ColorVectorSpace v0.10.0 (<v0.11.0)

Thanks for the reminder, I tagged a release. It should be out soon.


Error: Cannot find module '/usr/local/lib/node_modules/alfred-otter/dist/index.js'

Hi,
I just installed this great looking workflow using the npm command. I put in my email and password like instructed and using the debugger in Alfred I was able to see that it spits out an error:
Error: Cannot find module '/usr/local/lib/node_modules/alfred-otter/dist/index.js'
    at internal/main/run_main_module.js:17:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

When I type otter it fails immediately and shows my default search engines for Alfred

Pushed out an update. run the same npm command to get the latest version!


Implemented per service mapping

Fixes #24
This implements per service mapping of service name, port, protocol and scheme.
The ServiceNameParser has been renamed to ServiceNameMapper, because that's now what it essentially does, maps a Lagom service name to an Akka discover lookup, plus scheme. It first attempts to do the mapping via direct configuration. If there's no mapping there, it then attempts to do the mapping parsing it using the regex, and if that yields no mapping, then it just uses the service name as is with the configured default port, protocol and mapped scheme.

service-name is needed when the services you're looking up are in different namespaces, and that's actually the biggest reason why I did this PR, because right now the experience of services deployed to different namespaces is terrible.
Yes, service-name-suffix can be removed with Akka 2.5.20, but that only solves the problem when talking to services in the same namespace as you, if in different namespaces, you'll need to qualify the name with the namespace it's in.
This can also be done by changing the name in the Lagom descriptor to be fully qualified, but the client doesn't always have control over that, and sometimes in different environments the namespace can be different, like you might have team-1-prod as team 1s prod namespace, and team-1-test as their test namespace, so we need a way of mapping that in configuration.

@jroper, maybe the whole feature is in the wrong place.
If we consider how this would look like if we didn't have ServiceLocator and were using ServiceDiscovery directly, both the schema resolution as the namespace is not a ServiceLocator issue, but a Lagom Client issue.
If we take the example of gRPC integration, the schema is not something to be picked from some configuration. Instead, we configure the client to use http or https by calling withTls(true|false).
The namespace is not an issue neither, because the user can simply do the lookup the way they want. Either they use a fully-qualified name or an unqualified one on the same namespace. They can read that value from a configuration and we don't need to provide any utility for that.
For Cassandra and Kafka we don't need the schema, the respective client takes cares of that. The namespace is easily solved by setting the properties: CASSANDRA_SERVICE_NAME and KAFKA_SERVICE_NAME.
If I'm using something else, for instance, Elastic Search, I can pretty much do the look and configure the client with the schema that I want.
The problem is that ServiceLocator API returns a URI, so it is taking to itself the responsibility of deciding the schema for the client.
If we want to move to ServiceDiscovery in a future release, those properties will need to become a Lagom Client property instead. I guess that the right path to take now is to introduce this, see how it can be simplified using Akka 2.5.20 and add the properties on a path that is not ServiceLocator, but Lagom Client, e.g: lagom.client.service-name-mappings instead of lagom.akka.discovery.service-name-mappings.
That would be a quite strange thing to do, because for the moment this ServiceLocator impl will be reading those properties, but next release (v1.6.0), it will be the client.


Box.Context and Box.TestServiceProvider have incorrect constructor properties set to Object

Hi T3!
I'm running into an issue in my project that is caused by subtle problem with the way that Box.Context and Box.TestServiceProvider are defined.  The methods on those objects are set by completely replacing  the prototype properties with a new object, which causes the constructor property to become Object, instead of the correct Box constructor functions.
The current code defines the methods on these object like this:
	function Context(application, element) {
		this.application = application;
		this.element = element;
	}

	Context.prototype = {
		broadcast: function(name, data) {...},
		getService: function(serviceName) {...},
		...
	}

Because the prototype is replaced by {}, the constructor becomes object.
The fix is simple:
	function Context(application, element) {
		this.application = application;
		this.element = element;
	}

	Context.prototype.broadcast: function(name, data) {...};
	Context.prototype.getService: function(serviceName) {...};
	...

I'm happy to create a PR, but just wanted to run it by you guys first for feedback.
Thanks!
Adam

Hi Adam,
I think the changes you proposed are perfectly fine and a PR would be most helpful!

You can also restore the constructor, for a smaller change:

    function Context(application, element) {
        this.application = application;
        this.element = element;
    }

    Context.prototype = {
        constructor: Context,
        broadcast: function(name, data) {...},
        getService: function(serviceName) {...},
        ...
    }

Hi guys, I made a pull request here:
https://github.com/box/t3js/pull/173
Thanks!


All of my panels and tabs have disappeared

Not sure how to provide any further information to help. Everything is just gone despite the rest of the app working. It loads fine and I add stuff to it and everything, but all my previous settings are gone.

Not sure how to provide any further information to help. Everything is just gone despite the rest of the app working. It loads fine and I add stuff to it and everything, but all my previous settings are gone.

There can be 2 explanations for this:

Bug in miniboard
Bug in your setup

As no one else reported this yet, and I'm using 3 instances of miniboard myself, let's start with the most likely mistake:

If you are using Docker and change data inside the container, it will disappear after container is restarted. To prevent this, mount /data/miniboard somewhere permanent.

If that's not the case, I need more info:

Are you using Docker or other setup method?
Was config.yaml also affected? Did the theme settings disappeared too?
Did board.yaml file disappeared, or was it empty, or was there some of your config, but not all?
What docker logs miniboard says?

No reports on this issue in 2 months. Closing.


.ksn parameter is converted into header only when httpxe is detected.

LGTM, assuming the build passes


Rename constants to uppercase

noticed PlainMessage.Empty and NamespaceType need to search to find if an other are wrong

pull request #120 created


Cosmetic Changes

Force-pushed to remove the ten irrelevant commits. I will test these in-game probably tomorrow; it's supposed to snow a lot, so I'm sure there will be plenty of free time to be had. :grin:
Your master branch should never merge changes from upstream, or it will gain irrelevant commits that clutter pull request branches. A fork's default branch (usually master) should ideally only ever be behind its upstream. This shouldn't happen: "This branch is 10 commits ahead of Warehousing:master." But that's what your master branch says right now.
I know it isn't really your fault—you're using a GUI tool, and that tool probably did this when you asked it to synchronize your branch—but you really should fix that master branch so future PRs don't have this problem. It's relatively easy to do via Git commands, but I couldn't easily find a way to do it in IntelliJ.
cd /path/to/warehousing/fork
git checkout master
git fetch upstream
git reset --hard upstream/master
git push -f origin master:master

Replace main-repo-remote with the name of this repo. If you don't know it, git remote will show you the remotes you have (probably origin for your fork, which is the default name; and one for this repo).
None of those commands can change this branch. Specifying master:master in the push command ensures that it will only push from local master to remote master, and nothing else.

OK, while I was fixing #68 so it could be reopened, I also fixed your master branch. :smile_cat:
Use git checkout master && git fetch origin && git reset --hard origin/master to point your local master so it matches upstream.

This is a pretty subtle change, now that I had a chance to test it out.
I guess the goal was to match which side of the pole wires go on when stringing them along power lines? It works in most cases, though there are some rotations of the power poles that swap the colors.
Should probably do something about the "floating" wires when connected to basic storehouse/warehouse buildings, since their sprites don't have the connection points, but not necessarily in this PR.

Yeah that was the goal and the wires were offset from the antennas ever so slightly and I tried to make the shadow's a bit more accurate as well.
As far as the floating wires go I don't think it would be too difficult to add just the antenna to the basic buildings if new models aren't planned to be made.  I know you had assigned updating them to whoever had the original models and it would be super easy to do that while updating those.  If the models are going to change at all it might be better to wait until those changes have been completed.

I'm told Nova Kast is "excited" about making overhauled models, and we might even get an animation for when robots stop at a building. Factorio recently added a way to specify where robots should stop relative to a logistic container (the LogisticContainerPrototype::landing_location_offset added in 0.17.5), so we should be able to make some fancy stuff eventually.
Rather than adding the antenna, I was thinking of having the basic buildings use a circuit connector box, like regular chests do. Ran out of time when I started tracing through the base entities to see how they invoke one, but it should be possible. Would probably look better than adding the antennas, too.

It would be sweet if we could give them the same or similar animation as the vanilla chests where the portal opens and closes when the robots interact with them.
If he does that or manipulates the models and if you do plan to add in the small/tiny versions it would be awesome if he could generate the sprites in the different sizes needed.
I also totally agree it would look better to have them use the default circuit connector box.  It would just be a matter of manipulating where the box itself was generated on the sprite.  I've never messed with that so I have no idea how to do that but I'd be willing to try and figure it out.  Would you happen to know off the top of your head what it's called or if it's even possible to manipulate?

I figured it out, once I tweak it and get it to look right I'll open a new PR with my cosmetic-changes branch.  I know the models may change but doing it will at least give us a base to work from when the models do change.
Also you may even want to pull the changes in before the new version is released with the new models.

Got it to look pretty decent, still some work to do and it add's a lot of lines of code so I'm going to try to reduce that with a function if I can.


[Urgent Feature Request] Return vector id from Pinecone

While using
err = store.AddDocuments(context.Background(), []schema.Document{
{
PageContent: userData,
Metadata: map[string]any{
        },
    },
})

Please return pinecone vector id
Something like
id, err := store.AddDocuments(context.Background(), []schema.Document{
{
PageContent: userData,
Metadata: map[string]any{
        },
    },
})

if err != nil {
	log.Fatal(err)
}

This is very important to do update or delete vector from pinecone for which we can use other library.
Help needed here urgently, stuck in a project.

Sorry to hear that you're in a bit of a bind. Please feel free to open a PR suggesting the edit you'd like, in the mean time you can fork the code and use go.work files to replace your implementation.


Issue #2 Custom TechTree tied to Module Manager unnecessarily.

…ver is being used at the moment, if the TechTree to be backed up.

I could not reproduce the problem. This mod already trusts whatever tech tree is loaded into HighLogic at loadup and saves that to "defaultTechTreeUrl". The "backupTechTreeUrl" you fixed is only used if the default tree is already set as my mod's auto-created tech tree (which should never happen at loadup so is probably unnecessary anyway).
So I'm not sure why this mod isn't working as intended with your MM fork.


Chrisda to Main

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

File
Status
Preview URL
Details

exchange/docs-conceptual/connect-to-scc-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Connect-ExchangeOnline.md
:white_check_mark:Succeeded
View (exchange-ps)

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


Dockerfile available?

I'm currently trying to find a Dockerfile for docker.bintray.io/jfrog/artifactory-pro.
Is there one available somewhere?

Hi @katzefudder - you can find the OSS Docker file in the Artifactory OSS sources: https://jfrog.bintray.com/artifactory/jfrog-artifactory-oss-5.5.1-sources.tar.gz
There is a distribution/docker module. It has the sources for the Docker image. It's almost identical to the Pro version.
If you want more specific details, look at https://bintray.com/jfrog/reg2/jfrog%3Aartifactory-pro. It has a graphic outlining of the image (scroll to the Docker Details section).
We have future plans to add the Dockerfiles for Artifactory OSS/PRO and the needed resources to this repo in the future.

You're doing many things with the entrypoint-artifactory.sh, which unfortunately differs between OSS and  PRO. I'm pretty interested in having all parts in this repo, as it would make setup via Docker a lot more obvious and would also make documentation a lot more comprehensive than it is today.

Go ahead and pull the docker.bintray.io/jfrog/artifactory-pro:5.5.1 image, and bash into it
docker run --rm -it --entrypoint=/bin/bash docker.bintray.io/jfrog/artifactory-pro:5.5.1

Then, you can see /entrypoint-artifactory.sh.

Well, sure, I know that... somehow, I had the chance to look at it before I was reaching out to you ;)
We're actually trying to run Artifactory in production, and are currently evaluating different approaches about how we deploy the software in AWS. Having all the sources (all the glue that puts Artifactory in place) at hand would be a nice thing to have, even when thinking about maintainance and future releases.


Use converge_by blocks in provider actions

This allows us to get rid of the updated by last action nonsense :smiley_cat:
Alternatively, we can switch to execute blocks and use_inline_resources. That has the added benefit of addressing #9, and we can remove the shell out code, has converge_by built in, and gives us more clear implementation of things like the user to run as, or any environment variables to pass in.

The plugin provider uses use_inline_resources with executes for some time now. Looks like since this issue was opened, so I probably didn't follow up on myself.


bagel update

2 more roundstart borgs so 4 total
apc inside of ai core chunnel room
skub

2 more roundstart borgs so 4 total

why


Problem listing instances

I am getting an error when running
$ az vmss list-instance-connection-info ...
No load balancer exists to retrieve public IP address
$ az -v
azure-cli                          2.6.0

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

ID: 602e2a20-deb3-418e-7148-62a8890791ed
Version Independent ID: e3ec8eba-98aa-0523-3b07-8a8d3584be0c
Content: Tutorial - Create and manage an Azure virtual machine scale set - Azure Virtual Machine Scale Sets
Content Source: articles/virtual-machine-scale-sets/tutorial-create-and-manage-cli.md
Service: virtual-machine-scale-sets
Sub-service: management
GitHub Login: @ju-shim
Microsoft Alias: jushiman

@ingokofler
Thanks for your Question! We are currently investigating and will get back on this.

@ingokofler I just tried the tutorial on cloud shell as recommended in the document, the  az version is 2.5.1 and I am not facing issue while listing the connection info az vmss list-instance-connection-info.
Can you please try in cloud shell or with the version mentioned and see if the issue is resolved.

Nope, same behaviour here. Note that the VMSS is attached to a private LB only in our deployment.
admin@Azure:~$ az version
{
  "azure-cli": "2.5.1",
  "azure-cli-command-modules-nspkg": "2.0.3",
  "azure-cli-core": "2.5.1",
  "azure-cli-nspkg": "3.0.4",
  "azure-cli-telemetry": "1.0.4",
  "extensions": {}
}
admin@Azure:~$ az vmss list-instance-connection-info -g xxx  -n yyy
No load balancer exists to retrieve public IP address

@ingokofler Thanks of sharing the details.
Do you have public IP on the instance level, looks like that is the reason you are seeing this error.
Here is similar issue which has few more details.

No, i have just checked. There are no public IPs on instance level. Also worth mentioning, the LB and the VMSS are working fine. I can also see the instance private IPs on the Azure Portal but actually not via the Azure CLI. I also don't think that this is an permission problem as I have "Owner" permission on the full subscription.

@ingokofler , az vmss list-instance-public-ips command is to display the Public IP associated to the Instance level VMSS not the private IPs.

@ingokofler
Hope the provided information is helpful.
We will now close this issue. If there are further questions regarding this, please tag me in a comment. I will reopen it and we will continue the discussion.

@msrini-MSFT @VikasPullagura-MSFT
Why was this issue closed? In my case az vmss list-instance-connection-info is not working. I am not using public IPs, I am solely interested in getting out the private IPs of the instances.

@ingokofler , This command is used to Get the IP address and port number used to connect to individual VM instances within a set.
This command will not return Private IP address. If you have a Load balancer infront of your VMSS and have a NAT rule, you will be able to see the IP with port mapping in the output. If not, you will not see any results.
I have a VMSS with LB and here is the output.
karthik@Azure:~$ az vmss list-instance-connection-info --name VMSS1 --resource-group VMSS
{
"instance 1": "52.224.XX.47:50001",
"instance 3": "52.224.XX.47:50003"
}

@msrini-MSFT ok, so if there are no NAT rules the expectation is that there's no output. Understood.
But alternatively, what is the az cli command to get a list of the instances with their id and their internal IP addresses, so that I can login with ssh into them? I see those IP addresses on an instance level on the portal, but how to get them on the CLI?

@ingokofler , Execute the below command:
az vmss nic list --name Name--resource-group Name
"name": "VMSS-vnet-nic01-defaultIpConfiguration",
"primary": true,
"privateIpAddress": "<IP_ADDRESS>",
"privateIpAddressVersion": "IPv4",
"privateIpAllocationMethod": "Dynamic",
"privateLinkConnectionProperties": null,
"provisioningState": "Succeeded",
"publicIpAddress": null,
"resourceGroup": "VMSS",
You can get the private IP of each NIC.

understood. but with this command I don't get out the instanceIds easily, right? needs to be parsed out of this long resourceId string.

@ingokofler , Unfortunately there are no direct commands to get the private IP alone. You need to parse it from the above mentioned command.


Patch 1

Pre-submission checklist:
Please check each of these after submitting your pull request:

[ x] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[ ] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[x ] Have you picked the single best (existing) category for your project?
[ x] Does it follow the other guidelines from the new entries section?
[ x] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[ x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[ x] Does your project/product name match the text on the logo?
[ x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ x] ~15 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

Build failed because of:
No cached entry, and Open Application Model has issues with logo: oam.svg, Error in parsing SVG: Attribute without value
Line: 45
Column: 90
Char: >

Deploy preview for landscape failed.
Built with commit 6b88f9bb726bd06ada725d326fb365affaab3d02
https://app.netlify.com/sites/landscape/deploys/5f0f83d3439c050007e7e8ce

Build failed because of:
No cached entry, and Open Application Model has issues with logo: oam.svg, ENOENT: no such file or directory, open '/opt/build/repo/hosted_logos/oam.svg'

Build failed because of:
No cached entry, and Open Application Model has issues with logo: oam.svg, ENOENT: no such file or directory, open '/opt/build/repo/hosted_logos/oam.svg'

LGTM

I believe OAM would fit much better one category to the left in Application Definition rather than CI/CD. If you agree, could you please update the PR.

Agreed. Thank you @dankohn !


added disclaimer modal

@jgladwig can you put this into the release?

@jgladwig I'm going to merge and create the release now.


Update desktop-tooltips.md

@amandacofsky : Thanks for your contribution! The author, @davidiseminger, has been notified to review your proposed change.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

powerbi-docs/desktop-tooltips.md
:white_check_mark:Succeeded

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

@amandacofsky : Thanks for your contribution! The author, @davidiseminger, has been notified to review your proposed change.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

powerbi-docs/desktop-tooltips.md
:white_check_mark:Succeeded

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

Hi,  @amandacofsky -- looks good. @davidiseminger, I'm going to accept this change for you.


Enable Noobaa KMS configuration only when the cluster-wide encryption is enabled

Noobaa's root secret key, used for MCG encryption, should only  be
stored in to KMS server only if cluster wide encryption with StorageClass
encryption enabled.
Corrected the test cases accordingly.
Signed-off-by: Arun Kumar Mohan<EMAIL_ADDRESS>

@jarrpa , please take a look..

/ok-to-test

/cherry-pick release-4.7


Record.mapEntries returns undefined

R = Immutable.Record({'foo': 'bar'})
r = new R({'foo': 'baz'})
r.mapEntries(() => [42, 42])

steps to reproduce:

open https://facebook.github.io/immutable-js/docs/#/
f12
paste and run code
cry.

A Record is not a collection - where in v3 these functions have undefined behavior, they've been removed in v4.


Framework Laptop 13 120Hz screen not correctly handled

Hi,
I have the 120Hz screen on my FW 13 and the application shows 3 possibilities for the refresh rate: "Auto", "60Hz" and "165Hz". I believe that this is what it should show for a FW 16. Also, the "165Hz" button does nothing on my laptop.
Proposed solution
Add a laptop model check when the app builds the UI and dynamically set button text and click event functions to the compatible options.
Thank you for your great work and happy new year! :)

Ho that's intresting, i'll push some changes in 5 mins can you try again after?

the changes are live, the integration is basic atm but tell me if it work and send me your log in the logs folder 👍

did a other commit, try it out :)

It works and sets the refresh rate correctly to 120Hz!
However, the button text string is still missing:

And I noticed that the iGPU temperature is not logged and stays at 0.0°C
2024-12-31_1.log
Thanks! :)

did a other update, try it and send me your logs and your file sensors.json too please 🙏

2024-12-31_2.log
sensors.json
Here you go! :)
(120Hz string is fixed)

Thanks you, I look at the sensor id problem and I will tell you when i push a fix

Updated, can you try and again send me the files? Thanks for your help !

Updated, tell me if it works :)


Add layout support for Stacks, Scroll Groups, & Padding

Padding was added in XD v26, Stacks & Scroll Groups in v30.
Padding would be an obvious add for the pinned layout export or even just as a wrapped Padding widget. Stacks should map well to Column / Row in Flutter. Scroll groups should map to a ScrollView.
Unfortunately, all of these features currently lack API support in XD.

Note: ScrollableGroups is available in the XD API as of v30.

Planning to implement at least ScrollableGroup, and possibly Stacks or Padding (if API support becomes available) for v2.

Mostly complete in v2.0.0 (stacks, padding, background elements, and h/v scroll groups), leaving open though because I would still like to add support for panning (h+v) scroll groups.

Actually, I'm going to close this in favor of #106 which is more specific.