Orders closing in negative after reaching sell trigger.

Bot is selling at negative values, twice the last month. 20% loss even when the bot reached the threshold to trigger trail. Some of my trades have been successful, but two in BTCUSDT have been very bad. I haven't enabled stop loss. The following settings however are used:
Trigger percentage based on the last buy price 1.05
Stop price percentage 0.98
Limit price percentage 0.975
Sell quantity percentage for USDT 1
Sell quantity percentage for BTC 1
Sell quantity percentage for BUSD 1
This is set after reading the Wiki description of the sell scenario many many times.
Version
Running Version: v0.0.96 (209d2e0)
Latest Version: [v0.0.96]
Expected Behaviours
Sell in profit...
Screenshots

Also after buying the tokens back as I don't want to lose dollars on this trade, (as it was in profit...) it then bought the tokens back, but showed this which scared me so much (and also added all the value to a loss, thus -100% loss).
(13:39:09.430) BTCUSDT Manual BUY Order Filled: LIMIT

Order Result:
{
"symbol": "BTCUSDT",
"orderId":<PHONE_NUMBER>6,
"orderListId": -1,
"clientOrderId": "zRdVmKP2ZbFIUXkr9nBlPe",
"transactTime":<PHONE_NUMBER>398,
"price": "18106.30000000",
"origQty": "0.00500000",
"executedQty": "0.00500000",
"cummulativeQuoteQty": "90.53150000",
"status": "FILLED",
"timeInForce": "GTC",
"type": "LIMIT",
"side": "BUY",
"workingTime":<PHONE_NUMBER>398,
"fills": [],
"selfTradePreventionMode": "NONE",
"stopPrice": "0.00000000",
"isWorking": false,
"updateTime":<PHONE_NUMBER>111
}
Current API Usage: 40

(13:39:10.158) BTCUSDT Action - Removed last buy price:

Message: Balance is not enough to sell. Delete last buy price.
{
"lastBuyPrice": 18106.3,
"baseAssetQuantity": 0.00001,
"minQty": "0.00001000",
"baseAssetFreeBalance": "0.00001423",
"baseAssetLockedBalance": "0.00000000",
"totalBaseAssetBalance": 0.00001423,
"openOrders": [
{
"symbol": "BTCUSDT",
"orderId":<PHONE_NUMBER>6,
"orderListId": -1,
"clientOrderId": "zRdVmKP2ZbFIUXkr9nBlPe",
"price": "18106.30000000",
"origQty": "0.00500000",
"executedQty": "0.00000000",
"cummulativeQuoteQty": "0.00000000",
"status": "NEW",
"timeInForce": "GTC",
"type": "LIMIT",
"side": "BUY",
"stopPrice": "0.00000000",
"icebergQty": "0.00000000",
"time":<PHONE_NUMBER>398,
"updateTime":<PHONE_NUMBER>398,
"isWorking": true,
"workingTime":<PHONE_NUMBER>398,
"origQuoteOrderQty": "0.00000000",
"selfTradePreventionMode": "NONE",
"currentPrice": 18109.9,
"updatedAt": "2023-01-12T13:38:59.398Z"
}
]
}

Followed by a sell $-90 sell message that I already deleted.

Also I previously tried setting the following to positive values (which in my opinion would be logical, I want it to trigger at 5% and then close as lowest for example at 2% profit), but then it gave me errors that the trade would be executed immediately and nothing ever happened to the sell leading to missed opportunities.
Thus, instead of:
Stop price percentage 0.98
Limit price percentage 0.975
I previously had:
Stop price percentage 1.035
Limit price percentage 1.02

I think you are trading another BTC* pair and thus you are "stealing" BTC from BTCUSDT buy order when other pair trades are closed. You can't trade multiple symbols with the same asset.

Alright, that could well be the case since the initial config came with both XRPUSDT and XRPBTC I decided to give it a try as I thought it had the capability of doing this, but after understanding how it works with selling 100% and seeing why you chose this path instead of logging all the quantities (which maybe could be a good alternative functionality to 100%?) I guess it makes sense.
However, I'm still very confused about stop price and limit price after reading the documentation as well as the issues. Is it correct to set it to the proposed values from the docs if I want it to close at minimum at 2% profit?
Stop price percentage 0.98
Limit price percentage 0.975
Or is it possible to set:
Stop price percentage 1.035
Limit price percentage 1.02
I just don't want to get error again when it's time to trail next time, and neither a loss that could have been prevented by the right config.

However, I'm still very confused about stop price and limit price after reading the documentation as well as the issues. Is it correct to set it to the proposed values from the docs if I want it to close at minimum at 2% profit? Stop price percentage 0.98 Limit price percentage 0.975

It depends on your Trigger percentage. For example, if you trigger is set to 1.02 and limit is 0.98, then (rounded) your minimum profit will be 0%. Trigger price is value when the sell order is created and limit price is lowest price it can be sold for. That mean 1.02 x 0.98 = 0.9996.
If you want to sell at minimum 2% profit then you need to set for example 1.04 trigger percentage and limit 0.981. This will set minimum profit 1.04 x 0.98 = ~1.02.

Ok, great, thank you for the explanation.
However, this led to the new bug (let me know if you want a new issue or renaming this one) where it thought the manual trade buyback (with the "TRADE" button in the GUI) was thought to have 0 as buy price, which in turn led to a message of a loss of the whole value even if no sell trade happened (maybe lucky timing) as expected since I just bought in. Today I see that it sold and I was excited but confused when it said 100 USD profit. So I checked the trade log and see:

This happened even tho I adjusted the last buy price (which is required for it to sell at all).


⚠ Bofrost.at has degraded performance

In fb12d5a, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 3032 ms

Resolved: Bofrost.at performance has improved in 621bd28.


Video - redir5Gted2Gsm

Can you return the video "  https://youtu.be/L453KYMF7iM   "or place it on another resource?

Hello since this code has works only few times I prefer to not induce in error by sharing on YouTube. Will try to find another platform than YouTube to share. Thanks for interest, Bastien.

could you share any video demos?

I had one but since it work when it want (almost never) I have to review code first but when have time I will trySent from Android deviceLe 19 avr. 2023 04:01, SitrakaResearchAndPOC @.***> a écrit :
could you share any video demos?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

and how about the 5G to UMTS? is it stable? it's not difficult to run umts to GSM, I could share you the code!


Is there a way to use this in combination with vue-template-parser?

Currently my parser options are as follows:
parser: 'vue-eslint-parser',
parserOptions: {
    parser: '@typescript-eslint/parser',
    sourceType: 'module',
},

I was wondering if I could use html-eslint in order to use the rule element-newline

HI @LoiLock  Sorry for the late. Unfortunately All rules in html-eslint does not work with the vue-eslint-parser because the AST specs are different. 😢


[Bug]: Supabase db expose port

Description
I have deployed the supabase application, mostly with default settings.
In order to push db migrations from the location supabase instance, I need to specify the --db-url
supabase db push --db-url="postgres://postgre[...]

In order for this to work, I have to expose the db port in coolify.
In the DB container I have set a public port and checked the checkbox "Make it publicly available".
But the port is not exposed.  Also if I set a name for the container, it keeps the old
Minimal Reproduction (if possible, example repository)

Create supabase application
Go to Settings in DB container
Set public port
"Set Make it publicly available"

Exception or Error
Port not exposed
Version
v4.0.0-beta.265

Just found, that I can create destinations via Servers -> Destinations. But it is un-intuitive to not have this possibility from the side nav.

you can update the service compose yaml to expose the port

you can update the service compose yaml to expose the port

i have same issue . i tried to add ports in compose file but the coolify version dont have it .so the coolify parsing of the file is ignoring ports by default.
no other solutions?

make a new project and copy the docker compose yaml for supabase and add the ports

you can update the service compose yaml to expose the port

i have same issue . i tried to add ports in compose file but the coolify version dont have it .so the coolify parsing of the file is ignoring ports by default.
no other solutions?

i've managed to get it work that way:
    ports:
      - '5432:5432'

on the supabase-db service.

Having the same issue with the MongoDB service - checking the "publicly available" box doesn't open it on the specified port

I think once you select 'Make it publicly available' it creates an nginx docker container that does the forwarding (@andrasbacsai  correct me if I'm wrong :) ) - however, mine is stuck in a restarting loop (may or may not be the same sort of issue).
Before enabling

After enabling

logs error:
2024/06/07 11:01:58 [emerg] 1#1: invalid port in upstream "m0s8w4s:" in /etc/nginx/nginx.conf:12
nginx: [emerg] invalid port in upstream "m0s8w4s:" in /etc/nginx/nginx.conf:12

having the same problem here.

you can update the service compose yaml to expose the port

Yeah, but I would assume the UI checkbox would do the same.

I unchecked the make public box to avoid port conflict, then did this. it worked !

duplicate #3297

@andrasbacsai Is there solution for this? It prevents me from using Coolify for supabase and I wish i could standardize my infrastructure. I'm using separate Caddy server only for Supabase :(

@andrasbacsai Is there solution for this? It prevents me from using Coolify for supabase and I wish i could standardize my infrastructure. I'm using seaparate Caddy server only for Supabase :(

Duplicate of #3297. Please move to that issue for updates and discussions.

Duplicate of #3297. Please move to that issue for updates and discussions.


WebSocket connection Error

In chrome://extensions/?errors=onpiiolicjjcilbnkdgkajnpknndneom:
WebSocket connection to 'ws://localhost:8000/socketcluster/' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED

Do I have to run websocket server locally somehow? I just followed the installation steps:
npm install
npm run build
chrome://extensions
LOAD UNPACKED

FYI: I picked the directory <path>/hls-downloader-chrome-extension/build/ when loading unpacked extension. Since the readme doesn't mention which directory to load, I guess it's the build directory, but not sure.

Hi, it's caused by the remote redux Dev tools.
src/modules/store/index.js
const composeEnhancers = composeWithDevTools({ realtime: true, port: 8000 });

@puemos thank you very much for your quick reply. I am not a nodejs developer so I am not sure what the real problem is. Since you add a bug label here, does it mean I just need to wait until the bug gets fixed? :) thanks a lot.

yeah sure! probably this weekend

Solved!
you can ignore the error msg or use remotedev-server


{{changed_by}} is not always addressing the right user

Alarmo Version
V1.9.10
HA Version
2023.8.4
Bug description
I’m using Alarmo both with the HA app on iPhone and with a zigbee keypad. When I arm the alarm sometimes the wrong user is shown in the notification. Not every time but more often than not. It is also a random wrong user, not the same every time.
I have four users in Alarmo with different PIN codes and the problem is the same for all users. The problem is also the same using the app or the zigbee keypad. The {{changed_by}} wildcard is somehow not addressing the right user (the user with the used PIN code).
I’ve tried to delete users and add them again with new PIN codes but the problem persist.
Steps to reproduce
Setup notification with {{changed_by}} wildcard.
Arm the alarm with HA app on iPhone or zigbee keypad.
Relevant log output
No response

Close enough to my problem, as I wanna catch the user (state) reported by Yale that I use to control the alarm.
When unlocking with code on the Yale unit I suppose the notification in alarmo picks the state before Yale has a chance to change it. Maybe the possibility to add a delay for like 0,5-3 seconds could help? So that the state may change before the notification picks it.

I am unable to reproduce this issue.
I created 3 users with different pin code, and configure the alarm to require a code for arming.
Next I configured a notification using the changed_by wildcard.
For me, the wildcard is always showing the user corresponding to the entered code.
Do you have any further suggestions which could help me reproduce the issue?

Citgot uses a zigbee keypad and I uses a Yale lock to arm/disarm. So basically the alarmo works. But what’s needed is like a delay for a second or two before the notice goes out so that the state from the external units is able to be updated and received in alarmo.

