How to setup Grott with HA Core?

Hi, I'm new in...how to setup Grott with HA Core?

Hi, I need to update the documentation to reflect that option, however if you install the @egguy home assistant add-on: https://github.com/egguy/grott-home-assistant-add-on/tree/main
You can configure it in MQTT only mode and then use this integration to visualise the data.
Let me know if you have any issues.

Thank u, i'll try in the next days. Thanks

i Have this issue:

MQTT send failed: [Errno 99] Address not available

and then:

MQTT send failed: Connection Refused: not authorised.

These looks like problems in setting up grott using the other integration, I can try to help here but it might be better logging an issue in the @egguy repo.
Alternatively, @egguy - if you're able to help out here that would be great.
@Salsalove - When you get this working, please can you document whatever steps you took so that we can update the documentation on the affected repos?

Hi,
I will try to update the documentation, but it won't be before at least 1 week.
@muppet3000 Can I redirect to some of your documentation on how to configure the datalogger?
@Salsalove Do you use the addon? And have you an external MQTT broker?
If you are using the mosquitto addon, HA configure the grott add-on for you. (even in non grott-HA mode) So no need to change the parameters for MQTT.

@Salsalove Do you use the addon? And have you an external MQTT broker?
If you are using the mosquitto addon, HA configure the grott add-on for you. (even in non grott-HA mode) So no need to change the parameters for MQTT.

Hi, I'm using the add-on and these are the steps:

