Error 111, connection refused

Hi,
I have an app running on Heroku and I am using Python 3.6 with Redis + Celery. Whenever, I connect to my app via socket and try to run some command (commands go to the celery tasks) I get this error that the connection refused:
{"message": "Error 111 connecting to ec2-54-158-35-36.compute-1.amazonaws.com:8029. ECONNREFUSED.", "asctime": "2018-12-02T12:56:52Z+0000", "name": "socket_routes", "processName": "MainProcess", "filename": "socket_routes.py", "funcName": "error_handler", "levelname": "ERROR", "lineno": 325, "module": "socket_routes", "threadName": "MainThread", "exc_info": "Traceback (most recent call last):\n  File \"/app/.heroku/python/lib/python3.6/site-packages/redis/connection.py\", line 484, in connect\n    sock = self._connect()\n  File \"/app/.heroku/python/lib/python3.6/site-packages/redis/connection.py\", line 541, in _connect\n    raise err\n  File \"/app/.heroku/python/lib/python3.6/site-packages/redis/connection.py\", line 529, in _connect\n    sock.connect(socket_address)\n  File \"/app/.heroku/python/lib/python3.6/site-packages/eventlet/greenio/base.py\", line 261, in connect\n    socket_checkerr(fd)\n  File \"/app/.heroku/python/lib/python3.6/site-packages/eventlet/greenio/base.py\", line 50, in socket_checkerr\n    raise socket.error(err, errno.errorcode[err])\nConnectionRefusedError: [Errno 111] ECONNREFUSED\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n  File \"/app/.heroku/python/lib/python3.6/site-packages/redis/client.py\", line 2408, in _execute\n    return command(*args)\n  File \"/app/.heroku/python/lib/python3.6/site-packages/redis/connection.py\", line 610, in send_command\n    self.send_packed_command(self.pack_command(*args))\n  File \"/app/.heroku/python/lib/python3.6/site-packages/redis/connection.py\", line 585, in send_packed_command\n    self.connect()\n  File \"/app/.heroku/python/lib/python3.6/site-packages/redis/connection.py\", line 489, in connect\n    raise ConnectionError(self._error_message(e))\nredis.exceptions.ConnectionError: Error 111 connecting to ec2-54-158-35-36.compute-1.amazonaws.com:8029. ECONNREFUSED.\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n  File \"/app/.heroku/python/lib/python3.6/site-packages/redis/connection.py\", line 484, in connect\n    sock = self._connect()\n  File \"/app/.heroku/python/lib/python3.6/site-packages/redis/connection.py\", line 541, in _connect\n    raise err\n  File \"/app/.heroku/python/lib/python3.6/site-packages/redis/connection.py\", line 529, in _connect\n    sock.connect(socket_address)\n  File \"/app/.heroku/python/lib/python3.6/site-packages/eventlet/greenio/base.py\", line 261, in connect\n    socket_checkerr(fd)\n  File \"/app/.heroku/python/lib/python3.6/site-packages/eventlet/greenio/base.py\", line 50, in socket_checkerr\n    raise socket.error(err, errno.errorcode[err])\nConnectionRefusedError: [Errno 111] ECONNREFUSED\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n  File \"/app/.heroku/python/lib/python3.6/site-packages/flask_socketio/__init__.py\", line 626, in _handle_event\n    ret = handler(*args)\n  File \"/app/socket_routes.py\", line 40, in inner\n    return f(wheelme_id, other_arg, **kwargs)\n  File \"/app/socket_routes.py\", line 292, in rotateDirection\n    rotate.delay(wheelme_id, change_in_direction_left_is_positive)\n  File \"/app/.heroku/python/lib/python3.6/site-packages/celery/app/task.py\", line 413, in delay\n    return self.apply_async(args, kwargs)\n  File \"/app/.heroku/python/lib/python3.6/site-packages/celery/app/task.py\", line 536, in apply_async\n    **options\n  File \"/app/.heroku/python/lib/python3.6/site-packages/celery/app/base.py\", line 736, in send_task\n    self.backend.on_task_call(P, task_id)\n  File \"/app/.heroku/python/lib/python3.6/site-packages/celery/backends/redis.py\", line 189, in on_task_call\n    self.result_consumer.consume_from(task_id)\n  File \"/app/.heroku/python/lib/python3.6/site-packages/celery/backends/redis.py\", line 75, in consume_from\n    return self.start(task_id)\n  File \"/app/.heroku/python/lib/python3.6/site-packages/celery/backends/redis.py\", line 57, in start\n    self._consume_from(initial_task_id)\n  File \"/app/.heroku/python/lib/python3.6/site-packages/celery/backends/redis.py\", line 82, in _consume_from\n    self._pubsub.subscribe(key)\n  File \"/app/.heroku/python/lib/python3.6/site-packages/redis/client.py\", line 2482, in subscribe\n    ret_val = self.execute_command('SUBSCRIBE', *iterkeys(new_channels))\n  File \"/app/.heroku/python/lib/python3.6/site-packages/redis/client.py\", line 2404, in execute_command\n    self._execute(connection, connection.send_command, *args)\n  File \"/app/.heroku/python/lib/python3.6/site-packages/redis/client.py\", line 2415, in _execute\n    connection.connect()\n  File \"/app/.heroku/python/lib/python3.6/site-packages/redis/connection.py\", line 489, in connect\n    raise ConnectionError(self._error_message(e))\nredis.exceptions.ConnectionError: Error 111 connecting to ec2-54-158-35-36.compute-1.amazonaws.com:8029. ECONNREFUSED.", "timestamp": "2018-12-02T12:56:52Z+0000"}
I have tried to go and see the source code of Redis but still can't get what is going on. Why the connection is getting refused by Redis?

Hello @abylikhsanov
Are you sure that your Redis server is running on the same instance as your app? AFAIR this isn't the Heroku way, and that means you can't use socket connections - stick with TCP.

@itamarhaber How can I check that Redis is running? I might be doing it wrong

I went to the REDIS credentials and they have been changed. Thanks for that, I will go and change to a new URI on my app

Sure - closing this issue as it isn't related to redis-py.


chore: refine the connection description for SDKs

What's Changed in this PR

as title
Checklist

[ ] Please confirm that all corresponding versions of the documents have been revised.
[ ] Please ensure that the content in sidebars.ts matches the current document structure when you changed the document structure.
[ ] This change requires follow-up update in localized docs.

@sunng87 PTAL


(WARN) [1] in instance 'lld.reader' : Mismatch in input level buffer sizes (levelconf.nT). Level #0 has size 2 which is smaller than the max. input size of all input levels (10). This might cause the processing to hang unpredictably or cause incomplete processing.

when i am running IEMOCAP_01_wav_to_feature.ipynb
i am getting error like this.
i am unable to understand the error . can you please help me

Hi,
It seems the error comes from OpenSmile. I cannot understand the meaning of the error code, either.
I just checked the codes of the "preprocessing" and made it clear.
Please pull the repository, and use the code. ( I tested it )

put 'IEMOCAP_full_release' folder ( it can be downloaded from the IEMOCAP web page ) to "multimodal-speech-emotion/data/raw/IEMOCAP_full_release'
run the code in the "multimodal-speech-emotion/preprocessing"
you will get the processed data in the following folder, "multimodal-speech-emotion/data/processed/"

If you have any errors, please let me know it.

thank you sir. i will let you know
On Fri, 8 Feb 2019 at 18:34, David Seunghyun Yoon<EMAIL_ADDRESS>wrote:

Hi,
It seems the error comes from OpenSmile. I cannot understand the meaning
of the error code, either.
I just checked the codes of the "preprocessing" and made it clear.
Please pull the repository, and use the code. ( I tested it )

put 'IEMOCAP_full_release' folder ( it can be downloaded from the
IEMOCAP web page ) to
"multimodal-speech-emotion/data/raw/IEMOCAP_full_release'
run the code in the "multimodal-speech-emotion/preprocessing"
you will get the processed data in the following folder,
"multimodal-speech-emotion/data/processed/"

If you have any errors, please let me know it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/david-yoon/multimodal-speech-emotion/issues/2#issuecomment-461796360,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ap6TEdaW4KMyc78gwolUbkuHZbWrBmDYks5vLXXsgaJpZM4anff0
.


Carrier Grade docs typos

Typos

Learn Build status updates of commit d5be0f9:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: GitBranchDeletedOrForcePushed]

Cannot sync git repo to specified commit because ref +refs/pull/63/merge has been deleted or has been force pushed.
 If this is pull request, please ensure it is mergeable (no merge conflict) and open (not closed).

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


No space in confirmation text?

I am seeing a lack of a space in the confirmation message of the prompt:

I would assume a space should be appended between the label and the value?
Also, how can one turn off the confirmation message in the first place?
I am using iTerm on a Mac.

Yep, can confirm. Space needs to be added after Label.

Yep, can confirm. Space needs to be added after Label.


Pause the video on clicking on the video while playing

Is there any option in the videogular to pause the video when I click on the screen while the video is playing?

If i understand your question correctly, do you want to pause the video when you click anywhere on video when it is being played? Then you have this option already provided by Videogular.
Use this  . You can pause or play by clicking anywhere on the video canvas.
Cheers,
-/Sammi

You can add an ng-click on your body element and call API.pause() on ng-click.
For example:
<body ng-app="myApp" ng-controller="MyCtrl as ctrl" ng-click="ctrl.onClickBody()">
     <videogular vg-player-ready="ctrl.onPlayerReady($API)">
            <!-- videogular stuff -->
     </videogular>
</body>

Then in your controller:
angular.module("myApp", [/*dependencies*/]).controller("MyCtrl", function() {
    this.onPlayerReady = function(API){
        this.API = API;
    }
    this.onClickBody = function() {
        ctrl.API.pause();
    }
});

Closing, if you need help, please reopen.


no greeter.service

hi there,
in unit tests, the following service has been required:
const TestService = require("../../services/greeter.service");

meanwhile, there is no such service in /services folder.
I have added the greeter.service.js from the demo project and it worked.
should I make a pull request?

so, is there anything I could do to make it better? I want to start contributing on moleculer framework.

I appreciate it. I have a wishlist for Moleculer :) https://github.com/moleculerjs/moleculer/issues/100


Configurable Resources for Paperles

Chart Name
paperless-ngx
Is your feature request related to a problem? Please describe.
It'd be neat if paperless-ngx allowed to specify resource requests/limits
Describe the solution you'd like
resources:
  requests:
    cpu:
    memory
[...]

Describe alternatives you've considered
No response
Additional context
No response

It does! The configuration can be set exactly like in your solution :)

Although, similarly to the other open issue, this one will be changing soon due to a dependency chart upgrade. Currently, the config needs to look like this:
resources:
  requests:
    cpu:
    memory:

but soon it will change to:
controllers:
  main:
    containers:
      main:
        resources:
          requests:
            cpu:
            memory:

Ah neat, thanks, somehow I didn't realise that :)


[ISSUE] Uninstall is not removing config service

Describe the bug
When I try to uninstall an instance created with loadBalancer.enabled parameter set to false, service timescaledb-config is not removed.
To Reproduce