@Tobbe82 the changed_by property is updated simultaneously with the state. I don’t see a reason for adding a delay somewhere.
Delaying the responsiveness of alarmo for all users is not a good idea anyway.
What is the bug here on the side of alarmo exactly? It is not clear for me.

On my end the problem seems to have gone away. Now it never shows the wrong user. I don’t know why it was showing the wrong user from the start but it sorted itself out after a week or so (with several reboots inbetween). You can close this issue
Sent from Proton Mail for iOS
Den 11 okt. 2023 kl 21:13, Niels Faber @.***(mailto:Den 11 okt. 2023 kl 21:13, Niels Faber < skrev:

@.***(https://github.com/Tobbe82) the changed_by property is updated simultaneously with the state. I don’t see a reason for adding a delay somewhere.
Delaying the responsiveness of alarmo for all users is not a good idea anyway.
What is the bug here on the side of alarmo exactly? It is not clear for me.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


feat: governance gated permissioning system that allows breaking locks

Background
This meta-issue is created for the purpose of tracking issues related to governance gated permissioning system that allows breaking locks. This is essential as a part of enabling the transmigrator contract
The following issues are issues that needs to be tackled in before marking this issue complete.

[ ] https://github.com/osmosis-labs/osmosis/pull/4252
[ ] https://github.com/osmosis-labs/osmosis/pull/5861

v17 blocking

[x] https://github.com/osmosis-labs/osmosis/issues/5898

Design doc owner: @mattverse

just making sure, does this feature allow "break classic pool locks &  superfluid locks, if they swap all the assets to OSMO and stake it"? or is this feature a pre-requisite?

Planning to have off-line meeting with Boss on this, will update design doc once things have been set

Re-opening this issue, the two subsequent PRs should be included in the next upgrade


chore: Migrate from TypeScript 4.9 to 5.2

An incremental step to bringing the workspace config more in line with TanStack Query. TS version is pinned so it doesn't auto update (TS doesn't use semantic versioning).

Does the project still build after this? Last time I tried this a few months ago, there was some roll-up incompatibility

Does the project still build after this? Last time I tried this a few months ago, there was some roll-up incompatibility

I tested yarn run pr locally (and it also seemed to work on CI). Do you know what was breaking?

@lachlancollins checked out your PR and yarn build is still fine. Don't remember what I ran into a few months ago.
I ran npx npm-check-updates -u -ws --root typescript to update to version 5.3.3 though and had the same success, so might as well upgrade to the latest


Fix serialization issue in the IMAP sensor

This pull request fixes #254.
The problem was that headers list variable items contained a class instance which wasn't available to the trigger consumers (e.g. rules engine) so de-serializing (unpickling) the payload would fail and throw an exception.
The fix is simple - I simply flatten the list and make sure each headers item (tuple) is a list.

@nido009 I verified the fix myself with the test message you sent me and it works fine, but it would also be good if you can verify the fix as well.
/cc @jfryman

I will also look if it's possible to fail early and throw on serialization (pickling) instead of only failing on de-seralization.

@Kami sorry, doesn't help:
==> /var/log/st2/st2sensorcontainer.log <==
Jul 30 19:19:31 localhost st2sensorcontainer[27304]: DEBUG<PHONE_NUMBER>75536 log [-] [IMAPSensor]: entering poll
Jul 30 19:19:32 localhost st2sensorcontainer[27304]: DEBUG<PHONE_NUMBER>75536 log [-] [IMAPSensor]: polling mailbox dummyhost_main
Jul 30 19:19:32 localhost st2sensorcontainer[27304]: DEBUG<PHONE_NUMBER>75536 log [-] [IMAPSensor]: Processing 1 new messages
Jul 30 19:19:32 localhost st2sensorcontainer[27304]: DEBUG<PHONE_NUMBER>75536 log [-] [IMAPSensor]: starting body handling
Jul 30 19:19:32 localhost st2sensorcontainer[27304]: DEBUG<PHONE_NUMBER>75536 log [-] [IMAPSensor]: after body handling
Jul 30 19:19:32 localhost st2sensorcontainer[27304]: DEBUG<PHONE_NUMBER>75536 log [-] [IMAPSensor]: after fetching attachments
Jul 30 19:19:32 localhost st2sensorcontainer[27304]: DEBUG<PHONE_NUMBER>75536 log [-] Dispatching trigger (trigger=email.imap.message,payload={'trigger': 'email.imap.message', 'payload': {'body': u'-- \r\nMit freundlichen Gr\xfc\xdfen\r\n\r\nNils Dohse\r\n-- \r\nK\xe4hlen 2\r\n24248 M\xf6nkeberg\r\nTel: 0176/81017178\r\n', 'to'<EMAIL_ADDRESS>'from': u'Nils Dohse<EMAIL_ADDRESS>'uid': 14, 'headers': [['Return-Path'<EMAIL_ADDRESS>['X-Original-To'<EMAIL_ADDRESS>['Delivered-To'<EMAIL_ADDRESS>['Received', u'from mail-lb0-f175.google.com (mail-lb0-f175.google.com [<IP_ADDRESS>])\tby pl2.addix.net (Postfix) with ESMTPS id 30D293FD9C\tfor<EMAIL_ADDRESS>Thu, 30 Jul 2015 21:19:23 +0200 (CEST)'], ['Received', u'by lbbyj8 with SMTP id yj8so33335262lbb.0        for<EMAIL_ADDRESS>Thu, 30 Jul 2015 12:19:22 -0700 (PDT)'], ['Dkim-Signature', u'v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com; s=20120113;        h=mime-version:date:message-id:subject:from:to:content-type;        bh=5x3sYL7LIHqGpF9xuWAof54hjZGy9BQMoMJj1XoLPeQ=;        b=wFSCBjMH0HDAVSOIRFMfkIgeELzkrNivfY23FdtQ2kbIqoYcMVueuh7MBva3DDpD09         O/daWA/02/nD+2PiydTpHtqaAJdi7a6VH3DTyTO8P+Re7gg+bICQ8VDrf0FI1+3hTxAG         fLpzC78AYHO8hdWr05Ez3EfjHhVVlCoQpbb/4XsxE0rhiB6H0CfakAMeO9A8chbO/JQ8         oiKYhQpIAW0DFknC6VaauttE2ylD9a+4Gjc9Dx16+cI87PaZ2yEjZ4f6m6CA4hy/U2Dd         1BPsi63ehJ0cY+4zfro+1pmIg4yPtevWP+2zDv+rZ0+1zn72QO35mVFOBeMdovYyG5Zg         /Ymw=='], ['Mime-Version', u'1.0'], ['X-Received', u'by <IP_ADDRESS> with SMTP id kt9mr40355683lac.99.1438283962773; Thu, 30 Jul 2015 12:19:22 -0700 (PDT)'], ['Received', u'by <IP_ADDRESS> with HTTP; Thu, 30 Jul 2015 12:19:22 -0700 (PDT)'], ['Date', u'Thu, 30 Jul 2015 21:19:22 +0200'], ['Message-Id'<EMAIL_ADDRESS>['Subject', u'test3'], ['From', u'Nils Dohse<EMAIL_ADDRESS>['To'<EMAIL_ADDRESS>['Content-Type', ContentType('multipart', 'alternative', {'boundary': u'001a11345984aff6f8051c1c94ec'})]], 'date': u'Thu, 30 Jul 2015 21:19:22 +0200', 'has_attachments': False, 'attachments': [], 'message_id'<EMAIL_ADDRESS>'subject': u'test3'}})
Jul 30 19:19:32 localhost st2sensorcontainer[27304]: DEBUG<PHONE_NUMBER>75536 connection [-] Start from server, version: 0.9, properties: {u'information': u'Licensed under the MPL.  See http://www.rabbitmq.com/', u'product': u'RabbitMQ', u'copyright': u'Copyright (C) 2007-2015 Pivotal Software, Inc.', u'capabilities': {u'exchange_exchange_bindings': True, u'connection.blocked': True, u'authentication_failure_close': True, u'basic.nack': True, u'per_consumer_qos': True, u'consumer_priorities': True, u'consumer_cancel_notify': True, u'publisher_confirms': True}, u'cluster_name': u'rabbit@st2express', u'platform': u'Erlang/OTP', u'version': u'3.5.4'}, mechanisms: [u'PLAIN', u'AMQPLAIN'], locales: [u'en_US']
Jul 30 19:19:32 localhost st2sensorcontainer[27304]: DEBUG<PHONE_NUMBER>75536 connection [-] Open OK!
Jul 30 19:19:32 localhost st2sensorcontainer[27304]: DEBUG<PHONE_NUMBER>75536 channel [-] using channel_id: 1
Jul 30 19:19:32 localhost st2sensorcontainer[27304]: DEBUG<PHONE_NUMBER>75536 channel [-] Channel open
==> /var/log/st2/st2rulesengine.log <==
Jul 30 19:19:32 localhost st2rulesengine[27105]: ERROR<PHONE_NUMBER>16784 mixins [-] Can't decode message body: DecodeError(ImportError('No module named flanker.mime.message.headers.wrappers',),) (type:u'application/x-python-serialize' encoding:u'binary' raw:''\x80\x02}q\x01(U\x07triggerq\x02U\x12email.imap.messageq\x03U\x07payloadq\x04}q\x05(U\x04bodyq\x06Xd\x00\x00\x00-- \r\nMit freundlichen Gr\xc3\xbc\xc3\x9fen\r\n\r\nNils Dohse\r\n-- \r\nK\xc3\xa4hlen 2\r\n24248 M\xc3\xb6nkeberg\r\nTel<EMAIL_ADDRESS>Dohse n.dohse@gmail.comq\x0bU\x03uidq\x0cK\x0eU\x07headersq\r]q\x0e(]q\x0f(U\x0bReturn-Pathq\x10X\x13\x00\x00\x00n.dohse@gmail.comq\x11e]q\x12(U\rX-Original-Toq\x13X\x10\x00\x00\x00st2@dummyhost.deq\x14e]q\x15(U\x0cDelivered-Toq\x16X\x10\x00\x00\x00st2@dummyhost.deq\x17e]q\x18(U\x08Receivedq\x19X\xbd\x00\x00\x00from mail-lb0-f175.google.com (mail-lb0-f175.google.com [<IP_ADDRESS>])\tby pl2.addix.net (Postfix) with ESMTPS id 30D293FD9C\tfor<EMAIL_ADDRESS>Thu, 30 Jul 2015 21:19:23 +0200 (CEST)q\x1ae]q\x1b(U\x08Receivedq\x1cXn\x00\x00\x00by lbbyj8 with SMTP id yj8so33335262lbb.0        for<EMAIL_ADDRESS>Thu, 30 Jul 2015 12:19:22 -0700 (PDT)q\x1de]q\x1e(U\x0eDkim-Signatureq\x1fXP\x02\x00\x00v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com; s=20120113;        h=mime-version:date:message-id:subject:from:to:content-type;        bh=5x3sYL7LIHqGpF9xuWAof54hjZGy9BQMoMJj1XoLPeQ=;        b=wFSCBjMH0HDAVSOIRFMfkIgeELzkrNivfY23FdtQ2kbIqoYcMVueuh7MBva3DDpD09         O/daWA/02/nD+2PiydTpHtqaAJdi7a6VH3DTyTO8P+Re7gg+bICQ8VDrf0FI1+3hTxAG         fLpzC78AYHO8hdWr05Ez3EfjHhVVlCoQpbb/4XsxE0rhiB6H0CfakAMeO9A8chbO/JQ8         oiKYhQpIAW0DFknC6VaauttE2ylD9a+4Gjc9Dx16+cI87PaZ2yEjZ4f6m6CA4hy/U2Dd         1BPsi63ehJ0cY+4zfro+1pmIg4yPtevWP+2zDv+rZ0+1zn72QO35mVFOBeMdovYyG5Zg         /Ymw==q e]q!(U\x0cMime-Versionq"X\x03\x00\x00\x001.0q#e]q$(U\nX-Receivedq%Xg\x00\x00\x00by <IP_ADDRESS> with SMTP id kt9mr40355683lac.99.1438283962773; Thu, 30 Jul 2015 12:19:22 -0700 (PDT)q&e]q\'(U\x08Receivedq(XA\x00\x00\x00by <IP_ADDRESS> with HTTP; Thu, 30 Jul 2015 12:19:22 -0700 (PDT)q)e]q*(U\x04Dateq+X\x1f\x00\x00\x00Thu, 30 Jul 2015 21:19:22 +0200q,e]q-(U\nMessage-Idq.XD\x00\x00\x00CANBhjP9qNPrb-rdXJSa_LPcXmnzH1C8-OU7KGd0eKMQWST8eSQ@mail.gmail.comq/e]q0(U\x07Subjectq1X\x05\x00\x00\x00test3q2e]q3(U\x04Fromq4X\x1e\x00\x00\x00Nils Dohse n.dohse@gmail.comq5e]q6(U\x02Toq7X\x10\x00\x00\x00st2@dummyhost.deq8e]q9(U\x0cContent-Typeq:cflanker.mime.message.headers.wrappers\nContentType\nq;U\x15multipart/alternativeq<}q=U\x08boundaryX\x1c\x00\x00\x00001a11345984aff6f8051c1c94ecs\x86q>\x85\x81q?}q@(U\x04mainqAU\tmultipartU\x03subqBU\x0balternativeubeeU\x04dateqCX\x1f\x00\x00\x00Thu, 30 Jul 2015 21:19:22<EMAIL_ADDRESS>==> /var/log/st2/st2sensorcontainer.log <==
Jul 30 19:19:32 localhost st2sensorcontainer[27304]: DEBUG<PHONE_NUMBER>75536 channel [-] Closed channel #1
Jul 30 19:19:32 localhost st2sensorcontainer[27304]: DEBUG<PHONE_NUMBER>75536 log [-] [IMAPSensor]: after dispatch
Jul 30 19:20:02 localhost st2sensorcontainer[27304]: DEBUG<PHONE_NUMBER>75536 log [-] [IMAPSensor]: entering poll
Jul 30 19:20:05 localhost st2sensorcontainer[27304]: DEBUG<PHONE_NUMBER>75536 log [-] [IMAPSensor]: polling mailbox dummyhost_main
Jul 30 19:20:05 localhost st2sensorcontainer[27304]: DEBUG<PHONE_NUMBER>75536 log [-] [IMAPSensor]: Processing 0 new messages

@nido009 Could this simply be an old message in the message queue? Since I tried it multiple times with the patch and I couldn't reproduce the issue.
In any case, I will look some more tomorrow :)

