text:
Android 14 Permission related crash

I already have the following permissions declared in my manifest but it still throws an error and crashes.
Flutter version - 3.19.3
Plugin Version - 6.1.3
<uses-permission android:name="android.permission.CAPTURE_VIDEO_OUTPUT" />
<uses-permission android:name="android.permission.CAPTURE_AUDIO_OUTPUT" />
<uses-permission android:name="android.permission.FOREGROUND_SERVICE" />
<uses-permission android:name="android.permission.FOREGROUND_SERVICE_MEDIA_PLAYBACK" />
<uses-permission android:name="android.permission.FOREGROUND_SERVICE_MICROPHONE" />
<uses-permission android:name="android.permission.FOREGROUND_SERVICE_CAMERA" />
<uses-permission android:name="android.permission.FOREGROUND_SERVICE_MEDIA_PROJECTION" />

<service
    android:name="com.pravera.flutter_foreground_task.service.ForegroundService"
    android:foregroundServiceType="mediaPlayback|camera|microphone|mediaProjection"
    android:stopWithTask="true"/>

java.lang.RuntimeException: Unable to create service com.pravera.flutter_foreground_task.service.ForegroundService: java.lang.SecurityException: Starting FGS with type mediaProjection callerApp=ProcessRecord{73ae391 7353:com.sprintstudio.conversations/u0a190} targetSDK=34 requires permissions: all of the permissions allOf=true [android.permission.FOREGROUND_SERVICE_MEDIA_PROJECTION] any of the permissions allOf=false [android.permission.CAPTURE_VIDEO_OUTPUT, android:project_media]

I am using other permissions, but they need to be not only in the manifest, but explicitly asked to the user (with permission_handler pluggin for exemple).
Maybe this is the same for you ? Have you tried to ask them to the user ?

Yes, I am asking the relevant permissions.
I'm also asking for these permissions which are required for foreground task to work
await FlutterForegroundTask.requestIgnoreBatteryOptimization();
await FlutterForegroundTask.requestNotificationPermission();

Hey @bhavinb98, i am getting the same issue. Are you able to solve the issue ?

@ishabodiwala no, not yet

this may help

Have tried it already. It's not working.

@ishabodiwala Possible solution for your issue


text:
Transfer Test Utils

Transfer单元测试（除tooltips外）

@ForeseeBear Commit记录有问题，建议从dev拉新分支进行提交

@ForeseeBear 记得给Commit加下签名哦~

@all-contributors please add @ForeseeBear for code

@ForeseeBear 请回复下检视意见，并解决下冲突~

@ForeseeBear   这个pr太久没有处理检视意见和冲突，我先关闭，建议后续重新提交PR~

source: gharchive/pull-request

authors: ForeseeBear kagol

repo: DevCloudFE/vue-devui

license: MIT

license_type: permissive

license_source: github-api


text:
fix: replace axios with fetch

Changes

replace axios with fetch after upgrading broke the extension

#288  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jsalaber and the rest of your teammates on  Graphite

repo: DevCycleHQ/vscode-extension


text:
Add Preview mode to HtmlEditorExtender

See #97 for details.

Hello,
I got the CI build in order to get the latest fixes. I got this fix and it worked fine initially. But during testing, I see an issue/bug in the following scenario:
Add the data in htmlEditor in Edit mode. Then click on Preview mode to preview the changes you made. Then go back to Edit mode again, the text/update you made is gone. If you save the form, the htmlEditor value is empty. So basically we lose the change when switching between Edit mode and Preview mode.Can you please confirm ?
Thanks.

source: gharchive/issue

repo: DevExpress/AjaxControlToolkit

license_source: bigquery


