Issues running pipenv & pyenv

I am unable do activate virtualenv using pipenv shell with python managed by pyenv.
Here is the output of my terminal:
roger@ohm:/tmp/lab $ pipenv --venv
No virtualenv has been created for this project yet!
roger@ohm:/tmp/lab $ pipenv install requests
Creating a Pipfile for this project...
Creating a virtualenv for this project...
⠋Using base prefix '/home/roger/.pyenv/versions/3.6.1'
New python executable in /home/roger/.local/share/virtualenvs/lab-O8QxVB32/bin/python3.6
Also creating executable in /home/roger/.local/share/virtualenvs/lab-O8QxVB32/bin/python
Installing setuptools, pip, wheel...done.

Virtualenv location: /home/roger/.local/share/virtualenvs/lab-O8QxVB32
Installing requests...
Collecting requests
  Using cached requests-2.18.4-py2.py3-none-any.whl
Collecting urllib3<1.23,>=1.21.1 (from requests)
  Using cached urllib3-1.22-py2.py3-none-any.whl
Collecting idna<2.7,>=2.5 (from requests)
  Using cached idna-2.6-py2.py3-none-any.whl
Collecting certifi>=2017.4.17 (from requests)
  Using cached certifi-2<IP_ADDRESS>-py2.py3-none-any.whl
Collecting chardet<3.1.0,>=3.0.2 (from requests)
  Using cached chardet-3.0.4-py2.py3-none-any.whl
Installing collected packages: urllib3, idna, certifi, chardet, requests
Successfully installed certifi-2<IP_ADDRESS> chardet-3.0.4 idna-2.6 requests-2.18.4 urllib3-1.22

Adding requests to Pipfile's [packages]...
P.S. You have excellent taste! ✨ 🍰 ✨
roger@ohm:/tmp/lab $ pipenv shell
ERROR: The virtualenv hasn't been activated correctly.
Either the env is corrupted (try running `pew restore env`),
Or an upgrade of your Python version broke your env,
Or check the contents of your $PATH. You might be adding new directories to it
from inside your shell's configuration file.
In this case, for further details please see: https://github.com/berdario/pew#the-environment-doesnt-seem-to-be-activated

I followed the steps of the URL above, changing PATH order, but no sucess.

roger@ohm:/tmp/lab $ pew restore env
Running virtualenv with interpreter /usr/bin/env
/usr/bin/env: /home/roger/.pyenv/versions/3.6.1/lib/python3.6/site-packages/virtualenv.py: Permission denied

pyenv does some weird things, and isn't recommended.
Let's see if we can fix it, though. @berdario, do you have any thoughts on this? I believe it's related to pyenv's shimming.

Hmm, so I think this is an environment issue @rdemetrescu. I've used pyenv since the beginning of the project without issue. It looks like there may be permission issues on the directories that .pyenv is creating on your machine? Something is getting in the way of pew workon.

pyenv does some weird things, and isn't recommended.

What weird things are you referring to? I've used pyenv for years and have never had problems with pip, virtualenv, or any other packages I've installed.
How else do people manage the installation and selection of multiple Python versions? I think the usage of pyenv is more common than you let on. 😄

@jacebrowning I may be getting pyenv confused with pythonz :)

FTR some weird things do happen with pyenv, the main problem being the shims. Sometimes the path look up fails when pointed to shims, and I need to manually pass the “real” executable path) to some certain build scripts. Sometimes the shims themselves cause problems with feature checks (because which xxx and type xxx would return 0). I still use it because the overall benefits still outweigh edge case failures, but problems do exist.

@nateprewitt I did a fresh install of pyenv on my machine.
➜ pipenv install requests
Creating a Pipfile for this project...
Creating a virtualenv for this project...
⠋Using base prefix '/home/roger/.pyenv/versions/3.6.2'
New python executable in /home/roger/.local/share/virtualenvs/lab-O8QxVB32/bin/python3.6
Also creating executable in /home/roger/.local/share/virtualenvs/lab-O8QxVB32/bin/python
Installing setuptools, pip, wheel...done.

Virtualenv location: /home/roger/.local/share/virtualenvs/lab-O8QxVB32
Installing requests...
Collecting requests
  Using cached requests-2.18.4-py2.py3-none-any.whl
Collecting urllib3<1.23,>=1.21.1 (from requests)
  Using cached urllib3-1.22-py2.py3-none-any.whl
Collecting chardet<3.1.0,>=3.0.2 (from requests)
  Using cached chardet-3.0.4-py2.py3-none-any.whl
Collecting idna<2.7,>=2.5 (from requests)
  Using cached idna-2.6-py2.py3-none-any.whl
Collecting certifi>=2017.4.17 (from requests)
  Using cached certifi-2<IP_ADDRESS>-py2.py3-none-any.whl
Installing collected packages: urllib3, chardet, idna, certifi, requests
Successfully installed certifi-2<IP_ADDRESS> chardet-3.0.4 idna-2.6 requests-2.18.4 urllib3-1.22

Adding requests to Pipfile's [packages]...
P.S. You have excellent taste! ✨ 🍰 ✨

➜ pipenv shell
ERROR: The virtualenv hasn't been activated correctly.
Either the env is corrupted (try running `pew restore env`),
Or an upgrade of your Python version broke your env,
Or check the contents of your $PATH. You might be adding new directories to it
from inside your shell's configuration file.
In this case, for further details please see: https://github.com/berdario/pew#the-environment-doesnt-seem-to-be-activated

➜ pew restore env
Running virtualenv with interpreter /home/roger/.pyenv/versions/3.6.2/bin/python
Using base prefix '/home/roger/.pyenv/versions/3.6.2'
New python executable in /home/roger/.local/share/virtualenvs/env/bin/python
Installing setuptools, pip, wheel...done.

But the final result is still failure for me:
➜ pipenv shell
ERROR: The virtualenv hasn't been activated correctly.
Either the env is corrupted (try running `pew restore env`),
Or an upgrade of your Python version broke your env,
Or check the contents of your $PATH. You might be adding new directories to it
from inside your shell's configuration file.
In this case, for further details please see: https://github.com/berdario/pew#the-environment-doesnt-seem-to-be-activated

i think you have a shell configuration problem.
We have a fix in master that should solve this, maybe. let me release it.

i want to test on windows first. try running off of master and let me know how it goes! closing in the meantime

Thanks @kennethreitz . I upgraded to pipenv, version 5.3.5 but still no sucess here.
My environment is:
Ubuntu 15.10 (x86_64)
bash version: 4.3.42(1)-release
zsh version: zsh 5.1.1
Regarding pyenv, that's what I have on both .bashrc and .zshenv :
# .bashrc
export PATH="~/.pyenv/bin:$PATH"
eval "$(pyenv init -)"

# .zshenv
PATH="$HOME/.pyenv/bin:$PATH"
eval "$(pyenv init -)"

I will try to test it on a virtual machine, later.

you might want to try the changes i have landed in the master branch

Hi @kennethreitz , here is the new output:
➜ pipenv shell
{'code': <code object <module> at 0x7fbbeb4a6540, file "/home/roger/.local/share/virtualenvs/lab-O8QxVB32/bin/activate_this.py", line 6>, 'f': <_io.TextIOWrapper name='/home/roger/.local/share/virtualenvs/lab-O8QxVB32/bin/activate_this.py' mode='r' encoding='UTF-8'>, 'activate_this': '/home/roger/.local/share/virtualenvs/lab-O8QxVB32/bin/activate_this.py', 'shell_args': (), 'compat': False, 'python': False, 'three': None}
ERROR: The virtualenv hasn't been activated correctly.
Either the env is corrupted (try running `pew restore env`),
Or an upgrade of your Python version broke your env,
Or check the contents of your $PATH. You might be adding new directories to it
from inside your shell's configuration file.
In this case, for further details please see: https://github.com/berdario/pew#the-environment-doesnt-seem-to-be-activated

So, I discovered my .zprofile isn't sourced at all at my Ubuntu installation.
I changed my .zshenv to do all pyenv stuff within sentinel.
if [ -z $PYENV_ROOT ]; then
	export PYENV_ROOT="$HOME/.pyenv"
	export PATH="$PYENV_ROOT/bin:$PATH"
	eval "$(pyenv init -)"
fi

Everything is running fine now. I am able to do a pipenv shell.

✨🍰✨

For the record, there's also pipenv run -c, which runs in "compatibility mode" for less-well-configured shells.

Amazing! I reverted my changes in .zshenv and tested pipenv shell -c.
It worked like a charm.

I'm going to make a homebrew tap for all versions of Python.

@kennethreitz still planning on doing this? I'm increasingly finding pyenv shims to not be great.

@AlJohri this was done quite a bit ago https://github.com/kennethreitz/homebrew-pythons

Awesome :)

sticking with pyenv :)

Hey guys, any timeframe on supporting 3.6.3?
I'm a newbie and got this warning when trying to push a heroku build:
The latest version of Python 3 is python-3.6.2 (you are using python-3.6.3, which is unsupported).
Will figure out how to get pyenv to make everything happy on 3.6.2 for now but still curious.  Thanks!

@jaellis this isn't a pipenv issue, its an issue with the heroku python buildpack. submitted PR here: https://github.com/heroku/heroku-buildpack-python/pull/483
cc @kennethreitz

Thanks so much!

OK,
So. Whats is the best way to use pyenv and pipenv together
OR How does one manage multiple versions on python in tandem with pipenv
?

@awhillas What are you trying to do? If you specify python_version = <version installed with pyenv> in the [requires] section of your Pipfile it should just work.

so I can install pipenv with the system python, create a new project with it and then just make that change in the Pipfile and it will work... like magic...?

Just install Pipenv anywhere (as long as you can run it), and yes, it would just work. You don’t even need to add the shim directory to PATH or pyenv global anything (basically you don’t need to shims). All you need to set is the PYENV_ROOT environment variable.

@jacebrowning  please look into this issue of mine


Update README.md with Open in Codeanywhere button

This PR adds "Open in Codeanywhere" button to the Readme file, next to the same "Open in Gitpod" button.
Codeanywhere is a cloud-based Integrated Development Environment (IDE) that allows developers to code, learn, build, and collaborate on projects directly from their web browsers. This button opens the Codeanywhere VS Code IDE in the browser, pulls the repo, sets up a container environment and allows the developer to run the code - all of this with a single click and for free.

Sounds great! Thanks for the PR


Quoting tag in XMLName field

Tag in XMLName field must be quotted, for example, we should have:

XMLName xml.Name xml:"plant"
instead of:
XMLName xml.Name xml:plant