+1

I will also look if it's possible to fail early and throw on serialization (pickling) instead of only failing on de-seralization.

Making sure the data is serializable is a good idea. Lets just make it a requirement on the sensor sort of a best practice. I suspect a validation step in the triggerinstance data pipeline has a penalty impact on all well behaved triggerinstances and a reduction in system throughput. Anyway, that my opinion and if you feel that validation will not have a significant impact then works for me.
ps : we can discuss this offline to avoid a distraction on this PR.

This fix confirmed working with client. 👍

@manasdk

Making sure the data is serializable is a good idea. Lets just make it a requirement on the sensor sort of a best practice.

Agreed.

I suspect a validation step in the triggerinstance data pipeline has a penalty impact on all well behaved triggerinstances and a reduction in system throughput. Anyway, that my opinion and if you feel that validation will not have a significant impact then works for me.

Yeah, ideally we could detect it early and throw, but sadly that's not that easy to do.
One solution would be to only support simply types, otherwise we would need to check for references to classes in external packages / modules which are not available to other parts of the system and throw if one is detected.

kami [18:49]
yeah, got me confused at first
kami [18:50]
would need to write a custom pickle serializer for kombu if we wanted to throw on serialization and fail early
kami [18:50]
but it would be kinda hacky
kami [18:50]
since we would need to traverse the object and figure out if it references an external module which is not available on other hosts
kami [18:50]
and switching away from pickle would solve that for real so not worth spending much time on it right now imo

You are also right about the potential performance overhead.

@nido009 I believe I found another issue.
I will push another change shortly.

