Detected that custom integration 'audiconnect' calls async_forward_entry_setup for integration,

I am using Home Assistant v2024.7.0 on the container. With this integration usage, it is showing the following warning.
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:184
First occurred: 09:25:36 (14 occurrences)
Last logged: 09:25:54

Detected that custom integration 'audiconnect' calls async_forward_entry_setup for integration, audiconnect with title<EMAIL_ADDRESS>and entry_id: ccf436e2e4b62b97cb09a8967dd385f3, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/audiconnect/audi_account.py, line 157: self.hass.async_create_task(, please create a bug report at https://github.com/audiconnect/audi_connect_ha/issues
Detected that custom integration 'audiconnect' calls async_forward_entry_setup for integration, audiconnect with title<EMAIL_ADDRESS>and entry_id: ccf436e2e4b62b97cb09a8967dd385f3, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/audiconnect/audi_account.py, line 162: self.hass.async_create_task(, please create a bug report at https://github.com/audiconnect/audi_connect_ha/issues
Detected that custom integration 'audiconnect' calls async_forward_entry_setup for integration, audiconnect with title<EMAIL_ADDRESS>and entry_id: ccf436e2e4b62b97cb09a8967dd385f3, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/audiconnect/audi_account.py, line 167: self.hass.async_create_task(, please create a bug report at https://github.com/audiconnect/audi_connect_ha/issues
Detected that custom integration 'audiconnect' calls async_forward_entry_setup for integration, audiconnect with title<EMAIL_ADDRESS>and entry_id: ccf436e2e4b62b97cb09a8967dd385f3, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/audiconnect/audi_account.py, line 172: self.hass.async_create_task(, please create a bug report at https://github.com/audiconnect/audi_connect_ha/issues
Detected that custom integration 'hacs' accesses hass.helpers.event. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from event directly at custom_components/hacs/base.py, line 630: self.hass.helpers.event.async_track_time_interval(, please create a bug report at https://github.com/hacs/integration/issues

Is it a bug that we should fix?

Thanks for reporting, currently no bug but should be changed for the future.


withComponent

https://emotion.sh/docs/styled#change-the-rendered-tag-using-withcomponent

531dc810ba1f42e1d95322e56d91403f7cc495e2


Allow autodocumenting functions

Quick POC on autodocumenting functions, adding an example/test for each function
Exported to the doc:

This doc will be reworked btw. I plan to remove the full code box for the function and add a menu

Codecov Report

Merging #70 into master will increase coverage by 0.44%.
The diff coverage is 80%.

@@            Coverage Diff             @@
##           master      #70      +/-   ##
==========================================
+ Coverage    56.2%   56.64%   +0.44%
==========================================
  Files          65       65
  Lines        4660     4671      +11
==========================================
+ Hits         2619     2646      +27
+ Misses       1884     1867      -17
- Partials      157      158       +1

Impacted Files
Coverage Δ

template/extra_math.go
35.89% <100%> (+5.72%)
:arrow_up:

template/func_table.go
44.44% <72.72%> (+11.73%)
:arrow_up:

template/math_trig.go
4.05% <0%> (+4.05%)
: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 49a732d...9e7ca63. Read the comment docs.


Initial greeting on client connect contains package name

lalf@ubuntu:~$ telnet localhost 25
Trying ::1...
Trying <IP_ADDRESS>...
Connected to localhost.
Escape character is '^]'.
220 testsrv.com SMTP Guerrilla(1.5.1-90-gf9c4965) #1 (1) 2019-08-04T13:40:52+03:00

Why explicitly show the client that this package is used? Why not pretend Postfix?
Just sooner or later, the smartest system of sending letters will begin to filter domains with such an answer without even transferring any data further.
Maybe it makes sense to change this behavior? For example, make the setting in the configuration file.

Sounds good. PR to make this configurable would be welcome.

Sounds good. PR to make this configurable would be welcome.

Hello,
Thank you for your work.
Is it possible (as for now) to hide or configure this line SMTP Guerrilla?


about the "balanced_softmax_loss" in FedROD

”sample_per_class: A int tensor of size [no of classes]“
Maybe the value of it is the num instead of proportion?

Thank you for your advice! I have revised it in the latest version :-)


feat(tutorial): complete step 3 Hursley

Closes #
{{short description}}
Changelog
New

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

:+1::skin-tone-2: Looks good - I have recorded your completion of this step!


The Sprite Changes

Made new sprites for the three lowest tier of nuclear artillery shell (20t, 500t, and 1kt) and all nuclear rockets. Cleaned up californium sprite a lil bit. Modified prototype definitions as necessary. My discord is God of HyperDeath#6035, if you'd like to go into further discussion about sprite creation.

Before I merge this, would it be alright if you change the 15kt and 100kt artillery shells to match (just if the shade of green is different it looks a bit weird). The new sprites are great though!


Add timeout to notebook execution

Closes #97

Codecov Report

Merging #98 (f387f1e) into main (de78a8d) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #98   +/-   ##
=======================================
  Coverage   95.11%   95.11%
=======================================
  Files          26       26
  Lines        1515     1516    +1
=======================================
+ Hits         1441     1442    +1
  Misses         74       74

Impacted Files
Coverage Δ

pybryt/cli.py
100.00% <100.00%> (ø)

pybryt/execution/__init__.py
100.00% <100.00%> (ø)

pybryt/student.py
96.75% <100.00%> (ø)

Continue to review full report at Codecov.

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


Added french translation

I have translated the strings available in the translations.js file for the french language. Please note that you did not make all the strings available so that we do a complete translation.

Thanks for the PR @douno.  I am going to merge this and perhaps when we finish localization of the application, you could finish the rest of the french translation?

I will be happy to help with more translation. I work for Ehealth Africa and we will be using Hospitalrun for our patient record in Guinea.


Packit SRPM build takes too much time

Several times I've observed that building the SRPM takes quite some time. I tried to do some basic time check on the https://github.com/psss/tmt/pull/55 pull request. Here are the results:
15:20 ... commit pushed
15:21 ... travis started, packit SRPM build has just started...
15:23 ... travis tests completed, packit still building SRPM...
15:33 ... SRPM was built successfully (finally)

So it takes almost quarter of an hour to build the SRPM which is about 1 second on my laptop. Is there anything blocking the build? I think this delay should definitely be improved.

it seems like it's time to scale # of workers of packit-service up

We have now 3 workers so this should be resolved.

Tested today on https://github.com/psss/edd/pull/10. Looks better but still the difference is quite significant:

local make srpm takes 1 second
packit/srpm-build takes 5 minutes

Is there anything else making this simple initial step so slow?

This is why it's slow in the service (and sadly we can't change any of those, short-term):

all the commands are running in a sandbox - the whole repo is being copied to the sandbox, this is usually a network operation which is brutally slow in the cluster
it make take a while to get your job scheduled in packit-service
in the new cluster, we no longer need to copy stuff - we'll be able to use network volumes and share the content like that

Long-term, we are planning on moving packit-service to a cluster with much better performance.

I see, thanks for clarification. When do you plan to migrate to the new cluster?

as soon as possible, which will likely take weeks/months :/ since the new place is not even close to being ready

Lately the response time seems to be better. Already moved to the new cluster?

Already moved to the new cluster?

No, unfortunately not yet. Maybe some small tweaks helped that.

Sadly, we're not migrating any time soon :/ we were promised a new place, but it didn't turn out in the end.
Maybe we could revisit this and try to do some optimizations on p-s' side.

I don't know why. But it behaves much better now. Some optimization is always nice.


[BUG] Can't allocate same line item to multiple shipments

Describe the bug

Attempting to allocate a line item to multiple shipments fails, returning a 500 error code in the console.
Steps to Reproduce
Steps to reproduce the behavior:

Create SO and add line item with quantity > 1.
Create 2 shipments.
Allocate 1 unit to shipment 1.
Allocate non-zero number of units to shipment 2.

Expected behavior

Line item should increase Allocated count and additional list item should be added to left-hand side '+' dropdown menu.
However, nothing happens and the a 500 status error appears in the console.

Deployment Method

[x] Docker
[ ] Bare Metal
[x] Demo Server

Version Information

InvenTree-Version: 0.7.0 dev
Django Version: 3.2.13
Commit Hash: a68db90
Commit Date: 2022-05-12
Database: postgresql
Debug-Mode: False
Deployed using Docker: True

Can you please post the content of the 500 error message? You can access historical error logs via the admin interface
https://inventree.readthedocs.io/en/latest/settings/logs/

Type:
IntegrityError

Path:
http://localhost:8000/api/order/so/5/allocate/

Info:
(1062, "Duplicate entry '8-5' for key 'order_salesorderallocation_line_id_item_id_bb8750cc_uniq'")

When:
May 13, 2022, 11:49 a.m.

Data:
Traceback (most recent call last):

File "/home/inventree/.local/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute
return self.cursor.execute(sql, params)

File "/home/inventree/.local/lib/python3.8/site-packages/django/db/backends/mysql/base.py", line 73, in execute
return self.cursor.execute(query, args)

File "/usr/lib/python3.8/site-packages/MySQLdb/cursors.py", line 206, in execute
res = self._query(query)

File "/usr/lib/python3.8/site-packages/MySQLdb/cursors.py", line 320, in _query
self._do_get_result(db)

File "/usr/lib/python3.8/site-packages/MySQLdb/cursors.py", line 145, in _do_get_result
self._result = result = self._get_result()

File "/usr/lib/python3.8/site-packages/MySQLdb/cursors.py", line 352, in _get_result
return self._get_db().store_result()

MySQLdb._exceptions.IntegrityError: (1062, "Duplicate entry '8-5' for key 'order_salesorderallocation_line_id_item_id_bb8750cc_uniq'")

The above exception was the direct cause of the following exception:

Traceback (most recent call last):

File "/home/inventree/.local/lib/python3.8/site-packages/django/core/handlers/base.py", line 181, in _get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)

File "/home/inventree/.local/lib/python3.8/site-packages/django/views/decorators/csrf.py", line 54, in wrapped_view
return view_func(*args, **kwargs)

File "/home/inventree/.local/lib/python3.8/site-packages/django/views/generic/base.py", line 70, in view
return self.dispatch(request, *args, **kwargs)

File "/home/inventree/.local/lib/python3.8/site-packages/rest_framework/views.py", line 509, in dispatch
response = self.handle_exception(exc)

File "/home/inventree/.local/lib/python3.8/site-packages/rest_framework/views.py", line 469, in handle_exception
self.raise_uncaught_exception(exc)

File "/home/inventree/.local/lib/python3.8/site-packages/rest_framework/views.py", line 480, in raise_uncaught_exception
raise exc

File "/home/inventree/.local/lib/python3.8/site-packages/rest_framework/views.py", line 506, in dispatch
response = handler(request, *args, **kwargs)

File "/home/inventree/.local/lib/python3.8/site-packages/rest_framework/generics.py", line 190, in post
return self.create(request, *args, **kwargs)

File "/home/inventree/.local/lib/python3.8/site-packages/rest_framework/mixins.py", line 19, in create
self.perform_create(serializer)

File "/home/inventree/.local/lib/python3.8/site-packages/rest_framework/mixins.py", line 24, in perform_create
serializer.save()

File "/home/inventree/InvenTree/order/serializers.py", line 1007, in save
order.models.SalesOrderAllocation.objects.create(

File "/home/inventree/.local/lib/python3.8/site-packages/django/db/models/manager.py", line 85, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)

File "/home/inventree/.local/lib/python3.8/site-packages/django/db/models/query.py", line 453, in create
obj.save(force_insert=True, using=self.db)

File "/home/inventree/.local/lib/python3.8/site-packages/django/db/models/base.py", line 739, in save
self.save_base(using=using, force_insert=force_insert,

File "/home/inventree/.local/lib/python3.8/site-packages/django/db/models/base.py", line 776, in save_base
updated = self._save_table(

File "/home/inventree/.local/lib/python3.8/site-packages/django/db/models/base.py", line 881, in _save_table
results = self._do_insert(cls._base_manager, using, fields, returning_fields, raw)

File "/home/inventree/.local/lib/python3.8/site-packages/django/db/models/base.py", line 919, in _do_insert
return manager._insert(

File "/home/inventree/.local/lib/python3.8/site-packages/django/db/models/manager.py", line 85, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)

File "/home/inventree/.local/lib/python3.8/site-packages/django/db/models/query.py", line 1270, in _insert
return query.get_compiler(using=using).execute_sql(returning_fields)

File "/home/inventree/.local/lib/python3.8/site-packages/django/db/models/sql/compiler.py", line 1416, in execute_sql
cursor.execute(sql, params)

File "/home/inventree/.local/lib/python3.8/site-packages/django/db/backends/utils.py", line 98, in execute
return super().execute(sql, params)

File "/home/inventree/.local/lib/python3.8/site-packages/django/db/backends/utils.py", line 66, in execute
return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)

File "/home/inventree/.local/lib/python3.8/site-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers
return executor(sql, params, many, context)

File "/home/inventree/.local/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute
return self.cursor.execute(sql, params)

File "/home/inventree/.local/lib/python3.8/site-packages/django/db/utils.py", line 90, in __exit__
raise dj_exc_value.with_traceback(traceback) from exc_value

File "/home/inventree/.local/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute
return self.cursor.execute(sql, params)

File "/home/inventree/.local/lib/python3.8/site-packages/django/db/backends/mysql/base.py", line 73, in execute
return self.cursor.execute(query, args)

File "/usr/lib/python3.8/site-packages/MySQLdb/cursors.py", line 206, in execute
res = self._query(query)

File "/usr/lib/python3.8/site-packages/MySQLdb/cursors.py", line 320, in _query
self._do_get_result(db)

File "/usr/lib/python3.8/site-packages/MySQLdb/cursors.py", line 145, in _do_get_result
self._result = result = self._get_result()

File "/usr/lib/python3.8/site-packages/MySQLdb/cursors.py", line 352, in _get_result
return self._get_db().store_result()

django.db.utils.IntegrityError: (1062, "Duplicate entry '8-5' for key 'order_salesorderallocation_line_id_item_id_bb8750cc_uniq'")

Cheers, will look into this one.

@maksimstojkovic this has now been fixed in master :)


Pyautogui miss Y Coordinate

Hi,
I have a Python script which consists of 5 functions. If I run functions separately everything works smoothly. But if I run it in one main.py file a few of those mouse clicks miss Y  coordinate in the middle of the process. I am hopeless to find why it does miss it. X is always correct but Y coordinate is a bit too up and hence it miss an "OK" button
Did anyone ever experience this?

Bring in a concrete example...

I will do so. Thank you. I am new to this python and github thing :)


[feat] - add new instance types for dev spot node, updated NVME creation script to include more types

Will apply this on Monday, now I wanna chill.

This one was already applied to mainnet by @dumikau and @lazavikmaria


Revise incompatibility warning FAQs

I implemented the ideas from #1288 and split up the incompatibility_warning article into part_incompat and full_incompat.
To avoid duplicate fixes in response to your feedback, I am only providing an English version until all your concerns with this version are addressed.

I added a redirect from incompatibility_warning to part_incompat.

I have a few general remarks for improvement
The error message ("incompatibility warning") should be part of the entry heading. This way, search engines will hopefully lead  users directly to the FAQ entry if they search for the warning online.

Using a more active language and shorter sentences is encouraged
Example:

Since version 2.2, the Corona-Warn-App for Android contains a check which determines whether your device is fully capable of all Bluetooth-related features which the app needs to operate normally.

can be improved to

Since version 2.2, the Corona-Warn-App checks if your device supports all Bluetooth-related features normally used by the app.

If possible, we should get straight to the point
Example:

If you are seeing this message, the operating system of your device is lacking a functionality that Corona-Warn-App normally uses.

we can merge that sentence with the next paragraph

If you are seeing this message, the operating system of your device lacks the ability to send random IDs [to devices in your proximity]. [...]

The reason is that we want to get to the ">your own risk assesment is not affected" part quickly.

"Schachtelsatz" construction should be avoided, especially in english, but it's also a good idea for the german entry.

The only limitation which this incompatibility causes is that, in case you are infected and you decide to warn others, only users who were checked in to the same event or the same location, at the same time as you were, can be warned.

The way we could split this is by separating the information communicated here into separate sentences:

What is the limitation/What is limited? (warning people who were near you)
What does still work? (warning through Check-In functionality)

The revised text looks good to me, thanks.
In one section, the text reads "To resolve the problem, please ensure that you are using the latest version of your smartphone's operating system. If this doesn't help, please contact your device manufacturer."
Do you think it would help to add two sentences here like
"(Reverting to an older version of CWA does not help, because the technical incompatibility existed in previous versions, too. Just it was not visible to the user.)"    ?
This is meant for users like in #1288

Seit dem letzten Update v. 10.05. ist mein Bluetooth Chip plötzlich inkompatibel. Das kann ja wohl nicht sein. Mit der Vorgängerversion wieder alles okay. Geht das bei der Corona App jetzt genauso wie bei den meisten Banking Apps? Jedes Update eine Verschlimmbesserung?

But I’m uncertain if this suggestion would be too much.

@Lu9Bro Since there is no official downgrade procedure in both Google Play as well as in the stock Android system, I think the information that the check was added in 2.2 is sufficient. However some users might try this anyway… what do the others think?

I have added a German translation now.

@fynngodau I would take over now and make remaining in preparation for the next release. So if you still have local changes to push, the best time to do that is now :)