helm install timescaledb timescale/timescaledb-single --set "loadBalancer.enabled"=false
helm uninstall timescaledb
kubectl get service | grep config

Expected behavior
config service should be removed.

The config service is recreated by Patroni, and therefore can exist afterwards.
To fully purge all objects belonging to a cluster, see:
https://github.com/timescale/timescaledb-kubernetes/blob/master/charts/timescaledb-single/admin-guide.md#cleanup

For information, we're using terraform in our workflow, so the uninstall is triggered by terraform too, not expected to have to cleanup it manually :/


Expose function to perform header validation

Each month I get some data in a file with .xls extension.
Unfortunately this is some times a binary Excel file and sometimes a plain csv file.
Currently I try parse it as an Excel file and catch HeaderException if it was a csv content month.
To avoid catches exceptions like this, it would be nice if the logic to validate the header was exposed.

Perhaps we could add a TryCreateReader method to ExcelReaderFactory. I guess it should return false both if the given file is not an Excel file and if it is an Excel file but corrupted.

The absolutely simplest for us would be to refactor the probing code in CreateReader into a couple new public methods f.ex CanCreateBinaryReader, CanCreateOpenXmlReader, and CanCreateReader.
They will at least reject all CSVs except those starting with "PK". And accept any .zip files as valid OpenXml...
Any more in-depth probing will require creating the reader instance in a try/catch block, but I'm not sure if this belongs to the library.

Sure, with the downside that we'd open and probe the file twice in most cases. Presumably the user always want to open the file if the check is successful. But you're right, the user of the library might as well wrap the CreateReader call in a try/catch themselves. Would be more efficient in most cases.
Perhaps what we should do is better document what exceptions we throw.

Just to have some code examples:
With CreateReader:
using (var stream = File.Open(filePath, FileMode.Open, FileAccess.Read))
{
	try
	{
		using (var reader = ExcelReaderFactory.CreateReader(stream))
		{
		}
	}
	catch (NotSupportedException)
	{
		// read as csv
	}
}

With CreateBinaryReader:
using (var stream = File.Open(filePath, FileMode.Open, FileAccess.Read))
{
	try
	{
		using (var reader = ExcelReaderFactory.CreateBinaryReader(stream))
		{
		}
	}
	catch (HeaderException)
	{
		// read as csv
	}
}

With TryCreateReader:
using (var stream = File.Open(filePath, FileMode.Open, FileAccess.Read))
{
	IExcelDataReader reader = null;

	if (ExcelReaderFactory.TryCreateReader(stream, out reader))
	{
		using (reader)
		{
		}
	}
	else
	{
		// read as csv
	}
}

With CanCreateReader:
using (var stream = File.Open(filePath, FileMode.Open, FileAccess.Read))
{
	if (ExcelReaderFactory.CanCreateReader(stream))
	{
		using (var reader = ExcelReaderFactory.CreateReader(stream))
		{
		}
	}
	else
	{
		// read as csv
	}
}


Issue with Playback-Function on point-Timeline

Hi, I hope, I can still get some support for this great plugin.
I'd like to get a point-timeline with about 4000 points in a timerange of one year. I have the data in a json-file, with an start and end-date being the same. Exempel:
{ "start": "2019-01-01", "end": "2019-01-01"}
That leads to the problem of the playback-function doesn't work on play while while dragging the slider or just using the back- and forward-buttons work like a charme.
My function looks like this:
var pointTimeline = L.timeline(rechts, {
    onEachFeature: onEachFeature,
    style: function (feature) {
        return {
            radius: 5,
            color: 'red',
            fillColor: 'white'
        }},
        pointToLayer: function (feature, latlng) {
            return L.circleMarker(latlng, pointTimeline);
        }
});

var slider = L.timelineSliderControl({
    formatOutput: function (date) {
        return moment(date).format("DD-MM-YYYY");
    },
    enableKeyboardControls: true,
    steps: 3632
});
map.addControl(slider);
pointTimeline.addTo(map)
slider.addTimelines(pointTimeline);

Any idea of what I could do to get the playback-function work?

It's been a while since I've worked on this (sorry everyone; updates are hopefully coming soon) but I'm pretty sure you need some non-zero amount of time for the event to appear during playback. Next and previous work because they can pick up specific data points, even if their times are identical. I'm a little surprised that manually dragging the slider works, but it's probably the same idea as next/prev.
Could you add times to the data, or add a day to the end timestamp?

Hi Jonathan, thanks for getting back that quickly.
Adding a full day would distort the visualisation. I want to show a timeline of attacks and where they took place, so the attack-point for Day X should not show up on Day+1.
Adding hours and minutes could help, but adding both led to a "Invalid date"-Error. I used the follow format for the try
2019-01-03 23-59
Do you have any idea for a working format?
I'll add my case th #137 .

The dates get parsed by getting run through new Date(), so it has to be something that understands. 2019-01-03 23:59 works for me, but as best I can tell from the spec that's nonstandard. 2019-01-03T23:59 is better.


[WIP] Update: Add note when "-n" is less than default limit

So far so good, but as mentioned the other day - let's please also add some robotfm tests in addition to unit tests.

Robot tests: https://github.com/StackStorm/st2tests/pull/106 and st2cd action for the tests: https://github.com/StackStorm/st2cd/pull/292

Nice work on the tests and thanks for getting rid of the global variable. :+1:
Well test it a bit later.

I've tested it locally and it seems to work fine so I will go ahead and merge it :+1:
Feel free to merge the tests once new packages are built.


Update tsconfig.json

I was trying to remove the build errors. No luck

All good. Not really essential.

But this is exactly the kind of help the plugin needs. Good with otherwise.


new ContainerPool aggressively restarts containers under load

Environment details:

local deployment, Mac OS
docker 17.03 (server 17.05 on docker-machine)

Steps to reproduce the issue:

