Change reference status labels and the text underneath

Context
We need to update the wording of the status labels for references. There are changes to:

the wording of the labels
the colour of the labels
the wording that appears with some labels

Changes proposed in this pull request
Some labels have changed and only two labels will show additional text"

Requested
Request sent on ((date)) - [send reminder] or [cancel request]

Request failed
Email could not be sent - check email address and send again

Before
After

Guidance to review

Link to Trello card
https://trello.com/c/5Y3V1EH8/578-change-reference-status-labels-and-the-text-underneath
Things to check

[x] If the code removes any existing feature flags, a data migration has also been added to delete the entry from the database
[x] This code does not rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] If this code adds a column to the DB, decide whether it needs to be in analytics yml file or analytics blocklist
[x] API release notes have been updated if necessary
[x] Required environment variables have been updated added to the Azure KeyVault

 Change reference status labels and the text underneath

Tested on the review app. One bug I spotted is that if you request a new reference, you’re able send a reminder straight away - I thought you had to wait a period of time first?


UI for anonymized metrics.

Style still needs to be refined but the basics are all setup.

Clicking the icon opens the panel:

As soon as you uncheck the box in settings, the icon disappears:

Next to the sharing icon:

Updated UI:

:+1: good stuff!  We will push some style changes (CSS and changes to the boolean bubble showing logic) later on

done changes and added a TODO


🌱 Bump CAPI to v1.7.0-beta.1

as title says

/test-centos-e2e-integration-main
/test-ubuntu-integration-main

/test-ubuntu-integration-main


make apple user profile properties public

learned that lesson the hard way 🤦♀

Ah that's right! I know how that one goes.


Prep for posting guidance on C4IP website

@aubrey-oneal would you be interested in starting to look at the guidance placement related to this new asset on C4IP?

@ljcarot I'm going to put together an as-is map of the PLG patterns and guidance so we can see how things might connect.
I imagine that this will connect with the issue we created about how to deliver the Get started work, and Aubrey's work with the IA


Update groups-create-eligible.md

Aligned with https://docs.microsoft.com/en-us/graph/api/group-post-groups?view=graph-rest-beta&tabs=http

@BakkerJan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @BakkerJan
Thanks for contributing to the docs! We'll get your changes merged.
thanks


Reinforced windows are too strong.

Description