So if you still have local changes to push, the best time to do that is now :)

This PR is all I have at the moment ;)

I made quite a few changes to the existing text:

More precise definition of the problem
Merge the last paragraph (before the technical explanation) into the second paragraph
Align text and wording between the two FAQ entries
Remove first paragraph of full_incompat because it could be confusing
Add technica explanation to full_incompat

I don't know what's the plan under Android but iOS version 2.3 has been released today.


TeamPage.html issue #2

None of the links in the navbar are working also the social media accounts are not added (they are not working as well).

I can work on this issue. Please assign it to me.

please assign this issue to me. @SahityaRoy

Please wait we will change the style first then we will work on this

social media were added by me yesterday


Added a utility to run standalone.

Thanks for the PR, but a built-in command line tool is outside of the scope of this library.
I create the JJ for that purpose.


How to write and read at the same time

Could it implement real streaming like one side is writing, and another side is reading?
Example code (async by amphp):
$stream = Stream::create();

async(function() use ($stream) {
    while ($stream->isReadable()) {
        echo "--read--\n";
        echo $stream->read(512)."\n";
        delay(0.1);
    }
});

for ($i=0; $i<100; $i++) {
    $content = str_repeat((string)$i, 10);
    echo "--write--\n";
    $stream->write($content);
    delay(0.1);
}

$stream->close();

Synchronize code:
$stream = Stream::create();

for ($i=0; $i<100; $i++) {
    $content = str_repeat((string)$i, 10);
    $stream->write($content);
    echo $stream->read(512)."\n";

}

$stream->close();

Can not read anything... The problem is when call write, the cursor of stream is also moved, so read can not read anything..
Currently, must be completely written, then rewind before starting to read, it's not stream.
How do I achieve true streaming while writing and reading at the same time? Imagine download a file from http request, http server is writing, and client is reading, all in streaming.

As far as I know the (PHP) stream implementation is not designed for concurrent read/write operations because they share a single cursor. You may try a different approach with a producer-consumer pattern.


Dynamic index update

Hi!
Do I understand correctly that LOPQ does not currently support dynamic index update / adding new data to an existing dataset?

Hi @ashfaq92,
You're right.
And, to be clear, dynamic update is far out of the scope of search algorithm in general and LOPQ particularly.
In point of view of System Design, dynamic update should be basically a functionality of your Service using LOPQ as backbone search engine. It is very likely that you may replace LOPQ with something different but keep update subsystem unmodified.

Thank you for the prompt reply.
Actually my problem includes performing 'n' number of nearest neighbor batch queries for 'n' randomly generated vectors to a dataset and inserting one (based on some criteria) of these randomly generated to the existing dataset.
In this way, data-set will be incrementally increased each time after the batch queries are performed
can you please suggest any help in this case?