Updated test expectations.

Bump.
This would address issue #19.


Redefine specification for bright colors

This makes the definition of bright colors more specific, as per the discussion in https://github.com/tinted-theming/base24/issues/31. This also reverts the color order back to the previous version, so that base08-base0E are the primary colors, while base12-base17 are the secondary colors.
A grayscaled version of the example is also included to visualize the contrast between bright vs non-bright colors in terms of luminosity.

Yeah, I think I'm fine with this being merged!


tlsh: 4.9.3 -> 4.10.0

Motivation for this change
New release.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 139233 at fda09976 run on aarch64-linux 1

5 packages built successfully:

diffoscopeMinimal
python38Packages.telfhash
python38Packages.tlsh
python39Packages.telfhash
python39Packages.tlsh

2 suggestions:

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/tlsh/default.nix:27:3:
   |
27 |   meta = with lib; {
   |   ^

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/development/python-modules/tlsh/default.nix:28:0:
   |
28 |     description = "Trend Micro Locality Sensitive Hash";
   | ^

@ofborg build python3Packages.tlsh

looks like this package is missing a maintainer, would you like to maintain this package?

@figsoda I am only updating this package due to some interest in the Summer of Nix, I have no personal investment in it.

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

6 packages built:

diffoscope
diffoscopeMinimal
python38Packages.telfhash
python38Packages.tlsh
python39Packages.telfhash
python39Packages.tlsh


feat: Support Node.js v20

closes https://github.com/esbuild-kit/tsx/issues/291

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

@privatenumber JFYI In v20.6.0 initialize hook was added - https://nodejs.org/dist/latest-v20.x/docs/api/esm.html#initialize
It's avaialble in<EMAIL_ADDRESS>From docs about globalPreload:

This hook will be removed in a future version. Use initialize instead. When a loader has an initialize export, globalPreload will be ignored.

I have a open PR for it (https://github.com/esbuild-kit/esm-loader/pull/72), but I'm still on the fence about how to approach it as it would require usage via --import instead of --loader.


Configurable Buffer for Notifications

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
New Notification, Other
🔖 Feature description
I use uptime kuma for monitoring lots of different things and it is excellent, thank you.
I have also configured the notifications, however, there will be instances where we get a single timeout. This isn't always a true down time event, it may just be network conditions etc. If we are monitoring a third party API that we are relying on and there is a single time out. I don't necessarily want to get notified immediately. I'd rather wait until we have checked a couple of times, if it is down for multiple checks, then I want to get the notification so I know there is a true problem.
Basically I'd like to configure a buffer, where notifications do not get sent until the number of sequential failed checks is greater than the buffer value.
✔ Solution
I would like an option on a monitor, where we can configure a buffer value. The service  as down and does not trigger notifications until this number of checks have failed in a row greater or equal to the value configured as the buffer.
❓ Alternatives
We could have this as a global configuration option, or as an option on the notification setup
📝 Additional Context
No response

If I understood your request right, then this is already available:
See in each monitor the option under the heartbeat interval:
Retries
Maximum retries before the service is marked as down and a notification is sent

Yes, you are correct! I apologise I completely missed this. Thank you!


How about new release 0.4.x?

Latest release of the recommonmark is 0.4.0 at 2016-01-05: https://pypi.python.org/pypi/recommonmark/0.4.0
Do you have any release plan?

same issue

Even if you can't push a release for whichever reasons, at least increment the version number in master.
That way, whoever is eg. struck by the incompatibility of 0.4.0 with sphinx-argparse (requiring commonmark <= 0.5.4 and commonmark >= 0.5.6, respectively) can add a requirements.txt file saying git+https://github.com/rtfd/recommonmark.git#egg=recommonmark > 0.4.0 to their project. While the master version still says 0.4.0, no upgrade can be enforced from requirements.txt AFAICT.
(And still, please push a release, so those workarounds won't be necessary at all).

A requirements.txt file with -e git+https://github.com/rtfd/recommonmark.git#egg=recommonmark works just as well as a bumped version; my previous comment is thus moot. Thanks agj for pointing this out to me.


Image is in legacy registry

I got the following warning:
docker.io/iron/base: this image was pulled from a legacy registry.  Important: This registry version will not be supported in future versions of docker.

Do you have the latest Docker client installed?

Yes. 1.9.1.

How did you get this error?  I've never seen it.

I just typed docker pull iron/python


How to create a metric alert based on a Log Analytics query

I've managed to create a metric alert based on a custom Log Analytics query via the Azure Portal as is described here.
This seems to work, but now, I'm trying to do the same via an ARM template, so that this can be automated.  I'm trying to follow the documentation here, however, the sample is lacking some information I think.
The gist is, that you need to define a scheduledQueryRule with a LogToMetricAction and a metricAlert which depends on the scheduled query rule, and uses that information to define the alert.
I came up with an ARM template which defines these 2 resources as explained in the sample.   The scheduledQueryRule that I've created contains a query however (which is not present in the sample), like this.  (Redacted some things for simplicity):
"source": {
                    "dataSourceId": "[resourceId('microsoft.operationalinsights/workspaces', parameters('LogAnalytics_Name'))]",
                    "query":"InsightsMetrics | where Namespace == \"prometheus\" | where Name == \"rabbitmq_queue_messages_ready\" | summarize AggregatedValue = max(Val) by Computer, queuename, bin(TimeGenerated, 5m)",
                    "queryType": "ResultCount",
                    "authorizedResources": [
                        "[resourceId('microsoft.operationalinsights/workspaces', parameters('LogAnalytics_Name'))]"
                      ]
                },
"action": {
                    "odata.type": "Microsoft.WindowsAzure.Management.Monitoring.Alerts.Models.Microsoft.AppInsights.Nexus.DataContracts.Resources.ScheduledQueryRules.LogToMetricAction",
                    "criteria": [{
                            "metricName": "customMetrics/QueuedMessages",
                            "dimensions": [
                                {
                                    "name": "Computer",
                                    "operator": "Include",
                                    "values": [
                                        "*"
                                    ]
                                },
                                {
                                    "name": "queuename",
                                    "operator": "Include",
                                    "values": [
                                        "*"
                                    ]
                                }
                            ]
                        }
                    ]

What I want to do here -as far as I understand-  is create a 'LogToMetricAction' which converts the output of the query to a metric.   The metric is given the name 'customMetrics/QueuedMessages'.
When I deploy this template, I'm given the error:
{
  "code":"DeploymentFailed",
  "message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
  "details":
  [
        {
             "code":"BadRequest",
             "message":"Invalid Input :\r\nProperties.Action.properties.action.criteria.metricName: metricName customMetrics/QueuedMessages is not supported\r\n, metricName customMetrics/QueuedMessages is not supported"
        }
  ]
}

Any guidance on how to convert the query outputs to a metric ?
I also tried to 'export template' for the alert that I've created via the Portal, but then I get an ARM template that creates a scheduledQueryLog using a preview API version, and there 's no notion of any LogToMetricAction.

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

ID: fb45c876-8b2a-5e69-3745-5ee47f2bb27d
Version Independent ID: 4ace419b-24da-a3ef-0839-78a2d815cfb8
Content: Creating Metric Alerts for Logs in Azure Monitor - Azure Monitor
Content Source: articles/azure-monitor/alerts/alerts-metric-logs.md
Service: azure-monitor
Sub-service: alerts
GitHub Login: @harelbr
Microsoft Alias: harelbr

Hi @fgheysels ,
The 'Metric Alerts for Logs' feature isn't a general-purpose mechanism to convert log queries into metrics and alert on them. It is rather limited to a set of Log Analytics tables and performance counters described in the Overview section of this article.
For this reason, you can't use this feature with a custom query. You might want to look into the option of sending custom metrics, see more information here.
Hope this helps.

Thanks for the info.  However, I do find it strange that this seems to work when doing it via the portal ?

When I create an alert as in the above screenshot, it seems that I end up with a stateful metric-based alert, which uses data coming from a log query.

Thanks for sharing more details.
The type of alert rule illustrated in the screenshot is a log alert rule, with a log query that calculates a metric measurement. This is a different type of alert rule (it's not a metric alert rule).
Please refer to this article for a sample ARM template for creating a log alert rule.
Please note that the template example referred to above doesn't have the stateful property (autoMitigate). See here for how to use this property.

I have tried that, and created a 'normal' alert via an ARM template for my query, but when I go to the portal, and look at the alert rule via Azure Monitor, I notice some differences.
This is how the alert rule that I've created via ARM looks like:

The alert-rule that I've created via the Portal  as described here, looks like this:

(Notice the 'based on 'metric measurement' setting).

Additional information:  I've created the alert via the Portal from a 'ContainerInsights' solution, which is linked to my Log Analytics workspace.
Also, the notice that is put on that webpage, suggest that it is possible to create metrics based on custom queries:

It is specific metrics for log, not AKS metrics.
We do not recommend going in this path. Using alerts on the log directly has advantages on terms of reliability.

I'm not using AKS :)  We have a k3s deployed on a vessel (actually, we will have 70 vessels like that) and have ContainerInsights deployed there.   We're collecting prometheus metrics from RabbitMQ and sending those metrics to Log Analytcis via Azure Arc.
We want to be notified when something goes wrong on a ship (for instance, messages ending up in error queues).
In short, I've been able to create an alert for this via the Azure Portal.

As you can see here, I can select 'Metric Measurement' as an option for the 'Based on' dropdown.  When I select this option, my query needs to meet some requirements (I need to have an 'AggregatedValue' alias and my results must be grouped via the bin() method).
I have configured this alert to post a message to a teams channel.  So when the alert fires, I get a notification that looks like this:

This meets my requirements.
However since we have multiple environments (dev, tst, acc, prd), we don't create resources via the Portal, but do everything via IaC.  (Developers also do not have rights to access production for instance).
So, the idea is to create this alert - rule via an ARM template, however, I don't see how I can create this alert via an ARM template.
When inspecting the ARM template docs, I can only choose 'ResultCount' for query type.  (see here.
I also tried to create the alert rule using API version 2020-05-01-preview (as it seems that that's the only way to have the alert split by dimensions and to specify a 'mute time', but in that case, the 'search results' are no longer included when my alert fires.  In that case, the message that is posted to teams, looks like this:

And that is because the search results are now no longer included in the alert body.
Also, when I inspect the alert definition in the portal that I've created via an ARM template, this looks like this:

I'd be happy to discuss this offline further if you want.

I recommend you do not relay on search results in your integration. Future API version will not include search results.
Please use either dimensions or the links to get to the alert context. If you have to use the results, I recommend doing it via logic app and the provided LA API link we provide.

This is an example of a metric measurement alert template: https://docs.microsoft.com/azure/azure-monitor/alerts/alerts-log-create-templates#template-with-cross-resource-query-up-to-api-version-2018-04-16

Thanks, I'll have a look at it.
@yanivlavi :  calling the link to the API via a Logic App isn't that straightforward, as it needs authentication etc.   I once opened a support request and received the steps that are required to be able to call this API endpoint from a LA, but haven't tried it yet.  Anyway, afaik, it is not publicly documented.

It is described here:
https://docs.microsoft.com/en-us/azure/azure-monitor/logs/logicapp-flow-connector

Thanks, but that's not really what I'm looking for.   I don't want to specify a KQL query in the logic app.
I have a logic app which is triggered via an Action Group, because an alert was fired (the action group is configured with a webhook to the Logic App).
The Logic App receives a request where the body contains some information regarding the alert.  like this:
"LinkToFilteredSearchResultsAPI": "https://api.applicationinsights.io/v1/apps/<redacted>/query?query=customEvents%20%7C%20where%20name%20%3D%3D%20%22VesselTelemetryResumed...."

It doesn't seem to be so simple to just execute the request to that Uri, because you need to include an access token (how to get that one ? ).
But, now that I'm taking a look at this again, I also see that the alert context contains the query that caused the alert to  fire.  So together with the information you've provided with that article you've linked, it might be possible to take some steps.

Here is the docs on getting the token to use with the link:
https://dev.loganalytics.io/documentation/1-Tutorials/Direct-API


Can't sync with Google CardDav server

I set the server sync to "google.com", entered my email as user and my email account's password as password but RainLoop says that there were a synchronization error. What can I do?

Unfortunately, RainLoop does not support google Carddav server.

why ?

Because Google does not provide a standard CardDav access.


gettid: symbol not found

Error relocating /lib/libelogind.so.0: gettid: symbol not found

https://git.musl-libc.org/cgit/musl/commit/?id=d49cf07541bb54a5ac7aec1feec8514db33db8ea

https://git.musl-libc.org/cgit/musl/commit/?id=d49cf07541bb54a5ac7aec1feec8514db33db8ea

Fixed with https://github.com/bbusse/swayvnc/commit/549a6fab76cf84889acaf3de9837794a9f1857ca

Fixed with https://github.com/bbusse/swayvnc/commit/549a6fab76cf84889acaf3de9837794a9f1857ca


Added backend-type/matrix-type independent matrix-product in linalg

Bugfix for issue #2801. New addition :

One new method for matrix_product in Core module that
doesn't support preallocated result parameter but rather
returns the result in a newly created matrix.
Accompanying implementation in MatrixProduct
Two new unit-tests in MatrixProduct_unittest

@karlnapf travis error seems unrelated. Merging this one.

@yorkerlin Could you please check if this patch helps you with the failures in ViennaCL build? Just use
SGMatrix<float64_t> C = linalg::matrix_product(A, B);

instead of
linalg::matrix_product(A, B, C);

@lambday
I still need the following operations

linalg::elementwise_product(l, r, res);//res=l.*r
linalg::add(avec, bvec, res, 1.0, -1.0); //res=avec-bvec

void debug1()
{
SGVector<float64_t> left(2);
left[0]=8.57765;
left[1]=4.57765;
SGMatrix<float64_t> left_mat(left.vector,1,left.vlen,false);
SGMatrix<float64_t> res_mat(1,left.vlen);
linalg::elementwise_product(left_mat,left_mat,res_mat);
}

void debug2()
{
SGVector<float64_t> left(2);
left[0]=1.0;
left[1]=1.0;
SGVector<float64_t> right(2);
right[0]=8.57765;
right[1]=4.57765;
SGVector<float64_t> res(2);
linalg::add(left, right, res, 1.0, -1.0);
}

@yorkerlin coming on the way. By the way did you have a chance to take a look at the benchmark I added?

PR #2806

@yorkerlin See PR #2809 and #2811. That should solve the issue for viennacl build for now. Use
res = linalg::elementwise_product(l, r);
res = linalg::add(l, r,alpha,beta);

Looking forward to your comment on the benchmark.


abnormal induced morbidity/mortality

I am using abnormal induced morbidity/mortality (MP:0001657) for a phenotype of "poor survival after 30 minutes of ischemia while a 70% hepatectomy is performed."  None of the children of this term are satisfactory.  Perhaps this is the correct place for this annotation but the term definition makes me a little uneasy.  Could we use a specifc term such as "poor survival of surgical intervention"?
Reported by: hdene
Original Ticket: obo/mammalian-phenotype-requests/1079

Some annotations have been made to abnormal response to injury (MP:0005164) and children of this term. Added term 'abnormal susceptibility to injury induced morbidity/mortality' (MP:0020344). I don't think we need to create children of this term currently.


An error when moving thread to agent_shinjuku

Sorry to trouble you again. When I run agent_shinjuku and write the user-state thread number to /sys/fs/ghost/enclave_ 1/tasks, the following error was encountered：
$:bazel-bin/agent_shinjuku --ncpus 2
Core map
(  0 )	(  1 )	(  2 )	(  3 )
Initializing...
Initialization complete, ghOSt active.
PID 2517 Fatal segfault at addr 0x10:
[0] 0x7fb0313c13c0 : __restore_rt
[1] 0x55ce4c8378a5 : ghost::BasicDispatchScheduler<>::DispatchMessage()
[2] 0x55ce4c8368c9 : ghost::ShinjukuAgent::AgentThread()
[3] 0x55ce4c83ab0a : ghost::LocalAgent::ThreadBody()
[4] 0x7fb031612de4 : (unknown)

When I run the agent again_shinjuku or other programs will get such errors:
lib/enclave.cc:452(2716) CHECK FAILED: retries < kMaxRetries [10 >= 10]
errno: 16 [Device or resource busy]
PID 2716 Backtrace:
[0] 0x55b4422162f6 : ghost::LocalEnclave::CreateAndAttachToEnclave()
[1] 0x55b442216de5 : ghost::LocalEnclave::LocalEnclave()
[2] 0x55b4421cfab1 : ghost::AgentProcess<>::AgentProcess()
[3] 0x55b4421ca9d9 : main
[4] 0x7fd96a91d0b3 : __libc_start_main

How to solve the first error? How can I run another program without reboot? Thank you！

The Shinjuku scheduler expects the application it is scheduling to create a shared memory region known as the PrioTable. The PrioTable is used by the application to tell the scheduler which threads are runnable. The scheduler will crash if this region is not present. Please take a look at the RocksDB application for an example of creating and using a PrioTable.
If you are using the Shinjuku scheduler because you want support for a preemption time slice, the SOL scheduler and the centralized FIFO scheduler both support time slices now. You can set the time slice with the --preemption_time_slice command line argument. Neither of these two schedulers uses a PrioTable, so they will work with your application.
Regarding your second question, when an agent crashes, its enclave does not automatically get destroyed. Thus, when you launch another agent, it experiences the error you posted. You can resolve this error by destroying the enclave after an agent crash, before you launch the next agent. To destroy all enclaves on the machine, run the following command:
for i in /sys/fs/ghost/enclave_*/ctl; do echo destroy > $i; done

Please let us know if you have any other questions.

The Shinjuku scheduler expects the application it is scheduling to create a shared memory region known as the PrioTable. The PrioTable is used by the application to tell the scheduler which threads are runnable. The scheduler will crash if this region is not present. Please take a look at the RocksDB application for an example of creating and using a PrioTable.
If you are using the Shinjuku scheduler because you want support for a preemption time slice, the SOL scheduler and the centralized FIFO scheduler both support time slices now. You can set the time slice with the --preemption_time_slice command line argument. Neither of these two schedulers uses a PrioTable, so they will work with your application.
Regarding your second question, when an agent crashes, its enclave does not automatically get destroyed. Thus, when you launch another agent, it experiences the error you posted. You can resolve this error by destroying the enclave after an agent crash, before you launch the next agent. To destroy all enclaves on the machine, run the following command:
for i in /sys/fs/ghost/enclave_*/ctl; do echo destroy > $i; done

Please let us know if you have any other questions.

The Shinjuku scheduler expects the application it is scheduling to create a shared memory region known as the PrioTable. The PrioTable is used by the application to tell the scheduler which threads are runnable. The scheduler will crash if this region is not present. Please take a look at the RocksDB application for an example of creating and using a PrioTable.
If you are using the Shinjuku scheduler because you want support for a preemption time slice, the SOL scheduler and the centralized FIFO scheduler both support time slices now. You can set the time slice with the --preemption_time_slice command line argument. Neither of these two schedulers uses a PrioTable, so they will work with your application.
Regarding your second question, when an agent crashes, its enclave does not automatically get destroyed. Thus, when you launch another agent, it experiences the error you posted. You can resolve this error by destroying the enclave after an agent crash, before you launch the next agent. To destroy all enclaves on the machine, run the following command:
for i in /sys/fs/ghost/enclave_*/ctl; do echo destroy > $i; done

Please let us know if you have any other questions.

Could you explicitly give me more information about how to create and use a PrioTable?


How to control the compilation thread number exactly?

Problem description
I changed the NUM_THREADS to 4 in the Makefile, but it does not work.
sometimes, there are only 4 compilation tasks, while sometimes there are more than ten tasks, which makes me confused.
Because I compiled in the container, too many tasks will lead to crash for OOM, I want to control the compilation task number exactly. how to do this?
System information
compile
CMake log
No response

To change the number of threads when using docker compose you have to set the envvar: NUM_THREADS=4 or provide the var directly via the -e param as explained in the README


feat: add issue templates for bugs and feature requests

Resolves #14

Excellent stuff! Looks precise and concise!


list-prs-for-file - Use new style

Fix #7468
Updated the feature to use new .Overlay style and <anchored-position> element, fixing the issue along the way.
Test URLs
https://github.com/pypi/warehouse/blob/main/warehouse/packaging/models.py
Screenshot

There's a new issue though: hovercards now get covered by the popover - maybe there's someway to tweak the popover or we just disable the hovercard (and maybe revert to tooltips instead - I remember that's how the feature used to work).

There's a new issue though

That would be a deal breaker since this is a cosmetic change. The new dropdown uses the new popover API and their hovercard doesn't. There's zero way for us to "change the z-index" here unless we hack the hovercard to use the same API — which we shouldn't do.
I'd say let's wait until they update that component and then we can reopen this PR.

The new dropdown uses the new popover API and their hovercard doesn't.

Yeah too bad, this also breaks on GitHub's own menu (though the example below is a bit contrived):

There's zero way for us to "change the z-index" here unless we hack the hovercard to use the same API — which we shouldn't do.

I just discovered there's also this [data-hovercard-z-index-override] attribute, but you are right it won't help.

this also breaks on GitHub's own menu

We can only hope that they will update the hovercard soon. In their case however the user doesn't need to see the link while that popup is open.
Before this PR: The user has to close the symbols sidebar to use it
After this PR: The user cannot see the link they're hovering.
I'll close this PR for now because I found a fix for that specific issue. It'd be great to leave a comment in list-prs-for-file to mention this PR for future upgrades, so that we don't forget it

@kidonng wanna retry this? I found this class in the source code: js-hovercard-left
Before (below)

After (left)

Thank you by the way! 🙏


Consider renaming GetTestConfiguration in functional tests

This is doing some important stuff, its fairly misleading as it stands today, perhaps something more like ConfigureFunctionalTests()

Not worth doing


Discuss how we should react when availability API is down.

When SCSB's availability API is down or times out...we have a few options.
We can:

"null out" availability info in our response.
Trust the last availability information we got from ElasticSearch
Mark items we know to be dubious as possibly out of date and signal that in the UI.

This may be out of scope for this release but I wanted to record the conversation here.
CCing: @natalietsch, @nonword, @kfriedman, @jobinthomasnypl

This is in Jira here: https://jira.nypl.org/browse/SRCH-39


cant get ol.source to redraw tiles on tileurl changed when view projection is diffrent then source projection

I have a ol source that based on a menu changes the tile url:
                           if (oldUrl !== url) {
                                oldUrl = url;
                                source.setTileUrlFunction((coord, a, p) => url.replace("{Z}", coord[0].toString()).replace("{X}", coord[1].toString()).replace("{Y}", (-coord[2] - 1).toString()));
                                source.changed();
                                source.refresh();
                            }

this works well when the view projection is the same as the source projection, but when a different view projection is used - the layer wont redraw before zooming to a new tile layer.
Is this by design or a bug that we can fix?

Sounds like a bug. Looks like reprojected tile caches are not cleared when the source changes. Do you want to try to fix it?

If its easy for someone else that knows exactly what to to, i dont mind not doing it :) But if time permits and no one else has done it before the weekend, i will give it some hours to try :)

Actually, this seems to be happening even when projection is the same.
I tried to follow the code and it could track it down to the point that source's canExpireCache returns true and scheduleExpireCache on the ol.renderer.Layer is called but this postRenderFunction never gets called. @ahocevar Any suggestion on what might be going on here and where to look further?

@igorti Does setting loadTilesWhileAnimating: true and loadTilesWhileInteracting: true on the map fix the issue for you?

@ahocevar No, unfortunately it doesn't help. It might still be a cache issue, since I noticed that explicitly calling source.tileCache.clear() does trigger tile reload. I guess it's not ideal though since accessing tileCache object is internal API only.

@igorti Out of curiousity: Does 5e3d522dfa9276dd8978fcef33c31ba59c623d56 fix your problem?

@ahocevar That commit doesn't seem to make any difference. But! Now that I was setting up a simplified example in Codepen for you, I came to realise that this problem is probably due to how I was changing source's url. I was composing it in the getTileUrl function and I was changing the url by setting some member variables that getTileUrl would then use and call refresh to trigger reload. I changed the code to set new url with setUrl method and it works perfect now. Sorry for hijacking this thread as it's probably not related to @pksorensen issue as I thought it was.

I face the same problem as @igorti described. When I had a tile source url updated via setUrl method the tiles were refreshing fine, but as soon as I utilized tileUrlFunction they won't update once loaded. If my url has changed and I  zoom the map then new tiles are loaded from the new url but zooming back to the original zoom level won't update the tiles (no call to  'tileUrlFunction' happens). Calling source.changed() method does increase the revision counter but won't update the tiles. Calling source.refresh() method does refresh the map but as far as notice visually it first clears the cache and then fetches new tiles. So probably it is something related to the cache.

Important to notice that my view and source projections are the same.


Update helpers.php, remove goto statement

The goto statement can make the code's flow difficult to follow. PHP code is typically expected to have a more linear and understandable structure. For example, when using goto, it can jump from one part of the code to another in a non - sequential manner. This can lead to confusion for developers who are trying to understand the program's logic, especially in larger codebases.

https://github.com/igorw/retry/issues/3


GranTurismo7 Support

Hey Alexander,
first of all thank you very much for the great work!!!!
Do you think it would be possible to get GT7 work in Grafana Dashboards?
I´ve already opened UDP port 33740 in SimHub so i get some data from GT7 and can show them on a SimHub Dashboard.
So it should be possible to integrate that into Grafana right?
Any help would be appreciated
thanks

Hm. This plugin does not have support of Gran Turismo yet. It should not be too complicated to add it, but I do not have PS and cannot test it out. I'll keep it here as a feature request, maybe someone could implement it.

Hi, I discovered this Grafana plugin and I have a PS5, so I'm working on adding GT7 support in my fork. For now, I'd say the bare bones are finished.
What remains to be done (roughly):

Top priority: make the PS IP address configurable, either from the data source itself or from the docker compose file through an environment variable
EV support (would be helpful to find a way to change units dynamically in Grafana)
Additional flags decoding and visualisation (like TCS, ABS flags)
A better lap implementation overall (like better conversion of laptimes)
A smarter dashboard that can use the CarID and the maximum revs sent by GT7

I'll create a PR when it'll be ready.
Dashboard prototype

This is running on a Raspberry Pi 2 using Docker Compose. Fuel remaining is 100 since I was in a time trial without fuel consumption. The % near each wheel is a tyre slip ratio in percentage, calculated as tyre speed / car speed.


[feat] Add xopconsole - human & machine readable logger

Add the xopconsole base logger. xopconsole support replay and tries to be human-readable.

Codecov Report
Attention: 432 lines in your changes are missing coverage. Please review.

Comparison is base (0a9ba53) 76.45% compared to head (54f087d) 76.31%.

Files
Patch %
Lines

xopconsole/replay.go
60.64%
251 Missing and 91 partials :warning:

xopconsole/attributes.go
92.95%
25 Missing and 11 partials :warning:

xopconsole/console.go
88.14%
25 Missing and 7 partials :warning:

xopproto/extra.go
0.00%
20 Missing :warning:

xopconsole/builder.go
95.12%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #100      +/-   ##
==========================================
- Coverage   76.45%   76.31%   -0.15%
==========================================
  Files          65       68       +3
  Lines        9426    11153    +1727
==========================================
+ Hits         7207     8511    +1304
- Misses       1819     2133     +314
- Partials      400      509     +109

Flag
Coverage Δ

go_tests
76.31% <75.11%> (-0.15%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Is MjmlToJson removed from easy-email-core?

I am using this MjmlToJson to upload Mjml file to create template in the web-browser. But t says there is nosuch function in easy-email-core

That's found in the easy-email-extensions


Updated build dependencies and fixed a version issue with zero clipboard

I updated the build dependencies and verified it's working as expected. I also fixed a version issue in the source. Can we get a new release with this version fix out..
I noticed that there was never a karma.config so the tests fail (there are no tests).

LGTM, thanks @niemyjski I'll be using your fork for now


MAINT: Work around conda/joblib bug

Just a workaround for these errors in master until conda/travis/joblib updates (not sure whose fault it is) to fix them:
https://travis-ci.org/mne-tools/mne-python/jobs/586892855
Haven't tried to isolate the problem but basically all n_jobs > 1 tests fail on one build.

It's probably caused by a regression introduced in intel-openmp=2019.5. I am working on a minima reproduction example to file to anaconda.

Awesome, thanks for digging into it @ogrisel

FYI https://github.com/ContinuumIO/anaconda-issues/issues/11294

+1


How to handle fs.stat error on a file?

There are two potential error cases at present:

ENOENT: null is returned rather than stat. This would cause an unhandled exception if it were ever encountered (i.e. the file is deleted between fs.readdir and fs.stat). However, it is unlikely that any one will ever encounter this error and much less likely that they will be able to repeat it to know what happened and submit a bug.
Other errors (EPERM, etc). These are currently handled by passing the error to express and causing a 500 error.

ENOENT
In the first case I think we should just filter out the file.
If it's been deleted (or is otherwise a special type of file, such as a virtual file on fuse fs, which is returned from fs.readdir() but doesn't exist when you fs.stat()), why bother to show it? And why error out?
Other Erorrs
I disagree with the current behavior. For one, it's inconsistent between text/plain and application/json responses (work) and text/html responses (fail).
I think we should instead provide a stat object that looks like this:
{ "name": "foo.txt"
, "size": 0
, "lastModified": "1970-01-01T00:00:00.000Z"
, "type": "error/EPERM"
}

(or maybe something more conventional liketype: application/vnd.eperm+x-error)
Or perhaps omit the file.
In any case, I don't think that the current behavior of throwing a 500 on any single potential permission error is good behavior.

Yea, I believe there were some issues opened up about this in the past but no PRs ever materialized. I would except it to do the same thing that the Apache HTTPD index view does in this case, which I assume is either hide it or display it without additional metadata.

And also agree that all the three views should behave in the same way.

I don't know how Apache handles it, so how about we just hide it for now (most secure) and circle back around to it if there's a complaint.
Once we get https://github.com/expressjs/serve-index/pull/74 taken care of I'll come back around to this and update the PR.

We have time now to do it right :) waiting until later is unnecessarily churn. I can look at apache httpd and report back to see what it does and then we can decide how to love forward :+1:
Bringing up security means it is even more imparitive to validate our implementation against one that has been reviewed many times, or alternatively we can see if a security researcher can take a look at our design here :+1:


MechJeb2-dev causes CKAN to upgrade MechJeb2-release and crash on Windows GUI

Due to the <    "provides" : [         "MechJeb2"     ] > in NetKAN's metadata the CKAN suggests an update for MechJeb2, which doesn't exist:

and then crashes when I try to do the update giving "CKAN.InconsistentKraken" exception.

After the last update (1.8.1) the issue was mostly fixed; although CKAN still provides an option for an upgrade, the MechJeb doesn't show up in the "Changeset" tab, thus allowing other mods to upgrade.
However, when no other mods` upgrades are available, if MechJeb2 is selected for upgrading, the "Changeset" tab appears blank with no mods and non-functioning buttons at the bottom. No CKAN crashes here, though.


Unable to open swagger interface after deploying openfga container

I am running openfga container in my local machine. I am trying to browse the swagger interface to see what all endpoints available. But I am not sure of the url which needs to be used.
I tried with http://localhost:8080/api/service and http://localhost/swagger/index.html
Can anyone please help ?

Hi @sasanknvs! We currently do not expose an endpoint from the OpenFGA server with the Swagger file. Is this a feature that you'd be interested in?

When I browse through this link I see a Swagger interface already. I was trying to understand if that was already present in the openfga image ? If yes, where is the URL for that ?

@sasanknvs - As @miparnisari mentioned we do not yet serve the OpenAPI specification from the server at the moment. I agree this would be a nice addition. We should have a well-known endpoint serving the OpenAPI spec. That being said, if you're using the gRPC API we do expose gRPC server reflection. If you're using a tool like Postman or something similar, you can generate sample gRPC requests by using the reflection protocol.

I think this feature would be a great addition. It would help to test and learn locally how the endpoints work. Is this in the current roadmap?
Thanks


Edit "master language" and "ignore files" in repo setting

Is there a particular reason why that's no possible or something that just missing?
https://docs.abapgit.org/ref-dot-abapgit.html

ignore files can be added via the staging page, but currently no edit functionality. Except for changing the file manually in git
if someone changes the master language I think it can cause a lot of problems for the user

how about ML in read-only and a textarea for the ignored files?

sure


What to do about tweepy?

So tweepy may now be unmaintained: https://github.com/tweepy/tweepy/issues/2099#issuecomment-1529153771 . Ugh. granary's Twitter support is more or less unmaintained now too, so I wouldn't care, except an abandoned tweepy is now blocking some of our dependency upgrades, eg #700. Hrm. What to do?

The hawk-ish answer here is to drop granary's Twitter/X support.


Everyday ask you when will your code be available?

Prince Dubai like your code and want it open source

I like it, too.


Advertise a _http._tcp. Bonjour service

Is your feature request related to a problem? Please describe:
I often forget what port the config page is running on. I’ve got a bookmark on one of my computers but sometimes need to access it from other computers.
Describe the solution you'd like:
Since this vends an HTTP page on a nonstandard port it would be great if it advertised an _http._tcp. Bonjour service. I don’t know if any mainstream browsers still display _http._tcp. services in their UI, but it at least gives me a convenient way to look it up with other tooling.
Preferably it would either reuse the same multicast-dns server that Homebridge itself does, or use the underlying system’s implementation (mDNSResponder on macOS, Avahi on Linux). I suppose setting up a new multicast-dns server in this plugin isn’t the end of the world, but that adds complexity like needing to send goodbye packets and whatnot (bonjour-hap doesn’t currently do that but I have an open ticket on them to add it). Of course, reusing Homebridge’s server would require Homebridge providing access to it.

It would be great to have this as a built-in feature. My current workaround, with a vanilla Raspbian installation, is to create /etc/avahi/services/homebridge.service with the following contents:
<?xml version="1.0" standalone='no'?><!--*-nxml-*-->
<!DOCTYPE service-group SYSTEM "avahi-service.dtd">

<service-group>
  <name replace-wildcards="yes">%h Homebridge</name>
  <service>
    <type>_http._tcp</type>
    <port>8581</port> <!-- nb: replace with the port your instance is configured to run on -->
  </service>
</service-group>

Running sudo service avahi-daemon reload then publishes the mDNS record.

I will do this once homebridge/ciao is out of beta.
https://github.com/homebridge/ciao

Is homebridge/ciao still considered beta?


Feature/maintenance

Context
https://enrise.atlassian.net/browse/SAAS-1008
What has been done

Update dependencies
Add note about ajv and chai-json-schema-ajv to the readme
Remove people from maintainer list that no longer want to be a maintainer

How to test

Check the travis builds still work
Use the new version in our tests

Todo

[ ] Upgrade the version number

Notes

I saw we don't use a package-lock.json in this repo. This is probably okay since this is intended a package but it feels a bit weird.

FWIW if you, or @up9cloud or anyone else wants to pick up maintenance of this module and move it to using ajv I'd happily set you up to do so. More-so if anyone wants to merge the efforts of chai-json-schema-ajv into this I'd be happy to also do that.
There is no resistance to using ajv over tv4 - it is just we're very limited on maintainer-ship. If people are happy to work on this project, I'm more than happy to hand the keys over 😄

Thank you for your feedback @keithamus
We definitely also support efforts for merging the two, but haven't got the time, nor the project-driven motivation for such.
That said we will try to keep this plugin at the level where it is, and welcome any PR's.

Since I have no offical role/permissions in this repo I can't merge this merge request. @edwardsmit please merge. :)

I forgot to version a new version. Now I did :/


Payload nonce doesn't get updated on authorizationToken state change

When I submit a form for the second time, I'm getting the same payload as the one in the previous state.
On the first submission, I fetch the clientToken from the backend for the second time and set the authorizationToken state to the new token.

Hello,
I can't reproduce this behavior with braintree-web-drop-in (1.9.2) and braintree (2.4.0)


What is the point of cleanCookies function in utils.ts?

I was looking at the source code at this function in utils.ts:
export function cleanCookies() {
document.cookie.split(';').forEach(function(c) {
document.cookie = c
.replace(/^ +/, '')
.replace(/=.*/, '=;expires=' + new Date().toUTCString() + ';path=/');
});
}
It's not used anywhere except in a test, Cookies-test.js, where it is run in a beforeEach block in a Jest describe block. Why does that function exist?

It is only used within the tests to clean all cookies before performing a new test. It is necessary to make sure something from a test doesn't leak into the next one.
I'm not sure what's the confusion?

My bad, ok, I was confused because the tests pass without the beforeEach, and I thought document.cookie wasn't being used anywhere, but it is in the Cookies class.


How to get more than 100 rows using Airtable API using offest?

I am really new to the Airtable API and for some reason getting data from the API this way did not work.
``
from airtable import airtable
at = airtable.Airtable('Base_Key', 'Airtable_Key')
records = at.get_all(maxRecords=20)
``

Error : AttributeError: 'Airtable' object has no attribute 'get_all'

But I got it working this way -
``
import_ json
import requests
get_url = ‘https://api.airtable.com/v0/BASE_ID/TABLE_NAME’
get_headers = {
‘Authorization’: ‘Bearer API_KEY’ }
Response = requests.get(get_url, headers=get_headers)
Response_Table = Response.json()
``
However, this fetches only the first 100 records and am reading about offset and pagination but I am unable to figure how to incorporate it into this code.
I am using Python 3 on Jupyter Notebook
Thank you for the time!

see library docs for get_all or get_iter


Docs: #30 README Created for Daddy-Laugh

I have added a README file for Daddy-Laugh which includes the following:
~ Introduction
~ Requirements
~ Use Case
~ Features
~ Contribution
~ Credits
~ License

Seems perfect, just add a section for 'built-with' and we're good to go


Compare mapping inventory datatypes to v251 datatypes

User Story
As an engineer I want to know that all datatypes used by v251 and v251-elr mappings align with the specification so that we do not mis-map or leave out data.
Description/Use Case
The mapping inventory mixed datatypes from multiple versions of HL7 (v.2.5.1, v2.7, v2.9). The mappings for v251 should not use elements from v2.7 or v2.9. This is especailly important as the NIST mappings use the base v251 mapping which currently also include mapping for v2.7 or v2.9. Further, the mapping for RADx MARS will also rely on the base v251 mappings.
Dev Notes
Compare the data types from the NIST site (https://hl7v2-elr-testing.nist.gov/mu-elr/) to the mapped datatypes in metadata/HL7/datatypes/v251/hl7/datatypes. Only the regular datatypes need to be compared(i.e. the datatypes that do not end with _ELR).
Acceptance Criteria

[ ] datatypes in metadata/HL7/datatypes/v251/hl7/datatypes mirror the specification at https://hl7v2-elr-testing.nist.gov/mu-elr/

#13798


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 1254 ms

Resolved: Bofrost.at performance has improved in 6adad64 after 6 minutes.


Stops working on Omega protocol P5

Description
Stops working on Omega protocol P5
Additional Details / Steps to Reproduce
Timeline and alerts works perfectly fine, until I reach P5 in the omega protocol, then it just dissapears. No timeline, and no alerts. This has happened consistently over serveral game sessions. I have not edited the timeline, and I have english language on everything. before reaching P5 it works perfectly every time
Cactbot Module
Raidboss (alerts & timelines)
Configuration Info
Plugin Name          Enabled Version  Path
----------------------------------------------------------------------------------------------------------------------------------------
FFXIV_ACT_Plugin.dll True    <IP_ADDRESS>  C:\Program Files (x86)\Advanced Combat Tracker\FFXIV_ACT_Plugin.dll
OverlayPlugin.dll    True    0.19.29  C:\Users\Vegard\AppData\Roaming\Advanced Combat Tracker\Plugins\OverlayPlugin\OverlayPlugin.dll
CactbotOverlay.dll   True    <IP_ADDRESS> C:\Users\Vegard\AppData\Roaming\Advanced Combat Tracker\Plugins\cactbot\cactbot\CactbotOverlay.dll
Triggernometry.dll   True    <IP_ADDRESS>  C:\Users\Vegard\AppData\Roaming\Advanced Combat Tracker\Plugins\Triggernometry.dll

Overlay Name URL
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Overlay      https://haeruhaeru.github.io/mopimopi/?HOST_PORT=ws://<IP_ADDRESS>/fake/
Timers       file:///C:/Users/Vegard/AppData/Roaming/Advanced%20Combat%20Tracker/Plugins/cactbot-0.23.6/cactbot/ui/raidboss/raidboss.html?timeline=1&alerts=0
others test  https://zeffuro.github.io/ZeffUI/
Alerts       file:///C:/Users/Vegard/AppData/Roaming/Advanced%20Combat%20Tracker/Plugins/cactbot/cactbot/ui/raidboss/raidboss.html?timeline=0&alerts=1

Various Settings                                Value
--------------------------------------------------------------------------------------------------------------------------------------------
Plugin Language                                 English
Machina Region                                  Global
Game Version                                    2<IP_ADDRESS>0.0000
Screen Mode                                     Borderless Windowed
ACT Process Elevation                           Elevated (Admin)
FFXIV Process Elevation                         Not Elevated
Inject and use Deucalion for network data       True
Hide Chat Log (for privacy)                     False
Use WinPCap-compatible library for network data False
Disable high-performance network filter         False
Disable Combine Pets with Owner                 False
Disable Damage Shield estimates                 False
(DEBUG) Enable Debug Options                    False
(DEBUG) Log all Network Packets                 False
(DEBUG) Also Show 'Real' DoT Ticks              False
(DEBUG) Simulate Individual DoT Crits           False
(DEBUG) Graph Potency, not Damage               False
(DEBUG) Enable Benchmark Tab                    False
Cactbot User Dir                                C:\Users\Vegard\AppData\Roaming\Advanced Combat Tracker\Plugins\cactbot-0.23.6\cactbot\user\

Log & Screenshots
No response
Confirmation

[X] I reviewed  Common Issues and Workarounds and verified that my settings are correct.
[X] I used the search function to confirm this issue doesn't already exist.

Your Alerts overlay has the correct URL (.../Plugins/cactbot/cactbot/ui/...), but your Timers overlay does not (.../Plugins/cactbot-0.23.6/cactbot/ui/...).
In addition, your Cactbot User Dir is also pointing at the wrong folder and should be updated (and any associated custom user JS/CSS moved over).
As for why TOP itself might be desyncing, the only change to triggers was over 5 months ago, and the only change to timelines was an order adjustment for one of the branches in P5 which wouldn't impact syncing or triggers.
https://github.com/OverlayPlugin/cactbot/commit/8a680429b0d012b922528acf66f612b0f4153dfa#diff-c5150792ce5233e5e5fea58f1d109930ee748977e873a94461c37f44e212c20c

If fixing your overlay and user dir paths doesn't resolve the issue, can you upload a log file (split via https://overlayplugin.github.io/cactbot/util/logtools/splitter.html, feel free to use the anonymizer option on the splitter) and a dev can review?

That's a bit awkward. I haven't used it in a long time until recently, so I removed the plugin before reinstalling it, guess it wasn't as much of a clean install as I thought...
Anyways that solved the problem, thank you very much!
Not sure if it was TOP specific, I don't use it elsewhere. I read somewhere something about changing the ID's of the P5 bosses, so my guess is that it could have had something to do with that?

That's a bit awkward. I haven't used it in a long time until recently, so I removed the plugin before reinstalling it, guess it wasn't as much of a clean install as I thought...

There was a change made a while ago to remove the version number from the path specifically to resolve this sort of issue in the future, but there's not a good way to handle changing to the correct path automatically because the update process that actually extracts to the folder is controlled by ACT itself, not cactbot.
You're not the first person to have this issue, most of those users get their problem resolved on the discord #troubleshooting channel.

Not sure if it was TOP specific, I don't use it elsewhere. I read somewhere something about changing the ID's of the P5 bosses, so my guess is that it could have had something to do with that?

Referencing the older path can cause all sorts of strange issues, so I'm not sure exactly what was causing TOP P5 specifically to fail, but I'm glad that this resolved the problem for you.


[Implementation]

C++
		if (config.weapon) {
			interfaces.surface->setTextFont(Surface::font);
			const auto activeWeapon = interfaces.entityList->getEntityFromHandle(entity->getProperty<int>("m_hActiveWeapon"));
			auto weaponIndex = getWeaponIndex(activeWeapon->getProperty<WeaponId>("m_iItemDefinitionIndex"));
			if (!weaponIndex)
				return;
			std::wstring gap{ std::to_wstring(static_cast<int>(weaponIndex)) };
			const auto [width, height] = interfaces.surface->getTextSize(Surface::font, gap.c_str());
			interfaces.surface->setTextColor(config.weaponColor, 255);
			interfaces.surface->setTextPosition(bottom.x - width / 2, bottom.y - height /2 + 5);
			interfaces.surface->printText(gap.c_str());
		}

These are the codes for my weapon esp which is not complete as it shows weapon index instead of weapon and should be limited to just weapon and nades.
My question is how do i actually render weapons tho and nades.
Using if statements didn't work. or maybe @danielkrupinski could implement this better.
:)

I haven't yet implemented nades into my fork's weapon name esp, but here's how I did the weapon names:
(please note, this is most likely a godawful way of doing this, but no one's commented so i figured i'd try and help; plus i dont suffer any hitches nor crashes, and my computer is an actual potato)
Inside nSkinz/item_definitions.hpp, inside the game_data namespace:
constexpr weapon_name weapon_namesArray[]{
	{0, ""},
	{1, "Desert Eagle"},
	{2, "Dual Berettas"},
	{3, "Five-SeveN"},
	{4, "Glock-18"},
{5,""},
{6,""},
	{7, "AK-47"},
	{8, "AUG"},
	{9, "AWP"},
	{10, "FAMAS"},
	{11, "G3SG1"},
{12,""},
	{13, "Galil AR"},
	{14, "M249"},
{15,""},
	{16, "M4A4"},
	{17, "MAC-10"},
{18,""},
	{19, "P90"},
{20,""},
{21,""},
{22,""},
	{23, "MP5-SD"},
	{24, "UMP-45"},
	{25, "XM1014"},
	{26, "PP-Bizon"},
	{27, "MAG-7"},
	{28, "Negev"},
	{29, "Sawed-Off"},
	{30, "Tec-9"},
	{31, "Zeus"},
	{32, "P2000"},
	{33, "MP7"},
	{34, "MP9"},
	{35, "Nova"},
	{36, "P250"},
{37,""},
	{38, "SCAR-20"},
	{39, "SG 553"},
	{40, "SSG 08"},
	{41,"Golden Knife"},
	{42,"Knife"},
{43,""},
{44,""},
{45,""},
{46,""},
{47,""},
{48,""},
	{49,"C4"},
{50,""},
{51,""},
{52,""},
{53,""},
{54,""},
{55,""},
{56,""},
{57,""},
{58,""},
	{59,"Knife"},
	{60, "M4A1-S"},
	{61, "USP-S"},
{62,""},
{63,""},
	{64, "R8 Revolver"},
	};

Inside Esp.cpp:
if (config.weaponName) {
	auto activeWeapon = interfaces.entityList->getEntityFromHandle(entity->getProperty<int>("m_hActiveWeapon"));
	if (!activeWeapon)
		return;
	std::wstringstream wepName;
	wepName << game_data::weapon_namesArray[activeWeapon->getProperty<int>("m_iItemDefinitionIndex"), activeWeapon->itemDefinitionIndex()].name;

	renderPositionedText(wepName.str().c_str(), config.weaponNameColor, { bottom.x + boxWidth + 5, drawPositionY });
}

Sorry to have made you see this lmao
If you want to add nades, change ".name" in Esp.cpp to ".definitionIndex" and it will give you the numbers, then you just add them to weaponNameArray at their corresponding IDs


Bump typing-extensions dependency to >= 4.6.0 to fix import name issue in azure-servicebus

Description
Fixes "ImportError: cannot import name 'Buffer' from 'typing_extensions'" as described in this issue https://github.com/Azure/azure-sdk-for-python/issues/34868
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

@YaroBear please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree

/azp run python - servicebus - tests

Hi @YaroBear - Thanks for your contribution!! We'll merge this after tests pass!

/check-enforcer override


track https://github.com/rzeigler/waveguide-streams/issues/1

track https://github.com/rzeigler/waveguide-streams/issues/1

flacky because dependent on system clock, no troubles.


Edit article

A page was created to manage Post edition, and validating delete current image before update or delete a Post


To do list at the start

We need to create a mostly empty structure that will allow us to fill in with specific code

first objective: create a code that can compile and run

2e-8!!


JOSS Review "Automated tests" [Blocker]

There is no mention of tests, or how to run the tests in the documentation. Also the level of test coverage for this package is unknown

Added: "Requires installation of nose package. Tests are located in the forestci/tests folder and can be run with the nosetests command in the main directory" to README

Closed through #52


Fix failing build on main branch

Test name
Status

We run 0 out of 35

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1135/commits/0d66844008be3b54b14d78017ad3960134767f5e
image: perconalab/percona-xtradb-cluster-operator:PR-1135-0d668440


feature(formyField): Added support for fields with multiple elements having ngModels.

Closes: #275

Thanks for working on this. I think I'll make it a part of a beta release once you've adjusted some of the stuff and it's merged (probably Monday). Just because I'm not certain about how it will/should behave... Would like to get some feedback on the API.

Hey @ckniffen, so, just to verify, is this PR what you want it to be? I haven't had a chance to pull it down yet, but I want to verify with you that you think this is the best way (rather than the directive approach).

I think this is still the best way.  The only thing I don't yet know about is how to approach the digest.  Do we make it a breaking change or do the hacky thing of calling digest is one isnt running already?

Hmmm, yes... Good question... I'm thinking that we do the hacky thing. It's not awesome, but I think it's the best thing to do in this scenario.

I will make the change.

The update is there I think everything is now good to go.

Awesome! Thanks a ton. This is way cool!

By the way, thank you sooooo much for squashing this into a single commit. Makes the git history sooo much cleaner :+1:


Job executing with out of range IP

Hi All
After whitelisting the ranges (for all geographies) in the document we were still having issues with an inbound connection from Azure Devops. When running checks from the pipeline the external IP address being reported is: <IP_ADDRESS> which isn't within a valid range in this json file: https://www.microsoft.com/en-us/download/details.aspx?id=56519. I have checked and it is a Microsoft IP so should it's range be included as well.
Thanks
Ali

@thegrew Thanks for your question.
It looks like you've encountered an issue with the product itself (in the json file), rather than an issue with the documentation. To make sure it gets in front of the right people, please submit your bug here.


Error on deploy mariadb-cluster:10.3.26

Hi Nickolay,
I tried to deploy the Maria Cluster:
./anydbver deploy mariadb-cluster:10.3.26
But it is throwing this error:
fatal: [vinicius.grippa.default]: FAILED! => {"changed": false, "msg": "Failure downloading https://archive.mariadb.org/mariadb-10.3.26/yum/centos7-amd64/rpms/galera-25.3.31-1.rhel7.el7.centos.x86_64.rpm, HTTP Error 404: Not Found"}
Checking the repo and the only available for 25.3.31 is galera-25.3.31-1.el7.centos.x86_64.rpm.

MariaDB finally removed rhel7 from galera package name. Added a condition to support both new and old naming


Add Forward-Forward algorithm tutorial

The Forward-Forward .ipynb notebook was uploaded to the examples folder and the table in tutorials.rst was updated.

This is great. I'll go through this in more detail before merging in the next couple of days but it is already in great shape.


Complete _oasis to synchronized it with the OPAM package

This allows to generate the OPAM files with oasis2opam — the dev version (to be released soon).  Some dependencies that I added may not be necessary (but they were present in OPAM..., feel free to remove them and regenerate the OPAM file — another reason why automation is nice!).
Note that the license in _oasis and OPAM differ.

thanks


Update colours for improved readability of questions

Update the base set of colours for improved readability.
Other colours can be used by others to tailor the colours as preferred, via a dedicated branch or fork.

Completed


[Snyk] Security upgrade com.amazonaws:aws-java-sdk from 1.12.257 to 1.12.272

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `maven` dependencies of this project.
:sparkles: Snyk has automatically assigned this pull request, set who gets assigned.
As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

uasdm-server/pom.xml

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

611/1000  Why? Recently disclosed, Has a fix available, CVSS 6.5
Directory Traversal SNYK-JAVA-COMAMAZONAWS-2952700
com.amazonaws:aws-java-sdk:  1.12.257 -> 1.12.272
No
No Known Exploit

399/1000  Why? Has a fix available, CVSS 3.7
Information Exposure SNYK-JAVA-COMMONSCODEC-561518
com.amazonaws:aws-java-sdk:  1.12.257 -> 1.12.272
No
No Known Exploit

489/1000  Why? Has a fix available, CVSS 5.5
Information Exposure SNYK-JAVA-IONETTY-2812456
com.amazonaws:aws-java-sdk:  1.12.257 -> 1.12.272
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
👩💻 Set who automatically gets assigned
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Directory Traversal

Updated in another PR


Improve Dependency Processing

Cache the filtered files to speed up changed dependencies per example.
Also, do not compute diff when the last example and current example coverage
is the same for a given file.

@CodiumAI-Agent /review

PR Analysis

🎯 Main theme: Improving dependency processing in RSpecTracer
📝 PR summary: This PR introduces improvements to the dependency processing in RSpecTracer. It includes caching of filtered files to speed up changed dependencies per example and prevents unnecessary computation of diffs when the last and current example coverage is the same for a given file. It also changes the JSON generation method to pretty_generate for better readability.
📌 Type of PR: Enhancement
🧪 Relevant tests added: No
⏱ Estimated effort to review [1-5]: 3, because the PR includes changes to several files and introduces new logic in the code, which requires a thorough understanding of the existing codebase to review effectively.
🔒 Security concerns: No security concerns found

PR Feedback
💡 General suggestions: The PR is well-structured and the changes are logically grouped. However, it would be beneficial to add tests to verify the new behavior and ensure that it doesn't break any existing functionality.
 🤖 Code feedback:relevant filelib/rspec_tracer/coverage_reporter.rbsuggestion
Consider extracting the logic inside compute_diff method into a separate method for better readability and maintainability. [medium]
relevant linenext if current_stats == @coverage[file_path]relevant filelib/rspec_tracer/runner.rbsuggestion
It would be better to add a comment explaining the purpose of the filtered_files Set and how it improves performance. [medium]
relevant linefiltered_files = Set.newrelevant filelib/rspec_tracer/reporter.rbsuggestion
Instead of manually calling JSON.pretty_generate on each report, consider creating a helper method that writes the report to a file with pretty JSON formatting. This would reduce code duplication. [important]
relevant lineFile.write(file_name, JSON.pretty_generate(@all_examples))relevant filelib/rspec_tracer/runner.rbsuggestion
The register_file_dependency method could benefit from a brief comment explaining its purpose and functionality. [medium]
relevant linedef register_file_dependency(example_id, file_path)

 ✨ Usage guide:
Overview:
The review tool scans the PR code changes, and generates a PR review. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on any PR.
When commenting, to edit configurations related to the review tool (pr_reviewer section), use the following template:
/review --pr_reviewer.some_config1=... --pr_reviewer.some_config2=...

With a configuration file, use the following template:
[pr_reviewer]
some_config1=...
some_config2=...

  Utilizing extra instructions
The review tool can be configured with extra instructions, which can be used to guide the model to a feedback tailored to the needs of your project.
Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify the relevant sub-tool, and the relevant aspects of the PR that you want to emphasize.
Examples for extra instructions:
[pr_reviewer] # /review #
extra_instructions="""
In the code feedback section, emphasize the following:
- Does the code logic cover relevant edge cases?
- Is the code logic clear and easy to understand?
- Is the code logic efficient?
...
"""

Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

  How to enable\disable automation

When you first install PR-Agent app, the default mode for the review tool is:

pr_commands = ["/review", ...]

meaning the review tool will run automatically on every PR, with the default configuration.
Edit this field to enable/disable the tool, or to change the used configurations

  About the 'Code feedback' section
The review tool provides several type of feedbacks, one of them is code suggestions.
If you are interested only in the code suggestions, it is recommended to use the improve feature instead, since it dedicated only to code suggestions, and usually gives better results.
Use the review tool if you want to get a more comprehensive feedback, which includes code suggestions as well.

  Auto-labels
The review tool can auto-generate two specific types of labels for a PR:

a possible security issue label, that detects possible security issues (enable_review_labels_security flag)
a Review effort [1-5]: x label, where x is the estimated effort to review the PR (enable_review_labels_effort flag)

  Extra sub-tools
The review tool provides a collection of possible feedbacks about a PR.
It is recommended to review the possible options, and choose the ones relevant for your use case.
Some of the feature that are disabled by default are quite useful, and should be considered for enabling. For example:
require_score_review, require_soc2_review, enable_review_labels_effort, and more.

  More PR-Agent commands

To invoke the PR-Agent, add a comment using one of the following commands:

/review: Request a review of your Pull Request.
/describe: Update the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
/ask <QUESTION>: Ask a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.
/add_docs 💎: Generate docstring for new components introduced in the PR.
/generate_labels 💎: Generate labels for the PR based on the PR's contents.
/analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component.

See the tools guide for more details.
To list the possible configuration parameters, add a /config comment.

See the review usage page for a comprehensive guide on using this tool.

PR Review

 ⏱ Estimated effort to review [1-5]
2, because the changes are straightforward and mostly involve refactoring and performance improvements. The logic is clear, and the modifications are well-contained within specific methods.

 🧪 Relevant tests
No

 🔍 Possible issues
Performance Concern: The use of JSON.pretty_generate instead of JSON.generate might introduce a performance overhead due to prettifying the JSON output. This could be significant depending on the size of the data being processed.

 🔒 Security concerns
No

 Code feedback:
relevant filelib/rspec_tracer/coverage_reporter.rb
suggestion

Consider adding a direct comparison for the @coverage[file_path] and current_stats to avoid unnecessary processing for files that haven't changed. This could further optimize the performance by reducing the number of method calls. [important]

relevant linenext if current_stats == @coverage[file_path]
relevant filelib/rspec_tracer/runner.rb
suggestion

Instead of checking filtered_files.include?(file_path) for every file path, consider using a more efficient data structure or algorithm to reduce the computational complexity. This could potentially improve the performance when processing a large number of files. [medium]

relevant linenext if filtered_files.include?(file_path)
relevant filelib/rspec_tracer.rb
suggestion

Evaluate the necessity of using JSON.pretty_generate for the coverage report files. If human readability is not a requirement, switching back to JSON.generate could improve file writing performance. [important]

relevant lineFile.write(file_name, JSON.pretty_generate(report))
relevant filelib/rspec_tracer/reporter.rb
suggestion

For consistency and to avoid potential issues, ensure that all JSON writing operations either use JSON.generate or JSON.pretty_generate based on the performance and readability requirements. [medium]

relevant lineFile.write(file_name, JSON.pretty_generate(@all_examples))

 ✨ Review tool usage guide:
Overview:
The review tool scans the PR code changes, and generates a PR review. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on any PR.
When commenting, to edit configurations related to the review tool (pr_reviewer section), use the following template:
/review --pr_reviewer.some_config1=... --pr_reviewer.some_config2=...

With a configuration file, use the following template:
[pr_reviewer]
some_config1=...
some_config2=...

  Utilizing extra instructions
The review tool can be configured with extra instructions, which can be used to guide the model to a feedback tailored to the needs of your project.
Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify the relevant sub-tool, and the relevant aspects of the PR that you want to emphasize.
Examples for extra instructions:
[pr_reviewer] # /review #
extra_instructions="""
In the 'possible issues' section, emphasize the following:
- Does the code logic cover relevant edge cases?
- Is the code logic clear and easy to understand?
- Is the code logic efficient?
...
"""

Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

  How to enable\disable automation

When you first install PR-Agent app, the default mode for the review tool is:

pr_commands = ["/review", ...]

meaning the review tool will run automatically on every PR, with the default configuration.
Edit this field to enable/disable the tool, or to change the used configurations

  Auto-labels
The review tool can auto-generate two specific types of labels for a PR:

a possible security issue label, that detects possible security issues (enable_review_labels_security flag)
a Review effort [1-5]: x label, where x is the estimated effort to review the PR (enable_review_labels_effort flag)

  Extra sub-tools
The review tool provides a collection of possible feedbacks about a PR.
It is recommended to review the possible options, and choose the ones relevant for your use case.
Some of the feature that are disabled by default are quite useful, and should be considered for enabling. For example:
require_score_review, require_soc2_ticket, and more.

  Auto-approve PRs
By invoking:
/review auto_approve

The tool will automatically approve the PR, and add a comment with the approval.
To ensure safety, the auto-approval feature is disabled by default. To enable auto-approval, you need to actively set in a pre-defined configuration file the following:
[pr_reviewer]
enable_auto_approval = true

(this specific flag cannot be set with a command line argument, only in the configuration file, committed to the repository)
You can also enable auto-approval only if the PR meets certain requirements, such as that the estimated_review_effort is equal or below a certain threshold, by adjusting the flag:
[pr_reviewer]
maximal_review_effort = 5

  More PR-Agent commands

To invoke the PR-Agent, add a comment using one of the following commands:

/review: Request a review of your Pull Request.
/describe: Update the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
/ask <QUESTION>: Ask a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.
/add_docs 💎: Generate docstring for new components introduced in the PR.
/generate_labels 💎: Generate labels for the PR based on the PR's contents.
/analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component.

See the tools guide for more details.
To list the possible configuration parameters, add a /config comment.

See the review usage page for a comprehensive guide on using this tool.

@CodiumAI-Agent /improve

PR Code Suggestions
💡 [readability]
Avoid using unless with else as it can make the code harder to understand. Consider using if instead.
File: lib/rspec_tracer/coverage_reporter.rb (32-40)
  Example code:

Existing code:
unless @coverage.key?(file_path)
  missing_file_diff_coverage(example_id, file_path, current_stats)
  next
end
next if current_stats == @coverage[file_path]
existing_file_diff_coverage(example_id, file_path, current_stats)

Improved code:
if @coverage.key?(file_path)
  next if current_stats == @coverage[file_path]
  existing_file_diff_coverage(example_id, file_path, current_stats)
else
  missing_file_diff_coverage(example_id, file_path, current_stats)
end

💡 [maintainability]
Consider extracting the logic for checking if a file is filtered into a separate method to improve readability and maintainability.
File: lib/rspec_tracer/runner.rb (262-270)
  Example code:

Existing code:
def register_file_dependency(example_id, file_path)
  source_file = RSpecTracer::SourceFile.from_path(file_path)
  return false if RSpecTracer.filters.any? { |filter| filter.match?(source_file) }
  @reporter.register_source_file(source_file)
  @reporter.register_dependency(example_id, source_file[:file_name])
  true
end

Improved code:
def register_file_dependency(example_id, file_path)
  source_file = RSpecTracer::SourceFile.from_path(file_path)
  return false if filtered?(source_file)
  @reporter.register_source_file(source_file)
  @reporter.register_dependency(example_id, source_file[:file_name])
  true
end

def filtered?(source_file)
  RSpecTracer.filters.any? { |filter| filter.match?(source_file) }
end

💡 [maintainability]
Consider extracting the repetitive code for writing to a file into a separate method to improve maintainability.
File: lib/rspec_tracer/reporter.rb (229-282)
  Example code:

Existing code:
def write_all_examples_report
  file_name = File.join(@cache_dir, 'all_examples.json')
  File.write(file_name, JSON.pretty_generate(@all_examples))
end
...
def write_last_run_report
  file_name = File.join(RSpecTracer.cache_path, 'last_run.json')
  last_run_data = @last_run.merge(run_id: @run_id, timestamp: Time.now.utc)
  File.write(file_name, JSON.pretty_generate(last_run_data))
end

Improved code:
def write_all_examples_report
  write_to_file(File.join(@cache_dir, 'all_examples.json'), @all_examples)
end
...
def write_last_run_report
  last_run_data = @last_run.merge(run_id: @run_id, timestamp: Time.now.utc)
  write_to_file(File.join(RSpecTracer.cache_path, 'last_run.json'), last_run_data)
end

def write_to_file(file_name, data)
  File.write(file_name, JSON.pretty_generate(data))
end

💡 [readability]
Consider using a guard clause instead of wrapping the code inside the unless statement to improve readability.
File: lib/rspec_tracer/runner.rb (99-101)
  Example code:

Existing code:
next if filtered_files.include?(file_path)
filtered_files << file_path unless register_file_dependency(example_id, file_path)

Improved code:
next if filtered_files.include?(file_path)
register_file_dependency(example_id, file_path) && filtered_files << file_path

Generating PR code suggestions
Work in progress ...


Test suite failed to run

This issue introduced to master over the last few days:
 Your test suite must contain at least one test.

      at node_modules/jest-cli/build/test_scheduler.js:157:22

Steps to reproduce
Clone storybook
yarn bootstrap --core && yarn test --core --image
storybook 4.0.0-alpha.2

You need to run cd examples/official-storybook && yarn build-storybook before image tests
https://github.com/storybooks/storybook/blob/master/CONTRIBUTING.md#cra-kitchen-sink---image-snapshots-using-storyshots

Yes, they all pass after this. Thanks.


BOT NOT USER

The code gives bot user function, but bot can't function as a user

Provide more details about your issue


PeoplePicker: Specify to hide or show the users/groups which are hidden in the UI

Category
[ ] Enhancement
[x] Bug
[ ] Question
Version
Please specify what version of the library you are using: [latest]
Expected / Desired Behavior / Question
It would be a great enhancement to be able to hide or show the users/groups which are hidden in the SharePoint UI.

In 1.8.0 a new property showHiddenInUI is added to the PeoplePicker control.
<PeoplePicker
  context={this.props.context}
  titleText="People Picker"
  personSelectionLimit={5}
  // groupName={"Team Site Owners"}
  showtooltip={true}
  isRequired={true}
<EMAIL_ADDRESS><EMAIL_ADDRESS>  selectedItems={this._getPeoplePickerItems}
  showHiddenInUI={false}
  principleTypes={[PrincipalType.User]} />

Closing the issue as version 1.8.0 has just been released.


Selecting a country in 'Baseline' dropdown should naviagte the map to the corresponding country

Similar pan and zoom animation as current selection of a polygon on the map

I think this is related to #151 and may have been already started by @JohannDascalescu

I think this is related to #151 and may have been already started by @JohannDascalescu


Add auto waiting vote support and walletServer run start foreground

Description
Add auto waiting vote support and walletServer run start foreground.
1.Support auto waiting vote and quick vote choose,If use auto waiting vote it will waiting vote until every hour between 2~3  minutes,It can help vote more easily.
2.Change wallet server run with start foreground,can help more difficult to recycle by Android System.

Thanks @snakewaypasser !


Uses more click goodness

Added the following click addons:

click-didyoumean
click-extensions
click-plugins
Added example plugin with documentation.
Added prefix to all non-cli commands "cli_"
Now uses the decorator "catch_exceptions" to catch exceptions and remove the S3 zip file if neccessary.

Moved adding conditional command "manage" to init.py in order to avoid a circular dep
Added management command (also supports all commandline options of django)
Small fix to invoke when using extra_args
A bit of cleanup, and a look at how difficult tests will be.  Thinking we are going to need to postpone writing tests until we can decouple CLI from the loader code.  This will make testing much easier.
Added click to the requirements explicitly
Changed position of click in the requirements lol
Trying importing to the requirements.txt in order to get travis to pass
Had trouble installing the click-extensions library, so pulled out what we need instead.
Removing more cli tests that passed on my machine (with creds) but not on travis.  Will add them back when we can seperate CLI and logic.
New way of doing settings
Broke down a lot of the large methods to make it more testible.
Lot of unit tests.
Cleaned up some code quality stuff

Still need to work in all the changes that happened on master.

Coverage decreased (-18.03%) to 62.407% when pulling df1b4c3c5d814fc72321f31e5bc3f0a610277c8a on xuru:click_cli_changes into dbffbee20a550d2a00731fe4bc2d1abbcdb426f3 on Miserlou:master.

Coverage decreased (-18.03%) to 62.407% when pulling df1b4c3c5d814fc72321f31e5bc3f0a610277c8a on xuru:click_cli_changes into dbffbee20a550d2a00731fe4bc2d1abbcdb426f3 on Miserlou:master.

Unfortunately, there are a lot of things that are preventing me from merging this. :( Primarily - coverage has dropped 18%. Secondly, I very much don't like the pattern of "ripping out what we need" from upstream libraries, as this will eventually become a source of conflict. Far better to file any tickets upstream and have the integration be fixed.

What part of it is "upstream libraries"?  As far as I know I only broke down zappa/ZappaCLI.py into separate commands in the commands directory and a zappa/ZappaLauncher.py.  I was careful not to touch zappa/zappa.py as much as possible.
I know this is a huge PR, and I don't blame you for not accepting it.  I will leave the branch available on my repo in case you want to look at what I did later on when things slow down.
BTW, It's a shame that placebo adds so many files.  Really hard to see what is going on.  Thanks for having a look at it!


implement terraform deployer using  terraform-boot API

[ ] Add a new spring bean which can be activated with a specific profile.
[ ] When activated, we must use this  new logic for running Terraform scripts.
[ ] As part of the async job in xpanse -> accept the request, generate terraform files, call terraform-boot API with correct vars and env vars.
[ ] Implement for deploy and destroy.
[ ] Webhook URL must contain the task ID. refer to #759

depends on #757
Note - the old logic of executing the terraform binary directly from xpanse will be deleted after the terraform-boot based solution is fully working.

let me do it


Add more logs in the archive settings. (#659)

This is a cherry-pick of https://github.com/dotnet/source-build/pull/659, the same change to master.
Skip CI please.

Add more logs in the archive settings.

Set log archiving to also happen on success.

Add log archiving for tarball build subdirectories.

Also suppress verbose smoke-test output as we have these logs archiving now.

@dotnet-bot test CI please


Support ParamSpec and Concatenate (PEP 612)

This could potentially make pyanalyze.extensions.AsynqCallable redundant.

#352 added some support. We still need:

Classes that are generic over a ParamSpec
P.args/P.kwargs support


Suggest less disruptive step for content-prefs.sqlite

I took a look into content-prefs.sqlite, and it looks like spellchecker settings have the same ID.
Maybe worth suggesting to use a SQLite browser to remove those settings with Firefox close, more than removing all settings?
DELETE FROM prefs WHERE settingID=(SELECT id FROM Settings WHERE name='spellcheck.lang')

Well, actually I had the problem that on lots of sites the language was not automatically detected so I just followed the advice, quit Firefox, deleted the file and restarted Firefox ... just to find out that it didn't solve the problem for any of those sites. So I wonder how meaningful this advice is in the first place and if it ever is really necessary to delete these settings. IMHO that setting is only the default language chosen and an add-on should be able to override this choice.
@flodolo
I wasn't even aware that sub-selects are so common nowadays. In the good old days, we would have done it like this:
DELETE FROM prefs JOIN settings ON settings.id = prefs.settingID WHERE settings.name = 'spellcheck.lang'


Use danger swift correct href

Warnings

:warning:

Any changes to library code should be reflected in the Changelog.
Please consider adding a note there and adhere to the Changelog Guidelines.

  Generated by :no_entry_sign: Danger Swift against 68edb6c9ef854a0df7cef43c3403a8e2b6512b37

merge on green


How to optimize server  ?

I have 2 point relate to server.

task run very slow, especially Find neighbors of items. my server have 8cpu 4 core, 16g RAM.
how to optimize cache of redis ? i just run testing with about 50k items, but 16G ram redis it not enought. while in reality i have over 5 milion items. and over 1000 category.
Simply calculate,  50k items => 16G RAM, 500k item => 160G RAM, 5000k  => 1600G RAM ? OMG, terrible.  i was change database type for cache, but it very very slow.

Thanks.
Would be very grateful if there is any solution to help me improve

Tell me the version name please. 0.4 or 0.5

i think version is 0.5. i just pull latest again.
Now i reduce data categories each item but the task Find neighbors of items still slow. it run over 30 minute but just not yet 50%.
My data 42k item 0 user, 0 feedback, per item have multi label and multi categories. label i think 10 from 20 label per item, categories is from 2 to 5 per item


Insert Date and Time on file's names

This feature would help on identifying each usage of the telemetry.
Filename example:

Dados 1 - 01/07/2018 - 13:03
Dados 2 - 01/07/2018 - 13:03
Dados 3 - 12/08/2018 - 22:04

Solved by #60