Allow publishing using new Confluence editor

Atlassian have introduced a new Confluence editor:

https://confluence.atlassian.com/confcloud/confluence-editing-improvements-945107733.html

Please allow the publishing of Confluence pages using this new editor.
PS. I have done a little bit of research, but I cannot find out how to enable the new editor through the Confluence Cloud REST API. The content storage format appears to be the same.

I have not seen any issues with publishing pages via confluence-publisher and the new editor. Are you seeing errors?

The point is: when I generate any page using the REST API, using the AsciiDoc Confluence Publisher library, the page becomes a Legacy Editor page.
This can be checked as follows:
Steps to reproduce:

Publish a page using Confluence Publisher.
Visit the page in the Confluence user interface.
Edit the page

Expected result:

The new Confluence editor shows in step 3.

Actual result:

NOK: The legacy Confluence editor shows, in step 3.

@znerd I see, thanks for clarifying. I also see this behavior, but in our case we're never making any edits via Confluence for pages owned by confluence-publisher. (The new editor being crazy slow in Firefox doesn't help either)

There are several reasons why the new Confluence editor are the way forward:

There is a visual difference in appearance between pages based on the legacy vs. the new editor (when switching to the new editor elsewhere in the space, this becomes problematic), and
the new Editor offers certain features that the Legacy editor does not have, and
the Legacy editor may be left behind when new features are introduced.


MA - Investigation possible send errors for results on 1/23

On 1/24, MA reported that they received only 5 test messages for 1/23 - which is historically lower from past weeks. We need to investigate why this is and share with MA.
First pass review in Actions and Ops Dashboard does not show any failures from RS to MA.

No RS issues identified. MA was notified.


[openwrt/luci] Changing disassoc_low_ack wireless settings breaks 5g wireless [X5000R]

Steps to reproduce:

Network -> Wireless -> Edit a 5g SSID
Interface Configuration -> Advanced
Uncheck 'Disassociate On Low Acknowledgement'
Save & apply

Actual behavior:
Changes show the following:
# /etc/config/wireless
uci del wireless.radio1.band
uci del wireless.radio1.channel
uci add wireless.wifinet4.disassoc_low_ack='0'

Applying the changes disables wireless. Trying to edit the network again gives an error
TypeError
Cannot read properties of undefined (reading 'value')

This may be related to #5468. This is the same as #5771, which was closed without verification or a fix.
Expected behavior:
Example: Replace the following lines and remove this
wireless.radio1.band and wireless.radio1.channel should not be deleted.
Additional Information:
OpenWrt version information from system /etc/openwrt_release

This is still happening on 21.02.03.

root@den:/etc/config# cat /etc/openwrt_release
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='21.02.3'
DISTRIB_REVISION='r16554-1d4dea6d4f'
DISTRIB_TARGET='ramips/mt7621'
DISTRIB_ARCH='mipsel_24kc'
DISTRIB_DESCRIPTION='OpenWrt 21.02.3 r16554-1d4dea6d4f'
DISTRIB_TAINTS=''

root@den:/etc/config# opkg list-installed | grep luci
liblucihttp-lua - 2021-06-11-3dc89af4-1
liblucihttp0 - 2021-06-11-3dc89af4-1
luci - git-20.074.84698-ead5e81
luci-app-firewall - git-22.089.67741-3856d50
luci-app-opkg - git-21.312.69848-4745991
luci-base - git-22.083.69138-0a0ce2a
luci-lib-base - git-20.232.39649-1f6dc29
luci-lib-ip - git-20.250.76529-62505bd
luci-lib-jsonc - git-22.097.61937-bc85ba5
luci-lib-nixio - git-20.234.06894-c4a4e43
luci-mod-admin-full - git-19.253.48496-3f93650
luci-mod-network - git-22.046.85061-dd54dce
luci-mod-status - git-22.046.85784-0ac2542
luci-mod-system - git-22.019.40321-7a37d02
luci-proto-ipv6 - git-21.148.49484-14511e5
luci-proto-ppp - git-21.163.64918-6c6559a
luci-ssl - git-20.244.36115-e10f954
luci-theme-bootstrap - git-22.084.39047-f1d687e
rpcd-mod-luci - 20210614

Duplicate of #5771

Why did you close this and #5771 ? The problem still exists. #5771 was closed even though the problem is valid and exists in 21.02.03.


MockFirebase and authWithPassword() does not trigger an error?

(copied from another post on behalf of @liveakshay)
Ok, I have a similar problem with testing $authWithPassword.  The catch block of my $authWithPassword never gets invoked!  Despite using failNext and flush.  Please help.
Here is my controller and test spec.
login.js
function LoginController(FIREBASE_URL, $scope, $location, $log, $firebaseAuth, $firebaseObject, $firebaseArray) {

	function login() {
		console.log('authenticateUser', vm.email, vm.password);
		return vm.auth.$authWithPassword({
			email: vm.email,
			password: vm.password
		}).then(function(authData) {
			vm.user = global.userObj = $firebaseObject(global.ref.child(vm.getLoggedInUserID()));
			_setupUser(authData);
			var msg = "Logged in successfully, as user ";
			if(vm.user.isAdmin)
				msg = msg + "and administrator ";
			msg = msg + vm.email + "!";
			vm.success(msg);
			return authData;
		}).catch(function(error) {
			vm.err("* Authentication failed! ", error);
			return error;
		});
	}
}

Test Spec
'use strict';

describe('Controller: LoginCtrl', function () {

	// load the controller's module
	beforeEach(module('joggerApp'));

	var LoginCtrl, $scope, ref, $log;

	// Initialize the controller and a mock scope
	beforeEach(
		inject(function ($controller, $rootScope) {
			MockFirebase.override();
			$scope = $rootScope.$new();
			LoginCtrl = $controller('LoginCtrl', {
				$scope: $scope
			});
			ref = $scope.global.ref;
			// ref.autoFlush(true);
		})
	);

	it('should fail auth with wrong login email/password', function() {
		$scope.vm.email =<EMAIL_ADDRESS>		$scope.vm.password = "NO_WAY_THIS_IS_EVER_A_PASSWORD";
		ref.failNext('authWithPassword', new Error('does it matter?'));
		LoginCtrl.login().then(function(){
			expect($scope.global.errorMessage).toMatch('/* Authentication failed!/');
			console.log('YAY!!!');
			expect($scope.global.successMessage).toBeNull();
			console.log('YAY!!!');
			expect($scope.vm.user).toBeNull();
			console.log('YAY!!!');
		});
		ref.flush();
	});
});

Please determine if the error still occurs when you remove MockFirebase from the picture? If not, then this would be a bug with the MockFirebase lib. Reduce this to the smallest amount of code that still reproduces the error, in order to isolate the error to the correct lib, and create a new issue so these aren't confused.

I removed MockFirebase entirely.  Still doesn't trigger my catch block (and yes, I don't have a user with that username/password in my firebase DB).
I guess at this point I am just looking for help writing a Jasmine test spec that tests a controller that uses angularfire's $authWithPassword.  There are no examples out there!?

Generally speaking, your test units don't need to test the third party lib's functionality. If you want a test unit that tests $authWithPassword(), it's here. But if you want to test your own code, the answer would be to a) use an e2e test and run a real auth event or b) mock the $authWithPassword() method. You're not testing $authWithPassword() for bugs, so remove it from the picture.

I am trying to test that the controller correctly handles a rejected promise (given incorrect auth credentials), and sets the appropriate error message in the model, for the view.  I need the $authWithPassword function to fail, and trigger a rejected promise block in my controller.
Do I have to write an asynchronous jasmine test for this case (without using MockFirebase)?  Perhaps I can use jasmine spy or spyObject, like you have in the angularFire unit test specs?  Thank you for your continued patience and help.

On Apr 18, 2016, at 10:13 PM, katowulf<EMAIL_ADDRESS>wrote:
Generally speaking, your test units don't need to test the third party lib's functionality. If you want a test unit that tests $authWithPassword(), it's here. But if you want to test your own code, the answer would be to a) use an e2e test and run a real auth event or b) mock the $authWithPassword() method. You're not testing $authWithPassword() for bugs, so remove it from the picture.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

Doing a bit of housecleaning. MockFirebase is no longer used for tests, and the answer to the question posited here is to use e2e tests for auth and to mock Firebase services for unit tests using spies. Ping back if more help is needed.


gmail login ISSUES

NOT UPDATED

and this is the ui page

wht is jd