@ashfaq92, I believe LOPQSearcher.add_data or LOPQSearcher.add_codes would help you.


Testing

What testing system should we use for terra-stdlib? Busted is a nice and well developed framework for using with Lua, and is applicable to Terra-stdlib testing requirements, though it would be slightly more difficult to use since it couldn't directly interact with terra variables in the middle of terra functions. I'm also looking at the possibility of writing a new testing system designed like a cross of Spock and Busted to be able to interact with both Terra and Lua directly, and anything that Terra can abstract across through the C-ABI with ease. That is a bit further off though.
Should I just start writing tests in Busted for now and work on other things? or prioritize getting a testing platform with native support for Terra before proceding to other implementations?

I don't have a strong preference. Busted looks ok. The main limitation (of any Lua framework, not just Busted) is that you can't assert inside a Terra function, right? So you have to break up your tests and pass results back out of Terra whenever you want to check them. (Or I guess wrap the asserts in a cast so you can call from Terra.) I agree it's not pretty, but it doesn't seem that terrible either. I'd be inclined to move forward with something rather that works rather than rebuild the test suite from scratch.
I am slightly concerned about installation. How many dependencies does Busted have? Do we have luarocks integration or is that something we can do easily?
I'm happy to get other opinions on this too.

I'd much rather live in the lit or nix ecosystems than the luarocks ecosystem. The ability to make local and self-contained package dependencies is important and a massive headache-remover. But there isn't as well developed of a testing framework in lit as busted.
Yes, the main drawback of using a lua testing framework is not having knowledge of Terra things. Being able to assert inside a terra function such that it gets the types from the callsite to be polymorphic, the ability to break down the expression into components and display an annotated readout of exactly what failed, etc. I'd also like for it to integrate with my TerraWatch tool to be able to automatically rerun only the tests affected by a given source change based on what parts of the stdlib they import.
Using busted as the testing framework wouldn't create a dependency on the luarocks ecosystem at runtime. It would only be needed to run the tests during development, which is less bad. There is no need for luarocks integration in terra, developers and CI machines would just need to have luarocks to fetch busted and dependencies. No part of terra or the terra-stdlib code would need to know about busted, only the tests being written in busted formats.
Busted only has a small handful of dependencies.
It appears that someone has already added support for loading Terra files in busted so it should nominally just work to point the busted test root at a directory full of terra files. (in practice, it is appearing to require some nonzero effort.)

The existing terra support in busted was four years out of date and no longer functioning. I made a PR to update it. I have busted with Terra working on my machine now, but my setup is fragile. On more conventional systems, it should be easier.

Are there instructions for setting up Busted with Terra? It's probably worth adding to our CI as an external application so we don't break it in the future.

There are not yet. It's pretty simple. Busted provides a script that just runs the line require 'busted.runner'({ standalone = false }) in a lua/luajit interpreter with the luarocks loaders available. To make it work in Terra, all that needs to be done is make a script that runs that line in Terra with the luajit version of the luarocks libraries available.

I would recommend using CircleCI + Dockerfile for testing. Make a .circleci folder with config.yml and Dockerfile and the config becomes quite simplified. What's more is that tests are reproducible locally by running docker build -f .circleci/Dockerfile ..

But just shoving the testing into a Dockerfile to make configuration easily reproducible does seem like a good way to accomplish it. It shouldn't be the only way though because we do need to run the tests on many different systems because Terra actually touches some of the architectural details that nodejs is designed to hide. Especially the stdlib which is specifically for providing a consistent and uniform interface on multiple platforms. Maybe it just needs more dockerfiles.

I agree with @Qix- that this is what we should be doing, but this should really be split into a separate issue on the Terra repo.


[tests-only][full-ci] Forwardport test for send wrong host for adding user in group

Description
This PR forward ports PR https://github.com/owncloud/ocis/pull/5875
Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[x] Tests only (no source changes)

Checklist:

[ ] Code changes
[ ] Unit tests added
[x] Acceptance tests added
[ ] Documentation ticket raised:

E2E tests failed: https://drone.owncloud.com/owncloud/ocis/20850/87/1
:boom: To see the trace, please open the link in the console ...

npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/20850/tracing/unstructured-collection-of-testable-space-interactions-alice-2023-3-27-06-45-02.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/20850/tracing/user-login-can-be-managed-in-the-admin-settings-admin-2023-3-27-06-31-56.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/20850/tracing/user-login-can-be-managed-in-the-admin-settings-admin-2023-3-27-06-32-02.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/20850/tracing/user-login-can-be-managed-in-the-admin-settings-alice-2023-3-27-06-32-01.zip


Hello, I would like to konw how to try it out

After I put the entire download package in the website directory and unzipped it, I visited the index. php,
as shown below
A PHP Error was encountered
Severity: Warning

Message: mysqli::real_connect(): (HY000/1045): Access denied for user 'root'@'localhost' (using password: NO)

Filename: mysqli/mysqli_driver.php

Line Number: 203

Backtrace:

File: /www/wwwroot/<IP_ADDRESS>/application/controllers/Home.php
Line: 8
Function: __construct

File: /www/wwwroot/<IP_ADDRESS>/index.php
Line: 315
Function: require_once

A Database Error Occurred
Unable to connect to your database server using the provided settings.

Filename: controllers/Home.php

Line Number: 8

I think you must set database.php in config folder. That error mean your
database configuration in project must same with your database like
phpmyadmin or adminer
Pada tanggal Rab, 14 Jul 2021 pukul 17.08 mlost7 @.***>
menulis:

After I put the entire download package in the website directory and
unzipped it, I visited the index. php,
as shown below
A PHP Error was encountered
Severity: Warning
Message: mysqli::real_connect(): (HY000/1045): Access denied for user 'root'@'localhost' (using password: NO)
Filename: mysqli/mysqli_driver.php
Line Number: 203
Backtrace:
File: /www/wwwroot/<IP_ADDRESS>/application/controllers/Home.php
Line: 8
Function: __construct
File: /www/wwwroot/<IP_ADDRESS>/index.php
Line: 315
Function: require_once
A Database Error Occurred
Unable to connect to your database server using the provided settings.
Filename: controllers/Home.php
Line Number: 8
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tegarpratama/school-website/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AITY4FIS6LXLCV7RGZBRXUDTXVOY3ANCNFSM5ALEGIDA
.


add toInputStream to ByteString

See https://github.com/apache/incubator-pekko-http/blob/da6a228372efac2da05aae68c3acb982f7a7e58d/http-core/src/main/scala/org/apache/pekko/http/impl/engine/http2/hpack/ByteStringInputStream.scala#L30
wdyt @mdedetrich

Zio has toInputStream on ZStream.

One problem with adding toInputStream is that we won't be able to use it in pekko-http because we'll want pekko-http to still be able to use pekko-core 1.0.x - and presuambly, we wouldn't backport this to 1.0.x
Looking a pekko-http, I think we could improve performance by calling ByteString.toArrayUnsafe instead of toArray. Pekko-http only uses the byte[] to create a ByteArrayInputStream and this won't mutate the byte[] (but it doesn't clone it either).
That change would save us from cloning the array like ByteString.toArray does. See the hpack code link in the issue description.

We can source in that code in that code in pekko http, and when we bump the required pekko version, we change the package and recompile.

One problem with adding toInputStream is that we won't be able to use it in pekko-http because we'll want pekko-http to still be able to use pekko-core 1.0.x - and presuambly, we wouldn't backport this to 1.0.x
Looking a pekko-http, I think we could improve performance by calling ByteString.toArrayUnsafe instead of toArray. Pekko-http only uses the byte[] to create a ByteArrayInputStream and this won't mutate the byte[] (but it doesn't clone it either).
That change would save us from cloning the array like ByteString.toArray does. See the hpack code link in the issue description.
So what I think I'm saying is do this ByteString change but also do a separate pekko-http change that doesn't use this change yet.

There are many ways we can save this problem

Force Pekko-Http to use Pekko 1.0.x (thats what the minVersion is meant to specify)
Use reflection to detect if the method doesn't exist, and if it doesn't then pekko-http can use its own inner sourced variant

I would say even backporting this to Pekko 1.0.x wouldn't entirely solve the issue and hence gives a false sense of semver considering that it wouldn't work for the earlier versions of Pekko 1.0.x

#1085 merged


Add --create_externs_from_exports flag

Adds the --create_externs_from_exports flag, which allows the creation of externs from exported methods.
Also fixes a minor bug in AbstractCommandLineRunner that prevented the use of that flag with relative paths containing no separators.
Finally, changes the way generated externs are sorted so that they respect dependency order.  Alphabetical sorting is still used, but only within a script.  This is important for the generated externs of a large project to be used directly without editing.
Issue #1399

Added a couple more commits to fix the order of the generated externs.  PTAL.

Thanks Joey. Let's review this internally :)


lc0-compatibility

According to lc0, it should be UCI-compatible. However, PGN-spy fails when used with lc0:

Fails immediately:

I realize PGN-spy only works with select UCI-compatible engines - however, this would be great.

Yeah, I'm interacting with the engine in a somewhat non-standard way, and it's a little brittle.  I want to rewrite the engine interaction code from scratch, but haven't gotten around to it.


[RFC] Add compose

Would this be a good fit for relude?
compose :: [a -> a] -> a -> a
compose = foldr (.) id

Example

This is probably not needed when there is State monad. Ref


Feature Request: Add --create argument to az pipelines variable-group variable update

If the issue is to do with Azure CLI 2.0 in-particular, create an issue here at Azure/azure-cli

Extension name (the extension in question)
azure-devops
az pipelines variable-group variable update
Description of issue (in as much detail as possible)
Add a flag --create to the command az pipelines variable-group variable update
az pipelines variable-group variable update --group-id
--name
[--detect {false, true}]
[--new-name]
[--org]
[--project]
[--prompt-value {false, true}]
[--secret {false, true}]
[--value]
[--create]
--create-c
If the variable does not exist, it can be created - otherwise just perform the update; similar to the functionality in helm.

devops