So, we have reinforced windows which are very common on the station and reinforced walls.
Reinforced windows have 150 hp, reinforced walls have 600, the latter aren't see-through and use 4 plasteel plates and 2 steel.
Reinforced windows on the other hand use 1 steel plate and 2 glass plates.
Now then, this seems to make sense, except for the part where reinforced walls don't have a damage modifier and or it's too weak.
I couldn't find rei wall damage modifiers, I did find rei window however.
Blunt 1.0
Slash 0.3
Piercing 0.6
Heat, Shock 0.0
FLAT REDUCTIONS AS WELL, which is a major issue considering that the strongest weapons in the game deal up to 25~ damage (and that's the high-end, so that, and flat reductions make a lot of weapons in ss14 obsolete and it barely makes sense for a window that's already cheaper, can be shot through via lasers, is completely see-through and it doesn't use sci-fi materials like plasteel, an alloy of steel and plasma (maybe titanium instead of steel? not sure.)
Blunt 5
Slash 10
Piercing 5
Compare this to the reinforced wall, which has no damage modifiers whatsoever, as it parents from WallBase (which also has no modifiers), and the rei wall itself lacks them as well, effectively putting it on-par with the reinforced window or a bit weaker, whilst the latter can be made as thindows and be stacked essentially in 3 with minimum space loss.

Additional context

tl;dr
reinforced windows have damage modifiers that make them as strong (or a bit weaker) than rei walls, the latter not having damage modifiers, and from experience generally being weaker even considering that they have 4x the hp.
rei window bad, plsz nerf, too stronk. :tm:

Reinforced windows have that damage modifier to reduce griefing, they used to be plain paper. This is less an issue now most grief items break when thrown.
The flat reductions could probably be removed and the destruction behaviour needs modified so you’re less likely be to be able to repair it. If this means increasing our construction materials so be it, we need to stop copying bad design from SS13 if 1 shard = 1 rglass = 1 rwindow, because logically you should always get one shard, so it makes no sense a 4 sided window needing 1 sheet.

Uhhh wasn't there a structural rework recently, how does this affect the issue?


Ansible-Navigator role call issue

SUMMARY
when i check the syntax of playbook using ansible-navigator command its showing error but when i check using ansible-playbook command its showing no error
ANSIBLE-NAVIGATOR VERSION
ansible-navigator 3.4.2
CONFIGURATION
[devops@control ansible]$ cat ansible.cfg
[defaults]
inventory = inventory
roles_path = /home/devops/ansible/myroles:/usr/share/ansible/roles
collections_path = /home/devops/ansible/mycollections
remote_user = devops
[privilege_escalation]
become = True
become_method = sudo
become_user = root
become_ask_pass = False
LOG FILE

STEPS TO REPRODUCE
ansible-navigator run timesync.yml --syntax-check -m stdout
EXPECTED RESULTS
ERROR! the role '/usr/share/ansible/roles/linux-system-roles.timesync' was not found in /home/devops/ansible/roles:/home/runner/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles:/home/devops/ansible
The error appears to be in '/home/devops/ansible/timesync.yml': line 13, column 7, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
roles:
- /usr/share/ansible/roles/linux-system-roles.timesync
^ here
ACTUAL RESULTS
ERROR! the role '/usr/share/ansible/roles/linux-system-roles.timesync' was not found in /home/devops/ansible/roles:/home/runner/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles:/home/devops/ansible
The error appears to be in '/home/devops/ansible/timesync.yml': line 13, column 7, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
roles:
- /usr/share/ansible/roles/linux-system-roles.timesync
^ here
ADDITIONAL INFORMATION
when we check the playbook syntax using ansible-playbook its working perfect
below is the output of upper command.
[devops@control ansible]$ ansible-playbook --syntax-check timesync.yml
playbook: timesync.yml
when we check the playbook syntax using ansible-playbook its working perfect

Please find below content of playbook

name: time update
hosts: all
vars:
timesync_ntp_servers:
- hostname: 0.asia.pool.ntp.org
iburst: true
- hostname: 1.asia.pool.ntp.org
iburst: true
- hostname: 2.asia.pool.ntp.org
iburst: true
roles:

/usr/share/ansible/roles/linux-system-roles.timesync

Can you try this with --ee false?  I'm wondering if the role was not mounted into the execution environment and therefore when running in the execution environment it cannot be found.
By default navigator only mounts the current working directory into the container.
If content outside the current working directory is needed within the execution environment, additional volume mount can be added using the CLI and config file: https://ansible.readthedocs.io/projects/navigator/settings/#execution-environment-volume-mounts
Please let us know.
-Brad

Dear Mr. Brad,
Thank for your guidence issue is fixed.


[Hotfix] Fix shade plugin id and artifactId

@zhoujinsong These two places also need to be modified.

@zhoujinsong These two places also need to be modified.

Thanks for the help.


[local-volume] Added recommendation for using ID on block vol to README

Block volume ID's can be found by looking at ls -l /dev/disk/by-id. Using these IDs in directory names can help ensure that the related local PVs are unique and not confused with other local PVs, even if the node name is the same.

/assign @msau42

/lgtm

/assign @wongma7 - PTAL - thanks in advance.

@ianchakeres
Quick question.
Is the name of symlink under /dev/disk/by-id always unique between multiple nodes?
I'm not sure it's ensured.

It depends on the environment.  On baremetal, it typically should use the hardware serial number.  But in a VM environment, it may not be unique.

Here is one reference that describes the by-id naming: link
Here is another reference that is a little more specific: link
"""
for the disk devices in 60-persistent-storage.rules:
KERNEL=="sd*|sr*|cciss*", ENV{DEVTYPE}=="disk", ENV{ID_SERIAL}=="?*", SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}"
"""

Agree. It depends on hardware environment, storage type, etc.

if another node with the same name is created, that any volumes

on that node are unique and not mistaken for a volume on another node with
the same name.

So, I thought we can't say this is ensured.

@msau42  @mtanino  - What do you think about adding bare-metal to the first sentence?

Maybe you can say something like:
For raw block volumes, use a unique ID as the symlink name.  Depending on your environment, the id in /dev/disk/by-id may use the hardware's serial number and will be unique.  Otherwise, a unique ID may need to be generated.

I agree to use by-id naming, this is recommended way to refer physical device.
@msau42
That's looks good to me.

Additionally, this practice will ensure that if another node with the same name is created, that any volumes on that node are unique and not mistaken for a volume on another node with the same name.

Additionally, this practice will ensure that if another node with the same name is created, that any volumes on that node are unique and not mistaken for a volume on another node with the same name.

Are there any background that we want to ensure volume-id as unique between multiple node?
May be I'm missing the background.

See kubernetes/kubernetes#51431

Thanks. I understand.

lgtm.

/lgtm


pkg/testutil: ForceGosched -> WaitAllGoroutinesBlocked

ForceGosched() performs bad when GOMAXPROCS>1. When GOMAXPROCS=1, it
could promise that other goroutines run long enough to the block point
because it always yield the processor to other goroutines. But it cannot
yield processor to goroutine running on other processors. So when
GOMAXPROCS>1, the yield may finish when goroutine running on the other
processor has not run to block point.
Here is a test to confirm the case:
package main

import (
	"fmt"
	"runtime"
	"testing"
)

func ForceGosched() {
	// possibility enough to sched up to 10 go routines.
	for i := 0; i < 10000; i++ {
		runtime.Gosched()
	}
}

var d int

func loop(c chan struct{}) {
	for {
		select {
		case <-c:
			for i := 0; i < 1000; i++ {
				fmt.Sprintf("come to time %d", i)
			}
			d++
		}
	}
}

func TestLoop(t *testing.T) {
	c := make(chan struct{}, 1)
	go loop(c)
	c <- struct{}{}
	ForceGosched()
	if d != 1 {
		t.Fatal("d is not incremented")
	}
}

go test -v -race runs well, but GOMAXPROCS=2 go test -v -race fails.
Change the functionality to waiting for other goroutines to be blocked.
fixes #2936 #2935
/cc @jonboulle

@yichengq Unfortunately, this does not seem to fix everything. The test is still failing.

still dig into the left failure. That failure is not related to this PR in high probability because the failed test doesn't call ForceGosched func.

@yichengq Can we simply lock the os thread to fix the issue? we simply want to sched to another running routine.

Change it to simple sleep per xiang's suggestion. This is the simplest way to make the hack, and it works on local and travis.
The LockOSThread is not a good solution because it is not used for schedule.

LGTM


Confirm hosted Blazor IdS AKV certificate access guidance

Confirm guidance per https://github.com/dotnet/AspNetCore.Docs/issues/19572#issuecomment-979277203
https://docs.microsoft.com/en-us/aspnet/core/blazor/security/webassembly/hosted-with-identity-server?view=aspnetcore-6.0&tabs=visual-studio#host-in-azure-app-service-with-a-custom-domain-and-certificate
cc: @SzymonSel ... I'll get to this as soon as I can. 🏃🏃🏃🏃🏃🏃🏃🏃🏃🏃😅

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

ID: 9638772f-0f1e-c2a9-8a58-ae8c3e37ae28
Version Independent ID: 7a5b169e-08cb-cdba-4501-88d3da2723bb
Content: Secure a hosted ASP.NET Core Blazor WebAssembly app with Identity Server
Content Source: aspnetcore/blazor/security/webassembly/hosted-with-identity-server.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @guardrex
Microsoft Alias: riande

I've created the:

CI/CD with a default appservice name .azurewebsites.net

Azure Key Vault

Certificate for IndentityServer

Added the WEBSITE_LOAD_CERTIFICATES configuration on the app service with the certificates thumbnail

I'm getting a error on app startup:
System.InvalidOperationException: Couldn't find a valid certificate with subject 'CN=IdentityServerSigning' on the 'CurrentUser\My'
In Kudu Tools, doing a search on Get-ChildItem -path Cert:\CurrentUser\My also return no results.
I've troubleshooted this on other app services including F1 and B1 tiers to no avail.

@SzymonSel ... I can't repro any problems here with the basic guidance that we keep for this scenario. Here's the quick-'n-dirty test that I did to confirm the main aspect of the guidance ..

Created a self-signed cert in a KV.
Created an App Service at B1 level (with the app setting and thumbprint called out by Step 7).
Just for a side-test to make sure that any cert in KV would be seen by the app for use with a custom domain, I just checked the Import Key Vault Certificate area (for TLS/SSL settings) to make sure that the cert shows up in the drop-down list. You wouldn't do this for this IdS key signing cert. I'm just checking to make sure that the app in App Service can see 👁 the cert. This is the process one would follow if they had uploaded a PFX for DNS purposes.
Executed the PS command to see if that cert shows up. It does.

Two things ...

There's a couple of NIT side problems that I'll use this issue to fix. They change the Azure portal all the time 😅, and our Azure portal guidance is under constant threat of churn gremlins 😈.
For the phrase "Advanced Policy Configuration" in the doc, that should have the prefix selection and read: "Issuance Policy > Advanced Policy Configuration". So, I'll use this issue to make that quick update. There might other 😈😈😈 in these steps due to other portal churn, and I'll get it all fixed up when I reach this topic for further updates in 22H1.
I see a second little NIT in what's said about the PS command. It's useful in that case to see the IdS cert from that cert store, not the one that will be used for DNS. I should call that out. I'll see if I can find a good troubleshooting Azure doc for either/both App Service and KV cert problems, including a possible PS doc for troubleshooting. If I find something, I'll cross-link it in there at the end.

Second thing is that this is about the limit of what we'll be able to do here WRT the problem that you're having getting the cert to show up. Idk if the problem has to do with your CI/CD (I'm not experienced in that area for one thing) or if the problem just lies more in the config steps that you took.
We only work the ASP.NET Core side of things. Not getting a cert to show up for an App Service app from KV is an Azure gesture and falls to Azure docs for edge cases, gotchas, and troubleshooting. I realize that this is not what many devs hope for on their requests here, but we can't provide product support for all of Azure or deal directly with Azure docs. Those are completely different groups of folks from us. If Azure docs don't lead you to a solution for getting a cert available, then one should use the normal Azure support channels both within MS and via external, public support channels (SO, Slack, Gitter, etc.).

If you eventually discover a gotcha 😈 that would be good to call out in the doc here, please do come back and add a comment here on it. I'm open to hearing about things that could save folks time and trouble. It's especially good when we can cross-link from here to Azure docs for whatever it is. I'll take a look at the Azure links here to confirm that we're linking to their best, current content for this process.
_Leave this issue open. It will close automatically when my PR merges shortly.

But wait, what if I don't want to create the TLS/SSL certificate for the domain? (Which is my case, I'm fully satisfied with the default https://.azurewebsites.net)

Is it possible that the WEBSITE_LOAD_CERTIFICATES isn't loaded if don't explicitly add a custom TLS/SSL domain certificate? This is not possible for F1 tier app services, although:

Although the guidance focuses on using the certificate with a custom domain, the guidance is equally applicable to using a default Azure Apps domain, for example contoso.azurewebsites.net.

You don't need to follow that part of the guidance then. You can just create a self-signed cert for the IdS signing cert, put the app setting in the (B1 level) App Service, and the app should be able to use it from there. Still tho ... you should be able to 👁 it with the PS command in a Kudu PS console. If you don't, I can't explain why that's the case per this set of guidance.
WRT having both pieces of guidance here (the IdS signing cert and a custom domain), I'm going to leave these together in the section for the time being. Most devs need to do both really when using a custom domain because we don't recommend using the same cert for the DNS part as they use for IdS. Therefore, they should follow every step here. When I reach the topic next year for a large round of updates, I might split out the IdS piece.

Is it possible that the WEBSITE_LOAD_CERTIFICATES isn't loaded if don't explicitly add a custom TLS/SSL domain certificate?

That's not relevant AFAIK. If you only want to use a cert for IdS, then you just put one thumbprint there for that self-signed cert. It should just work at that point.

... and btw ... I don't recall exactly if the B1 aspect was only a custom domain aspect. I know that the B1 level is required for custom domains. I don't know if that's a requirement for just IdS cert. I don't know because I'm explaining out both scenarios and it's required for custom domains. I'll take a look at that aspect when I circle around in 22H1. If I do split the section and B1 isn't required for merely the IdS cert, then I'll call that out after I've confirmed that it's the case.

Thanks. Just to summarize, I don't need a custom domain or TLS cert. I just need one for the IdS.

I just need one for the IdS.

Ok ... that's cool. After you add the app setting, it should work (and show up in the CurrentUser\My store). If not, seek help from Azure :cat2::cat2::cat2: on the Net. There's likely an edge case here of some sort with your Azure scenario ... something that the doc can possibly call out depending on what it is.
If you haven't already done so, I've had some luck in the past just starting a process over from scratch because I was unaware that I missed something along the way. You could try (if you haven't already) a fresh KV and a fresh App Service. If it works, then it was just a tiny misconfiguration in the original attempt.

Yeah thanks, I've guess I've already also or almost all possible combinations. Will give a go again and report back if I find anything.

After some tests, It seems clear to me, than in order to have the certificate specified in WEBSITE_LOAD_CERTIFICATES to be loaded by the app, it also need to be added in TLS/SSL settings.
I'm quite sure if you remove the certificate from the TLS/SSL settings, it will also dissappear from the app service ie. Get-ChildItem will not return this certificate.
So in short - one cannot run IdetintityServer with this scenario on F1 tier

Ok ... we're good. I must have known/seen that, too, because the instruction is ....

Select the app's TLS/SSL settings. Select Private Key Certificates (.pfx). Use the Import Key Vault Certificate process twice to import both the site's certificate for HTTPS communication and the site's self-signed Identity Server token signing certificate.

... keyword there is "both" ... so the guidance seems ok right now 🤞 on that point.

When I revisit this for the big round of updates later, I think it will be worth making that whole sentence in BOLD TEXT. I'll do that when I circle back.


Feature request: make JSON schema available as a file

The datafile schema is stored within the ruby sdk as a Hash constant. As Optimizely is unable to envision the multitude of integrations of the ruby-sdk, nor the many potential toolchains and development environments into which the ruby-sdk will be installed, it would be more versatile for the json schema to be shipped as a standard schema file ( datafile-v2.schema.json). This would enable the schema to be hooked into test suites and other tools that (rightfully) expect the schema to be a regular file.
The ruby sdk could still parse the file into a hash and expose it as a constant. But making the actual file available would enable additional schema toolchain configurations.

My apologies for the delay in response to this issue. The team is updating our processes and reviewing all open issues and PR's. If this Feature Request is still relevant, please add your suggestion to our idea portal here https://feedback.optimizely.com/ where it can be evaluated with the other ideas for the product.  From here it will be appropriately prioritized and brought to the engineering team.


Warnings when using thefuck

WARNING: Token 'COND_ERROR' defined, but not used
WARNING: There is 1 unused token
Unable to create '/usr/local/lib/python3.4/dist-packages/bashlex/parsetab.py'
[Errno 13] Permission denied: '/usr/local/lib/python3.4/dist-packages/bashlex/parsetab.py'
The above lines appear everytime I launch a shell, and everytime I use thefuck

Just run sudo thefuck one time, and the file will be created which will fix your issue. But it would be better if this can be fixed upstream (by bashlex)

The WARNING lines are caused by https://github.com/idank/bashlex/issues/20
The other lines are a separate matter. It could be fixed by changing bashlex so that it does not try to create parsetab.py (see https://github.com/dabeaz/ply/issues/79#issuecomment-243572084), but after some informal testing, I'm worried this might make thefuck slower, since it would be rebuilding the parser table on every invocation, rather than loading from parsetab.py.
Perhaps a better solution would be to make it so that thefuck can tell bashlex to put the parsetab.py file in ~/.config/thefuck/.

@josephfrazier we actually should stop using bashlex because of gpl license of it.

@LoZeno try 3.14

@nvbn Oops, I wasn't aware of the licensing conflict. Sorry about that! I'll open a new issue for finding an alternative solution to https://github.com/nvbn/thefuck/pull/580


[enhancement] add dynamic leverage rate for margin, future gateways

环境

操作系统: 如Windows 10或者Ubuntu 18.04
Python版本: 如VNStudio-2.0.6
vn.py版本: 如v2.0.5发行版或者dev branch 20190101（下载日期）

Issue类型
三选一：Bug/Enhancement/Question
Can you add dynamic leverage rate for margin, future gateways ?
Recently, vnpy only supported fix leverage (max multiple) which bring max risk for strategy.
预期程序行为
实际程序行为
重现步骤
针对Bug类型Issue，请提供具体重现步骤以及报错截图

In vn.py, we use cross margin (CME futures margin mode) instead of isolated margin (OTC forex margin mode), so the only factor which influences your risk level should be your total position value, or  in another word, how many contracts you open. Therefore, there is no need to change leverage level, but using the max multiple is enought.


Invalid use of Function() with argument(s) of type(s): (Literalint, int64, Literalint)

from numba import njit, jit
from tqdm import tqdm
fib=[1,2,3,5,8,13,21,34,55,89,144,233,377,610,987,1597,2584,4181,6765,10946,17711,28657,46368,75025,121393,196418,317811,514229,832040,1346269,2178309,3524578,5702887,9227465,14930352,24157817,39088169,63245986,102334155,165580141,267914296,433494437,701408733,1134903170,1836311903,2971215073,4807526976,7778742049,12586269025,20365011074,32951280099,53316291173,86267571272,139583862445,225851433717,365435296162,591286729879,956722026041,1548008755920,2504730781961,4052739537881,6557470319842,10610209857723,17167680177565,27777890035288,44945570212853,72723460248141,117669030460994,190392490709135,308061521170129,498454011879264,806515533049393,1304969544928657,2111485077978050,3416454622906707,5527939700884757,8944394323791464,14472334024676221,23416728348467685,37889062373143906,61305790721611591,99194853094755497,160500643816367088,259695496911122585,420196140727489673,679891637638612258,1100087778366101931,1779979416004714189]
m=1000000007
t=0
@njit(fastmath=True)
def s(f):
	tt=0
	x=0
	if f//9!=0:
		tt=45
		x=9
	for i in range(1,f//9):
		tt=(tt+((45*pow(10,i,m))%m+(x*9)%m)%m)%m
		x=x*10+9
	xx=f%9
	tt=(tt+(((xx*(xx+1))/2)%m+(x*xx)%m)%m)%m
	# print(tt)
	return tt

for f in tqdm(fib):
	t=(t+s(f))%m
print(t)

Here is a full traceback while running this code :
Traceback (most recent call last):
  File "test.py", line 23, in <module>
    t=(t+s(f))%m
  File "C:\Users\Neel\Anaconda3\envs\env_1\lib\site-packages\numba\dispatcher.py", line 401, in _compile_for_args
    error_rewrite(e, 'typing')
  File "C:\Users\Neel\Anaconda3\envs\env_1\lib\site-packages\numba\dispatcher.py", line 344, in error_rewrite
    reraise(type(e), e, None)
  File "C:\Users\Neel\Anaconda3\envs\env_1\lib\site-packages\numba\six.py", line 668, in reraise
    raise value.with_traceback(tb)
numba.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend)
Invalid use of Function(<built-in function pow>) with argument(s) of type(s): (Literal[int](10), int64, Literal[int](1000000007))
Known signatures:
 * (float64, int64) -> float64
 * (float64, uint64) -> float64
 * (float32, float32) -> float32
 * (float64, float64) -> float64
In definition 0:
    All templates rejected with literals.
In definition 1:
    All templates rejected without literals.
This error is usually caused by passing an argument of a type that is unsupported by the named function.
[1] During: resolving callee type: Function(<built-in function pow>)
[2] During: typing of call at test.py (15)

File "test.py", line 15:
def s(f):
    <source elided>
        for i in range(1,f//9):
                tt=(tt+((45*math.pow(10,i,m))%m+(x*9)%m)%m)%m
  ^

This is not usually a problem with Numba itself but instead often caused by
the use of unsupported features or an issue in resolving types.

To see Python/NumPy features supported by the latest release of Numba visit:
http://numba.pydata.org/numba-doc/latest/reference/pysupported.html
and
http://numba.pydata.org/numba-doc/latest/reference/numpysupported.html

For more information about typing errors and how to debug them visit:
http://numba.pydata.org/numba-doc/latest/user/troubleshoot.html#my-code-doesn-t-compile

If you think your code should work with Numba, please report the error message
and traceback, along with a minimal reproducer at:
https://github.com/numba/numba/issues/new

I presently have tried njit & jit both with functions pow, numpy.pow and math.pow, none of which work.

Hi, I think the error means that pow supports the 2-argument form only.
Maybe substitute this:
pow(10,i,m)

With...
pow(10, i) % m

Thanks for the report, I think @rjenc29's assessment is correct, this is a feature request for the three argument form of pow.


Nexus Platform

 Freshdesk Ticket ID: 49417
 Freshdesk Ticket Agent: Martha Nagginda
 Freshdesk Ticket Agent Email<EMAIL_ADDRESS> Ticket Priority: Medium
 Freshdesk Ticket Description:

Bula Vinaka,I ran into a few problems while uploading the datasets today. (19/04/22)
The images attached shows the problem I had faced while uploading.

Some of the problems I ran into are as follows:
A sample dataset that was uploaded showed an error message as you can see below. Even though, it shows an error message,  it can still be viewed but you will have to open a new tab and navigate to the uploaded dataset menu.
Some datasets are like this upon upload but some are not.
While trying to edit the style for the sample data, it requires you to sign into the platform again, if you press cancel, it shows something different on the screen.
The thumbnail does not show even after updating the metadata.
It takes a while for a dataset to be uploaded even though the size of the data is only 1MB.

I appreciate your help on this matter and look forward to your response. Please let me know if you need any more clarification on the issues I've explained.
Thank you.

Agent Martha Nagginda linked Freshdesk ticket 49417 for this issue.

Agent Support created comment.
Hi Ulamila,

thanks for raising the issues. The problem with the form requesting credentials when working on styles should be fixed now.
We're investigating the other issues with regard to the upload errors and the failed thumbnails.

==Our support, Your Success! Visit https://geosolutionsgroup.com/enterprise-support-services for more information.
==

Support @ GeoSolutions

https://www.geosolutionsgroup.com


make the target hidden completely

Codecov Report

Merging #2172 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2172      +/-   ##
==========================================
+ Coverage   73.98%   73.98%   +<.01%
==========================================
  Files          51       51
  Lines        4178     4179       +1
==========================================
+ Hits         3091     3092       +1
  Misses       1087     1087

Impacted Files
Coverage Δ

src/api.show.js
88.88% <100%> (+0.42%)
:arrow_up:

Continue to review full report at Codecov.

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

Hi,
Do you think you could add some asserts for this in 'api.show-spec'?
Thanks!

@panthony Sorry, we may not have time to do it at this point

@Xuefeng-Zhu No worries, hard to ask for tests so long after :)

Tested and it does fix the issue.


Fix very old matchers to allow running on RSpec 2.8

If interesting, here is the actual issue.
Improvement is ~10 seconds (~15%) per test run.
RSpec 2.6:
> time b/rspec spec
real	0m57.419s
user	0m42.232s
sys	0m7.091s

RSpec 2.8:
> time b/rspec spec
real	0m48.237s
user	0m30.093s
sys	0m6.745s

Actually the rspec-rails-matchers are totally unmaintained and most people seem to give up in favour of shoulda-matchers.
I think we should too.

Yes, I agree. Would feel saver to use a real version instead of a git revision which might disappear.

I'm working on it right now. Will send another PR.
Also I think before releasing the 2.0 of neo4j we need to update all the dependencies and try to avoid hard ones. Especially like 3.0.pre4".

Yes, agree.
There is also one API change I want to do. The arguments of the Neo4j::Node.rel? method is not consistent with the other methods - http://neo4j.rubyforge.org/Neo4j/Rels.html

I don't know API well yet, but this is a good chance to clean up and fix long-standing things.
Perhaps, the following should be on agenda for 2.0:

ensure new gems layout works
pass all pending specs
update all dependencies
get rid of some deps if possible (I'm not exactly sure why will_paginate is there honestly)

Surely you have much more than that in mind :)

Looks like this broke the build for 1.9
http://travis-ci.org/#!/andreasronge/neo4j/jobs/510594

Gosh. That's JRuby bug. To fix, we need to call srand very early in the process (that's why I'm using binstubs and manually modifying it).
I would leave it as is for now unless there's a way call srand early on Travis. I hope JRuby 1.6.6 will be released soon-ish (weeks maybe).


Simplify makefiles

This change set eliminates unnecessary (redundant) declarations of
default flags already set globally, and then eliminates the subsequently
identical make files, substituting a single, common makefile via the make
"include" statement.
Many of the system-specific declarations set in the remaining make file
could now more easily be discovered via a subsequent autoconf / automake
implementation.

The optic's here are not great<EMAIL_ADDRESS>This PR has been sitting for 6 months, and the identical set of changes get committed in march with
Are you folks not interested in contributions, or not interested in giving credit for contributions?
commit 35388eb6ba4e5e42cc57650dbd831b366bf43ca2
Author: Rick Wertenbroek<EMAIL_ADDRESS>Date:   Thu Mar 7 17:33:12 2024 +0100
Use a common makefile

The makefiles were exact duplicates, use a common makefile.
Add a common makefile in the common directory and include
it in the other makefiles.

Signed-off-by: Rick Wertenbroek<EMAIL_ADDRESS>


[WIP]: Add a separate action for removing old wheels

Description

[!TIP]
This is a draft PR at the time of writing, and the description is a stub – it shall be updated soon. However, reviews on the approach are welcome!

This PR closes #62; by converting the .github/workflows/remove-wheels.yml workflow to a composite action in remove-wheels/action.yml that users can trigger in their workflows separately to delete binaries uploaded to the https://anaconda.org/scientific-python-nightly-wheels/ index or other Anaconda.org indices.
This way, users should be able to add, for example:
- name: Remove old wheels
  uses<EMAIL_ADDRESS># or, better, via the commit hash
  with:
    anaconda_token: ${{ secrets.ANACONDA_NIGHTLY_UPLOAD_TOKEN }} # same as that for uploads (convenience?)
    # Optionally override defaults:
    # n_latest_uploads: '5'
    # anaconda_user: 'my-custom-org'

or similar variations, to delete any but the last five wheel uploads, which means that this repository does not need to do so and can delegate this responsibility to the workflow files for the twenty-six packages listed under the https://anaconda.org/scientific-python-nightly-wheels/repo page.
Changes made
To be updated
Checklist

[ ] Resolve the to-do items (some of them have been marked as inline comments in the code for now)
[ ] Add relevant documentation, and adjust headings in the README
[ ] If .github/workflows/remove-wheels.yml stays, figure out how to not unintentionally delete wheels without the existence of packages-ignore-from-cleanup.txt

I've been meaning to do this for some time now, and I didn't receive a response to https://github.com/scientific-python/upload-nightly-action/issues/62#issuecomment-2015611358 back then. However, since it was mentioned that PRs would be welcome for reviews, and the repository has recently received quite a few updates (and a new release! 🎉), so I finally spent thirty minutes of my time writing this out—mostly just adding the script to a separate file—wherein I've added the necessary scaffolding around its creation as a separate, distributable action.

Okay, I've just read some discussion(s) on keeping the removal of old wheels "centralised" in https://github.com/scientific-python/upload-nightly-action/issues/4#issuecomment-1564825980 and in the comments after it. Those made sense to me, so, this PR could be considered in conjunction with that policy – to let SPNW clean up old wheels itself, and let these changes be a "refactor" of the wheel removal logic in a sense, i.e., from being embedded in a workflow to a separate action that gets used in it. This would also ease the removal process around those who want to take up the responsibility of removing their wheels that have been uploaded outside SPNW-managed Anaconda.org indices. It is to be noted that that discussion predates the ones linked in #62, so it is likely the case that requests for easier removals have arisen in more contexts by now.

Yes, having the cleanup parts moved to a new action and then using it sounds to be the right way to go, that way we expose the functionality for easy reuse while we also keep using it.

I am in transit and won't have time to review or give feedback on this for a few days. My original intent in Issue https://github.com/scientific-python/upload-nightly-action/issues/62 was to make a new repository and have that action be totally independent of this repository. Though, we can certainly get this in here and then just move it elsewhere later if people agree that's a good idea.

That sounds great! Thanks for triggering the workflow for me – I shall revisit this either later in the day or early next week. That said, I don't think one can run the workflow from forks, though... I have an account on Anaconda.org already since I'm helping manage the PyWavelets wheels (#75), should I add a dummy package for testing?

to make a new repository and have that action be totally independent of this repository. Though, we can certainly get this in here and then just move it elsewhere later if people agree that's a good idea.

Personally, I would say that related actions like these ones could be grouped together just fine, since one repository is easier to manage, rather than two – easier permissions to deal with, unified documentation in the README, unified dependency management (using pixi), etc., so this could fit in the same repository very well. For another example, https://github.com/github/codeql-action contains six actions, with each managed in its own folder.

to make a new repository and have that action be totally independent of this repository. Though, we can certainly get this in here and then just move it elsewhere later if people agree that's a good idea.

Personally, I would say that related actions like these ones could be grouped together just fine, since one repository is easier to manage, rather than two – easier permissions to deal with, unified documentation in the README, unified dependency management (using pixi), etc., so this could fit in the same repository very well. For example, https://github.com/github/codeql-action contains six actions, with each managed in its own folder.

Thanks for the reviews so far! I can officially mark this ready for review now. I've added additional context about most of my questions in my review above.

I am not sure if the Anaconda token that is authorised to maintainers of, say, a package X is restricted to only remove wheels for said package X

There is a restriction. Users are only allowed to do actions on the packages they are given access to 😃
There is just a handful of folks who have higher access right to administrate the Anaconda account. Here the token setup is very light but we use all the tools Anaconda gives us.

Thanks for the clarification! Should we make a mention of this in the documentation?

Feel free to make a suggestion 👍

CI is going to fail here because I don't have an ANACONDA_TOKEN set up in my fork's secrets. I could set an Anaconda organisation up (instructions would be welcome) for testing (or look into failures in a new PR, though I don't recommend that).
Or, the best way I can think of is that I could try this with a project in a PR downstream with the action set to my fork – since I help co-maintain PyWavelets's nightly wheels as I mentioned earlier up somewhere :) I would be unavailable next week, please let me know if this is reasonable and I'll try it out as early as the week after.


Alerting bug: Sync propagation to Alertmanager

It seems possible for syncs being sent to AM to fail on at least one of the AM nodes :
[FAILED] in [It] - /home/alex/repos/opni/test/plugins/alerting/alerting_test.go:409 @ 07/19/23 19:29:40.029
<< Timeline

[FAILED] Timed out after 30.000s.
Expected success, but got an error:
    <*errors.errorString | 0xc00496ed50>:
    condition agent-disconnect is not OK, instead in state Pending, configuration updates are scheduled for activation
    {
        s: "condition agent-disconnect is not OK, instead in state Pending, configuration updates are scheduled for activation",
    }
In [It] at: /home/alex/repos/opni/test/plugins/alerting/alerting_test.go:409 @ 07/19/23 19:29:40.029

An easy solution is to rework the alertops  Service :
service ConfigReconciler {
  rpc ConnectRemoteSyncer(ConnectRequest) returns (stream SyncRequest) {}
}

to be a bidirectional stream.
Requirements:

[ ] API needs to be changed, connection acquisition needs to be changed
[ ] Connection retry logic needs to be reworked a little
[ ] Retrier policies for errors should be moved to where the sync requests are made, not inside the config reconciler service

Nice to have:

[ ] Config retrier should have some sort of or Info() api returning the last applied hash (or whatever representation of the unique application of a sync request)
[ ] Alerting plugin should also have an Info() api containing some Info about itself and Infos about connected services and alertmanagers

Reopening, since there seems to be another sync hang issue


version deprecation notice does not mention the CLI flag

In the Electron Slack channel, there have been several questions about why --electronVersion does not work. It occurred to me today it was because that the deprecation message for the version option says:
The version parameter is deprecated, use electronVersion instead

What it should say is:
The version parameter is deprecated, use electronVersion instead (or --electron-version in the CLI)

PR filed: #560


Add a menu option to edit config file.

Should open the configuration file in the default text editor for the machine.
Note this has only been tested in Linux.
Addresses #328

This doesn't seem to open an editor for me. (OSX 10.10.5). I'll look into this further shortly

@jwrb most likely that's cause there is no system default editor for .conf files.

Double clicking config files opens them up just fine. Using the open command in terminal also works as expected (opening the files in sublime text)
 open ~/Library/Application\ Support/Paycoin/paycoin.conf

Works just fine. So I'm not sure this is a system issue. More the way it's implemented?

Why did this also get merged? Didn't we merge #409 which is the same?

Hmm yes it shouldn't have been merged but because the two commit IDs are identical to the ones in #409 it actually had no ill effect.

@jwrb aye that was my bad but as @mitchellcash said they're identical so no ill effect... Either way, oops.


Template and Service resources in Applications should required partition

@pjbreaux
Take a look at the code I added because I assume you also want partition for the template.load() so I added it as a required refresh parameter.  Maybe this isn't right?
Also added unit and functional tests for the new arg.
Issues:
Fixes #200
Problem:
Partition should be requred for template and services for iApps when they are created instead
of letting the system add whatever partition it wants.
Analysis:

Added 'partition' to the self._meta_data['required_creation_args']
Added 'partitoin' to the self._meta_data['required_refresh_args']
Added unit and functional tests to cover the new parameters.

Tests:

Ran all functional tests
Ran all unit tests

Looks good. Merging.


run preprocessing button is not displayed

After creating a new dataset then going to the preprocessing tab, no preporcessing button is displayed.

Closed by https://github.com/girder/otm-client/commit/76af47f44c061b9a0f5d5b001c709eae83bd2880


backdating steps on conductor doesn't work right

I was working in contract A-083-14 to change the date it was started to a few days earlier than when we originally marked it.  I went in and hit the mark complete button and the box keeps opening and closing making it nearly impossible to actually type in a date.
After I finally got it completed, it made the 'step complete in -22 hours' which is very odd.

Working on this now.


a particular youtube channel could not be downloaded,

I tried to download the channel https://www.youtube.com/user/livedreams2. After executing the command, it tried to download the pages and says that the channel had been terminated.  but, I still can access the channel and watch videos in the channel. Could it be problems with the downloader?
thanks

Carefully read new issue template and provide all requested information.


⚠ Bofrost.fr has degraded performance

In 0f0ef06, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1240 ms

Resolved: Bofrost.fr performance has improved in fadbc30 after 15 minutes.


add FontAwesomeKit.Swift

Add FontAwesomeKit.Swift in README.md
Project URL

https://github.com/qiuncheng/FontAwesomeKit.Swift
Description

😀😘A better choice for iOS Developer to use FontAwesome Icon with UI.😍
Why it should be included to awesome-ios (optional)
Easy to use and so lightweight.
Checklist

[x] Addition in chronological order (bottom of category)
[x] Supports iOS 8 or later
[x] Only one project/change is in this pull request
[x] Supports Swift 3
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Error

  :no_entry_sign:
  Found 3 link issues

Link issues by awesome_bot

Line
Status
Link

1447
301
https://github.com/OEASLAN/OEANotification redirects tohttps://github.com/OEA/OEANotification

2285
301
https://github.com/sxyx2008/awesome-ios-animation redirects tohttps://github.com/ameizi/awesome-ios-animation

2286
301
https://github.com/sxyx2008/awesome-ios-chart redirects tohttps://github.com/ameizi/awesome-ios-chart

  Generated by :no_entry_sign: danger

thx


NEED Help ASAP

FYI python updated
Traceback (most recent call last):
File "SocialFish.py", line 25, in
from core.view import *
File "/opt/SocialFish/core/view.py", line 14, in
from huepy import *
ModuleNotFoundError: No module named 'huepy'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "SocialFish.py", line 28, in
import pip
ModuleNotFoundError: No module named 'pip'

same problem !!


Set '[dap-repl]' buffer to 'nobuflisted'

REPL buffer is set to listed by default.
Is there any way to set REPL buffer to unlisted by configuring nvim-dap-ui?

No nvim-dap-ui does not control the REPL buffer, but you can do
vim.api.nvim_create_autocmd("FileType", {
  pattern = "dap-repl",
  callback = function(args)
    vim.api.nvim_buf_set_option(args.buf, "buflisted", false)
  end,
})

No nvim-dap-ui does not control the REPL buffer, but you can do [...]

@rcarriga I just encountered the same question/problem: After calling require('dap').terminate() I expect all dap-related buffers will be deleted. In the current status, the only buffer left is the one named [dap-repl]:1. Are you still recommend creating the FileType-autocmd ourselves?


When debugging Python code, you can display the shape or size of tensors, matrices, lists, etc

Deep learning debugging is more concerned with shape or size. It would be more useful if the shape or size of tensors or matrices could be displayed first during debugging, as is the case with pycharm.
In vscode:

In pycharm:

This is an issue for debugpy or the Python extension


Support IME?

I like this great project, but it seemed IME is not supported for now (at least in Windows).

I'm sorry,  what are you referring to when you say IME?

IME is the Input Method Engine/Module, which is for input non-western character text, see following screenshot:

Oh, my mistake, I use a wrong page code, and that cause the IME disabled.


Bug search field on IE

Search field to facilitate the search for options until the ok time:
Firefox (ok)
Chrome (ok)
With problems:
Internet Explorer (is being fixed, for v1.1.1)

IE loses reference to the <li>  cached when we clear the list, then in IE and modal options will be filtered through the element visibility.
However, if liability to optimize the specific code, will soon in the next versions


Add completion for php defaults functions and classes

These should be done using https://github.com/JetBrains/phpstorm-stubs


The detected CUDA version (11.8) mismatches the version that was used to compile       PyTorch (12.1). Please make sure to use the same CUDA versions

RuntimeError:
The detected CUDA version (11.8) mismatches the version that was used to compile
PyTorch (12.1). Please make sure to use the same CUDA versions.

my torch version is 2.0.1

If your cuda version is 11.8, this command might help:
pip install torch==2.0.1+cu118 torchvision==0.15.2+cu118 --index-url https://download.pytorch.org/whl/cu118

Ref: https://pytorch.org/get-started/previous-versions/

same problem,mark

If your cuda version is 11.8, this command might help:
pip install torch==2.0.1+cu118 torchvision==0.15.2+cu118 --index-url https://download.pytorch.org/whl/cu118

Ref: https://pytorch.org/get-started/previous-versions/

I have a very similar problem:
The detected CUDA version (11.7) mismatches the version that was used to compile
PyTorch (12.1). Please make sure to use the same CUDA versions.
And I use this:
pip install torch==2.0.1+cu117 torchvision==0.15.2+cu117 --index-url https://download.pytorch.org/whl/cu117
but still I recive the same error. Can you help me?

@128Ghe980 Make sure that you run pip install in your conda env.
Try python -c "import torch; print(torch.__version__)". The output should be 2.0.1+cu117

@Tan-YiFan pip install -e . gave me the error as described in https://github.com/vllm-project/vllm/issues/1453#issue-1958405821
pip list | grep torch shows that I have torch 2.1.0+default installed. However, I couldn't import torch to check its version, because it gave me another error:
18:53 $ python
Python 3.9.0 (default, Nov 15 2020, 14:28:56)
[GCC 7.3.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import torch
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/yi_wang999747/miniconda3/envs/vllm/lib/python3.9/site-packages/torch/__init__.py", line 235, in <module>
    from torch._C import *  # noqa: F403
ImportError: /home/yi_wang999747/miniconda3/envs/vllm/lib/python3.9/site-packages/torch/lib/../../nvidia/cusparse/lib/libcusparse.so.12: undefined symbol: __nvJitLinkAddData_12_1, version libnvJitLink.so.12

I uninstalled PyTorch 2.1.0 and installed PyTorch 2.0.1. Then I do not longer suffer from the above error.

The error message in https://github.com/vllm-project/vllm/issues/1453#issue-1958405821 means

You have NVCC version 11.8 installed on your host / conda env.
You are using it to build vLLM's PyTorch extensions as listed in the setup.py file.
You have PyTorch installed on your host / conda env.
The version of NVCC used to build PyTorch is 12.1
You must use NVCC 12.1 to build vLLM's PyTorch extensions

So, you need to upgrade your CUDA / NVCC to version 12.1.

modify torch version to 2.0，is ok

same question with cuda11.8，mark

I'm getting this error in a Docker build, So I don't thick the problem is in my system. Am I wrong?
made this issue for tracking: https://github.com/mistralai/mistral-src/issues/76

Starting from vLLM v0.2.2, PyTorch v2.1 + CUDA 12.1 is supported. If problems are not solved, it might help to use vLLM >= v0.2.2.

Unfortunately I am still experiencing this issue. The script keeps telling me that
The detected CUDA version (11.8) mismatches the version that was used to compile
      PyTorch (12.1). Please make sure to use the same CUDA versions.

Even though I have only specifically installed cu118. Even more so, nvcc- --version yields 11.8 and python -c "import torch; print(torch.version.cuda)" also prints 11.8. So I have no idea where this 12.1 is coming from but it seems to have to do with the extensions that it is loading. So I wonder whether there is a mismatch between those that come with the library and PyTorch.

Same problem with @BramVanroy , have you solved the issue? Thanks

Same problem with @BramVanroy , have you solved the issue? Thanks

Sadly, no.

Same Problem.

Hi guys, not sure this will help, but I was troubleshooting this myself for another repo (GroundingDINO) and managed to solve the issue so just sharing the solution.
I think this error occurs when the pip creates a temporary python environment to build some package, but that temporary environment may fetch a version of pytorch that's compiled with a different version of cuda than your system. To fix this, you can use the command pip install --no-build-isolation package_name, so for example for the GroundingDINO package it would be:
pip install --no-build-isolation -e GroundingDINO

pip install --no-build-isolation -e . fixed the problem. Thank you, @alik-git

Hi guys, not sure this will help, but I was troubleshooting this myself for another repo (GroundingDINO) and managed to solve the issue so just sharing the solution.
I think this error occurs when the pip creates a temporary python environment to build some package, but that temporary environment may fetch a version of pytorch that's compiled with a different version of cuda than your system. To fix this, you can use the command pip install --no-build-isolation package_name, so for example for the GroundingDINO package it would be:
pip install --no-build-isolation -e GroundingDINO

Thank you @alik-git ! You saved my day!

pip install --no-build-isolation -e GroundingDINO

so do I replace 'GroundingDINO' with 'torch'?
sorry for the question, newbie here

Yes that's right, whatever the name of your package that you want to install is

If your cuda version is 11.8, this command might help:
pip install torch==2.0.1+cu118 torchvision==0.15.2+cu118 --index-url https://download.pytorch.org/whl/cu118

Ref: https://pytorch.org/get-started/previous-versions/

In my case the error is -
"The detected CUDA version (10.0) mismatches the version that was used to compile
PyTorch (12.1). Please make sure to use the same CUDA versions."
I can not seem to find any command that suits it. Kindly help.

The following command  can fix my same problom.
 pip install -U  torch==2.3.1 torchvision==0.18.1 torchaudio==2.3.1 --index-url https://download.pytorch.org/whl/cu118

code from pytorch website
https://pytorch.org/get-started/previous-versions/

pip install --no-build-isolation -e . fixed the problem. Thank you, @alik-git

thanks, it helps.