installed the add-on "Grott - HA extension"  with this configuration (I'm using mosquitto, so I have not change mqtt parameters):

reroutered Growatt WiFi via dialogue (I tried via WiFi Configuration, in hotspot mode,  but for me the address <IP_ADDRESS> doesn't work)... <IP_ADDRESS> is HA host so mosquitto host:

installed Grott from HACS to find mqtt sensors leaving "+" in the configurator

From Grott HA extention log:

Grott settings:
_Generic:
version:             	 2.7.8
verbose:             	 True
trace:               	 False
config file:         	 grott.ini
minrecl:             	 100
decrypt:             	 True
compat:              	 False
invtype:             	 default
invtypemap:          	 {}
include_all:         	 False
blockcmd:            	 False
noipf:               	 True
time:                	 auto
sendbuf:             	 True
timezone:            	 local
valueoffset:         	 6
offset:              	 6
inverterid:          	 automatic
mode:                	 proxy
grottip              	 default
grottport            	 5279
_MQTT:
nomqtt               	 False
mqttip:              	 localhost
mqttport:            	 1883
mqtttopic:           	 energy/growatt
mqttmtopic:          	 False
mqttmtopicname:      	 energy/meter
mqttinverterintopic: 	 False
mqtttretain:         	 False
mqtttauth:           	 False
mqttuser:            	 grott
mqttpsw:             	 secret
_Growatt server:
growattip:           	 <IP_ADDRESS>
growattport:         	 5279
_PVOutput:
pvoutput:            	 False
pvdisv1:             	 False
pvtemp:              	 False
pvurl:               	 https://pvoutput.org/service/r2/addstatus.jsp
pvapikey:            	 yourapikey
pvinverters:         	 1
pvsystemid:          	 systemid1
_Influxdb:
influx:             	 False
influx2:            	 False
database:           	 grottdb
ip:                 	 localhost
port:               	 8086
user:               	 grott
password:           	 secret
organization:       	 grottorg
bucket:             	 grottdb
token:              	 secret
_Extension:
extension:          	 True
extname:            	 grott_ha
extvar:             	 {'ha_mqtt_host': 'core-mosquitto', 'ha_mqtt_port': '1883', 'ha_mqtt_user': 'addons', 'ha_mqtt_password': 'kiqueithoh5tox7dahpeav4ahSh5sooziepie3zee6xaeMohthaichiu5uyuzong'}
Grott proxy mode started

Grott - libscrc not installed, no CRC checking only record validation on length!

Hostname : 8ce4abae-grott
IP :  <IP_ADDRESS> , port :  5279

('<IP_ADDRESS>', 20872) has connected
Growatt data decrypted V2

Grott Growatt data decrypted
Growatt plain data:
00e90006033f01045847443643433433344d00000000000000000000000000000000000000004
5454d30434c4a30385700000000000000000000000000000000000000001708190e3133030000
007c00050000607c1079003a000060bc00000000000000000001404009b70000000100fa00000
000000000000000000000000000000000000000000000000000000000000000000000004e9813
88092b005400004f120000000000000000000000000000000000000000000000000089000005a
e00155de0000000ca0000063d0000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000064201eb01ae0
1cf00000216106d105c0000000000000000000000000000000000000000000000000000000300
00002900000000000000010000000000000000000003e80464000500000000000000000000000
0000000000000000000000dac0214005b00000000000000000000000000000000000000000000
00000000000000000000000052d00000000000000000000052d00000002900050c8925c600000
0300000016d000000020000033300000013000001530000004700000199000000c40000043600
00000000000000001500000000000000000000000000000000000000000000000003e80000006
200000000005b14c802c6002922742c06305c8686000100060064163000000000000086860000
000000004150415000000d040d0200010e100d030d040d030d030d020d030d030d040d030d030
d030d040000046504e10003000000290000000004190000000000000000000000000000009400
0005ff000000920000034d0000533300005333000000ca00010000013700010000019e0000000
00000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000
000000000010d040d02000100100003000401bc018c000300010000005b005b00000000000000
00002300c00000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000001833
Possible Inverter serial EEM0CLJ08W
Inverter serial not recognised - using inverter type default
Growatt new layout processing

decrypt       :  True
offset        :  6
record layout :  T06NNNNX

Grott data record date/time processing started
date-time:  2023-08-25T14:49:51
Grott values retrieved:

datalogserial        :  XGD6CC434M
pvserial             :  EEM0CLJ08W
pvstatus             :  5
pvpowerin            :  2470.0
pv1voltage           :  421.7
pv1current           :  5.8
pv1watt              :  2476.4
pv2voltage           :  0.0
pv2current           :  0.0
pv2watt              :  0.0
pvpowerout           :  0.0
pvfrequentie         :  0.0
pvgridvoltage        :  0.0
pvgridcurrent        :  0.0
pvgridpower          :  0.0
pvgridvoltage2       :  0.0
pvgridcurrent2       :  0.0
pvgridpower2         :  0.0
pvgridvoltage3       :  0.0
pvgridcurrent3       :  0.0
pvgridpower3         :  131858932.0
totworktime          :  0.0
pvenergytoday        :  0.0
pvenergytotal        :  0.0
epvtotal             :  13.7
epv1today            :  145.4
epv1total            :  140028.8
epv2today            :  20.2
epv2total            :  159.7
pvtemperature        :  49.1
pvipmtemperature     :  53.4

MQTT jsonmsg:
{"device": "EEM0CLJ08W", "time": "2023-08-25T14:49:51", "buffered": "no",
"values": {"datalogserial": "XGD6CC434M", "pvserial": "EEM0CLJ08W",
"pvstatus": 5, "pvpowerin": 24700, "pv1voltage": 4217, "pv1current": 58,
"pv1watt": 24764, "pv2voltage": 0, "pv2current": 0, "pv2watt": 0,
"pvpowerout": 0, "pvfrequentie": 0, "pvgridvoltage": 0, "pvgridcurrent": 0,
"pvgridpower": 0, "pvgridvoltage2": 0, "pvgridcurrent2": 0, "pvgridpower2":
0, "pvgridvoltage3": 0, "pvgridcurrent3": 0, "pvgridpower3":<PHONE_NUMBER>,
"totworktime": 0, "pvenergytoday": 0, "pvenergytotal": 0, "epvtotal": 137,
"epv1today": 1454, "epv1total": 1400288, "epv2today": 202, "epv2total":
1597, "pvtemperature": 491, "pvipmtemperature": 534}}
Grott MQTT topic used : energy/growatt
MQTT send failed: [Errno 99] Address not available
Grott Send data to PVOutput disabled
Grott Send data to Influx disabled
Grott extension processing started :  grott_ha
Grott HA 0.0.7-rc2 - creating EEM0CLJ08W config in HA
Grott extension processing ended :  0
Growatt packet received:
<socket.socket fd=4, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('<IP_ADDRESS>', 57652), raddr=('<IP_ADDRESS>', 5279)>
Data less then minimum record length, data not processed
Growatt packet received:
<socket.socket fd=5, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('<IP_ADDRESS>', 5279), raddr=('<IP_ADDRESS>', 20872)>
Data less then minimum record length, data not processed
Growatt packet received:
<socket.socket fd=4, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('<IP_ADDRESS>', 57652), raddr=('<IP_ADDRESS>', 5279)>
Data less then minimum record length, data not processed
Growatt packet received:
<socket.socket fd=4, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('<IP_ADDRESS>', 57652), raddr=('<IP_ADDRESS>', 5279)>
Data less then minimum record length, data not processed

So I can't see any sensor in HA.

From mosquitto broker log:

2023-08-25 14:54:05: New connection from <IP_ADDRESS>:57672 on port 1883.
error: received null username or password for unpwd check
2023-08-25 14:54:05: Client automatic disconnected, not authorised.
2023-08-25 14:54:05: New connection from <IP_ADDRESS>:35735 on port 1883.
2023-08-25 14:54:05: New client connected from <IP_ADDRESS>:35735 as Grott - HA (p2, c1, k60, u'addons').
2023-08-25 14:54:08: Client Grott - HA disconnected.
2023-08-25 14:54:14: New connection from <IP_ADDRESS>:51094 on port 1883.
2023-08-25 14:54:14: Client  closed its connection.
2023-08-25 14:54:40: Saving in-memory database to /data//mosquitto.db.
2023-08-25 14:56:14: New connection from <IP_ADDRESS>:38172 on port 1883.
2023-08-25 14:56:14: Client  closed its connection.
2023-08-25 14:58:14: New connection from <IP_ADDRESS>:39366 on port 1883.
2023-08-25 14:58:14: Client  closed its connection.
2023-08-25 14:59:08: New connection from <IP_ADDRESS>:44782 on port 1883.
error: received null username or password for unpwd check
2023-08-25 14:59:08: Client automatic disconnected, not authorised.
2023-08-25 14:59:08: New connection from <IP_ADDRESS>:35651 on port 1883.
2023-08-25 14:59:08: New client connected from <IP_ADDRESS>:35651 as Grott - HA (p2, c1, k60, u'addons').
2023-08-25 14:59:08: Client Grott - HA disconnected.
2023-08-25 15:00:14: New connection from <IP_ADDRESS>:51636 on port 1883.
2023-08-25 15:00:14: Client  closed its connection.
2023-08-25 15:02:14: New connection from <IP_ADDRESS>:36710 on port 1883.
2023-08-25 15:02:14: Client  closed its connection.
2023-08-25 15:04:08: New connection from <IP_ADDRESS>:34774 on port 1883.
error: received null username or password for unpwd check
2023-08-25 15:04:08: Client automatic disconnected, not authorised.
2023-08-25 15:04:08: New connection from <IP_ADDRESS>:54565 on port 1883.
2023-08-25 15:04:08: New client connected from <IP_ADDRESS>:54565 as Grott - HA (p2, c1, k60, u'addons').
2023-08-25 15:04:11: Client Grott - HA disconnected.
2023-08-25 15:04:14: New connection from <IP_ADDRESS>:41982 on port 1883.
2023-08-25 15:04:14: Client  closed its connection.
2023-08-25 15:06:14: New connection from <IP_ADDRESS>:33990 on port 1883.
2023-08-25 15:06:14: Client  closed its connection.
2023-08-25 15:08:14: New connection from <IP_ADDRESS>:60130 on port 1883.
2023-08-25 15:08:14: Client  closed its connection.
2023-08-25 15:09:11: New connection from <IP_ADDRESS>:47168 on port 1883.
error: received null username or password for unpwd check

Are you using grott or grott edge? From the logs I extrapolate this is the non edge version.
Can you try with the edge version? It has a lot of bug fix and is more or less the stable version.
I will probably rename and change how the addon published in the near future.

Are you using grott or grott edge? From the logs I extrapolate this is the non edge version.
Can you try with the edge version? It has a lot of bug fix and is more or less the stable version.
I will probably rename and change how the addon published in the near future.

Now I'm trying with grout edge
creation of adam gif
From Mosquitto log:

2023-08-25 18:34:15: New connection from <IP_ADDRESS>:40676 on port 1883.
2023-08-25 18:34:17: Client  closed its connection.
2023-08-25 18:36:15: New connection from <IP_ADDRESS>:55988 on port 1883.
2023-08-25 18:36:15: Client  closed its connection.
2023-08-25 18:37:02: New connection from <IP_ADDRESS>:40013 on port 1883.
2023-08-25 18:37:02: New client connected from <IP_ADDRESS>:40013 as Grott - HA (p2, c1, k60, u'addons').
2023-08-25 18:37:05: Client Grott - HA disconnected.
2023-08-25 18:37:05: New connection from <IP_ADDRESS>:33353 on port 1883.
2023-08-25 18:37:05: New client connected from <IP_ADDRESS>:33353 as Grott - HA (p2, c1, k60, u'addons').
2023-08-25 18:37:05: Client Grott - HA disconnected.
2023-08-25 18:38:15: New connection from <IP_ADDRESS>:38536 on port 1883.
2023-08-25 18:38:15: Client  closed its connection.
2023-08-25 18:39:51: New connection from <IP_ADDRESS>:46675 on port 1883.
2023-08-25 18:39:51: New client connected from <IP_ADDRESS>:46675 as Grott - HA (p2, c1, k60, u'addons').
2023-08-25 18:39:51: Client Grott - HA disconnected.

I don't understand what IP is <IP_ADDRESS>

i have another question...why the datalogger change continuously the port?

@egguy magically i can see all the sensors in the MQTT integration but the last update was on 25th August... 😔

From Grott Log i can see the data update in realtime:


Carousel control only change active item once🐛

Describe the bug
Supposed I have a Carousel on a page with 3 items on the list. After a set period of time (5 seconds by default), the control change the active item to the second one. After that it won't move to the third item at all.
To make the Carousel move to the next item after that is either to switch to another tab and switch back, to swich to other window and switch back, or to move the cursor over the control.
I've tested with the vanilla boostrap and it seems to work fine.
How to reproduce
Steps to reproduce the behavior:

Add a Carousel control on a page.
Observe the behavior.

Carousel page on Sveltestrap document is also a good way to observe the behavior.
Expected behavior
Carousel control should keeps cycling through items unless ride is set to false.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows 11
Browser: Chrome
Version: 127.0.6533.72

Mobile (please complete the following information):

Device: iPhone 13
OS:
Browser: Firefox
Version: 128.3

Additional context
Add any other context about the problem here.

I digged into the component a little bit.
The carousel moves the active item to the next using setRideTimeout() which calls setTimeout(autoNext, interval). However ... setTimeout() will run the function only once. May be we should change this to setInterval() instead ??


⚠ Samsung has degraded performance

In 368af0b, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 3040 ms

Resolved: Samsung performance has improved in 1eaaebc.


support database/sql.Null

From Go 1.22, Null type is available.

Summary by CodeRabbit

Tests

Added a test for database table creation functionality.

Refactor

Improved logic handling for type cases in database operations.
Removed specific type check for JSON in database column definitions.

New Features

Introduced a method to check for SQL null types in database interactions.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

18 of 21 (85.71%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 66.606%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

table.go
18
21
85.71%

Totals

Change from base Build<PHONE_NUMBER>:
0.2%

Covered Lines:
726

Relevant Lines:
1090

💛  - Coveralls


Invalid captcha

If you publish a post, the captcha image won't get updated for the next post

Fixed in 3992a662c131ba12afd1faedfd211941e66953c2


Improve performance of MarkerTree::is_disjoint

Summary
Resolves https://github.com/astral-sh/uv/issues/6137.

I'm struggling to find complex resolution cases that are also consistent, but it does seem to be a small improvement in most cases.

Worked on this a little more and ran some microbenchmarks, this does seem to be a significant improvement, especially for markers that are not disjoint.
marker_disjointness     time:   [118.69 ns 119.12 ns 119.55 ns]
                        change: [-40.348% -40.036% -39.771%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 12 outliers among 100 measurements (12.00%)
  12 (12.00%) high mild

marker_disjointness_current
                        time:   [307.31 ns 307.92 ns 308.60 ns]
                        change: [-1.0642% -0.8529% -0.5884%] (p = 0.00 < 0.05)
                        Change within noise threshold.
Found 18 outliers among 100 measurements (18.00%)
  15 (15.00%) low mild
  1 (1.00%) high mild
  2 (2.00%) high severe

marker_disjointness     time:   [308.82 ns 309.33 ns 309.85 ns]
                        change: [-49.069% -48.924% -48.768%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 8 outliers among 100 measurements (8.00%)
  1 (1.00%) low mild
  6 (6.00%) high mild
  1 (1.00%) high severe

marker_disjointness_current
                        time:   [1.2548 µs 1.2555 µs 1.2562 µs]
                        change: [-1.9563% -1.6812% -1.4606%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 1 outliers among 100 measurements (1.00%)
  1 (1.00%) high mild

Nice win! Order of magnitude improvement in the second benchmark. Is that the case where the markers aren't disjoint?

Yup, that's when the markers are not disjoint, so the latter case ends up creating the conjoined markers that we just throw away.


[Communication - Identity] PhoneNumbersClient - get phone number [AAD] can get a purchased phone number failing in nightly runs

Communication - Identity nightly test runs are failing with:

Error message:
Input phoneNumber +18334567952 cannot be found.
Stack trace:
RestError: Input phoneNumber +18334567952 cannot be found.
at handleErrorResponse (/mnt/vss/_work/1/s/sdk/core/core-client/src/deserializationPolicy.ts:251:17)
at deserializeResponseBody (/mnt/vss/_work/1/s/sdk/core/core-client/src/deserializationPolicy.ts:159:43)
at processTicksAndRejections (internal/process/task_queues.js:97:5)

For more details check here:

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1563628&view=results

@Azure/acs-identity-sdk for notification.

looking at the error, this seems to be related to the phone number service

The number has been put back on the resource and the pipeline is working again.


[3281] Add discard to users

Context
Changes proposed in this pull request
Guidance to review
Checklist

[ ] Make sure all information from the Trello card is in here
[ ] Attach to Trello card
[ ] Rebased master
[ ] Cleaned commit history
[ ] Tested by running locally

 Soft delete users


not work for me

hey is this still working i tried install it but nothing works

it's not working for me to :'( (i'm on firefox)

DiscordPlus+ is now back!


[now-client] Create Static Deployment

Is there going to be support for static deployments? Either in the now-client or in the private API and detect the deployment type?
When I try to deploy without a package in the body it returns the following error:
StatusCodeError: 500 - {"err":{"code":"internal_server_error","url":"https://zeit.co/errors/internal_server_error","message":"An unexpected error occurred"}}

What I would like to be able to do is something like:
const NowClient = require('now-client')

const now = new NowClient();

const create = async () => {
  try {
    const body = {
      'index.html': 'Hello World!',
    };
    const deployment = await now.createDeployment(body);
    console.log(deployment);
  } catch(e) {
    console.log(e);
  }
};

create();

This has been implemented, however the API has changed a lot since 2017.
Take a look at the now-client npm package to see example usage.
Thanks!


fix: tag name in RHP is not correct

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/37783
PROPOSAL: https://github.com/Expensify/App/issues/37783#issuecomment-1987648438
Tests

Precondition:

User is an employee of Collect workspace.
The Collect workspace has dependant multilevel tag set up. (details here for how to setup)
The multilevel tag is as follow:
First level: State
Second level: Region

Go to workspace chat.
Create a manual request with first and second level of tag.
Go to request details page.
Click the first level tag (State).
Click the second level tag (Region).
When the respective level tag is opened, the RHP will show the correct tag name (Step 4 and 5).

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

Precondition:

User is an employee of Collect workspace.
The Collect workspace has dependant multilevel tag set up. (details here for how to setup)
The multilevel tag is as follow:
First level: State
Second level: Region

Go to workspace chat.
Create a manual request with first and second level of tag.
Go to request details page.
Click the first level tag (State).
Click the second level tag (Region).
When the respective level tag is opened, the RHP will show the correct tag name (Step 4 and 5).

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

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

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/113963320/cad2099c-79b1-4474-a0d1-d2796769cdcf

Android: mWeb Chrome

https://github.com/Expensify/App/assets/113963320/34817778-9045-42b4-8967-7e3177ed5a4c

iOS: Native

https://github.com/Expensify/App/assets/113963320/ec8951e9-1cff-4f31-856e-7f7c3c27332f

iOS: mWeb Safari

https://github.com/Expensify/App/assets/113963320/e5e0d806-262b-4484-a359-98c6b5f97d8f

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/113963320/4fd0ae0b-2cb4-48cc-9749-243ac805b266

MacOS: Desktop

https://github.com/Expensify/App/assets/113963320/383d3aef-15a9-4109-a3a3-49da661572d0

Ah yep, so there was an effective dupe of the issue - that's definitely frustrating. I'll start an internal discussion on compensation since work was done here.

my solution also uses the orderWeight as the id to put in the route instead of tagIndex.

I do still like the idea of updating our usage of tagIndex as I feel like otherwise we're opening ourselves up to re-experiencing this kind of bug.
Let me double check with the team and I'll get back to you tomorrow on whether or not to proceed. Otherwise we can provide 50% compensation for the investment into the issue and time-spent 🙇

Sorry fro the delay here - I've got consensus that we should move forward with the change to use orderWeight

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/NikkiWines in version: 1.4.63-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/mountiny in version: 1.4.63-21 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Heading levels in the "Testimonials" section

Looks like "Elsewhere Around the Internet" should probably be a level 1 heading (like "Testimonials")? Not sure.
http://hdlab.stanford.edu/palladio/testimonials/

Checked in fix to bring in line with Testimonials & the Tutorials/FAQ page.


How to test an action?

Hi,
Thanks for writing this great library. I can't believe this is not built into vuex. I hope vuex + typescript will be a better match once vue3 is out.
Anyway, my question is: how can I test an action now that we use moduleActionContext inside the actions?
I get:
TypeError: Invalid value used as weak map key

export const fooActionContext = (context: any) =>
    moduleActionContext(context, fooModule)

My code is:

// foo.ts
import { Context } from './types';
import { fooActionContext } from './store';

export const actions = {
  foo(context: Context) {
    const { commit } = fooActionContext(context)
  }
} as const

// fooModule.ts
import { actions } from './foo';

export const fooModule = {
  namespaced: true,
  state: {},
  getters: {},
  actions,
  mutations: {}
} as const

// foo.test.ts
import { actions } from './foo';

test("foo", async () => {
  const commit = jest.fn()
  await actions.foo({ commit } as any)

  expect(commit).toHaveBeenCalled()
})

// store.ts
import Vue from 'vue';
import Vuex from 'vuex';
import { createDirectStore } from 'direct-vuex';
import { fooModule } from './fooModule';

Vue.use(Vuex)

export const { moduleActionContext } = createDirectStore({
  state: {},
  modules: {
    fooModule
  }
} as const)

export const fooActionContext = (context: any) =>
  moduleActionContext(context, fooModule)

What am I doing wrong? And how should I test an action how that we call fooActionContext() inside the action?
Thanks in advance!

Internally, I use the original 'dispatch' function as a key for a cache. I've just disabled the cache if 'dispatch' is not defined. Please upgrade and test again.

I upgraded and it is working now! Thanks! :tada:
Quick question:
I typecast the object with the spy function as any:
await actions.foo({ commit } as any)

Is there a better approach so that I can avoid using any?

Another thing. If I add an action bar:
export const actions = {
  foo(context: Context) {
    const { commit, dispatch } = fooActionContext(context)
    dispatch.bar()
    commit.FOO()
  },
  bar(context: Context) {
    console.log("bar")
  }
} as const

And then try to test it:
import { actions } from './foo';

test("foo", async () => {
  const commit = jest.fn()
  const dispatch = jest.fn()
  await actions.foo({ commit, dispatch } as any)

  expect(commit).toHaveBeenCalled()
  expect(dispatch).toHaveBeenCalledWith()
})

Then I get:
TypeError: dispatch.bar is not a function

    6 |   foo(context: Context) {
    7 |     const { commit, dispatch } = fooActionContext(context)
>  8 |     dispatch.bar()
       |              ^
    9 |     commit.FOO()
  10 |   },
  11 |   bar(context: Context) {

Maybe not so strange. But then I would expect the same error with commit?
Can you provide an example on how to test actions when using this library? It is a little different than passing dispatch/commit in as spies like we usually do :slightly_smiling_face:

In foo.test.ts, add a first import: import './store'.
There is a mutual import due to fooActionContext:
export const fooActionContext = (context: any) =>
  moduleActionContext(context, fooModule)

If the actions are imported first, then, in fooActionContext, the fooModule object has properties actions and mutations set to undefined.

Is there a better approach so that I can avoid using any?

You could declare the action without a Context type:
foo(context: any)

It is valid IMHO because we don't use anything directly in this context object.

Hmmm....my sort-typescript-imports vscode extension is preventing me from importing store on the first line :laughing:
If I disable the extension it works...hmmm...I will think about what to do.
Btw, I really like the changes in 0.8. Much nicer! :+1:
Thanks again!

Maybe you could try with the old way?
require("./store")

Thanks for the tips! I will find a solution that works 🙂

I think I can close this issue.


Nuscenes Minidataset

@xinge008  Thanks for sharing the code base i have the following queries
1.To generate the .pkl files  should we always use SECOND code base as you have mentioned
2.To save the  predictions along with label should we follow the same steps mentioned in polar seg ?
Support will be highly appreciated !!!

To save the prediction, you can refer this line. In this way, you can obtain the prediction.

@xinge008  i have used the same method but for visualisation of nuscenes we need to color code it similar to semanttick kitti

For color coding, you can refer to the color mapping in SemanticKITTI


Remove deprecated config for 5.0

Meta issue => https://github.com/elastic/logstash/issues/3858

LGTM!


fix: replace celerybeatmongo repo

Description
This PR replaces celerybeatmongo repository. It contains PR fixing can't compare offset-naive and offset-aware datetimes error.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] Bug fix

How Has This Been Tested?
Integration tests
Checklist

[x] My commit message is conventional
[x] I have run pre-commit on all files before creating the PR
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have checked my code and corrected any misspellings

Codecov Report

Merging #448 (fe513c0) into develop (fe5a6d3) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #448   +/-   ##
========================================
  Coverage    87.00%   87.00%
========================================
  Files           23       23
  Lines         1424     1424
========================================
  Hits          1239     1239
  Misses         185      185

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 fe5a6d3...fe513c0. Read the comment docs.

:tada: This PR is included in version 1.6.1-beta.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


findMatchingElement to return a React node

Is your feature request related to a problem? Please describe.
I think containsMatchingElement is great but unfortunately it can't be used to return the matched element. I'm stuck with findWhere.
Describe the solution you'd like
  findMatchingElement(node) {
    const rstNode = getAdapter(this[OPTIONS]).elementToNode(node);
    const predicate = other => nodeMatches(rstNode, other, (a, b) => a <= b);
    return findWhereUnwrapped(this, predicate);
  }

Describe alternatives you've considered
findWhere should work, but IMO using React element is nice and easy.

I suppose you could do wrapper.findWhere(n => n.matchesElement(nodeToMatch))?


Spawns kernels when loading atom (?)

I think (and it's really hard to reproduce) that when I reload atom, in dev mode, sometimes a julia thread spawns that take 100% CPU.

This doesn't sound like a thing that would happen, but please let me know if you figure out anything more. Hydrogen should only be starting kernels when you first tell it to run some code. In fact, Hydrogen itself shouldn't be activated by Atom until you use hydrogen:run or its shortcut.

Definitely happens when I start an atom session in ~.

Can you open the console in the Atom dev tools (View -> Developer) and see what Hydrogen is printing out?  I had the same issue with them, but not with hydrogen - it doen't start kernel on atom restart.
You can check this by:
ps aux | grep hydrogen

@tpoisot I'm closing this issue. Please, feel free to reopen if you still need help.

that's fine -- I removed the package bc  the issue persisted, and use the notebook instead.
t

Le 21 juil. 2016 à 10:06, Nicolas Riesco<EMAIL_ADDRESS>a écrit :
@tpoisot I'm closing this issue. Please, feel free to reopen if you still need help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Reopening because the issue persists.

Oh really I just checked and can't reproduce this.

@lgeiger Did you use the IJulia kernel?

I should have read the issue more carefully. No, I only have python, root and ijavascript installed.

@n-riesco have you experienced this lately? I know when i first tried out the uber-juno (and the packages it installs) I was having issues with it having conflicting keybindings with Hydrogen.
uber-juno installs: tool-bar, latex-completions, language-julia, ink, julia-client
I disabled uber-juno packages early on because I thought it was spawning julia on startup, but have since tried and not seen the same issue.

@BenRussert I've just tested IJulia v1.4.1 on Hydrogen v1.6.0 and the 100%-CPU spike is hardly noticeable.

A comment for IJulia users:
IJulia users should expect a little delay when running IJulia for the first time after installation (because the package has to be precompiled; Hydrogen now shows a notification when this happens). But this delay is a one time thing. It won't happen next time you run IJulia.

@n-riesco You've given an excellent explanation. Thanks!
@lgeiger How do you feel about closing this issue as resolved?

@n-riesco Thanks for the great explanation and testing!
I think we can close this as resolved 👍
@tpoisot Feel free to reopen if you still have issues.


opt: do not materialize changed vec

As per
[this][https://github.com/thrumdev/nomt/pull/323#discussion_r1730422403]
comment, allocation in get_changed is not insignificant. This commit
avoids allocation of a vector by passing an iterator.

#329  👈
master

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

Join @pepyakin and the rest of your teammates on  Graphite


undefined reference to makedev

Build on raspberry pi zero w with gentoo fails with the error above.
This is probably due to glibc-2.24+ not including sysmacros.h from types.h
Thus, please #include <sys/sysmacros.h>
in pigpio.c
Adding this line fixes the issue.

Hi, that would be great if that could be added.
I'm also creating an ebuild for gentoo (currently using HEAD on the git repo),
are there any plans to have release versions or will this just stay fluid?

Should be fixed in V65.


Engineering departament

About the PR
Adds an Engineering department, Chief Engineer, Ordnance Tech. Maintenance Tech, theirs jumpsuits and more gloves.
Why / Balance
Resolves #131, resolves #133, resolves #134, resolves #137, resolves #139, resolves #140, resolves #141, resolves #143, resolves #144
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl: Tunguso4ka

add: Engineering department has been added to the game.

yay, SubprocessException ComputeManagedAssemblies not found.


Add promise API.

Add promise API.

Coverage increased (+0.5%) to 97.802% when pulling 5b05cbdac799343761dd570f32f90f4caba0cd3f on promise-api into 10d20a9c5033fef57204983efb534b28ea427691 on master.


[FLINK-9692][Kinesis Connector] Fix bug in adaptive reads implementation

Previous PR had a bug in the implementation that inflated averageRecordSizeInBytes and thus set maxNumberOfRecordsPerFetch to 0 in some cases resulting in a ValidationException from AWS.

👍


[Chore] Add amino name for tx msgs

Closes: #XXX
What is the purpose of the change
Tons of the messages were broken when we moved to using telescope
Testing and Verifying
n/a
Documentation and Release Note

[ ] Does this pull request introduce a new feature or user-facing behavior changes?
[ ] Changelog entry added to Unreleased section of CHANGELOG.md?

Where is the change documented?

[ ] Specification (x/{module}/README.md)
[ ] Osmosis documentation site
[ ] Code comments?
[ ] N/A

What is the pattern we are choosing for these names? It seems some go osmosis/module/name and other osmosis/name

What is the pattern we are choosing for these names? It seems some go osmosis/module/name and other osmosis/module-name

whatever is listed in the codec.go file


consider testharness.js

we should consider porting the tests to https://github.com/w3c/testharness.js
-- mainly because it is used in the web-platform-tests and we might be able to cross-pollinate between the tests here and the webrtc/mediacaptuer tests there.

To clarify, that's instead of tape/chai? Webdriver/mocha will still drive the test?
@alvestrand @foolip wdyt?

instead of tape for running in-browser tests. The mocha/chai stuff is unit tests

testharness.js works well for things other than testing built-in browser APIs, and I personally enjoy using it. Getting more people using it decreases the barrier to contributing to web-platform-tests, which obviously would be great :)

I have a PR in wpt which does one of the tests I have in mind. Now I need to figure out how to

sync tests between wpt and adapter
run the wpt tests from our CI after inserting adapter

NPM all the things!

I ported some tests here
Feels ok to use. Now I need to figure out how the wpt run on travis... that looks neat!

the karma/mocha/chai combo was more attractive (#597)


Editor in mdbook looks much worse on Chrome

More fun re Web stuff — unfortunately my CSS antics don't seem work on Chrome, and so the left column is much wider than the right.
Firefox:

Chrome:

Closed by https://github.com/max-sixty/prql/pull/329


Fixed issue with email regular expression

This bug is fixing the issue reported in issue #11

@hkellaway I don't why I can't add you to the reviewers, but here is the PR to fix your issue.


constify all payload paths

(builds on top of gmsk_improvements)
this constifies all user payload paths, silencing related const warnings

It looks like you made some changes to master recently to do something similar. Is this patch obsoleted?


7707 validator slashing protection

PR Description
Add --validator-slashing-protection-enabled option to enable VC shutdown when a validator gets slashed.
When using a remote BN, this option requires the BN to support the new attester_slashing and proposer_slashing SSE events.
In order to ensure BN backward compatibility, the VC will subscribes to the attester_slashing and proposer_slashing SSE events only when the --validator-slashing-protection-enabled is enabled (in addition to the head events) otherwise it will only subscribe to the head events.
Fixed Issue(s)

fixes #7707
Documentation

[x] I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

[x] I thought about adding a changelog entry, and added one if I deemed necessary.

When the VC is used with a remote BN that doesn't support the attester_slashing and the proposer_slashing events the SSE connection will fail (and retry with the failover BN if any). I'm trying to customise the retry strategy in EventSourceBeaconChainEventAdapter::createEventSource to exclude the attester_slashing and proposer_slashing topic from the query params when the request fails but didn't find a way to do it yet. Not sure if that's even possible

im not sure where to test so general observation...
Negative testing -
eg. a slashing occurs which is not a validator we're a custodian of - should not shut us down :)
This would be hard to replicate on a network, slashings aren't super common so we might end up not seeing it, but we'd be easily able to see we don't trigger if a slashing we don't care about arrives at a low level i assume...

only minor things - may be worth a demo to show it working...

@rolfyone and @zilm13 fyi, I pushed these lasts changes: https://github.com/Consensys/teku/pull/7826/commits/d99c2fa923f5845ede483a1eb7ff37e711fe5adf in order to handle the use case when the BN/VC are running in a single process and thus not using SSE. I tested both use cases and they both work (remote BN and single process VC/BN)
I had a discussion with @tbenr and we were thinking that it might be cleaner to move the slashing actions to a separate channel (other than ValidatorTimingChannel, something like ValidatorSlashingChannel) or we could leave as is...
Let me know if you have any thought otherwise I could demo the current implementation and then we merge it

Let me know if you have any thought otherwise I could demo the current implementation and then we merge it

My main thought is theres a lot of renaming in this and it makes it a lot harder than it needs to be to review. this kind of cleanup should be kept outside of substantive changes, it's just good practice and probably would have made this not look like a 'big pr' that i hate so much.
I'm not sure that the feature is 'done' given the code here, and would like to see some testing around a few things, and agree with @zilm13 that an acceptance test will be important.
A demo will make me more confident without setting it all up to see exactly what's going on, and we need to make sure we're clear about what we're asking in usage, which i briefly noted.
I think given the outstanding bits, we might want to mark the cli arg as hidden, remove the change entry, and merge this part, then unhide the entry once we're actually done and at that point we can add a change entry. We definitely want to hold off merging until after the release is done.
I think this is a good example of why we outline how to do a feature. Not following our own processes and trying to rush one in has probably made this a lot harder and ultimately take a lot longer than it needed to.

Let me know if you have any thought otherwise I could demo the current implementation and then we merge it

My main thought is theres a lot of renaming in this and it makes it a lot harder than it needs to be to review. this kind of cleanup should be kept outside of substantive changes, it's just good practice and probably would have made this not look like a 'big pr' that i hate so much. I'm not sure that the feature is 'done' given the code here, and would like to see some testing around a few things, and agree with @zilm13 that an acceptance test will be important. A demo will make me more confident without setting it all up to see exactly what's going on, and we need to make sure we're clear about what we're asking in usage, which i briefly noted. I think given the outstanding bits, we might want to mark the cli arg as hidden, remove the change entry, and merge this part, then unhide the entry once we're actually done and at that point we can add a change entry. We definitely want to hold off merging until after the release is done.

Few remarks here:

The feature is now complete. We now support both separate VC and single process VC/BN
For clarity, I renamed the option to shut-down-when-validator-slashed to make it clear that we shut down whatever we're running (separate VC or a VC/BN node). This is explained in the documentation PR in more details
To make things clear, this feature works in both cases: separate VC (the VC is shut down) and VC/BN in a single process (the whole Teku node is shutdown). There is a documentation PR for more details since we can't put all of them in the option description. Please check https://github.com/Consensys/doc.teku/pull/526
There is only one renaming/refactoring of the SlashingRiskDetectionAction in order to reuse what has been already done for the doppelganger detection. There are existing tests for the refactored files already and that hasn't been changed
There a separate PR to add an acceptance test: https://github.com/Consensys/teku/pull/7852
There isn't a detailed spec for this feature so the implemented behaviour could be changed if needed
I will do a demo to show how this feature works

I think it would be valuable to have AT tests both for separate VC and single node BN+VC as far as we found it's different cases

The feature is now complete. We now support both separate VC and single process VC/BN

remarks / conversation welcome. imo this feature is yet to meet our definition of done, and we can continue on this path this time, but in future (im sure i said that last time) i have a very strong preference for not following this methodology. I'm not sure I can make that any clearer at this point.

My suggestion:

hide cli arg (-X, undocumented)
remove changelog entry until acceptance test is ready to merge at least
get this tested enough to accept a merge so we can move past this huge pr, and we finish the feature when it is fully acceptance tested.

Alternatively use this as a starting point, break it down, as previously suggested.


Add downgraded inputs

This implements InputPin for gpio A and B in input mode and makes downgrade downgrade all pins, not just outputs.

If you have an InputPin, you downgrade it, and then, you can use set_high from OutputPin, no? It looks bad.

That would certainly be bad but unless i'm mistaken, I don't think that's the case.
The downgraded impl of OutputPin looks like this:
impl<MODE> OutputPin for $PXx<Output<MODE>>

And for input pins:
impl<MODE> InputPin for $PXx<Input<MODE>>

Additionally, the downgrade impl looks like this
 impl<MODE> $PXi<MODE> {
    pub fn downgrade(self) -> $PXx<MODE> {

As far as I understand, the above code means that MODE will be inherited which to me seems like it would mean that you can only get a downgraded Output from a real Output and same for Input.
Or did I miss something important here?


Update kafka vendor to support detect kafka broker controller

Problem:
Test function for sending log couldn't support auto-detect kafka broker
controller now, when user input a broker endpoint which isn't the controller couldn't create kafka topic.
Solution:
update kafka vendor and detect broker controller
Issue:
https://github.com/rancher/rancher/issues/19448
Related test PR:
https://github.com/rancher/validation/pull/159

updated

LGTM


IndexError: list index out of range

Hello!
I trained this model with own dataset, but it fails in the mAP evaluation phase, does anyone have the same problem?
(tensorflow) root@gpuserver:/home/gpuserver/models/yolact# python train.py --config=yolact_base_config
loading annotations into memory...
Done (t=0.03s)
creating index...
index created!
loading annotations into memory...
Done (t=0.00s)
creating index...
index created!
Initializing weights...
Begin training!
/root/anaconda3/envs/tensorflow/lib/python3.6/site-packages/torch/nn/parallel/_functions.py:61: UserWarning: Was asked to gather along dimension 0, but all input tensors were scalars; will instead unsqueeze and return a vector.
warnings.warn('Was asked to gather along dimension 0, but all '
[  0]       0 || B: 5.480 | C: 23.075 | M: 5.976 | S: 67.004 | T: 101.536 || ETA: 0:00:00 || timer: 23.377
[  0]      10 || B: 4.757 | C: 18.774 | M: 5.625 | S: 47.000 | T: 76.155 || ETA: 11 days, 7:25:02 || timer: 1.176
[  0]      20 || B: 4.587 | C: 15.804 | M: 5.362 | S: 29.147 | T: 54.900 || ETA: 11 days, 7:50:00 || timer: 1.180
[  0]      30 || B: 4.582 | C: 13.355 | M: 5.309 | S: 19.954 | T: 43.199 || ETA: 11 days, 6:14:29 || timer: 1.272
[  0]      40 || B: 4.553 | C: 11.175 | M: 5.306 | S: 15.150 | T: 36.183 || ETA: 11 days, 6:35:18 || timer: 1.266
[  0]      50 || B: 4.497 | C: 9.617 | M: 5.303 | S: 12.227 | T: 31.645 || ETA: 11 days, 6:12:37 || timer: 1.120
[  0]      60 || B: 4.433 | C: 8.514 | M: 5.290 | S: 10.265 | T: 28.503 || ETA: 11 days, 4:48:22 || timer: 1.166
[  1]      70 || B: 4.383 | C: 7.700 | M: 5.304 | S: 8.850 | T: 26.237 || ETA: 11 days, 7:53:19 || timer: 1.236
[  1]      80 || B: 4.339 | C: 7.073 | M: 5.269 | S: 7.781 | T: 24.464 || ETA: 11 days, 6:55:00 || timer: 1.173
[  1]      90 || B: 4.294 | C: 6.585 | M: 5.250 | S: 6.945 | T: 23.074 || ETA: 11 days, 6:22:39 || timer: 1.217
[  1]     100 || B: 4.235 | C: 6.015 | M: 5.230 | S: 5.666 | T: 21.147 || ETA: 11 days, 5:30:35 || timer: 1.259
[  1]     110 || B: 4.131 | C: 4.426 | M: 5.184 | S: 1.178 | T: 14.920 || ETA: 11 days, 4:57:38 || timer: 1.177
[  1]     120 || B: 4.045 | C: 3.427 | M: 5.202 | S: 0.242 | T: 12.915 || ETA: 11 days, 4:43:12 || timer: 1.214
[  2]     130 || B: 3.926 | C: 2.860 | M: 5.195 | S: 0.192 | T: 12.174 || ETA: 11 days, 5:57:53 || timer: 2.714
[  2]     140 || B: 3.817 | C: 2.654 | M: 5.138 | S: 0.180 | T: 11.789 || ETA: 11 days, 5:43:35 || timer: 1.230
[  2]     150 || B: 3.694 | C: 2.571 | M: 5.045 | S: 0.170 | T: 11.480 || ETA: 11 days, 5:23:29 || timer: 1.217
[  2]     160 || B: 3.617 | C: 2.516 | M: 4.966 | S: 0.158 | T: 11.256 || ETA: 11 days, 5:37:45 || timer: 1.277
[  2]     170 || B: 3.540 | C: 2.467 | M: 4.876 | S: 0.149 | T: 11.031 || ETA: 11 days, 5:16:56 || timer: 1.222
[  2]     180 || B: 3.440 | C: 2.419 | M: 4.831 | S: 0.141 | T: 10.831 || ETA: 11 days, 4:54:42 || timer: 1.176
[  2]     190 || B: 3.342 | C: 2.364 | M: 4.716 | S: 0.135 | T: 10.558 || ETA: 11 days, 4:41:58 || timer: 1.187
Computing validation mAP (this may take a while)...
Traceback (most recent call last):
File "train.py", line 374, in
train()
File "train.py", line 303, in train
compute_validation_map(yolact_net, val_dataset)
File "train.py", line 367, in compute_validation_map
eval_script.evaluate(yolact_net, dataset, train_mode=True)
File "/home/gpuserver/models/yolact/eval.py", line 791, in evaluate
prep_metrics(ap_data, preds, img, gt, gt_masks, h, w, num_crowd, dataset.ids[image_idx], detections)
File "/home/gpuserver/models/yolact/eval.py", line 401, in prep_metrics
ap_obj = ap_data[iou_type][iouIdx][_class]
IndexError: list index out of range

Can you share your dataset config object and annotation file?
Also, are you on the latest commit?

Thanks a lot for your reply!
Here is my config object:
my_custom_dataset = dataset_base.copy({
'name': 'My Dataset',
'train_images': '../data/cocolike/coco/images/train2017/',
'train_info':   '../data/cocolike/coco/annotations/instances_train2017.json',

'valid_images': '../data/cocolike/coco/images/val2017/',
'valid_info':   '../data/cocolike/coco/annotations/instances_val2017.json',

'has_gt': True,
'class_names': MY_CLASSES,
'label_map': MY_LABEL_MAP

})
and MY_CLASSES and MY_LABEL_MAP are:
MY_CLASSES = ('person')
MY_LABEL_MAP = { 1:  1 }
Here is my last annotation object:
{
"id": 163,
"image_id": 58,
"category_id": 1,
"segmentation": [
[
436,
344,
467,
333,
495,
321,
534,
308,
561,
306,
561,
318,
557,
349,
561,
395,
563,
422,
554,
435,
522,
440,
501,
442,
474,
441,
451,
424,
439,
402,
427,
376
]
],
"bbox": [
427,
306,
136,
136
],
"iscrowd": 0,
"area": 1.0
}
],
"categories": [
{
"id": 1,
"name": "person"
}
]
}
After searching for the solution, I find that the problem is the class name, shall I change the class name from "person" to "person_person" in the annotation file or ?
THX!

I don't think it's the name of the classes, since I don't actually use those anywhere except for displaying purposes. Are you sure that every category_id in your annotation is a 1? Looking at the error more in depth, it looks like it could be caused by a category_id that is not 1.

Hi,
Thanks for your reply!
You are right, something wrong with the converter of the labelme2coco, after retrying converting again the problem is now solved
Thanks a lot!
I rly love this model!

Glad to see that worked!

@remindchobits I am facing same kind of issues , did you change anything in lableme2coco.py file?

cocolike

@remindchobits Hi I have a question about this annotation file. Did you use the already given .json file (instances_train2017.json) or you made your own custom? because the last annotation object you posted I dont know how to make my own annotation file. I just want to predict persons only in the image.

Thanks a lot for your reply!
Here is my config object:
my_custom_dataset = dataset_base.copy({
    'name': 'My Dataset',

    'train_images': '../data/cocolike/coco/images/train2017/',
    'train_info':   '../data/cocolike/coco/annotations/instances_train2017.json',

    'valid_images': '../data/cocolike/coco/images/val2017/',
    'valid_info':   '../data/cocolike/coco/annotations/instances_val2017.json',

    'has_gt': True,
    'class_names': MY_CLASSES,
    'label_map': MY_LABEL_MAP
})

and MY_CLASSES and MY_LABEL_MAP are:
MY_CLASSES = ('person')
MY_LABEL_MAP = { 1:  1 }

Here is my last annotation object:
  {
   "id": 163,
   "image_id": 58,
   "category_id": 1,
   "segmentation": [
    [
     436,
     344,
     467,
     333,
     495,
     321,
     534,
     308,
     561,
     306,
     561,
     318,
     557,
     349,
     561,
     395,
     563,
     422,
     554,
     435,
     522,
     440,
     501,
     442,
     474,
     441,
     451,
     424,
     439,
     402,
     427,
     376
    ]
   ],
   "bbox": [
    427,
    306,
    136,
    136
   ],
   "iscrowd": 0,
   "area": 1.0
  }
 ],
 "categories": [
  {
   "id": 1,
   "name": "person"
  }
 ]
}

After searching for the solution, I find that the problem is the class name, shall I change the class name from "person" to "person_person" in the annotation file or ?
THX!

@remindchobits
Hi I have a question about this annotation file. Did you use the already given .json file (instances_train2017.json) or you made your own custom? because the last annotation object you posted I dont know how to make my own annotation file. I just want to predict persons only in the image.

how did you deal with the1 problem?please!


[Feature]:Theme for Indie-Kart

Describe the feature
we can add theme for the web ,
light and dark mode
Add ScreenShots

here we can add dark and light mode toggle button
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@trishanu-init ,please assign me


Scalability benchmarks

Empress needs to be run against a huge tree (> 1 million tips)

Just wondering if there are any updates on this issue; thank you.

Installed the latest version of empress and ran it on one of the large trees generated in Qiita within a 2020.2 Qiime2 conda environment;  the mapping file, feature-table and taxonomies from the moving pictures dataset - only one dataset.
Note that this is a tree was created over a year ago (we could generate even  larger today), is the 100bp fragments insertion tree and is ~8.8M tips:
In [1]: from skbio import TreeNode
In [2]: tree = TreeNode.read('../insertion_tree.relabelled.tre')
In [3]: print(tree.count(tips=True))
8830174

I generated the no-taxonomy, GG and Silva added empress qzv's to test, each takes ~3hrs to generate the qzv and it works just fine (no error messages). However, when I try to open them in https://view.qiime2.org/, the browser fails with:

and if I unzip the qzv and try to open the index.html or empress.html, I get:

Anyway, here are the testing files.
cc: @ElDeveloper

@antgonza I'm looking into this

Once we identify upper bounds for what sorts of data sizes Empress can comfortably visualize, we should document this clearly in the README so that e.g. users with billion-tip trees know that they probably want to consult another tool and/or a priest ._.


ENH: use the ISO8601 delimiters for date

ISO8601 date delimiter is "-", not "/"
space between date and time is now accepted as modification of ISO8601 standard so no change there

Description
Existing: Transient Scan ID: 17     Time: 2019/02/22 14:22:52
Revised: Transient Scan ID: 17     Time: 2019-02-22 14:22:52
Motivation and Context
Cosmetics:  why not use ISO standard format here?

Codecov Report

Merging #1148 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #1148   +/-   ##
======================================
  Coverage    89.3%   89.3%
======================================
  Files          51      51
  Lines        8556    8556
======================================
  Hits         7641    7641
  Misses        915     915

Impacted Files
Coverage Δ

bluesky/callbacks/best_effort.py
73.13% <ø> (ø)
: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 7772017...60bbb05. Read the comment docs.

@mrakitin Thanks for the review!


Closes (#1700) in docs

All I did:

I made the data-collection.md file contain the theory/definitions of the components of OpenTel Collector.
I made the configuration.md file contain only the configurations examples for the components and stripped all definitions. I made grammatical changes to improve technical perception.
I made significant changes to both files, like tables (requires adding  to the static site generator to show the ticks. Or replacing the :heavy_check_mark: with something else.), and more elaborate definitions with example scripts.

thanks @theghostmac , can you make sure that you sign the CLA & that the build works:

1:27:55 AM: ERROR 2022/10/05 23:27:55 docs/concepts/data-collection.md: use a local path, not an external URL, for the following reference to a local page: https://opentelemetry.io/docs/concepts/signals

I'd (somewhat strongly) vote against committing any .idea files. Consider adding /.idea to the top-level .gitignore file.
WDYT @svrnm?

I assume this was a mistake. Let's add it to the .gitignore

@theghostmac have you had a chance to look through feedback here?

Yes. I am trying to finish up with the work that brought me to the repository, after that, I'll fix the issues.
Thanks for reminding me.

@tigrannajaryan  I changed the wording to simply "export data"; would that be sufficient?

Closing due to inactivity, and there's now conflicts. If you'd like to get these changes in, please ping here or resubmit and we'll take a look.


Conditional or

Fix #22

:tada: This PR is included in version 1.4.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[MM-22618] Clicking on setting team links to proper tab

Summary
When clicking on a server on the settings page to open that server's tab, if tabs were manually reordered, the proper incorrect tab can load. This PR takes into account the manual tab order to ensure that clicking on a server on the settings page will load the correct tab.
Issue link
https://mattermost.atlassian.net/browse/MM-22618

@deanwhillier
Error trying doing the automated Cherry picking. Please do this manually


docs: add polarpoint.io

Checklist:

[ ] My organization is added to USERS.md.

I'm no longer able to accept the DCO for this PR. Instead, I'm presented with the set-up page:

@simster7 does it work for you.
@edlee2121 FYI


Avar2 support in font identification and contour variations / situations where coords are provided

In https://docs.rs/read-fonts/latest/read_fonts/tables/avar/type.Avar.html#method.version it says that Major version is set to 1.

For identification of avar2 fonts in Blink it would be useful if this API would be able to return 2 for avar2 fonts.

For applying axis variations and retrieving paths in Skrifa, Glyph::draw, and in situations where normalized coords are provided, Skrifa would need to know how to apply avar2 axes.

CC @behdad

Yeah, applying the ItemVariationStore only. It's this code:
https://github.com/harfbuzz/harfbuzz/blob/f35b0a63b1c30923e91b612399c4387e64432b91/src/hb-ot-var-avar-table.hh#L318-L347


AadHttpClient - not getting token in Edge browser anymore

Category

[ ] Question
[ ] Typo
[x] Bug
[ ] Additional article idea

Expected or Desired Behavior
Expect token to be returned with TokenFactoryiframe when using AadHttpClient in spfx also in the Edge browser. Has worked before but recently stopped working.
Observed Behavior
Works for other browsers like Chrome, Firefox and IE, but not Edge (not even in In Private mode).
Steps to Reproduce
Test a web part using AadHttpClient in Edge and in Chrome, to see the difference.

hey @AndreasNorefalk, we are not aware of any regressions here especially on Edge.
Can you please share the example or tell us the steps to repro the issue?
thanks a lot

Hav tried both using the AadHttpClient with: new AadHttpClient(..) and through the factory with this.context.aadHttpClientFactory. They both have stopped working in Edge.
Getting the token through aadTokenProviderFactory and then using the regular HttpClient however seems to be working fine in Edge.

Thanks @AndreasNorefalk. Can you please share the sample code that doesn't work for you? also, what version of Edge is not working for you?
thanks

hi, I am not sure if this is related so I post this issue over here as we are having issue with edge too. I can see we are able to retrieve the token ( i tested the token by grabbing it and use it in Postman and the token is valid and the call was successful)
What i have found so far:
I identified the issue in this file https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-05-31.011/sp-pages-assembly_en-au_226a2c779e07f656911b8c4964fa1b69.js
return n.headers = new Headers(n.headers || void 0), n.headers.append("Authorization", "Bearer " + o), g.fetchCore(r, new Request(t, n), s._serviceScope, s._fetchProvider, e._className);
i have highlighted the issue in Edge as it would throw invalid argument error
regards

Hi, the following Edge version:
Microsoft Edge 44.17763.1.0
Microsoft EdgeHTML 18.17763
Example:
let apiClient = new AadHttpClient(this.props.context.serviceScope, adalConfig.clientId); apiClient.get(url, AadHttpClient.configurations.v1, {         cache: "no-cache"       }).then(response => {         resolve(response);       }).catch(err => {         reject(err);       });

I am having the same issue. Both in a normal and isolated SPFX webparts. My Edge is a bit older: Microsoft Edge 41.16299.1004.0.
Receiving this error: TypeError: Invalid argument at Anonymous function (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-05-31.012/isolated-web-part-application-assembly_default_fd8d4d8aab6464fb64e6cd4cd176ee17.js:516:42819)

Same issue here. Calling the AadHttpClientFactory:
this.aadClient = await this.context.aadHttpClientFactory.getClient(AppSettings.AppId);
let httpResponse: HttpClientResponse = await this.aadClient
.get(${AppSettings.WebApiUrl}/${groupId}, AadHttpClient.configurations.v1);
Receiving this error: TypeError: Invalid argument
Using Edge: Microsoft Edge 44.17763.1.0 and SPFx 1.8.1

We are now actively looking into this. Thanks for reporting the issue.

Thank you Vesa! My client would really appreciatie this...

I have the same issue
Internet Explorer Edge: 18.17763
SPFx: 1.8.2
with: AadHttpClientFactory
Call azure web api as anonymous and the error is: Invalid argument

hey guys
we have to make sure the header isn't undefined. so this is what you can do
    const requestHeaders: Headers = new Headers();
    requestHeaders.append('Accept', 'application/json');
    const httpClientOptions: IHttpClientOptions = {
      headers: requestHeaders
    };
    return client
      .get(url, AadHttpClient.configurations.v1,httpClientOptions)

obviously you can add whatever header you like/appropriate/applicable to you
this has been tested and working for IE edge
spfx 1.8.1 and Edge version is 44.18362.1.0
regards

You won me the answer.
It works for me:
const requestHeaders: Headers = new Headers();
requestHeaders.append('Content-type', 'application/json');
requestHeaders.append('Cache-Control', 'no-cache');
return client.get('https://...', AadHttpClient.configurations.v1, { cache: "no-cache", headers: requestHeaders })

In IE it worked fine, but now I have to execute the call twice for the changes to be refiled, that's why I got the handling of the cache, if someone knows how to correct it, tell how to do it please

There was a regression in the service that caused this issue. This issue should now be resolved. Please reopen this issue if you're still seeing this behavior.
Thanks!

I can confirm this is working now! Thanks @lahuey and @VesaJuvonen for the quick action on this.


plotly and paraview missing from Numba-only Docker image

Hi Bempp.
I'm using the Numba-only Docker image on a Windows computer.
If I try and reproduce Solving your first problem with Bempp, I don't get the pretty picture (I think because neither plotly nor paraview are included in the Docker image?).
This is not a problem for me at all.  And I appreciate that, the more features included in the Docker image, the larger the Docker image becomes to download and install.  But I thought I'd point it out as it might dishearten beginners.
Yours sincerely,
David Wardle.

I'll take a look at adding the plotting libraries to the docker image. As the image is designed to primarily run Jupyter Lab, I think it makes most sense to include plotly but maybe not paraview.
(I'll also check they're included in the images with OpenCL as I may have missed them there too.)


Aggregator should tolerate having no available replicas

Issue: https://github.com/open-cluster-management/backlog/issues/11303
Changes
When Redisgraph is disabled, the aggregator deployment doesn't have any available replicas.  With this change, this condition won't be interpreted as an error by the ACM install.

Covered in https://github.com/open-cluster-management/search-aggregator/pull/124


Typo in an example

Docs Build status updates of commit 1acf455:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/test/configure-unit-tests-by-using-a-dot-runsettings-file.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@Mikejo5000
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


AUP check ignored when auth succeeds with warning

Using 5.2.0-RC4 in a simple dev environment with minimal configuration.  I have added the both a password policy and the acceptable usage policy check.  When a user authentications who has not completed the check and has a password expiration outside of the warning period, the AUP check is displayed.  If i set the password policy warning days to a large value, say 365 to force the password policy warning to show, the password policy warning shows as required.  However, when the user clicks the continue button, the AUP check should display, it does not, it proceeds directly to the service.

Cool. Thanks for the issue report. It sounds like password policy and AUP flows need a small adjustment in their webflow config to work together. Definitely worth looking into. Please investigate & file a pull request to address the case. Thanks again!


Missing event when toggling between type to filter/find

re  #64727
The outline has a check box that toggled between filter/find. I don't wanna take that away and to keep in sync with the flyover I need to know when the filter/find has changed via that button.

Exposing tree.onDidUpdateOptions, option name to look for is filterOnType.

Verification: please code review.


Is #release() necessary?

Hi,
What happens if I don't release the download manager? If it's necessary what is the best way to keep one download manager across the entire app that I can use from multiple activities and intent services which may finish prior to the download completing.
Thanks,
Daniel

Hi,
I have the same question.
Thanks

After diving to the code, i have a conclusion that release is only needed when you need to cancel all the pending and running requests. If you need to let the download still running in the background, you don't need to call release.
For keeping the download manager to be available to all of your activities, you need to make the download manager declared to the application scope and can be requested from there. Or you can make a singleton of it.
CMIIW

@hendrawd Thanks for stepping in. You got all the points covered. Closing this issue.


fix(payment): PI-345 prevent actions with certificate while processing payment

What?
Remove certificate action button while payment in process
Why?
To prevent changing amount by shopper after submitting payment
Testing / Proof
Unit test and manually tested
https://github.com/bigcommerce/checkout-js/assets/9430298/e6237a4d-b74d-4afc-879a-00f137b0422a
@bigcommerce/team-checkout

Hey @PavlenkoM another note on this PR, instead of hiding the button can we just disable it?

Hi @animesh1987 @bc-peng
As you requested before:

I migrated this component to functional and migrated unit test for this component to react testing library
Also make "remove" action disabled instead of hiding

can you please look?
And also have a question, how can I get color for the button from theme? https://github.com/bigcommerce/checkout-js/pull/1613/files#diff-911fc412c6e9e36a7b387dc31dec0dc4eb19f4927c32fa1b8fbd4db3823dab47R114


server restarted after edit an api's

How to reproduce:
i have api routes called api/test.js
export const GET = (req, res, next) => {
  res.send("GET REQUEST");
};

and i try to edit the handler
export const GET = (req, res, next) => {
  res.send("GET REQUESTTT");
};

and got:
11:04:06 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:06 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:06 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:06 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:06 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:06 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:07 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:07 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:07 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:07 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:07 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:07 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:07 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:07 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:07 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:07 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:08 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:08 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:08 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:08 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:08 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:08 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:08 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:08 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:08 AM [vite] server restarted.
Forced re-optimization of dependencies
Forced re-optimization of dependencies (x2)
11:04:09 AM [vite] server restarted.
Port 5173 is in use, trying another one...
11:04:09 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:09 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:09 AM [vite] server restarted.
Forced re-optimization of dependencies
11:04:09 AM [vite] server restarted.
Forced re-optimization of dependencies

How to fix it?

Hello, could you share a repository with this issue with the node, nmp or yarn versión?, include the package-lock.json please.
I will tried to réplicate this behavior and I can't do it.

I have the same issue, i enabled the debug on HMR with "-d hmr" and saw the additional info on the image. It doesnt do this if I start it with --debug

Hi @tteke , Do you use MACOS? is possible that the MAC create a new hidden files into this directory? because I tested in Windows and Linux in Debug mode and don't have this behavior. Could you check it?

Hey. Yes I am on MACOS. I just checked the .api directory and there isnt any other hidden filed generated in there.


python311Packages.werkzeug: 2.3.7 -> 3.0.1; python311Packages.flask: 2.3.3 -> 3.0.1; python311Packages.quart: 0.18.4 -> 0.19.4

https://werkzeug.palletsprojects.com/en/3.0.x/changes/#version-3-0-0
https://flask.palletsprojects.com/en/3.0.x/changes/#version-3-0-0
https://github.com/pallets/quart/blob/0.19.1/CHANGES.rst
This is a draft, because it is likely premature to upgrade these packages.
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

This seems to break powerdns-admin (@Flakebi @zhaofengli), because flask-admin uses flask-babelex, which is hot garbage.

Changes LGTM. A fix for pgadmin4 is in #284100

This seems to break powerdns-admin (@Flakebi @zhaofengli), because flask-seasurf (unmaintained since 2022), has failing tests, due to api breakage.

Thanks for the heads-up. A fix is in #292178.


[Problem] Find largest prime factor

Develop an algorithm to find largest prime factor of given number.
For example: 15 -> 3 5

Largest prime factor of 15 is 5 here.

Find the largest prime factor of<PHONE_NUMBER>43.

I would like work on this problem.

Waiting for you.
On Mon, Aug 15, 2022, 12:31 AM n3rdy_c0uch @.***> wrote:

I would like work on this problem.
—
Reply to this email directly, view it on GitHub
https://github.com/ademclk/callofcode/issues/14#issuecomment-1214452759,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVTBEJ7HYH5SEYSUVIWUEQDVZFQT7ANCNFSM56QK7DNA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hey, Is this issue Available? Also I would like my name to show in the contributors, My previous PR has been accepted but my name dosen't show up, what to do?

You can solve this problem. Idk why normally it should appear when I merge your solution to main branch. Send a pr again and let's see if it works or not.

Hey, Is this issue Available? Also I would like my name to show in the contributors, My previous PR has been accepted but my name dosen't show up, what to do?

You can solve this problem. Idk why normally it should appear when I merge your solution to main branch. Send a pr again and let's see if it works or not.

Hey, Is this issue Available? Also I would like my name to show in the contributors, My previous PR has been accepted but my name dosen't show up, what to do?

Oh, maybe I made a mistake while changing directories and I deleted your code. If you still have it please pr that again.

I will PR This one


Add utility function to check if tournament is currently running at a certain datetime

The function just checks, whether the provided datetime is within the last 7 days of the datetime.month. Regardless if a tournament is/was actually running.

Will be implemented with v0.5.0


fix: discovery uses V2 when version is None

Passing version=None to discovery.build(), with intent to always
get the latest version of the discovery document,
no longer attempts to use Discovery V1, which fails with
Bad Request errors.
Instead, it uses Discovery V2, which supports null version use case.
Fixes: #971

ping?


hextazy: 0.2 -> 0.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/faelian/hextazy/releases.
meta.description for hextazy is: TUI hexeditor in Rust with colored bytes
meta.homepage for hextazy is: https://github.com/faelian/hextazy
meta.changelog for hextazy is: https://github.com/faelian/hextazy/releases/tags/0.5
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.5 with grep in /nix/store/99fhzv5himbh3h5dz3ac8iqmvmys0hj2-hextazy-0.5
found 0.5 in filename of file in /nix/store/99fhzv5himbh3h5dz3ac8iqmvmys0hj2-hextazy-0.5

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

hextazy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/99fhzv5himbh3h5dz3ac8iqmvmys0hj2-hextazy-0.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A hextazy https://github.com/r-ryantm/nixpkgs/archive/07b0ac787f9abad5e249f12171a323925b416bd2.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/07b0ac787f9abad5e249f12171a323925b416bd2#hextazy

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/99fhzv5himbh3h5dz3ac8iqmvmys0hj2-hextazy-0.5
ls -la /nix/store/99fhzv5himbh3h5dz3ac8iqmvmys0hj2-hextazy-0.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

hextazy

Maintainer pings
cc @AkechiShiro for testing.

On hold for now and may need to be rebased on #327591 as well as updated

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/0xfalafel/hextazy/releases.
meta.description for hextazy is: TUI hexeditor in Rust with colored bytes
meta.homepage for hextazy is: https://github.com/0xfalafel/hextazy
meta.changelog for hextazy is: https://github.com/0xfalafel/hextazy/releases/tags/0.6
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.6 with grep in /nix/store/9l8wsckcwgdran2p95j4pi6738bdlq0f-hextazy-0.6
found 0.6 in filename of file in /nix/store/9l8wsckcwgdran2p95j4pi6738bdlq0f-hextazy-0.6

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

hextazy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9l8wsckcwgdran2p95j4pi6738bdlq0f-hextazy-0.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A hextazy https://github.com/r-ryantm/nixpkgs/archive/cd833e70dc45e5117fa751d77a1a7dbf04b176f2.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/cd833e70dc45e5117fa751d77a1a7dbf04b176f2#hextazy

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9l8wsckcwgdran2p95j4pi6738bdlq0f-hextazy-0.6
ls -la /nix/store/9l8wsckcwgdran2p95j4pi6738bdlq0f-hextazy-0.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

hextazy

Maintainer pings
cc @AkechiShiro for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 329376 run on x86_64-linux 1

1 package built:

hextazy

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4515


New version: viarotel.Escrcpy version 1.20.0

Created by 🥟 Dumplings in workflow run #6349.

Log
Updated: 1.19.4 → 1.20.0
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

/azp run

https://github.com/microsoft/winget-pkgs/issues/142854


Allow for multiple Guesses

https://github.com/sopra-fs23-group-20/server/commit/0afec38f394160c6472711ac7de8ea37e77c937a
https://github.com/sopra-fs23-group-20/client/commit/215da03995eeece9fb05a325114cced455470206


[WIP] Initial BepInExPack mod support (Implements #282)

This is just a carbon copy of our ValheimPlus installer with some BepInExPack specific modifications.
It will currently install BepInExPack and copy plugins from /config/bepinex/plugins/.

Thanks, fixed!

Will this add the ability to modify BepInEx.cfg values with env variables similar to what is currently supported for valheim_plus.cfg values?

@thetaiter not sure. BepInEx uses sections with . in the name which is not an allowed env var character.
E.g.
[Logging.Console]
Enabled = false

Not sure how we would encode Logging.Console. We could of course come up with arbitrary rules like three underscore mean a dot, two underscore mean an underscore or something like that so that we would set BEPINEXCFG_Logging___Console_Enable=false. Not pretty but workable.

@thetaiter the answer is now yes. In https://github.com/lloesche/valheim-server-docker/pull/288/commits/1ec2b5e771b7fea48692a00ecbf9d0c03ddc5920 I reworked the existing config generator and made it more universal. It can now generate/update arbitrary cfg files from env variables. Be it BepInEx.cfg or a plugins custom config file. There's also now a PRE/POST_BEPINEX_CONFIG_HOOK that allows you to call the config generator whenever BepInEx config is being generated or updated.

Amazing, thank you! Great work on this project, very impressive.


Remove incorrect section regarding revocation of SPO availability keys

The SPO BYOK feature does not and never has supported revocation of availability keys. This section should not have been added.

@KCCross Please merge this PR. Thanks

Sending this to the PT.


twitter data sentimental analyser

This file has the python code used to perform the basic sentimental analysis of the tweets by giving the words positive value and negative value and generating a net score that tells the overall tweet positive negative or null.
The file contains all the required data to run the code.

merged properly

I would like to work in this project.Kindly assign me.@tejas-droid


Sylvan/Wildwood chestplate doesn't glow on the chest when enchanted

Minecraft 1.12.2
Forge: <IP_ADDRESS>36
Roots: 3.0.0 (3.0.2)

That ... is really weird. And with your skin I just... wow.

Worth noting is that this is specifically the chest pieces that make up the various parts of the armor rather than any of the other parts that are rendered separately (head, arms, etc)

FYI - the center of the chestplate doesn't even show up now... v 3.0.5

I'm on 3.0.0 and the chest portion of the wildwood chestplate doesn't show up on my character.  When I first put it on, I thought it looked like it flew up off me into the sky.  When looking above me, I saw a small dot.  After doffing then donning it again, it no longer showed up above me in the sky in third person view.  I believe it's a cumulative shift in the coordinate of the armor or something.

@SkyLord-Volmir That was fixed in 3.0.5 I believe.

Is this still occurring @VallenFrostweaver ?

Nope. Fixed.


✨ Support delete own account and other tweaks

✨ Support delete own account and other tweaks

Awesome, thanks @estebanx64 and @alejsdev! :rocket:


Add flter by categoryId option to admin mentor applications endpoint

Purpose

The purpose of this PR is to fix #104
Goals
Add the category filter via a query param categoryId
Approach
Updated the endpoint to support both status and categoryId query params
Screenshots
Checklist

[x] This PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.
[x] I have read and understood the development best practices guidelines ( http://bit.ly/sef-best-practices )
[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
[x] I have made corresponding changes to the documentation

Related PRs

Test environment

Learning

@anjula-sack, I don't have access to update API doc: https://documenter.getpostman.com/view/27421496/2s93m1a4ac#e48b80ba-df2c-4ffc-b399-edb5f2811618

This is no longer required


Differentiate community and corporate accounts

When listing organization accounts for a user, there is no indication to differentiate community projects and corporate projects.
To replicate this issue-

Log in
Click on 'Your organizations'

A list of organizations appear.

Priority - low

Given that our feature set for Community and Corporate accounts has not diverged, and is unlikely to in the long run... I'm not sure this is a priority at this point.


cli/wallet: show tx fee before relaying

Fix #2175 .
Signed-off-by: Evgeniy Stratonikov<EMAIL_ADDRESS>

And TestNEP17Transfer's regexp for network fee should be updated to a human-readable format.


flame does not show up as a "flutter" package

https://pub.dartlang.org/packages/flame
Note it has no Flutter logo shown.  @kevmoo  (I hope this was the right repo to file in.)

@eseidelGoogle: analysis shows an error: Error(s) in lib/util.dart: The class 'ServicesBinding' can't be used as a mixin because it extends a class other than Object. (line:40, col:46). Only packages without errors get platform classification.

@eseidelGoogle – the v2 work includes making these types of issues easy to debug. The bits @isoos are available for authors – just obscured at the moment

FYI @luanpotter

@eseidelGoogle, thanks for noticing and letting me know :)
So, this is weird indeed, because I ran both flutter analyze and flutter packages pub publish --dry-run and neither gave me any errors nor warnings whatsoever. How could I be able to get a log of these obscured errors, as you put it?
As regards the error itself, I don't really understand it, it seems that Dart 1.13 "supports mixins that can extend from classes other than Object" [1]. Now admittedly my min SDK version was 1.8, so I bumped that up, and yet, no logo. It also required the --supermixin flag, and I don't know if that is used or not in this hidden analysis PUB is performing.
Note that what I'm trying to achieve is not without precedent, as it's done by flutter itself:
class WidgetsFlutterBinding extends BindingBase with SchedulerBinding, GestureBinding, ServicesBinding, RendererBinding, WidgetsBinding {
    // ...
}

On line 847 of flutter/lib/src/widgets/binding.dart.
Forgive me for my understanding of Dart's mixins (and the language itself) is rather limited yet.

The simplest way to debug what is happening or missing is to add the following analysis_options.yaml file to your project:
analyzer:
  strong-mode: true

# Source of linter options:
# http://dart-lang.github.io/linter/lints/options/options.html

linter:
  rules:
    - camel_case_types
    - hash_and_equals
    - iterable_contains_unrelated_type
    - list_remove_unrelated_type
    - unrelated_type_equality_checks
    - valid_regexps

and run dartanalyzer . in the project root. It'll list the errors and warnings that we are looking at, and if there is a pending error, please fix it.

@kevmoo Do we need a bug about making those above analyzer options the ones default for pub publish to let authors know of these failures before upload? (or maybe you already have another solution planned).

Please file an issue on the pub client – 'dart-lang/pub' – for that.
pkg/pana is public – so folks can run this analysis now. We'll need to
ponder if it makes sense to integrate pub + pana
On Mon, Nov 13, 2017 at 6:46 AM, Eric Seidel<EMAIL_ADDRESS>wrote:

@kevmoo https://github.com/kevmoo Do we need a bug about making those
above analyzer options the ones default for pub publish to let authors
know of these failures before upload? (or maybe you already have another
solution planned).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/pub-dartlang-dart/issues/562#issuecomment-343940757,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABCivzLnm0djtIsr9p5FlXEAJHpvFhnks5s2FZLgaJpZM4QbDCl
.

Issues in the package analysis may occur not only at package upload time, it may be that a dependency of the package changes in a breaking way, or a new version of the SDK, flutter or pana uncovers or changes something.
A larger package may take a minute or more to get analyzed, and I think it is better to keep it optional. The goal should be to expose the issues and the steps to fix them on the pub site, and everybody can decide when to do it.

@luanpotter fixed the supermixin in the code, but there are other errors with the current repo. I've submitted https://github.com/luanpotter/flame/pull/2 to help fixing the issues. Once they are fixed, a new version should show up as flutter package.


Fix coding style and refactor the test application

https://github.com/Zubax/zubax_style_guide

Partially resolved in master.