Would running create and then update suffice in this use case? Create fails if there is existing entity with the same name. In this case when update runs, the actual update happens. You could even use conditional side on your end to orchestrate between create and update.
The clear delineation of create/update intent lets us ensure predictability for the commands.


Added the grid package

Introducing the material design grid 🚀
This grid is made of 12 columns to make possible complex designs but even responsive ones.
The grid is a fundamental tool in the design and can be used everywhere.
Basically, everything you have to do is put a "Col" component which is responsive and can be set to any width inside the "Grid"
// TODOS: 📝

[x] Pull feature

[x] Push feature

[x] Extra large feature

LGTM👍🏻


[GitLab] My Reviews fails or hangs

Extension
https://www.raycast.com/tonka3000/gitlab
Description
After a clean installation of the extension, I try running My Reviews and get either Cannot search Reviews: FetchError: request to https://gitlab.com/api/v4/user?per_page=50&page=1 failed, reason: socket hang up or a hanging window. In the case of the former, I am capable of successfully issuing the query and get the results as expected.
https://user-images.githubusercontent.com/8957630/220628717-edc0d402-e0eb-48c4-a8ce-c1f999770ae3.mov
Steps To Reproduce
Execute the My Reviews action
Current Behaviour
Received either Cannot search Reviews: FetchError: request to https://gitlab.com/api/v4/user?per_page=50&page=1 failed, reason: socket hang up or a hanging window.
Expected Behaviour
MRs that I'm assigned as a reviewer are retrieved.

My gitlab url is https://gitlab.com. My token scope is api and read_api. I've tried all possible combinations between the two.

@pernielsentikaer raycast issue?

Hi @z4f1r0v 👋
Are you still experiencing this issue?

Not anymore. Closing.


Problem with character encoding on some russian torrent trackers?