text:
Properly disable resize hack in server tests (closes #719)

\cc @inikulin

@testcafe-build-bot \retest

lgtm

authors: AndreyBelym georgiy-abbasov inikulin

repo: DevExpress/testcafe

license: mit


text:
Update file on Unused Image clean-up in Domain 6

File changed: Identify_the_steps_you_would_take_to_clean_up_unused_images_on_a_filesystem_also_on_DTR.md
Add the official instructions on cleaning unused filesystem images.

@arush-sal Thanks for looking up the last missing link topic.
In the rest of the guide we always use "Official Docker Documentation" as the sub heading for providing links to the Docker documentation. Also we use the page name of the linked page - in this case  "Prune unused Docker objects" as the link title. Can you please adjust this to keep it consistent with the rest of the guide? Thanks.

@Govinda-Fichtner Thank you for the explanation, I have fixed it. It should be good to go.
p.s: I tried to search around but wasn't able to find the solution to unused image clean up in DTR

authors: Govinda-Fichtner arush-sal

repo: DevOps-Academy-Org/dca-prep-guide


text:
Added POPO Flags in io Package

Description
Added the # POPO Update comment flag within the io package which contains the parsing functionality for AaC.
Linked Items:
Closes #752
Added

POPO flagging comment within the io Package.

Checklist:

[x] I updated project documentation to reflect my changes.

No documentation to update

[ ] My changes generate no new warnings.
[x] I updated new and existing unit tests to account for my changes.

No tests to update

[x] I linked the associated item(s) to be closed.
[x] I bumped the version.

Not bumping version since just adding comments

[x] I added the labels corresponding to my changes.

Believe the heaviest changes will be within the _yaml and _parse_source files since _yaml is where the initial ingest of the yaml files takes place to begin parsing into the dictionary structures to be worked with. Then the conversion into AaC's understanding of a Definition object takes place within _parse_source if I am following/understanding things correctly. So, these two pieces will have more than just a change of data object to work with which is what we have to date been flagging elsewhere, but should be where the handling for translating to the new data object takes place, I believe.

repo: DevOps-MBSE/AaC


text:
🛑 Wiki is down

In 970539c, Wiki (https://wiki.dtdhomelab.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wiki is back up in a017423 after 8 minutes.

repo: DevanTheDude/DTDHomelab


text:
'RangeError: Maximum call stack size exceeded' when I try to run Zenbot on Binance.

System information

Have I written custom code (as opposed to using zenbot vanilla): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 17.04
Zenbot version: v4.10
NodeJS version: v8.9.4
Python version: v2.7.14
Exact command to reproduce:  ./zenbot.sh trade --paper

Describe the problem
I'm getting a RangeError: Maximum call stack size exceeded when I try to run Zenbot on Binance.
After a fresh install I try to run Zenbot on Binance, with one of their pairs, for example BTC-USDT. The only thing I changed in the conf.js. was c.selector = 'binance.BTC-USDT'
Source code / logs
I keep getting the following errors, after the bot runs for a bit:
2018-02-07 10:14:00  7788.19 BTC-USDT                95                               0.00000 BTC  1000.00000000 USDT   +0.00%   -1.67%
2018-02-07 10:16:00  7804.00 BTC-USDT   +0.20%       56                               0.00000 BTC  1000.00000000 USDT   +0.00%   -1.87%
2018-02-07 10:18:00  7847.98 BTC-USDT   +0.56%      125                               0.00000 BTC  1000.00000000 USDT   +0.00%   -2.42%
2018-02-07 10:20:00  7871.51 BTC-USDT   +0.29%      102                               0.00000 BTC  1000.00000000 USDT   +0.00%   -2.71%
2018-02-07 10:22:00  7848.02 BTC-USDT   -0.30%      116                               0.00000 BTC  1000.00000000 USDT   +0.00%   -2.42%
2018-02-07 10:24:00  7835.99 BTC-USDT   -0.16%       68                               0.00000 BTC  1000.00000000 USDT   +0.00%   -2.27%
2018-02-07 10:26:00  7871.41 BTC-USDT   +0.45%      131                               0.00000 BTC  1000.00000000 USDT   +0.00%   -2.71%
2018-02-07 10:28:00  7890.00 BTC-USDT   +0.23%       66                               0.00000 BTC  1000.00000000 USDT   +0.00%   -2.94%
2018-02-07 10:30:00  7935.13 BTC-USDT   +0.57%      172                               0.00000 BTC  1000.00000000 USDT   +0.00%   -3.49%
2018-02-07 10:32:00  7867.74 BTC-USDT   -0.85%      104                               0.00000 BTC  1000.00000000 USDT   +0.00%   -2.66%
2018-02-07 10:34:00  7864.15 BTC-USDT   -0.05%       99                               0.00000 BTC  1000.00000000 USDT   +0.00%   -2.62%
2018-02-07 10:36:00  7920.11 BTC-USDT   +0.71%       90                               0.00000 BTC  1000.00000000 USDT   +0.00%   -3.30%
2018-02-07 10:38:00  7941.98 BTC-USDT   +0.27%       62                               0.00000 BTC  1000.00000000 USDT   +0.00%   -3.57%
2018-02-07 10:40:00  7968.92 BTC-USDT   +0.33%      147                               0.00000 BTC  1000.00000000 USDT   +0.00%   -3.90%
2018-02-07 10:42:00  7929.66 BTC-USDT   -0.50%       93   --- 27.05                      0.00000 BTC  1000.00000000 USDT   +0.00%   -3.42%
2018-02-07 10:44:00  7880.00 BTC-USDT   -0.63%      110  ---- 23.81                      0.00000 BTC  1000.00000000 USDT   +0.00%   -2.81%
2018-02-07 10:46:00  7853.94 BTC-USDT   -0.34%      116  ---- 22.31                      0.00000 BTC  1000.00000000 USDT   +0.00%   -2.49%
2018-02-07 10:48:00  7900.20 BTC-USDT   +0.58%       70   --- 30.69                      0.00000 BTC  1000.00000000 USDT   +0.00%   -3.06%
2018-02-07 10:50:00  7905.17 BTC-USDT   +0.06%       50   --- 31.55                      0.00000 BTC  1000.00000000 USDT   +0.00%   -3.12%
2018-02-07 10:52:00  7892.20 BTC-USDT   -0.17%       62   --- 30.49                      0.00000 BTC  1000.00000000 USDT   +0.00%   -2.96%
2018-02-07 10:54:00  7965.31 BTC-USDT   +0.92%      118    -- 42.24                      0.00000 BTC  1000.00000000 USDT   +0.00%   -3.85%
2018-02-07 10:56:00  7977.47 BTC-USDT   +0.15%       68    -- 43.94                      0.00000 BTC  1000.00000000 USDT   +0.00%   -4.00%
2018-02-07 10:58:00  7956.87 BTC-USDT   -0.26%       79    -- 41.70                      0.00000 BTC  1000.00000000 USDT   +0.00%   -3.75%
2018-02-07 11:00:00  7962.89 BTC-USDT   +0.07%       61    -- 42.62                      0.00000 BTC  1000.00000000 USDT   +0.00%   -3.82%
2018-02-07 11:02:00  7955.03 BTC-USDT   -0.10%       30    -- 41.70                      0.00000 BTC  1000.00000000 USDT   +0.00%   -3.73%
2018-02-07 11:04:00  7919.91 BTC-USDT   -0.45%       91    -- 37.76                      0.00000 BTC  1000.00000000 USDT   +0.00%   -3.30%
2018-02-07 11:06:00  7922.00 BTC-USDT   +0.02%       82    -- 38.13                      0.00000 BTC  1000.00000000 USDT   +0.00%   -3.33%
2018-02-07 11:08:00  7911.21 BTC-USDT   -0.14%       45    -- 36.90     0.0105      buy  0.00000 BTC  1000.00000000 USDT   +0.00%   -3.20%
2018-02-07 11:10:00  7919.00 BTC-USDT   +0.09%       56    -- 38.45     0.0170   0.0023           0.00000 BTC  1000.00000000 USDT   +0.00%   -3.29%
2018-02-07 11:11:59  7923.03 BTC-USDT   +0.05%       24    -- 39.28     0.0195   0.0030           0.00000 BTC  1000.00000000 USDT   +0.00%   -3.34%
An error occurred RangeError: Maximum call stack size exceeded
    at each (/home/user/zenbot/node_modules/run-series/index.js:14:17)
    at Array.<anonymous> (/home/user/zenbot/lib/engine.js:858:20)
    at each (/home/user/zenbot/node_modules/run-series/index.js:17:24)
    at Array.<anonymous> (/home/user/zenbot/lib/engine.js:858:20)
    at each (/home/user/zenbot/node_modules/run-series/index.js:17:24)
    at Array.<anonymous> (/home/user/zenbot/lib/engine.js:858:20)
    at each (/home/user/zenbot/node_modules/run-series/index.js:17:24)
    at Array.<anonymous> (/home/user/zenbot/lib/engine.js:858:20)
    at each (/home/user/zenbot/node_modules/run-series/index.js:17:24)
    at Array.<anonymous> (/home/user/zenbot/lib/engine.js:858:20)
An error occurred RangeError: Maximum call stack size exceeded
    at each (/home/user/zenbot/node_modules/run-series/index.js:14:17)
    at Array.<anonymous> (/home/user/zenbot/lib/engine.js:858:20)
    at each (/home/user/zenbot/node_modules/run-series/index.js:17:24)
    at Array.<anonymous> (/home/user/zenbot/lib/engine.js:858:20)
    at each (/home/user/zenbot/node_modules/run-series/index.js:17:24)
    at Array.<anonymous> (/home/user/zenbot/lib/engine.js:858:20)
    at each (/home/user/zenbot/node_modules/run-series/index.js:17:24)
    at Array.<anonymous> (/home/user/zenbot/lib/engine.js:858:20)
    at each (/home/user/zenbot/node_modules/run-series/index.js:17:24)
    at Array.<anonymous> (/home/user/zenbot/lib/engine.js:858:20)
...

RangeError: Maximum call stack size exceeded

This looks like a problem in trades.map
I suppose the bot doesn't crash but keeps spitting the error over and over again?
How large is your trades object (check the API object at http://b.o.t.ip/trades)?

I'm actually not able to connect to the web UI. Should I set the IP of the web server where Zenbot is running in the conf.js (ie. 192.168.1.139)?

The endpoint is exposed on start.
Web UI running on http://...
By default the API listens on all available IPv4 interfaces on a random port above 20000

Same issue here. The trades array length at http://b.o.t.ip/trades is 14387.

14387

Thats not a crazy lot.
I have a PR open which fixes a possible problem with dublicating trades getting added to s.trades: https://github.com/DeviaVir/zenbot/pull/1240/commits/439a024c05284e1a671019a4b4e55fd0f45fa2c0

I found these changes between a working exchange.js and the latest updated exchange.js.

This is still a bug today. I can't do any trades on Binance now.

There is a chance that this could be alleviated by #1324 as it doesn't use the run-series loop anymore.

authors: brucetus defkev glennfu klahaeck krystophv reynard80

repo: DeviaVir/zenbot


text:
🛑 Semantic Search Dev is down

In bae14d0, Semantic Search Dev (https://semantic-dev.devkraft.in/api/v1/health) was down:

HTTP code: 502
Response time: 747 ms

Resolved: Semantic Search Dev is back up in ea9a526 after 10 minutes.

repo: DevkraftTechnologies/upptime


text:
Feature/updated UI

Created a donate_message component under st_helpers.py

Added donate_message component to all pages

Moved Player table from Home to new page 'All Players'

Added xGI/GI scatter chart to the home page

I've created a "dev" branch of the repo, that will allow us to first test our changes using this app:
https://fantasy-premier-league-dev.streamlit.app/

authors: James-Leslie steinarkarlsson

repo: Devonquendi/fpl-app


text:
Forgot brazil region : ^)

After looking at my production logs I've noticed that i forgot to add brazil region to the thirds preset.

smh poor brazil

wait did you lint this

yes : ^)

authors: AndyTempel Devoxin


text:
Grafico de linhas - Dashboard

Grafico de linhas - Retrabalho (dado: Quantidade)

Front e
Rota no back-end.

Entregue!

repo: DevsDomain/D-Traker


text:
OBB

Make sure to merge master after I merge armageddon

repo: Devsh-Graphics-Programming/Nabla


text:
geological timescale ontology

There is an ontology for the geological timescale here https://github.com/CGI-IUGS/timescale-ont and a dataset representing the international chronostratigraphic chart nearby https://github.com/CGI-IUGS/timescale-data
The International Commission on Stratigraphy are planning to adopt this as the point-of-truth for the standard geological timescale.
related also: proposed Darwin Core Vocabulary Enhancement - ChronometricAge: https://github.com/tdwg/chrono/issues/15

Just confirming that indeed the International Commission on Stratigraphy are indeed planning on adopting this Geo Time Scale dataset and, in future, producing all Charts from it as automated reports.
This will take a while but we should get an English-only chart generated in the first quarter of 2021. Regards Nick (who is now Webmaster of the ICS)

tdwg/chrono is targeted for reporting numeric temporal coordinate locations; the Geologic time scale reports ages using time ordinal eras-- named intervals anchored in the rock record via GSSP.  The numeric temporal coordinates of the boundaries of those intervals are updated as new data become available.

we have incorporated Chronometric age in our new data model (see: https://github.com/DiSSCo/openDS/blob/master/data-model/fdo-type/digital-specimen/0.3.0/schema/chronometric-age.json)

authors: nicholascar sharifX smrgeoinfo wouteraddink

repo: DiSSCo/openDS


text:
Cannot build project when swiftlint 0.43.0+ is installed

Hi,
We're currently integrating pact-consumer-swift via Carthage. Recently we've noticed that this has started to fail to build via Carthage, or indeed via Xcode directly. We're getting a build error during the Swiftlint build phase:
Linting Swift files in current working directory
Error: No lintable files found at paths: ''

Looking at the swiftlint changelog (https://github.com/realm/SwiftLint/releases) for 0.43.0 shows a change was made related to paths inside configuration files:

Configuration files now consistently have their included/excluded
relative file paths applied relative to their location in the file
system. Previously the root configuration file applied these relative
to the current working directory, but nested configurations applied
these to their location in the file system.

Because the swiftlint configuration file resides within Configuration, the included directory of - Sources/ is being interpreted as ./Configuration/Sources/ rather than ./Sources/, so is unable to lint anything and fails the build. This can be validated by prefixing paths in included and excluded with ../ which then lints all the expected files and builds successfully.
A few different fixes here, but possibly moving the configuration back to .swiftlint.yml in the root of the directory is the easiest one that maintains backwards compatibility with the older versions of Swiftlint?

Thanks for raising this.
Personally I have nothing against moving it back to root of this project. Especially when it's (still) the only file in /Configuration folder. Will need an update of a swiftlint sh script. PRs welcome 👍

Closed with #121

authors: sebskuse surpher

repo: DiUS/pact-consumer-swift


text:
Rotation scans get an extra _1 on the end of the filename

It looks like Hyperion is adding the run_number on to the rotation scan twice i.e. see data in /dls/i03/data/2024/cm37235-2/TestInsulin/ins_9 where we get ins_9_8_1.nxs. Here the 8 is the runnumber appended by GDA and passed into Hyperion and the _1 is Hyperion adding another run number on. This is probably best fixed by just not including the run number when GDA gives the filename to Hyperion
Acceptance Criteria

Rotation scans do not have the additional _1

I believe this was being caused by the GDA line which gets the prefix for hyperion's rotation parameters:
prefix = extended_request.getDnaFilePrefix()[:-1]
In Hyperion's debug logs, the prefix from this line included the underscore + runnumber from the previous hyperion FGS. Then, the Hyperion line
@property
 def full_filename(self):
     return f"{self.prefix}_{self.run_number}"

Would add on another underscore run-number.

See solution at https://gerrit.diamond.ac.uk/c/gda/gda-mx/+/41720/1. To test, cherry pick this change onto i03-live and test on a beamline (doesn't require beam)

Deployed GDA change on i03_live and it appeared to fix issue

authors: DominicOram olliesilvester

repo: DiamondLightSource/hyperion


text:
Inconsistent JSON.STRAPPEND: The return type of JSON.STRAPPEND should be integer but it is returning string

Steps to reproduce

JSON.SET doc $ '{"a":"foo", "nested": {"a": "hello"}, "nested2": {"a": 31}}'
JSON.STRAPPEND doc $..a '"baz"'

Expected output

The expected output when the above set of commands when run on Redis
Observed output

The observed output when the above set of commands when run on DiceDB
The steps to run the test cases are mentioned in the README of the dice-tests repository.
Expectations for resolution
This issue will be considered resolved when the following things are done

changes in the dice code to meet the expected behavior
Successful run of the tcl test behavior

You can find the tests under the tests directory of the dice repository and the steps to run are in the README file. Refer to the following links to set up DiceDB and Redis 7.2.5 locally

setup DiceDB locally
setup Redis 7.2.5 locally
setup DiceDB CLI

@JyotinderSingh @lucifercr07 I would like to work on this issue, pls assign it to me
thanks

@shashi-sah2003 Can you tag me here when you solve this issue? Because I was really frustrated no matter how much time I spend on this issue. Please have a look at this comment in this issue, This user says that the output is coming correctly in MacOS, but in windows, it is coming differently
https://github.com/DiceDB/dice/pull/976#issuecomment-2395457327

@shashi-sah2003 Can you tag me here when you solve this issue? Because I was really frustrated no matter how much time I spend on this issue when I was working on JSON.ARRLEN. Please have a look at this comment in this issue, This user says that the output is coming correctly in MacOS, but in windows, it is coming differently
https://github.com/DiceDB/dice/pull/976#issuecomment-2395457327

Hey @surya0180 , did you verify if this is Windows specific issue?

@shashi-sah2003 Can you tag me here when you solve this issue? Because I was really frustrated no matter how much time I spend on this issue when I was working on JSON.ARRLEN. Please have a look at this comment in this issue, This user says that the output is coming correctly in MacOS, but in windows, it is coming differently
#976 (comment)

Hey @surya0180 , did you verify if this is Windows specific issue?

@iamskp11 From people I know who are using windows, all are facing the same issue. Though I did not check with people who is mac in particular, I still think its something related to the terminal in an OS

@surya0180 I am going to work on this issue today. btw have you confirmed if this issue is only windows specific?

@JyotinderSingh @lucifercr07 can you guys pls look at this issue as I can see in this function integer type is being appended in the resultArray but it's returning this https://github.com/DiceDB/dice/issues/1108#issue-2590724286
func evalJSONSTRAPPEND(args []string, store *dstore.Store) []byte {
	if len(args) != 3 {
		return diceerrors.NewErrArity("JSON.STRAPPEND")
	}

	key := args[0]
	path := args[1]
	value := args[2]

	obj := store.Get(key)
	if obj == nil {
		return diceerrors.NewErrWithMessage(diceerrors.NoKeyExistsErr)
	}

	errWithMessage := object.AssertTypeAndEncoding(obj.TypeEncoding, object.ObjTypeJSON, object.ObjEncodingJSON)
	if errWithMessage != nil {
		return diceerrors.NewErrWithFormattedMessage(diceerrors.WrongKeyTypeErr)
	}

	jsonData := obj.Value

	var resultsArray []interface{}

	if path == "$" {
		// Handle root-level string
		if str, ok := jsonData.(string); ok {
			unquotedValue := strings.Trim(value, "\"")
			newValue := str + unquotedValue
			resultsArray = append(resultsArray, int64(len(newValue)))
			jsonData = newValue
		} else {
			return clientio.RespEmptyArray
		}
	} else {
		expr, err := jp.ParseString(path)
		if err != nil {
			return clientio.RespEmptyArray
		}

		_, modifyErr := expr.Modify(jsonData, func(data any) (interface{}, bool) {
			switch v := data.(type) {
			case string:
				unquotedValue := strings.Trim(value, "\"")
				newValue := v + unquotedValue
				resultsArray = append([]interface{}{int64(len(newValue))}, resultsArray...)
				return newValue, true
			default:
				resultsArray = append([]interface{}{clientio.RespNIL}, resultsArray...)
				return data, false
			}
		})

		if modifyErr != nil {
			return clientio.RespEmptyArray
		}
	}

	if len(resultsArray) == 0 {
		return clientio.RespEmptyArray
	}

	obj.Value = jsonData
	return clientio.Encode(resultsArray, false)
}

@JyotinderSingh @lucifercr07 can you guys pls look at this issue as I can see in this function integer type is being appended in the resultArray but it's returning this #1108 (comment)
func evalJSONSTRAPPEND(args []string, store *dstore.Store) []byte {
	if len(args) != 3 {
		return diceerrors.NewErrArity("JSON.STRAPPEND")
	}

	key := args[0]
	path := args[1]
	value := args[2]

	obj := store.Get(key)
	if obj == nil {
		return diceerrors.NewErrWithMessage(diceerrors.NoKeyExistsErr)
	}

	errWithMessage := object.AssertTypeAndEncoding(obj.TypeEncoding, object.ObjTypeJSON, object.ObjEncodingJSON)
	if errWithMessage != nil {
		return diceerrors.NewErrWithFormattedMessage(diceerrors.WrongKeyTypeErr)
	}

	jsonData := obj.Value

	var resultsArray []interface{}

	if path == "$" {
		// Handle root-level string
		if str, ok := jsonData.(string); ok {
			unquotedValue := strings.Trim(value, "\"")
			newValue := str + unquotedValue
			resultsArray = append(resultsArray, int64(len(newValue)))
			jsonData = newValue
		} else {
			return clientio.RespEmptyArray
		}
	} else {
		expr, err := jp.ParseString(path)
		if err != nil {
			return clientio.RespEmptyArray
		}

		_, modifyErr := expr.Modify(jsonData, func(data any) (interface{}, bool) {
			switch v := data.(type) {
			case string:
				unquotedValue := strings.Trim(value, "\"")
				newValue := v + unquotedValue
				resultsArray = append([]interface{}{int64(len(newValue))}, resultsArray...)
				return newValue, true
			default:
				resultsArray = append([]interface{}{clientio.RespNIL}, resultsArray...)
				return data, false
			}
		})

		if modifyErr != nil {
			return clientio.RespEmptyArray
		}
	}

	if len(resultsArray) == 0 {
		return clientio.RespEmptyArray
	}

	obj.Value = jsonData
	return clientio.Encode(resultsArray, false)
}

My guess here is that we may be encoding it the wrong way, the best way to debug this is to attach a debugger.

I just tried this on my local (with both async and resp servers) and I am unable to reproduce the issue
> redis-cli -p 7379
127.0.0.1:7379> JSON.SET doc $ '{"a":"foo", "nested": {"a": "hello"}, "nested2": {"a": 31}}'
OK
127.0.0.1:7379> JSON.STRAPPEND doc $..a '"baz"'
1) (integer) 6
2) (integer) 8
3) (nil)
127.0.0.1:7379>

@JyotinderSingh I tried your method of accessing dicedb server using redis-cli, it's working correctly as you have shown above but while accessing it through dicedb-cli it's producing the issue that I have mentioned above.

Is this some kind of bug with dicedb-cli?

@JyotinderSingh I tried your method of accessing dicedb server using redis-cli, it's working correctly as you have shown above but while accessing it through dicedb-cli it's producing the issue that I have mentioned above.

Is this some kind of bug with dicedb-cli?

It might be a bug with the CLI. We'll need to look into it a little deeper.

@JyotinderSingh as this is related to bug with the CLI, should I close this issue?

repo: DiceDB/dice


text:
docs: Update PERSIST command documentation (#774)

fixes #774
I have updated the documentation of PERSIST command

No we don't need comment
I will make the changes

@lucifercr07 I have removed the comment
pls check


text:
unworkable with default arguments setting

    // Add arguments to the executed fix command, like so: ['--level=psr2', '--fixers=linefeed,short_tag,indentation'].
    "phpformatter.arguments": [
        "--level=psr2"
    ],

Console

The "--level" option does not exist.

PHP CS Fixer recently released an update. The --level argument has been renamed to --rules. More details can be found here.

Closed this because there has been no response and I believe this should be the proper fix.

authors: Dickurt Ult-UX

repo: Dickurt/vscode-php-formatter


text:
sideComments:  element attribute in the blog editor data-section-id="1" for all

I'm seeing the same comments appear for each paragraph I write on the blog post, using the sideComments feature.

Fixed in #170

authors: coopermaruyama cosmicBboy

repo: Differential/meteor-blog


text:
Organization logo

Closes #43

Wrong branch, closing..

repo: Digipalvelutehdas/APIKA


text:
Add keyboard shortcut to start/stop drawing annotation

Pressing n will

Open the New Annotation dialog if no annotations are selected
Put the user into or cancel "draw mode" for the current annotation if one is selected

Fixes in part #145

@manthey coverage is failing - do you usually have tests for things like keyboard shortcuts?

This starts drawing a line.  Were you thinking of adding additional keyboard bindings for the other shapes?  Or should we have a concept of a recent shape and choose that?  And, if so, then we might want another key to cycle through the shapes.

We do test some keyboard shortcuts (e.g., https://github.com/DigitalSlideArchive/HistomicsUI/blob/master/tests/web_client_specs/annotationSpec.js#L327).

This starts drawing a line. Were you thinking of adding additional keyboard bindings for the other shapes? Or should we have a concept of a recent shape and choose that? And, if so, then we might want another key to cycle through the shapes.

Additional keyboard bindings for each shape would be easiest to implement code-wise and UX-wise, I think. (just adding keyboard shortcuts to each of the shapes' tooltips seems easier than trying to communicate what the recent shape is to the user).

We do test some keyboard shortcuts (e.g., https://github.com/DigitalSlideArchive/HistomicsUI/blob/master/tests/web_client_specs/annotationSpec.js#L327).

Thanks, I'll take a look at those and write some tests for the new shortcuts.

I think using letters that are somehow associated with the shape will be more memorable than using the top right six letters (but I'm willing to be argued out of it).  Maybe:
o point
r rectangle
l ellipse
c circle
p polygon
n line

I think using letters that are somehow associated with the shape will be more memorable than using the top right six letters (but I'm willing to be argued out of it). Maybe: o point r rectangle l ellipse c circle p polygon n line

I don't have a strong preference, but I can see it being easier to remember if they are associated with a letter. I'll change it to those

I added tests for the new shortcuts. Looks like CI is happy with coverage now.

authors: manthey mvandenburgh

repo: DigitalSlideArchive/HistomicsUI


text:
🛑 ZL1OTD Repeater is down

In 97188d9, ZL1OTD Repeater (https://zl1otd.dvnz.nz) was down:

HTTP code: 502
Response time: 19142 ms

Resolved: ZL1OTD Repeater is back up in 6fc57e6.

repo: DigitalVoiceNZ/upptime


text:
🛑 data-crypto-event is down

In 6a060f3, data-crypto-event ($LAMBDA_MONIT_SERVER_URL?server=crypto_event) was down:

HTTP code: 502
Response time: 20119 ms

Resolved: data-crypto-event is back up in 99cb66b after 2 hours, 20 minutes.


text:
⚠ RPC server - Figment Solana has degraded performance

In 986df3c, RPC server - Figment Solana ($FIGMENT_SOLANA_RPC_URL) experienced degraded performance:

HTTP code: 429
Response time: 292 ms

Resolved: RPC server - Figment Solana performance has improved in dbad451.

repo: DimensionDev/status


text:
🛑 API - Alchemy EVM NFT is down

In fb8617e, API - Alchemy EVM NFT ($ALCHEMY_EVM_NFT_API_URL) was down:

HTTP code: 429
Response time: 179 ms

Resolved: API - Alchemy EVM NFT is back up in bf8d82f.