(❁´◡`❁)

jd is one of the powerfull program


Board Review: Azure Device Update Public Preview launch

###Context
This is a follow up review for Azure Device Update Rest API’s and Swagger with Peter Marcu and Johan Stenberg's feedback
###The Basics

Service team responsible for the SDK library: COSINE > EDS team working on Azure Device Update for IOT Devices
Link to documentation describing the service:
ADU Architecture.docx
ADU Private Preview GitHub
Contact (if service team, provide PM and Dev Lead):
PM: Val Olson
Dev: David Pokluda, Oscar Lee, Jimmi Tirifon

About this client library and Artifacts

Name of the service library: Azure Device Update
Languages for this review:
<will add new PR's by 9/24>
Swagger: https://github.com/Azure/azure-rest-api-specs-pr/pull/1978

Champion Scenarios
Azure Device Updates (ADU) has few core capabilities and touchpoints for updating IOT devices Over the Air (OTA)

Publish new update
retrieve the newly imported update
wait for update to be installable to our device
create deployment to deploy our new update to our device
check deployment status until it's completed
retrieve device properties to check installed update present
retrieve all updates installed on the device
delete the update
retrieve the deleted update and check that it no longer exists

The above leverages all core API methods and champions main scenarios of Update publishing and Device update deployment.

PR's

.NET: https://apiview.dev/Assemblies/Review/e69a527c94d2444f816d5341759582d8
Python: https://apiview.dev/Assemblies/Review/b4767c5c88b24f788ca10f79aa8f5b1d

scheduled for 9/30 in case we don't get to SDKs in REST API Review

I am not sure how to share the sample (champion scenario). Here is the sample project from .NET project:
\DPOKLUDA\Public\MU\Tasks\Current\AzureSdk\Data\Net\Azure.Iot.DeviceUpdate\samples

[MS Internal Only]Video


Out of likes for today

Hey, I just set up the whole thing and wanted to throw a few likes.
But no matter how I do it (hastags, database) it starts running and stops immidiately with the given error of "out of likes for today"
Can anyone help?
Thanks!

Have you updated the Instabot?


Wrong image tag for version 0.1.1

The new version 0.0.1 of the job-executor-service is not tagged as keptnsandbox/job-executor-service:0.1.1 as described in the README and used in the Kubernetes and Helm files but is tagged as keptnsandbox/job-executor-service:0-1-1 instead. This seems to be the case because the release branch is named release-0-1-1 instead of release-0.1.1, and the branch name is used in the Github Action, which builds the Docker image.
It would be great to change the tag of this release so that the given installation scripts work correctly.

I pushed the images with the correct tag 0.1.1


Calendar and task assignment

A calendar widget on bottom right of the web page.
Admin or some special user can create task for some user(s). These tasks will show up in the calendar.
Integration of this with google calendar and several other features....
How does this feature sound ? Would it be good to have this feature ?
Anybody wants to discuss it ?

@timabbott @lfaraone What do you think ?

I don't think it makes sense to try moving Zulip into providing a task management/calendaring feature at this point; I think we'd have a hard time making something competitive with existing projects without a ton of work.  If you're interested in working on something in this direction, I think cleaning up bots/gcal-bot (which was written years ago to provide calendar reminders via Zulip messages) to be a proper, easy to use, integration and moving it into api/integrations/, would be valuable!  And I can definitely imagine making the integration 2-way, where you can send a chat message to the gcal bot to cause a meeting to be scheduled.
@chandan5 does that seem like a reasonable way to make progress towards your goals?

Yeah it would be good to provide task assignment by making gcal-bot two way. Can you tell me what a bot exactly is ? According to my understanding its a service which can be activated by admin and then functionality provided by that bot can be used. Can you point me to some resources for how bot works at Zulip.

In zulip, a "bot" is just a special user who can't login intended to be used for integrations like those in zulip.com/integrations.  There's some docs on the API at https://zulip.com/api/ and more in api/ in the Zulip git repository for the Zulip API, and we also support incoming webhook integrations via the the code under zerver/views/webhooks/.  So to write a two-way bot, you'd need to write some code in the Gcal bot to use the Zulip message receive API (see e.g. api/examples/print-messages).

In general I'd like for there to be better calendar integration; cleaning up the current gcal-bot code (per the integration writing guide so it doesn't depend on the user running the code on their local machine, and so the integration can go into api/integrations/, would be great.
I'd also like more general calendar integration so Zulip can integrate with free and open source calendars. I'd like to have a bot listen to an iCalendar feed (e.g. from http://calagator.org/ ) and announce new events, or changes of date/time/location, in a Zulip stream. A quick web search brings up https://pypi.python.org/pypi/icalendar/ in case that would make it easy to generalize the code in gcal-bot to also read iCalendar files.

bots/gcal-bot (which was written years ago to provide calendar reminders via Zulip messages)

Just barging in to say that a more practical implementation of this functionality (i.e. that would somehow work for all users in our org, without running 1 bot per user, and ideally without us having to deploy anything external to Zulip Cloud at all!) would be a really welcome feature.

i want to work on it


I've done something completly wrong! Delete this pull please!

See more information in Issue #196!

I'm so sorry about doing this Pull-Request. Currently I'm trying to send a correct Pull-Request, but I fail.
Can anybody recommend me a good site or a step-by-step instructions on the web?
I'm so sorry about this :(

No problem, thanks for helping! :)


Release script uploads binaries with OS capitalized

@dgageot @jeanlaurent FYI
I haven't been able to debug it yet but the uploaded binaries (and in the template) for this RC, the names look like docker-machine_Darwin-amd64 (note that the OS is capitalized).  This is violating our previous convention of all lowercase, so we probably should fix it.

This is to mimic the other projects like compose. So not a bug to me

This was requested in #494, implemented in #2915.
If you look at docker/docker and docker/compose binary names, they have the same.
I don't like the fact that we have a capital in the middle of nowhere like this, but hey, everyone else @ Docker is doing that, so...

Hm OK, I hadn't realized it was intentional.  Thanks!

I'll update the binary names to be the correct format


[History/MongoDB] Get data in CSV format

I'm submitting a ...

[ ] bug report
[X] feature request
[ ] support request

Do you want to request a feature or report a bug?
New feature.

What is the current behavior?
The history service API allows to get data only on json format.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
NA

What is the expected behavior?
The history service API should allow to get data on json or csv formats according to the HTTP Accept header (see https://datatracker.ietf.org/doc/html/rfc7231#section-5.3.2). For instance, if its value is text/csv the data should be returned in CSV format. It's worth to say that if the HTTP Accept header is absent, the current behavior should be kept, ie, returns in json format.

What is the motivation / use case for changing the behavior?
It can make easier to process the data in some systems.

Please tell us about your environment:
NA

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
NA

mosquitto_pub -h localhost -p 1883 -t admin:27b235/attrs  -m '{"pressao":939}' -u admin:27b235
mosquitto_pub -h localhost -p 1883 -t admin:27b235/attrs  -m '{"temperatura":31,"pressao":960}' -u admin:27b235
mosquitto_pub -h localhost -p 1883 -t admin:27b235/attrs  -m '{"temperatura":27}' -u admin:27b235
mosquitto_pub -h localhost -p 1883 -t admin:27b235/attrs  -m '{"temperatura":18,"pressao":957,"timestamp":"2021-11-24T00:20:00.000000Z"}' -u admin:27b235
mosquitto_pub -h localhost -p 1883 -t admin:27b235/attrs  -m '{"temperatura":13,"pressao":910,"timestamp":"2021-11-20T06:50:00.000000Z"}' -u admin:27b235
mosquitto_pub -h localhost -p 1883 -t admin:27b235/attrs  -m '{"temperatura":21,"pressao":921,"timestamp":"2021-11-21T06:50:00.000000Z"}' -u admin:27b235
mosquitto_pub -h localhost -p 1883 -t admin:27b235/attrs  -m '{"temperatura":9,"pressao":1008,"timestamp":"2021-11-22T06:50:00.000000Z"}' -u admin:27b235
mosquitto_pub -h localhost -p 1883 -t admin:27b235/attrs  -m '{"temperatura":4,"pressao":1019,"timestamp":"2021-11-22T06:50:00.000000Z"}' -u admin:27b235

curl -X GET "localhost:8000/history/device/27b235/history?attr=temperatura" -H "Authorization: Bearer ${JWT}" -H 'Content-Type: application/json' 2>/dev/null | jq
[
  {
    "attr": "temperatura",
    "value": 27,
    "device_id": "27b235",
    "ts": "2021-11-25T13:29:38.876000Z",
    "metadata": {}
  },
  {
    "attr": "temperatura",
    "value": 31,
    "device_id": "27b235",
    "ts": "2021-11-25T13:29:26.120000Z",
    "metadata": {}
  },
  {
    "attr": "temperatura",
    "value": 18,
    "device_id": "27b235",
    "ts": "2021-11-24T00:20:00Z",
    "metadata": {}
  },
  {
    "attr": "temperatura",
    "value": 9,
    "device_id": "27b235",
    "ts": "2021-11-22T06:50:00Z",
    "metadata": {}
  },
  {
    "attr": "temperatura",
    "value": 4,
    "device_id": "27b235",
    "ts": "2021-11-22T06:50:00Z",
    "metadata": {}
  },
  {
    "attr": "temperatura",
    "value": 21,
    "device_id": "27b235",
    "ts": "2021-11-21T06:50:00Z",
    "metadata": {}
  },
  {
    "attr": "temperatura",
    "value": 13,
    "device_id": "27b235",
    "ts": "2021-11-20T06:50:00Z",
    "metadata": {}
  }
]

curl -X GET "localhost:8000/history/device/27b235/history?attr=temperatura" -H "Authorization: Bearer ${JWT}" -H 'Content-Type: application/json' -H 'Accept: text/csv'
"attr","value","device_id","ts"
"temperatura",27,"27b235","2021-11-25T13:29:38.876000Z"
"temperatura",31,"27b235","2021-11-25T13:29:26.120000Z"
"temperatura",18,"27b235","2021-11-24T00:20:00Z"
"temperatura",9,"27b235","2021-11-22T06:50:00Z"
"temperatura",4,"27b235","2021-11-22T06:50:00Z"
"temperatura",21,"27b235","2021-11-21T06:50:00Z"
"temperatura",13,"27b235","2021-11-20T06:50:00Z"

curl -X GET "localhost:8000/history/device/27b235/history?attr=pressao" -H "Authorization: Bearer ${JWT}" -H 'Content-Type: application/json' 2>/dev/null | jq
[
  {
    "attr": "pressao",
    "value": 960,
    "device_id": "27b235",
    "ts": "2021-11-25T13:29:26.120000Z",
    "metadata": {}
  },
  {
    "attr": "pressao",
    "value": 939,
    "device_id": "27b235",
    "ts": "2021-11-25T13:29:08.146000Z",
    "metadata": {}
  },
  {
    "attr": "pressao",
    "value": 957,
    "device_id": "27b235",
    "ts": "2021-11-24T00:20:00Z",
    "metadata": {}
  },
  {
    "attr": "pressao",
    "value": 1008,
    "device_id": "27b235",
    "ts": "2021-11-22T06:50:00Z",
    "metadata": {}
  },
  {
    "attr": "pressao",
    "value": 1019,
    "device_id": "27b235",
    "ts": "2021-11-22T06:50:00Z",
    "metadata": {}
  },
  {
    "attr": "pressao",
    "value": 921,
    "device_id": "27b235",
    "ts": "2021-11-21T06:50:00Z",
    "metadata": {}
  },
  {
    "attr": "pressao",
    "value": 910,
    "device_id": "27b235",
    "ts": "2021-11-20T06:50:00Z",
    "metadata": {}
  }
]

curl -X GET "localhost:8000/history/device/27b235/history?attr=pressao" -H "Authorization: Bearer ${JWT}" -H 'Content-Type: application/json' -H 'Accept: text/csv'
"attr","value","device_id","ts"
"pressao",960,"27b235","2021-11-25T13:29:26.120000Z"
"pressao",939,"27b235","2021-11-25T13:29:08.146000Z"
"pressao",957,"27b235","2021-11-24T00:20:00Z"
"pressao",1008,"27b235","2021-11-22T06:50:00Z"
"pressao",1019,"27b235","2021-11-22T06:50:00Z"
"pressao",921,"27b235","2021-11-21T06:50:00Z"
"pressao",910,"27b235","2021-11-20T06:50:00Z"

curl -X GET "localhost:8000/history/device/27b235/history" -H "Authorization: Bearer ${JWT}" -H 'Content-Type: application/json' 2>/dev/null | jq
{
  "pressao": [
    {
      "attr": "pressao",
      "value": 960,
      "device_id": "27b235",
      "ts": "2021-11-25T13:29:26.120000Z",
      "metadata": {}
    },
    {
      "attr": "pressao",
      "value": 939,
      "device_id": "27b235",
      "ts": "2021-11-25T13:29:08.146000Z",
      "metadata": {}
    },
    {
      "attr": "pressao",
      "value": 957,
      "device_id": "27b235",
      "ts": "2021-11-24T00:20:00Z",
      "metadata": {}
    },
    {
      "attr": "pressao",
      "value": 1008,
      "device_id": "27b235",
      "ts": "2021-11-22T06:50:00Z",
      "metadata": {}
    },
    {
      "attr": "pressao",
      "value": 1019,
      "device_id": "27b235",
      "ts": "2021-11-22T06:50:00Z",
      "metadata": {}
    },
    {
      "attr": "pressao",
      "value": 921,
      "device_id": "27b235",
      "ts": "2021-11-21T06:50:00Z",
      "metadata": {}
    },
    {
      "attr": "pressao",
      "value": 910,
      "device_id": "27b235",
      "ts": "2021-11-20T06:50:00Z",
      "metadata": {}
    }
  ],
  "temperatura": [
    {
      "attr": "temperatura",
      "value": 27,
      "device_id": "27b235",
      "ts": "2021-11-25T13:29:38.876000Z",
      "metadata": {}
    },
    {
      "attr": "temperatura",
      "value": 31,
      "device_id": "27b235",
      "ts": "2021-11-25T13:29:26.120000Z",
      "metadata": {}
    },
    {
      "attr": "temperatura",
      "value": 18,
      "device_id": "27b235",
      "ts": "2021-11-24T00:20:00Z",
      "metadata": {}
    },
    {
      "attr": "temperatura",
      "value": 9,
      "device_id": "27b235",
      "ts": "2021-11-22T06:50:00Z",
      "metadata": {}
    },
    {
      "attr": "temperatura",
      "value": 4,
      "device_id": "27b235",
      "ts": "2021-11-22T06:50:00Z",
      "metadata": {}
    },
    {
      "attr": "temperatura",
      "value": 21,
      "device_id": "27b235",
      "ts": "2021-11-21T06:50:00Z",
      "metadata": {}
    },
    {
      "attr": "temperatura",
      "value": 13,
      "device_id": "27b235",
      "ts": "2021-11-20T06:50:00Z",
      "metadata": {}
    }
  ]
}

curl -X GET "localhost:8000/history/device/27b235/history" -H "Authorization: Bearer ${JWT}" -H 'Content-Type: application/json' -H 'Accept: text/csv'
"attr","value","device_id","ts"
"pressao",960,"27b235","2021-11-25T13:29:26.120000Z"
"pressao",939,"27b235","2021-11-25T13:29:08.146000Z"
"pressao",957,"27b235","2021-11-24T00:20:00Z"
"pressao",1008,"27b235","2021-11-22T06:50:00Z"
"pressao",1019,"27b235","2021-11-22T06:50:00Z"
"pressao",921,"27b235","2021-11-21T06:50:00Z"
"pressao",910,"27b235","2021-11-20T06:50:00Z"
"temperatura",27,"27b235","2021-11-25T13:29:38.876000Z"
"temperatura",31,"27b235","2021-11-25T13:29:26.120000Z"
"temperatura",18,"27b235","2021-11-24T00:20:00Z"
"temperatura",9,"27b235","2021-11-22T06:50:00Z"
"temperatura",4,"27b235","2021-11-22T06:50:00Z"
"temperatura",21,"27b235","2021-11-21T06:50:00Z"
"temperatura",13,"27b235","2021-11-20T06:50:00Z"


[SPARK-17637][Scheduler]Packed scheduling for Spark tasks across executors

What changes were proposed in this pull request?
Restructure the code and implement two new task assigner.
PackedAssigner: try to allocate tasks to the executors with least available cores, so that spark can release reserved executors when dynamic allocation is enabled.
BalancedAssigner: try to allocate tasks to the executors with more available cores in order to balance the workload across all executors.
By default, the original round robin assigner is used.
We test a pipeline, and new PackedAssigner  save around 45% regarding the reserved cpu and memory with dynamic allocation enabled.
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
Both unit test in TaskSchedulerImplSuite and manual tests in production pipeline.

Test build #65830 has started for PR 15218 at commit c3ebf9c.

Test build #65830 has finished for PR 15218 at commit c3ebf9c.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #65831 has started for PR 15218 at commit ffe9800.

Test build #65832 has started for PR 15218 at commit d5f76ae.

Test build #65832 has finished for PR 15218 at commit d5f76ae.

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

Merged build finished. Test FAILed.

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

Test build #65831 has finished for PR 15218 at commit ffe9800.

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

Merged build finished. Test FAILed.

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

Failed in DirectKafkaStreamSuite. It should has nothing to do with the patch.

retest please

See https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65832/testReport/org.apache.spark.streaming.kafka010/DirectKafkaStreamSuite/pattern_based_subscription/history/

@gatorsmile  Thanks. #65832 is the latest one which does not have the same failure.

Test build #65856 has started for PR 15218 at commit f71f1c0.

Test build #65856 has finished for PR 15218 at commit f71f1c0.

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

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

Merged build finished. Test PASSed.

Test build #66328 has started for PR 15218 at commit c7a0ce2.

Test build #66328 has finished for PR 15218 at commit c7a0ce2.

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

Merged build finished. Test PASSed.

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

@mridulm Thanks for review this. Will wait for a while in case there are more comments before solving it.

Test build #66465 has started for PR 15218 at commit ed8dd69.

Test build #66465 has finished for PR 15218 at commit ed8dd69.

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

Merged build finished. Test PASSed.

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

Btw, taking a step back, I am not sure this will work as you expect it to.
Other than a few taskset's - those without locality information - the schedule is going to be highly biased towards the locality information supplied.
This typically will mean PROCESS_LOCAL (almost always) and then NODE_LOCAL - which means, exactly match the executor or host (irrespective of the order we traverse the task list).
The shuffle of offers we do is for a specific set of purposes - spread load if no locality information (not very common imo) or spread it across cluster when locality information is of more 'low quality' - like from an InputFormat or for shuffle when we are using heuristics which might not be optimal.
But since I have not looked at this in a while, will CC kay. +CC @kayousterhout pls do take a look in case I am missing something.

@mridulm Thanks for the comments. Your concern regarding the locality is right. The patch does not change this behavior, which takes priority of locality preference. But if multiple executors satisfying the locality restriction, the policy will be applied. In our production pipeline, we do see a big gain with respect to reserved cpu resources when dynamic allocation is enabled.
@kayousterhout Would you like take a look and provide your comments?

@zhzhan I am curious why this is the case for the jobs being mentioned.
This pr should have an impact if the locality preference of the taskset being run is fairly suboptimal to begin with, no ?
If the tasks have PROCESS_LOCAL or NODE_LOCAL locality preference - that will take precedence, and attempts to spread the load or reduce spread to nodes as envisioned here will not work.
So the target here seems to be RACK_LOCAL or ANY locality preference - which should be fairly uncommon; unless I am missing something here w.r.t the jobs being run.

@mridulm  You are right. This patch is mainly for the job that has multiple stages, which is very common in production pipeline. As you mentioned, if there is shuffle involved, getLocationsWithLargestOutputs in MapOutputTracker typically return None for the ShuffledRowRDD and ShuffledRDD because of the threshold REDUCER_PREF_LOCS_FRACTION (20%).
The ShuffledRowRDD/ShuffleRDD can be easily more than 10 partitions (even hundreds) in real production pipeline, thus the patch does help a lot in CPU reservation time.

I am assuming @kayousterhout does not have comments on this.
Can you please fix the conflict @zhzhan ? I will merge it in after that to master.

Test build #67021 has started for PR 15218 at commit 98a9747.

Test build #67021 has finished for PR 15218 at commit 98a9747.

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

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

Merged build finished. Test PASSed.

Merged to master, thanks @zhzhan !

@mridulm  Thanks for reviewing this.

@zhzhan and @mridulm all the classes need to be private[scheduler] shouldn't they?

@mridulm @zhzhan I liked the idea here, but unfortunately I think it's merged prematurely. There are insufficient documentation and basic styles that don't align with rest of Spark. I'm going to revert this. It would be good to get this in, and I think with very little work we can get it to a shape that look a lot better.

@zhzhan in general it'd be great to have proper documentation on the classes. For example, it is important to document the behavior of the various assigners, and even more importantly, document the contract for TaskAssigner. The control flow is fairly confusing right now -- I'm not very smart and things that are complicated take me a long time to understand, and when I try changing them in the future, there's a very good chance I will make a mistake and mess it up. It would be great if we can simplify the control flow. If we can't, then we should document it more clearly. For example, when init/reset should be called are all part of the contracts, and none of them are really documented.

@rxin Thanks a lot for the detail review. I will update the patch.

The test case design is pretty good. It covers all the scenarios.

Could you add a check for the negative case? That means, when users do not provide the right TaskAssigner name, we fall back to the default round robin one
For the existing unchanged test cases in TaskSchedulerImplSuite.scala, please add a check to verify whether it picks the default one.
If possible, please change one of the existing test case in TaskSchedulerImplSuite.scala, ensure that users are allowed to input the round robin as the task assigner.

@wangmiao1981 Thanks for reviewing this. I will open another PR solving these comments soon.


--save_mask option for Tile Processing

Is there a way to save the instance mask separately (similar to --save_mask used in WSI processing) for Tile Processing?

The instance map is saved here as a .mat file. You will need to specifically access the inst_map key when loading. If you wanted to save this as an image, then you can independently save inst_map as an image in the code as you wish. Make sure that your instance id's aren't effected by using specific data types such as uint8!


BuilderViewImplementation

Corrected errors from last request. BuilderApp linked to LevelTypeSelect and BuilderView

Denied pending more changes to storing highest level ID


Case insensitive search?

Problem
I have data that was imported from an external source with inconsistent capitalization. Searching in lowercase does not return the intented results. Eg: 'sno' returns 'snow' but not 'Snow'.
class Tag < ActiveRecord::Base
  include PgSearch
  pg_search_scope :autocomplete, against: :name,
                                 using: {tsearch: {prefix: true}}
end

Question
Is there a setting I can add to my search scope to make it case insensitive without needing to add AR validations / normalize the attributes being searched through?
Thanks for maintaining this project. It's been very helpful.

what's the status on this. I'm having the same problem

Have the same problem too

@asiniy Are you using the Russian dictionary? Like this:
class Tag < ActiveRecord::Base
  include PgSearch
  pg_search_scope :autocomplete,
    against: :name,
    using: {
      tsearch: {
        dictionary: 'russian',
        prefix: true
      }
    }
end

See http://www.postgresql.org/docs/current/static/textsearch-dictionaries.html for more information. As for whether or not the search is insensitive, that's really up to what PostgreSQL full-text-search does under the hood. pg_search for the most part just forms the queries for you. If there is an option to change the queries generated to choose whether case is insensitive or not, that would be something great to add to pg_search, but otherwise that might be something that you'd need to configure directly with the database.

@nertzy here is mine scope.
  pg_search_scope :search, against: { title: 'A', description: 'B' },
    using: { tsearch: { prefix: true, dictionary: 'russian' } }

Task.search('Фасад') # => return records
Task.search('фасад') # => hasn't any record. 'фасад' is undersored 'Фасад'

Make sure that you have configured collation and ctype correctly. Type \l+ in psql console and run something like SELECT LOWER('Фасад') If LOWER doesn't produce the right result you can be sure that it is an enconding issue. In this case, you have to dump your data, create a new database with correct LC_COLLATION, LC_CTYPE and restore the data.

Just to keep it for future googlers 🧐
Add to database.yml collation and ctype rows as in following example for russian language:
default: &default
  adapter: postgresql
  encoding: unicode
  collation: ru_RU.UTF-8
  ctype: ru_RU.UTF-8

Thanks @arkdy! I'm going to close this issue, since this appears not to be a pg_search issue.

By change database.yml I got error
ActiveRecord::StatementInvalid: PG::InvalidParameterValue: ERROR:  new collation (ru_RU.UTF-8) is incompatible with the collation of the template database (C)
HINT:  Use the same collation as in the template database, or use template0 as template.

I have to add template: template0 rails database.yml
default: &default
  adapter: postgresql
  encoding: unicode
  template: template0
  collation: ru_RU.UTF-8
  ctype: ru_RU.UTF-8

Now search works as case insensitive


Show pedometer distance graph

[ ] Show a chart of distance since the pedometer was reset

More research is needed to see how useful this would be


Keep MonitorControl from asking for Accessibility Features everytime

First of all, thank you so much for this app. I looked for something like this for a long time!
Since I had no idea about DDC/CI, all options that I could find involved installing virtual sound devices and things like that.
They did solve the problem, but were more complex to install or weren't free.
I use it to control sound volume of my external monitor connected through DisplayPort, and the native volume keys on Apple's wireless keyboard work fine with the app, so there's no need to grant Accessibility Features to it. But it keeps asking for granting every single time it's launched.
Is there another way to stop these requests?

I had the same hickup when first installing MonitorControl and solved it:

go into Settings --> Security --> Privacy --> Accessibility
Remove MonitorControl from there (click on it and use the Minus Symbol, NOT deselect)
Restart your Mac
Start MonitorControl and confirm the use of accessibility
Restart again (just to be sure)

Now everything should be fine :-)

Hi, thank you for responding and sorry for taking so much time to write my own response.
Eventually I just added the app to the list of Accessibility Features in order to stop all the constant prompts.
Currently I use a common PC wireless keyboard (with a USB dongle).
The issue now is that after updating to v1.5.2 the brightness and volume keys (along with the on-screen notifications) stopped working. They worked normally in v1.3.0.


Initial checkin

basic top module
updated info.yaml
basic cocotb testbench

apologies, PR made on the wrong project. Disregard!


[BUG]: Record Count is mismatched on ScholarshipTopClasStudents

On Search list view record count is showing 29 but on card view its showing 26

Steps to replicate

Login with scholarship
Click on ScholarshipTopClasStudents card
Click on add
Add single record
Record count will get increased
Go back to the card view

@Renuka-S This issue is regarding EER record count which is not duplicate.
#603  This is regarding issuance portal which is duplicate i have marked. Jaya has already created same issue long back - #500


Hanging on a unary call using a custom client timeout

**The call hangs forever regardless the timeout duration setting:
GoogleAdsServiceClient.SearchPagedResponse response;
try ( GoogleAdsServiceClient googleAdsServiceClient = googleAdsClient.getLatestVersion().createGoogleAdsServiceClient() ){
String query = "SELECT customer_client.client_customer, customer_client.level, "
+ "customer_client.manager, customer_client.descriptive_name, "
+ "customer_client.currency_code, customer_client.time_zone, "
+ "customer_client.id "
+ "FROM customer_client "
+ "WHERE customer_client.level <= 1 AND customer_client.status IN ('ENABLED')";
                GoogleAdsServiceClient.SearchPagedResponse response = googleAdsServiceClient.searchPagedCallable()
                        .call(SearchGoogleAdsRequest.newBuilder()
                                .setQuery( query )
                                .setCustomerId( Long.toString( customerIdToSearchFrom ) )
                                .build(),
                                GrpcCallContext.createDefault()
                                        .withTimeout(Duration.ofMinutes(1)));

I also tried the alternative search func:
.search(
SearchGoogleAdsRequest.newBuilder()
.setQuery( query )
.setCustomerId( Long.toString( customerIdToSearchFrom ) )
.build() );
This one timeout after an hour with:
io.grpc.StatusRuntimeException: UNAVAILABLE: Credentials failed to obtain metadata
What's interesting is that among multiple accounts we have, this timeout issue only happen on a specific one. Other accounts all look fine.
**
Steps to Reproduce:
Expected behavior:
**Client library version and API version:
**
Client library version:
Google Ads API version:
V10
JDK version:
1.8 and 11
**Request/Response Logs:
io.grpc.StatusRuntimeException: UNAVAILABLE: Credentials failed to obtain metadata
**

Anything else we should know about your project / environment:

Hi,
This is due to invalid credentials (client ID, client secret, refresh token). Please see issue #169 .
Thanks,
Josh


OTT-353 Move searchHighlights to Stimulus Highlighter component

Jira link
OTT-353
What?
I have:

Created a new Hightlighter component which will highlight a given term within the contained DOM element
Replaced the old JQuery implementation and removed it

Why?
I am doing this because:

OTT-346

Existing tests should cover any regression.  No change to existing behaviours.
@HWallenberg to review.

Excellent ! 🙌
Just a couple of things, again we need to remove the this.searchHighlight.initialize(); at the bottom of commodities.js as it's throwing a js error and there are some js linting issues. Other than that, this is really good to get done, thanks. 😄
yarn run eslint $(git diff --name-only --diff-filter=ACM $(git merge-base main HEAD)..HEAD | egrep '\.js' | grep -v json)
See failed pipeline here👇

@HWallenberg Should be good to go now.


(BOLT-1259) Add acceptance tests for local transport

This commit adds acceptance tests for the local transport. These tests are intended to set a baseline for testing local transport on a variety of supported platforms that are not covered by integration tests. This first iteration tests the behaviour of run-as accross different platforms as well as using bolt's puppet to apply manifest code.

CLA signed by all contributors.

Passing bolt-vanagon package acceptance tests.  https://jenkins-master-prod-1.delivery.puppetlabs.net/view/__experimental automatic/job/experimental_auto_bolt-vanagon_vanagon-integration-suite_no-PEZ-daily-master/
It was passing the bolt component git based tests on Friday. Currently blocked on the cri 2.15.4 compatibility with the system ruby on osx10.13 bolt controller. I think that a fix upstream in r10k (restrict cri version) will keep the bolt gem compatible with ruby 2.3.


Image appears zoomed and cropped

Any idea what might be causing the image to be cropped? I've seen similar issues in the older version, but a lot of the API has changed, and I am unsure how to approach it. I've tried changing the camera options but it doesn't appear to do anything for the stack version.
The image currently looks like this:

It should look like this:

This is a stack view. I've added the zoom and pan tool, but it seems like the image is still cropped.
Changing the properties or camera through setCamera and setProperties doesn't appear to do anything. I tried directly setting sHeight and sWidth, but that also doesn't appear to help.
Possibly Software Versions:
    "@cornerstonejs/calculate-suv": "1.0.2",
    "@cornerstonejs/core": "0.8.1",
    "@cornerstonejs/streaming-image-volume-loader": "0.2.24",
    "@cornerstonejs/tools": "0.15.4",
<EMAIL_ADDRESS>"24.0.0",
    "react": "17.0.2",
    "vite": "2.7.2"

These are the current viewport settings:

These are the metadata associated with the image using a custom metadataprovider with cornerstonewebimageloader
(not a real patient below)
accessionNumber: 7974669
acquisitionDate: 20150519
acquisitionNumber: 25
acquisitionTime: "082223"
additionalPatientHistory: ""
angleOfFirstView: 0
biopsyPosition: 0
biopsyRefLocation: 0
biopsyTLocation: 0
bitsAllocated: 16
bitsStored: 16
cellNumberAtTheta: 389.75
cellSpacing: 1.0239
centerACoordOfPlaneImage: 47.5999985
centerRCoordOfPlaneImage: 2.5999999
centerSCoordOfPlaneImage: -135.75
columns: 512
contentDate: 20150519
contentTime: "082225"
convolutionKernel: "STANDARD"
correctedAfterglowTerms: 0
dasAdInput: 0
dasCalMode: 0
dasFpaGain: 0
dasOutputSource: 0
dasTriggerSource: 0
dataCollectionDiameter: 500
degreeOfRotation: 362.926819
degreesOfAzimuth: 87
deltaStartTime: 0
dependantOnNumberOfViewsProcessed: 2
distanceSourceToDetector: 949.075012
distanceSourceToPatient: 541
durationOfXrayOn: 1
exposure: 37
exposureTime: 1000
filterType: "BODY FILTER"
firstScanRas: "S"
focalSpots: 1.2
frameOfReferenceUid: "<IP_ADDRESS>.4.1.59<IP_ADDRESS>0725868.1504138972.1445369770092.7.0"
fullFidelity: "CT_LIGHTSPEED"
gantryDetectorTilt: 0
gantryPeriod: 1
generatorPower: 36000
highBit: 15
horizontalFrameOfReference: 640.039978
imageActualDate:<PHONE_NUMBER>
imageFromWhichPrescribed: 2
imageOrientationPatient: (6) [1, '0.000000', '0.000000', '0.000000', 1, '0.000000']
imagePositionPatient: (3) [-131.1, -176.1, -135.75]
imageType: (3) ['ORIGINAL', 'PRIMARY', 'AXIAL']
instanceCreationDate: 20150519
instanceCreationTime: "082225"
instanceNumber: 200
institutionName: "Stanford"
kvp: 120
lastScanRas: "I"
manufacturer: "GE MEDICAL SYSTEMS"
manufacturerModelName: "Discovery ST"
maxOverrangesInAView: 0
midScanFlag: 1
midScanTime: 56.425903
modality: "CT"
nameOfPhysiciansReadingStudy: ""
noViewsRefChannelsBlocked: 0
normalACoord: -0
normalRCoord: 0
normalSCoord: 1
numberOfCellsInDetector: 912
numberOfOverranges: -1
numberOfTriggers: 992
operatorsName: "JL"
patientAge: "068Y"
patientBirthDate: 19470328
patientId: 8907068
patientName: "Kim^SphericalMets"
patientPosition: "HFS"
patientSex: "F"
patientWeight: 70
performedProcedureStepDescription: "Radiation Oncology CT"
performedProcedureStepId: "PPS ID  21429"
performedProcedureStepStartDate: 20150519
performedProcedureStepStartTime: "081652"
photometricInterpretation: "MONOCHROME2"
pixelData: null
pixelPaddingValue: -2000
pixelRepresentation: 1
pixelSpacing: (2) [0.501953, 0.501953]
planeType: 2
positionReferenceIndicator: "OM"
privateCreator: "GEMS_HELIOS_01"
privateScanOptions: 2
productId: "Discovery ST"
protocolName: "2.3 STEREO BRAIN"
raCoordOfTargetReconCentre: (2) [2.6, 47.599998]
reconPostProcessingFlag: 1
reconstructionDiameter: 257
referenceChannels: 0
referencedImageSequence: [{…}]
referencedPatientSequence: [{…}]
referencedStudySequence: [{…}]
referringPhysicianName: ""
requestAttributesSequence: [{…}]
rescaleIntercept: -1024
rescaleSlope: 1
rescaleType: "HU"
rotationDirection: "CW"
rows: 512
samplesPerPixel: 1
scanFovType: 16
scanOptions: "AXIAL MODE"
scanPitchRatio: ""
scoutType: 0
segmentNumber: 0
seriesContrast: 0
seriesDate: 20150519
seriesDescription: "STEREO BRAIN"
seriesFromWhichPrescribed: 1
seriesInstanceUid: "<IP_ADDRESS>.4.1.59<IP_ADDRESS>0725868.1504138972.1445369770092.6.0"
seriesNumber: 2
seriesTime: "082114"
sliceLocation: -135.75
sliceThickness: 1.25
smartScanOnOffFlag: 0
softwareVersions: "CyberKnife Information System <IP_ADDRESS>"
sopClassUid: "1.2.840.10<IP_ADDRESS>.1.1.2"
sopInstanceUid: "<IP_ADDRESS>.4.1.59<IP_ADDRESS>0725868.1504138972.1445369770092.189.0"
startScanToXrayOnDelay: 0
startTimeSecsInFirstAxial:<PHONE_NUMBER>.773211
stationName: "stct"
studyDate: 20150519
studyDescription: "Radiation Oncology CT"
studyId: 21429
studyInstanceUid: "<IP_ADDRESS>.4.1.59<IP_ADDRESS>0725868.1504138972.1445369770092.2.0"
studyTime: "081652"
suiteId: "STCT"
tableEndLocation: 0
tableHeight: 176
tableSpeed: 0
tableStartLocation: 0
totalSegmentsRequested: 0
triggerFrequency: 984
triggerOnPosition: 147.926682
uniqueImageIdentifier: null
unknownTagData: ""
viewCompressionFactor: 1
vmaClip: 0
vmaMamp: 0
vmaMod: 0
windowCenter: 40
windowValue: 400
windowWidth: 400
xRayTubeCurrent: 300
xrayChain: 99

Is this happening for this Stack of images only? or other stacks work fine?

It happens on all stacks, and I've tried just swapping out my source URLs with the random images. It still gives me a zoomed in and cropped image.

hmmm, the demo examples are working fine (https://www.cornerstonejs.org/docs/examples)
I'm wondering if this is related to your metadataProvider. How are you loading the images?

Using the cornerstone webimageloader library. The metadata gives back exactly what is shown with the exception that the custom metadata checks if type is calibratedPixelSpacing; if so, it gives back the pixelSpacing value.

Hi, I'm having the same error, I'm using the latest versions of the packages and still having errors when loading the example Image
https://rawgit.com/cornerstonejs/cornerstoneWebImageLoader/master/examples/Renal_Cell_Carcinoma.jpg
I'm getting this result, also working with the cornerstoneWebImageLoader

if it's a metaprovider error, please can someone show the correct values for this, because in the code examples the metadaprovider are not similar to the examples that are in the documentation.
https://www.cornerstonejs.org/docs/how-to-guides/custom-metadata-provider
is nothing clear to the data that need to be defined in the provider for the viewer to work.


Default ordering of search results

When no search query has been entered (as in browse all, browse by content type, browse by topic), results should be default ordered with most recent resources appearing first.
This will ensure that the default results stay fresh and new resources are featured.

Clarification: the default sort should be based on the "Date Posted" field (i.e., the date something was added to the Hub), not the date an item was published or created. For example, if a publication from 2007 was just posted to the Hub, it would still appear at the top of the default browse results (until it is displaced by even more recent submissions).

I've managed to implement this in the code, but I've run into a snag: Most content types don't actually have/require this date created field. If I sort in this way, those without dates appear first, with the correctly sorted items with a date created at the end. I can confirm sorting's working correctly, if I invert it to be in ascending order, those items with dates appear at the top, but with the oldest item appearing first.
I thought I should get some feedback here to see how you'd like to proceed. I feel like sorting this way doesn't accomplish anything in a world where almost nothing has this data to sort by (and if someone does put it on their submission, it's doomed to go to the end of the list).

Unless you mean "Date Published" referring to the date it was approved and published to the Hub. I just did a ticket about making these labels more uniform, but we kind of use different names for them all over the place in here.

Not sure if you resolved this on the call yesterday, but the intention was to organize by date posted in the Hub (which all resources should have) rather than the date created/published field. There is a comment above from Apr 14 that tries to clarify this.

Yes I got it straightened out, just confusion over nomenclature.


Add Wheaton college (Norton, MA, USA)

College URL: https://wheatoncollege.edu/
Program URL:
https://wheatoncollege.edu/academics/programs/computer-science/#

@tony-tong-wheaton lib/domains/edu/wheaton: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.


Fix Cask handling in brew deps and brew uses.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?

Fixes #10906.

Review period will end on 2021-03-23 at 22:28:14 UTC.


don't bother with transactions for client DB

Some users are still hitting 'database is locked' errors despite SQLite being tuned properly as far as I can tell. We really don't need transactions for this, so just remove them.

@vito is it the busy_timeout setting that allows concurrent writes to work with no locking? Just curious

@sipsma I think journal_mode=WAL is closer to that - busy_timeout just controls how long it'll wait for a lock. This post does a quick rundown of common settings, but we already set all of them. (Even that post doesn't cover all of it btw, there's more in the comments here - which we also already configure.)
It's a bit surprising this happened considering we already tune all the "magic knobs" I know of and even have one-db-per-client, but I'm pretty certain we don't actually need transactions for this, so it seems worth trying and might help perf a bit. Merged this a bit aggressively so that I can hand the CI-pushed image ref to the affected user and see if it fixes things for them. Will keep an eye out for any sketchiness.


Compare MOZJPG

I've found this : https://css-ig.net/articles/guetzli
MOZJPG compress more but quality is better with GUETZLI ?? I read GUETZLI has better compression.... or  it's because it's not the same quality ........ what settings should I use to get the best results ???
I would love to do testing too but.... I don't understand how to compare because DISSM is for 2 PNG !!!
"This tool computes (dis)similarity between two or more PNG images using an algorithm approximating human vision."
https://github.com/pornel/dssim
I've found for Windows :+1: https://kornel.ski/dssim
But I have a error : "not a PNG files" when I try JPGS !!!
Ok I found it.... It works if I convert JPGS to PNGS with Photoshop

There's an issue for this comparison: #10

Sorry I did'nt see that ! Thank you very much for your very useful tool !!


Network discovery?

It's kinda hard to figure out your switch's IP address, maybe there's a way to do network discovery by broadcasting the IP address

Good one....


Two input field + mobile => not always the appropiate date is replaced

Having a setup where you have both 'element' and 'elementEnd' configured, 'allowRepick' enabled and you are on mobile, the repick is not working correctly. Not the clicked element's value will be replaced but the initially bigger value.
Also if you disable the 'allowRepick' then - by design - you always have to select two dates, but in the previously mentioned setup, also only on mobile, the selector closes after the first click, replacing the biggest date, while keeping the smaller one.
I was trying to figure it out, but no luck yet. My best guess is that the onMouse event handlers are the key as they don't activate on mobile environment, Maybe this is causing the issue.

Should be fixed in v1.0.27 (just now published).
Thanks for information.

Wow, that was fast. Thanks.


How devices get the symmetric keys?

The SAS token is generated based on the symmetric key which is stored in the registry of the IoT hub. But how does the device get the key? It's said that the key is not sent on the wire. Thanks!

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

ID: 5abe8bb4-f610-0800-6ad8-b78349018779
Version Independent ID: c772405d-98b1-ebdc-29e9-2b65da12ba99
Content: Understand Azure IoT Hub security
Content Source: articles/iot-hub/iot-hub-devguide-security.md
Service: iot-hub
GitHub Login: @wesmc7777
Microsoft Alias: wesmc

Hello @JiudanZheng
The Symmetric Keys are not sent over the wire. Rather we can make use of 'Token Service' to handle generating the SAS token which can live for a short duration of time. If the IoT Device is compromised, the attack can abuse the device for only SAS token lifetime (Expiry time).
For more information please look at the below document. where no secret keys are stored on IoT Device.
Please refer to the Custom device and module authentication

Please let us know if that helps your query.

Hi @SatishBoddu-MSFT,
Thanks for the reply. I just went through the doc you sent to me. What are the details of custom authentication here? It's username/password or just device ID used as the identity of the device?

Hello @JiudanZheng

For more info, please see this document Using the MQTT protocol directly (as a device)
For example, when we use any MQTT client tool to Authenticate with IoTHub, we use them in the following highlighted fields. [Image is just to show the the usage]

@JiudanZheng Does that answer your query? We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


diff editor: Uncaught Error: Assertion Failed when enabling editor.ignoreTrimWhitespace

Version: 1.75.0 from main

set "diffEditor.ignoreTrimWhitespace": false

File 1, using 4 spaces as indentation

if True:
    print(2)

File 2, using tab as indentation

if True:
	print(2)

Select both files and invoke Compare Selected

Dev tools pop up on debugger statement
Uncaught Error: Assertion Failed

Error: Assertion Failed
    at assertFn (../../../vs/base/common/assert.js:48:45)
    at SmartLinesDiffComputer.computeDiff (../../../vs/editor/c…ffComputer.js:52:35)
    at EditorSimpleWorker.computeDiff (../../../vs/editor/c…pleWorker.js:250:42)
    at EditorSimpleWorker.computeDiff (../../../vs/editor/c…pleWorker.js:244:39)
    at SimpleWorkerServer._handleMessage (../../../vs/base/com…pleWorker.js:365:69)
    at Object.handleMessage (../../../vs/base/com…pleWorker.js:350:55)
    at SimpleWorkerProtocol._handleRequestMessage (../../../vs/base/com…pleWorker.js:156:42)
    at SimpleWorkerProtocol._handleMessage (../../../vs/base/com…pleWorker.js:125:33)
    at SimpleWorkerProtocol.handleMessage (../../../vs/base/com…pleWorker.js:118:18)
    at SimpleWorkerServer.onmessage (../../../vs/base/com…pleWorker.js:355:28)
    at eval (../../../vs/base/common/errors.js:19:31)
bootstrap-window.js:261 [uncaught exception]: null

@aeschli I'm having trouble reproducing. Have you customized other settings?

Blocks https://github.com/microsoft/vscode/pull/169555

I can reproduce when typing a <space> in one of the sides:

It looks like this was an incorrect assertion introduced via https://github.com/microsoft/vscode/commit/c2cc481940d538a41c311411484ffc909b8054b8
I will comment out the assertion for now.

You are correct, there needs to be additional spaces in file 2 after print(2). Sorry for that. I fixed the description
if True:
	print(2)


[v1.12] renovate: Replace update-hubble-version.sh with Renovate Bot

Custom backport of https://github.com/cilium/cilium/pull/23508 to v1.12. This does not contain the renovate.json changes (since that file does not exist in stable branches, it's only read by renovate from the default branch).

/test-backport-1.12

Should we get one of the original reviewers to review this (and sibling backport PRs) as well?

Should we get one of the original reviewers to review this (and sibling backport PRs) as well?

We can, but I don't think it's necessary. It's a fairly harmless change. As long as the image build passes, there should be no functional change, since (if you ignore the deleted scripts) we're basically only adding a few # renovate lines that will be picked up by Renovate once it's merged. The worst that could happen I think is that the change does not take any effect, because we missed something in the renovate.json in master. But that would have to fixed in master and wouldn't change the diff of this PR.

Maybe to give more context: Renovate is already active on the v1.1x branches since the upstream PR was merged. It would already bump the Hubble CLI docker images, if they were out of date (which they are currently only in v1.13, see https://github.com/cilium/cilium/pull/23520).
The only interesting thing that this PR here adds (besides the script removal) is the # renovate annotations to the pinned digests/version in the shell script. The regex for those annotations is already live on all stable branches and master. Thus, once this PR is merged, Renovate will start automatically updating them if there is a new Hubble CLI GitHub release (which currently, there is not), without any further configuration needed.

https://jenkins.cilium.io/job/Cilium-PR-K8s-1.20-kernel-4.9/1576/ hit unrelated flake https://github.com/cilium/cilium/issues/18318
https://jenkins.cilium.io/job/Cilium-PR-K8s-1.22-kernel-4.9/415/ hit unrelated flake https://github.com/cilium/cilium/issues/13071

Marking ready to merge.


Strange behavior on IE<11

I've noticed that I sometimes don't see js-search results that match part of a word in older versions of IE (before IE11). For example, here's the latest Safari:

And here's the same thing in IE10:

I can't seem to figure out what's causing some of the results to appear in IE (doesn't appear to be related to capitalization or the location of the match within the string) but not others. Any guidance here would be much appreciated.

Sorry about the gif quality; here's a closer look at the number of results.
Safari:

IE10:

Hey @JacobEvelyn.
Sorry for the slow response! I'm traveling in China atm and my Internet access is spotty.
Thanks for the quality bug report. Greatly appreciate the detail.
I have no idea what's going on here to be honest. I am able to reproduce the issue though using a VM with IE 10.

I am able to reproduce this with a reduced book set:
{
  "books": [
    {
      "isbn": "0877854106",
      "title": "A Swedenborg Sampler: Selections from Heaven and Hell, Divine Love and Wisdom, Divine Providence, True Christianity, and Secrets of Heaven",
      "author": "Emanuel Swedenborg"
    },
    {
      "isbn": "0520203259",
      "title": "Hellenistic history and culture",
      "author": "Peter Green"
    },
    {
      "isbn": "0521228298",
      "title": "The Hellenistic world from Alexander to the Roman conquest : a selection of ancient sources in transla",
      "author": "M. M Austin"
    },
    {
      "isbn": "0521306965",
      "title": "A Hellenistic anthology",
      "author": "Neil Hopkinson"
    }
  ]
}

For some reason, IE10 shows the following results:

Search text
Num results

h
4

he
0

hel
0

hell
1

Chrome behaves as would be expected.

Ah! Found the issue, although I'm not sure I understand it.
I was tokenizing like so:
public expandToken(token:string):Array<string> {
  var expandedTokens = [];
  var prefixString:string = '';

  for (var i = 0, length = token.length; i < length; ++i) {
    prefixString += token.charAt(i);
    expandedTokens.push(prefixString);
  }

  return expandedTokens;
}

But for some reason, IE10 would sometimes turn a token like "foobar" into "f, foobar, foobar, foobar, foobar, foobar" (instead of "f, fo, foo, foob, fooba, foobar"). I was able to fix this by changing the tokenizer to use .substr instead of appending to the string:
public expandToken(token:string):Array<string> {
  var expandedTokens = [];
  var prefixString:string = '';

  for (var i = 0, length = token.length; i < length; ++i) {
    expandedTokens.push(token.substr(0, i + 1));
  }

  return expandedTokens;
}

Fixed via 2f496b3, released as version 1.3.2. Thanks for the report.

Thanks so much for the speedy investigation and fix!

Hi @bvaughn,
This bug was reintroduced with https://github.com/bvaughn/js-search/commit/201d73246e33f2d881818cfdca83230f74b1a86a

PRs welcome. I won't have time to look into this.


possibly add #include <stdint.h> to number.h

when compiling for some, such as STM32, boards, I get errors of undefined 'uint32_t' and 'uint16_t'.
I believe that this can be resolved by adding '#include <stdint.h>' just after then multiple include safeguard, say at line 34.
If you have an alternative suggestion, I'm all ears!
This is using the IDE 2.2.1

Done, see 02af385c5ae6fe44498c4e9d050a99000cb1beee


hide action column on grid when visible buttons dosen't exist #1…

Q
A

Is bugfix?
yes

New feature?
no

Breaks BC?
no

Tests pass?
no

Fixed issues
#12468

First of all visibleButtons property could be either bool value or a closure.
Secondly, this change breaks backward compatibility by changing default behavior.
The PR can not be accepted, sorry.


change table name (fix #47) and some minor changes

@noam148 what can you say about this changes?

Thanks it's merged!


Android 6.0 permissions

Right now it's not working at android 6.0.
http://developer.android.com/intl/pt-br/training/permissions/requesting.html

Latest commit fixes this issue.

Thanks


I am unable to pump out of the grindr without taking coal. [1.15.2]

I am using logistical transporters from Mekanism.

This is a standard vanilla behaviour for furnaces, blast furnaces, etc: sides are for fuel extract/insertion (although there is no vanilla method for extracting fuels).
You'll need to attach your logistical transporter to the bottom in order to actually get the output, as though it were a furnace.


Fix an issue with range sliders

At the moment the range sliders don't work:

After this change they do:

Also included a very minor text change.

is this an abandoned project because the issue still persists

Not abandoned—I just missed the PR, thanks for fixing it @andreaselia!


added docker support

added dockerfile and docker-compose file

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

Duplicate of #670. Please see my comment there.


Update DEX file magic

https://github.com/mihaip/dex-method-counts/blob/master/src/com/android/dexdeps/DexData.java#L571-L572
static class HeaderItem {
  public static final byte[] DEX_FILE_MAGIC = { 0x64, 0x65, 0x78, 0x0a, 0x30, 0x33 }; // , 0x??, 0x00 };
}

private static boolean verifyMagic(byte[] magic) {
  return Arrays.equals(Arrays.copyOfRange(magic,0,HeaderItem.DEX_FILE_MAGIC.length), HeaderItem.DEX_FILE_MAGIC)
  && magic[HeaderItem.DEX_FILE_MAGIC.length] >= 0x30
  && magic[HeaderItem.DEX_FILE_MAGIC.length+1] == 0x00;
}

Guessing you're asking for the magic values to be updated with more recent versions. https://android.googlesource.com/platform/dalvik.git/+/67b37246c3edd037abc4b4af7e616e335aa64544/tools/dexdeps/src/com/android/dexdeps/DexData.java#547 has the complete list.
I'm no longer using or maintaining this tool, but if you would like to submit a PR with the updates, I'm happy to review it.


Is there a way to exclude certain notations?

I've been consistently utilizing this fantastic Lint tool, thank you.
I've run into a challenge lately and wanted to check if there's a feature for it. When there is a specific identifier, like 'some-vpc-0000', it doesn't pass the Lint unless it's 'some-VPC-0000'.
I'd appreciate it if there's a way to exclude this particular notation. If not, please allow me to assist in implementing this feature.

Should I proceed with this approach?
https://dev.classmethod.jp/articles/how-to-ignore-in-textlint/

You may try https://github.com/textlint/textlint-filter-rule-comments
<!-- textlint-disable -->

some-vpc-0000 is ok here

<!-- textlint-enable -->

<!-- textlint-disable aws-service-name -->

some-vpc-0000 is ok here

<!-- textlint-enableaws-service-name -->

some-vpc-0000 is not ok here

@watany-dev
I apologize for the delayed response!
For recurring prefixes, as you've said, they can be ignored with regular expressions!
Also, if you want to locally ignore the rules, as @exoego has mentioned, you can address this by inserting comments within the markdown.
@watany-dev Would either of these methods work for you?
@exoego Thank you as always!

Since some time has passed, I am going to close this issue for now.


cmd/link: ppc64 broken

ppc64 is broken on master & release-branch.go1.11 and go1.12:
https://build.golang.org/log/1113408cb4a4ffce758700267ba33b8eef9f4b63
from:
https://go-review.googlesource.com/c/go/+/172701
https://go-review.googlesource.com/c/go/+/172697
etc

I looked at this briefly on one of our ppc64 machines with master. From the error message, it sounds like x.o is created in a way that loadelf.go doesn't like. I was not able to reproduce the same error message that happens in the log.
If I try to run all the tests in cmd/link, I get an error on the statement that does go env CC, however if I just run the single test for TestSectionsWithSameName then it passes. In the output when running them all, it runs some tests, then I see PAUSE, then CONT, and almost as if the environments are getting mixed up between tests.
 go test -test.run=TestSectionsWithSameName -test.v
=== RUN   TestSectionsWithSameName
=== PAUSE TestSectionsWithSameName
=== CONT  TestSectionsWithSameName
--- PASS: TestSectionsWithSameName (0.35s)
    elf_test.go:80: gcc [-fPIC -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build142403988=/tmp/go-build -gno-record-gcc-switches] -o /tmp/go-link-TestSectionsWithSameName039763643/x.o /tmp/go-link-TestSectionsWithSameName039763643/x.s
    elf_test.go:87: /usr/bin/objcopy --rename-section .text2=.text1 /tmp/go-link-TestSectionsWithSameName039763643/x.o /tmp/go-link-TestSectionsWithSameName039763643/x2.syso
    elf_test.go:107: /home/boger/golang/go/bin/go build
PASS
ok  	cmd/link	0.357s

 go test -test.v
=== RUN   TestDWARF
--- SKIP: TestDWARF (0.00s)
    testenv.go:177: skipping test: no cgo
=== RUN   TestDWARFiOS
--- SKIP: TestDWARFiOS (0.00s)
    dwarf_test.go:181: skipping on non-darwin/amd64 platform
=== RUN   TestSectionsWithSameName
=== PAUSE TestSectionsWithSameName
=== RUN   TestLargeSymName
--- PASS: TestLargeSymName (0.00s)
=== RUN   TestIssue21703
=== PAUSE TestIssue21703
=== RUN   TestIssue28429
=== PAUSE TestIssue28429
=== RUN   TestUnresolved
--- PASS: TestUnresolved (0.29s)
=== RUN   TestBuildFortvOS
--- SKIP: TestBuildFortvOS (0.00s)
    testenv.go:177: skipping test: no cgo
=== RUN   TestLargeText
--- FAIL: TestLargeText (1.59s)
    linkbig_test.go:92: Build failed for big text program with internal linking: exit status 1, output: go: cannot find main module; see 'go help modules'
=== CONT  TestSectionsWithSameName
=== CONT  TestIssue28429
=== CONT  TestIssue21703
--- FAIL: TestSectionsWithSameName (0.01s)
    elf_test.go:67: exit status 1
--- PASS: TestIssue28429 (0.25s)
--- PASS: TestIssue21703 (0.25s)
FAIL
exit status 1
FAIL	cmd/link	2.145s

I must not be running it exactly the same way as the builder does, or the system is different. I was testing on a power8 rh7.6 with gcc 4.8.5 and binutils 2.27. Also some newer gcc versions didn't fail either.


[Bug]: Audit failures from lodash imports

Version
27.0.5
Steps to reproduce
Use Jest@latest (27.2.4 today).
Run npm audit, see audit failures related to lodash (this is from better-npm-audit):
╔══════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                                      === npm audit security report ===                                                       ║
║                                                                                ║
║ ID      │ Module │ Title                              │ Paths           │ Sev.     │ URL                                               │ Ex. ║
║ 1002373 │ lodash │ Arbitrary code execution in lodash │ lodash          │ critical │ https://github.com/advisories/GHSA-8p5q-j9m2-g8wr │ n   ║
╚═════════╧════════╧════════════════════════════════════╧═════════════════╧══════════╧═══════════════════════════════════════════════════╧═════╝

But when you look at the advisory it's an edge case: it's a vulnerability that is only present when you take user input and put it into a template. NPM's audit is very paranoid and that's OK. Better to get notified about all potential failures IMO.
Then I run a why and get a lot of output similar to this:
           node_modules/jest-cli
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/jest
                dev<EMAIL_ADDRESS>from the root project
                peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>                node_modules/ts-jest
                  dev<EMAIL_ADDRESS>from the root project

So the conclusion seems to be that ts-jest is importing too much of Lodash.
Expected behavior
I'd like ts-jest to not result in audit failures.
Actual behavior
I'm getting audit failures.
Debug log
I don't think this is relevant here.
Additional context
We solve this by importing the mini-packages like lodash.range. It looks this is feasible here as well.
I'm open to making a PR for this if the team is willing to consider this change.
Environment
System:
    OS: macOS 10.15.7
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
  Binaries:
    Node: 14.17.6 - ~/.nvm/versions/node/v14.17.6/bin/node
    npm: 7.22.0 - ~/.nvm/versions/node/v14.17.6/bin/npm
  npmPackages:
    jest: ^27.2.4 => 27.2.4

PR is welcome, indeed I see https://github.com/kulshekhar/ts-jest/blob/main/package.json#L63


update dependabot to weekly

Description
Please summarise the changes.
Related issues
Please mention any github issues addressed by this PR.
Checklist

[ ] I have performed a self-review of my code.
[ ] I have commented hard-to-understand parts of my code.
[ ] I have made corresponding changes to the public API documentation.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have updated the changelog with any user-facing changes.

It would be nice to do the action update a bit more coordinated on all the extensions together


Update julia to v1.5.2

Can we do https://github.com/JuliaRegistries/General/pull/18872#issuecomment-668341969 instead?

I agree. Now that we have https://julialang-s3.julialang.org/bin/versions.json, I don't think we need to have Julia in the registry.


FIX: add check for 64-bit macOS in Try_Browser.

Since 64-bit builds define TO_OSX_X64 rather than TO_OSXI, browse currently attempts to exec xdg-open and x-www-browser rather than leveraging open.
N.B. The ifdef here is pretty ugly; it's probably worth factoring out the platform check as some forks have already done.

Thanks... I will try to remember it and try it once I will be sitting in front of Mac.


Support extracted comments

#.

Blocked by #106

Dear @mondeja Please reopen this, because according to Weblate # is a comment FROM a translator, not FOR the translator and not supported as such by Weblate (https://github.com/WeblateOrg/weblate/issues/8260#issuecomment-1289355788). So, to make the comments appear in Weblate as hints to the translators and to stay in the POT files also after md2po updating them, it makes sense to make md2po keeping the #. comments.

The intention is to not touch the source md files to:

ensure better human readability,
avoid probably markdownlinter complaining about HTML content (untested)
and leave them as much original as possible for alternative translation methods, like direct md to md translations.
Instead, the goal is to concentrate the translator activities and data in pot (and their po) files, here through comments in pot files.

Use --save along with --po-filepath to avoid the stripping. Example:
Markdown:
Some text that needs to be clarified

PO:
#
msgid ""
msgstr ""

#. This is a comment for a translator
msgid "Some text that needs to be clarified"
msgstr ""

Execution: md2po foo.md -s -p foo.po

That's strange, because I already used the options (version 1.0.3):
md2po -q -w 0 -d 'Content-Type: text/plain; charset=UTF-8' -d 'Language: en' -s --pofilepath ../resources/pot_files/content/"$1".pot --po-encoding UTF-8 ../content/"$1".md
Can you spot the problem?

I might have found the problem: --pofilepath seems not to be fully equivalent to -p!
After I changed the option to -p in my command above, it preserves the #. comments.

Can you spot the problem?

No, please share a minimal reproducible example.

I might have found the problem: --pofilepath seems not to be fully equivalent to -p!

That's not possible, you've done something else.


Authentication module

In one of the MRs, someone asked a question about an example of authorship. In 2021 you wrote that if you find time you will implement such an example. Is this up to date?
I'm interested in this topic and would like to see what it might look like with your eye.

I'd recommend to follow one of many NestJS auth tutorials out there, for example:
https://docs.nestjs.com/security/authentication
That should be enough in most cases, I don't think that my implementation would be much different than that.


Using kam1n0 with IDA Demo

Hello,
I am trying to use Kam1n0 with IDA Demo: I am able to see the interface but I am not able to perform any analysis. Is there a way to fix that?
Also, are we able to test Kam1n0 with IDA Pro free?
Thanks.

Hi! Currently Kam1n0-plugin is not working with the demo version. One needs to heavily modify the plugin source code. This is currently not a priority in our to-do list.  Thanks!


SyntaxError: Unexpected token } in JSON at position 199 at JSON.parse()

Description
I'm using lint-staged 13.1.2 with husky version 8.0.0 and eslint 8.17.0. When trying to commit to my branch, I keep getting an error from the lint-staged node modules:

It seems to be referencing the loadConfig.js file's jsonParse() method. I see that there is a searchPlaces array in that file which I'm guessing could be related to the issue, but I don't see any errors with my package.json in terms of brackets, and I don't have another lint-staged config file. The debug logs seem to support the idea that the problem is with my package.json, but I don't even have a
loadConfig.js

package.json
{

    "name": "axen-ui",

    "version": "0.0.1",

    "author": "Ionic Framework",

    "homepage": https://ionicframework.com/,

    "scripts": {

        "ng": "ng",

        "start": "sudo ng serve --proxy-config proxy.conf.js",

        "build": "ng build",

        "test": "ng test",

        "lint": "ng lint",

        "style": "npx prettier --write src/",

        "e2e": "ng e2e",

        "prepare": "husky install"

    },

    "private": true,

    "dependencies": {

        "@angular/animations": "^13.3.12",

        "@angular/cdk": "13.0.0",

        "@angular/common": "~13.3.12",

        "@angular/compiler": "~13.3.12",

        "@angular/core": "~13.3.12",

        "@angular/forms": "~13.3.12",

        "@angular/platform-browser": "~13.3.12",

        "@angular/platform-browser-dynamic": "~13.3.12",

        "@angular/router": "~13.3.12",

        "@angular/service-worker": "~13.3.12",

        "@fusioncharts/fusiontime": "^2.6.0",

        "@ionic-native/core": "^5.0.0",

        "@ionic-native/splash-screen": "^5.0.0",

        "@ionic-native/status-bar": "^5.0.0",

        "@ionic/angular": "^6.1.10",

        "@ionic/storage": "^2.2.0",

        "@kolkov/angular-editor": "^3.0.0-beta.0",

        "@syncfusion/ej2-angular-calendars": "19.2.62",

        "@types/chrome": "0.0.89",

        "@types/file-saver": "^2.0.1",

        "@types/hammerjs": "^2.0.36",

        "angular-fusioncharts": "^4.0.0",

        "assert": "^2.0.0",

        "cordova-browser": "6.0.0",

        "core-js": "^2.5.4",

        "date-fns": "^2.28.0",

        "dom-to-image": "^2.6.0",

        "exceljs": "^1.12.0",

        "file-saver": "^2.0.2",

        "fusioncharts": "^3.15.0-sr.1",

        "hammerjs": "^2.0.8",

        "html2canvas": "^1.0.0-rc.5",

        "idb-keyval": "^3.2.0",

        "ionic-input-mask": "^1.0.1",

        "ionic-selectable": "^4.9.0",

        "keyword-highlighter": "^1.0.6",

        "ng-starrating": "^1.0.20",

        "ng2-datepicker": "^3.1.1",

        "ngx-cookie-service": "^11.0.2",

        "ngx-device-detector": "^1.3.19",

        "ngx-mask": "^15.0.2",

        "ngx-pagination": "^5.0.0",

        "ngx-perfect-scrollbar": "^8.0.0",

        "rxjs": "^6.5.5",

        "rxjs-compat": "^6.5.5",

        "tslib": "^1.10.0",

        "util": "^0.12.4",

        "yup": "^0.32.11",

        "zone.js": "~0.11.4"

    },

    "devDependencies": {

        "@angular-builders/custom-webpack": "^8.2.0",

        "@angular-devkit/architect": "~0.1303.10",

        "@angular-devkit/build-angular": "~13.3.10",

        "@angular-devkit/core": "~13.3.10",

        "@angular-devkit/schematics": "~13.3.10",

        "@angular-eslint/builder": "13.5.0",

        "@angular-eslint/eslint-plugin": "13.5.0",

        "@angular-eslint/eslint-plugin-template": "13.5.0",

        "@angular-eslint/schematics": "^13.5.0",

        "@angular-eslint/template-parser": "13.5.0",

        "@angular/cli": "~13.3.10",

        "@angular/compiler-cli": "~13.3.12",

        "@angular/language-service": "~13.3.12",

        "@ionic/angular-toolkit": "^2.1.2",

        "@types/chrome": "0.0.89",

        "@types/jasmine": "~3.3.8",

        "@types/jasminewd2": "~2.0.3",

        "@types/node": "^12.20.54",

        "@types/underscore": "^1.9.3",

        "@typescript-eslint/eslint-plugin": "5.27.1",

        "@typescript-eslint/parser": "5.27.1",

        "cordova-plugin-device": "^2.0.2",

        "cordova-plugin-ionic-keyboard": "^2.2.0",

        "cordova-plugin-ionic-webview": "^4.1.3",

        "cordova-plugin-splashscreen": "^5.0.2",

        "cordova-plugin-statusbar": "^2.4.2",

        "cordova-plugin-whitelist": "^1.3.3",

        "eslint": "^8.17.0",

        "husky": "^8.0.0",

        "jasmine-core": "~3.4.0",

        "jasmine-spec-reporter": "~4.2.1",

        "karma": "^6.3.6",

        "karma-chrome-launcher": "~2.2.0",

        "karma-coverage-istanbul-reporter": "~2.0.1",

        "karma-jasmine": "~2.0.1",

        "karma-jasmine-html-reporter": "^1.4.0",

        "lint-staged": "^13.1.2",

        "prettier": "^2.8.4",

        "protractor": "^7.0.0",

        "puppeteer": "^11.0.0",

        "stylelint": "^15.2.0",

        "stylelint-config-standard": "^30.0.1",

        "stylelint-config-standard-scss": "^7.0.1",

        "ts-node": "~7.0.0",

        "typescript": "~4.6.4",

        "webpack": "^5.75.0",

        "webpack-dev-server": "^4.11.1",

        "webpack-extension-reloader": "^1.1.1"

    },

    "description": "An Ionic project",

    "cordova": {

        "plugins": {

            "cordova-plugin-whitelist": {},

            "cordova-plugin-statusbar": {},

            "cordova-plugin-device": {},

            "cordova-plugin-splashscreen": {},

            "cordova-plugin-ionic-webview": {},

            "cordova-plugin-ionic-keyboard": {}

        },

        "platforms": [

            "browser"

        ]

    },

    "browser": {

        "fs": false,

        "path": false,

        "os": false

    },

    "resolve": {

        "alias": {

            "process": "process/browser"

        }

    },

    "lint-staged": {

        "src/**/*.{js,ts,html,css,scss,json}": "prettier --write --ignore-unknown",

        "src/**/*.{js,ts}": "eslint --fix",

        "src/**/*.{css,scss}": "stylelint --fix"

    }

}

Steps to reproduce
Make a commit with husky pre-commit hook.
Debug Logs

expand to view

Environment

OS: macOS Ventura
Node.js: v16.19.0
lint-staged: 13.1.2

Downgrading to 12.5.0 didn't resolve my issue, plus it doesn't let me commit whether it's through GitHub desktop or the CLI. Running npx lint-staged with the --debug flag seems to show that the issue is with parsing my package.json, but I don't see what's wrong with it.

Would version 13.2.1 work any better?


setFillColor() not working

setFillColor() and setFillColorResource() have no effect at all. Nothing happens when using these.
Either in xml or java.
PS: I have worked it around by making borderWidth 100 when I want to fill a color, so it fills with the color. But would still like to get fillColor working.

What are you trying to achieve? fillColor is only used as a background for a drawable with transparent areas. If you just want to have a solid color fill the circle you can use a ColorDrawable as source for the CircleImageView.

Filling circleImageView with a solid color like this would fill the whole square aroudn it. Isn't that the problem setFillColor() solves? I just want to color my circle. That's all.

And I want set image transparent. I was trying to set transparent with setFillColor() but no luck. I think method name is not correct.

As I said, fillColor is only used as a background for a drawable with transparent areas - I agree that the naming could be better.
To just fill the circle with a solid color do one of the following:
<de.hdodenhof.circleimageview.CircleImageView
    android:layout_width="128dp"
    android:layout_height="128dp"
    android:src="@color/foobar"/>

or in code:
CircleImageView civ = ...
civ.setImageResource(R.color.foobar);

I also find that it have no effect,when I find the color like this
http://stackoverflow.com/questions/9114587/how-can-i-save-colors-in-array-xml-and-get-its-back-to-color-array
CircleImageView civ = ...
civ.setImageResource(colors[i]);

@gushoubang colors[0] probably isn't a resource - look for Resources$NotFoundException in your logcat. Use civ.setImageDrawable(new ColorDrawable(rainbow[0])); instead.


fix for https://github.com/chef/chef/issues/4689

rework the set_members method so duplicates are avoided ( #4689)

:+1:

we could wrap the things we're expecting to be arrays in Array(), but I think this is ok :+1:

:+1:

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
GitHub Users Who Are Not Authorized To Contribute
The following GitHub users do not appear to have signed a CLA:

@mawinter69

Please sign the CLA here.

Hi. Your friendly Curry bot here. Just letting you know that all commit authors have become authorized to contribute. I have added the "Signed CLA" label to this issue so it can easily be found in the future.


Add getBalance() to WebLN

Feature description
webln.getBalance() should return the current balance in sats.
Describe the solution
Extension

[ ] Add to webln
[ ] Create a new permission to read the account balance

Others

[ ] Add docs to webln.guide
[ ] Create typings in webln typescript package

Describe alternatives
No response
Additional context
No response
Are you working on this?
None

WebLN when there is a function to read the balance? Or is there a function to read the balance but the units are not what people want?
Is this method in the webln standard?
@reneaaron

WebLN when there is a function to read the balance? Or is there a function to read the balance but the units are not what people want?

The format needs to be decided on. I currently think a response like this would make sense:
{
  balance: 123
}

Where the balance is returned in sats.

Is this method in the webln standard?

Not yet.


support classification schemes

Hi folks, thanks for all your work on this; lonboard has been lovely! I'm curious if there is interest in supporting commonly-used map classification schemes (a-la the scheme argument in geopandas's plot function) under the hood (particularly in the viz API)? We just added a small function in mapclassify that makes it much easier to grab a color set from matplotlib than the one geopandas is using manually at the moment
From a users' perspective, it would be sweet if viz had parity with geopandas's explore, though of course, it's also easy to just pass the colors in manually, so no worries if it's not in scope :)

👋 I've wanted to explore better integration with mapclassify for a while (https://github.com/developmentseed/lonboard/issues/136). In general I'm working to minimize Lonboard's (required) dependencies (e.g. https://github.com/developmentseed/lonboard/pull/472 and https://github.com/developmentseed/lonboard/pull/582).
It would definitely be good to have an example of how to use with mapclassify. It might be in scope to make mapclassify an optional dependency so that viz can be closer to parity with explore, and to raise an ImportError if mapclassify isn't installed and the user wants to use a classification scheme. I don't think I want to add mapclassify as a hard dependency though.

sweet (sorry, missed that issue, can close this in its favor); makes perfect sense to me and would be exactly how geopandas treats it (def don't want a hard dependency).
(FWIW, longraph is fun with other parts of pysal too :)

Longraph looks really cool!
I'm not very familiar with mapclassify or classification schemes in general, so if you ever get the itch, an example notebook here using mapclassify would be welcomed 🙂

yep, happy to  (thanks! props to you, really. Lonboard does the heavy lifting; good docs count)
there's a short example with lonboard in cell 8 but will throw a more detailed on together quickly

though it occurs to me there's also the long-winded version on classification scheme with mapclassify here and here, fwiw

I figure a minimal example notebook is fine that then links to those in-depth resources. It's good to have the visibility that the libraries work together, and then the user can dig into mapclassify to figure out exactly what they want.


Add paranoid verfication config for devise_security.rb

WHAT

Add paranoid verfication config for devise_security.rb

WHY

because there was no description about paranoid_code_regenerate_after_attempt in devise_security.rb.

ATTENTION

This is my first time to make a pull request, so I would appreciate it if you could point out any missing items.

Coverage remained the same at 97.927% when pulling 37d6662b23a06def1831fd0655b3135baa9ece0f on kossy0701:add_paranoid_verification_config into a2856daef0dd46ebc0333baa96974fbbb0095d2c on devise-security:master.