use [https://github.com/markusthoemmes/openwhisk-performance] to run throughput test (tests/throughput.sh)
run throughput test:
./throughput.sh https://<IP_ADDRESS>  "$(cat ~/git/forks/tysonnorris/openwhisk/ansible/files/auth.guest)" 10 1000
in a separate terminal check for nodesjsaction containers - notice they are constantly recreated
docker ps | grep nodejs

Provide the expected results and outputs:
Expected: Don't restart containers when scheduling activation for an action that already has max warm containers that are all busy. Instead, requeue the activation for later.
Provide the actual results and outputs:

Per above, notice the containers are restarting constantly, even though there is only a single action being exercised

Notice throughput latency is way up, compared to 4 concurrent users.

[Mon May 15 2017 20:24:41 GMT+0000 (UTC)] INFO Requests: 0 (0%), requests per second: 0, mean latency: 0 ms
[Mon May 15 2017 20:24:46 GMT+0000 (UTC)] INFO Requests: 10 (1%), requests per second: 2, mean latency: 2904.3 ms
[Mon May 15 2017 20:24:51 GMT+0000 (UTC)] INFO Requests: 20 (2%), requests per second: 2, mean latency: 4631.8 ms
[Mon May 15 2017 20:24:56 GMT+0000 (UTC)] INFO Requests: 28 (3%), requests per second: 2, mean latency: 4242.9 ms
[Mon May 15 2017 20:25:01 GMT+0000 (UTC)] INFO Requests: 36 (4%), requests per second: 2, mean latency: 5887.2 ms
[Mon May 15 2017 20:25:06 GMT+0000 (UTC)] INFO Requests: 50 (5%), requests per second: 3, mean latency: 5270.4 ms
[Mon May 15 2017 20:25:11 GMT+0000 (UTC)] INFO Requests: 60 (6%), requests per second: 2, mean latency: 4091.2 ms
[Mon May 15 2017 20:25:16 GMT+0000 (UTC)] INFO Requests: 70 (7%), requests per second: 2, mean latency: 4556.8 ms
[Mon May 15 2017 20:25:21 GMT+0000 (UTC)] INFO Requests: 84 (8%), requests per second: 3, mean latency: 4444.2 ms
[Mon May 15 2017 20:25:26 GMT+0000 (UTC)] INFO Requests: 94 (9%), requests per second: 2, mean latency: 4195.4 ms

Additional information you deem important:
n/a

Regression confirmed! Thank you very much for catching this.
As already discussed, one simple fix is to exclude identical actions from being scheduled for removal (we should do this anyway).

nice find @tysonnorris.
can we add a performance regression test?

@rabbah "performance regression test" - do you mean using https://github.com/markusthoemmes/openwhisk-performance? I'm not sure this is possible currently. In the meantime I'm trying to fix up the ContainerPoolTests to at least verify proper functionality with regards to removals when pool is full.

One note - with #2246 , for a load of:

varied actions OR
varied invocation namespaces
the expected behavior is:
Once the pool is maxed out, additional activations with either different action OR different invocation namespace will be queued until are containers in Free state

This still leaves the potential for "hogging the container pool" by specific actions+invocation namespaces.
To better handle that, some options to add may be:

track the number of requeues a Run message goes through via ContainerPool.receive
log data on requeue metrics (are internal metrics available in other mechanisms? jmx, etc?)
limit the number of same-action( and same user) Runs a ContainerProxy may process IFF there are requeues occurring for other Runs that have different actions/users.

This would increase container "thrashing", but would prevent low traffic actions from being starved while being submitted alongside higher traffic actions. Any thresholds used should be tunable, via whisk properties.

I would only force queue the messages if the container is really maxed out. That means: No containers available and each namespace has exactly 1 container (that's an overload scenario basically).
As commented in the PR, I would always schedule a container of the most consuming resource for removal, even if it's in Busy state. That action would still finish, but the other action can go on and no starvation happens. This scheme induces a bit of overcommit, which I tend to think we can live with.


Document email 'from' field configuration

To send from a service like Postmark, the from email needs to be specified in apostrophe-forms. This should probably be in readme
'apostrophe-forms': {
      email: {
        from: "First LastName<EMAIL_ADDRESS>      }
 }

Also should be done anyway to make it way less spammy.
On Sep 3, 2015 4:58 PM, "Samantha Combs"<EMAIL_ADDRESS>wrote:

To send from a service like Postmark, the from email needs to be specified
in apostrophe-forms. This should probably be in readme
'apostrophe-forms': {
email: {
from: "First LastName<EMAIL_ADDRESS>}
}
—
Reply to this email directly or view it on GitHub
https://github.com/punkave/apostrophe-forms/issues/25.


fix hero text

Fixes #63

Oh sorry I didn't notice the copy got updated here - I have removed the double text and highlighted the text earlier in the paragraph.

@secondl1ght just as I hit the approve it seems conflict appeared, can you address it please?


Need way to set window size/options

Hey, ive just started using this library. I see no way to set a window size.
Is there any way to go about setting the size of my windows in pixels?
If not can support be added in for it?
Thanks

partially implemented - window.setWindowState()
implemented for Windows platform only so far

#258

Assuming it's working.


Enable densenet test

It seems to pass for me locally. Let's check if it passes in CI.
If not, here's a CI that adds functionality to modify the tolerance values: https://github.com/onnx/onnx/pull/628

seems already enabled by now. closing.


async method with non-future return does not cause type error

Example:
import 'dart:async';

String future1() async {
  print('1');
  await Future.delayed(Duration(seconds: 1));
  return 'foobaz';
}

Future<void> main() async {
  print(await future1());
}

Dart 1, checked mode:
Unhandled exception:
type 'Future' is not a subtype of type 'String' of 'function result'
#0      future1 (file:///usr/local/google/home/bkonyi/sdk/tmp.dart:3:24)
#1      main (file:///usr/local/google/home/bkonyi/sdk/tmp.dart:9:15)
<asynchronous suspension>
#2      _startIsolate.<anonymous closure> (dart:isolate-patch/dart:isolate/isolate_patch.dart:279)
#3      _RawReceivePortImpl._handleMessage (dart:isolate-patch/dart:isolate/isolate_patch.dart:165)

Dart 2:
1
foobaz

This issue looks like a variation/duplicate of #33425

Closing as a duplicate of https://github.com/dart-lang/sdk/issues/33425
Note the instructions as https://www.dartlang.org/dart-2#migrating-packages - an important step is running the analyzer which does surface this error.


Remove obliterate local references on segment zamboni

Cleans up the local references created to store the obliterate ranges within the merge tree. Also adds a test to validate that the references exist prior to zamboni, and are removed after.

i broke this PR, as i tried to point at LocalReferenceObliterate, which is the branch we should use the collaborate


Crashes on opening a file

RUST_BACKTRACE=full inlyne a.md
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /home/fuh/.cargo/git/checkouts/glyphon-e1a2543889d66ef0/5bf8b6b/src/text_render.rs:104:26
stack backtrace:
   0:     0x55ce29017c01 - <unknown>
   1:     0x55ce29048d5f - <unknown>
   2:     0x55ce29012e47 - <unknown>
   3:     0x55ce29017a15 - <unknown>
   4:     0x55ce29018fc3 - <unknown>
   5:     0x55ce29018d54 - <unknown>
   6:     0x55ce29019549 - <unknown>
   7:     0x55ce29019401 - <unknown>
   8:     0x55ce29018066 - <unknown>
   9:     0x55ce29019192 - <unknown>
  10:     0x55ce2826da93 - <unknown>
  11:     0x55ce2826db23 - <unknown>
  12:     0x55ce28bcf018 - <unknown>
  13:     0x55ce2831d0c1 - <unknown>
  14:     0x55ce282f4198 - <unknown>
  15:     0x55ce282d9a31 - <unknown>
  16:     0x55ce282db475 - <unknown>
  17:     0x55ce283140aa - <unknown>
  18:     0x55ce282c9fe3 - <unknown>
  19:     0x55ce282ca7ad - <unknown>
  20:     0x55ce2900ca2b - <unknown>
  21:     0x55ce28314705 - <unknown>
  22:     0x7f206fe4614a - __libc_start_call_main
  23:     0x7f206fe4620b - __libc_start_main_impl
  24:     0x55ce2826e235 - <unknown>
  25:                0x0 - <unknown>

a.md

I can't reproduce this unfortunately, so there must be something specific to your system. It looks like you're already running a build from the main branch. Can you post a stacktrace with a build that includes debug info? Should be as simple as the following if you already have cargo installed
$ # From within the inlyne repository
$ RUST_BACKTRACE=full cargo run -- a.md

back2.txt

Thanks for the full backtrace with debug info. It looks like this is a duplicate of #87 (specifically the panic seems to match https://github.com/trimental/inlyne/issues/87#issuecomment-1553803763)
I haven't had the time to investigate more, but it seems to be a pretty consistent issue that people are running into on fedora


Nonexistent issues get linked in commit messages and comments

Description
Currently, when users mention nonexistent issues in commit messages or comments, the system generates a hyperlink for them. However, when hovered over, these links lead to a "Network error" tooltip due to a 404 error because the referenced issue doesn't exist. This behavior can be confusing and misleading for users.
Potential Solutions:

Sub-Optimal Solution: Indicate that the issue does not exist when being hovered over in lieu of a Network error.
Optimal Solution: Issues should only be highlighted if they exist within the repository like in GitHub.

What makes the second solution more difficult is because we can't be invoking SQL queries on every page render to check the existence of a referenced issue.
GitHub internally links the issue at the time of commit or comment, not at the page render and this can be confirmed by making a new initialized repository, referencing #1 in a commit message before and after the first issue is created, and you'll only see the second commit (which is post-issue) get highlighted and linked.
Gitea Version
v1.21.10
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots

Git Version
No response
Operating System
No response
How are you running Gitea?
Running a fresh instance via CLI from gh-codespaces.
Database
SQLite

That's currently expected behaviour because the references are not checked because of performance reasons.

What we could do is at time of creation of the commit or creation/edit of a comment containing issue refs, check if the referenced issue exists, and if it does not exist, don't perform the replacement in the comment or commit message.
Such a method is possible without any ill effects on performance and is also historically accurate so that one can not link to future issues.

Well… That does have a major drawback though, @silverwind:
If I understand your proposal correctly, it means we have to hardcode HTML into a comment.
I am not a fan of that at all, especially since it irreversibly changes what you entered.

Nope, commit hashes are actually checked. I made sure to confirm this when making the issue.
https://github.com/go-gitea/gitea/assets/28637006/fe5056b7-d399-4aa7-a8b3-d23c0eab8d0d

Well… That does have a major drawback though, @silverwind: If I understand your proposal correctly, it means we have to hardcode HTML into a comment. I am not a fan of that at all, especially since it irreversibly changes what you entered.

Why HTML? it could just be hardcoding a reference which gets translated into HTML on page render.

Well… That does have a major drawback though, @silverwind: If I understand your proposal correctly, it means we have to hardcode HTML into a comment. I am not a fan of that at all, especially since it irreversibly changes what you entered.

Indeed, that's a drawback. Also it would require commit messages to be stored in database which I think they are not currently.

And it will not highlight references which are not valid at commit time.

On the other hand, existing instances with thousands of issues would not benefit from a fix that is done at commit/comment time, so likely doing it purely at render time is still ideal.

Any updates? In the meantime, why don't we just handle "Not Found" responses?

Yes, maybe a quick fix is the frontend can handle 404 and return a better description to end users.

We could at least detect the 404 and show "It looks like this issue does not exist", that'd at least get the ugly error away as a temporary solution.

https://github.com/go-gitea/gitea/pull/31181 will hide the popup completely on non-existant issue, so after that, the only remaining task would be to not linkify these nonexistant issues in first place on backend.


Error when applying

Hi,
I am new to kubernetes and the temporal-operator. While trying the "Getting Started" page I receive the following error when applying the file to the cluster:
Error from server (InternalError): error when creating "dep.yaml": Internal error occurred: failed calling webhook "mtemporalc.kb.io": failed to call webhook: Post "https://temporal-operator-webhook-service.temporal-system.svc:443/mutate-temporal-io-v1beta1-temporalcluster?timeout=10s": context deadline exceeded.
Any help is appreciated.
Best,

Thank you @alexandrevilain. We have currently opted for a deployment without temporal-operator. In case I give it a try again sometime in the future, I will post the logs. For now I close the issue.
Best,

I just came across the exact same error deploying this on a GKE private cluster. It is related to this (from cert-manager docs): https://cert-manager.io/docs/installation/compatibility/#gke
The webhook needs a firewall rule that allows the GKE control plane to access it.
That said, I wasn't sure what to put in the target list, so I allowed all IP addresses in to test that this was the issue. After doing that, I was able to apply the yaml properly without the error.
@alexandrevilain do you have any idea what IP target we should use to allow specific access to the webhook? i.e. rather than <IP_ADDRESS>/0

Leaving this for future users in case anyone runs across the same issue.
If you're running on a private cluster, you'll need to add a firewall rule that allows the GKE control plane to access the target service (the temporal-operator-webhook-service). Find your control plane's address range (GKE > Clusters > select your cluster > Networking > Control plane address range). Copy the address range and create a firewall rule with that range as the source.
Use TCP port 9443.
Should work after that!

Thanks @calvinl !
Maybe we could add a doc section ?

Thank you @calvinl !


Copy no longer works in iOS 11

Firstly, thanks for your hard work on this plugin, it's worked great for me in iOS 10 and below.
However, since iOS 11 came out, the copy function no longer works as expected. For example, if I do the following:
cordova.plugins.clipboard.copy('password');
And then open the Facebook app on iOS 11, tap and hold on the password field and tap 'Paste':

Then nothing gets pasted:

If I then open the default iOS Notes app and attempt to paste there, instead of the plain text being pasted, I get this "text" object pasted:

However, in some apps, such as the default iOS Mail app, the text will be pasted as expected:

Is there any chance this could be fixed? Or does anyone know of a workaround?
Thanks.

Never mind, I fixed it by following the advice in this issue:
#26


Update comment in README about Cython 3

Cython 3 has been released, it's not a future project any more!

Thanks


[5.1] Fix nested route names with group that has no "as" option

Fixes #9204

Duplicate of #9198.


Fix typo in environment variables table contents.

Addresses https://github.com/buildkite/docs/issues/2869.

Hi @yaningo ,
Thanks very much for spotting out the issue mentioned in https://github.com/buildkite/docs/issues/2869.
Please feel free to approve this PR so that I can merge it in and resolve that issue.

Thanks @JuanitoFatas !


Publishing an unchanged version when there are user comments removes the comments

Ideally, unless the changed text replaces the entire text that is the subject of the comment (highlighted, usually) the comment should not be removed.  Current behavior is, even if no changes are made, the comments get blown away.

This is on the list to resolve best I can. At the moment the plugin publishes the content after conversion the ADF (https://developer.atlassian.com/cloud/jira/platform/apis/document/structure/) Confluence returns comments as part of ADF so that removes the comments from being displayed.
Currently the thinking I have is to grab all comments (potentially just unresolved ones) in the page just before publish and adding a section to the bottom with all the inline comments. FYI Page comments are always good to go already its just inline comments that have this issue.
I also want to add tests and improve the compatibility between the ADF generated by https://atlaskit.atlassian.com/packages/editor/editor-json-transformer and what Confluence returns to stop publishing pages for changes that is just a difference in how the two systems generate ADF. This is on the list to do once I get a few more initial functional features sorted.

Started on https://github.com/obsidian-confluence/obsidian-confluence/pull/164

Next version will have the feature that does its best to handle this.
I have also created some documentation for this though it wasn't easy so probably isn't super easy to understand at this point.
https://obsidian-confluence.com/features/comment-handling.html

https://github.com/obsidian-confluence/obsidian-confluence/releases/tag/3.7.0


New Grip Reward and Reward Function Style for Pick-Place-V2

Just a Draft for now. Grip reward now grows smoothly from 0 -> 1 as it gets closer to the puck and cages. Caging but not grasping gets 0.5 reward, caging and grasping is a full 1 pt reward. This leads to much simpler reward functions that look like this:
in_control = hprod(object_grasped, in_place)
reward = (2*object_grasped) + (5*in_control) + lift_bonus

closing this because I believe we've standardized gripping functions.


Exceptions during parsing and other errors.

These are the entries (not published):
https://nomad-lab.eu/prod/rae/gui/entry/id/sa6kfegYRumPwIR2ZEptlQ/x6ggFOMoG3EZUXlZgGvOyn7LlpSa/logs
https://nomad-lab.eu/prod/rae/gui/entry/id/sa6kfegYRumPwIR2ZEptlQ/14mjscjcq8Yy7N1c64neFlOV-uBV/logs
These are the exceptions:
Traceback (most recent call last):
  File "/app/nomad/processing/data.py", line 460, in parsing
    self._parser_results, logger=logger)
  File "/usr/local/lib/python3.7/site-packages/cp2kparser/cp2k_parser.py", line 1425, in parse
    self.parse_configurations_quickstep()
  File "/usr/local/lib/python3.7/site-packages/cp2kparser/cp2k_parser.py", line 1137, in parse_configurations_quickstep
    parse_calculations(md_steps)
  File "/usr/local/lib/python3.7/site-packages/cp2kparser/cp2k_parser.py", line 1113, in parse_calculations
    sec_system = self.parse_system(atomic_coord)
  File "/usr/local/lib/python3.7/site-packages/cp2kparser/cp2k_parser.py", line 1004, in parse_system
    lattice_vectors = self.get_lattice_vectors(trajectory._frame)
  File "/usr/local/lib/python3.7/site-packages/cp2kparser/cp2k_parser.py", line 852, in get_lattice_vectors
    cell.get('ABC').split(), dtype=float), units).to('angstrom').magnitude
ValueError: could not convert string to float: '${LBOX}'

Traceback (most recent call last):
  File "/app/nomad/processing/data.py", line 460, in parsing
    self._parser_results, logger=logger)
  File "/usr/local/lib/python3.7/site-packages/cp2kparser/cp2k_parser.py", line 1425, in parse
    self.parse_configurations_quickstep()
  File "/usr/local/lib/python3.7/site-packages/cp2kparser/cp2k_parser.py", line 1137, in parse_configurations_quickstep
    parse_calculations(md_steps)
  File "/usr/local/lib/python3.7/site-packages/cp2kparser/cp2k_parser.py", line 1107, in parse_calculations
    parse_md_step(calculation)
  File "/usr/local/lib/python3.7/site-packages/cp2kparser/cp2k_parser.py", line 1080, in parse_md_step
    val = val.to('joule').magnitude
AttributeError: 'numpy.ndarray' object has no attribute 'to'

There are other errors: "Error reading trajectory", "Error reading MD energies".

@ladinesa responded:
The Error reading MD energies is expected for the other upload since the trajectory and energies files present do not match what are indicated in the output. I do not try to read these files as I suppose that these belong to another calculation. Maybe the the uploader can shed light on why this is the case maybe I am missing something as this seems to be a restart calculation.
The other issue concerns a variable assignment in the input file. I provided support for such a case in the latest commit.

Dear @ladinesa
I am doing some tests on NOMAD, so I didn't check all the files that I uploaded (I am not the one who  has run these simulations).  I have taken  few examples from my colleagues and tried to upload them on NOMAD. I think the problem come from our outputs. I have taken today one Gaussian output and one example of CP2K outputs where I know that the simulations have finished without problems and this time the data has been uploaded without problem. I will check with my colleagues for the other folders that they gave me and for which the upload has not been successful.   I keep you updated if the problem is related to CP2K parser or to the output.
In our team, we launch MD simulations using CP2K or Gaussian. For the servers that we use, we need to restart calculations each 24h that's why you see restart files. May be the examples that I got from my colleagues were not complete.
Thanks for you help.


interface to gr1py, a new tool for GR(1)

https://github.com/slivingston/gr1py
https://pypi.python.org/pypi/gr1py
"gr1py is an enumerative (or concrete) reactive synthesis tool for the GR(1) fragment of LTL. It is pure Python."
I recommend reviewing PR #133 first because this is based on it. To run tests, try
./run_tests.py -f gr1py

Notes with comments:

There is no reference to gr1py in the User's Guide nor among the checks of optional dependencies in setup.py. I recommend leaving it this way until we have experimented more with it, and possibly until the interface becomes more sophisticated.
There is currently no declared preference about which versions of gr1py are supported. We should wait until the next release to decide it because gr1py could continue to progress between now and then. However, if you want to declare something now, use at least 0.1.0.
A quick demonstration of the new interface is to modify examples/robot_planning/continuous.py to have ctrl = synth.synthesize('gr1py', specs, on line 101.

In some TuLiP examples (including those that involve abstractions), we create explicit models in the form of transition systems and then encode the transition system in temporal logic to interface symbolic solvers. With gr1py (as of this pull-request), it looks a bit redundant to go from TS to spec and back to an explicit TS compatible with gr1py. Do you envision this redundancy to be eliminated to some extent (I can imagine this might be tricky in some cases) when you say "interface becoming more sophisticated", or maybe compatible transition system structures to be used in TuLiP and gr1py?

There are a few comments worth mentioning here.
An informal observation (I do not claim to have formally proved it, but it seems simple). In problems arising from abstractions, enumerated graphs are constructed. A formula that encodes such a graph has size at least as large as the graph, because it mentions every node, and every edge. This is special to the problems in tulip, and does not apply to problems that arise from "unfolding" a program. As a result, the resulting specification is about-linear in the state space (assuming the state space contains only states resulting from discretization).
Due to the previous size comparison, the cubic complexity of GR(1) synthesis can be misleading for formulae resulting from discretization. With thousands of states, a formula with thousands of disjuncts results. However, this doesn't lead to a blowup in synthesis, because the formula is already linear in the state space, so its cubed length saturates in the complexity analysis by the number of states.
This argument suggests that it may not be too bad to run the fixpoint algorithm on an enumerated representation, instead of a symbolic one.
Another note is the comment in 2012 Bloem et al. JCSS that with an enumerated data structure the complexity is better.
About the issue above of converting twice:

enumerated graph in tulip -> formula
formula in tulip -> enumerated graph in gr1py

I would assume that this is not a performance issue, unless proved otherwise with profiling.
One reason is the enumeration mentioned above, which implies that the enumerated graph is about as large as the formula, so the amount of computation for conversions is linear in that size.
Another reason for converting everything to formulae, and then letting gr1py enumerate the state space is to unify handling of enumerated graphs and (string) formulae given as input.
This ensures a clean, standardized interface between the frontend (abstraction etc.) and the backend(s) (gr1py, gr1c, etc.).
For example, the graph representations inside tulip can change completely, the internals of gr1py, but as long as the frontend outputs the same syntax that the backend understands, the implementors of the frontend and backend do not need to know anything about the internals of the other part, or modify their code.
In a situation where I am parsing-flattening repeatedly, and was once doing that with manipulation of abstract syntax trees as enumerated graphs, the former approach has proved much cleaner and modular, whereas the latter is error prone.
A side comment is that a symbolic solver in Python has been interfaced to within the branch python_symbolic_streett_1_interface and will be candidate for merging after this one. So, we will have both types of solvers, and can also compare. I suspect that this may lead to observations similar to the comparison between enumerative and symbolic model checkers for hardware vs software systems (due to structure of the associated BDDs).

I agree with the modularity comment (performance to be determined).
BTW, we have reported a similar observation in the switching protocol synthesis paper with Fei Sun et al. (ACC 14) that implements some fixed point algorithms on explicit graph representation.
For abstractions, the transition graph is sparse (i.e., the branching factor is low). For instance, if you are abstracting continuous-time systems, transitions are limited to neighbors (and discrete-time systems modeling physics do not jump too further in one step for reasonable sampling frequencies). This makes certain explicit data structures for system representation advantageous at least from a practical standpoint. Similarly for the controller representation.
Would be interesting to see if our observations carry over to these new set of solvers.

For the record, as of 19a17b15e358845900e193ccae9e659170a23ebe, on:

Debian GNU/Linux 8 (jessie) 32-bit
Intel® Core™2 CPU 6700 @ 2.66GHz × 2
2.0 GiB
Python 2.7.8
networkx 1.10

with gr1py:
$ /usr/bin/time -f "%E real, %U user, %S kernel, %P cpu %M max (KB)" python gr1.py
0:32.37 real, 30.45 user, 0.37 kernel, 95% cpu 35508 max (KB)

and with gr1c:
$ /usr/bin/time -f "%E real, %U user, %S kernel, %P cpu %M max (KB)" python gr1.py
0:02.06 real, 1.82 user, 0.09 kernel, 93% cpu 42808 max

Note that gr1.py uses a one-hot encoding.


[[CHORE]] Remove unreachable branch

The _checkParams function included a guard to ensure it was only
invoked in appropriate situations. Because its one and only call site
was itself guarded by an equivalent condition, the branch in
_checkParams was unreachable.
Although this situation made the internal guard of _checkParams safe
to remove, doing so would have made the function more dangerous in
general since anyone introducing new invocations in the future would
have to take care to perform a similar check.
To avoid introducing such a dangerous interface, remove the function
entirely and inline its body at its only call site.

Coverage remained the same at 100.0% when pulling d20f1db7f01e8aca74f99b3943a1bb51bad720b2 on jugglinmike:remove-unreachable into 70b6639c903685412247ac226d10c1a19cb4ecdd on jshint:master.


Upgradable contracts using set_code function

This pr is a follow up for #10567.
The question that naturally comes to mind:

Do we need to check if there is deployed contract behind the hash that is being set?

That would give us a little bit for of certainty when calling set_code function. On the other hand we won't be able to set hash for the contract that has not been deployed yet. As for me it doesn't make much sense considering that we don't make full check of what we're setting with this call anyways.
Thoughts and comments are required and welcome.

I think we need to check whether the code hash already exists. It is necessary because we need to increase the ref count of the code that we are switching to. This will prevent the code from being deleted. The reason for that is that we don't want the owner of a code being able to delete it when it is in use.
We could of course get rid of the ref counting and let the owner always delete the code. Anyone who still needs the code would then need to re-upload the code (they can get it from an archive node). However, this can lead to intermediate breakage and might prevent people from sharing code.

Makes sense. Will add the check using contains_storage method.

@athei, please take a look at what has been done, and let me know what you think

@athei, please take a look at updated.
I'm not sure how to stop execution of the contract though, what are your thoughts on this?

@athei, do you have any thoughts on this one? I think we could just mention in docs that tx revert scenario you talked about previously. What do you think?

Yeah I think we can leave it the way it is: Non terminating. More docs is always nice. It is nothing out of the ordinary, though: If you revert everything gets reset.
One other thing is bugging me: This will weaken our deterministic address assumption. Before this change you can always confidently assume that a contract address identifies a specific code hash. After this change this is no longer true for contracts which include set_code. I mean this might be okay because the assumption still holds for contracts which don't use set_code.

What are the negative consequences of breaking this deterministic address assumption?

I was hoping you had some idea since it was your proposal to add this function. Deterministic addresses are nice because you can know the address and embed it into a contract before the target needs to be actually deployed. However, this is still the case for contracts which don't use set_code (which are call contracts as of right now).

We won't be able to revert these changes before it's sealed to stable, will we?

I don't understand what you mean.

Deterministic addresses are nice because you can know the address and embed it into a contract before the target needs to be actually deployed.

Yeah, we sacrifice this for upgradability. That was my way of thinking.

We won't be able to revert these changes before it's sealed to stable, will we?

I don't understand what you mean.

I mean that we can roll out this change as an unstable feature first, and if we realise something that we are missing right now we can just revert this change, right? (In case something really bad happens, which is unlikely)

Yes this is correct. We want to have it as unstable first at least until we have support it in ink! and people get a chance to play with it.

I think only root calls should be allowed to call this function seeing as contracts are a public utility, users of a contract wouldn't like if the code changes under them.

@seunlanlege, it's a good point actually. Let's leave it as it is for now, and if we receive any negative feedback before sealing it to stable we can think of adding this feature, I feel like making it right now is premature optimization, imho.

Will take a look tomorrow!

I think only root calls should be allowed to call this function seeing as contracts are a public utility, users of a contract wouldn't like if the code changes under them. But this is more of a philosophical debate.

This was discussed in: https://github.com/paritytech/substrate/issues/10567
The bottom line is that the trust that is required for proxy contracts and a contract that uses set_code is the same. Proxy contracts can also change the code that is executed by changing the contract to delegate_call into. Users can decide to not trust contracts which use set_code in the same way the might not trust proxy contracts.

Okay, so I changed the benchmark and added verify block, didn't get any errors. Seems to be pretty straightforward. @athei, @HCastano what do you think?

You changed the benchmark so that you set it to the same code multiple times. This won't work out because this will repeatedly read from the same OwnerInfo and hence will still yield too few reads. You need to keep the original structure of setting it to different code hashes.

@athei, this is what i'm getting on my machine (without #[skip_meta]):
        // Storage: System Account (r:1 w:0)
        // Storage: Contracts ContractInfoOf (r:1 w:1)
        // Storage: Contracts CodeStorage (r:1 w:0)
        // Storage: Timestamp Now (r:1 w:0)
        // Storage: Contracts OwnerInfoOf (r:36 w:36)
        fn seal_set_code_hash(r: u32, ) -> Weight {
                (0 as Weight)
                        // Standard Error: 7_683_000
                        .saturating_add((1_705_926_000 as Weight).saturating_mul(r as Weight))
                        .saturating_add(T::DbWeight::get().reads((99 as Weight).saturating_mul(r as Weight)))
                        .saturating_add(T::DbWeight::get().writes((99 as Weight).saturating_mul(r as Weight)))
        }

Seems pretty crazy :)

/benchmark runtime pallet pallet_contracts

Weights for b32e4ec8f71a68184264e514446597e800e7e0fe are at https://gist.github.com/joao-paulo-parity/374c56737868015b7fcd3b3bb7e4bbaa

Some crazy numbers here.

Some crazy numbers here.

Which numbers do you mean exactly?

Which benchmark numbers do you mean exactly?
Number of reads and writes for contracts OwnerInfoOf.

Which benchmark numbers do you mean exactly?

Number of reads and writes for contracts OwnerInfoOf.

The metadata looks strange indeed. But this is only relevant for actual dispatchables. For us it is more of a debugging help.
@shawntabrizi Do you have any idea how this quirky number of 36 is here. I thought read and writes depending on a component are not part of the metadata?
// Storage: System Account (r:1 w:0)
// Storage: Contracts ContractInfoOf (r:1 w:1)
// Storage: Contracts CodeStorage (r:1 w:0)
// Storage: Timestamp Now (r:1 w:0)
// Storage: Contracts OwnerInfoOf (r:36 w:36)
fn seal_set_code_hash(r: u32, ) -> Weight {
	(0 as Weight)
		// Standard Error: 2_158_000
		.saturating_add((932_937_000 as Weight).saturating_mul(r as Weight))
		.saturating_add(T::DbWeight::get().reads((99 as Weight).saturating_mul(r as Weight)))
		.saturating_add(T::DbWeight::get().writes((99 as Weight).saturating_mul(r as Weight)))
}

bot merge


Babel Error: api.caller is not a function - while trying to install 3.2.0

Describe the bug
When trying to install as per Quck Start, getting an error:
at /Users/***/dev/test-meteor-complete/node_modules/@babel/preset-env/src/index.ts:390:13: api.caller is not a function
   at /Users/***/dev/test-meteor-complete/node_modules/@babel/preset-env/src/index.ts:390:13
   at /Users/***/dev/test-meteor-complete/node_modules/@babel/helper-plugin-utils/src/index.ts:62:12
   at packages/meteor-desktop-bundler/bundler.js:815:28
   at Function.time
   (/Users/***/.meteor/packages/meteor-tool/.<IP_ADDRESS>3agd.102mc++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/tools/tool-env/tools/tool-env/profile.ts:284:30)
   at MeteorDesktopBundler.processFilesForTarget (packages/meteor-desktop-bundler/bundler.js:499:17)

To Reproduce

Have following packages installed:

  "dependencies": {
    "@babel/runtime": "^7.23.5",
    "less": "^4.2.0",
    "meteor-node-stubs": "^1.2.7",
    "vue": "^3.4.7",
    "vue-meteor-tracker": "^3.0.0-beta.7",
    "vue-router": "^4.2.5"
  },
  "devDependencies": {
    "@meteor-community/meteor-desktop": "^3.2.0",
    "electron": "17.4.11",
    "electron-builder": "24.6.4"
  }

Run command:
meteor --mobile-server=<IP_ADDRESS>:3000 OR npm run desktop

Observe the errors related to @babel api.call

Versions:

Meteor version: 2.14
Package version: 3.2.0

Additional context
Tried multiple times to reset meteor (deleting .meteor/local folder as well as delete node_modules on multiple steps), tried to add @babel/preset-env and @babel/core - still no luck.

npm run desktop result:
ERROR  electronApp:  error while transpiling or minifying:  TypeError: api.caller is not a function
    at builder (/Users/***/dev/test-meteor-complete/node_modules/@babel/preset-env/src/index.ts:390:13)
    at /Users/***/dev/test-meteor-complete/node_modules/@babel/helper-plugin-utils/src/index.ts:62:12
    at ElectronApp.transpileAndMinify (/Users/***/dev/test-meteor-complete/node_modules/@meteor-community/meteor-desktop/lib/electronApp.js:854:33)
    at ElectronApp.build (/Users/***/dev/test-meteor-complete/node_modules/@meteor-community/meteor-desktop/lib/electronApp.js:451:24)
    at MeteorDesktop.run (/Users/***/dev/test-meteor-complete/node_modules/@meteor-community/meteor-desktop/lib/index.js:123:9)
INFO  electronApp:  packing .desktop to asar
VERBOSE  electronApp:  clearing temporary .desktop
INFO  meteorApp:  checking for any mobile platform
INFO  meteorApp:  building meteor app
DEBUG  meteorApp:  clearing build dir
INFO  meteorApp:  acquiring index.html
ERROR  meteorApp:  error while trying to download index.html for web.cordova, be sure that you are running a mobile target or with --mobile-server:  TypeError: The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received type boolean (false)
    at Object.writeFileSync (node:fs:2362:5)
    at MeteorApp.copyBuild (/Users/***/dev/test-meteor-complete/node_modules/@meteor-community/meteor-desktop/lib/meteorApp.js:657:20)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at MeteorApp.build (/Users/***/dev/test-meteor-complete/node_modules/@meteor-community/meteor-desktop/lib/meteorApp.js:856:17)
    at ElectronApp.getMeteorClientBuild (/Users/***/dev/test-meteor-complete/node_modules/@meteor-community/meteor-desktop/lib/electronApp.js:553:9)
    at ElectronApp.build (/Users/***/dev/test-meteor-complete/node_modules/@meteor-community/meteor-desktop/lib/electronApp.js:464:13)
    at MeteorDesktop.run (/Users/***/dev/test-meteor-complete/node_modules/@meteor-community/meteor-desktop/lib/index.js:123:9) {
  code: 'ERR_INVALID_ARG_TYPE'

A clean repo to try to install to is here:
https://github.com/vbgm/meteor-vue3-less

"@meteor-community/meteor-desktop": "^3.1.1" seem to be working, but hot code push seem to be struggling..

I’m having the same error indeed every time I build a new version of my app. However, the build continues and I’m not sure what consequences this error has for my app.This wasn’t showing up in running the test cases AFAIK.Would downgrading Babel solve it temporarily?On 11 Jan 2024, at 10:37, Victor Blagomir @.> wrote:
npm run desktop result:
ERROR  electronApp:  error while transpiling or minifying:  TypeError: api.caller is not a function
at builder @./preset-env/src/index.ts:390:13)
at @./helper-plugin-utils/src/index.ts:62:12
at ElectronApp.transpileAndMinify @./meteor-desktop/lib/electronApp.js:854:33)
at ElectronApp.build @./meteor-desktop/lib/electronApp.js:451:24)
at MeteorDesktop.run @./meteor-desktop/lib/index.js:123:9)
INFO  electronApp:  packing .desktop to asar
VERBOSE  electronApp:  clearing temporary .desktop
INFO  meteorApp:  checking for any mobile platform
INFO  meteorApp:  building meteor app
DEBUG  meteorApp:  clearing build dir
INFO  meteorApp:  acquiring index.html
ERROR  meteorApp:  error while trying to download index.html for web.cordova, be sure that you are running a mobile target or with --mobile-server:  TypeError: The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received type boolean (false)
at Object.writeFileSync (node:fs:2362:5)
at MeteorApp.copyBuild @./meteor-desktop/lib/meteorApp.js:657:20)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at MeteorApp.build @./meteor-desktop/lib/meteorApp.js:856:17)
at ElectronApp.getMeteorClientBuild @./meteor-desktop/lib/electronApp.js:553:9)
at ElectronApp.build @./meteor-desktop/lib/electronApp.js:464:13)
at MeteorDesktop.run @.***/meteor-desktop/lib/index.js:123:9) {
code: 'ERR_INVALID_ARG_TYPE'
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Has anyone been able to find a solution to this yet?
I am also trying to upgrade after having issues with 3.1.0 that (I assume due to babel/present-env) was converting js classes into functions and breaking when class inheritance was used. Not sure how much related to this issue with preset-env is.

Getting the same with 3.2 and a different kind of error with 3.1 - but excited to see this is working! I just updated Color Schemer to 2.16 and it was running at least for development.
Does anyone know what the last working versions of Meteor x Meteor-Desktop were?

Getting the same with 3.2 and a different kind of error with 3.1 - but excited to see this is working! I just updated Color Schemer to 2.16 and it was running at least for development.
Does anyone know what the last working versions of Meteor x Meteor-Desktop were?

3.2 works fine for me with Meteor 2.16. I haven’t tested it on 3.0x RC? yet.

@a4xrbj1 nice, and you are able to build a Mac app?
So far, I am able to run but not build

Mac, Windows and Linux, yes
On Thu, 20 Jun 2024 at 03:02, Max Savin @.***> wrote:

@a4xrbj1 https://github.com/a4xrbj1 nice, and you are able to build a
Mac app?
So far, I am able to run but not build
—
Reply to this email directly, view it on GitHub
https://github.com/Meteor-Community-Packages/meteor-desktop/issues/37#issuecomment-2179326192,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADHGCE6HS5KA523EHDXB7MDZIHIV7AVCNFSM6AAAAABBVXVRP6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZZGMZDMMJZGI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Oh wow, sounds too good to be true. Can you share your package.json and
desktop settings file? Would really appreciate it as I haven’t been able to
update this app in years
On Wed, Jun 19, 2024 at 3:59 PM Andreas West @.***>
wrote:

Mac, Windows and Linux, yes
On Thu, 20 Jun 2024 at 03:02, Max Savin @.***> wrote:

@a4xrbj1 https://github.com/a4xrbj1 nice, and you are able to build a
Mac app?
So far, I am able to run but not build
—
Reply to this email directly, view it on GitHub
<
https://github.com/Meteor-Community-Packages/meteor-desktop/issues/37#issuecomment-2179326192>,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ADHGCE6HS5KA523EHDXB7MDZIHIV7AVCNFSM6AAAAABBVXVRP6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZZGMZDMMJZGI>

.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/Meteor-Community-Packages/meteor-desktop/issues/37#issuecomment-2179387642,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPP5A6AL4I3SMMCW5RFJ23ZIHPLHAVCNFSM6AAAAABBVXVRP6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZZGM4DONRUGI
.
You are receiving this because you commented.Message ID:
@.***>

3.2 works fine for me with Meteor 2.16. I haven’t tested it on 3.0x RC? yet.

@a4xrbj1 are you sure 3.2 is working?  I'm trying it with Meteor 2.1.6, and getting the api.caller() is not a function error.
I thought it was working to start with, but then I made a trivial change to my desktop.js file (triggering a change in the desktop hash and a re-build), then I get this error.
@iokill I've tried your 'dirty' fix from dupe #38 by using your branch meteor npm install -D https://github.com/innerspacetrainings/meteor-desktop#preset-env-hotfix and I still get the same error.
In the meantime, 3.1.1 appears to be be working for me so far...

Why would I say it’s working when it’s not? Not sure why you question what I write but as I’ve written before, we’re using Meteor desktop since years and version 3.2 works fine, we distribute apps for all 3 OS to our users regularly.

On 13 Aug 2024, at 06:29, wildhart @.***> wrote:
3.2 works fine for me with Meteor 2.16. I haven’t tested it on 3.0x RC? yet.
@a4xrbj1 https://github.com/a4xrbj1 are you sure 3.2 is working? I'm trying it with Meteor 2.1.6, and getting the api.caller() is not a function error.
I thought it was working to start with, but then I made a trivial change to my desktop.js file (triggering a change in the desktop hash and a re-build), then I get this error.
@iokill https://github.com/iokill I've tried your 'dirty' fix from dupe #38 https://github.com/Meteor-Community-Packages/meteor-desktop/issues/38 by using your branch meteor npm install -D https://github.com/innerspacetrainings/meteor-desktop#preset-env-hotfix and I still get the same error.
In the meantime, 3.1.1 appears to be be working for me so far...

Why would I say it’s working when it’s not? Not sure why you question what I write.

The only reason I questioned it was because, as I wrote, it appeard to be working for me until I made a change to my desktop.js file causing it to be recompiled.  Before that the cached desktop build was was working fine.
That's great that it's working for you, and sorry if you took offence at my questioning it.
Would you mind sharing your package.json and desktop settings?  You appear to be the only person in this thread for whom it is working.

package.json:
"dependencies": {
@./client-s3": "3.565.0",
@./client-sso-oidc": "3.565.0",
@./client-sts": "3.565.0",
@./runtime": "^7.25.0",
@./browser-logs": "^5.23.3",
@./ddp-graceful-shutdown": "^0.9.2",
"animate.css": "^4.1.1",
"bcrypt-nodejs": "0.0.3",
"body-parser": "^1.20.2",
"bootstrap": "^3.3.7",
"bootstrap-tourist": "^0.3.2",
"bowser": "^2.11.0",
"clipboard": "^2.0.11",
"crypto": "^1.0.1",
"d3": "^7.9.0",
"d3-cloud": "^1.2.7",
"d3-hierarchy": "^3.1.2",
"d3-request": "^1.0.6",
"d3-selection-multi": "^1.0.1",
"dayjs": "^1.11.12",
"electron": "17.4.11",
"electron-builder-squirrel-windows": "24.13.3",
"electron-updater": "^6.2.1",
"eslint-plugin-react-hooks": "^4.6.2",
"fake-uagt": "^1.1.1",
"font-awesome": "^4.7.0",
"fs-js-lite": "^2.6.6",
"jquery-bridget": "^3.0.1",
"knox": "^0.9.2",
"labelauty": "^1.1.3",
"lazysizes": "^5.3.2",
"leaflet": "^1.9.4",
"leaflet.markercluster": "^1.5.3",
"libnpx": "^10.2.4",
"masonry-layout": "^4.2.2",
"meteor-node-stubs": "^1.2.9",
"ngraph.graph": "^20.0.1",
"ngraph.svg": "^0.0.17",
"owl.carousel": "^2.3.4",
"popper.js": "^1.16.1",
"qs": "^6.13.0",
"request": "^2.88.2",
"toastr": "^2.1.4",
"underscore": "^1.13.7",
"update-notifier": "^6.0.2",
"velocity-animate": "^1.5.2",
"velocity-ui-pack": "^1.2.2"
},
"devDependencies": {
@./core": "^7.25.2",
@./eslint-parser": "^7.25.1",
@./notarize": "^2.3.2",
@./osx-sign": "^1.3.1",
@.***/meteor-desktop": "3.2.0",
"electron-builder": "^24.13.3",
"electron-packager": "^17.1.2",
"electron-rebuild": "^3.2.9",
"eslint": "^8.57.0",
"eslint-config-airbnb": "^19.0.4",
"eslint-import-resolver-meteor": "^0.4.0",
"eslint-plugin-import": "^2.29.1",
"eslint-plugin-jsx-a11y": "^6.9.0",
"eslint-plugin-meteor": "^7.3.0",
"eslint-plugin-react": "^7.35.0",
"nock": "^13.5.4"
}
Our desktop.js has a lot of app specific code and I don’t think it’s relevant for your problem. Check which versions we’re using in regards to Babel, that will be most likely the area where the difference lies.
In regards to questioning, if something doesn’t work for you but someone else writes that it works for them, you should question your own code base, not what the other person is stating.

On 13 Aug 2024, at 13:25, wildhart @.***> wrote:
Why would I say it’s working when it’s not? Not sure why you question what I write.
The only reason I questioned it was because, as I wrote, it appeard to be working for me until I made a change to my desktop.js file causing it to be recompiled. Before that the cached desktop build was was working fine.
That's great that it's working for you, and sorry if you took offence at my questioning it.
Would you mind sharing your package.json and desktop settings? You appear to be the only person in this thread for whom it is working.
—
Reply to this email directly, view it on GitHub https://github.com/Meteor-Community-Packages/meteor-desktop/issues/37#issuecomment-2285364089, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADHGCEZKUHAVDCY6X35F2TLZRGKGNAVCNFSM6AAAAABBVXVRP6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBVGM3DIMBYHE.
You are receiving this because you were mentioned.


feat(#303): Default Environment

Add environment to the presets tab which will set the default environment on opening a collection. Show default environment inside of environment selector. Also add cli support for default environments.
Description

This is to fix #303 by adding the property called environment inside of Collection > Presets. The collection descriptor file, bruno.json will now have the preset structure of:
{
  "presets": {
     "defaultUrl": "",
     "defaultRequestType": "",
     "environment": null
  }
}

The preset environment will only change the environment under these conditions:

The collection is first being opened
The collection is being opened again and the current session had the environment set to No Environment (if its something else then it won't set the environment)

In the future we can rely on something like lastEnvironment to override the preset environment if people set it in their preferences.
https://github.com/usebruno/bruno/assets/115114979/09145231-3f86-48be-9af7-0bf5e65df067
The environment selector now has a helpful indicator showing what the preset environment is by the yellow (Default) value at the end of it. Any old collections that don't have a preset environment or the environment can't be found in the current list of environments will default to No Environment insuring that nothing breaks.
Some behavior that I need some guidance on @helloanoop, would be the formatting of (Default) indicator and whether to have it display next to No Environment if an environment preset is defined but not found. Currently I am setting it to No Environment in the environment selector and showing an error message on collection open when environment can't be found.
Now Bruno cli will try to look for the new environment preset value and set it as the environment if none is given.

I think this is a very helpful QOL change that will make opening and testing APIs a quick and easy process.
Contribution Checklist:

[x] The pull request only addresses one issue or adds one feature.
[x] The pull request does not introduce any breaking changes
[x] I have added screenshots or gifs to help explain the change if applicable.
[x] I have read the contribution guidelines.
[x] Create an issue and link to the pull request.

Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.
Publishing to New Package Managers
Please see here for more information.

I personally would like something like this, is there any plans to incorporate such functionality? @helloanoop


Fourier-DeepONet's dataset

Hello, I recently read one of your research papers. Could you please provide the data set for FWI-F?
I wish you all the best in your work!

The release of any dataset requires approval from LANL, so we are currently unable to release it. However, you can generate the FWI-F by utilizing the OpenFWI velocity model and performing seismic forward modeling with a random frequency range of 5 to 25 Hz.


(#RICEMAN) gen9ggsp: unban zacian

#RICEMAN: "unban zacian"
Created via Iolanthe on Tue, 16 Jul 2024 00:22:53 GMT.

Superseded by https://github.com/OperationTourCode/OTC/pull/520


Use int64. Accept any integer value in New.

I also noted that the m.assertSameCurrency(om) calls in the Add and Subtract methods do nothing, as the error response is ignored, and the methods themselves do not return an error.

Thanks @tylerb,
PR looks nice, I'm really happy this is one. 👍
Before merging to master README should be updated.
I could create release branch and take care of README or if you have spare time please update PR I will be really thankful, please let me know.

I also noted that the m.assertSameCurrency(om) calls in the Add and Subtract methods do nothing, as the error response is ignored, and the methods themselves do not return an error.

oh, damn, I will take care.
Thank you so much!

I won't have time to update the README for a while. Very busy the next few days. If you could merge it and then update the README, I'd appreciate it. Thanks!

@Rhymond any chance of getting this merged in the next little bit? I'm diving into this project on my end, and I really want to use your package to handle these new money calculations.

@tylerb I will do it today

Thanks!
On Apr 18, 2017, 9:57 AM -0600, Raimondas<EMAIL_ADDRESS>wrote:

@tylerb (https://github.com/tylerb) I will do it today
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (https://github.com/Rhymond/go-money/pull/12#issuecomment-294890672), or mute the thread (https://github.com/notifications/unsubscribe-auth/AAEUlAeFGZHY5iOS-62f8PdsJTU8-G3uks5rxN1ogaJpZM4M96cw).


Secretless has a Cassandra DB connector

Objective
Adds a Cassandra DB connector to Secretless, so it can proxy connections to a Cassandra backend.
Feature Overview
Details TBA, but Cassandra apparently ships with the AllowAllAuthenticator on by default and support for a PasswordAuthenticator in the default distribution (see here for more info)
If this connector is interesting for you, please share info about the Cassandra DB versions you're using, the authentication mode your server is configured with, and the client you're using to connect to it.
AC:

[ ] Secretless can proxy Cassandra PasswordAuthenticator-based auth
[ ] There are tests for this functionality

Story Breakdown
To be added. Will include handler, tests, documentation, etc.

Did a demo for Centene (https://www.centene.com/) today and they were asking about AWS-hosted DBs like Cassandra and RDS instance types. We're not in an active sales-cycle with them, just a datapoint.

@jodyhuntatx we do our XA and performance testing against RDS instances, so we've already tested with PostgreSQL, MySQL, and MSSQL!

Last Friday, I spent some time exploring possible implementations of Cassandra support for Secretless-Broker. This is what I found!

There exists a third-party driver, GoCQL, that is fairly comprehensive in its implementation of the Cassandra protocols. I forked it here: https://github.com/BradleyBoutcher/gocql
When exploring this repository, I think we can focus our attention on conn.go and conn_test.go. This module contains a majority of the methods we would need for creating and authenticating a connection.
The driver has a nice baked-in implementation of SSLOptions you can see below. EnableHostVerification in particular will be helpful, as we had to create a solution for this exact issue ourselves in MsSQL.

type SslOptions struct {
	*tls.Config

	// CertPath and KeyPath are optional depending on server
	// config, but both fields must be omitted to avoid using a
	// client certificate
	CertPath string
	KeyPath  string
	CaPath   string //optional depending on server config
	// If you want to verify the hostname and server cert (like a wildcard for cass cluster) then you should turn this on
	// This option is basically the inverse of InSecureSkipVerify
	// See InSecureSkipVerify in http://golang.org/pkg/crypto/tls/ for more info
	EnableHostVerification bool
}

Overall, I think this would be something we could reasonably implement.
I made a branch called cassandra-support that can be used if anyone else wants to dig in. The local version of the forked repo sits inside our third_party directory as a submodule, so we can make changes as needed for now.

Nice find @BradleyBoutcher! I'm glad to see the library you found uses BSD 3-clause, which allows code modifications and distribution. Thanks for looking into this - if you get to the point of getting e2e with an initial version of this, that'd be cool!


problem when change locale

New Issue Checklist

I have read the guidelines for contributing and I understand:

[x] My issue is happening in the latest version of SideMenu.
[x] My issue can not be answered on stackoverflow.com.
[x] My issue was not solved in the README.
[x] My issue is not a request for new functionality that I am unwilling to build and contribute with a pull request.
[x] My issue is reproducible in the demo project.

Issue Description

When I change locale, Instead of opened from left to right, It open up from the bottom up.
and print log -> 'SideMenu Warning: menuLeftNavigationController cannot be modified while it's presented.'
What is the problem?

Please follow the README carefully.

I read the document well, but I did not notice the problem.

This is not a problem in the demo project. You've missed a step in the README.

It works normally right. Only when change locale, opens the menu from bottom to top

If you can make minimal changes to the Example project that demonstrate this is a true bug in SideMenu and share that modified project, I'll take a look.

SideMenu-master 2.zip
I made changes to the example file
The project is attached

What are the steps to demonstrate the problem?

This is not an issue with SideMenu.
You're asking me to support a locale switcher library. SideMenu is not guaranteed to work with other libraries.
The locale switcher that reloads the application is strange and not properly releasing the view controllers in the stack, which is why you are getting the error message.

There is no problem if we put locale change button on the home screen
It only creates a problem when put locale change button on the menu
So the problem is custom locale lib?

@maebrahimi you need to investigate this further on your own to find out what the source of the problem is.

Thank you for the help me

You're changing the app's root view controller. Read up and make sure you understand what's going on there.


fix: change moduleName -> mockModuleName

This fixes the following error, i.e. #216, which should still be open:
the module factory of `jest.mock()` is not allowed to reference any out-of-scope variables.     Invalid variable access: moduleName

This fixes #216 for me using TypeScript using @latest for all libraries (i.e. next-11.0.2) in a TypeScript environment.
There would seem to be something "lost in translation" between the .ts -> .js with types.d.ts conversion for the npm package.
This solution comes from a monkey-patch, but it's a simple refactor of one variable name on 4 lines, so it should be good to go.

What kind of change does this PR introduce?
Bug fix for breaking bug on current npm package version<EMAIL_ADDRESS>installed with npm install --save-dev next-page-tester --force.
What is the current behaviour?
Same as closed #216. Given the complexity of this project, it's difficult to provide a minimal repo, but here you go.
Repository: @DoctorDerek/calendar-appointments
Branch: next-page-test-bug
Link: https://github.com/DoctorDerek/calendar-appointments/tree/next-page-test-bug
Repo instructions

Clone the repo's next-page-test-bug branch
npm install --force
npm run test
View error
...
Profit

Note that --force is required because of the peerDependency inaccuracy (^10...) in next-page-test ... I didn't want to fix that in the same PR because it is potentially confusing. There shouldn't have been any breaking changes with Next 11, that I could tell, though.
Monkey patch instructions:
// Change lines 96-103 in /node-modules/next-page-test/dist/utils.js to:
function preserveJestSharedModulesIdentity(modules) {
    for (const mockModuleName of modules) {
        // @NOTE for some reason Jest needs us to pre-import the modules
        // we want to require with jest.requireActual
        require(mockModuleName);
        jest.mock(mockModuleName, () => jest.requireActual(mockModuleName));
    }
}

What is the new behaviour?
It works.
Does this PR introduce a breaking change?
No.
Other information:
Please check if the PR fulfills these requirements:

[ N/A ] Tests for the changes have been added
[ N/A ] Docs have been added / updated

Coverage remained the same at 100.0% when pulling bb5dd1b61ab01029247075a78ace72f2e16e0eae on DoctorDerek:patch-2 into 30e1273ac09e9822abdffd76b564667654de5ff9 on toomuchdesign:master.

I honestly don't know what's happening in Jest for that error message to appear. BTW this seems what Jest suggests in order to silence the error. Thanks @DoctorDerek 👍

@all-contributors please add @DoctorDerek for bug and code


Url Error

I cant type urls on the chat bar but ''mojang'' option works

I also have this issue. I think there is something with the url special character escaping? It works if you enclose the url in double quotes
"<url>"


[Question] Community Meeting?

What happened:
Nothing happened, just a question 😄
Is there OpenYurt community meeting taking place local or global?
What you expected to happen:
Community meeting ? Sharing experience ? anything related to OpenYurt 👍
How to reproduce it (as minimally and precisely as possible):
Just be online 😮💨  ❓
others
/kind question

@fujitatomoya Yes, there is an OpenYurt community meeting every Wednesday at 11:00 AM(beijing time),  but the language of the meeting is still Chinese.
The meeting info is here: https://github.com/openyurtio/openyurt#meeting
btw: in the community meeting, we are sharing the status of every SIGs in OpenYurt(https://github.com/orgs/openyurtio/projects), meanwhile, we also discuss proposals or some code details of OpenYurt.

there is an OpenYurt community meeting every Wednesday at 11:00 AM(beijing time), but the language of the meeting is still Chinese.

I see, that is something I cannot do ... or I study Chinese 😄
anyway we have some members in Shanghai, so they might be able to attend.

there is an OpenYurt community meeting every Wednesday at 11:00 AM(beijing time), but the language of the meeting is still Chinese.

I see, that is something I cannot do ... or I study Chinese 😄
anyway we have some members in Shanghai, so they might be able to attend.

@fujitatomoya welcome shanghai members to attend OpenYurt community meeting.


Laravel 5.2 value of the search query

Is there way to access the value of the search query directly in stead of using the {{{q}}} option is this does not work with Laravel 5.2 blade templates.

So far i have got it working if a put set value in but for the life of me do not seem to be able to access the search box input text. I know its something glaringly obvious but I just cant see it.
$('#addSystems #system').selectpicker({         liveSearch: true,         bindEvent: 'keyup paste'     }).ajaxSelectPicker({         ajaxOptions: {             url: '/sys-l',             type: 'GET',             dataType: 'json',             headers: {                 'X-CSRF-Token': $('#_token').val(),             },             data: function () {                 var params = {                     system:  $('#addSystems #system').selectpicker().find('.bs-searchbox input').val()                 };                 return params;             },             beforeSend: function (xhr, opts) {                 if ($('#addSystems #system').selectpicker().find('.bs-searchbox input').val() < 3){                     xhr.abort ();                 }             }             },             emptyRequest: true,             locale: {                 emptyTitle: 'Search for system...'             },             preprocessData: function(data){                 return data;             },             preserveSelected: false         });

@hybrid1969 try:
$('#addSystems #system).data().selectpicker.$searchbox.val();

That was it, very much appreciated.


Fix typo in Discard model

I accidentally called it Discards instead of Discard, which broke stuff because it doesn't match the name of the serializable. Whoops!!

this did not cause the error we're currently struggling with, so this can wait and merge with the rest of the branch ive been working on


fix: bail out of gql migration if @auth uses queries/mutations

Codecov Report

Merging #9004 (60a82d8) into master (489d784) will increase coverage by 0.09%.
The diff coverage is 92.22%.

@@            Coverage Diff             @@
##           master    #9004      +/-   ##
==========================================
+ Coverage   55.56%   55.65%   +0.09%
==========================================
  Files         873      872       -1
  Lines       48783    48802      +19
  Branches     9704     9709       +5
==========================================
+ Hits        27105    27163      +58
+ Misses      20801    20762      -39
  Partials      877      877

Impacted Files
Coverage Δ

...tion/src/provider-utils/awscloudformation/index.ts
13.15% <0.00%> (ø)

packages/amplify-cli-core/src/cfnUtilities.ts
13.33% <0.00%> (ø)

...amplify-cli-core/src/feature-flags/featureFlags.ts
80.93% <ø> (ø)

...r-awscloudformation/src/amplify-service-manager.js
5.85% <0.00%> (ø)

...r-awscloudformation/src/amplify-service-migrate.js
10.84% <0.00%> (ø)

...y-provider-awscloudformation/src/push-resources.ts
17.39% <0.00%> (-1.05%)
:arrow_down:

...lify-cli/src/domain/amplify-usageData/UsageData.ts
94.82% <33.33%> (-3.36%)
:arrow_down:

...s/awscloudformation/utils/cloudformationHelpers.ts
12.06% <40.00%> (-0.22%)
:arrow_down:

...ansformer-migrator/src/migrators/auth/ownerAuth.ts
85.29% <91.30%> (+59.57%)
:arrow_up:

...aphql-transformer-migrator/src/schema-inspector.ts
98.24% <91.66%> (+7.13%)
:arrow_up:

... and 32 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8ea9e9d...60a82d8. Read the comment docs.


[docker] bump neuron version to 2.20.0 SDK

Description
Update to Neuron 2.20.0 SDK for LMI Neuron

If this change is a backward incompatible change, why must this change be made?
Interesting edge cases to note here

Version numbers for the SDK can be confirmed here https://awsdocs-neuron.readthedocs-hosted.com/en/latest/release-notes/index.html#latest-neuron-release


label-signee, label-timestamp and label-hint options seems to not working in the config file.

Hello,
if i specify  --label-signee xxxxx --label-timestamp yyyyy --label-hint zzzzzz in the command line,  this works.
however if i specify this options in the yaml config file , as this:
label-signee: xxxxx
label-timestamp: yyyyy
label-hint: zzzzzz
this is not working, and i get the default messages ( Signee, Timestamp and Hint )
other options  ( hint, image, certificate, keys, page, width etc) ,  are working in the config file.
is it possible to specify these options in config ?
best regards.

After looking at the code,   i answer to my own question !
in the config file,   the options are :  labelSignee, labelTimestamp, labelHint.
sorry, i should have search before creating the issue.


Update to use log4j 2 for security compliance

Describe the bug
This project still depends on log4j 1.2,  which contains some security issue.
To Reproduce
GitHub detect it and send the triggers security alert.
Expected behavior
Should see any security alerts for this project.
Environment (please complete the following information):

OS: All
Java version:  All
TA-SDK Version: 0.5.1

Additional context
N/A
Screenshots
If applicable, add screenshots to help explain your problem.

change delivered.


Confirm why perpendicular baseline is negative in some cases

See the discussion here: https://github.com/ASFHyP3/hyp3-isce2/pull/61#discussion_r1203083603

comparing the meta.txt files produced by hyp3-isce2 and hyp3-gamma for the pair:
S1A_IW_SLC__1SDV_20190610T015047_20190610T015114_027611_031DB6_D8FA
S1A_IW_SLC__1SDV_20190622T015048_20190622T015115_027786_0322F1_7A8E,  I found that hyp3-isce2 reports the Perpindicular Baseline: -14.321817636040937, and hyp3-gamma reports the Baseline: -14.845.


Add missing or update all current diagrams in the SRS

what do we need to update?

The .env file
On Jul 10, 2016 5:00 PM, "habibmn09"<EMAIL_ADDRESS>wrote:

what do we need to update?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/157#issuecomment-231610614,
or mute the thread
https://github.com/notifications/unsubscribe/AMuN2KmCPc8pl_Hcubqwt_2WXpoNc2UEks5qUV2CgaJpZM4JEWgd
.

the diagrams are out of date, please look at the app and code to determine updates where needed

some of the diagrams were not correct to begin with, and I left comments for you to correct them, many weeks ago, but you did nothing


loosen the type of AWSPreparedRequest's body argument

Referencing the implementation of of its reset_stream() method shows they're expecting to handle a broad range of body objects
https://github.com/boto/botocore/blob/4b728545d43ff70287ae1d0dce42e995790e6b85/botocore/awsrequest.py#L518

Published botocore-stubs 1.33.7.post1 with3 the fix included.


feat(fmt): add the alloy formatter to vscode-alloy

Added the scaffolding for a standard extension (https://code.visualstudio.com/api/get-started/your-first-extension)
Registered a formatter with the formatter API (https://code.visualstudio.com/blogs/2016/11/15/formatters-best-practices)

It's pretty basic, in that when the format command is called for a grafana-alloy file, it runs alloy fmt -w <file path>. That's it. It works on my machine, and I'm not sure how to test it, but more than happy to change things to follow any conventions, I'm fairly new to TS. Cheers!

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


New version: Cuba_jll v4.2.0+2

Autogenerated JLL package registration

Registering JLL package Cuba_jll.jl
Repository: https://github.com/JuliaBinaryWrappers/Cuba_jll.jl
Version: v4.2.0+2

Pause, I need to do some tests


[EN] Feedback for: /web/tools/chrome-devtools/?hl=en

Could you put an option in so the developer can choose whether to escape carriage returns and newlines sent to the console?  Right now they are escaped by default with no other option.  Thanks.

Hi! Sorry, our Git repo is meant for issues with content on the site. Check out https://developer.chrome.com/devtools/docs/contributing for how to ask questions or file issues on DevTools.


App layout design programmatically using Matlab

Topic Suggestion
App layout design programmatically using Matlab
Writing sample(s):
https://www.section.io/engineering-education/image-processing-using-matlab/
App layout design programmatically using Matlab
Proposed article introduction
The app layout is the structure that interfaces the user with the app. The app consists of figures, these figures contain one or more UI(user interface). The UI components hold the interactive parts used while operating the app.
In Matlab, apps can be designed using GUI(graphical user interface) or programmatically using Matlab functions. This article will discuss designing app figure layout programmatically using Matlab functions. Through these functions, app UI components like buttons, dialog boxes, and containers can be made.
Apps are used in day-to-day activities in making life easier, they can be used in communication, data processing, and entertainment purposes.
Key takeaways

Creating app layout using matlab functions.
Understanding the basic components of uifigure based apps.
Understanding of uifigure function operations.

Article quality
The most obvious way of designing an app layout in matlab is by using the App designer or GUI(graphical user interface). This article discusses designing app layout through coding using matlab functions.

Great topic 🚀 , make sure it matches the following:

Adds value beyond what is in the official docs and what is covered in other blog sites.
To avoid potential article closure, it should not overlap with existing EngEd articles or incoming topic suggestions.

Please reference any relevant EngEd articles in yours and build a unique project - Approved.


Link VS code to cloud account

Link VS code to a cloud account (same as visual studio) to sync the configurations and extensions between different machines.

/duplicate of https://github.com/microsoft/vscode/issues/2743


Retrieving even a single iOS ECG measurement w/ voltage data causes app to crash

Hi there, thanks so much for the fantastic package!!
I am trying to retrieve iOS ECG data including voltage information within my Flutter app.
Sadly the app crashes when I try to retrieve just a single ECG reading. I have tracked them back and they crash within the Swift file at the line let voltageQuery = HKElectrocardiogramQuery(ecgSample) { (query, [result][1]) in ie. when it's actually retrieving the data (relevant Apple documentation here).
Whenever I do it, I get the memory error:
* thread #3, queue = 'com.apple.HealthKit.HKHealthStore.client.0x281d32630', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
    frame #0: 0x0000000000000000
error: memory read failed for 0x0
Target 0: (Runner) stopped.

I get the same error on both an iPhone 7 and iPhone 11 (both running min. iOS 14) using various different readings.
Does anyone know how to avoid this happening please?
I'm not sure if say there's a way to retrieve a part of a reading for example, as I think the app is just struggling to handle the size of variable.
Thanks a lot!

It sounds like you're encountering a memory access error when attempting to retrieve ECG data within your Flutter app using the health_kit plugin. Memory access errors like EXC_BAD_ACCESS typically occur when your app tries to access memory that it doesn't have permission to access or when attempting to access memory that has already been deallocated.
Here are a few steps you can take to troubleshoot and potentially resolve this issue:
Check Permissions: Ensure that your app has the necessary permissions to access health data, including ECG data, on the iOS device. You may need to request permission explicitly in your app's Info.plist file and handle permission requests properly in your Flutter code.
Verify Data Retrieval: Double-check that your code for retrieving ECG data is correct and properly configured. Make sure you're using the correct APIs and following Apple's guidelines for querying health data, as outlined in the relevant documentation.
Error Handling: Implement proper error handling in your code to catch and handle any exceptions or errors that may occur during data retrieval. This can help prevent crashes and provide more informative error messages for debugging purposes.
Memory Management: Review your code for any potential memory management issues, such as retaining references to objects unnecessarily or failing to release resources properly. Make sure you're following best practices for memory management in both your Flutter and Swift code.
Testing: Test your app on different iOS devices and iOS versions to see if the issue persists across different environments. This can help identify whether the problem is specific to certain devices or configurations.
Community Support: Consider reaching out to the Flutter community, such as forums, discussion groups, or GitHub repositories related to the health_kit plugin. Others may have encountered similar issues and can provide insights or assistance in troubleshooting the problem.
By carefully reviewing your code, verifying permissions and data retrieval mechanisms, implementing error handling, and testing across different environments, you should be able to identify and address the underlying cause of the memory access error in your Flutter app.

Hi there, thanks so much for the fantastic package!!
I am trying to retrieve iOS ECG data including voltage information within my Flutter app. Sadly the app crashes when I try to retrieve just a single ECG reading. I have tracked them back and they crash within the Swift file at the line let voltageQuery = HKElectrocardiogramQuery(ecgSample) { (query, [result][1]) in ie. when it's actually retrieving the data (relevant Apple documentation here).
Whenever I do it, I get the memory error:
* thread #3, queue = 'com.apple.HealthKit.HKHealthStore.client.0x281d32630', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
    frame #0: 0x0000000000000000
error: memory read failed for 0x0
Target 0: (Runner) stopped.

I get the same error on both an iPhone 7 and iPhone 11 (both running min. iOS 14) using various different readings.
Does anyone know how to avoid this happening please?
I'm not sure if say there's a way to retrieve a part of a reading for example, as I think the app is just struggling to handle the size of variable.
Thanks a lot!


Define Function

Function to look up the Miriam-Webster (or whomever) definition page for the word: !define(word)
Possibly add ability to search Urban Dictionary with a flag?

Done.
main


VM creation from template with auth mode HTTP

User should be able to see a modal dialog with a login, password and a link to the specified url and be able to open it.


Wiki page "How to include Material" is outdated

Whe wiki page How to include Material seems to be outdated.

Importing "MaterialModule" is deprecated

I'll be updating this and removing the branch


Change how alignment rules works

do not use ‘all’
belongsTo or constraints

Also included alignment for Slf4J 2.0.8+ based on the published BOM

With #81, the alignment rules are now also defined through an Enum, using similar structure as the capability rules.
We can use this to add more alignment in the future and address #22.


Response fuzzing is too slow.

[x] Why?
[x] Feature gate complex Arbitrary implementations

Feature-gating the more complex Arbitrary implementations increases fuzzing throughput by a factor of 4 to 5. We should still improve the implementations. But keeping the feature seems like a good idea.


Enhancement: Minify CSS when adding adding a CSS Preprocessor such as Sass

Enhancement: Request for pull request
Add command to minify CSS when adding Adding a CSS Preprocessor (Sass, Less etc.) to your Create React App.
Currently
When adding a CSS preprocessor, the addition of the following script lines produces an App.css file that is not minified.
   "scripts": {
+    "build-css": "node-sass-chokidar src/ -o src/",
+    "watch-css": "npm run build-css && node-sass-chokidar src/ -o src/ --watch --recursive",
     "start": "react-scripts start",
     "build": "react-scripts build",
     "test": "react-scripts test --env=jsdom",

I'd like to propose adding a line to let developers know that they can simply add --output-style compressed to the watch-css line if someone would like to minify their compiled scss.

Thanks! Closing this in favor of the PR.