I use some Russian torrent trackers (https://kinozal.tv), and they have a problem with character encoding. Can you tell me what to do?

Hi, this issue will be fixed in next update.


Use gossip protocol for real service discovery

Hello,
I feel a simplification in the design of etcd would be if it didnt require a discovery node... just like a real/fully distributed system and would move over to a design like consul. Etcd has a nice http interface, and is already established in coreos.. I get that.. but I feel consul has a superior design. Perhaps, use the serf project right in etcd? ..

@pkieltyka Almost 3 years :+1:

I just feel the service discovery should be gossip based


Update traslate file spanish to es_v0.1.json

Testing file translate
Changes / Comments
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[ ] Does the pull request title have the sheet name(s)? Include each sheet name.
[ ] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Testing update spanish template. If all is Ok, I´ll finish the complete translation


[Python] pyarrow.compute.utf8_center disagrees with str.center when number of needed padding characters is odd

Describe the bug, including details regarding any error messages, version, and platform.
In [1]: import pyarrow as pa; import pyarrow.compute as pc

In [2]: pa.__version__
Out[2]: '10.0.1'

In [3]: s = "bb"

In [4]: s.center(5, "X")
Out[4]: 'XXbbX'

In [5]: pc.utf8_center(pa.scalar(s), 5, padding="X")
Out[5]: <pyarrow.StringScalar: 'XbbXX'>

I suppose in theory it's arbitrary where the two XX are added (front or back) to center the string, but I would expect to match the standard library behavior for consistency
Component(s)
Python

So this diff makes things consistent with Python stdlib, but the comment notes that this might be intentional?
diff --git a/cpp/src/arrow/compute/kernels/scalar_string_utf8.cc b/cpp/src/arrow/compute/kernels/scalar_string_utf8.cc
index fb197e13a..6c4d88ba7 100644
--- a/cpp/src/arrow/compute/kernels/scalar_string_utf8.cc
+++ b/cpp/src/arrow/compute/kernels/scalar_string_utf8.cc
@@ -930,7 +930,7 @@ struct Utf8PadTransform : public StringTransformBase {
     int64_t right = 0;
     if (PadLeft && PadRight) {
       // If odd number of spaces, put the extra space on the right
-      left = spaces / 2;
+      left = (spaces / 2) + 1;
       right = spaces - left;
     } else if (PadLeft) {
       left = spaces;

Issue resolved by pull request 41449
https://github.com/apache/arrow/pull/41449

I think this might still not match the cpython behavior.  Based on the OP and https://github.com/pandas-dev/pandas/pull/59624 (the pandas test test_center_ljust_rjust_fillchar)
In [19]: a1 = "a"

In [20]: a1.center(5, "X")
Out[20]: 'XXaXX'

In [21]: pc.utf8_center(pa.scalar(a1), 5, padding="X", lean_left_on_odd_padding=True)
Out[21]: <pyarrow.StringScalar: 'XXaXX'>

So far so good.  But when the input string has an even number of characters:
In [22]: b4 = "bbbb"

In [23]: b4.center(5, "X")
Out[23]: 'Xbbbb'

In [24]: pc.utf8_center(pa.scalar(b4), 5, padding="X", lean_left_on_odd_padding=True)
Out[24]: <pyarrow.StringScalar: 'bbbbX'>

IIUC with lean_left_on_odd_padding=True the number of spaces to put on right/left is determined here as
left = spaces / 2;
right = spaces - left;

By contrast in cpython it is determined here as
marg = width - STRINGLIB_LEN(self)
left = marg / 2 + (marg & width & 1);

With another dose of "IIUC", it looks like the marg &width & 1 term is missing from the pyarrow version.

The default for the argument (keeping existing behaviour) is True, so by setting it to False I get:
In [42]: pc.utf8_center(pa.scalar(b4), 5, padding="X", lean_left_on_odd_padding=False)
Out[42]: <pyarrow.StringScalar: 'Xbbbb'>

It's certainly not a very clear argument name .. (it's the original data that "leans left", and not the new padding characters), but when setting it to False, do the pandas tests then pass?

(Updated my previous comment, for which the a1 example should have been using 4 spaces instead of 5.)
Using lean_left_on_odd_padding=False fixes the b4 case, but breaks the a1 case, (see https://github.com/pandas-dev/pandas/pull/59624#issuecomment-2313330376).

Hmm, ok so it seems, based on the single example above, we missed how Python actually works .. It doesn't just align on the right side (e.g 'XXbbX'), but so apparently they align on the left or right depending on whether the total width is odd or even .. (maybe a bit similar like round-to-even logic?)
One lucky part might be that this addition in pyarrow might not completely miss the point, because I think we can mimic that behaviour in pandas exactly (if we want), by doing something like:
if width % 2 == 0:
    # width is even
    lean_left = True
else:
    lean_left = False

pc.utf8_center(arr, width, padding=fillchar, lean_left_on_odd_padding=lean_left)


Add support for ProcessList

Signed-off-by: John Howard<EMAIL_ADDRESS>Similar to statistics.

@darrenstahlmsft

LGTM


museum: photos-v0.9.30 -> photos-v0.9.35

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ente-io/ente/releases.
meta.description for museum is: API server for ente.io
meta.homepage for museum is: https://github.com/ente-io/ente/tree/main/server
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found photos-v0.9.35 in filename of file in /nix/store/qsvk3bbqbp1d97w6914rlqzqfl33pawm-museum-photos-v0.9.35

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

museum

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qsvk3bbqbp1d97w6914rlqzqfl33pawm-museum-photos-v0.9.35 \
  --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 museum https://github.com/r-ryantm/nixpkgs/archive/d71269b6e9587f909a6476ea040ed3b06add203b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/d71269b6e9587f909a6476ea040ed3b06add203b#museum

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qsvk3bbqbp1d97w6914rlqzqfl33pawm-museum-photos-v0.9.35
ls -la /nix/store/qsvk3bbqbp1d97w6914rlqzqfl33pawm-museum-photos-v0.9.35/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:

museum

Maintainer pings
cc @surfaceflinger @pinpox 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 340195 run on x86_64-linux 1

1 package built:

museum


Intersection types with arrays and array methods cannot find all fields

Bug Report
Intersection of arrays cannot find all fields when using array methods, while the fields are working fine if a single element is directly accessed from the array.
🔎 Search Terms
type, intersection, array methods
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about intersection

⏯ Playground Link
Playground link with relevant code
💻 Code
var obj: {
  foo?: string;
}[] & {
  bar?: boolean;
}[] = [{foo: "a", bar: true}];

obj.forEach((q) => q.bar); // bar does not exist
obj.map((q) => q.bar) // bar does not exist
obj[0].bar; // OK

🙁 Actual behavior
When using array methods (forEach, map, filter etc) only the first type is recognized in unions - field from the second type are not recognized.
🙂 Expected behavior
All fields are considered valid in an intersection of arrays.

I kept investigating and I found #11961 from 2016. I assume it is still valid, right?

Correct


useProxy not working

Hi.
I add proxy, but its not working
plugin.useProxy('http://xxxxx:6000', {changeGeolocation : true}).useFingerprint(fingerprint);
My proxy is incomming ipv4 and outgoing ipv6

Good day, it seems that the problem may be on the puppeteer side, because it adds an enable-feautres argument, which can break things. Please try using ignoreDefaultArgs launch option like this:
await plugin.launch({
  ignoreDefaultArgs: ['--enable-features=NetworkServiceInProcess2'],
});

If it helps, I will prepare a fix. If not, please describe your problem in more detail.

hi @CheshireCaat,
Thank for your reply.
I tried
await plugin.launch({   ignoreDefaultArgs: ['--enable-features=NetworkServiceInProcess2'], });
But, its working with ipv4 only, I used ipv4 on incomming connection and outgoing is ipv6 then got error.
Error: net::ERR_CONNECTION_CLOSED at https://google.com/     at navigate (C:\workspace\fingerprint-switcher\node_modules\puppeteer-core\lib\cjs\puppeteer\common\Frame.js:240:23)     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)     at async Frame.goto (C:\workspace\fingerprint-switcher\node_modules\puppeteer-core\lib\cjs\puppeteer\common\Frame.js:206:21)      at async CDPPage.goto (C:\workspace\fingerprint-switcher\node_modules\puppeteer-core\lib\cjs\puppeteer\common\Page.js:439:16)     at async C:\workspace\fingerprint-switcher\main.js:26:5
This is my code
`    const fingerprint = await plugin.fetch('xxxxxx', {
tags: ['Microsoft Windows', 'Chrome'],
dynamicPerfectCanvas : false,
timeLimit: '15 days',
minBrowserVersion : 96
});
// 25A4D1D5
// Apply fingerprint:
plugin.useFingerprint(fingerprint);
plugin.useProxy('http://ipv4:6000', {changeGeolocation : true}).useFingerprint(fingerprint);
//
// console.log(fingerprint)
// Launch the browser instance:
const browser = await plugin.launch({headless : false, ignoreDefaultArgs: ['--enable-features=NetworkServiceInProcess2']});

// The rest of the code is the same as for a standard `puppeteer` library:
const page = await browser.newPage();
await page.goto('https://google.com/');`

When I use ipv4 proxy, I check on iphey.com and can not bypass location error
Can you help me how to bypass this

@minhdv92, where is proxy?

@bablosoft
proxy here
plugin.useProxy('http://ipv4:6000', {changeGeolocation : true}).useFingerprint(fingerprint);
you can try this proxy <IP_ADDRESS>:20000

@minhdv92, I don't see any issue, except NetworkServiceInProcess2
https://i.imgur.com/G1dxl22.png
If you report about issue, please attach full code, including proxy, excluding FingerprintSwitcher keys, also actual result and expected result, video and screenshots would be nice also.

hi @CheshireCaat  @bablosoft
I tried version 1.1.2 but still got the error

@minhdv92
DON'T attach FingerprintSwitcher keys. Next time it will be banned without refund.
Your code runs successful on my side. What are results of testing with puppeteer, BAS? Does the page will load if catch error?
Why do you think that the issue is not with proxy?
Please also attach wireshark log.

@bablosoft
Sorry for this, I edited.
This is test results of puppteteer,
When I run the code, its open chrome and loading page, then crash by "connection closed"

This is test results of puppteteer,

This is tests results for puppteteer-with-fingerprints.
Your code runs successful on my side. What are results of testing with puppeteer, BAS? Does the page will load if catch error?
Why do you think that the issue is not with proxy?
Please also attach wireshark log.

I tried with puppeteer and its working

But now, I can not create new fingerprint to test again

Ok, we are working on ipv6 proxies problem, meanwhile you can you BAS.

thank @bablosoft
I'm waiting your update

Fixed


Remove extra call to iTunesConnect web objects that invalidates myacinfo cookie

For dev portal accounts that don't have iTunesConnect accounts associated with them, this call was invalidating the myacinfo cookie that is required to make authenticated calls. This call doesn't appear neccessary as it doesn't provide any additional cookies as compared with line 286.
This PR allows accounts that only have dev portal access to use tools like sigh, cert and produce
Fixes #3901
Fixes #5386
Fixes #5384

Thanks @asfalcone for preparing this change. I could reproduce the issue on an Enterprise account before this change, and this PR fixes the login issue 👍
Also non-Enterprise accounts work with no problem before and after this change, so this is ready to be merged and pushed live 🚀


mobile: Use TestEnvironment::runfilesPath for the cert paths

This PR updates the cert paths to use TestEnvironment::runfilesPath so that we can use data attribute without relying on the actual directory structure between Envoy Core and Envoy Mobile. This PR will make the code more portable and this is also best practice that Bazel recommends.
Risk Level: low (only affects tests)
Testing: n/a
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features: n/a

/retest


Bring up to prosemirror-transform 1.7.0

Add support for the AttrStep. See https://github.com/ProseMirror/prosemirror-transform/commit/9ee7c0806f38180bae0e60d7d84af4fd9ee44f26

Very happy they added that, will try to port it here soon!


STORM-1466: Move the org.apache.thrift7 namespace to something correct/sensible

+1

I'm also going to cherry-pick this back into the 1.0 branch.

+1 NB


Issue/3034 compiler determinism

Description
Removes a source of nondeterminism from the compiler: construction of an Instance instance used a set to prune duplicates from a sequence. Iteration over this set was then indirectly used to drive control flow (a method was called that as a side effect appended to the execution queues). This PR performs the pruning in a deterministic way and adds a test case for a model that was affected by this.
closes #3034
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[x] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request

Processing #3924.

Processing #3923.

Processing #3924.


Autocomplete possible key names

Simular to how command completion works, it would suggest possible names when adding new nbt entries and let you cycle through them. It would elluminate the need for obscure item factories since you'd be able to add any data to any item without precisely knowing the keys' names as long as vanilla or any mod has them registered.

I have gotten this suggested before, and I have started looking into it! I'm unclear how easy it is going to be to get a list of all the usable keys, so this may take longer than expected. It would be a very useful feature.

yeah, and they'd need to only be suggested in directories where they belong and would take effect. This feature would be worthy of a 2.0 release.

I've finally released this in v1.13.0! It requires NBT Autocomplete to be installed at the same time. In addition to suggesting tag names in the "+" prompt, it also suggests stuff in the value editor and expand editor.


Edit download link

Currently, it suggests finding th zip file link in the dashboard. However, since the GitHub redesign, this link isnt there anymore - it is in a dropdown at the top. I have just linked to the file and suggested using git for those who can. I think this is a bit easier.

Looks good @RichardLitt, thanks for catching that and making this suggestion! 👍


Caution: This kata does not currently have any known supported versions for Python.

I've come across a few katas in the last couple of days that have this message above the description beside the editor when after clicking 'Train'. I am referring to the Python versions of the katas. I even tried opening a different browser (Firefox instead of Chrome) and logging in but the message is the same. I briefly searched the issues and couldn't find this mentioned before.

Caution: This kata does not currently have any known supported versions for Python.

On these examples, I (and others) have submitted solutions and they have passed the test cases. I just found it odd that there is a message about no "known supported versions for Python" although the kata seems to function normally with at least one version of Python. I mentioned this to @GiacomoSorbi to see if he knew about this and he suggested I open an issue. So here it is (hopefully this is the right place!).
Here are a few examples of katas where I am getting that same message. They seem to be fairly new katas (some still beta). If I find more I will update this list (if necessary).

http://www.codewars.com/kata/the-barksdale-code/python
http://www.codewars.com/kata/assignment-number-3/python
http://www.codewars.com/kata/assignment-number-2/python
http://www.codewars.com/kata/competitive-eating-scoreboard/python
http://www.codewars.com/kata/what-is-between/python

If anything this seems like a very minor issue as these katas seem to be functioning fine. Just wanted to let you guys know.

I'm seeing this as well, in my first attempt at Kata authoring.  Occurs whether I choose 2.7 or 3.4.


SCM Guide: Enhance introductory content

Made the following changes:

A few edits to the intro section
Added an audience section
Moved organizational management section to operations
Added GitLab items to the organization section
Added an intro and operation sections to the GitHub and GitLab READMEs
Small typo fixes

Other open questions:

The existing Intro talks about integrating security tools but I don't see anything on it in the docs.
GitLab has SSO, not sure why this wasn't added? https://docs.gitlab.com/ee/user/group/saml_sso/
GitLab uses projects instead of repository, is it ok to use "repository" in the Intro?
Should docs be manually generated for items that don't automatically come from Legitify?


[Feature] Navigation with arrow keys

More user-friendly and going along the shortcut.

We can use a list of lists and compare heights of mangas.
Basically:

(1), (2), (3)
(4), (5), (6)

  (7)

The first level is each line and separated by commas the second level of the list.


Add other advisors to team page

I need to get headshots and short bios for each of the following, then add them to the team page:

[ ] Quinn Slack
[ ] Beyang Liu

@zachlatta should we move this issue to Backlog because you're assigned to it as per our agreement that any assigned tasks should be in backlog?

Not going to do this.


Future scheduling

PR to bring scraping code into master, was originally going to be left as a separate branch AFTER iteration 2 because seed scripts and database columns were not compatible yet but we will create another story for that and merge this first as just a story for the code itself and not the integration of the code. Iteration was to have a fully functional scraper for both HKN and Berkeleytime websites for course surveys, professor ratings, and course catalog information as discussed with our GSI, Avi, Adnan and the customer Professor Patterson. All necessary instructions and shell scripts have been included to make running the scripts easier from ruby.

As a note for grading, now new commits were added to the PR and one run of data from a scrape was included in the commit as well


Run example - "connection pool has ended"

Bug report
Describe the bug
I followed the steps to be able to run the example and test the grid, but the connection is not kept online.
A clear and concise description of what the bug is.
The sample application is unable to stay connected to Supabase. The environment variable is correctly configured in .env, but as soon as the application tries to fetch the data from Supabase, this message appears in the log "connection pool has ended".
To Reproduce

Go to "Run example" in Read.me and follow steps
Access your project at subase.com>settings>Database. Look for the Connection string block.
Copy your string and paste it in the environment variable NEXT_PUBLIC_CONNECTION_STRING
Run the application and see the error in the terminal

Expected behavior
The application is expected to remain Online
Screenshots

If applicable, add screenshots to help explain your problem.
System information

OS: [ Windows10]
Browser [ chrome]
Version of supabase/grid: [e.g. 2.0.0]
Version of Node.js: [e.g. 14.19.3]

I followed the steps to be able to run the example and test the grid, but the connection is not kept online.
That's expected for the example app @jjromary cos i end the connection pool on each query
https://github.com/supabase/grid/blob/7bc0b11c1c6d49550b88cccee338e5751b01dbd3/example/pages/api/sql-query.ts#L17-L21

https://github.com/supabase/grid/blob/7bc0b11c1c6d49550b88cccee338e5751b01dbd3/example/components/grid.tsx#L7-L8
if you can't see your table data, try to change default schema and tableName to an existing table in your db

Thanks for the explanation @phamhieu , I was able to visualize the data of my table.

I followed the steps to be able to run the example and test the grid, but the connection is not kept online.

That's expected for the example app @jjromary cos i end the connection pool on each query
https://github.com/supabase/grid/blob/7bc0b11c1c6d49550b88cccee338e5751b01dbd3/example/pages/api/sql-query.ts#L17-L21
https://github.com/supabase/grid/blob/7bc0b11c1c6d49550b88cccee338e5751b01dbd3/example/components/grid.tsx#L7-L8
if you can't see your table data, try to change default schema and tableName to an existing table in your db

Thanks for the explanation @phamhieu , I was able to visualize the data of my table.


(v5) Tutorial update following template change

📋 Explain your issue
First, sorry if I choose the wrong template... Incorrect Content Report didn't seem to fit so...
As discussed during Talking & Doc'ing yesterday (at least for me, the 14/11), the tutorial for v5 needs to be updated following the changes made by https://github.com/withastro/astro/pull/12083.
I haven't finished the tutorial yet, it took me longer than I thought. (This is the first time I do it, you have to excuse me. 🎉 Well, it's mainly taking notes that takes time! 😄 )
I stopped at Add an RSS feed. To avoid losing my notes, I preferred to share them now.
First try with pnpm create astro@beta
I tried this approach first but, I agree with Chris. If we keep pnpm create astro@latest, there are too many things to update. Even by modifying two steps while initializing the project, from step 12 it is no longer possible to follow the tutorial without major changes.
Second try with pnpm create astro@beta -- --template minimal
In summary, there are fewer changes but we will have problems with Typescript from Unit 5 onwards. I haven't looked for fixes yet, just noted the reported errors.
Also, I skipped the steps related to Github and Netlify because I don't see why they would be affected... and I didn't want to waste time with that. If needed, I'll redo the tutorial when I have more time.

On Create your first Astro project

Step 1 needs to be updated with the template flag
Step 4 and 5 needs to be removed

On Create a blog post archive

Step 1, nit:

-const allPosts = Object.values(await import.meta.glob('./posts/*.md', { eager: true }));
+const allPosts = Object.values(import.meta.glob('./posts/*.md', { eager: true }));

We don't need await. In VS Code, this is underlined with three dots when we use it: 'await' has no effect on the type of this expression.ts(80007). So it's probably best not to include it.

Step 2, we start having issues with Typescript!

{allPosts.map((post) =>
{post.frontmatter.title}
)}

Both url and frontmatter are underlined and show the following error Property 'url' does not exist on type 'unknown'.ts(2339).

On Generate tag pages

First, a nit: is there an Expressive Code syntax to highlight all the added props as ins? I had seen a post on Discord about this, and by going quickly, I also got caught! It's confusing that some lines are green while some parts, also added, are gray.
Then, new Typescript error due to frontmatter in filteredPosts: Property 'frontmatter' does not exist on type 'unknown'.ts(2339).

On Build a tag index page

First, a nit: same as before we don't need await for const allPosts = Object.values(await import.meta.glob('../posts/*.md', { eager: true }));
Then, again, Typescript error due to frontmatter.

I stopped there, but I imagine we'll have similar problems with Typescript going forward.

I see two options:

create a Typescript type for Object.values but this is not beginner friendly
try introducing a step in the project initialization to use another preset for Typescript

Edit: I just checked and when using --template minimal, it seems the default Typescript preset is still "astro/tsconfigs/base". So I guess the Typescript errors I noted already exists in v4...
Consistency

In the "Try it yourself - Customize your blog post layout" section of Create and pass data to a custom blog layout, we show this refactoring:

Published on: {frontmatter.pubDate.toString().slice(0,10)}

Then, in the next example and in the next page we show:

{frontmatter.pubDate.toString().slice(0,10)}

Shouldn't we keep Published on: to be consistent and avoid confusing the reader?

In the "Code Check-in: MarkdownPostLayout" section of Build a tag index page

{frontmatter.description}

{frontmatter.pubDate.toString().slice(0,10)}

The description was after the publication date in the previous pages, now it is before.
Since this is a check aimed at novices, it may be better to remain consistent... (and point 1 also applies here).
Accessibility, unrelated to v5
I think we have an accessibility problem in "Test your knowledge". Firefox developer tools report me a contrast issue for:

the "Submit" button (light theme 2.76 / dark theme 1.98)
the "Correct" mention (light theme 1.58 / dark theme 6.40 so it is ok)
the "Try again" mention (light theme 2.61 / dark theme 3.90)

More or less related, I would say that the green color for the checkmark stings the eyes a little... especially for the light theme. (I don't know if you say that in English... "piquer les yeux", let's just say it's not pleasant to look at 😅 )
define:vars, more or less related to v5 (v6?)
I thought there was some discussion about define:vars. Both for scripts and styles. I haven't seen any PR related to this topic, so I guess that there is no progress on this question. I preferred to note it anyway. If its use is discouraged, maybe it's time to not display it in the tutorial. Or maybe this can wait until a more precise decision...
On Style your About page, we use define:vars to define a CSS variables. Should this be updated?

Ah! This is amazing! I've had my head down all day working in the files themselves, but this is all relevant in #10035 !

Maybe I should have mentioned you before (and maybe Chris and HiDeoo) but as I know you are busy I hesitated! 😉

I thought there was some discussion about define:vars. Both for scripts and styles

Only for scripts! It's still a perfectly valid and encouraged pattern for styles!

accessibility

Let's do that entirely in a different issue/PR!

consistency issues

Yes, let's tackle those here!

1st & 2nd try re: INSTRUCTIONS:
See my updates to the text / intro, and whether those are sufficient!
1st & 2nd try re: TYPESCRIPT ERRORS:
YES! This is what we want, and still to do in the original PR. These should absolutely be tackled here.
1st & 2nd try re: await import.meta.glob()
Let's address this issue wherever it occurs in this PR, but I distinctly remember being told to ADD IN the await (which wasn't there in the Astro.glob() version of the tutorial). So, I will need especially @delucis to weigh in here for code accuracy and pedagogy.

minimal template tsconfig.json looks like strict to me. Are you on the next branch?
https://github.com/withastro/astro/blob/next/examples/minimal/tsconfig.json

Only for scripts!

Oh okay! I thought that applied to both.

accessibility

Let's do that entirely in a different issue/PR!

Yes that makes sense, I just added it there so I wouldn't forget to talk about it. 😅

1st & 2nd try re: INSTRUCTIONS:
See my updates to the text / intro, and whether those are sufficient!

From what I've read, I think so! But I'm up for retesting the tutorial with these changes in mind and going all the way through this time. I can do this tomorrow, rather in the afternoon (for me), so within 24 hours I should be able to add more information.

minimal template tsconfig.json looks like strict to me. Are you on the next branch?
https://github.com/withastro/astro/blob/next/examples/minimal/tsconfig.json

Following the link, you are right. However, when I use pnpm create astro@beta -- --template minimal (I just checked again), the tsconfig.json file contains:
{
  "extends": "astro/tsconfigs/base"
}

Maybe the astro@beta package is not up to date?

Maybe the astro@beta package is not up to date?

Interesting! So for the sake of THIS PR, assume that it will be the strict template.
This is what we currently show for running create astro for beta 5. Does it work with this command?

Oh ok, so I followed the tutorial with Astro v4 apparently... I didn't think to check package.json. 😭 I did try @next and it didn't work at all. Then, I though @beta would work with v5...
So I just tested both pnpm create astro@latest -- --ref next and pnpm create astro@latest -- --ref next --template minimal. Both works with v5.
With pnpm create astro@latest -- --ref next, we still have How would you like to start your new project? and I can choose Empty (which seems to be minimal).
And in both cases, I have the following prompt: How strict should TypeScript be? and I can choose Relaxed (so, base).
I'm even more confused now. I thought the PR removed these questions... This definitely needs more testing...

Uh, well... I'm not sure what to expect from all that! Might be time to ask the devs what's going on there!

I just retested both commands to make sure I didn't do something stupid last night. 😅 I put a more detailed "report" below... but it corresponds to my observations from yesterday.
So, pnpm create astro@latest -- --ref next seems to be the right command, only the prompt does not match...
pnpm create astro@latest -- --ref next

package.json:

  "dependencies": {
    "astro": "^5.0.0-beta.8",
    "@astrojs/check": "^0.9.4",
    "typescript": "^5.6.3"
  },

src/pages/index.astro uses import { Welcome } from 'astro:components';
tsconfig.json extends "astro/tsconfigs/strict"
The prompt seems to match the old/current prompt...
The template seems broken...

Prompt
Template

pnpm create astro@beta

package.json:

  "dependencies": {
    "astro": "^4.16.13"
  },

src/pages/index.astro does not use import { Welcome } from 'astro:components';!
tsconfig.json extends "astro/tsconfigs/base"
The prompt seems to match the new prompt...
The template seems fine.

Prompt
Template

So I redid the tutorial, in full this time (except Github/Netlify). I relied on #10035.
Other than what I've already noted, there's not much new. Typescript errors are just a little different (and again, the principle is the same: it doesn't know the shape of objects).

Create your first Astro project

Here, given the previous observation, I did not follow the steps to the letter but your modifications seem good to me.
But, if we want to be faithful to the questions asked, nit:

“Where would you like to create your new project?” should be “Where should we create your new project?”
“Would you like to install dependencies?” should be “Install dependencies?”
“Would you like to initialize a new git repository?” should be “Initialize a new git repository?”

Here my steps:

pnpm create astro@latest -- --ref next --template minimal
Confirm "y"
Where should we create your new project? "./tutorial"
Do you plan to write TypeScript? "y" (This step should no longer exists but in the meantime...)
How strict should TypeScript be? "enter" (Strict, recommended but this step should no longer exists)
Install dependencies? "y"
Initialize a new git repository? "y"

Use your first CSS variable

This is not really a change, rather a "bug".
Using define:vars on


U5-news-BE-developed

Summary
Backend for news tab has been developed, now it sets news from API
Screenshot

Trello Card
https://trello.com/c/OFGWsLRe/11-u5-home-page-backend-news

Changes uploaded

changes has been uploaded


Thanks, image-> sketch capabilities (rtsc available)?

Thank you so much for this great repo,
I was wondering if you have any plans to implement rtsc for converting also image to sketch with different techniques?
https://rtsc.cs.princeton.edu/  or neural contourns or other?
Do you know if there is already a repository for these converstions?
Great work and thanks

https://openaccess.thecvf.com/content_cvpr_2018/papers/Song_Learning_to_Sketch_CVPR_2018_paper.pdf
Hello, you may want to check this project.


Unable to import module when running from a read-only filesystem

When importing guidance from a read-only filesystem, there are a couple of issues:

Opening the log.txt file (in https://github.com/microsoft/guidance/blob/main/guidance/_utils.py#L10) will always raise an exception as it can't be opened for writing. Can this be switched to use the standard python logging module instead?

Setting caching=False still tries to create the cache directory. Can be worked around by setting os.environ['XDG_CACHE_HOME'] = '/tmp' (or somewhere that is definitely writeable) before importing, but isn't ideal.

System info:

OS: AWS Lambda Python 3.9
Guidance Version: 0.0.47

hey @pthimon interesting that you are running it in aws lambda. How do you manage the stateless computation? I am having trouble storing, loading and continuing a partially executed program.

Hi @Sam1320 I'm just storing the partial template string, and then reloading it when the next request comes in.
The simplest example would be:
initial_template = '''{{~#geneach 'conversation' stop=False~}}
{{#user~}}
{{await 'user_message'}}
{{~/user}}

{{#assistant~}}
{{gen 'assistant_message' temperature=0.8 max_tokens=500}}
{{~/assistant}}
{{~/geneach}}'''

template = load_template(user_id)  # from a db
if not template:
  template = initial_template
chat = guidance(template)
output_template = chat(user_message=msg) # msg is from request
save_template(str(output_template), user_id)  # saves to db, can save output_template.variables() if you need them

Obviously the template would be more complicated in a real example!

Hey @pthimon  thanks for the reply!.
How do I save the variables() ?
I am doing the following:
import guidance
guidance.llm = guidance.llms.OpenAI('gpt-3.5-turbo')
guidance.llm.cache.clear()

prompt = guidance(
'''{{#system~}}
You are a helpful assistant
{{~/system}}
{{~#geneach 'conversation' stop=False~}}
{{#user~}}
{{set 'this.user_text' (await 'user_text')}}
{{~/user}}
{{#assistant~}}
{{gen 'this.ai_text' temperature=0 max_tokens=300}}
{{~/assistant}}
{{~/geneach}}''', stream=False, silent=True)

prompt = prompt(user_text ='Hello there :)')

with open('prompt.txt', 'w') as f:
    f.write(str(prompt))

with open('prompt.txt', 'r') as f:
    prompt = f.read()

prompt = guidance(prompt)

prompt = prompt(user_text ='I want to travel to the moon')

But get the error:
AssertionError: Can't set a property of a non-existing variable: conversation[-1].user_text

Error in program:  Can't set a property of a non-existing variable: conversation[-1].user_text

I didn't need to save the variables as I just parsed the messages out of the generated template, so removing the this. prefix on those variables makes it run.

Experiencing this same issue — would love the option to either disable log.txt, or choose my own home for it!


fix: Provide multiple values for TRANSLOCO_SCOPE to support lazy loading multiple json files

PR Checklist
Please check if your PR fulfills the following requirements:

[X] The commit message follows our guidelines: https://github.com/ngneat/transloco/blob/master/CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[X] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?
It does not support multi: true when providing TRANSLOCO_SCOPE, meaning you can only have one scope per module/component
Issue Number: N/A
What is the new behavior?
Fix for https://github.com/ngneat/transloco/issues/181. This makes it possible to provide multiple translate scopes to a module or component. Works with structural directives and pipe.
Does this PR introduce a breaking change?
[ ] Yes
[X] No

Other information

@mohamedaarab1994 looks ok, I have added a few comments.
Also, could you please add some tests to your code?
Thanks.

@MohamedAarab any progress on the comments? we want to release a new version with this feature

@itayod Yes, sorry for the delay, had no access to my work pc, I will commit ASAP

@itayod Yes, sorry for the delay, had no access to my work pc, I will commit ASAP

It's ok :) Thanks!

@mohamedaarab1994 almost there, just revert the implementation and add UT

@mohamedaarab1994 LGTM!
Great work on the feature thanks!


fix bug where cannot draw strand bound to other strand

Create a strand in the forward direction:

In Pencil mode, try to draw a reverse strand within the same offsets. The strand will appear, but dragging the mouse while the button is down will not expand the strand:

The same happens if a reverse strand is already present and you try to draw an overlapping forward strand:

I noticed that if you start drawing a strand outside the boundaries of another, it stops you from dragging it over the existing strand (despite one forward and the other reverse):

So it seems likely that the bug is some bounds-checking code that is not properly accounting for forward/reverse booleans in domains.

I fixed this by reverting the code in state/design.dart, in the method Deisng.domain_on_helix_at. It's currently
  /// Return [Domain] at [address], INCLUSIVE, or null if there is none.
  Domain domain_on_helix_at(Address address, [StrandCreation strand_creation = null]) {
    for (var domain in this.helix_idx_to_domains[address.helix_idx]) {
      if (domain.contains_offset(address.offset) && domain.forward == address.forward) {
        return domain;
      }
    }
    return null;
  }

But to fix the bug in #855, it was changed to this:
  /// Return [Domain] at [address], INCLUSIVE, or null if there is none.
  Domain domain_on_helix_at(Address address, [StrandCreation strand_creation = null]) {
    for (var domain in this.helix_idx_to_domains[address.helix_idx]) {
      if (domain.contains_offset(address.offset) && domain.forward == address.forward) {
        return domain;
      } else if (strand_creation != null && overlap(domain, address.offset, strand_creation.start)) {
        return domain;
      }
    }
    return null;
  }

I'm not sure how to reproduce the bug in #855, but I'm putting this comment here for help with fixing that bug.

In case we re-open this issue, see this comment for why I reverted the change for it: https://github.com/UC-Davis-molecular-computing/scadnano/issues/883#issuecomment-1646740743


fix(exporter-collector-grpc): incorrect default URL after 0.20.0 update

Which problem is this PR solving?

Fixes the connection issue mentioned at https://github.com/open-telemetry/opentelemetry-js/issues/2264, where exporter-collector-grpc is not connecting to otel grpc connector when using localhost:4317.

Short description of the changes

Changes documentation and defaults from localhost:4317 to grpc://localhost:4317 for @opentelemetry/exporter-collector-grpc package

I am a bit lost with those CI errors... I suppose these issues were not due to my changes or were they?

Looking into the asserts which fail it looks very much like it is because of the changes here
      Uncaught AssertionError [ERR_ASSERTION]: 'grpc://localhost:4317' === 'localhost:4317'
      + expected - actual

Seems the NodeJS 16 CI test failed. Is there a way which I can re-trigger it or is it fine as it is?

Can you please ensure this is working fine with this example
You can also update the docker compose to the latest version you were testing.
If all is fine we tend to update readme with information about last tested version so that it is clear which version is compatible with this as spec and collector were not always are in sync.

Seems the NodeJS 16 CI test failed. Is there a way which I can re-trigger it or is it fine as it is?

The node 16 test is fine, but the browser test failure is probably real.

I will try to run re-run the tests in composer during the weekend. The browser test is probably something that I missed while searching and replacing the default URL updates.

So, just tested it based on the examples and it seems fine. I need to note though that, on Zipkin, the service is marked as unknown instead of BASIC-SERVICE. I need to understand how to check the browser issue.

If all is fine we tend to update readme with information about last tested version so that it is clear which version is compatible with this as spec and collector were not always in sync.
I tested with the version which is in the README currently, so should be all good 😉

I just re-ran the browsers tests locally through lerna run --scope @opentelemetry/instrumentation-fetch test:browser and it seems to work. Could someone re-trigger the browser test in the CI just to see if it is fine?

Ok, so something is off here. With the example, it works as far as I add the config.url=grpc://localhost:4317. But, if left empty and leave it to go with the default config, this will error.
Checking a bit the code, I found this: https://github.com/open-telemetry/opentelemetry-js/blame/main/packages/opentelemetry-exporter-collector-grpc/src/util.ts#L110-L122
It seems it is just used to check if the schema is either HTTP or GRPC, but actually it doesn't do anything with it, as it returns target.host at the end. The default value I added in this PR contains grpc://, which obviously breaks the GRPC client later on.
Should I revert the default values and just add documentation that grpc:// or http:// is required on the url?
Another thing as well: the grpc-collector is not sending data to the Zipkin, but I guess this is what I mentioned on issue #2264.

Checking a bit the code, I found this: main/packages/opentelemetry-exporter-collector-grpc/src/util.ts#L110-L122 (blame)

I find it odd that the collector grpc check for https since it only support grpc.

Should I revert the default values and just add documentation that grpc:// or http:// is required on the url?

I think that would be the way to go if grpc itself doesn't support using just a hostname/port combination

@brunoluiz any update on the browser tests here?

As mentioned on https://github.com/open-telemetry/opentelemetry-js/pull/2266#issuecomment-863951585, I've reverted the changes and just kept the README changes. The utils might have some reason to exist, but changing default values causes it to crash. I suppose more investigation might be required?

In the PR title you have incorrect default URL. Is the default URL actually bad or is it just the documented example with the bad URL?

In the PR title you have incorrect default URL. Is the default URL actually bad or is it just the documented example with the bad URL?
After discussion here, I reverted the changes on the default URL itself, as the default URLs work fine. But, if the developer specifies some other URL, it requires the grpc scheme to be defined.

Due to that, I just changed title and description accordingly. Let me know if it ready to merge.

Another PR has been opened to update the behavior to automatically add grpc:// if not set, but i think its make sense to tell users that its required anyway in the docs


Support ZLO device types to support newer Zigbee devices in ZHA

Description:
Support the device types that are added in https://github.com/zigpy/zigpy/pull/176
so newer Zigbee (3.0) devices can be supported.
Tested with my innr RB 285 C bulb.
This PR is waiting for an official zigpy release (cc @Adminiuga)
See https://github.com/zigpy/zigpy/pull/176
Checklist:

[x] The code change is tested and works locally.
[ ] Local tests pass with tox. Can be verified after release of zigpy
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

Hi @jurriaan,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

can merge once builds pass

Um, we have to push new zigpy version to PyPi for the build to pass.

@Adminiuga correct, mentioned that in this PR description. Is it possible for you to push a new version?

@jurriaan just pushed new version to PyPi. Update the manifest.json and run script/gen_requirements_all.py
@dmulcahey is it ok to bump version for zigpy in this PR you would you like a new one?

Same is fine by me...

aprs device tracker breaks this build...

@jurriaan do you want to try rebasing it to prior https://github.com/home-assistant/home-assistant/commit/8fcfcc40fccb606e7dfe4b79c41ec3dcb408e6c5#diff-34298aba7fdfcffa995d0a1fd0b2a068 commit? To exclude homeassistant.components.aprs, as it seems device tracker is breaking the builds.

@Adminiuga Rebased and green


Overlap of long links on search results

I believe it's similar to #72 but now it's on search results instead of page content.

The content that caused the issue:
@Book{IMC-Embedded-Install-Guide,
  author     = "Hewlett-Packard Development Company",
  ref-author = "HP",
  title      = "H3C Intelligent Management Center: Centralized Deployment Guide with Embedded Database",
  url        = "https://www.h3c.com/en/Support/Resource_Center/EN/Network_Management/Catalog/H3C_IMC/IMC/Technical_Documents/Install___Upgrade/Installation_Guides/Distributed_Deployment_Local_Databas/",
  year       = 2022
}

Hello.
The previous change was targeted for "#dokuwiki__content .page p" and seems too narrow. I've widened the target to "#dokuwiki__content .page".
Could you try re-install?


cannot install extension  and [DEP0005] DeprecationWarning: Buffer() (without ECONNRESET problem)

code-server version: code-server v1.1156-vsc1.33.1
OS Version: centos 7
nodejs version tried : v10.14.2 and v10.16

Description
When trying to install extension with command line, it does not work.
Steps to Reproduce
Try to install any extension :

/opt/vscode-server/code-server --install-extension eamodio.gitlens --user-data-dir=/root/.vscode
/opt/vscode-server/code-server --install-extension ms-python.python --user-data-dir=/root/.vscode

Got same result :
(node:697) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
INFO  code-server v1.1156-vsc1.33.1
ERROR (node:709) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
ERROR
ERROR Extension 'eamodio.gitlens' not found.
ERROR Make sure you use the full extension ID, including the publisher, eg: ms-vscode.csharp
ERROR
ERROR Failed Installing Extensions: eamodio.gitlens
ERROR

Unfortunately, it looks like gitlens doesn't support vscode 1.33.1 anymore. When you install an extension from the command line it doesn't report that a compatible version wasn't found.
code-server v2 is almost out, and the VS Code version bundled with code-server will be on par with the release version of VS Code.

Issue is stale. Closing as no longer relevant to current tree.


Flutter build apk not working with flavors

Cannot release apk for production!!!
After upgrading to null safety i needed to upgrade to gradle 4.0.
Same as https://github.com/flutter/flutter/issues/58247 which was opened over a year ago!!
Gradle expects a ../libs.jar for every combination of flavor - buildType (in new project needs 3 - release - debug - profile, in my project needs 48 so the 'solutions' (offered on the above issue) of running each one once is out of the question especially with dev-op).
This prevents us from any future action with our app. Can this be fixed maybe in a hotfix?
Steps to Reproduce

Run flutter create counter
Add this to build.gradle:

``
flavorDimensions "app"

productFlavors {
	flavor1{
		dimension "app"
	}
	flavor2{
		dimension "app"
	}
}

Run flutter build apk --flavor flavor1

Output:
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':app:lintVitalFlavor1Release'.

Could not resolve all artifacts for configuration ':app:flavor2ReleaseRuntimeClasspath'.
Failed to transform libs.jar to match attributes {artifactType=processed-jar, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
Execution failed for JetifyTransform: C:\Users\nikts\Projects\counter\build\app\intermediates\flutter\flavor2Release\libs.jar.
Transform's input file does not exist: C:\Users\nikts\Projects\counter\build\app\intermediates\flutter\flavor2Release\libs.jar. (See https://issuetracker.google.com/issues/158753935)

flutter doctor:
C:\Users\nikts\Projects\counter>flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 2.0.6, on Microsoft Windows [Version 10.0.19042.928], locale en-US)
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
[√] Chrome - develop for the web
[√] Android Studio (version 4.1.0)
[√] VS Code (version 1.56.0)
[√] Connected device (2 available)
• No issues found!

try to run with. Run
flutter build apk --flavor flavor1 --release or flutter build apk --flavor flavor1 --profile this is working fine for me.

Why was this closed? it is not fixed

@niktses The fix is pushed to master and you will need to upgrade to latest master version to see the fix and wait for it to reach to stable.

@darshankawar
is it somehow foreseeable when this will get merged into stable?
i still have the problem with 2.2.3
and i have to use gradle version 3.5.4 to get my release builds working with flavors

I have the same problem, but it is solved when flavors are commented


[FLINK-3589] Allow setting Operator parallelism to default value

Adds the public field ExecutionConfig.PARALLELISM_UNKNOWN as a flag
value to indicate that the default parallelism should be used.

passing the default to Operator.setParallelism() will result in an exception, intended?

Perhaps there should be two flags, PARALLELISM_DEFAULT = -1 to reset the parallelism to the system default, and PARALLELISM_UNKNOWN = -2 which leaves the parallelism unchanged.

The changes look correct. If you could add a small test to verify that passing PARALLELISM_UNKNOWN doesn't modify the parallelism we're probably good to go.

and a rebase since github says there are conflicts ,)

I just stumbled across this in the code.
I am a bit confused by the two different flags PARALLELISM_DEFAULT and PARALLELISM_UNKNOWN. What is the purpose of the later?

PARALLELISM_UNKNOWN is a no-op which leaves the parallelism unchanged. This is a useful default for batch algorithms such as JaccardIndex for which parallelism can be optionally configured. If the user does not specify a parallelism we do not want to override the parallelism of the ExecutionEnvironment as would happen if we used PARALLELISM_DEFAULT.

Couldn't that be equally well checked in the program that calls setParallelism(...)?
Just asking because this is handled only in very few parts of the DataSet API anyways (not at all handled in streaming) and seems a bit of a special case.
You may notice, I am starting to ask this question about "what needs to be part of the API, what can be part of the user program" quite a bit lately ;-) Trying to be conscious about complexity and commitment to maintaining all the API contructs.

It's good to have you back :)
I think we can get by with only PARALLELISM_DEFAULT since java.operators.Operator.setParallelism(int) is only called by the Scala and Python APIs. I'll open a ticket.


feat: Pass space ref to file.upload provider

Motivation / Background
This PR aims to complete the first two TODOs from #6717
Details

[x] Passes the relevant space to provides.file.upload
[x] Remove the need for useResolvePlugin(parseFileManagerPlugin) in the EditorMain component of the markdown plugin

Feedback applied & rebased

@icidasset it looks like a lint check is failing, could you take a look at that?

@wittjosiah Should be good now, remaining failures are unrelated to the changes made here.


[Bug] Email not setup message is shown to user even though email is setup

Description
Steps to reproduce the behaviour:

create a fresh install with a fresh org with user registration disabled and no email settings entered, invite users, have them register. No way to reset a users pass manually
Try to add email settings to env and restart container, following sendgrid directions, password recovery still says email is not setup and reset email did eventually get sent even though it says
You haven’t setup any email service yet. Please configure your email service to receive a reset link

Important Details

Version: [Cloud / Self-Hosted vx.x]
OS: [e.g.MacOSX]
Browser [e.g. chrome, safari]

@mohanarpit Hey is this still an issue? I couldn't reproduce it using the following steps:

Disable signup
Create an account using the admin email
Invite a new user -> sign-up with the new user
Setup email settings -> restart using the cmds from the docs
Try forgot password flow, the forgot password modal showed the success message

Yes

/ # env | grep -i mail
APPSMITH_MAIL_PORT=587
APPSMITH_MAIL_ENABLED=true
APPSMITH_MAIL_USERNAME=apikey
APPSMITH_MAIL_SMTP_AUTH=true
<EMAIL_ADDRESS>APPSMITH_MAIL_SMTP_TLS_ENABLED=true
APPSMITH_MAIL_PASSWORD=SG.XXXXXXXXXXXXXXXXXXXX
<EMAIL_ADDRESS>APPSMITH_MAIL_HOST=smtp.sendgrid.net

Okay after adding the environment variables to the editor container, the message went away
Seems like a config issue causes this
Do you really need all the SMTP login details in the editor? Which ones specifically are needed to avoid this issue?

Okay after adding the environment variables to the editor container, the message went away
Seems like a config issue causes this
Do you really need all the SMTP login details in the editor? Which ones specifically are needed to avoid this issue?

@0sanity
Here just adding APPSMITH_MAIL_ENABLED=true, would hide the warning message on the client. If that's what you meant.


COPY TO: Log when the client request compression

We have some traces from users requesting COPY TO operations, with compression in the logs.
We know for a fact that they requested compression, because there's a difference in reported sizes between SQL API traces and nginx traces, showing a compression ratio > 50%.
If the header Accept-Encoding: gzip is present, the field of the trace data-ingestion.gzip should be set to true. Wondering if that header is passed from nginx to node or if it is lost in the way.
cc/ @dppascual @oleurud

@CartoDB/rt-managers I think this is a good candidate for RT

PR https://github.com/CartoDB/CartoDB-SQL-API/pull/532

Adding more info about it.
I decided to set the gzip value as null because of node doesn't know if the compression happens or not.
Nginx is the responsible about compress the response and although the client sends the Accept-Encoding: gzip, nginx may choose not to compress the body https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Encoding
Knowing that, for me, it has sense to save in the log as true or false because it gives us an important information.


Sorting by multiple criteria does not work

Describe the bug

Sorting only works when it is by one criterion only
Steps to reproduce
/
Expected behavior
/
Are you using the mobile app?
No
Obsidian debug info
/
Relevant log output
No response

Hi @Zachary0116. Yes, this is a known bug. I will fix it this week.
Related to #318

Fixed in 8.2.0.


OPDS 1.x parser can't handle the Feedbooks OpenSearch Document

It seems that the current parser cannot parse the OpenSearch Description Document from the Feedbooks catalog: http://www.feedbooks.com/opensearch.xml

closing this issue as it has been handled in a PR that is merged.