Start using 2 Dispatcher classes

Currently there is only 1 Dispatcher - The Dispatcher.
It has no specific typing except for the event name, other than that its *args: Any, **kwargs: Any which kind of makes sense for gateway opcode events & gateway DISPATCH events. (as manually filtering this yourself is stupid)
I don't have any specific ideas for improvement for opcode events and DISPATCH events, however for events nextcore produces, using vauge and dynamic typing is stupid.
I propose something like this (No clue about class name
d: Dispatcher2[EventType1, EventType2] = Dispatcher2()

@d.listen()
async def all_events(event: EventType1 | EventType2): # Or just realistically use typing.Any
    ...
@d.listen(EventType1)
async def one_event(event: EventType1):
    ...

This avoids reading typehints - which I do not want in this library, as it is "magic".

What about calling the new dispatcher TypedDispatcher since it has more specific typing? Alternatively, the current dispatcher could be renamed RawDispatcher, but that would obviously be a breaking change.

imo EventDispatcher is more accurate


Support for "," "L" "?" characters in crons

There are some cron systems that use these additional symbols. For example AWS Event Bridge / Cloud Watch Events.
https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-create-rule-schedule.html#eb-cron-expressions
Example
* 10 * * ? *

Moved to local-crontab


End time earlier than start time considered not valid

A time span like 22:00-05:00 is not considered valid in strict mode, even though

it is described as valid in the specification and

this parser itself pretty-prints 22:00-29:00 as 22:00-05:00. (So, it currently creates strings that itself considers invalid)

As I previously pointed out https://github.com/simonpoole/OpeningHoursParser/issues/80#issuecomment-1881145178, mentioned in the README and in the JavaDoc https://github.com/simonpoole/OpeningHoursParser/blob/master/src/main/java/ch/poole/openinghoursparser/OpeningHoursParser.jj#L79  the behaviour wrt times is configurable.


dfuseeos local producer/mindreader fails long term unit tests

Brief:
Running dfuseeos in unit tests, when I run full suite, fails, but works initially.  It's coming off the rails somewhere.
Took a look at the logs and just seeing http nodeos errors and nothing else is popping out.
Dfuseeos output: too big telegram link: https://t.me/dfuseAPI/13219
Subscription logs (if of use)
pprovider1-dfuse-2020-09-24.log
Command used:
dfuseeos start -vvvv \
    --search-archive-grpc-listen-addr ":13050" \
    --apiproxy-http-listen-addr ":8081" \
    --eosq-api-endpoint-url ":8081" \
    --dashboard-http-listen-addr ":8082" \
    --search-archive-http-listen-addr ":14016" \

We believe this may be a race condition created internally, closing unless proven otherwise.


v2: Cannot read property 'cursor' of undefined

I've got a query procedure that I've been calling as follows;
In v2 an error is raised when no results are found.  In v1 this wouldn't raise an error, and I'd just have an empty result set.
assignedProjects(toCompanyId:115, first: 20) {
    edges {
      node {
        id
        name
      }
    }
    pageInfo {
      endCursor
    }
  }

{
  "data": {
    "assignedProjects": {
      "edges": [],
      "pageInfo": {
        "endCursor": null
      }
    }
  },
  "errors": [
    {
      "message": "Cannot read property 'cursor' of undefined",
      "locations": [
        {
          "line": 21,
          "column": 7
        }
      ]
    }
  ]
}

Fixed in<EMAIL_ADDRESS>:+1:


[PDI-18782] Support for compressed files in XBaseInput step

Includes a compression combo box in XBaseInputDialog, similar to the one found in TextInputDialog, showing the available compression providers
Wraps the file inputstream into the corresponding decompressing inputstream
Small refactorings and removal of unused code
Workaround for bug in javadbf library (doesn't check return from InputStream.read(char[], int, int))
Adds a couple of tests for gzip and zip compressed files

:white_check_mark: Build finished in 45m 48s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine,ui

:ok_hand: All tests passed!
Tests run: 3682, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message

:x: Build failed in 3h 1m 22s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine,ui

:exclamation: No tests found!
Errors:
Filtered log (click to expand)

script returned exit code 1

:information_source:  This is an automatic message

:x: Build failed in 2h 41m 14s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine,ui

:exclamation: No tests found!
Errors:
Filtered log (click to expand)

script returned exit code 1

:information_source:  This is an automatic message


Add integration tests with pytest-operator

Thanks for the review! Ready to be merged? Feel free to do so, as I don't have merge permissions.

@zmraul , i think this repo is allowing merge without minimal 2 approvals. Should it be changed?

@zmraul , i think this repo is allowing merge without minimal 2 approvals. Should it be changed?

I don't think I have access to change this. Maybe @edumucelli @mthaddon can help?

@zmraul , i think this repo is allowing merge without minimal 2 approvals. Should it be changed?

I don't think I have access to change this. Maybe @edumucelli @mthaddon can help?

Everyone in the data-platform or ``data-platform-adminsgroups hasadmin` access to this repo, so I'd go towards managing per-group than per-person rights. I'd suggest asking the manager of those groups to add the respective people.

@zmraul , i think this repo is allowing merge without minimal 2 approvals. Should it be changed?

I don't think I have access to change this. Maybe @edumucelli @mthaddon can help?

Everyone in the data-platform or data-platform-admins groups has admin access to this repo, so I'd go towards managing per-group than per-person rights. I'd suggest asking the manager of those groups to add the respective people.

Fixed :)


Hardening Options On Android

As per pen testing:

Prevent file sharing

Add these as On<Android> options

Fixed in !14


refactor(injector): remove outdated workaround on function stringify

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Enhancement
What is the current behavior? (You can also link to an open issue here)
The injector annotator appends an empty string at the end of Function.prototype.toString to solve a bug found on Chrome 50-51 when trying to annotate functions by it's parameters name.
What is the new behavior (if this is a feature change)?
The injector annotator doesn't append the empty string anymore, as it's no longer necessary on Chrome's current version, 54.
Does this PR introduce a breaking change?
No
Please check if the PR fulfills these requirements

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

Other information:
Current tests are already covering this functionality on  injectorSpec.js on the annotation test context.
Remove an outdated workaround for Chrome 50-51 since Chrome is already on v54 for a bug in which
Function.prototype.toString didn't work as expected for the injector's annotation.

👍 for the intention of cleaning up, but I am afraid we can't remove this just yet. Although endusers are likely to run on latest versions, CI environments often use less up-to-date versions (e.g. we are running on Chrome 51 on Travis). So, removing this could potentially break the CI builds of other libs or apps.
The Remove workaround when Chrome v52 is released comment was over-optimistic on my part :smiley:
Closing since this is not actionable atm - we'll have to revisit some time in the future.

Thanks for the explanation @gkalpak :smiley:!


doc: add documentation about functional expectation vs Sonatype Platform

Implementation for #72

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

Chrome Web Store
v2.10.1
GitHub release

Your semantic-release bot :package::rocket:


Add ADR to template

Documenting Architecture Decision Record is a good thing to do.

:tada: This issue has been resolved in version 1.8.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Allow the cache to be invalided by subnets

1. Why is this change necessary?
If you have a dynamic environment you can't invalidate the cache. That's because AppCache will check if the request is allowed. At the moment you can only add IP addresses and you can't add subnets.
If you run a cronjob in a Kubernetes cluster then the cronjob runs in a different pod than the webserver. So if the cronjob pod sends a BAN request to the web server, the IP address is not allowed. You can't add the IP address of the pod because it's dynamic and will change.
2. What does this change do, exactly?
Add the possibility to add subnets to the Shopware config file ("app/config/config.php" => purge_allowed_ips).
3. Describe each step to reproduce the issue or behaviour.
Setup a dynamic environment for example with Kubernetes. Run a cronjob that updates doctrine entities (e.g. Articles).
4. Please link to the relevant issues (if any).
None.
5. Which documentation changes (if any) need to be made because of this PR?
https://developers.shopware.com/developers-guide/http-cache/#cluster-environments
6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

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

Hey,
can you change the target to 5.7. We don't plan a new patch version for 5.6 anymore

Hey,
can you change the target to 5.7. We don't plan a new patch version for 5.6 anymore

Then definitely there should be a backport for version 5.6.

Hey,
can you change the target to 5.7. We don't plan a new patch version for 5.6 anymore

This is safe that there will be no update in 5.6 anymore?
Because we might not update to 5.7 and would need to keep our intermediate fork with the fix on 5.6.

We are releasing in a short time 5.7 and therefore we don't plan an another version

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-26075
Please use this issue to track the state of your pull request.

Thanks for your Contribution! :blue_heart:


Add filter on vector size

Hello,
New feature required following this conversation with @generall on Discord.
Thanks

https://github.com/qdrant/qdrant/issues/2737


Error installing Dlib with Python3.7

Hi,
I know that this problem is everyware, but i can't find the solution.
I have CMAKE installed:
PS C:\Git\dlib> cmake --version
cmake version 3.18.0-rc1

CMake suite maintained and supported by Kitware (kitware.com/cmake).

and python
PS C:\git\dlib> python setup.py install --clean
running install
running bdist_egg
running egg_info
writing dlib.egg-info\PKG-INFO
writing dependency_links to dlib.egg-info\dependency_links.txt
writing top-level names to dlib.egg-info\top_level.txt
package init file 'dlib\__init__.py' not found (or not a regular file)
reading manifest file 'dlib.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
no previously-included directories found matching 'tools\python\build*'
writing manifest file 'dlib.egg-info\SOURCES.txt'
installing library code to build\bdist.win-amd64\egg
running install_lib
running build_py
running build_ext
Removing old directory C:\git\dlib\build\temp.win-amd64-3.7\Release
Building extension for Python 3.7.4 (tags/v3.7.4:e09359112e, Jul  8 2019, 20:34:20) [MSC v.1916 64 bit (AMD64)]
Invoking CMake setup: 'cmake C:\git\dlib\tools\python -DCMAKE_LIBRARY_OUTPUT_DIRECTORY=C:\git\dlib\build\lib.win-amd64-3.7 -DPYTHON_EXECUTABLE=C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\python.exe -DCMAKE_LIBRARY_OUTPUT_DIRECTORY_RELEASE=C:\git\dlib\build\lib.win-amd64-3.7 -A x64'
-- Building for: NMake Makefiles
CMake Error at CMakeLists.txt:3 (project):
  Generator

    NMake Makefiles

  does not support platform specification, but platform

    x64

  was specified.

CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
-- Configuring incomplete, errors occurred!
See also "C:/git/dlib/build/temp.win-amd64-3.7/Release/CMakeFiles/CMakeOutput.log".
Traceback (most recent call last):
  File "setup.py", line 261, in <module>
    'Topic :: Software Development',
  File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\lib\site-packages\setuptools\__init__.py", line 145, in setup
    return distutils.core.setup(**attrs)
  File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\lib\distutils\core.py", line 148, in setup
    dist.run_commands()
  File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\lib\distutils\dist.py", line 966, in run_commands
    self.run_command(cmd)
  File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\lib\distutils\dist.py", line 985, in run_command
    cmd_obj.run()
  File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\lib\site-packages\setuptools\command\install.py", line 67, in run
    self.do_egg_install()
  File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\lib\site-packages\setuptools\command\install.py", line 109, in do_egg_install
    self.run_command('bdist_egg')
  File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\lib\distutils\cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\lib\distutils\dist.py", line 985, in run_command
    cmd_obj.run()
  File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\lib\site-packages\setuptools\command\bdist_egg.py", line 172, in run
    cmd = self.call_command('install_lib', warn_dir=0)
  File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\lib\site-packages\setuptools\command\bdist_egg.py", line 158, in call_command
    self.run_command(cmdname)
  File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\lib\distutils\cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\lib\distutils\dist.py", line 985, in run_command
    cmd_obj.run()
  File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\lib\site-packages\setuptools\command\install_lib.py", line 11, in run
    self.build()
  File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\lib\distutils\command\install_lib.py", line 107, in build
    self.run_command('build_ext')
  File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\lib\distutils\cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\lib\distutils\dist.py", line 985, in run_command
    cmd_obj.run()
  File "setup.py", line 135, in run
    self.build_extension(ext)
  File "setup.py", line 172, in build_extension
    subprocess.check_call(cmake_setup, cwd=build_folder)
  File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\lib\subprocess.py", line 347, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['cmake', 'C:\\git\\dlib\\tools\\python', '-DCMAKE_LIBRARY_OUTPUT_DIRECTORY=C:\\git\\dlib\\build\\lib.win-amd64-3.7', '-DPYTHON_EXECUTABLE=C:\\Program Files (x86)\\Microsoft Visual Studio\\Shared\\Python37_64\\python.exe', '-DCMAKE_LIBRARY_OUTPUT_DIRECTORY_RELEASE=C:\\git\\dlib\\build\\lib.win-amd64-3.7', '-A', 'x64']' returned non-zero exit status 1.

That’s the error you get when visual studio’s c++ compiler isn’t installed. You sure you installed the c++ compiler?

You are right @davisking . I don't see in dependencies the compiler. I thought that CMake is the compiler.
It works! Thanks


Repositioning voice channels does not work as intended

Example:
VoiceChannel new: the successful callback from guild.getController().createVoiceChannel
VoiceChannel moveBy: the voice channel to move it near for, retrieved using new.getGuild().getVoiceChannelsByName("MOVE BY NAME", true).get(0)
guild: retrieved from newest instance new.getGuild();
Code I am trying to execute:
guild.getController().modifyVoiceChannelPositions().selectPosition(new).moveTo(moveBy.getPosition()).queue();
It doesn't move the channel at all, nothing happens. I am now using this because my previous code also stopped working entirely:
Channel channel = event.getGuild().getController().createVoiceChannel(icon + " " + roomType + " " + roomNumber).complete();
ChannelOrderAction action = new ChannelOrderAction(event.getGuild(), ChannelType.VOICE);
Channel startRooms = event.getGuild().getVoiceChannelsByName("MOVE BY NAME", true).get(0);
action.selectPosition(channel).moveTo(startRooms.getPosition()).queue();

Forgot to include channels are in different categories... But I don't see any ways of moving a channel into a category.

Thanks to @MinnDevelopment I found out I have to first invoke the setParent(category) method on the channel manager, and then move the channel. Closing issue.

@Galkon Thank you for detailing the answer to this issue when closing it.

Much appreciated @Galkon


Imported file has a wrong encoding: csv file, works fine with xls

ISSUE
Same file trying to import with django-admin, file contains emoji and non standard ascii characters (ex: "è"): format xls works fine, csv output is:
Imported file has a wrong encoding: 'ascii' codec can't decode byte 0xc3 in position 31: ordinal not in range(128)

Strange behaviour is that in development environment worked fine even in csv format, in deploy no.
CONFIG:
python3
tablib==2.0.0
Django==3.0.6
django-import-export==2.1.0
Any clue on this?

What encoding is the import csv file set to?
Are you setting admin.from_encoding anywhere?
can you supply an example of the failing file?

@matthewhegarty csv file is set to unicode UTF-8
In development enviroment I haven't set any from_encoding, but after in deploy failed I've tried setting it into this class:
class ProductsAdmin(ImportExportActionModelAdmin):
    resource_class = ProductResource
    list_display = ['productName', 'get_supplier', 'category', 'price', 'get_isAvailable', 'id', 'created']
    readonly_fields = ['created']
    list_filter = ('category__supplier', 'category__categoryName')
    search_fields = ('productName',)

    def get_supplier(self, obj):
        return obj.category.supplier

    get_supplier.short_description = 'Supplier'
    get_supplier.admin_order_field = 'category__supplier'

    def get_isAvailable(self, obj):
        return obj.isAvailable()

    get_isAvailable.short_description = 'isAvailable'
    get_isAvailable.boolean = True

    def get_import_form(self):
        return CustomImportForm

    def get_confirm_import_form(self):
        return CustomConfirmImportForm

    def get_form_kwargs(self, form, *args, **kwargs):
        # pass on `category` to the kwargs for the custom confirm form
        if isinstance(form, CustomImportForm):
            if form.is_valid():
                supplier = form.cleaned_data['supplier']
                kwargs.update({'supplier': supplier.id})
        return kwargs

    def get_resource_kwargs(self, request, *args, **kwargs):
        """
        The request isn't usually passed to the ModelResource constructor, so we need to add it to the kwargs dict for
          that call. Fortunately, Django Import/Export has a dedicated hook for that.
        :param request:
        :param args:
        :param kwargs:
        :return:
        """
        rk = super().get_resource_kwargs(request, *args, **kwargs)
        rk['request'] = request
        return rk

I've attached to this comment the file I've used:
As I Pointed out before: it only fails in deploy environment and message says can't decode from ascii (I use non-ascii characters: accent letters and emoji)
Product-2020-05-22.zip

it only fails in deploy environment

That is a big red flag for me. What is the difference between the two environments, I assume local vs production?

I tried importing the emoji char in a csv file on the django-import-export test env, and it worked fine,  and since it works in dev for you, we can rule out an issue with the library.
Like @andrewgy8 says, you'll have to nail down the differences between the envs.  The error message is indicating that your file is being treated as ascii not unicode, so why is this.  Once you have ruled out code or deployment differences, you could consider OS, filesystems, upload process, etc.  Can you get onto the deployment environment and inspect the file encoding?

Hey @matthewhegarty,
I'm saying this is weird basically because I've tried local (dev environment) and deploy (server backend), local client with the same exact file. Not only the same file, but at the same location.
I've tried to narrow down the differences, but since xls works fine with the upload, it looks super weird to me. Do you have any clue on where to look ?
On dev I'm using manage runserver
whereas in deploy apache2/wsgi application

it only fails in deploy environment

That is a big red flag for me. What is the difference between the two environments, I assume local vs production?

Yeah exactly, local is development environment run through manage runserver.
Deploy is production environment on a LAMP server with apache2 and running django backend through wsgi application

Could you check the setting on your apache server for AddDefaultCharset?

Could you check the setting on your apache server for AddDefaultCharset? I was reading this btw https://stackoverflow.com/questions/913869/how-to-change-the-default-encoding-to-utf-8-for-apache

@andrewgy8 I haven't set anything for AddDefaultCharset, but before writing here I've tried setting it but nothing changed. Csv was still interpreted as ascii encoding and xls worked out fine

Do you have any clue on where to look for differences in the two environment that could have lead to interpreting the csv file with ascii encoding ?

First I would try to prove that the server file has the wrong encoding - is it definitely ascii?
Then follow the chain back for how the file gets to the server - at what point does it get its encoding set?
You could try to reproduce prod env locally using Docker

What this does even mean in context of uploading files? Do you think Apache detects text files and changes their encoding or what?
I have the same problem too but with charmap codec. My settings related to import_export are IMPORT_EXPORT_USE_TRANSACTIONS = True and there's nothing about encodings in my resource. I try to import a CSV in UTF-8 from admin panel and then there's this page with the exception. I use a built-in Django web server. How do I fix this? Why does it even use charmap if the default is UTF-8?

@rarjpg Would it be possible to open this as a separate issue?.  Please include enough information to help us understand the issue.  Include steps to reproduce and an example file.  Please supply information about your os, dependency versions etc.
thanks

@andrewgy8 No I didn't, I used the workaround using only xls files. Haven't tried yet if there have been any useful updates to the package!
Also couldn't crack any difference between deploy and development environment, except from the DEBUG=true enabled/disabled

Hello Masters,
today I get this bug too.. looking the code, the problem is that the open/read file function don't have the encoding option.
I have make a PR to fix it.
thanks and attentive to your comments.

Hey guys, sorry to get you back after so long having opened the issue.
I've seen very randomly on django docs  (https://docs.djangoproject.com/en/3.1/howto/deployment/wsgi/modwsgi/) this:
https://docs.djangoproject.com/en/3.1/howto/deployment/wsgi/modwsgi/
I still don't know if could this be the solution we were looking for:

Unfortunately this has NOT solved my issue :'(

Hello Masters,
today I get this bug too.. looking the code, the problem is that the open/read file function don't have the encoding option.
I have make a PR to fix it.
thanks and attentive to your comments.

Hey guys, sorry to get you back after so long having opened the issue.
I've seen very randomly on django docs  (https://docs.djangoproject.com/en/3.1/howto/deployment/wsgi/modwsgi/) this:
https://docs.djangoproject.com/en/3.1/howto/deployment/wsgi/modwsgi/
I still don't know if could this be the solution we were looking for:

Unfortunately this has NOT solved my issue :'(

Hello Masters,
today I get this bug too.. looking the code, the problem is that the open/read file function don't have the encoding option.
I have make a PR to fix it.
thanks and attentive to your comments.

File parsing was fixed in #1306 according to python best practice.  Can you reproduce this issue with the latest release?

Closing as fixed


Send messages to group periodically

I want to build a telegram bot to send a message to a super group every couple of hours. Anyone has any idea how to realize that feature?

In my opinion you can use the Tick-Event to measure the time. After an hour you send to the Group and save the last time you send to the Group. And so on...
You must know the id of the Group.

https://github.com/mullwar/telebot/issues/125

i have done implement this functionality using node-cron same like #125


chore: code commenting for all major files

Initial checklist

[x] I read the support docs
[x] I read the contributing guide
[x] I agree to follow the code of conduct
[x] I searched issues and couldn’t find anything (or linked relevant results below)
[x] If applicable, I’ve added docs and tests

Description of changes
TODO

Codecov Report

Merging #25 (570204d) into main (75bf545) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff            @@
##              main       #25   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           15        15
  Lines          275       338   +63
  Branches        25        25
=========================================
+ Hits           275       338   +63

Files Changed
Coverage Δ

packages/config/src/commitlint.ts
100.00% <100.00%> (ø)

packages/config/src/configCreator.ts
100.00% <100.00%> (ø)

packages/config/src/index.ts
100.00% <100.00%> (ø)

packages/config/src/prettier.ts
100.00% <100.00%> (ø)

packages/config/src/tsup.ts
100.00% <100.00%> (ø)

packages/core/src/index.ts
100.00% <100.00%> (ø)

packages/ui/src/components/Templ.tsx
100.00% <100.00%> (ø)

packages/ui/src/index.ts
100.00% <100.00%> (ø)

packages/utils/src/constants.ts
100.00% <100.00%> (ø)

packages/utils/src/index.ts
100.00% <100.00%> (ø)

... and 1 more


Qiskit's historical API versions don't match their docs

We have three Qiskit versions (0.36, 0.35, and 0.34) with the documentation shifted. Those three versions have the documentation of the next version instead of its own:

Docs in qiskit/0.36 correspond to qiskit/0.37
Docs in qiskit/0.35 correspond to qiskit/0.36
Docs in qiskit/0.34 correspond to qiskit/0.35
We don't have docs for qiskit/0.34

We should shift every version except qiskit/0.36 given that we currently have version 0.37.0 there whereas in qiskit/0.37 we have version 0.37.2.
Once the shifting is done we need to remove qiskit/0.34 which will be duplicated in qiskit/0.35.
To shift every version we only need to rename the version folder in .out with the correct one and regenerate the docs. For example, to shift qiskit/0.35 we can run:
mv .out/python/sources/qiskit/0.35.0 .out/python/sources/qiskit/0.36.0
npm run gen-api -- -p qiskit -v 0.36.0 -a "" --historical

Versions regenerated:

[x] qiskit 0.36
[x] qiskit 0.35
[x] qiskit 0.34

Removed and redirects are working. https://docs.quantum.ibm.com/api/qiskit/0.34 goes to https://docs.quantum.ibm.com/api/qiskit/0.35. Good work @arnaucasau!


After my machine was powered on, all pods did not wake up and reported the error "failed to reserve sandbox name " xxxx \ ": name " xxx \ "is reserved for " 9d423d30a81701807be0b8664a85380287b605ddd915c4fa8ae195801b25ba9e \ ""

Description
After my machine was powered on, all pods did not wake up and reported the error "failed to reserve sandbox name " xxxx \ ": name " xxx \ "is reserved for " 9d423d30a81701807be0b8664a85380287b605ddd915c4fa8ae195801b25ba9e \ ""
Note:My machine does not have a battery. It is powered on in 1970 and synchronizes time with the central server. This process may cause the pod to be recreated and report this error.
Steps to reproduce the issue
1.Power off and restart
Describe the results you received and expected
Power off and restart the pod to start normally.
What version of containerd are you using?
containerd github.com/containerd/containerd v1.7.20 8fc6bcff51318944179630522a095cc9dbf9f353
Any other relevant information
unc --version
runc version 1.1.13
commit: v1.1.13-0-g58aa9203-dirty
spec: 1.0.2-dev
go: go1.21.11
libseccomp: 2.5.5
uname -a:
Linux edgenode19 5.10.0 #41 SMP Mon Jan 29 10:09:59 CST 2024 aarch64 aarch64 aarch64 GNU/Linux
k8s:1.29.5
Show configuration if it is related to CRI plugin.
disabled_plugins = []
imports = []
oom_score = 0
plugin_dir = ""
required_plugins = []
root = "/var/lib/containerd"
state = "/run/containerd"
temp = ""
version = 2
[cgroup]
path = ""
[debug]
address = ""
format = ""
gid = 0
level = ""
uid = 0
[grpc]
address = "/run/containerd/containerd.sock"
gid = 0
max_recv_message_size = 16777216
max_send_message_size = 16777216
tcp_address = ""
tcp_tls_ca = ""
tcp_tls_cert = ""
tcp_tls_key = ""
uid = 0
[metrics]
address = ""
grpc_histogram = false
[plugins]
[plugins."io.containerd.gc.v1.scheduler"]
deletion_threshold = 0
mutation_threshold = 100
pause_threshold = 0.02
schedule_delay = "0s"
startup_delay = "100ms"
[plugins."io.containerd.grpc.v1.cri"]
cdi_spec_dirs = ["/etc/cdi", "/var/run/cdi"]
device_ownership_from_security_context = false
disable_apparmor = false
disable_cgroup = false
disable_hugetlb_controller = true
disable_proc_mount = false
disable_tcp_service = true
drain_exec_sync_io_timeout = "0s"
enable_cdi = false
enable_selinux = false
enable_tls_streaming = false
enable_unprivileged_icmp = false
enable_unprivileged_ports = false
ignore_deprecation_warnings = []
ignore_image_defined_volumes = false
image_pull_progress_timeout = "5m0s"
image_pull_with_sync_fs = false
max_concurrent_downloads = 3
max_container_log_line_size = 16384
netns_mounts_under_state_dir = false
restrict_oom_score_adj = false
sandbox_image = "registry.k8s.io/pause:3.9"
selinux_category_range = 1024
stats_collect_period = 10
stream_idle_timeout = "4h0m0s"
stream_server_address = "<IP_ADDRESS>"
stream_server_port = "0"
systemd_cgroup = false
tolerate_missing_hugetlb_controller = true
unset_seccomp_profile = ""
[plugins."io.containerd.grpc.v1.cri".cni]
  bin_dir = "/opt/cni/bin"
  conf_dir = "/etc/cni/net.d"
  conf_template = ""
  ip_pref = ""
  max_conf_num = 1
  setup_serially = false

[plugins."io.containerd.grpc.v1.cri".containerd]
  default_runtime_name = "runc"
  disable_snapshot_annotations = true
  discard_unpacked_layers = false
  ignore_blockio_not_enabled_errors = false
  ignore_rdt_not_enabled_errors = false
  no_pivot = false
  snapshotter = "overlayfs"

  [plugins."io.containerd.grpc.v1.cri".containerd.default_runtime]
    base_runtime_spec = ""
    cni_conf_dir = ""
    cni_max_conf_num = 0
    container_annotations = []
    pod_annotations = []
    privileged_without_host_devices = false
    privileged_without_host_devices_all_devices_allowed = false
    runtime_engine = ""
    runtime_path = ""
    runtime_root = ""
    runtime_type = ""
    sandbox_mode = ""
    snapshotter = ""

    [plugins."io.containerd.grpc.v1.cri".containerd.default_runtime.options]

  [plugins."io.containerd.grpc.v1.cri".containerd.runtimes]

    [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
      base_runtime_spec = ""
      cni_conf_dir = ""
      cni_max_conf_num = 0
      container_annotations = []
      pod_annotations = []
      privileged_without_host_devices = false
      privileged_without_host_devices_all_devices_allowed = false
      runtime_engine = ""
      runtime_path = ""
      runtime_root = ""
      runtime_type = "io.containerd.runc.v2"
      sandbox_mode = "podsandbox"
      snapshotter = ""

      [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]
        BinaryName = ""
        CriuImagePath = ""
        CriuPath = ""
        CriuWorkPath = ""
        IoGid = 0
        IoUid = 0
        NoNewKeyring = false
        NoPivotRoot = false
        Root = ""
        ShimCgroup = ""
        SystemdCgroup = false

  [plugins."io.containerd.grpc.v1.cri".containerd.untrusted_workload_runtime]
    base_runtime_spec = ""
    cni_conf_dir = ""
    cni_max_conf_num = 0
    container_annotations = []
    pod_annotations = []
    privileged_without_host_devices = false
    privileged_without_host_devices_all_devices_allowed = false
    runtime_engine = ""
    runtime_path = ""
    runtime_root = ""
    runtime_type = ""
    sandbox_mode = ""
    snapshotter = ""

    [plugins."io.containerd.grpc.v1.cri".containerd.untrusted_workload_runtime.options]

[plugins."io.containerd.grpc.v1.cri".image_decryption]
  key_model = "node"

[plugins."io.containerd.grpc.v1.cri".registry]
  config_path = ""

  [plugins."io.containerd.grpc.v1.cri".registry.auths]

  [plugins."io.containerd.grpc.v1.cri".registry.configs]

  [plugins."io.containerd.grpc.v1.cri".registry.headers]

  [plugins."io.containerd.grpc.v1.cri".registry.mirrors]

[plugins."io.containerd.grpc.v1.cri".x509_key_pair_streaming]
  tls_cert_file = ""
  tls_key_file = ""

[plugins."io.containerd.internal.v1.opt"]
path = "/opt/containerd"
[plugins."io.containerd.internal.v1.restart"]
interval = "10s"
[plugins."io.containerd.internal.v1.tracing"]
[plugins."io.containerd.metadata.v1.bolt"]
content_sharing_policy = "shared"
[plugins."io.containerd.monitor.v1.cgroups"]
no_prometheus = false
[plugins."io.containerd.nri.v1.nri"]
disable = true
disable_connections = false
plugin_config_path = "/etc/nri/conf.d"
plugin_path = "/opt/nri/plugins"
plugin_registration_timeout = "5s"
plugin_request_timeout = "2s"
socket_path = "/var/run/nri/nri.sock"
[plugins."io.containerd.runtime.v1.linux"]
no_shim = false
runtime = "runc"
runtime_root = ""
shim = "containerd-shim"
shim_debug = false
[plugins."io.containerd.runtime.v2.task"]
platforms = ["linux/arm64/v8"]
sched_core = false
[plugins."io.containerd.service.v1.diff-service"]
default = ["walking"]
[plugins."io.containerd.service.v1.tasks-service"]
blockio_config_file = ""
rdt_config_file = ""
[plugins."io.containerd.snapshotter.v1.aufs"]
root_path = ""
[plugins."io.containerd.snapshotter.v1.blockfile"]
fs_type = ""
mount_options = []
root_path = ""
scratch_file = ""
[plugins."io.containerd.snapshotter.v1.btrfs"]
root_path = ""
[plugins."io.containerd.snapshotter.v1.devmapper"]
async_remove = false
base_image_size = ""
discard_blocks = false
fs_options = ""
fs_type = ""
pool_name = ""
root_path = ""
[plugins."io.containerd.snapshotter.v1.native"]
root_path = ""
[plugins."io.containerd.snapshotter.v1.overlayfs"]
mount_options = []
root_path = ""
sync_remove = false
upperdir_label = false
[plugins."io.containerd.snapshotter.v1.zfs"]
root_path = ""
[plugins."io.containerd.tracing.processor.v1.otlp"]
[plugins."io.containerd.transfer.v1.local"]
config_path = ""
max_concurrent_downloads = 3
max_concurrent_uploaded_layers = 3
[[plugins."io.containerd.transfer.v1.local".unpack_config]]
  differ = ""
  platform = "linux/arm64/v8"
  snapshotter = "overlayfs"

[proxy_plugins]
[stream_processors]
[stream_processors."io.containerd.ocicrypt.decoder.v1.tar"]
accepts = ["application/vnd.oci.image.layer.v1.tar+encrypted"]
args = ["--decryption-keys-path", "/etc/containerd/ocicrypt/keys"]
env = ["OCICRYPT_KEYPROVIDER_CONFIG=/etc/containerd/ocicrypt/ocicrypt_keyprovider.conf"]
path = "ctd-decoder"
returns = "application/vnd.oci.image.layer.v1.tar"
[stream_processors."io.containerd.ocicrypt.decoder.v1.tar.gzip"]
accepts = ["application/vnd.oci.image.layer.v1.tar+gzip+encrypted"]
args = ["--decryption-keys-path", "/etc/containerd/ocicrypt/keys"]
env = ["OCICRYPT_KEYPROVIDER_CONFIG=/etc/containerd/ocicrypt/ocicrypt_keyprovider.conf"]
path = "ctd-decoder"
returns = "application/vnd.oci.image.layer.v1.tar+gzip"
[timeouts]
"io.containerd.timeout.bolt.open" = "0s"
"io.containerd.timeout.metrics.shimstats" = "2s"
"io.containerd.timeout.shim.cleanup" = "5s"
"io.containerd.timeout.shim.load" = "5s"
"io.containerd.timeout.shim.shutdown" = "3s"
"io.containerd.timeout.task.state" = "2s"
[ttrpc]
address = ""
gid = 0
uid = 0

maybe image is broken because of unexpected poweroff .try https://github.com/containerd/containerd/pull/10284 or https://github.com/containerd/containerd/pull/9401 to enable sync.

maybe image is broken because of unexpected poweroff .try #10284 or #9401 to enable sync.

This has nothing to do with the image, right? The error is: "failed to reserve sandbox name"：

similar:
https://github.com/containerd/containerd/issues/9459


Version 1.3.0-alpha breaks backwards-compatibility

Hello,
Without the variable USE_NET8_ARTIFACTS_CREDENTIAL_PROVIDER set to false, using the credprovider for old dotnet versions is likely to fail.
Dotnet 6 image build
Console output (azure pipelines)
##[error]#12 [build 3/6] RUN curl -sSL https://raw.githubusercontent.com/microsoft/artifacts-credprovider/master/helpers/installcredprovider.sh | bash
##[error]#12 0.270 INFO: Creating the nuget plugin directory (i.e. /root/.nuget/plugins).
##[error]#12 0.272 Downloading from https://github.com/Microsoft/artifacts-credprovider/releases/latest/download/Microsoft.Net8.NuGet.CredentialProvider.tar.gz
##[error]#12 0.611 tar: invalid magic
##[error]#12 0.611 tar: short read
##[error]#12 0.611 tar: plugins/netcore: not found in archive
##[error]#12 ERROR: process "/bin/bash -eo pipefail -c curl -sSL https://raw.githubusercontent.com/microsoft/artifacts-credprovider/master/helpers/installcredprovider.sh | bash" did not complete successfully: exit code: 1

Docker image
FROM mcr.microsoft.com/dotnet/sdk:6.0-alpine3.16 AS build

# Install Bash
# hadolint ignore=DL3018
RUN set -eu \
    && apk add --no-cache --update bash curl

# Install Credential Provider and set env variables to enable Nuget restore with auth
ARG PAT
ARG NUGET_ENDPOINT="https://pkgs.dev.azure.com/xxx"
ARG \
  USE_NET6_ARTIFACTS_CREDENTIAL_PROVIDER="false"

SHELL ["/bin/bash", "-eo", "pipefail", "-c"]
# hadolint ignore=SC2016
RUN curl -sSL https://raw.githubusercontent.com/microsoft/artifacts-credprovider/master/helpers/installcredprovider.sh | bash
ENV NUGET_CREDENTIALPROVIDER_SESSIONTOKENCACHE_ENABLED=true
ENV VSS_NUGET_EXTERNAL_FEED_ENDPOINTS='{"endpointCredentials": [{"endpoint":"'${NUGET_ENDPOINT}'", "password":"'${PAT}'"}]}'

Dotnet 3.1 image build
Console output (azure pipelines)
##[error]#13 [build 3/7] RUN curl -sSL https://raw.githubusercontent.com/Microsoft/artifacts-credprovider/master/helpers/installcredprovider.sh | bash
##[error]#13 0.320 INFO: Creating the nuget plugin directory (i.e. /root/.nuget/plugins).
##[error]#13 0.322 Downloading from https://github.com/Microsoft/artifacts-credprovider/releases/latest/download/Microsoft.Net8.NuGet.CredentialProvider.tar.gz
##[error]#13 0.670 tar: invalid magic
##[error]#13 0.670 tar: short read
##[error]#13 0.671 tar: plugins/netcore: not found in archive
##[error]#13 ERROR: process "/bin/bash -eo pipefail -c curl -sSL https://raw.githubusercontent.com/Microsoft/artifacts-credprovider/master/helpers/installcredprovider.sh | bash" did not complete successfully: exit code: 1
##[error]------
##[error] > [build 3/7] RUN curl -sSL https://raw.githubusercontent.com/Microsoft/artifacts-credprovider/master/helpers/installcredprovider.sh | bash:
##[error]0.320 INFO: Creating the nuget plugin directory (i.e. /root/.nuget/plugins).
##[error]0.322 Downloading from https://github.com/Microsoft/artifacts-credprovider/releases/latest/download/Microsoft.Net8.NuGet.CredentialProvider.tar.gz
##[error]0.670 tar: invalid magic
##[error]0.670 tar: short read
##[error]0.671 tar: plugins/netcore: not found in archive

Dockerfile
FROM mcr.microsoft.com/dotnet/core/sdk:3.1-alpine3.10 AS build

RUN set -eu \
    && apk add --no-cache --update bash~=5.0 curl~=7.66

# Install Credential Provider and set env variables to enable Nuget restore with auth
ARG PAT
ARG NUGET_ENDPOINT="https://pkgs.dev.azure.com/xxx"
ARG USE_NET6_ARTIFACTS_CREDENTIAL_PROVIDER="false"

SHELL ["/bin/bash", "-eo", "pipefail", "-c"]
RUN curl -sSL https://raw.githubusercontent.com/Microsoft/artifacts-credprovider/master/helpers/installcredprovider.sh | bash
ENV NUGET_CREDENTIALPROVIDER_SESSIONTOKENCACHE_ENABLED true
ENV VSS_NUGET_EXTERNAL_FEED_ENDPOINTS '{"endpointCredentials": [{"endpoint":"'${NUGET_ENDPOINT}'", "password":"'${PAT}'"}]}'

The issue here is that the shortened URL https://aka.ms/install-artifacts-credprovider.sh is pointing to the master branch of this repo, which is currently an alpha version.
Maybe it would be possible to have a separate channel or a separate URL for alpha versions of the cred provider ?
Thanks !

Linked to #525.

What was happening for me, when using:
ENV USE_NET6_ARTIFACTS_CREDENTIAL_PROVIDER false
In the dockerfile, is that it was looking for:
https://github.com/Microsoft/artifacts-credprovider/releases/download/v1.2.3/Microsoft.Net8.NuGet.CredentialProvider.tar.gz
Which doesnt exist in 1.2.3 version anymore.
I have had to specify the alpha build using:
ENV AZURE_ARTIFACTS_CREDENTIAL_PROVIDER_VERSION=v1.3.0-alpha

Should be resolved when #528 is merged. Sorry for the inconvenience everyone, we have some follow up items from this to make our CI validation better for these install scripts - I'll also bring up the idea of "pre-release" install scripts for folks who want to test changes early.

Please let me know if you're still facing any failures with the changes from #528 or mark the issue as resolved if it's no longer occurring.


Text does not support HTML formatting

It would be good for openAlertDialog and openConfirmDialog to explicitly call out the fact that text does not support any formatting (html tags as well as \n, which was supported by the old Xrm.Utility.alertdialog), as this will help people as they move from using the old deprecated method to these new methods. Also, it might be worth calling out why its not supported (I am guessing to prevent injection of malicious code).

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 04410a08-16f5-c176-181c-3cad4a9e0f55
Version Independent ID: b67ad3ae-d413-9e50-affd-916c39b62b2d
Content: openAlertDialog (Client API reference) in Dynamics 365 for Customer Engagement
Content Source: ce/developer/clientapi/reference/Xrm-Navigation/openAlertDialog.md
Service: crm-online
GitHub Login: @KumarVivek
Microsoft Alias: kvivek

Chrome 73.0.3683.103

If I increase the window's width then the text box size is not increasing.
I'm missing the text auto wrap here, cause we have a horizontal slider now
If I reduce back the width and if I add new line to the text then the formatting looks weird, just like for @rajrao , the second is more to the left then the 1st line
Or sometimes it looks like this with the new line:

Or looks competly weird:

Original starting text was: "DEV TESZT: "
And as you see it changed to: ": DEV TESZT"

\n not working for me on Chrome.
My Version is Version 1612 (<IP_ADDRESS>) (DB <IP_ADDRESS>)


NugetPackage Warning message incorrect

See:
https://github.com/PowerShell/PackageManagementProviderResource/blob/master/DSCResources/MSFT_NugetPackage/MSFT_NugetPackage.psm1#L414
The order of the parameters are incorrect so a message like this can be recevied:
You are installing the module 'Git-Trusted-Certificates' from an untrusted repository 'Trusted'. Your current InstallationPolicy is
'https://nexus.contoso.com/nexus/service/local/nuget/nuget-hosted/'. If you trust the repository, set the policy to "Trusted". "Untrusted" otherwise.
Line 414 should be:
Write-Warning -Message  ($localizedData.InstallationPolicyWarning -f $Name, $packageFound.Source, $InstallationPolicy)

This issue was moved to OneGet/oneget#254


fix [#17252]: Add Linux Toolchain location for 64bit installations

This fix adds the Linux toolchain location for 64bit installations.

@DJViking thanks for the PR. I've rebased this on our release branch so we can make it into 7.1 - replaced this PR with #17289


PENV-383: api tests get jd by pulse

- What I did
implement integration tests for endpoint /pulses/{pulse-number}/jetdrops
- How I did it
- How to verify it
- Description for the changelog

Codecov Report

Merging #78 into master will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #78      +/-   ##
==========================================
+ Coverage   75.01%   75.05%   +0.03%
==========================================
  Files          43       43
  Lines        2774     2778       +4
==========================================
+ Hits         2081     2085       +4
  Misses        555      555
  Partials      138      138

Impacted Files
Coverage Δ

test/api/apiwrapper.go
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


[[FLINK-26031] Support projection pushdown on keys and values in sst file readers

Projection pushdown is an optimization for sources. With this optimization, we can avoid reading useless columns and thus improve performance.
This PR is waiting for #16 and #17 and https://github.com/apache/flink/pull/18657. Please review the last commit only.

If we provide projection on keys:

Does DeduplicateAccumulator work? Should we check it?
a,b,c -> a,b: Does SortMergeReader work? Since one file iterator will produce more than one records per key.
a,b,c -> b,c: Does SortMergeReader work? Since it uses PriorityQueue?


api 6.5: request_user and request_chat keyboard buttons

https://core.telegram.org/bots/api#keyboardbuttonrequestchat is missing

Closes #603

https://github.com/tucnak/telebot/commit/78610849e172ba8c6462cba6c4ff1224cd36819f


icewm: 3.5.0 -> 3.5.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ice-wm/icewm/releases.
meta.description for icewm is: A simple, lightweight X window manager
meta.homepage for icewm is: https://ice-wm.org/
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.5.1 with grep in /nix/store/fkdx6gr7y9di3j8gpa5k9d9ak8l2cphf-icewm-3.5.1
found 3.5.1 in filename of file in /nix/store/fkdx6gr7y9di3j8gpa5k9d9ak8l2cphf-icewm-3.5.1

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

icewm

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/fkdx6gr7y9di3j8gpa5k9d9ak8l2cphf-icewm-3.5.1 \
  --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 icewm https://github.com/r-ryantm/nixpkgs/archive/4ca55358d81873b9b268e268f85c768985ee69b0.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/4ca55358d81873b9b268e268f85c768985ee69b0#icewm

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/fkdx6gr7y9di3j8gpa5k9d9ak8l2cphf-icewm-3.5.1
ls -la /nix/store/fkdx6gr7y9di3j8gpa5k9d9ak8l2cphf-icewm-3.5.1/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 --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

icewm

Maintainer pings
cc @AndersonTorres for testing.

@NixOS/nixpkgs-merge-bot merge


[Identity] Merging changes from Hotfix/identity 3.1.3 into main

Packages impacted by this PR
@azure/identity

API change check
API changes are not detected in this pull request.


Update and rename 0000-01-01-intro.md to 0000-01-01-nathanfrees.md

Change name
Change line 5 text

Changes


Fixed social button to show 'unspecified' for default contact method.

Description
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] 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 not work as expected)
[ ] This change requires a documentation update

Change Status

[x] Complete, tested, ready to review and merge
[ ] Complete, but not tested (may need new tests)
[ ] Incomplete/work-in-progress, PR is for discussion/feedback

How Has This Been Tested?

[x] Test A - Ran application in simulator to verify "unspecified" appears instead of @@swaapApp
[ ] Test B

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My code has been reviewed by at least one peer
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] There are no merge conflicts

 Fix preferred contact to not say @@swaapApp if user has not set preferred contact


Can't use with npm 8 and react 17

When I try to install in a react 17 project and npm 8, I get this:
npm ERR! While resolving:
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/use-route-as-state
npm ERR<EMAIL_ADDRESS>from the root project

I assume this is because peerDependencies in package.json still lists ^16.0.0 as the react dependency. I have to install with ---legacy-peer-deps to get it to install. Any chance we can get that fixed?

Sorry for the late answer, I'm moving my apartment. I guess it can be easy to fix, but I need to understand the change of peerDependencies from npm 6 to npm7,8.
If you can take it I will very thank you!
I hope I will get it next week.

@zwily Sorry my late, I think it's working now, with v5.2.1.


Tooltip does not get the theme via styled-components ThemeProvider

components: Tooltip
reactstrap version latest
import method umd/csj/es
react version #16.13.1
bootstrap version latest

What is happening?
styled-components expose a ThemeProvider component which can be wrapped around the app to expose the theme in the React app's styled-components. But using Tooltips does not seem to get this theme prop, possibly due to not using Portals inside.
What should be happening?
The theme prop should be accessible inside the Tooltip component
Steps to reproduce issue

create a styled-component inside a tooltip
wrap your app under ThemeProvider
Now try to access the theme prop in the styled-components inside the tooltip

Hey, I tried your use case but cannot seem to find the bug. I also checked the code for the tooltip and it seems to be using ReactDOM.createPortal.
https://github.com/reactstrap/reactstrap/blob/master/src/PopperContent.js#L171
This is how I tried reproducing the issue: https://codesandbox.io/s/misty-moon-z1y1y?file=/src/App.tsx

Hi,
Seems like I had been testing on v6.4.0. Bumping up the version seems to resolve the issue, as used in the codesandbox link given above.
@koenvg Are there any breaking changes for tooltips from v6.4.0 to 8.6.0?


Default to using new build pipeline

Use the new build pipeline when creating apps on supported node versions.

@fiveisprime It seems like this happens by default.  Is there any work that needs to be done for this?


Register to render loop

Hello,
there is a way to register to a renderloop without actually using RenderLoop.Run?
What i want is a controllated render loop(V-Sync working) and a callback to "Draw" in my form to notify me when to draw.

Use RenderLoop.NextFrame and you can handle your loop on your own, that's what RenderLoop.Run is doing:
https://github.com/sharpdx/SharpDX/blob/bdb12ec420d2b6ff32da184453c722380596ceb8/Source/SharpDX.Desktop/RenderLoop.cs#L206-L219


Add .py as text to gitattributes.

Missed this in the prior PR. Part of issue #55.

No code changes here.

I just noticed there is a typo in the first line of this file:
# .gitarttributes instead of # .gitattributes


Update plugins.md

Fixed grammar & capitalization errors on line #3803 to "not required by all Leaflet users" from "not required by all of Leaflet users" and to "JavaScript" from "javascript".

:+1:


Fix GLYPH_NOTFOUND_CHAR_FALLBACK index value

Currently if codepoint is not found; '_' character is returned. (Supposed to be '?')
It's fixed by using index value of fallback character instead of using the character value.

@hanaxar Actually, checking the code, this fix could neither work as expected. If the charset is unordered, the ? codepoint must be fetched, it could not be in position - 32, because it's unordered.
So, the function is wrong and it needs a redesign, just pushing a review myself


Unix sockets' support

Discussion: http://forum.rejectedsoftware.com/groups/rejectedsoftware.vibed/thread/10870/
I have a WIP branch https://github.com/nazriel/vibe.d/commits/unix_sockets related to this (source/vibe/web/web.d  change is unrelated, sorry)
But I am not sure if I am going towards right direction API wise etc.
@s-ludwig could you look at this please?
Thanks!

First of all, let me say I hate the kinda +1, or "bump" posts, but this is one of that kind :/
@s-ludwig Sorry to bothering you, but there has been some progress about that stuff?
I tried searching over the code to see if there was something fairly implemented, but have given up without success.
This option would be extremely interesting, because the projects would easily coexist with existing ones on our machines, besides the improvement would involve.

First of all, let me say I hate the kinda +1, or "bump" posts, but this is one of that kind :/

I am using it to talk to the docker daemon. It only works with libevent, but that is ok for me.

very nice

Is it possible to use listenUDP() with a unix socket? Or is it tcp+http only?

only connectTCP. But it would be trivial to implement. On the other hand you could wait for @s-ludwig to rewrite vibe, I bet its gonna support it.

Should be possible for the 0.8.0-beta version with the vibe-core configuration for vibe-d:core. At least it's auto tested for the underlying eventcore library, just not yet in the vibe.d context.

The functionality seems to be in Phobos - does vibe.d wrap the same stuff?

No, vibe.d goes directly down to the OS APIs to avoid the overhead of the class based std.socket module where possible.

@s-ludwig performance. always nice.  Will try beta out.  Just to confirm, listenUDP() should be possible with it?

Hm, I just noticed that I forgot to merge the USDS related changes to NetworkAddress. Once that is done, listenUDP with a USDS NetworkAddress should work (the function will be renamed to listenDatagram later on).

According to https://github.com/vibe-d/vibe.d/pull/1342#issuecomment-321856809 this is fixed and should be closed.


rename global_pre_comps

@michaeldeistler you can have a look at it, but I guess there is not much to see. If tests pass, I will just merge it. Hope that is fine :)

missed a few replaces -.-, now it should pass


TI/RS Delivery Loop

Bug
Describe the Bug
When connecting ReportStream and the TI service locally, a delivery loop occurs.
See branches:

https://github.com/CDCgov/trusted-intermediary/tree/rs-form-data
https://github.com/CDCgov/prime-reportstream/tree/john-etor-demo

Also see all the messages from Aug 4th in https://flexion.slack.com/archives/C04FT9U8MPB/p1691135600671569
Impact
The PHL would be unable to use our service for order delivery.
To Reproduce

Submit an ORM order to ReportStream locally
OML files in the SFTP folder continue to be created every minute or two

Expected Behavior
The OML order should only appear once in the SFTP folder.
Screenshots
n/a
Logs
n/a
Version
See above
Additional Context
none

This is complete given the merge of https://github.com/CDCgov/prime-reportstream/pull/10979


NLP diagram

https://insights.ai-jobs.net/the-past-and-the-present-of-natural-language-generation/


Upgrade selenium

The requirements.txt file currently specifies selenium==2.53.6, which is three years old. Moreover, this repository is installed last in https://hub.docker.com/r/freelawproject/courtlistener-django, so this version is what that container image ultimately ends up using.

Am I to understand that fixing this is key to fixing the CL bugs because of some install-order thing?

I haven't identified any issues caused by this old version (other than Firefox/GeckoDriver compatibility) but it is being used in that image due to the order in which projects are installed, and because packages are being installed system-wide.


serbian translation has mistakes in some places

title is sufficient

If you are able to, please help us by contributing changed to the translations.
How to open/What is a PR: https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests

I dont speak serbian but if you add a comment saying where you have found mistakes and what the correct translation is I would be happy to add those fixes to the translation.

I already made a pull request and fixed it

As this is fixed I'll close the issue


Offsetting map tile locations

I have a map based on the OSGB coordinate system for a single city which I would like to display as an overlay on a MapSui map. The map tiles do not sit on a MBtiles tile boundary so I'm wondering if there is a way to offset the coordinates to allow the tiles to align with the MBtiles map.
Is this possible in MapSui or would the tiles have to be realigned somehow before display?

So, the overlay is not positioned correctly? Could you show a screenshot?
There are number of ways to fix this.
The best way would be to fix your mbtiles dataset. The mbtiles file should contain metadata wrt it's positioning. In BruTile this is called the TileSchema. When this data is missing it is assumed it is the most common 'whole world' schema.
An alternative is to specify the schema in code. In the code below I took part of the MBTilesOverlaySample and added a custom schema.

        public static TileLayer CreateMbTilesLayer(string path)
        {
            var customSchema = new TileSchema();
            // todo: initialize schema
            var mbTilesTileSource = new MbTilesTileSource(new SQLiteConnectionString(path, true), customSchema);
            var mbTilesLayer = new TileLayer(mbTilesTileSource);
            return mbTilesLayer;
        }

Now the question is, what is the correct schema? That is not possible for me to know. It should be known to the person who created the schema. Perhaps you could start off with a copy of BruTile's GlobalSphericalMercator schema (the whole world) and then modify some of it's parameters. Perhaps only the offset needs to be changed.
https://github.com/BruTile/BruTile/blob/master/BruTile/Predefined/GlobalSphericalMercator.cs

Thanks, I will get a screenshot tomorrow.
I think the issue is the schema having been looking at the source over the last few hours. It is using the whole world schema and so the tile bounds of my map do not sit on the tile bounds of the whole world "grid" (i.e. they don't match the rows/cols exactly) which is causing an offset.
So, what would be the solution to a map for example, based on bounds os OSGB (400000, 1200000) to (500000, 1300000). I would like to both display this map tileset correctly as well as restrict the view to just those tiles. I believe the latter is achieved with a ViewportLimiter which I'm looking into now but I'm not clear on how I would display the map correctly in the first place.
I'm not an expert at mapping (as you can probably tell). Do I need to convert my coordinates to lat/lng and  then produce a custom schema to restrict to those coordinates?

MBTiles positioning and ViewportLimiter are separate problems. Let's first get the positioning right.
Using whole schema would not be a problem if the data in your mbtiles file would be correct. The MBTiles file is an ordinary sqlite file. Please use a tool like DB Browser for sqlite to inspect your data. You can also read a bit about the MBTiles specification.
You can read a bit about projections here:
https://mapsui.com/documentation/projections.html

Thanks, I've actually read both of those and already using DB Browser. I guess I must be missing something in my knowledge to answer this question.
Using the Tile Map Service Specification my map tiles does not land on a tile boundary which I believe is the cause of the offset. So, at what point does this need to be adjusted? Do I need to somehow reposition the map tiles themselves before creating the SQLite DB? Or would this be something that can be adjusted via metadata (can't find anything that suggests it can be). Or could this be adjusted via a projection or schema at the Mapsui level?
Sorry if this is a simple question but I'm not from a mapping background and I'm not sure exactly where I need to be focussing to resolve this problem.

my map tiles does not land on a tile boundary which I believe is the cause of the offset

The tile schema of the overlay does not have to match the base layer tile schema in any way. It can have a different tiles size, different offset and even different resolutions. Mapsui has no limitations in this respect. But you do need to the set the correct schema somehow.
One hard constraint is that your tileset does need to be in the same coordinate system (projection). Mapsui can not reproject tiles and most of the time you do not want to reproject.

Do I need to somehow reposition the map tiles themselves before creating the SQLite DB

Well te schema needs to be correct. I understand this is not a very helpful answer but it is hard to answer this question without any knowledge of the data. How did you generate the mbtiles, where did you get it from?

I think I need to take a step back and go back to basics on this as I may be mistaken as to what's causing the offset. Thanks for the clarification.
Is there any documentation on creating a schema?

Actually I expect you do not need to tweak the TileSchema in code. The tool you use to generate the tile schema should help you to generate the right schema. Perhaps there was something wrong with the parameters you choose.
A possible cause is the coordinate system, or projections. This is defined in an EPSG code. The coordinate system of the openstreetmap background map is called SphericalMercator and it in EPSG:3857. Your tileset should be generated in that same projection.

The tile set was created using a script I wrote to split the larger tiles into smaller JPGs and generate an MBTiles file. I've attempted to use the EPSG:3857 projection but that's where the offset issue comes from. I'm now trying to use the OSGB (EPSG:27700) projection directly and I've created a separate issue for that. I'm hoping one way or another there is a solution to this.


Working Tests

This should fix the broken tests as demonstrated https://github.com/MHKiT-Software/MHKiT-Python/pull/216

The old versions of these files still remain in this commit. We can add wind_toolkit.py and hindcast.py to mhkit.wave.io.hindcast, but they should also be removed from mhkit.wave.io. This then causes some issues with the tests because all the paths need to change. I'm working to update the paths in the tests and all of the import calls to get this running correctly


Azure Search python sdk returns "Operation returned an invalid status 'Partial Content'"

Package Name: azure-search-documents
Package Version: 11.6.0b1, 11.4.0b11
Operating System: Windows 11
Python Version: 3.11
Describe t he bug
A clear and concise description of what the bug is.
When trying to enumerate results returned from search client using "async for .by_page()" the sdk raises an error "Operation returned an invalid status 'Partial Content'".
To Reproduce
Steps to reproduce the behavior:
Just try to enumerate search results of async search client using by_page().
Expected behavior
The results should enumerate.
Additional context
This was already working code deployed to server and in production. It has retroactively stopped working. I haven't faced an issue from Microsoft sdks yet where already working code was retroactively broken. It broke on Friday too! Clients are raising tickets.
Related issue (Which was closed):
https://github.com/Azure/azure-sdk-for-python/issues/35575
Error Logs:
---------------------------------------------------------------------------
HttpResponseError                         Traceback (most recent call last)
Cell In[239], line 1
----> 1 async for page in results.by_page():
      2     print(page)
      3     async for document in page:

File [D:\Dev Env\Dev Env](file:///D:/Dev Env/Dev Env)Dev Env\scripts\.venv\Lib\site-packages\azure\core\async_paging.py:94, in AsyncPageIterator.__anext__(self)
     92     raise StopAsyncIteration("End of paging")
     93 try:
---> 94     self._response = await self._get_next(self.continuation_token)
     95 except AzureError as error:
     96     if not error.continuation_token:

File [D:\Dev Env\Dev Env](file:///D:/Dev Env/Dev Env)Dev Env\scripts\.venv\Lib\site-packages\azure\search\documents\aio\_paging.py:108, in AsyncSearchPageIterator._get_next_cb(self, continuation_token)
    106 async def _get_next_cb(self, continuation_token):
    107     if continuation_token is None:
--> 108         return await self._client.documents.search_post(search_request=self._initial_query.request, **self._kwargs)
    110     _next_link, next_page_request = unpack_continuation_token(continuation_token)
    112     return await self._client.documents.search_post(search_request=next_page_request, **self._kwargs)

File [D:\Dev Env\Dev Env](file:///D:/Dev Env/Dev Env)Dev Env\scripts\.venv\Lib\site-packages\azure\core\tracing\decorator_async.py:77, in distributed_trace_async.<locals>.decorator.<locals>.wrapper_use_tracer(*args, **kwargs)
     75 span_impl_type = settings.tracing_implementation()
     76 if span_impl_type is None:
---> 77     return await func(*args, **kwargs)
     79 # Merge span is parameter is set, but only if no explicit parent are passed
     80 if merge_span and not passed_in_parent:

File [D:\Dev Env\Dev Env](file:///D:/Dev Env/Dev Env)Dev Env\scripts\.venv\Lib\site-packages\azure\search\documents\_generated\aio\operations\_documents_operations.py:417, in DocumentsOperations.search_post(self, search_request, request_options, **kwargs)
    415     map_error(status_code=response.status_code, response=response, error_map=error_map)
    416     error = self._deserialize.failsafe_deserialize(_models.SearchError, pipeline_response)
--> 417     raise HttpResponseError(response=response, model=error)
    419 deserialized = self._deserialize("SearchDocumentsResult", pipeline_response)
    421 if cls:

HttpResponseError: Operation returned an invalid status 'Partial Content'

@xiangyan99
results = await search_client.search(
                    search_text=query_text,
                    filter=_filter,
                    query_type=QueryType.SEMANTIC,
                    query_language="en-us",
                    scoring_profile=None,
                    query_speller="lexicon",
                    semantic_configuration_name="default",
                    top=top,
                    query_caption="extractive|highlight-false" if use_semantic_captions else None,
                    vector_queries=vec,
                )

Only happening when I'm passing the query_type as Semantic.

@ShivangiReja  @joseharriaga @jairmyree @dgetu @weidongxu-microsoft

I'm also having this same issue with azure-search-documents==11.4.0.

I am having the issue even when running the semantic reranker tutorial notebook https://github.com/Azure-Samples/azure-search-python-samples/blob/main/Quickstart-Semantic-Search/semantic-search-quickstart.ipynb
Error is: HttpResponseError: Operation returned an invalid status 'Partial Content'

I'm encountering the same error. Currently, I've had to temporarily switch the query type to QueryType.FULL to bypass this issue, but it's resulting in lower relevance in retrievals. It seems to be a widespread problem, affecting Azure AI Playground as well. It appears to be related to a resource issue on Azure.

Yes, I've done changed the query type and that works, but the results are really bad. Hoping this is fixed soon.

This is a critical bug to resolve. Can it be esclated.

Please try raising a support request in Azure too.

Azure responded to the ticket I opened earlier this morning. They mentioned that this behavior is occurring due to an outage issue, and they are currently collaborating with the engineering team to resolve it.

Thanks for reporting the issue.
This is a service issue and please use https://azure.microsoft.com/support/create-ticket to open support ticket for help.


Index creation via REST API does not apply passed-in options

(reported by user)
Looks like options Map passed via POST to /v2/schemas/keyspaces/{keyspaceName}/tables/{tableName}/indexes (and payload bound as Sgv2IndexAddRequest) is somehow not being used for index creation.
It is not yet clear where information is dropped: integration test that tries to pass unrecognized options does not fail; options make their way to REST API handler at least, and are used for Query creation for request to Bridge.
Original report showed expected matching CQL:
create CUSTOM INDEX on route (race_name)
  USING 'org.apache.cassandra.index.sai.StorageAttachedIndex' WITH OPTIONS = { 'case_sensitive': 'false'};

for REST payload of:
{
 "column": "race_name",
 "options":
  {
   "case_sensitive": "false"
  }
}

Looks like the issue is that QueryBuilder will only add options (customIndexOptions) if customIndexClass is non-null:
    if (customIndexClass != null) {
      query.append(" USING").append(String.format(" '%s'", customIndexClass));
      if (customIndexOptions != null && !customIndexOptions.isEmpty()) {
        query.append(
            customIndexOptions.entrySet().stream()
                .map(e -> String.format("'%s': '%s'", e.getKey(), e.getValue()))
                .collect(Collectors.joining(", ", " WITH OPTIONS = { ", " }")));
      }
    }

so probably need to pass explicit customIndexClass to make sure options are added as expected.

Fixed via #2822, closing.


Nov 2019

Description of Changes:

How This Was Tested:

Related Issue(s) or Specifications:

Checklist:

[ ] Code follows code style of this project
[ ] Tests added to cover changes
[ ] All new and existing tests passing

Questions / Additional Notes:

@shrubin2 - please fill out the PR description so I know what your trying to do, how you tested it, and any links to designs! That'll help me review this.
Additionally, CI is failing :grimacing:


⚠ Bofrost.es has degraded performance

In cdd3399, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1726 ms

Resolved: Bofrost.es performance has improved in 631f8d1.


Fixing profiling and comparing profiling implementations

Description
The issue #224 discusses a couple of ways to rethink when and how profiling is run. This PR implements two ways, so we can see how they pan out in parallel.

Updates the profiling workflow that runs on pushes to develop (so after a PR is merged) to correct a couple of minor structural issues and add a pull request to update the stats. The current implementation simply tries to push to develop but that isn't allowed.

Adds a parallel implementation that (should) only run when a PR is reviewed and approved. This one then commits the updated files to the PR. I think we'll need to add the new action to the list of tests needed to merge.

So:
pyrealm_profiling_after_push.yaml: An approved PR is merged, the profiling and benchmarking runs and a second PR is created to add the updates (hopefully with a warning on failed tests).
👍 Only runs once.
👎 Requires an extra PR, failing code is now in develop.
👎 🤯  Oh god, and I suppose it is going to start of another profiling run when it gets merged, which will... etc etc.
pyrealm_profiling_on_approve.yaml: An approved PR is merged, the profiling and benchmarking runs and a second PR is created to add the updates (hopefully with a warning on failed tests).
👍 Stops failing code making it into develop without fixing/justification, single PR.
👎 Might run several times.
Fixes #224 (maybe)
Type of change

[x] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[x] Bug fix (non-breaking change which fixes an issue)

Key checklist

[ ] Make sure you've run the pre-commit checks: $ pre-commit run -a
[ ] All tests pass: $ poetry run pytest

Further checks

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works

pre-commit.ci run

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 95.23%. Comparing base (aef5907) to head (bf7c62e).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #225   +/-   ##
========================================
  Coverage    95.23%   95.23%
========================================
  Files           28       28
  Lines         1701     1701
========================================
  Hits          1620     1620
  Misses          81       81

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@AmyOctoCat - the on approval profiling script was broken so it failed its own test when you approved it. Can you reapprove so we can see if that is now fixed.

@AmyOctoCat I wondered if something like that was needed, or maybe this: https://stackoverflow.com/a/71367604

@AmyOctoCat I wondered if something like that was needed, or maybe this: https://stackoverflow.com/a/71367604

Sorry David, only just noticed your comment, that looks like it should do the job. I'm hoping the last commit I pushed achieves something similar, but if it doesn't work, that'll be next port of call...

It ran!

That worked! I'm not sure what happens with the actions here - I've seen this before and things just seem to hang for some reason.


AlphaMask of Body / Bra / Inner

Is it possible that the AlphaMask of Body / Bra / Inner could be used just as in KK Blender Porter Pack, so that for example two body textures are used at the end, the normal which always comes out at the end and one that had used the AlphaMask to color certain areas of the texture black and thus in MMD are transparent.
The normal one is then used as a morph and the one with missing areas as a standard texture, So no texture stings above the other, which often happens in MMD, because the figure moves and so steep of the body as an example then still pierce.
As an example of KK Blender Porter Pack
The default texture with Opaque 1:

The morph texture with Opaque 0:

This has been resolved with version 3.0.0.


fix: globalProperties not ShallowUnwrapRef on the template

fix #954
This will shallow unwrap the __VLS_ctx type

Hi @pikax, I think you should add ShallowUnwrapRef to https://github.com/vuejs/core/blob/cea82cffa3963d6d7f82f490ba0dba50a1d202db/packages/runtime-core/src/componentPublicInstance.ts#L206 instead of here. Otherwise it only works for volar but not works for webstorm.


Cannot save best model

Hi author,
When i finished the training process, i met the following issue. I used the python==3.9, torch==2.0.0+cu118, torchaudio==2.0.1+cu118, and pytorch-lightning==2.0.4. How can i sovle it?

You need use the basemodel
https://github.com/JusperLee/TDANet/blob/main/look2hear/models/base_model.py

I solved the problem followed your suggestion, tks!


Rendering produces noisy rendering with even simple materials. Image comparison between blender and maya.

I set up a simple scene to test stuff out. Here's what I got:
Blender:

Here's a similar render made in Maya:

Do you have the same settings and materials in both scenes?  What are your sampling settings?  Are you using the same lights?
Both the blender addon and RenderMan for Maya use the same RenderMan on the backend, if your scene is set up the same they should come out similarly.  However the defaults may be different.

I'm going to close this issue, it's probably better handled on the forum:
https://renderman.pixar.com/forum/forumdisplay.php?s=&forumid=166


JSON encoding problems.

The bot is crashing when calling the method set_user_info() from db.py
Traceback (most recent call last):
  File "./src/run.py", line 9, in <module>
    init.init()
  File "/home/karma-farm-reddit/src/init.py", line 63, in init
    set_user_info()
  File "/home/karma-farm-reddit/src/db.py", line 41, in set_user_info
    db_config.upsert({"config": "user", "value": j}, Config.config == "user")
  File "/home/karma-farm-reddit/venv/lib/python3.7/site-packages/tinydb/table.py", line 393, in upsert
    updated_docs = self.update(document, cond)
  File "/home/karma-farm-reddit/venv/lib/python3.7/site-packages/tinydb/table.py", line 358, in update
    self._update_table(updater)
  File "/home/karma-farm-reddit/venv/lib/python3.7/site-packages/tinydb/table.py", line 605, in _update_table
    tables = self._storage.read()
  File "/home/karma-farm-reddit/venv/lib/python3.7/site-packages/tinydb/storages.py", line 120, in read
    return json.load(self._handle)
  File "/usr/lib/python3.7/json/__init__.py", line 296, in load
    parse_constant=parse_constant, object_pairs_hook=object_pairs_hook, **kw)
  File "/usr/lib/python3.7/json/__init__.py", line 348, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python3.7/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python3.7/json/decoder.py", line 353, in raw_decode
    obj, end = self.scan_once(s, idx)
json.decoder.JSONDecodeError: Expecting property name enclosed in double quotes: line 1 column 22397 (char 22396)

I think the error comes from me not being able to decode it can't decode the variable j, that is a dictionary.
It's expecting part of it to be enclosed in double quotes.
The dictionary j is all in single quotes, it looks like this.
[...]'pref_clickgadget': 5, 'created':<PHONE_NUMBER>.0, 'gold_creddits': 0, 'created_utc':<PHONE_NUMBER>.0, 'has_ios_subscription': False, 'pref_show_twitter': False, 'in_beta': False, 'comment_karma': 5281[...]

What is causing that and how do I solve it? It is running on a Debian GNU/Linux 10 Release 10 server. I ran the bot using the run_linux.sh file.

removing as this won't be an issue in upcoming 4.0 release

removing as this won't be an issue in upcoming 4.0 release


chore(actions): update github actions to remove deprecated methods

Signed-off-by: Akhil Mohan<EMAIL_ADDRESS>Why is this PR required? What issue does it fix?:
Github actions deprecated the set-env command. Instead of that environment files are the recommended option now.
What this PR does?:

use environment files in github actions instead of deprecated set-env command
tag generation in release workflow is now fixed with the correct release tag

Does this PR require any upgrade changes?:
No
If the changes in this PR are manually verified, list down the scenarios covered::
Any additional information for your reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:

[ ] Fixes #
[x] PR Title follows the convention of  <type>(<scope>): <subject>
[ ] Has the change log section been updated?
[ ] Commit has unit tests
[ ] Commit has integration tests
[ ] (Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
[ ] (Optional) If documentation changes are required, which issue on https://github.com/openebs/openebs-docs is used to track them:

Codecov Report

Merging #6 (faeb6f5) into develop (72b79ff) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           develop      #6   +/-   ##
=======================================
  Coverage     0.68%   0.68%
=======================================
  Files           10      10
  Lines          585     585
=======================================
  Hits             4       4
  Misses         581     581

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 72b79ff...faeb6f5. Read the comment docs.


What's the reason using DDPM instead of DDIM?

Thank you for sharing an interesting work.
Is there any reason that the EgoEgo uses DDPM as a scheduler?
From my knowledge, some schedulers, such as DDIM and DPMSolver, can accelerate the sampling process.

Hi, we didn't try DDIM since we were not aiming for speed in this project. DDIM or DPMSolver can be used here, but I'm not sure if they would introduce some artifacts like jitters.


Widget freeze

At  some point the widget does not refresh anymore. I have to remove it and recreate it on the phone.
The application However still works.
My phone: xiaomi MI 9T pro.

Some questions:

Are you using latest app version v2.22 ?
How many checkers in your list?
What does the windget look like when it stops updating? Are there any messages?
When the widget stops updating, try adding a new checker to list. Does the new checker appear in the widget?

Some questions:

Are you using latest app version v2.22 ?
How many checkers in your list?
What does the windget look like when it stops updating? Are there any messages?
When the widget stops updating, try adding a new checker to list. Does the new checker appear in the widget?

Out of date


_type is not returned with Image Metadata for dimension field

Hi there, I've been playing around with groqd today (Amazing - 5⭐) and immediately ran into a problem.
You have the following in sanityImage.ts

_type: schemas.literal("sanity.imageDimensions"),

After a few tries I realised, that this field is not returned. (despite some docs on sanity.io)
On their reference however, it is corresponding to how my recent install behaves. See here

Thanks for reporting! Admittedly, I just followed their docs when adding the types here. But this should be a pretty quick fix to patch this up! I'll see if I can get something in tomorrow.

Was just digging into this, and I'm having troubles replicating the issue – I seem to consistently get the _type field back on the image dimensions. Can you give me some more info on the type of image you're querying for that has that _type field missing?
FWIW I ran this query in a vision dashboard to check for images with missing _type on dimensions:
*[_type == "sanity.imageAsset" && defined(metadata.dimensions._type)]

and didn't get any results.

Hiya, sorry, busy day at work here.
Doesn't no results mean it cannot find an image asset where _type is defined?
I ran the same query on my Vision - on their movie sample setup and indeed, I get no results. but as soon as i removed ._type from the query I received the results.
I believe, if you want to find assets, where there is no _type field defined, you need to negate the query
*[_type == "sanity.imageAsset" && !defined(metadata.dimensions._type)]

So basically, you have validated it 😀 by not getting any results.

I still think we perhaps should not remove it from schema creation, but mark it optional, so if there is a weird internal Sanity thing where it may or may not be included, would still allow this to work?

Okay, I also did a bit more digging - I created my setup from a dataset provided by Sanity... aaand I think when that got loaded it lacked the _type field.
I've gone ahead and uploaded an image manually and that has the _type.
Despite this, I still think it could be optional. I've created a PR for this. What you do think? #86


Feat: destination vector db add option for embedding without field names

Description
Responding to issue #48627
Including field names when embedding text changes the semantic meaning of a vector, so it is useful to have the option of embedding only the text without the field names.
This is my first contribution, so please let me know what else is needed!
Changes
Adds an additional config to allow user to choose whether or not to embed field names with a vector db destination.

Summary by CodeRabbit

New Features

Introduced a new configuration option to control the inclusion of field names in embeddings, enhancing flexibility in document processing.

Bug Fixes

Improved the document generation logic to conditionally omit field names based on the new configuration setting.

Tests

Added tests for the new omit_field_names_from_embeddings field in the configuration model to ensure proper functionality.

Resolves https://github.com/airbytehq/airbyte/issues/48627#issue-2684912914

@frankiebromage - Thanks for creating this!
Just a heads up: one challenge with rolling this out will be that most of the vector store destinations are several versions behind in their CDK pin. This may be related to the reason the Pinecone test failed in CI.

Kicking the tires on CI again


IntersectionController not initialized in node environments

Which package(s) are affected?
Observers (@lit-labs/observers)
Description
In upgrading @lit-labs/observers, we had a test failing that has an intersection controller. The code we were testing looks a bit like this:
@customElement("my-element")
export class MyElement extends LitElement {
  #myController = new IntersectionController(...);

  firstUpdated() {
    this.#myController.observe(...);
  }
}

Now, we test this with JSDOM, that happens to run in a node environment. This causes isServer to be true, and since https://github.com/lit/lit/pull/4591 there is short circuit behaviour in the constructors of the controllers exported in the observers package. This short circuiting prevents construction of this IntersectionController which makes the call in firstUpdated fail (cannot call observe on undefined). Thats an issue in JSDOM because it does execute the components lifecycle.
I was a bit surprised, I personally expected that it would be stubbed with no-ops in node environments, which also would have gone over well in my JSDOM tests. Instead, construction is prevented, causing calls to error.
Reproduction
I am having a hard time producing a solid reproduction for this. I hope my description above is sufficient but let me know :).
Workaround
We worked around this by adding resolve: { conditions: ["browser"] } to our vitest config.
Is this a regression?
Yes. This used to work, but now it doesn't.
Affected versions
Failing in (@lit-labs/observers) 2.0.4, worked in 2.0.2
Browser/OS/Node environment
Node: v20.18.0

I think the workaround you mention is a viable solution here. Testing with JSDOM in a Node environment rather than a real browser inherently comes with their pitfalls with this being one of them.
Our solutions for SSR support in other packages including the core lit-html and LitElement have all involved using export conditions targeting the "node" environment which the isServer check is based on. We'll likely continue to lean on that so if you want to test as if you're in the browser, I would recommend keeping the "browser" condition for the module resolution settings.

Thanks. One thing I wonder, the SSR codepath prevents construction of these controllers. So calling any method on them gets you an error. I guess that surprised me at first, although there is also something to say for erroring, as these methods are not going to do something in SSR environments. What do you think?

I was talking about SSR environments. Your explanation makes sense to me, I was just wondering if we could do more for users who accidentally use one of these controllers in an SSR environment and get strange "cannot read property observe of undefined" type errors (because the IntersectionController was not constructed). But yeah, you are right, thats never going to be complete anyway.
Thanks, I guess we can close this :).


TomEE support?

TomEE v1.7.2 is a JavaEE 6 server and uses CDI but in a lower version that in this library, is there some possibility of be compatible with JavaEE 6? Which CDI 1.2 features are required for this library?

I saw @AroundConstruct CDI 1.2 feature, I'm trying to find a workaround with CDI 1.1, but i think is not trivial

Java EE 6 uses CDI 1.0 (JSR 299) which lacks the following features compared to 1.2 that are leveraged by Metrics CDI:

@Priority annotation for global enablement of interceptors and alternatives (CDI 1.1 feature depending on Java Interceptors Specification 1.2),
@AroundConstruct lifecycle callback for constructors (CDI 1.1 feature depending on Java Interceptors Specification 1.2),
@Vetoed annotation (CDI 1.1 specification),
@WithAnnotations annotation (CDI 1.1 specification),
Portable behaviour of getBeans method call in AfterBeanDiscovery lifecycle callback (CDI 1.2 specification).

So the majority of missing features from CDI 1.0 are available starting CDI 1.1 which means that porting Metrics CDI to CDI 1.1 would be a lot easier than porting it to CDI 1.0.
If CDI 1.0 is still a requirement, that is upgrading the OpenWebBeans dependency in your TomEE setup is not possible (as WildFly can be patched to upgrade Weld):

lack of @Priority can be replaced by explicit enablement in beans.xml for each user bean archive,
lack of @AroundConstruct could simply be eluded by not offering instrumentation of constructor calls and not having metrics registered when beans get instantiated,
@Vetoed and @WithAnnotations annotations could be emulated in the extension.

A similar work has been done in Camel CDI to provide support for Java EE 6: https://github.com/astefanutti/camel-cdi/commit/541d6d903ffa108f7261000b44fe7300fe93e81b
That being said, it looks like TomEE is upgrading its OpenWebBeans dependency with CDI 1.2 support so that may be an option to wait until the next TomEE release:
https://git1-us-west.apache.org/repos/asf?p=tomee.git;a=blob;f=pom.xml;h=6e257709c8db1252370e83343056928055e4038e;hb=refs/heads/master#l98

Let me close this. Feel free to reopen if CDI 1.1 compatibility is still a strong requirement.


Rename Mavlink class generate virtual RC setter/getter

This is a very tiny change, but I thought I'd PR it anyway.
Describe problem solved by this pull request
I was looking at the mavlink receiver, and I found the statement if (_mavlink->get_manual_input_mode_generation()) to be confusing.
Describe your solution
I renamed the getter so that the client code now looks like if (_mavlink->should_generate_virtual_rc_input()) which better reflects what the code does.
I also renamed the setter from set_manual_input_mode_generation to set_generate_virtual_rc_input.
Describe possible alternatives
None.

Thanks!


Fix clone iterable objects

Hi!
Currently, when trying to clone objects that implement the interface "\IteratorAggregate", an error occurs because "Spatie\Cloneable\Cloneable.php:13" iterates over the elements of the collection.
With my pull request, I propose a solution to this problem.

Ah, great! Thanks


Minor updates to C++ style guide.

/cc @tituswinters

@tituswinters Thank you very much for the quick review!


Publish eslint-plugin-metamask-design-tokens Library to npm with Shared Libraries Team Support

Description
To maximize the utility and accessibility of our eslint-plugin-metamask-design-tokens library, we aim to publish it to npm. This step will facilitate its adoption across various projects, enabling teams to easily integrate and enforce our design system's color usage standards. Collaborating with the shared libraries team, we seek to ensure that the library meets all requirements for public npm packages, including documentation, versioning, and licensing. This initiative is crucial for extending our design system's reach and consistency across projects, promoting code quality and visual coherence.
Technical Details

Collaboration: Work closely with the shared libraries team to prepare the eslint-plugin-metamask-design-tokens library for npm publication. This includes:

Reviewing and finalizing the library's documentation for clarity and completeness.
Ensuring the library adheres to npm's package naming conventions and versioning best practices.
Confirming the library's licensing is appropriate for public distribution.

npm Setup: Set up an npm account (if not already available) and configure access rights, ensuring the shared libraries team can manage future updates.
CI/CD Integration: Implement CI/CD workflows for automated testing, building, and publishing of the library to npm, streamlining the release process.

Acceptance Criteria

The eslint-plugin-metamask-design-tokens library is successfully published to npm and is publicly accessible.
The library's npm page includes comprehensive documentation, guiding users on installation, configuration, and usage.
Automated CI/CD workflows are in place for reliable and efficient library updates and publishing.
Collaboration with the shared libraries team results in a smooth publication process, adhering to all technical and procedural standards.

Additional Notes
Publishing this library to npm represents a significant milestone in our efforts to standardize design system compliance across projects. It underscores our commitment to code quality, design consistency, and developer efficiency. By leveraging the expertise of the shared libraries team, we aim to ensure that the library not only meets the technical requirements for npm publication but also aligns with our broader goals for design system integration.
Tracking
This task is a pivotal component of our strategy to enhance design system adoption and adherence. Progress on this task will be tracked through this GitHub issue, with milestones and updates documented as the publication process advances.

This has been completed
https://consensys.slack.com/archives/G1L7H42BT/p1711733977470589
https://www.npmjs.com/package/@metamask/eslint-plugin-design-tokens


i18n(ko-KR): update rednering-modes.mdx

Description (required)

update rednering-modes.mdx
#8469

Related issues & labels (optional)

Closes #
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

ko
basics/rendering-modes.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.