@nido009 I've pushed another change (635d37b11a53d5adf91b382fa9cd8552a545ccc6) - can you please test it again with this change?
(Again, I couldn't reproduce the issue, but I checked the flanker code and there are some other cases where header value is not a simple type which would cause the same issue).

@Kami great, that fixed it. now i can finally proceed and try something real with it :smile:

@Kami Thanks! :bow:
@nido009 stellar! Interested to know how you use it once it's all up and running. :)

@jfryman sure i will. keep on with the good work.


Implement returnKeyType/returnKeyLabel on Android

This PR implements returnKeyType on Android.
It is implemented with EditText.setImeOptions() that allows us to specify options on an input, in this case change the return button icon. To be noted that it is also possible to specify a string instead of an icon with [EditText.setImeActionLabel()](http://developer.android.com/reference/android/widget/TextView.html#setImeActionLabel(java.lang.CharSequence, int%29) while being 2 different things I added both of these behaviors in this PR since it was mostly at the same place/component.
Problems encountered :

All the ReactEditTexts were set to IME_ACTION_DONE by default (reference). I'm not sure why and couldn't get more informations since it was part of the initial Android React Native release.
IME_ACTION_PREVIOUS and IME_ACTION_NEXT have a different behavior than the others, they are supposed to go to the previous/next focusable view. I wanted initially to keep that behavior but I wasn't able to (The EditTexts are set to be non-focusable by default (reference) and I had to walk through recent blurOnSubmit implementation (https://github.com/facebook/react-native/pull/6215)). I settled for watching the result of the ime action, and if it's previous/next, clear the focus (expected behavior) and eats the event.
I'm not sure how to represent the returnKeyType propType as it's getting complex; basically it's an different enum on Android/iOS. I followed the keyboardType propType example but it was simpler due to being only a subset of values on one platform.

Test plan :

Launched website to make sure doc was displaying properly
Checked that every action was working/displaying correctly
Checked that every event (especially onSubmit) was fired correctly
Implemented examples in UIExplorer

I can add screenshots directly to the PR if more convenient.

I tested this PR but there seems to be an issue. Assume that there are two TextInputs, email and password. After typing in email, I want to focus on a password TextInput by tapping on it, but it doesn't work and keeps the focus on the email TextInput so I will have to click on return key. That is kinda frustrating.

@mohebifar Are you sure this is new behavior caused by the PR?

Should we call it actionKeyLabel and actionKeyType instead?

@mohebifar Are you sure this is new behavior caused by the PR?

@dmmiller Not so sure. I replaced the contents of TextInput.js and ReactTextInputManager.java with the ones proposed in this PR. After all, when I reverted the changes, the problem went away and it worked well.

Assigning to @dmmiller who's reviewing. Thank you Dave!

@Bhullnatik updated the pull request.

Sorry for the delay, got caught up with life.
@dmmiller I don't think it's possible to set any string on iOS. I really don't mind having only one prop for this, but the description will get kind of long to list every possible choice on iOS & Android. Do you want me to give it a try?

Given that iOS doesn't support it, I think this is reasonable.
@facebook-github-bot shipit

@brunobar79 would you mind taking a look at this pull request? It's been a while since the last commit was reviewed.

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review.

Hi team,
Is it possible to add the same feature for iOS platform?


t4 and t5 nevy in testing is not working and breaking the mod

Can you send me a screenshot of the error? Because it worked fine on mine

no further explanation provided, the issue will be assumed to be solved


Support of Swift?

I added a swift class, then it complains:
Check dependencies
Swift is not supported for static libraries.

when I click run.

1

Unfortunately, currently it is not possible to use Swift in a static library. react-native-create-library would have to create a dynamic framework, what would add a lot of overhead to the startup time of your app if you link a lot of dynamic libs. Furthermore currently react-native link does not support dynamic frameworks.
That said you can still use Swift in a React Native library, if you integrate the library via CococaPods. CocoaPods should automatically create a dynamic lib from your React Native library and setup your Xcode project the right way, like e.g. native-navigation (https://github.com/airbnb/native-navigation) does as it is Swift only too.
The cool thing is that if you use react-native-create-library to bootstrap the library you should also get a podspec file you can use to integrate via CocoaPods.

I found out interesting fact. If I add even empty swift file to main project I get this bunch of settings:

then I create bridging file SomeName-Bridging-Header.h and setup property Objective-C-Bridging-Header to refer to this file. And after that I can use swift code in the static library in the way how it describes here https://facebook.github.io/react-native/docs/native-modules-ios.html (Making Objective-C Manager file for exposing Swift module from the library) It builds and links.
Im not so good with Xcode and don't know if there is a way to get those bunch of settings without creating empty swift file.

Funny :) but I found description of the same hack on the bottom of the doc I put the link before
[ https://facebook.github.io/react-native/docs/native-modules-ios.html]
So it means there no other ways to get those settings in Xcode than to add a empty swift file to main project. And this will allow to use swift in static libraries.

@Elf2707 Im trying to do the same that you did however i get this error in my swift code 'AVStreamingKeyDeliveryPersistentContentKeyType' is only available on iOS 9.0 or newer is there a way to set the iOS deployment version in the static library

I found out interesting fact. If I add even empty swift file to main project I get this bunch of settings:

then I create bridging file SomeName-Bridging-Header.h and setup property Objective-C-Bridging-Header to refer to this file. And after that I can use swift code in the static library in the way how it describes here https://facebook.github.io/react-native/docs/native-modules-ios.html (Making Objective-C Manager file for exposing Swift module from the library) It builds and links.
Im not so good with Xcode and don't know if there is a way to get those bunch of settings without creating empty swift file.

I did the same till RN 0.59. Now with RN 0.60 pods are mandatory things. And i am facing linking issue with Swift file. Any help guys ??
Error i am getting after i migrated to RN 0.60. is as follows : -
Undefined symbols for architecture x86_64:
"OBJC_CLASS$AmeliaChat", referenced from:
objc-class-ref in libreact-native-amelia.a(AmeliaChat.o)
l_OBJC$CATEGORY_AmeliaChat$_RCTExternModule in libreact-native-amelia.a(AmeliaChat.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

You can use my https://github.com/iyegoroff/make-react-native-package CLI tool to scaffold a react-native package with Swift/Kotlin/Typescript


runtime error in running blitzgsea

Ran
signature = pd.read_csv("https://github.com/MaayanLab/blitzgsea/raw/main/testing/ageing_muscle_gtex.tsv")
blitz.enrichr.print_libraries()
library = blitz.enrichr.get_library("KEGG_2021_Human")
result = blitz.gsea(signature, library, shared_null=True)
I get the following error:
File<EMAIL_ADDRESS>line 140, in _check_not_importing_main
raise RuntimeError('''
RuntimeError:
An attempt has been made to start a new process before the
current process has finished its bootstrapping phase.
    This probably means that you are not using fork to start your
    child processes and you have forgotten to use the proper idiom
    in the main module:

        if __name__ == '__main__':
            freeze_support()
            ...

    The "freeze_support()" line can be omitted if the program
    is not going to be frozen to produce an executable.

    To fix this issue, refer to the "Safe importing of main module"
    section in https://docs.python.org/3/library/multiprocessing.html

Can you please suggest how to fix this error?

I have added something that might fix it, but I am not sure since the error does not occur for me. The error might be operating system dependent, and I have only tested it on macos. There is an updated version 1.3.43 you can try. Let me know if it fixed it.

I tried the updated version, but I still get the same error. I noticed that when I set result = blitz.gsea(signature, library, processes=1) it works. But I cannot get it to work using multiprocessors (deafult=4).

Hm, in what environment are you running it. I just tested it with Python 3.9.6 and also 3.12.3 and don't get the issue. I tested it in jupyter notebook and in the Python console.

ok, I can get it running from a python console. But when I copy the commands to a file for e.g. test.py and run it ($python test.py) I get that error . But it works from the python console.

A fix on your side can be to make sure the script runs in main:
import blitzgsea as blitz
import pandas as pd

signature = pd.read_csv("https://github.com/MaayanLab/blitzgsea/raw/main/testing/ageing_muscle_gtex.tsv")
library = blitz.enrichr.get_library("GO_Biological_Process_2023")

if __name__ == "__main__":
    result = blitz.gsea(signature, library, permutations=2000)
    print(result)

this will work without error. I am trying to find a way to make it work without this, but in general this would be good practice when running python scripts.

i tried a lot of ways to mitigate, but did not find anything that would work. I update the docs to include if __name__ == "__main__":. This will work in any case, whether users use jupyter notebooks or run the code in a script.


Mixed results after upgrading to Home Assistant 2021.5

After upgrading my HA install to 2021.5, the lights that I had configured to work with Adaptive Lighting only half worked. I had set up four entities - two Ecosmart zigbee bulbs via ZHA and two Shelly Duo bulbs via the built-in integration. They were all working before the update.
After the update, the zigbee bulbs continue to work with Adaptive Lighting and the Shelly bulbs stopped. I had the four entities selected as the lights in the integration, but after noticing the Shelly bulbs not changing color or brightness I checked the Adaptive Lighting options dialog and the two Shelly bulbs were no longer listed, nor available for selection in the dropdown box.
I tried replacing the entities with a light group that all four bulbs belong to instead and that still allowed the zigbee bulbs to work, but not the Shelly Duo's. I can still manually control the Shelly's brightness and temp via their individual entities or the light group itself.
I believe that Adaptive Lighting needs to be updated to handle the new color modes introduced in 2021.5.

I have the same issue when turning on adaptive lighting
[140526038688048] 'tuple' object has no attribute 'sunrise'

As a follow up here are some screenshots of the entities in dev tools
This lights works with adaptive lighting

This light does not

It appears that when they added color modes to the Shelly lights it removed the supported features that adaptive lighting checks against.

Same issue here with Philips Hue bulbs integrated via ZHA :(

Definitely having the same issue.  I think it may have something to do with Home Assistant changing the colour picker to now support RGBW and RGBWW.
The colour behaviour seems a bit random

Did you see here #110 ?

Did you guys update to the latest version?

I installed mine via HACS 3 days ago, so I assume it is latest version.  HACS is not reporting an update

Did you see here #110 ?

Had not seen that as I did not search closed issues.  I only installed Adaptive Lighting for first time 3 days ago

@DigitalFeonix, I am pretty sure that you are having this issue because the light reports supported_features: 0 which is incorrect.
This means that your light reports that it is not possible to do brightness adjustments or color adjustments. Hence, Adaptive-lighting won't try to do those.

Mine is not related to supported features.  I might try a clean install on a test Raspberry Pi 3B+ and test a clean install in case something weird happened during the update to 2021.5

@basnijholt Thank you for the quick fix! My Hue bulbs are also functioning again!

My hue bulbs are not working. They only transition from min to max temp, but nothing in-between.

It appears my LIFX and cheap zigbee lights are working perfectly. Hue tends to work 75% of the time. But all in all I’m a very satisfied customer. :) anything I can do to help let me know!!

I use mostly Hue globes and all of mine are working fine now.
Had the nunistall and reinstall the integration but after that all was good.

@basnijholt  @austwhite
With Hue lights via Deconz, the lights adjust to 2200 kelvin at sunrise and 5000 kelvin at sunset. Those are my minimum bad maximum settings. No changes in-between (although the correct temperatures are reflected in the adaptive light component).

@basnijholt @austwhite
With Hue lights via Deconz, the lights adjust to 2200 kelvin at sunrise and 5000 kelvin at sunset. Those are my minimum and maximum settings. No changes in-between (although the correct temperatures are reflected in the adaptive light component).

That's odd, I have used DeConz (the up.e assistant plugin version) for all my Hue lamps for a long time and on latest versions and HA 2021.5.5 the colour temp is no issue.
Are you using with the RGB option on or off?
i have a combination of Ambience white and full colour lamps and all work fine.
During the evening they dim and colour temp drops evenly from 5500(my max) down to 2000 (my min).
It seems to be hit and miss.  Works for me in Australia.  Maybe location nos affecting it too?

@basnijholt @austwhite
With Hue lights via Deconz, the lights adjust to 2200 kelvin at sunrise and 5000 kelvin at sunset. Those are my minimum and maximum settings. No changes in-between (although the correct temperatures are reflected in the adaptive light component).

That's odd, I have used DeConz (the home assistant plugin version) for all my Hue lamps for a long time and on latest versions and HA 2021.5.5 the colour temp is no issue.
Are you using with the RGB option on or off?
i have a combination of Ambience white and full colour lamps and all work fine.
During the evening they dim and colour temp drops evenly from 5500(my max) down to 2000 (my min).
It seems to be hit and miss. Works for me in Australia. Maybe location is affecting it too?
As a note, all my Hue globes are on the latest Hue firmware also. Mine are all the older ones with no Bluetooth. That may make a difference.

Using Deconz on windows. All Hue ambiance.

Maybe there is a difference between DeConz in Windows and the Docker version included as a HA add-on.
I definitely do not have the same issue using DeConz add-on.

Would like to point out this is fixed, see the diff since 2021.5.0:
git diff 2021.5.0 dev homeassistant/components/light/__init__.py


feat: implement core part

Codecov Report

Merging #5 (f44f34b) into main (babb580) will decrease coverage by 10.00%.
The diff coverage is 83.07%.

@@             Coverage Diff              @@
##              main       #5       +/-   ##
============================================
- Coverage   100.00%   90.00%   -10.00%
============================================
  Files            5        7        +2
  Lines           60      110       +50
============================================
+ Hits            60       99       +39
- Misses           0       11       +11

Impacted Files
Coverage Δ

lib/src/core/file_command.dart
0.00% <0.00%> (ø)

lib/src/core/core.dart
95.45% <94.23%> (-4.55%)
:arrow_down:

lib/src/core/command.dart
100.00% <100.00%> (ø)

lib/src/core/input_options.dart
100.00% <100.00%> (ø)

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 babb580...f44f34b. Read the comment docs.


Add vertical ROI for XL

SetReadMode(3)
SetSingleTrack((stop_line-start_line)/2 + start_line, stop_line-start_line)

Feature added in #480. Note that WPSC is not currently calibrating per-unit vertical ROI for XL units, so the new roi_vertical_region_1_start/end attributes would need to be manually added to the virtual EEPROM file.


Save As does not right trim spaces from a filename

Issue Type: Bug
If you do a Save As, and add a space to the end of the filename by accident,  there is no right trim of trailing spaces. You get files with a trailing space in the filename which is very confusing especially when using the new SSH extension to a Linux system.
VS Code version: Code 1.44.1 (a9f8623ec050e5f0b44cc8ce8204a1455884749f, 2020-04-11T01:48:12.622Z)
OS version: Windows_NT x64 10.0.16299
Remote OS version: Linux x64 3.10.0-1062.18.1.el7.x86_64
Extensions (6)

Extension
Author (truncated)
Version

remote-containers
ms-
0.112.0

remote-ssh
ms-
0.51.0

remote-ssh-edit
ms-
0.51.0

remote-wsl
ms-
0.44.2

vscode-remote-extensionpack
ms-
0.20.0

mssql
ms-
1.9.0

(1 theme extensions excluded)

If you are running on a system where spaces in the filename are permitted (not Windows) then you should be allowed to have a space.

Agreed as part of The name. Not in trailing though. It's not done that way.
I would say it's not common but I have never seen that. Like trailing
spaces in a password. Good luck debugging that. If someone actually wanted
a trailing space they should do it explicitly. My opinion. It should be
trimmed l and r.
On Wed, Apr 22, 2020, 10:16 AM Alex Ross<EMAIL_ADDRESS>wrote:

If you are running on a system where spaces in the filename are permitted
(not Windows) then you should be allowed to have a space.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/95760#issuecomment-617806414,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB2TBINTU4ZTXB7ZK34Q4DTRN3343ANCNFSM4MNG6FBQ
.

While trying to verify this on macOS I found this strange behavior:
On "Save As" on a file (e.g. test.js) I added a space at the of "test.js" and saved.
A file "test.js mjs" showed up in the explorer.

This change only impacts the simple file dialog. We let the system file dialog do whatever it's going to do.

@alexr00 BTW, this problem does not occur in Stable.


/self returns random user when no cookie is passed

Please take a look at the HAR file attached from the loading of www site
www.realdevsquad.com.har.zip
I am seeing this when there is no cookie set for the user:

/self is returning data for a random user

Fixed by: #92


ARM support

Hi everyone!
Could you please compile it for ARM as well so we could run it on devices such as raspberry pi?

I tried to compile on centos7-aarch64. npm install and npm run pack finish successfully but the generated release/orca-1.2.1-arm64.AppImage does not work:
[me]~/orca-3.3.4% release/orca-1.2.1-arm64.AppImage --help
[me]~/orca-3.3.4% echo $?
1

npm run test:unit fails on every major test:
test/unit/server_test.js ............................ 14/34 17s
  createServer: > should reply pong to ping post
  not ok should be equal
    +++ found
    --- wanted
    -pong
    compare: ===
    at:
      line: 153
      column: 11
      file: test/unit/server_test.js
      type: Request
      function: _post
      method: _callback
    stack: |
      Request._post [as _callback] (test/unit/server_test.js:153:11)
      Request.self.callback (node_modules/request/request.js:185:22)
      Request.<anonymous> (node_modules/request/request.js:1161:10)
      IncomingMessage.<anonymous> (node_modules/request/request.js:1083:12)
    source: |
      t.equal(body, 'pong')

Any ideas on this?

I use the recommended node and npm:
<EMAIL_ADDRESS>which node
~/node-v8.17.0-linux-arm64/bin/node
<EMAIL_ADDRESS>which npm
~/node-v8.17.0-linux-arm64/bin/npm


Examining the enforcement of Send and Receive rates in P2P configuration

Problem
Despite the send and receive rate settings in the P2P configuration, it is possible that these settings only apply to the average traffic rate and not the maximum rate. This issue needs further investigation, and there may be a need to develop a test for a definitive conclusion (I am working on it).

When sending data to another peer, a sequence of function calls occurs, as depicted below. The amount of data sent is monitored and moderated through the invocation of Limit on the available flow Monitor object within the P2P connection:

sendRoutine
sendSomePacketMsgs()
sendSomePacketMsgs()
c.sendMonitor.Limit(...)

It's important to note that the Limit function is a blocking call and returns the maximum allowed amount of bytes to be transferred. However, there appears to be an issue where the return value of this function is ignored within the sendSomePacketMsgs() function, potentially allowing more data to be sent than the specified limit. This could lead to a violation of the specified data transfer rate; this means that the specified send rate is applied to the average rate rather than the maximum rate.

After conducting a more thorough investigation on how SendRate is enforced in the p2p connections, I have arrived at the following results. In summary, the current implementation enforces SendRate as the maximum send rate, albeit with some minor variations, as elaborated upon below:
Each connection sends data in the form of a PacketMsg, with a size limit of 1034 bytes, as defined by maxPacketMsgSize.
When we invoke the sendSomePacketMsgs() function, it sends a maximum of numBatchPacketMsgs of such messages, totalling 10 * 1034 bytes = 10,340 bytes. This amount is sent without blocking (after the call to the Limit has successfully returned)
Once such a batch is transferred, the Limit function ensures that the current amount of sent data within the current rate sample duration (100 ms) does not exceed the following value:
sampleRate  * SendRate = 0.1 * 512,000 bytes = 51,200 bytes.
Context: The sampleRate is set to 5 times the clockRate, which equals 100 milliseconds.
This means that a series of batches totalling 10,340 bytes each will be sent until reaching the 51,200-byte limit. The maximum error that can occur (rate violation) is when the sample period has not ended, meaning that the 100 ms since the last sample have not elapsed, and another batch of data is sent. Up to 4 batches (4 * 10,340 bytes) , no limit is breached. However, on the fifth batch, we exceed the limit (but without getting caught) by an extra 500 bytes, i.e., 5 * 10,340 bytes = 51,700 bytes in a sample (500 bytes more than allowed). Therefore, the rate limit goes as high as 51,700 bytes per roughly 100 ms, or 517 KB per second, instead of the intended 512 KB/s.
My local tests also assert the same results. Will open a PR for that as well.
To generalize:
For a given SendRate and a sample period of 100 ms (according to the current connection setup), the effective maximum rate would be calculated as follows:

batch_size_bytes = numBatchPacketMsgs * maxPacketMsgSize
rate_per_100_ms = ceil((SendRate * 0.1) / batch_size_bytes) * batch_size_bytes
Rate per second: 10 * rate_per_100_ms

Another important takeaway from this analysis is that the maximum blocking time is between 5ms up to to the sample rate, which is 100 ms. This is because, at the end of each sample period, the information about that sample is reset and data transfer can be resumed.

I have inspected the receive rate and here are the findings:
Summary: The receive rate is essentially the maximum rate, however, the effective max rate is slightly higher than that (however, the error in the receive rate is smaller than the send rate error). Below is the algorithm:

Infinite loop:

One PacketMsg is received (with the max size of 1034 bytes, see this comment for code references).
Check whether the total amount of data transferred in the current sample period has exceeded the maximum allowed amount, which is RecvRate * sample period (sample period being 0.1 s)`.

If it has, then pause receiving until the current sample period has passed (checking every 5 ms to determine if the sample period has passed and we have entered the next sample period). When a sample period has passed, the amount of received data is also reset.
If it hasn't exceeded the maximum allowed amount, continue the loop.

To generalize:
For a given RecvRate and a sample period of 0.1 s (according to the current connection setup), the effective maximum receive rate would be calculated as follows:
max_rate_per_100_ms = ceil((RecvRate * 0.1) / maxPacketMsgSize) * maxPacketMsgSize
Rate per second: 10 * max_rate_per_100_ms
I will soon open a PR to test out the max receive rate.

I'd like to highlight that the results related to the maximum send rate in the current analysis and the outcomes of my latest experimentation on mocha-4 align perfectly. As illustrated in the figure below, which demonstrates the send traffic rate per peer, all values consistently remain below 517KB/s, indicating the overall health of the node.

The same observation as the above is true for the receive rate per connection. Please see


cannot coerce a set to a string error when users.ldap.daemon.enable is false

When trying to configure LDAP, but the users.ldap.daemon.enable option is set to false, an error is thrown on running nixos-rebuild:
$ sudo nixos-rebuild switch --show-trace
building Nix...
building the system configuration...
error: while evaluating the attribute ‘activationScript’ of the derivation ‘nixos-15.09.597.71e29b4’ at /nix/store/m3fvi30ys8pm500lb87l7q8kh11nqamj-nixos-15.09.597.71e29b4/nixos/nixpkgs/nixos/modules/system/activation/top-level.nix:102:7:
while evaluating the attribute ‘system.activationScripts.script’ at /nix/store/m3fvi30ys8pm500lb87l7q8kh11nqamj-nixos-15.09.597.71e29b4/nixos/nixpkgs/nixos/modules/system/activation/activation-script.nix:58:9:
while evaluating ‘textClosureMap’ at /nix/store/m3fvi30ys8pm500lb87l7q8kh11nqamj-nixos-15.09.597.71e29b4/nixos/nixpkgs/lib/strings-with-deps.nix:69:35, called from /nix/store/m3fvi30ys8pm500lb87l7q8kh11nqamj-nixos-15.09.597.71e29b4/nixos/nixpkgs/nixos/modules/system/activation/activation-script.nix:79:18:
while evaluating ‘id’ at /nix/store/m3fvi30ys8pm500lb87l7q8kh11nqamj-nixos-15.09.597.71e29b4/nixos/nixpkgs/lib/trivial.nix:4:8, called from undefined position:
while evaluating the attribute ‘text’ at /nix/store/m3fvi30ys8pm500lb87l7q8kh11nqamj-nixos-15.09.597.71e29b4/nixos/nixpkgs/nixos/modules/system/activation/activation-script.nix:9:5:
while evaluating the attribute ‘text’ at /nix/store/m3fvi30ys8pm500lb87l7q8kh11nqamj-nixos-15.09.597.71e29b4/nixos/nixpkgs/lib/strings-with-deps.nix:76:38:
cannot coerce a set to a string, at /nix/store/m3fvi30ys8pm500lb87l7q8kh11nqamj-nixos-15.09.597.71e29b4/nixos/nixpkgs/nixos/modules/config/ldap.nix:192:53

I am guessing this is because ${ldapConfig} is a set, here: https://github.com/NixOS/nixpkgs/blob/release-15.09/nixos/modules/config/ldap.nix#L194

Pinging @rickynils who performed last commit on that file.

(triage) can you still reproduce this?

Yes.

@a1russell,
I can't repro on 20f009d
$ cat ldap.nix
{ config, lib, ... }:

{ users.ldap.daemon.enable = true; }

$ nix-build -I nixos-config=./ldap.nix '<nixpkgs/nixos>' -A vm
/nix/store/g9nlm0mmzmbwl2i6yw3sjs7nhih7xk3v-nixos-vm

Could you try to produce a minimal config file that repro's the error?

Ah, I suppose there's another thing needed to recreate the bug (bind.distinguishedName).
    ldap = {
      enable = true;
      server = "";
      base = "";
      daemon.enable = false;
      bind.distinguishedName =<EMAIL_ADDRESS>    };

Still works
$ cat ./ldap.nix
{ config, lib, ... }:

{
  users.ldap = {
    enable = true;
    server = "";
    base = "";
    daemon.enable = false;
    bind.distinguishedName =<EMAIL_ADDRESS>  };
}
$ nix-build -I nixos-config=./ldap.nix '<nixpkgs/nixos>' -A vm
/nix/store/q8lspf5643a561pc1dc3c2w9x5m9ci4l-nixos-vm

When trying to configure LDAP, but the users.ldap.daemon.enable option is set to false

I guess that's the point where it would fail?

I should mention that I'm still on stable branch.
$ nix-build -I nixos-config=./ldap.nix '<nixpkgs/nixos>' -A vm
error: cannot coerce a set to a string, at /nix/store/dnfca8r2s9m2rf925p9r9z8rl3q35zl5-nixos-16.03.1171.9cb194c/nixos/nixpkgs/nixos/modules/config/ldap.nix:193:53
(use ‘--show-trace’ to show detailed location information)
$ cat ldap.nix
{ config, lib, ... }:

{
  users.ldap = {
    enable = true;
    server = "";
    base = "";
    daemon.enable = false;
    bind.distinguishedName =<EMAIL_ADDRESS>  };
}
$ nix-build -I nixos-config=./ldap.nix '<nixpkgs/nixos>' -A vm
error: cannot coerce a set to a string, at /nix/store/dnfca8r2s9m2rf925p9r9z8rl3q35zl5-nixos-16.03.1171.9cb194c/nixos/nixpkgs/nixos/modules/config/ldap.nix:193:53
(use ‘--show-trace’ to show detailed location information)

Maybe it's fixed in unstable. I can't verify that, myself, though.

Closed with 19ee3ba

Thanks @obadz! (and @fpletz and @markus2342, of course)


Latest listen version bump gives dependency error on FontCustom

I'm using middleman-fontcustom for my project, which depends on fontcustom.
Fontcustom has has it's listen version set to ">=1.0","<3.0" in the gemspec.
Middleman-core has it's listen version set to "~> 3.0.3" since 5 days ago.
As such, these two are now incompatible apparently for no good reason (gemspec is the only file changed, suggesting not using new functionality listen 3.0 introduced). Would it be possible to define the listen gem dependency as just >= 2.7.9 or something?
There's a pull request open for this issue where it belongs, but it seems Fontcustom is not really as actively maintained as Middleman.

 They really sure separate their CLI functionality from their assets.
Listen 3 seems to be a very safe upgrade. I'll hold releasing MM 3.4 until this is resolved.

I'm doing some issue-gardening 🌿🌷🌾 and came across this issue.
Sorry that this has lingered for quite a while! I'd suggest either closing this issue since it's not related to middleman.


amplify publish fails when auth and hosting added

Describe the bug
Setting up amplify on new project. Amplify init went well. Then did amplify add auth and amplify add hosting, then amplify publish. The publish failed.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
Cognito and hosting setup and app runs.
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: OSX

Additional context
Default region is ca-central-1 if that helps.

Could you provide some error logs as to what exactly failed during the publish step?

See screenshot above, and here's text version:
$ amplify publish
| Category | Resource name           | Operation | Provider plugin   |
| -------- | ----------------------- | --------- | ----------------- |
| Auth     | csidryeyeamplifycognito | Create    | awscloudformation |
| Hosting  | S3AndCloudFront         | Create    | awscloudformation |
? Are you sure you want to continue? true
⠸ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS                           dryeyefrontend-20180922133200 AWS::CloudFormation::Stack Sat Sep 22 2018 13:55:55 GMT-0600 (Mountain Daylight Time) User Initiated
CREATE_IN_PROGRESS                           hostingS3AndCloudFront        AWS::CloudFormation::Stack Sat Sep 22 2018 13:55:59 GMT-0600 (Mountain Daylight Time)
CREATE_IN_PROGRESS                           authcsidryeyeamplifycognito   AWS::CloudFormation::Stack Sat Sep 22 2018 13:55:59 GMT-0600 (Mountain Daylight Time)
CREATE_IN_PROGRESS                           hostingS3AndCloudFront        AWS::CloudFormation::Stack Sat Sep 22 2018 13:56:00 GMT-0600 (Mountain Daylight Time) Resource creation Initiated
CREATE_FAILED                                authcsidryeyeamplifycognito   AWS::CloudFormation::Stack Sat Sep 22 2018 13:56:00 GMT-0600 (Mountain Daylight Time) Template format error: Unrecognized resource types: [AWS::Cognito::UserPool, AWS::Cognito::IdentityPoolRoleAttachment, AWS::Cognito::UserPoolClient, AWS::Cognito::IdentityPool]
CREATE_FAILED                                hostingS3AndCloudFront        AWS::CloudFormation::Stack Sat Sep 22 2018 13:56:00 GMT-0600 (Mountain Daylight Time) Resource creation cancelled
UPDATE_ROLLBACK_IN_PROGRESS                  dryeyefrontend-20180922133200 AWS::CloudFormation::Stack Sat Sep 22 2018 13:56:01 GMT-0600 (Mountain Daylight Time) The following resource(s) failed to create: [hostingS3AndCloudFront, authcsidryeyeamplifycognito].
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS dryeyefrontend-20180922133200 AWS::CloudFormation::Stack Sat Sep 22 2018 13:56:03 GMT-0600 (Mountain Daylight Time)
DELETE_IN_PROGRESS                           hostingS3AndCloudFront        AWS::CloudFormation::Stack Sat Sep 22 2018 13:56:04 GMT-0600 (Mountain Daylight Time)
⠏ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS dryeyefrontend-20180922133200-hostingS3AndCloudFront-37AZP5DDFNZ7 AWS::CloudFormation::Stack Sat Sep 22 2018 13:56:00 GMT-0600 (Mountain Daylight Time) User Initiated
CREATE_IN_PROGRESS S3Bucket                                                          AWS::S3::Bucket            Sat Sep 22 2018 13:56:02 GMT-0600 (Mountain Daylight Time)
CREATE_IN_PROGRESS S3Bucket                                                          AWS::S3::Bucket            Sat Sep 22 2018 13:56:03 GMT-0600 (Mountain Daylight Time) Resource creation Initiated
DELETE_IN_PROGRESS dryeyefrontend-20180922133200-hostingS3AndCloudFront-37AZP5DDFNZ7 AWS::CloudFormation::Stack Sat Sep 22 2018 13:56:05 GMT-0600 (Mountain Daylight Time) User Initiated
CREATE_FAILED      S3Bucket                                                          AWS::S3::Bucket            Sat Sep 22 2018 13:56:05 GMT-0600 (Mountain Daylight Time) Resource creation cancelled
⠏ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE authcsidryeyeamplifycognito AWS::CloudFormation::Stack Sat Sep 22 2018 13:56:07 GMT-0600 (Mountain Daylight Time)
⠙ Updating resources in the cloud. This may take a few minutes...

DELETE_SKIPPED  S3Bucket                                                          AWS::S3::Bucket            Sat Sep 22 2018 13:56:26 GMT-0600 (Mountain Daylight Time)
DELETE_COMPLETE dryeyefrontend-20180922133200-hostingS3AndCloudFront-37AZP5DDFNZ7 AWS::CloudFormation::Stack Sat Sep 22 2018 13:56:27 GMT-0600 (Mountain Daylight Time)
⠹ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE          hostingS3AndCloudFront        AWS::CloudFormation::Stack Sat Sep 22 2018 13:56:39 GMT-0600 (Mountain Daylight Time)
UPDATE_ROLLBACK_COMPLETE dryeyefrontend-20180922133200 AWS::CloudFormation::Stack Sat Sep 22 2018 13:56:39 GMT-0600 (Mountain Daylight Time)
⠧ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack
✖ An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete

><EMAIL_ADDRESS>build /Users/hisham/src/dry-eye-frontend
> ng build --prod

Date: 2018-09-22T19:57:28.412Z
Hash: 36e9dc638b4af6f83439
Time: 26836ms
chunk {scripts} scripts.fac25701f9a4563f3d54.js (scripts) 461 kB  [rendered]
chunk {0} runtime.a66f828dca56eeb90e02.js (runtime) 1.05 kB [entry] [rendered]
chunk {1} styles.59aec90edeadc2d31877.css (styles) 187 kB [initial] [rendered]
chunk {2} polyfills.c9a5fed38d6e21c1ef81.js (polyfills) 63.6 kB [initial] [rendered]
chunk {3} main.483f39f85700e2536834.js (main) 3.77 MB [initial] [rendered]

WARNING in Circular dependency detected:
src/app/shared/symptoms/method-symptom-control/method-symptom-control.component.ngfactory.js -> src/app/shared/symptoms/symptom-control-adapter/symptom-control-adapter.component.ngfactory.js -> src/app/shared/symptoms/method-symptom-control/method-symptom-control.component.ngfactory.js

WARNING in Circular dependency detected:
src/app/shared/symptoms/symptom-control-adapter/symptom-control-adapter.component.ngfactory.js -> src/app/shared/symptoms/method-symptom-control/method-symptom-control.component.ngfactory.js -> src/app/shared/symptoms/symptom-control-adapter/symptom-control-adapter.component.ngfactory.js
frontend build command exited with code 0
✖ Error has occured during publish.
2018-09-22T19:57:28.534Z - error: uncaughtException: Cannot read property 'HostingBucketName' of undefined date=Sat Sep 22 2018 13:57:28 GMT-0600 (Mountain Daylight Time), pid=27948, uid=501, gid=20, cwd=/Users/hisham/src/dry-eye-frontend, execPath=/Users/hisham/.nvm/versions/node/v10.9.0/bin/node, version=v10.9.0, argv=[/Users/hisham/.nvm/versions/node/v10.9.0/bin/node, /Users/hisham/.nvm/versions/node/v10.9.0/bin/amplify, publish], rss=97132544, heapTotal=66342912, heapUsed=58367640, external=773113, loadavg=[2.25244140625, 1.900390625, 1.93212890625], uptime=362287, trace=[column=66<EMAIL_ADDRESS>function=getHostingBucketName, line=37, method=null, native=false, column=29<EMAIL_ADDRESS>function=Object.run, line=13, method=run, native=false, column=7, file=internal/process/next_tick.js, function=process._tickCallback, line=68, method=_tickCallback, native=false], stack=[TypeError: Cannot read property 'HostingBucketName' of undefined,     at getHostingBucketName (/Users/hisham/.nvm/versions/node/v10.9.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-hosting/lib/S3AndCloudFront/helpers/file-uploader.js:37:66),     at Object.run (/Users/hisham/.nvm/versions/node/v10.9.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-hosting/lib/S3AndCloudFront/helpers/file-uploader.js:13:29),     at process._tickCallback (internal/process/next_tick.js:68:7)]

Is it because Auth is not available in ca-central-1? Shouldn't it then give me an alternative?

Maybe needs a fix like this but for cognito: https://github.com/aws-amplify/amplify-cli/pull/192

Ok I will switch to us-east-1 for now but this means I will only use
amplify cli to setup auth since I prefer to use ca-central-1 for the other
services that are available there (such as data store and hosting). This
means I have to set these service up manually or use aws cdk or similar.
Would be great if you can create feature request for region specific
stacks. That would be very helpful as ideally I’d like to use the amplify
cli to manage everything...
On Sat, Sep 22, 2018 at 4:23 PM Kaustav Ghosh<EMAIL_ADDRESS>wrote:

@hisham https://github.com/hisham Curently we are supporting the
following regions.l and pushing towards a region specific stack for the
CloudFormation deployments.
'us-east-1': 'US East (N. Virginia)',
'us-east-2': 'US East (Ohio)',
'us-west-2': 'US West (Oregon)',
'eu-west-1': 'EU (Ireland)',
'eu-central-1': 'EU (Frankfurt)',
'ap-northeast-1': 'Asia Pacific (Tokyo)',
'ap-southeast-1': 'Asia Pacific (Singapore)',
'ap-southeast-2': 'Asia Pacific (Sydney)',
'ap-south-1': 'Asia Pacific (Mumbai)',
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aws-amplify/amplify-cli/issues/194#issuecomment-423777612,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAE_vWF-gHrF3u4jqyaZm8gDsRC9185Qks5udrhngaJpZM4W1a7-
.

I have the same issue with eu-central-1

Having same issue in us-east-1, I'm guessing it is not entirely related to region.
Error: Cannot read property 'HostingBucketName' of undefined,     at getHostingBucketName (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-hosting/lib/S3AndCloudFront/helpers/file-uploader.js:37:66),     at Object.run (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-hosting/lib/S3AndCloudFront/helpers/file-uploader.js:13:29),     at process._tickCallback (internal/process/next_tick.js:68:7)]
seems that context is not getting passed

I am having the same issue.

I'm having the same issue here:
error: uncaughtException: Cannot read property 'HostingBucketName' of undefined date

No solution to this yet? I am having the same issue.
error: uncaughtException: Cannot read property 'HostingBucketName' of undefined date

@kempei after switching aws profile to us-east-1 (an amplify supported region), everything worked fine, so this I believe was an issue from me attempting to use amplify-cli in a non-supported region (ca-central-1)

getting Error: Hosting is already fully enabled.

@amlcodes This issue comes up when you abrupt the amplify hosting add flow. You can delete the amplify/backend/hosting directory and run amplify hosting add command once again and then amplify publish.

@leonjorge23 This usually occurs when your Cloudformation tempalte fails to push. The cloudformation stacktrace would be helpful for us to debug.

I had this issue error: uncaughtException: Cannot read property 'HostingBucketName' of undefined date when I am init a react project using creare-react-app. I was initially set the out dir to 'public/' (which is build/ by default). After restart amplify  init and the change to build/, the problem solved. I guess it I hope this can help you.


Endpoint seems wrong when updating ACL

i get an error: The requested resource wasn't found.
404 (Not Found), showing the following endpoint in the console:
http://localhost:8080/api/collections/posts/records/posts
    async accessReader() {
      // Update collection ACL
      const collectionId = 'posts';
      const newAcl = {
        'reader': {
          'read': true
        }
      };
      try {
        const updatedCollection = await this.pb.collection('posts').update(collectionId, { acl: newAcl });
        console.log('Collection ACL updated:', updatedCollection);
      } catch (error) {
        console.error(error.message);
      }
    },

what i would expected the endpoint to be instead
http://localhost:8080/api/collections/posts/

The above code sample doesn't seem correct.

collectionId is not an id.

collection('posts').update(id, data) is for updating a single collection record, not the collection itself.

You can get 404 response from the update call in case the client request doesn't satisfy the collection Update API rule (this is a side effect of the fact that  API rules are also filters; see the note in https://pocketbase.io/docs/api-rules-and-filters/#api-rules).

If the above doesn't help, please elaborate and provide more details about your use case and data structure in a Q&A discussion.

Side-note: if you are looking for updating a collection configuration programatically, you can check https://pocketbase.io/docs/api-collections/.


Fix content-type header for http2

What will this PR do? Since 1.0 request.headers methods work case-insensitive.

@steffans It's not working with http2. In my program, the ajax response.data is string when the server response with content-type: application/json, which is a http2 request. After I add the response.headers.get('content-type') at line 40 then working.

@steffans I just check again, The vue-resource which I used is 1.0.2

@steffans  Maybe you should close this pr.I found i used the wrong version of vue-resource.  The package.json is updated when i pull from the laravel/laravel. But i didn't reinstall it. So the 1.0.0+ is working for me.


WIP implement sdl 0243 display capability fix

WIP
Items missing:

[x] T&G manager
[ ] menu manager
[ ] choice set manager

CLA

[X] I have signed the CLA

Codecov Report

Merging #1188 into develop will decrease coverage by 0.07%.
The diff coverage is 30.95%.

@@              Coverage Diff              @@
##             develop    #1188      +/-   ##
=============================================
- Coverage      47.36%   47.28%   -0.08%
- Complexity      4323     4337      +14
=============================================
  Files            481      481
  Lines          23338    23392      +54
  Branches        2648     2658      +10
=============================================
+ Hits           11055    11062       +7
- Misses         11604    11656      +52
+ Partials         679      674       -5

Impacted Files
Coverage Δ
Complexity Δ

...vicelink/proxy/rpc/enums/SystemCapabilityType.java
100% <100%> (ø)
4 <0> (ø)
:arrow_down:

...icelink/managers/screen/BaseSoftButtonManager.java
48.48% <16.66%> (-9.1%)
42 <1> (-4)

...ink/managers/screen/BaseTextAndGraphicManager.java
48.45% <30%> (-0.88%)
74 <6> (ø)

...icelink/proxy/rpc/GetSystemCapabilityResponse.java
80.95% <0%> (-19.05%)
8% <0%> (+3%)

...link/proxy/rpc/SetInteriorVehicleDataResponse.java
80.95% <0%> (-19.05%)
8% <0%> (+3%)

...evicelink/proxy/rpc/DiagnosticMessageResponse.java
80.95% <0%> (-19.05%)
8% <0%> (+3%)

...link/proxy/rpc/GetInteriorVehicleDataResponse.java
83.33% <0%> (-16.67%)
11% <0%> (+4%)

...com/smartdevicelink/proxy/rpc/GetDTCsResponse.java
88% <0%> (-12%)
11% <0%> (+4%)

...rtdevicelink/proxy/rpc/WindowTypeCapabilities.java
100% <0%> (+28.57%)
7% <0%> (+1%)
:arrow_up:

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 e71879a...2858873. Read the comment docs.


fix(page-header-tools-margin): removed margin-top/bottom

closes #2040
Breaking changes

Removed --pf-c-page__header-tools--MarginTop: var(--pf-global--spacer--sm);
Removed --pf-c-page__header-tools--MarginBottom: var(--pf-global--spacer--sm);
Removed margin-top
Removed margin-bottom

Preview: https://patternfly-next-pr-2821.surge.sh

@mcoker updated

@mattnolting nice! can you also update the issue description to say removed --pf-c-page__header-tools--MarginTop and --pf-c-page__header-tools--MarginBottom, since those are what users will need to update?

@mcoker updated

Can you say something to the effect of "The following variables were removed. Any reference to them should be removed as they are no longer used in patternfly"?


How to do text23D?

I've noticed that the current example only demonstrates image-to-3D generation. Would it be possible to kindly provide an example for text-to-3D conversion as well? I'm eager to explore this aspect further.

@Adamdad The demo has both image-to-3D and text-to-3D, please check it more carefully.

I've checked the demo you've provided, but couldn't find an instruction for text to 3D.
Where can I find inference command for text to 3D, such as the one in the README.md for image to 3D.

@hayoung-jeremy There is no infer code for text now, but you can check this part: https://github.com/3DTopia/LGM/blob/main/app.py#L85


⚠ ClamAV has degraded performance

In 5e5dbf9, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 179 ms

Resolved: ClamAV performance has improved in 8e3c679.


[HOLD for payment 2024-12-05] [$250] Search - Expenses change position briefly when switching from Settings to Search

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

Version Number: 9.0.63-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause - Internal Team
Action Performed:
Precondition:

Have many expenses

Go to staging.new.expensify.com
Go to Search
Change sorting a few times (click Merchant, From, To etc)
Click Settings
Go back to Search
Might need to repeat Step 4 and 5 a few times to see the expenses changing position briefly

Expected Result:
The expenses will not change position briefly when switching from Settings to Search after changing sorting order.
Actual Result:
The expenses change position briefly when switching from Settings to Search after changing sorting order.
Workaround:
Unknown
Platforms:

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

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

Screenshots/Videos

Add any screenshot/video evidence

https://github.com/user-attachments/assets/014ee706-3257-4095-9ee9-7728cfcdd733
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021858539185487721038
Upwork Job ID:<PHONE_NUMBER>487721038
Last Price Increase: 2024-11-18
Automatic offers:

FitseTLT | Contributor | 105027229

Issue OwnerCurrent Issue Owner: @isabelastisser

@jjcoffee can you please review the proposal above? Thanks!

@FitseTLT's proposal LGTM! As an example, if we are comparing two equivalent values (e.g. two expenses both with a merchant of "Test"), we would not be returning the expected value of 0 as we only perform conversion to lower case on one of the compared values.
I think we should perform conversion to lower case on both values as otherwise we'd be doing case-sensitive sorting which doesn't really make sense in this context.
:ribbon::eyes::ribbon: C+ reviewed

@marcochavezf bump on this one

@marcochavezf Bump for assignment Thx

@isabelastisser Could you star the issue for @marcochavezf, so that it gets his attention? Thanks!

@marcochavezf, can you please provide an update? Thanks!

Payment summary:
@jjcoffee requires payment through NewDot Manual Requests C+ $250 PENDING
@FitseTLT requires payment automatic offer (Contributor) PAID!

All set!

$250 approved for @jjcoffee


handling out paramters  stopped working

Hi
First of all, thanks for great driver
recently after I uopdated my project to emulate and check broken-pipe problem, new compiled binary gets:
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
When I try to execute out-paramater example I also get this error:
Connection string:  oracle://user:pass@server:poer/?SID=sid&TRACE FILE=oracle_trace.log
Finish create table GOORA_TEMP_VISIT : 1.028699205s
100 rows inserted:  1.525866289s
Can't get output parameters ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at line 2

Finish drop table:  67.15662ms

in my oracle_trace file:
2022-12-24T15:02:24.9767: Exec With Context:
2022-12-24T15:02:24.9767: Exec:
BEGIN
SELECT VISIT_ID, NAME, VAL, VISIT_DATE INTO :1, :2, :3, :4 FROM GOORA_TEMP_VISIT WHERE VISIT_ID = 1;
END;
2022-12-24T15:02:24.9767:     0:
{{} 0xc000292b38 false}
2022-12-24T15:02:24.9768:     1:
{{} 0xc000287810 false}
2022-12-24T15:02:24.9768:     2:
{{} 0xc000292b40 false}
2022-12-24T15:02:24.9768:     3:
{{} 0001-01-01 00:00:00 +0000 UTC false}
2022-12-24T15:02:24.9768:
Write packet:
00000000  00 ef 00 00 06 00 00 00  00 00 03 5e 00 03 04 05  |...........^....|
00000010  29 00 01 01 6f 01 01 0d  00 00 00 00 04 7f ff ff  |)...o...........|
00000020  ff 01 01 04 00 00 00 00  00 00 00 00 00 01 00 00  |................|
00000030  00 00 00 6f 42 45 47 49  4e 0a 53 45 4c 45 43 54  |...oBEGIN.SELECT|
00000040  20 56 49 53 49 54 5f 49  44 2c 20 4e 41 4d 45 2c  | VISIT_ID, NAME,|
00000050  20 56 41 4c 2c 20 56 49  53 49 54 5f 44 41 54 45  | VAL, VISIT_DATE|
00000060  20 49 4e 54 4f 20 3a 31  2c 20 3a 32 2c 20 3a 33  | INTO :1, :2, :3|
00000070  2c 20 3a 34 20 46 52 4f  4d 20 47 4f 4f 52 41 5f  |, :4 FROM GOORA_|
00000080  54 45 4d 50 5f 56 49 53  49 54 20 57 48 45 52 45  |TEMP_VISIT WHERE|
00000090  20 56 49 53 49 54 5f 49  44 20 3d 20 31 3b 0a 45  | VISIT_ID = 1;.E|
000000a0  4e 44 3b 01 01 01 01 00  00 00 00 00 00 00 02 80  |ND;.............|
000000b0  00 00 00 00 02 03 00 00  01 16 00 00 00 00 00 00  |................|
000000c0  00 01 03 00 00 00 00 01  10 00 00 02 02 30 01 00  |.............0..|
000000d0  02 03 00 00 01 16 00 00  00 00 00 00 00 0c 03 00  |................|
000000e0  00 01 0b 00 00 00 00 00  00 00 07 00 00 00 00     |...............|
2022-12-24T15:02:24.9884:
Read packet:
00000000  00 0b 00 00 0c 00 00 00  01 00 01                 |...........|
2022-12-24T15:02:24.9888:
Read packet:
00000000  00 0b 00 00 0c 00 00 00  01 00 02                 |...........|
2022-12-24T15:02:24.9888:
Write packet:
00000000  00 0b 00 00 0c 00 00 00  01 00 02                 |...........|
2022-12-24T15:02:24.9946:
Read packet:
00000000  00 98 00 00 06 00 00 00  00 00 04 01 01 01 71 00  |..............q.|
00000010  02 19 66 00 00 01 0b 00  2f 00 00 00 00 00 03 07  |..f...../.......|
00000020  ea 72 02 01 7e 00 03 01  db ae 01 29 00 00 00 00  |.r..~......)....|
00000030  00 00 00 00 00 62 4f 52  41 2d 30 36 35 30 32 3a  |.....bORA-06502:|
00000040  20 50 4c 2f 53 51 4c 3a  20 6e 75 6d 65 72 69 63  | PL/SQL: numeric|
00000050  20 6f 72 20 76 61 6c 75  65 20 65 72 72 6f 72 3a  | or value error:|
00000060  20 63 68 61 72 61 63 74  65 72 20 73 74 72 69 6e  | character strin|
00000070  67 20 62 75 66 66 65 72  20 74 6f 6f 20 73 6d 61  |g buffer too sma|
00000080  6c 6c 0a 4f 52 41 2d 30  36 35 31 32 3a 20 61 74  |ll.ORA-06512: at|
00000090  20 6c 69 6e 65 20 32 0a                           | line 2.|
2022-12-24T15:02:24.9948: Summary: RetCode:6502, Error Message:"ORA-06502: PL/SQL: numeric or value error: character string buffer too small\nORA-06512: at line 2\n"
2022-12-24T15:02:24.9948:
Write packet:
00000000  00 15 00 00 06 00 00 00  00 00 11 69 00 01 01 01  |...........i....|
00000010  01 0b 03 93 00                                    |.....|
2022-12-24T15:02:24.9993:
Read packet:
00000000  00 0f 00 00 06 00 00 00  00 00 09 01 01 01 73     |..............s|

if I can help with more information, please let me know.

I've tried previous versions, this issue happens after version 2.5.4 and with previous versions this problem does not happened

un-commenting
par.MaxCharLen = len([]rune(value))

in file parameter_encode.go did fix the issue

I comment this line to let oracle 11g work

I will investigate the issue and find a solution


feat: traefik v3 upgrade

What does this PR do?
This PR migrates the chart to Traefik v3.
CRDs have been updated according to their definition in
The RBACs have been updated to remove the containo.us group and add the ServersTransportTCP resource.
Motivation
The new version of Traefik Hub is based on Traefik v3.
More

[ ] Yes, I updated the tests accordingly
[x] Yes, I ran make test and all the tests passed

I've added a no-merge as I'm not sure what should be the target branch.

@jspdown main branch is now ok. You can merge it.


fix bug in crf.CrfDecodeForwardRnnCell

When I read your code implementation of crf, I found a little bug in class CrfDecodeForwardRnnCell, check it!

Get it! Thank you, I suggest updating the comment, it's easy to mislead.

Do you want to update it in this PR?

Do you want to update it in this PR?
Yes, I do. I suggest

state: A tuple containing a [batch_size, num_tags] matrix containing the
        previous step's score values.

is better.

@tracy-talent Yup, it's what we should go with it.


Kickstart basemaps

CR @javisantana
as a comment, 👏 for the stackLayout, it's been so easy to start working on this new view
/cc @xavijam @viddo

I recreated the carousel component as a mosaic (the little squares)
@xavijam would it be worth it consolidating in a single component? Also, I had to do one slight change as with the current design the mosaic item can be not-selected, not-highlighted (i.e. I change the source, and hover with the mouse see attached)

@javisantana @viddo is the basemaps well placed in the files structure? I tried to follow the same patterns of other objects in the show view
right now it only works with tiled basemaps, next would be adding Plain basemaps, but if it's ok in general I'd add tests then ask for merge
thanks!

Looks reasonable 👍

Btw, I find the custom- prefix on files/components to be superfluous, being a component implies that it should be customizable already, custom would/should the exception.

merging as soon as it gets 💚
right now just updating the url for tilelayer basemaps, next is working with labels-on-top basemaps and replacing the whole layer


Move doc/ to resources/

History - we originally had docs in lib/ and took advantage of this during the installs so that p6doc would  be able to find the installed libs. At some point, I moved this to doc/ so that we could keep separate the modules used to build the site or run p6doc. We then created a Build.pm to copy those files from doc/ into the installed lib/ dir to mimic the original functionality.
This worked, but at some point, trying to create the files this way during install caused permission issues as the install is going to the wrong directory (and the user running the install may not have permissions in that folder)
However, since then (2014!), a resources/ mechanism has been introduced. Files in resources/ can be installed and then retrieved via %?RESOURCES.

Move any top level doc/* files into resources/*
Update tests, scripts, and build to track new directory
Add all pod6 files expected to be readable after install to the META6.json file.
Add a test (t/) to insure we report on any missing or extra files (so we can track add/remove/rename)
Remove custom Build.pm6

This task should resolve #2896

It would solve p6doc; it would probably break everything else. Main problem is that current CUR precompilation is not compatible with Documentable's cache. It would make a lot of sense if Documentable's cache was compatible with CUR, which it should really be.
Also, #2896 is solved with the new p6doc... which, alas, we haven't deployed yet. So I see this as something at the tail end of the 2.0 roadmap #2983. What do you think?

What is "the new p6doc" ?

Also, bin/p6doc doesn't use Documentable. (I'm referring to the script, not the overall repo)

The new p6doc does. Please check the roadmap, it's a project that was
finished last summer.

Can you point me at the Roadmap? I don't see one by that name in the wiki or the files in the repo.

I already did in my first reply, it's issue #2983

So, whichever of the 4 repos described in #2983 is going to install the pod files for next-gen p6doc to read needs this change to correctly install the files.
Is the plan that this repo will do that install and other repos will read them? This is what I would expect, then I would have ng-p6doc depend on this module (rather than using a git sub-module or something similar)

So, whichever of the 4 repos described in #2983 is going to install the pod files for next-gen p6doc to read needs this change to correctly install the files.
Is the plan that this repo will do that install and other repos will read them? This is what I would expect, then I would have ng-p6doc depend on this module (rather than using a git sub-module or something similar)

It already depends on documentable, since it shares some common functionality. If we eventually decide to install Raku/doc in the RESOURCES, well, we'll add it as a dependency, but for the time being what we need is to have a working documentable cache initialized. And yes, that will go to the documentation of p6doc when it's eventually deployed.

Where can I read up on the Documentable cache so I can find out what problem it's trying to solve, and why it's in conflict with the resource/ fix?
In the meantime, if you're not intending for users to install the docs and bin/p6doc from this repo, we should remove the Build.pm, and bin/p6doc - Leaving the install & tools in a broken state (esp. when fixes are occurring in a different repo) is bad for the users. (we could leave bin/p6doc if it's partially working, but I know it's broken for some cases)

Where can I read up on the Documentable cache so I can find out what problem it's trying to solve, and why it's in conflict with the resource/ fix?

Of course, in https://github.com/Raku/Documentable
It's not in conflict. It simply uses a different mechanism to index precompiled documents, due to lack of documentation of the CUR API. Anyway, the doc precompilation needs to go a bit further than that, since it also pre-indexes and does a host of other stuff.
Baseline is: it would be nice to really understand how CUR works and make it work for us here. That was pretty much laid out in this issue. Please note that this is totally independent of deploying the new p6doc. Current-new one works with current documentable.

In the meantime, if you're not intending for users to install the docs and bin/p6doc from this repo, we should remove the Build.pm, and bin/p6doc - Leaving the install & tools in a broken state (esp. when fixes are occurring in a different repo) is bad for the users. (we could leave bin/p6doc if it's partially working, but I know it's broken for some cases)

I recently merged a PR with some fixes: #3196. I'd rather have something partially working than nothing, although, TBH, p6doc usage might be so close to zero that it's totally undistinguishable from it, which might explain why there are no more complaints about it not working. Anyway, it's something that we should offer and we'll do that, as soon as we get around to it (but there are other issues in front of them).

I whole-hearted support the efforts of all to make the resources available without the user having to do a lot of magic he shouldn't have to worry about. I did file an issue with Rakudo about access to %?RESOURCES but ran into the CUR roadblock pointed out by @ugexe (issue #3821 which I closed after Nick's explanation, but he did indicate a hackery solution for the existing CUR).

This issue is not rejected, it's admitted and part of the roadmap. However, it needs some way to go... The first thing would be to make this an only-docs repo, and spinning off all tooling for generating webpages or whatever. Which will be done eventually, but as said, some way to go...

Since we don't install this repository anymore (for some time), my request to align the folder structure with the install structure doesn't matter. No need for the change unless we go back an install model.


Update deprecated Neo4jGraph import to support langchain-neo4j

Description
This PR addresses the following deprecation warning encountered during execution of the Graph Memory module in mem0:
LangChainDeprecationWarning: The class Neo4jGraph was deprecated in LangChain 0.3.8 and will be removed in 1.0. An updated version of the class exists in the langchain-neo4j package and should be used instead. To use it run pip install -U langchain-neo4j and import as from langchain_neo4j import Neo4jGraph.
Previously, using graph_memory.py triggered this warning during initialization:
\Lib\site-packages\mem0\memory\graph_memory.py:42: LangChainDeprecationWarning: The class `Neo4jGraph` was deprecated in LangChain 0.3.8 and will be removed in 1.0.
  self.graph = Neo4jGraph(

Fix Overview
The changes in \mem0\memory\graph_memory.py update the import to the new langchain-neo4j package while maintaining backward compatibility with langchain-community.
Old Import:
try:
    from langchain_community.graphs import Neo4jGraph
except ImportError:
    raise ImportError("langchain_community is not installed. Please install it using pip install langchain-community")

New Import:
try:
    from langchain_neo4j import Neo4jGraph
except ImportError:
    try:
        from langchain_community.graphs.neo4j_graph import Neo4jGraph
    except ImportError:
        raise ImportError(
            "Neither 'langchain-neo4j' nor 'langchain-community' is installed. "
            "Please install one using 'pip install langchain-neo4j' or 'pip install langchain-community'."
        )

This ensures compatibility with both the new langchain-neo4j package and the older langchain-community package, eliminating the deprecation warning.
BTW - building poetry also upgraded poetry.lock any available packages by itself, I'm not very familiar yet with poetry so will free to remove that if not necessary :)
Type of change
Please delete options that are not relevant.

[x] Refactor (does not change functionality, e.g. code style improvements, linting)

How Has This Been Tested?
I wrote a simple script that just init mem0 calss with a local ollama llm, chromadb and neo4j, before the fix the warning popup was displayed and now it dosent
Please delete options that are not relevant.

[x] Test Script (please provide)

from mem0 import Memory

config = {
        "embedder": {
            "provider": "ollama",
            "config": {
                "model": "mxbai-embed-large"
            }
        },
        "llm": {
        "provider": "ollama",
        "config": {
            "model": "llama3.2",
            }
        },
        "vector_store": {
            "provider": "chroma",
            "config": {
                "collection_name": "VectorStore",
                "path": "db",
            }
        },
        "graph_store": {
            "provider": "neo4j",
            "config": {
                "url": "bolt://localhost:7687",
                "username": "neo4j",
                "password": "yourpassword"
            }
        },
        "version": "v1.1"
}

m = Memory.from_config(config)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas (self explanatory)
[x] I have made corresponding changes to the documentation (not needed as much as I know)
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works (not needed)
[x] New and existing unit tests pass locally with my changes (locally i got errors on testing but no new ones with this changes)
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

Maintainer Checklist

[ ] closes #xxxx (Replace xxxx with the GitHub issue number)
[ ] Made sure Checks passed

 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.


updating http-server dependency to 0.9.0

https://github.com/indexzero/http-server/issues/244
It solved the issue of server crashing with : "header content contains invalid characters'); ^ TypeError: The header content contains invalid characters"

Hi @elarbi, tks for that. I'll test, merge and publish that later on

@elarbi I've merged the PR and published a new version<EMAIL_ADDRESS>Thanks for the PR.


[cPP Comment 22, 23] FCS_(D)TLSS_EXT.2

Location: FCS_(D)TLSS_EXT.2; A.7.1.2; C.2.2.2 / FCS_(D)TLSC_EXT.1.3; B.3.1.5; C.2.2.1
Comment 22: The override exceptions are much too broad. Also, a TOE should reject invalid revocation status information, but continue looking for valid information. This requirement that defines a different response for (any) invalid response could be interpreted to prevent the TOE from continuing to look for valid information.
Suggested Change: Consider omitting these exceptions altogether, or refining the allowance so that the administrator exceptions are limited to specific certificates / circumstances and the first three selections in the second selection are removed.
Comment 23: Elements 2 and 3 of this SFR appear to be contradictory: Element 3 does not allow an exception that might be defined in element 2.
Suggested Change:  Preference is to omit the exception in element 2 – it might be more reasonable for the TSF to alert (or fail and log the event to allow) an administrator to reconfigure the reference ID than to allow override of the check.

Comment 22: This sounds like it is related to TD0669, but the comment doesn't seem to match the NDcPP SFR. The SFR does not discuss "invalid revocation status information." Even if it did, I believe invalid revocation status should be treated the same way as inability to contact the revocation server. If an attacker is in a position inject invalid revocation responses, the attacker should also be able to block revocation checks.
Comment 23: I agree this is an inconsistency although it doesn't seem to have caused problems in the past.


Fail to start k3s if nm-cloud-setup is enabled

Signed-off-by: Manuel Buil<EMAIL_ADDRESS>Proposed Changes
Even though we are documenting that nm-cloud-setup service breaks the k3s cluster: rancher/docs#3336, it is a good idea to verify this when starting the k3s service and not allow it to start if the user forgot to disable that service. If the OS is not running systemd, it will deploy k3s.
Required ==> /usr/bin/sh
Types of Changes
New Feature. Verifies if nm-cloud-setup is enabled
Verification
Deploy RHEL8.4 which use nm-cloud-setup by default and run k3s. It should fail to start with the following log in journactl:
sh[1118717]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
sh[1118717]: + exit 1

Linked Issues
rancher/rke2#1053

Do we need to worry about the nm-cloud-setup.timer service as well?

My tests show that if nm-cloud-setup.service is disabled, that is enough


Add verbose flag

Adds verbose flag to NNDescent and PyNNDescentTransformer and adds the timestamped messages I added to UMAP.

Failed appveyor build seems to be due to an intermittent network problem, so I am going to merge this.

Pull Request Test Coverage Report for Build 21

42 of 46 (91.3%)  changed or added relevant lines in 3 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+1.4%) to 95.791%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pynndescent/pynndescent_.py
8
12
66.67%

Files with Coverage Reduction
New Missed Lines
%

pynndescent/pynndescent_.py
1
85.41%

Totals

Change from base Build 20:
1.4%

Covered Lines:
1775

Relevant Lines:
1853

💛  - Coveralls


Support for PHP 8.1

Got an error when try to do the basic match query
Call to undefined method Elastic\ScoutDriverPlus\Builders\MatchQueryBuilder::value()

Hey @Thavarajan, PHP 8.1 is supported. Can you please provide more details: the version of elastic-scout-driver-plus you use and the call stack (trace)?

Im running this on php8.2 with no issues. Just FYI :)


unable play youtube video [flutter Web]

This is web-based project
play YouTube video within page without having any issue.
while using some packages faced scroll issue,

I'm using AlertDialog to handle the situation.


[feature] SCXML import?

Could I pass SCXML file to xstate?

In the future, you will be able to. It will likely be in an @xstate/scxml package.

@davidkpiano Thank you for your work. I started something similar three years ago (SCXML-based): https://github.com/aksonov/statem but didn't found any community interest...
I'm maintaining RNRF component (https://github.com/aksonov/react-native-router-flux) and want to integrate it with xstate to make app navigation independent from UI layer.
One issue I was not able to solve three years ago - how to support stacks with SCXML (typical push/pop operations)? Looks like it is not supported there...

Do you mean simulating pushdown automata or simply maintaining a stack?
You can use a combination of context, assign(...), and cond: ... (<data>, <assign>, and <transition cond="..."> to simulate it, I believe.

You can use a combination of context, assign(...), and cond: ... (, , and  to simulate it, I believe.

@davvidbaker Could you clarify? I want to use state machine for app navigation. For example, from Home account, user may go to own User Profile and to Friends List. From Friends List user may go to other's User Profile pages. The question how to implement 'pop' operation for User Profile, that should go to previous state from the stack (Home OR Friends List)

More interesting situation will be if User Profile also contains "Friends List" tab. Then we could have indefinite sequence User Profile -> Friends List -> User Profile -> etc.

hey  ! great work ! any news about this feature ?

I'm also pretty interested in this feature. I find PUG as the most legible format for SCs, JSON/YAML is too verbose vertically, XML is also noisy with the closing tags. PUG would perfect, but it turns into XML, so we need xml import :)

Conversion is partially supported by https://github.com/davidkpiano/xstate/blob/master/src/scxml.ts , it ain't 100% ready yet though - so stay tuned.