Removed font-manager === THIS FIXES THE BLANK SCREEN ERROR DIALOG

I jumped in to debug this assuming it was some native issue based on the type of error with no info
-- added a touch of logging for errors and onerror to mancy window
-- added gulp task to recompile font-manager
-- after some testing - font manager on sierra is flakky with many fonts

removed font manager - left task to recompile it for the future - everything compiles now

this should fix the crash issues for a lot of people

@princejwesley any chabnce of getting the fonts update in so the distro version works everywhere?  I use a bunch of computers so it would be cool - but trust me I understand being busy!

@jglanz this weekend I'll update and share the new version! thanks


Add UniqueContactList

Description
Part of #64. This PR implements UniqueContactList, which is adapted form UniquePersonList. This is necessary since the AddressBook class uses UniquePersonList to keep track of Person objects.

LGTM


WACZ reading / streaming

(Suggested by @ikreymer)
Add a command and associated API for reading and streaming the contents WACZ files, either locally or remotely.
See: https://www.npmjs.com/package/unzipit

(Suggested by @rebeccacremona)
This feature should allow for specialized / simplified extractions such as:

Extracting the CDX of a WACZ
Extracting the datapackage signature
Looking up for a specific record in the underlying WARC(s)
etc...


我查看表数据的时候为什么会出现这个错误，查看其它的表又没问题的Error 3010014: Invalid symbol  Error Details:precision 219 should be <= 18 Unable to unpack built-in type 'asset' while processing 'betamount'

This is caused by data that was written by a different version of the contract ABI.  It can no longer be deserialized correctly using the currently loaded ABI.  If it is an account you control, you should load a version of the contract that can read both formats and migrate the data from the old to the new format.  If it is an account you do not control, you will need to find the old format and deserialize the hexadecimal string yourself.

"cleos get table" got the error just like the issue description. 在2019年02月01日 04:48，jgiszczak 写道： What does the table look like when you use cleos get table to retrieve the data? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

As I said originally, the ABI must match the table definition, or deserialization won't work.


Create editionable worldwide org

https://trello.com/c/3WmL0sbs
Add feature flag for editionable worldwide organisations
Add basic editionable worldwide organisation
The existing worldwide organisation modelling presents various issues.
Worldwide organisations surface the main body of their content through an
associated corporate information about us page. Issues include:

Draft pages don't update correctly #8358
We redirect from the base path of the corporate information page back to the
worldwide organisation #8037

We want to add new "editionable" worldwide organisations in order to improve
this area of Whitehall. The intention being that these eventually replace the
existing worldwide organisation models.
This adds the basic routes, model and controller actions. The actions are
behind a feature flag.
No publishing API presenter is configured yet.

⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠
Follow these steps if you are doing a Rails upgrade.

[...] or broken 👍

Other than that erblint CI step

[...] or broken 👍

Other than that erblint CI step

Didn't notice that sorry!

One comment but otherwise looking great, thanks

Ooh, as a slight aside would you mind adding instructions in the PR description on how to set the feature flag up in a docker environment? I had to delete the feature flag changes to see it because I was too lazy to work it out

There is a doc here https://github.com/alphagov/whitehall/blob/main/docs/feature_flags.md


Support for Italian mnemonics

Coverage remained the same at 94.529% when pulling dac96cf18b03dc1676feec2b2bf8057bcd875b86 on isocolsky:bump/bitcore-mnemonic into 7f15c05f80e976c62fe5f9345516bc1444eb785f on bitpay:master.


License detection needs to match libappstream

There has been some controversy recently around GNOME Software misidentifying unknown/obscure licenses as proprietary - https://gitlab.gnome.org/GNOME/gnome-software/-/issues/2004
So the "source of truth" in terms of whether something is free or not is v. important - I think the only way we as a community can get this right and improve over time is to ensure we share the list(s).
Flathub must use either the same code or the same list and logic as libappstream so we can focus our efforts into one place. (https://github.com/ximion/appstream/blob/master/src/as-spdx.c#L741 + https://github.com/ximion/appstream/blob/master/data/spdx-free-license-ids.txt)

This has been implemented.


Checkboxs are broken in current version (1.2)

This was just a simple Yes/no checkbox. No label and the checkbox are spit out in groups of two.
Screenshot below

I addressed this in https://github.com/xodigital/Formerly/pull/11 - so you can see the fixes there :)

sample fixed in 1.3.1 15253789a318c2c1d9e0697d5f90213c0ca9beea


When a single page, picture carousel can be used, but as a component of the time, only the following points, pictures do not move.

‘window’
Version
Which versions are you using:

react-native-swiper 1.5.13?
react-native v0.48.4

Expected behaviour
When a single page, picture carousel can be used, but as a component of the time, only the following points, pictures do not move.
I used navigation in TabNavigator to do the bottom switch, Swiper as a component can not be used, only the following points active, the picture does not follow.

Actual behaviour

How to reproduce it>
To help us, please fork this component, modify one example in examples folder to reproduce your issue and include link here.

你是autoplay的时候，下面的点在动，但是图片不动吗？我也是这个问题，然后滑动的时候，每次只滑动一点，旋转手机屏幕以后就恢复了，现在解决了吗

@ZiQiangWang @CJX27 I have the same problem. Have you solved it?


Callback is not called with local minima of initial guess in basinhopping algorithm

My issue is about ...
As far as I understand, callback function is called when a local minima is found. When I use basinhopping global minimization algorithm, I have observed that the callback function is not called when local minima is found for initial guess. I have tried to reproduce this issue with the following example:
from scipy.optimize import basinhopping
import numpy as np

def func(x):
    print("Objective function count: " + str(func.counter))
    func.counter += 1
    return np.random.rand(1)*1000

def callback_func(x, f, accepted):
    print("Callback count: " + str(callback_func.counter))
    callback_func.counter += 1

func.counter = 0
callback_func.counter = 0
x0 = 2000

minimizer_kwargs = {"method": "COBYLA", "options":{"maxiter": 1}}
optimizer = basinhopping(func, x0, minimizer_kwargs=minimizer_kwargs, niter=2, callback=callback_func)

It produces following result:
Objective function count: 0
Objective function count: 1
Callback count: 0
Objective function count: 2
Callback count: 1

For the above mentioned example, both callback function and the objective function should have been called thrice but callback is called only twice.
Scipy/Numpy/Python version information:
 1.2.1 1.16.4 sys.version_info(major=3, minor=7, micro=4, releaselevel='final', serial=0)

The callback is called once per basinhopping iteration. You set niter to 2 for basinhopping, so I would only ever expect the callback to be called twice.

With all due respect, I disagree with your previous comment. There is a local minima that is obtained from the initial guess and that information is not passed to the callback function. By this I mean to say that, suppose I am gathering all the predicted local minima's achieved by exploiting callback function then I will not be having any data regarding the local minima obtained by starting from initial guess. I will surely have data for further iterations but not for initial guess and this is where my problem is.
I hope I am able to explain my problem properly.

There is a local minima that is obtained from the initial guess and that information is not passed to the callback function. By this I mean to say that, suppose I am gathering all the predicted local minima's achieved by exploiting callback function then I will not be having any data regarding the local minima obtained by starting from initial guess.

I'm not sure I understand what you mean. The initial guess is just that, a guess - it's not a minimum.
The code structure is simple here:
    for i in range(niter):
        if callable(callback):
            val = callback(...)

So @andyfaff's answer seems right, niter is an upper bound on the number of times the callback function is called.

Maybe with the following example, I would be able to convey myself:
from scipy.optimize import basinhopping
import numpy as np

def func(x):
    print("Data passed to objective: " + str(x))
    print("Objective function count: " + str(func.counter))
    func.counter += 1
    return np.random.rand(1)*1000

def callback_func(x, f, accepted):
    print("Data passed to callback: " + str(x))
    print("Callback count: " + str(callback_func.counter))
    callback_func.counter += 1

func.counter = 0
callback_func.counter = 0
x0 = 2000

np.random.seed(1)

minimizer_kwargs = {"method": "COBYLA", "options":{"maxiter": 5}}
optimizer = basinhopping(func, x0, minimizer_kwargs=minimizer_kwargs, niter=1, callback=callback_func)
print(optimizer)

The output is as follow:
Data passed to objective: [ 2000.]
Objective function count: 0
Data passed to objective: [ 2001.]
Objective function count: 1
Data passed to objective: [ 1999.]
Objective function count: 2
Data passed to objective: [ 1998.]
Objective function count: 3
Data passed to objective: [ 1998.5]
Objective function count: 4
Data passed to objective: [ 1998.59233859]
Objective function count: 5
Data passed to objective: [ 1999.59233859]
Objective function count: 6
Data passed to objective: [ 1997.59233859]
Objective function count: 7
Data passed to objective: [ 1998.09233859]
Objective function count: 8
Data passed to objective: [ 1998.84233859]
Objective function count: 9
Data passed to callback: 1998.5923385947688
Callback count: 0
     nit: 1
     fun: 0.11437481734488664
    nfev: 10
 message: ['requested number of basinhopping iterations completed successfully']
       x: array(1999.0)

For this example, I have used maxiter for COBYLA as 5 and the objective function was called 10 times for niter of 1. This shows that local minimization was performed twice but the data related to local minima was passed to callback only once.

@rgommers, @prince2110, I think I've got to the bottom of this.

the callback function is indeed called once per basinhopping iteration.
However, when the BasinHoppingRunner is constructed, there is an initial minimisation. This initial minimisation is not set to the callback function. As the documentation is written it probably should be, but that initial minimisation would not be after a basinhopping step had been taken. At the worst this would result in niter+1 callbacks for niter steps.

If my previous commit in the wrong PR solves this issue, then can I again submit a new pull request ?

I've already done one, #13029.


Missing dockerhub credentails

The only source of our credentials are stored encrypted within travis, we cannot copy them over and we need to do a password reset and then update the credentials into our secure storage in a way that allows us to add new projects in the future.
Right now this means that if we want to use containers, we have to either create a new account, or use ECR. Both of these mean giving individuals more access to assets which we are doing out of convenience but why not just fix the issue and limit prod and asset access.

Reset creds in dockerhub
Get new creds and store into 1PW
Update creds within frontend, backend and new frontend.
Incorporate other projects to use dockerhub instead of ECR.

Sent a query to DockerHub support around recovering the operationcode user.

No response from DockerHub. Not even an automated email :(

After reaching out on Twitter, I got these credentials reset today. They've been added to 1Password, and updated the operationcode_backend and operationcode_frontend repos in Travis.


Add line index and character index to tokeniser state

Untagged from milestone 1.0, as we will not be able to complete

Tokenizer doesn't exist anymore


Default values are not overridden

Hello everybody. I have some problems with connecting to consul. I have next values in my bootstrap.properties:
spring.cloud.config.overrideNone=false
spring.cloud.config.overrideSystemProperties=false
spring.cloud.config.allowOverride=true

But they are not overrode default values in PropertySourceBootstrapProperties. I think that there is mistake in this place:
https://github.com/spring-cloud/spring-cloud-commons/blob/941275ded2fca60f4320df6fe9bceb8fdf172f25/spring-cloud-context/src/main/java/org/springframework/cloud/bootstrap/config/PropertySourceBootstrapConfiguration.java#L155
Because, in my case, new values are not available from incoming object. This object has field  propertySources. This field contains two objects with type of ConsulPropertySource. Therefore, new values are not loaded from bootstrap.properties
If i am not right, please give me an advice, how i can set props correct for loading values from property file without overriding values from consul.

Sorry for disturb, i thought these properties must be in bootstrap.properties or application.properties.


logger: use fabulous functions for creating new writer

This PR adds support for using fabulous on Windows, with all the colors. 🌈

Rainbows on Windows


Add data in intents_thai and intents_eng krub!

Add some word in data/intents_en  and intents_th krub!

Nice one, thank you for adding stuff here.


[MRG] edits drop high psi docs

Hi @gverbock
thank you so much for such great work!
very well done! the docs contain a lot of information
Here I add edits to most files. Changes wording mostly.
I am still working on the main file you edited, the DropHighPSIFeatures.rst. In short, I still need to go over the code examples. But they look great, so it would mostly be changing a bit the wording here and there and making sure that no output is missing.
Thanks a lot!

@gverbock ready to merge :)


svlogd can't write with /var/log at 0700

Some customers set /var/log 's mode to 0700, which breaks Chef Server 12.3.1+ initial reconfigure.
/var/log/opscode is either not present or unwritable even if present and the reconfigure fails.

The change itself looks fine, but I think customers who have set it to 0700 may be upset to find that installing Chef Server has changed that without telling them?

To clarify further: I think this belongs in preflight checks, and we can fail gracefully with an error message telling them to how to create the directory manually and set required permissions.

Closing in favor of issue #847 after discussion with @sean-horn


Mono/C# support for UWP

After Android (#20267), iOS (#20268) and HTML5 (#20270), we'll likely want to bring Mono/C# export support for UWP. This issue is to discuss what needs to be done and the progress.
CC @neikeq

This may already be working. Has anyone tried it?

I can try testing on Windows. Ideally this should be tested on an ARM device and on Xbox One too, but I don't have any of these devices.

Eh, I can't even build with the Mono module enabled...

Need to change this to include UWP: https://github.com/godotengine/godot/blob/b2d7641a0dd65a782f981fb1f73c5e84a90f816c/modules/mono/config.py#L85

Those I can't get around:
modules\mono\utils\mono_reg_utils.cpp(61): error C3861: 'RegOpenKeyExW': identifier not found
modules\mono\utils\mono_reg_utils.cpp(64): error C3861: 'RegOpenKeyExW': identifier not found
modules\mono\utils\mono_reg_utils.cpp(75): error C3861: 'RegQueryValueExW': identifier not found
modules\mono\utils\mono_reg_utils.cpp(81): error C3861: 'RegQueryValueExW': identifier not found
modules\mono\utils\mono_reg_utils.cpp(125): error C3861: 'RegCloseKey': identifier not found
modules\mono\utils\mono_reg_utils.cpp(147): error C3861: 'RegCloseKey': identifier not found
modules\mono\utils\mono_reg_utils.cpp(225): error C3861: 'RegCloseKey': identifier not found
inner_prod_aligned.c

It's not possible to access the registry on UWP.

Is it possible to use the .NET framework instead of Mono?

@vnen That's how Unity does it, they use .Net (Core? I believe) for UWP, and then typically use Mono for everything else.

@NathanWarden I mean if Godot can already do it, if there's some build flag to enable it.

@vnen That makes sense. I'm very sure you're on the right track, but I don't think that has been added. I haven't seen it yet at least. I can't imagine it would be too difficult though.
Were you thinking the build flag should just include .Net Core as an additional target (for use only with UWP), or to replace Mono entirely when built with that flag?

It should replace Mono. I don't see a reason to add Mono stuff to the binary and not use it.

That makes a lot of sense, unless UWP builds are going to be available in Godot proper at some point. .Net Core is a very stripped down version of .Net and is incompatible with both Mono and .Net proper in a lot of places.
So, I suppose the idea is this would be a version that people just have to compile from source for now.
How Unity supports both is that they spit out the compile errors to the console for the incompatibilities at build time with .Net Core since their UWP template obviously uses it. It's a little bit annoying, but much better than limiting the API across the board. I think they build the .Net Core assembly against msbuild at export time. Thus, you can still just have one version of the editor, but the UWP build template is .Net Core only.
So, essentially, Unity builds the UWP template against .Net Core, but builds the editor against whichever .Net version they're using. Actually, they have multiple right now that you can select from.
Sorry if I've just made a rabbit trail out of this. I suppose all you're trying to do is just simply seeing if a Godot build can compile against UWP :)

Well, I'm the maintainer of the Godot UWP port (or at least I try to), but I'm not really willing to put much effort into the C# support. So if @neikeq can make it work with .NET I can help with the UWP part.
With UWP we can add the dependencies in the manifest which are installed automatically, so it probably doesn't need any additional library.

I hear you, it would be quite a bit of effort. Plus, it doesn't have to all be perfect on the first pass either. Thanks for all of your hard work :)

Moving to 3.2 milestone, for 3.1 the focus is on getting the desktop platforms in good shape, plus maybe Android support if we can figure out the buildsystem.

@vnen I am excited that there is interest on Godot for UWP.
I see lots of potential for Godot as an alternative to Unity for Hololens 2 that is running on Snapdragon 850.
I believe Hololens OS is a variant of the Windows 10 on ARM
I am interested to know if there is a community interest to
(1) Get Godot running native in Windows 10 on ARM, as a step to get Godot eventually running on Hololens 2
(2) raise Microsoft Hololens team to include Godot as one of the game engine

I am closing these issues so we can focus on getting UWP to export consistently
Other issue identified

This won't happen until at least June as it's not part of my current roadmap. It should not require much work to get this done as I suppose it will share most of the code from Windows, but I have zero experience with UWP.

@neikeq After seeing the recent VR Occulus Quest, Godot is getting extremely exciting. I see Godot has lots of potential. Among the platform, UWP has the biggest need for Godot. There is simply nothing like this. But Microsoft technology is rapidly converging towards UWP.
When I finally has time to start compiling Godot, I will have a clearer picture of why it is difficult for UWP. Why the community fails to see the potential.
There are different options towards UWP.
The current option, if I understand correctly is UWP console. THis is LIKE EVERYONE Else, this is not the one BIG GAP the microsoft community needs.
We need UWP control. This is where everyone in Microsoft is talking. Another word for that is WinUI
Converting UWP console to UWP control is doable. I can not say much until I know enough of godot engine
Hopefully there are enough curious developer to look into that to drive godot into more awareness.
The biggest OBSTACLE right now:
WE need SDK project and .NET standards 2.0 to 2.1 ASAP.
This is preventing proper exploitation of Godot for Microsoft development technology

@GeorgeS2019 If anything, UWP seems to be getting less and less popular among Microsoft product users.

@Calinou   This is STANDARD observation!!!!  :-)  There are lots of debate at Windows Central on this topic
The key point:  After CES2020
The rise of Snapdragon, Windows on ARM.
I know there is also a plan to export to Windows on ARM
BUT UWP  (Control, not console) will empower the community, WILL DRAW microsoft to continue putting grant to GODOT like previous year.
I see GODOT not just for gaming, but application, VR and hopefully MR/AR  that all headset SDK need

Is this proposal to be included in 4.0 milestone?

Hopefully, the benefits of the UWP .Net Native compiler will not get lost in the mix.  Some projects require perf and a much harder path to disassembly.  The UWP .Net Native compiler is quite mature at this point.  Its compiled code is not a open book.  JIT only makes sense if you don't care about folks peering into your work since you are effectively releasing the source for modules that need to be jitted.  Byte code obfuscation is both a drag on perf and stability.

@Noemata The godot community is fantastic in moving good ideas forwards. This issue is on milestone 4.0. The community needs professionals who know more of UWP, .NET5 to plan the best path forwards. Welcome!

A more recent update on the status of Godot UWP export
Hopefully we have similar Up-to-date feedback on the feasibility to create Godot UWP export using mono/c#

Status of UWP in milestone 4.0

Full disclosure: I'm blind, am using Godot to build mostly audio games, so I can't comment on whether or not rendering works. I did eventually enable file-logging and do see a render error, but blamed it on running in a VM with limited graphics capability. I'll look at the rendering issue and figure out if I'm experiencing it or not.
So, IOW, if you're determining that rendering works based on my experiences, don't. :)

@ndarilek I am listing these old issues here because it will be good to get an update to see if these old issues still critical for getting UWP Godot app to work properly after export.

I get it. I just wanted to make sure you weren't flagging rendering as
working because of my experience. If it's because of someone else's,
perfect. :)

Is there any news in the meantime? If I understood the hints in other Godot issues correctly, Godot 4 will properly use .NET 5? This step would be very welcome. .NET 5 is very fast.

@SommerEngineering The plan is to keep using Mono for the foreseeable future, as .NET 5 doesn't really have good mobile support yet. Hopefully, .NET 6 should have better mobile support.

@SommerEngineering The plan is to keep using Mono for the foreseeable future (including for Godot 4.0), as .NET 5 doesn't really have good mobile support yet. Hopefully, .NET 6 should have better mobile support.

It looks like .NET 6 is tentatively planned to be final by November 2021. Though understandably that date may be subject to change, I have no insight into the process. But I did see they have just released preview 4, so hopefully it's stabilizing. Also not sure about if it has better mobile support yet.

Also, UWP requires many fixes to be in a functional state for Godot 3.2 before we can consider adding C# support.

@Calinou Just curious, would you say this is still the case? Are there still a lot of unresolved issues with UWP exports?

@Calinou Just curious, would you say this is still the case? Are there still a lot of unresolved issues with UWP exports?

Yes.

This issue is only relevant for the 3.x branch as there is no UWP support in 4.x.
After all this time has passed, I think I can confirm that there are no official plans to implement Mono support for UWP in 3.x. The focus of the .NET contributors is on reaching platform support parity for .NET 7/8 in Godot 4.x (Android was just added, iOS and Web are still missing).


Bump to Core/Software 7.8.1 and Service Desk 3.11.1

Description of the Change
Bump versions to:

Core/Software: 7.8.1
Service Desk: 3.11.1

Verification Process
docker build -t blacklabelops/jira .

Applicable Issues

https://confluence.atlassian.com/jiracore/issues-resolved-in-7-8-1-947165858.html
https://confluence.atlassian.com/jirasoftware/issues-resolved-in-7-8-1-947165844.html
https://confluence.atlassian.com/servicedesk/issues-resolved-in-3-11-1-947165885.html

Thanks for the version update!


Update tutorial-pipeline-batch-scoring-classification.md

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


Add "chr"

Missing "chr" prefix so this fails.

Depending on the used annotation, chromosome format may or may not have chr prefix. Suggested changes do not add more generalization or fix any problem. Please use the provided code with the notion that it may need to be tailored for each specific use case.


SHB result

Hi，there:
I retrained SH-B with the code and the hyper-parameters given; However the best MAE was 7.6, which is far different than the result given by the paper. Is there any tricks I should conduct in order to replicate your result?

Different environments may result in different optimal epochs. You may try to train the model for 2000 or 3000 epochs (optionally, add torch.backends.cudnn.deterministic = True before training for reproducibility).
In general, SHB and SHA share the same training parameters.


Add kitspace.yml for rev C1

Add kitspace yaml to facilitate ordering rev C1 boards and components via https://kitspace.org

What happens when we add another board release? The format of the Kitpace file doesn't seem to allow for more than one per repository at a time.

What happens when we add another board release? The format of the Kitpace file doesn't seem to allow for more than one per repository at a time.

I believe this is implemented by using multi: as per https://github.com/kitspace/kitspace#the-multi-field

Okay, can you use that right away?

Good question, I'm asking the Kitspace maintainers now

Closing in favor of #195


bump contour to 1.30.1

adjust linter settings
bump contour to 1.30.1

Looks like there's a regression with contour v1.30.1 and a bunch of our tests

/hold

Asked if there are known issues here - https://kubernetes.slack.com/archives/C8XRH2R4J/p1734754791329519
Unfortunately, don't have time to investigate this


Add Duchess of the Zoo (still jumper) by Krayon Koz

Song Name
Duchess of the Zoo (still jumper)
Artist Name
Krayon Koz
Source
Youtube
Youtube Link
gU4DIN-NrOWL8P92
Direct File Link
No response
Song ID
6
Start Offset [ms]
0
Extra
Created from Auto Nong.
As the name suggests, jumper is literally the beat koz uses with no changes or remixes

reject
invalid YouTube link


The operator 'aten::nonzero' is not currently supported on the MPS backend and will fall back to run on the CPU

Setup - Macbook Pro M1 64gb
I am able to run the script locally and generate images but I see this warning. I am currently getting 1.47it/s, is that typical for this setup or slower than normal? A standard 512x512 images takes around 30seconds with 50 iterations.
/stable-diffusion/ldm/modules/embedding_manager.py:153: UserWarning: The operator 'aten::nonzero' is not currently supported on the MPS backend and will fall back to run on the CPU. This may have performance implications. (Triggered internally at /Users/runner/work/_temp/anaconda/conda-bld/pytorch_1663657712311/work/aten/src/ATen/mps/MPSFallback.mm:11.)

That is typical for this setup, and this is a duplicate issue of #262.

Are you using pytorch-nightly? Yes, this warning is common, although your times are slower than mine (26-27s, also with 64GB and for 512x512).
I'm using Pytorch 1.12.1 which is a bit faster, so it might be that.

Yes, I am using pytorch nightly. For some reason the setup didn't work with the regular stable version. Let me give it a try again to go back to 1.12.1. Thanks.

Oh, that's most likely it then! Let me know if it gets faster :)

There a general issue for unsupported MPS operations in the pytorch GitHub
https://github.com/pytorch/pytorch/issues/77764#issuecomment-1254553391
Worth going there and giving atenL::nonzero an upvote.

This is a known upstream issue (not really a problem; it is expected) related to the ongoing implementation of pytorch operations on MPS.


Update dependencies and silence fast-float audit.

Closes #21
Closes #22
Closes #23
Closes #24
Closes #25

This has issues with our development dependencies requiring a significantly higher MSRV in simple-bench, which removing it as a workspace member should fix.


chore(deps): CVE-2024-37890 force ws resolution to 8.17.1

Description
1.2.x CVE 2024 37890 force ws resolution to 8.17.1
Corresponding PR: https://github.com/janus-idp/backstage-showcase/pull/1728
Which issue(s) does this PR fix

Fixes #? https://issues.redhat.com/browse/RHIDP-2733

PR acceptance criteria
Please make sure that the following steps are complete:

[ ] GitHub Actions are completed and successful
[ ] Unit Tests are updated and passing
[ ] E2E Tests are updated and passing
[ ] Documentation is updated if necessary (requirement for new features)
[ ] Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

Looks good - should there be a PR for 1.3 branch too?

Looks good - should there be a PR for 1.3 branch too?

This should have been for release-1.3

hmm... moved target to release-1.3 and created a lot of conflicts. Oops.  Might be best to start over with a fresh PR @Fortune-Ndlovu

fresh pr: https://github.com/janus-idp/backstage-showcase/pull/1762


python3Packages.platformdirs: 3.5.1 -> 3.9.1

Description of changes
fixes https://github.com/NixOS/nixpkgs/issues/242935
https://github.com/platformdirs/platformdirs/compare/3.5.1...3.9.1
I am still running nixpkgs-review but I feel like it will not finish any time soon
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

included in #244135

@SuperSandro2000 its my 100th closed/merged PR ! you win a small prize !


Per media-query font-size adjustement

Since initial idea with rems didn't worked out https://github.com/ArmorDarks/ekzo.sass/issues/40, we have to consider some better options.
So far:

Do everything manually
Enhance current $ekzo-font-sizes map to carry information about font-sizes for specific elements for specific breakpoints.

$ekzo-font-sizes: (
  text: (
    base: (
      phone: 14px,
      phone-ls: 14px,
      tablet: 16px,
      tablet-ls: 16px,
      lap: 16px,
      desk: 16px,
    ),
    '--': (
      phone: 12px,
      phone-ls: 12px,
      tablet: 14px,
      tablet-ls: 14px,
      lap: 14px,
      desk: 14px,
    ),
    '-': (
      phone: 11px,
      phone-ls: 11px,
      tablet: 12px,
      tablet-ls: 12px,
      lap: 12px,
      desk: 12px,
    )
  )
) !default;

but this looks like... too much...

Responsive helpers seems to be quite elegant solution to that issue. And quite modular.
Going to test it out on production...


Version v0.2.1: 2014.04.22 fails to boot from SD card

Galileo Firmware is updated to the latest version (state May 2014). I have SD card (Toshiba 30MB/s) that works fine when I use it to boot Intel's Linux Image 0.7.5.
If I put on the same card the files of ConnectAnyThing Version v0.2.1: 2014.04.22 then the terminal on Galileo's UART shows me the following boot messages:
...
[    3.176256] mmc0: new high speed SDHC card at address 0007
[    3.200865] mmcblk0: mmc0:0007 SD08G 7.21 GiB
[    3.235781]  mmcblk0: p1
[    3.251098] tsc: Refined TSC clocksource calibration: 399.076 MHz
[    3.257435] Switching to clocksource tsc
[    3.383128] udevd[543]: starting version 182
Waiting for removable media...
5  4  3  2  1  0...
Mounted filesystems
/dev/mmcblk0p1 on /media/mmcblk0p1 type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
Available block devices
ls: /dev/sd*: No such file or directory
Cannot find rootfs.img file in /media/mmcblk0p1 , dropping to a shell
sh: can't access tty; job control turned off
fdisk -l shows the following:
Disk /dev/mmcblk0: 7742 MB,<PHONE_NUMBER> bytes
84 heads, 38 sectors/track, 4737 cylinders
Units = cylinders of 3192 * 512 = 1634304 bytes
Device Boot      Start         End      Blocks  Id System
/dev/mmcblk0p1               3        4738     7557120   b Win95 FAT32
Any ideas how can I boot into ConnectAnyThing?

Hi,
I have the same error and I have the files as you mentioned. However it is not up and running for Intel Galileo Gen1. I have used this MicroSD card before for Linux image for Arduino and I had no problem. Any idea what could be wrong?
It would be great if you can take a look at my question details here:
https://communities.intel.com/message/316574#316574
Bests,
Mona Jalal


Fixed: inspecting document.title deleted it as a side-effect (when cached)

Minimal reproducible example with linkedom 0.16.10:
import { parseHTML } from 'linkedom/cached';

const html = '<!DOCTYPE html><title>Test</title>';
const { document } = parseHTML(html);
console.log('Title:', document.title); // Title: Test
console.log('Title:', document.title); // Title:          <-- missing (title removed as a side-effect)

Thanks! It's up and running. If you had an issue please be sure that gets closed too 👋


Abstract catalog object

Consider an AbstractCatalog class, with common elements used in all catalogs.
Reasoning is because Catalog structures for different content types have different fields.

Commit:
https://github.com/cjcodeproj/medialibrary/commit/a459494faf9da1daf1d3d0ae123ff9b00ee3b5aa

Closing notes:
I left a generic Catalog() object class in place, meant to act as a sort of final object.
The unit tests work across the Catalog() object, since the AbstractCatalog is not meant to be used as an instance.


Is there any distribution(umd production version) file of @material/styles ?

What I want to do
I'm trying to exclude material-ui from my bundle file. But there seems no umd development/production version of @material/styles package.
What is the problem
There are some components like ThemeProvider, which is exported by @material-ui/styles, caused @material-ui/esm/styles is included again when bundling files with webpack.
If I exclude @materal-ui/styles in webpack's externals section, there will be a error printed in my console(can not find components, blablabla....).
I did some research about the error, it seems there is no export of the component I need(ThemeProvider as above mentioned).

We have no UMD version of @material-ui/styles. Did you try to create your own vendor bundle (with React, Material-UI etc.)?

Also, I hope you are not using the UMD version of @material-ui/core.


Test PR to trigger PR preview for testing

What
Test PR to trigger PR preview for testing
Why
I need a way to test PR previews for laboratory-v2
Issue addressed by this PR
https://github.com/stellar/ops/issues/2846

Preview is available here:http://laboratory-pr743.previews.kube001.services.stellar-ops.com/

Preview is available here:http://laboratory-pr743.previews.kube001.services.stellar-ops.com/

Preview is available here:http://laboratory-pr743.previews.kube001.services.stellar-ops.com/

Preview is available here:http://laboratory-pr743.previews.kube001.services.stellar-ops.com/


Dex/OIDC fails to configure

First, the manual says to configure "public-url". Not sure what it will be for the extended cluster.
I assumed this is the address of the ambassador (.xip.io).
Configured public-url='http://.xip.io:80' for both dex-auth and oidc-gatekeeper.
Once both dex and oidc charms finished the config, oidc complaints:
time="2020-01-26T11:03:23Z" level=error msg="OIDC provider setup failed, retrying in 10 seconds: Get https://<IP_ADDRESS>.xip.io/dex/.well-known/openid-configuration: x509: certificate is valid for ingress.local, not <IP_ADDRESS>.xip.io"
And obviously the ambassador doesn't allow to login, instead showing "OIDC Setup is not complete yet."

So how does one get to the dashboard?

@lwileczek-dmc You can declare the <IP_ADDRESS>.xip.io in your /etc/hosts point to valid public ip address and access. Now Im verify can I force to pass de HOST proxy header in Ingress entry for solve this.


Gas errors on the network

A number of subgraphs on the network have hit the default gas limit, so indexers must configure a larger one. We should look into these with the purpose of adjusting gas costs that may be overestimated. These subgraphs have been reported as going over the limit:
QmTiKBqwDjDtjAoCNgKLFjyg9UmwyFkVMFRVzBdnFmwYEi, QmayVPFDjZ4PP8rsKiNsZ3bZsqrQo4RTaeMm966wQsjP7R, QmWd8mE5nedM5smvzQhDYmsWEcgiAtdqccdZ2XCsvCdVEK.
The Eden Network (QmWd8mE5nedM5smvzQhDYmsWEcgiAtdqccdZ2XCsvCdVEK, source link case has more details. It fails with:
May 11 12:44:54.957 ERRO Subgraph failed with non-deterministic error: failed to process trigger: block #13807949 (0x0bf6…ac4c), transaction 0229c81e816101dbb7f5ecfb4ea3a0eb2c82083f10123e0a504a1dbd7063eaa1: Gas limit exceeded. Used:<PHONE_NUMBER>2787	wasm backtrace:	    0: 0x2235 - <unknown>!~lib/@graphprotocol/graph-ts/index/Value#toArray	    1: 0x2891 - <unknown>!src/network/stakeUnstake	    2: 0x271f - <unknown>!src/network/stakeUnstake~anonymous|5	    3: 0x292b - <unknown>!src/network/stake	    4: 0x29d2 - <unknown>!~lib/internal/memory/memcmp	, retry_delay_s: 1800, attempt: 651, sgd: 101, subgraph_id: QmWd8mE5nedM5smvzQhDYmsWEcgiAtdqccdZ2XCsvCdVEK, component: SubgraphInstanceManager
May 11 12:44:54.955 INFO Done processing trigger, gas_used: 0, data_source: EdenNetwork, handler: stake, total_ms: 62643, transaction: 0x0229…eaa1, address: 0x9e33…c453, signature: Stake(indexed address,uint256), block_hash: 0x0bf6b37adec469650eeac0d9dea4add97fcf9acbc37c3412accf40b96399ac4c, block_number: 13807949, sgd: 101, subgraph_id: QmWd8mE5nedM5smvzQhDYmsWEcgiAtdqccdZ2XCsvCdVEK, component: SubgraphInstanceManager

Probably due to iterating over a large collection, the network.stakers array might be as large as 4.5k entries.

thanks @leoyvens - we should investigate whether the gas costs are miscalibrated, but also consider if the subgraphs themselves could be optimised, or if more gas-efficient affordances are required for developers (i.e. there is no available optimisation based on the current graph-node feature set)

Still relevant.

Ran into this too

Does anyone know how to manually increase such limit?

@songhobby that's a different issue, on eth_call gas, the fix will be rolled out to hosted tomorrow.


Generic typing on Tchef

Pick a validation library and test if we can validate the payloads.

Merging just the generic/type inference/autocomplete on response feature.
Will branch out actual validation.


[DO NOT MERGE] Auto parallel memory and performance analysis.

PR types
Others
PR changes
Others
Description
Auto parallel memory and performance analysis for dynamic graph.

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


Subscriptions / Personal Plan

Description of the new feature / enhancement
download by subscription if the videos are in the my list
Scenario when this would be used?
videos that are in the my list are not displayed, which are all ok in purchased

See the new version 1.14

See the new version 1.14

you're the best


object detection('VOCDataset')

whether the code of object detection is only useful with COCO dataset，what about VOCDataset. when I use 'VOCDataset' , the error is as follows:

please give me some advice ,thank you very much!

We just simply add the UniFormer model in MMDetection, thus it's impossible for the incompatibility of other datasets.
For the bug you meet, you'd better learn to localize the real reason. As shown in your report, it is mainly because of the bug in apex, you can fix the bug as here.

As there is no more activity, I am closing the issue, don't hesitate to reopen it if necessary.


Change to collector causing issues with nodejs

I did some digging to figure out what exactly was causing the issue I was seeing and it appears to be related to PR #194.
I am pretty new to go so I really don't know why this causes an issue 😅 Also I only tested this with nodejs but it is possible it is causing trouble in other environment I just haven't tested those 🤷♂
Here are the steps I took to build everything and a sample of the Cloudwatch logs I am seeing

run make publish-layer in the collector folder to have a local build of the collector
run npm i in the nodejs folder
Run terraform init in the nodejs/integration-tests/aws-sdk/wrapper
Run terraform apply to deploy
Run a GET request on the endpoint that was exposed on API gateway.

Then in CloudWatch I am just seeing the following followed by a timeout from lambda and API gateway
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|   timestamp   |                                                                                message                                                                                |
|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|<PHONE_NUMBER>819 | 2021/12/30 19:16:52 [collector] Launching OpenTelemetry Lambda extension, version:  v0.1.0                                                                                |
|<PHONE_NUMBER>834 | 2021-12-30T19:16:52.834Z info service/collector.go:186 Applying configuration...                                                                                |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.834Z info builder/exporters_builder.go:254 Exporter was built. {"kind": "exporter", "name": "logging"}                                                                                |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.835Z info builder/pipelines_builder.go:222 Pipeline was built. {"name": "pipeline", "name": "metrics"}                                                                                |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.835Z info builder/pipelines_builder.go:222 Pipeline was built. {"name": "pipeline", "name": "traces"}                                                                                |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.835Z info builder/receivers_builder.go:224 Receiver was built. {"kind": "receiver", "name": "otlp", "datatype": "metrics"}                                                                        |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.835Z info builder/receivers_builder.go:224 Receiver was built. {"kind": "receiver", "name": "otlp", "datatype": "traces"}                                                                         |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.835Z info service/service.go:86 Starting extensions...                                                                                |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.835Z info service/service.go:91 Starting exporters...                                                                                |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.835Z info builder/exporters_builder.go:40 Exporter is starting... {"kind": "exporter", "name": "logging"}                                                                                |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.835Z info builder/exporters_builder.go:48 Exporter started. {"kind": "exporter", "name": "logging"}                                                                                |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.835Z info service/service.go:96 Starting processors...                                                                                |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.835Z info builder/pipelines_builder.go:54 Pipeline is starting... {"name": "pipeline", "name": "metrics"}                                                                                |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.835Z info builder/pipelines_builder.go:65 Pipeline is started. {"name": "pipeline", "name": "metrics"}                                                                                |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.835Z info builder/pipelines_builder.go:54 Pipeline is starting... {"name": "pipeline", "name": "traces"}                                                                                |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.835Z info builder/pipelines_builder.go:65 Pipeline is started. {"name": "pipeline", "name": "traces"}                                                                                |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.835Z info service/service.go:101 Starting receivers...                                                                                |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.835Z info builder/receivers_builder.go:68 Receiver is starting... {"kind": "receiver", "name": "otlp"}                                                                                |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.835Z info otlpreceiver/otlp.go:68 Starting GRPC server on endpoint <IP_ADDRESS>:4317 {"kind": "receiver", "name": "otlp"}                                                                              |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.835Z info otlpreceiver/otlp.go:86 Starting HTTP server on endpoint <IP_ADDRESS>:4318 {"kind": "receiver", "name": "otlp"}                                                                              |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.835Z info otlpreceiver/otlp.go:141 Setting up a second HTTP listener on legacy endpoint <IP_ADDRESS>:55681 {"kind": "receiver", "name": "otlp"}                                                        |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.835Z info otlpreceiver/otlp.go:86 Starting HTTP server on endpoint <IP_ADDRESS>:55681 {"kind": "receiver", "name": "otlp"}                                                                             |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.835Z info builder/receivers_builder.go:73 Receiver started. {"kind": "receiver", "name": "otlp"}                                                                                |
|<PHONE_NUMBER>835 | 2021-12-30T19:16:52.835Z info service/telemetry.go:92 Setting up own telemetry...                                                                                |
|<PHONE_NUMBER>836 | 2021-12-30T19:16:52.836Z info service/telemetry.go:116 Serving Prometheus metrics {"address": ":8888", "level": "basic", "service.instance.id": "27f930a5-d42a-4826-af98-8b11dc15fec2", "service.version": "latest"}  |
|<PHONE_NUMBER>836 | 2021-12-30T19:16:52.836Z info service/collector.go:235 Starting otelcol... {"Version": "v0.1.0", "NumCPU": 2}                                                                                |
|<PHONE_NUMBER>836 | 2021-12-30T19:16:52.836Z info service/collector.go:131 Everything is ready. Begin running and processing data.                                                                                |
|<PHONE_NUMBER>826 | START RequestId: 80ac2185-73a7-4743-8b6d-5b4edb2d1ee4 Version: $LATEST                                                                                |
|<PHONE_NUMBER>432 | 2021/12/30 19:17:03 [collector] Launching OpenTelemetry Lambda extension, version:  v0.1.0                                                                                |
|<PHONE_NUMBER>469 | 2021-12-30T19:17:03.469Z info service/collector.go:186 Applying configuration...                                                                                |
|<PHONE_NUMBER>469 | 2021-12-30T19:17:03.469Z info builder/exporters_builder.go:254 Exporter was built. {"kind": "exporter", "name": "logging"}                                                                                |
|<PHONE_NUMBER>469 | 2021-12-30T19:17:03.469Z info builder/pipelines_builder.go:222 Pipeline was built. {"name": "pipeline", "name": "traces"}                                                                                |
|<PHONE_NUMBER>469 | 2021-12-30T19:17:03.469Z info builder/pipelines_builder.go:222 Pipeline was built. {"name": "pipeline", "name": "metrics"}                                                                                |
|<PHONE_NUMBER>469 | 2021-12-30T19:17:03.469Z info builder/receivers_builder.go:224 Receiver was built. {"kind": "receiver", "name": "otlp", "datatype": "traces"}                                                                         |
|<PHONE_NUMBER>470 | 2021-12-30T19:17:03.469Z info builder/receivers_builder.go:224 Receiver was built. {"kind": "receiver", "name": "otlp", "datatype": "metrics"}                                                                        |
|<PHONE_NUMBER>470 | 2021-12-30T19:17:03.469Z info service/service.go:86 Starting extensions...                                                                                |
|<PHONE_NUMBER>470 | 2021-12-30T19:17:03.469Z info service/service.go:91 Starting exporters...                                                                                |
|<PHONE_NUMBER>470 | 2021-12-30T19:17:03.469Z info builder/exporters_builder.go:40 Exporter is starting... {"kind": "exporter", "name": "logging"}                                                                                |
|<PHONE_NUMBER>470 | 2021-12-30T19:17:03.470Z info builder/exporters_builder.go:48 Exporter started. {"kind": "exporter", "name": "logging"}                                                                                |
|<PHONE_NUMBER>470 | 2021-12-30T19:17:03.470Z info service/service.go:96 Starting processors...                                                                                |
|<PHONE_NUMBER>470 | 2021-12-30T19:17:03.470Z info builder/pipelines_builder.go:54 Pipeline is starting... {"name": "pipeline", "name": "traces"}                                                                                |
|<PHONE_NUMBER>470 | 2021-12-30T19:17:03.470Z info builder/pipelines_builder.go:65 Pipeline is started. {"name": "pipeline", "name": "traces"}                                                                                |
|<PHONE_NUMBER>470 | 2021-12-30T19:17:03.470Z info builder/pipelines_builder.go:54 Pipeline is starting... {"name": "pipeline", "name": "metrics"}                                                                                |
|<PHONE_NUMBER>470 | 2021-12-30T19:17:03.470Z info builder/pipelines_builder.go:65 Pipeline is started. {"name": "pipeline", "name": "metrics"}                                                                                |
|<PHONE_NUMBER>470 | 2021-12-30T19:17:03.470Z info service/service.go:101 Starting receivers...                                                                                |
|<PHONE_NUMBER>470 | 2021-12-30T19:17:03.470Z info builder/receivers_builder.go:68 Receiver is starting... {"kind": "receiver", "name": "otlp"}                                                                                |
|<PHONE_NUMBER>470 | 2021-12-30T19:17:03.470Z info otlpreceiver/otlp.go:68 Starting GRPC server on endpoint <IP_ADDRESS>:4317 {"kind": "receiver", "name": "otlp"}                                                                              |
|<PHONE_NUMBER>470 | 2021-12-30T19:17:03.470Z info otlpreceiver/otlp.go:86 Starting HTTP server on endpoint <IP_ADDRESS>:4318 {"kind": "receiver", "name": "otlp"}                                                                              |
|<PHONE_NUMBER>470 | 2021-12-30T19:17:03.470Z info otlpreceiver/otlp.go:141 Setting up a second HTTP listener on legacy endpoint <IP_ADDRESS>:55681 {"kind": "receiver", "name": "otlp"}                                                        |
|<PHONE_NUMBER>470 | 2021-12-30T19:17:03.470Z info otlpreceiver/otlp.go:86 Starting HTTP server on endpoint <IP_ADDRESS>:55681 {"kind": "receiver", "name": "otlp"}                                                                             |
|<PHONE_NUMBER>470 | 2021-12-30T19:17:03.470Z info builder/receivers_builder.go:73 Receiver started. {"kind": "receiver", "name": "otlp"}                                                                                |
|<PHONE_NUMBER>470 | 2021-12-30T19:17:03.470Z info service/telemetry.go:92 Setting up own telemetry...                                                                                |
|<PHONE_NUMBER>471 | 2021-12-30T19:17:03.471Z info service/telemetry.go:116 Serving Prometheus metrics {"address": ":8888", "level": "basic", "service.instance.id": "0c59d806-ac4d-4b29-88e7-55cfea4607df", "service.version": "latest"}  |
|<PHONE_NUMBER>471 | 2021-12-30T19:17:03.471Z info service/collector.go:235 Starting otelcol... {"Version": "v0.1.0", "NumCPU": 2}                                                                                |
|<PHONE_NUMBER>471 | 2021-12-30T19:17:03.471Z info service/collector.go:131 Everything is ready. Begin running and processing data.                                                                                |
|<PHONE_NUMBER>847 | EXTENSION Name: collector State: Started Events: []                                                                                |
|<PHONE_NUMBER>847 | END RequestId: 80ac2185-73a7-4743-8b6d-5b4edb2d1ee4                                                                                |
|<PHONE_NUMBER>847 | REPORT RequestId: 80ac2185-73a7-4743-8b6d-5b4edb2d1ee4 Duration: 20020.53 ms Billed Duration: 20000 ms Memory Size: 384 MB Max Memory Used: 31 MB                                                                     |
|<PHONE_NUMBER>847 | 2021-12-30T19:17:22.847Z 80ac2185-73a7-4743-8b6d-5b4edb2d1ee4 Task timed out after 20.02 seconds                                                                                |
|<PHONE_NUMBER>166 | 2021/12/30 19:17:23 [collector] Launching OpenTelemetry Lambda extension, version:  v0.1.0                                                                                |
|<PHONE_NUMBER>196 | 2021-12-30T19:17:23.196Z info service/collector.go:186 Applying configuration...                                                                                |
|<PHONE_NUMBER>196 | 2021-12-30T19:17:23.196Z info builder/exporters_builder.go:254 Exporter was built. {"kind": "exporter", "name": "logging"}                                                                                |
|<PHONE_NUMBER>196 | 2021-12-30T19:17:23.196Z info builder/pipelines_builder.go:222 Pipeline was built. {"name": "pipeline", "name": "traces"}                                                                                |
|<PHONE_NUMBER>196 | 2021-12-30T19:17:23.196Z info builder/pipelines_builder.go:222 Pipeline was built. {"name": "pipeline", "name": "metrics"}                                                                                |
|<PHONE_NUMBER>196 | 2021-12-30T19:17:23.196Z info builder/receivers_builder.go:224 Receiver was built. {"kind": "receiver", "name": "otlp", "datatype": "traces"}                                                                         |
|<PHONE_NUMBER>197 | 2021-12-30T19:17:23.196Z info builder/receivers_builder.go:224 Receiver was built. {"kind": "receiver", "name": "otlp", "datatype": "metrics"}                                                                        |
|<PHONE_NUMBER>197 | 2021-12-30T19:17:23.197Z info service/service.go:86 Starting extensions...                                                                                |
|<PHONE_NUMBER>197 | 2021-12-30T19:17:23.197Z info service/service.go:91 Starting exporters...                                                                                |
|<PHONE_NUMBER>197 | 2021-12-30T19:17:23.197Z info builder/exporters_builder.go:40 Exporter is starting... {"kind": "exporter", "name": "logging"}                                                                                |
|<PHONE_NUMBER>197 | 2021-12-30T19:17:23.197Z info builder/exporters_builder.go:48 Exporter started. {"kind": "exporter", "name": "logging"}                                                                                |
|<PHONE_NUMBER>197 | 2021-12-30T19:17:23.197Z info service/service.go:96 Starting processors...                                                                                |
|<PHONE_NUMBER>197 | 2021-12-30T19:17:23.197Z info builder/pipelines_builder.go:54 Pipeline is starting... {"name": "pipeline", "name": "traces"}                                                                                |
|<PHONE_NUMBER>197 | 2021-12-30T19:17:23.197Z info builder/pipelines_builder.go:65 Pipeline is started. {"name": "pipeline", "name": "traces"}                                                                                |
|<PHONE_NUMBER>197 | 2021-12-30T19:17:23.197Z info builder/pipelines_builder.go:54 Pipeline is starting... {"name": "pipeline", "name": "metrics"}                                                                                |
|<PHONE_NUMBER>197 | 2021-12-30T19:17:23.197Z info builder/pipelines_builder.go:65 Pipeline is started. {"name": "pipeline", "name": "metrics"}                                                                                |
|<PHONE_NUMBER>197 | 2021-12-30T19:17:23.197Z info service/service.go:101 Starting receivers...                                                                                |
|<PHONE_NUMBER>197 | 2021-12-30T19:17:23.197Z info builder/receivers_builder.go:68 Receiver is starting... {"kind": "receiver", "name": "otlp"}                                                                                |
|<PHONE_NUMBER>197 | 2021-12-30T19:17:23.197Z info otlpreceiver/otlp.go:68 Starting GRPC server on endpoint <IP_ADDRESS>:4317 {"kind": "receiver", "name": "otlp"}                                                                              |
|<PHONE_NUMBER>197 | 2021-12-30T19:17:23.197Z info otlpreceiver/otlp.go:86 Starting HTTP server on endpoint <IP_ADDRESS>:4318 {"kind": "receiver", "name": "otlp"}                                                                              |
|<PHONE_NUMBER>197 | 2021-12-30T19:17:23.197Z info otlpreceiver/otlp.go:141 Setting up a second HTTP listener on legacy endpoint <IP_ADDRESS>:55681 {"kind": "receiver", "name": "otlp"}                                                        |
|<PHONE_NUMBER>197 | 2021-12-30T19:17:23.197Z info otlpreceiver/otlp.go:86 Starting HTTP server on endpoint <IP_ADDRESS>:55681 {"kind": "receiver", "name": "otlp"}                                                                             |
|<PHONE_NUMBER>197 | 2021-12-30T19:17:23.197Z info builder/receivers_builder.go:73 Receiver started. {"kind": "receiver", "name": "otlp"}                                                                                |
|<PHONE_NUMBER>197 | 2021-12-30T19:17:23.197Z info service/telemetry.go:92 Setting up own telemetry...                                                                                |
|<PHONE_NUMBER>198 | 2021-12-30T19:17:23.198Z info service/telemetry.go:116 Serving Prometheus metrics {"address": ":8888", "level": "basic", "service.instance.id": "8dbe0f4d-2c62-406f-b5ad-cf9178feebe3", "service.version": "latest"}  |
|<PHONE_NUMBER>198 | 2021-12-30T19:17:23.198Z info service/collector.go:235 Starting otelcol... {"Version": "v0.1.0", "NumCPU": 2}                                                                                |
|<PHONE_NUMBER>198 | 2021-12-30T19:17:23.198Z info service/collector.go:131 Everything is ready. Begin running and processing data.                                                                                |
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Originally posted by @Danwakeem in https://github.com/open-telemetry/opentelemetry-lambda/discussions/199

Yeah I'm experiencing this issue as well.
It looks like my handler isn't called - all my handler currently does is log the event payload out.
Remove the layer - everything works fine and the event is logged. Add it back - lambda times out with no output produced.

Hey thanks for posting this issue! I wished I had seen this before trying to debug our issue this weekend 🥲
I should have a a fix for this in https://github.com/open-telemetry/opentelemetry-lambda/pull/207, please let me know if you think there is still an issue! 😄


Update to use feature flag terminology?

Update to use feature flag terminology used in v3 of Microsoft.FeatureManagement?

This was based on a preview version of v3 which did not go ahead. Closing this issue.


Fail on initialization error

An error message is logged when some of the user apps contain a telegrambot.py module that cannot be imported correctly (see #13).
If STRICT_INIT in settings.DJANGO_TELEGRAMBOT is set to True (recommended), the app will terminate if some of the telegrambot.py files cannot be imported.

Codecov Report

Merging #15 into master will increase coverage by 10.97%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           master      #15       +/-   ##
===========================================
+ Coverage   31.39%   42.37%   +10.97%
===========================================
  Files           8        8
  Lines         293      295        +2
===========================================
+ Hits           92      125       +33
+ Misses        201      170       -31

Impacted Files
Coverage Δ

django_telegrambot/apps.py
53.51% <100%> (+17.44%)
: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 5e8a1b7...e6109c5. Read the comment docs.


Wrong song being found

System OS
Windows
Python Version
3.9 (CPython)
Install Source
pip / PyPi
Install version / commit hash
4.0.5
Expected Behavior vs Actual Behavior
Downloading Matt Watson - No Nut November outputs a bass guitar cover of the song instead of the actual song
Expected
spotdl download https://open.spotify.com/track/1ddxqZGFM00vtzhAflKkTW
Downloaded "Matt Watson - No Nut November": https://www.youtube.com/watch?v=kVr31ryrXQM

Info
Results

Video Title
No Nut November (feat. Freddie Dredd, Kill Bill: The Rapper & Carson Tucker)

Channel Name
Matt Watson - Topic

YT Link
https://www.youtube.com/watch?v=kVr31ryrXQM

Actual
spotdl download https://open.spotify.com/track/1ddxqZGFM00vtzhAflKkTW
Downloaded "Matt Watson - No Nut November": https://www.youtube.com/watch?v=LGaKOIpYU40

Info
Results

Video Title
Matt Watson, Freddie Dredd, Kill Bill: The Rapper, Carson Tucker - NO NUT NOVEMBER [Bass Cover]

Channel Name
Nick Maxwell

YT Link
https://www.youtube.com/watch?v=LGaKOIpYU40

I'm purely assuming this, but is because the title matches closer to the search? It would be weird considering that the "correct result" is the first search result on yt-music... idk
Temp fix
spotdl download "https://youtu.be/kVr31ryrXQM|https://open.spotify.com/track/1ddxqZGFM00vtzhAflKkTW"
Steps to reproduce
spotdl download https://open.spotify.com/track/1ddxqZGFM00vtzhAflKkTW
Traceback
FOLDER_PATH>spotdl download https://open.spotify.com/track/1ddxqZGFM00vtzhAflKkTW
Downloaded "Matt Watson - No Nut November": https://www.youtube.com/watch?v=LGaKOIpYU40

Other details
I was considering posting this in the discord but decided against it cause there is no real place to post this other than help. Is it cool if I keep adding problematic songs to this git issue, or would it be easier/better for a issue per song???

Spotdl not giving up
Downloading Metaroom - M.I.L.F - Metaroom Remix, depending on version and algorithm of search, gives random results instead of giving up or just choosing one of the many community uploads instead cause the original does not exist anymore.
spotdl download https://open.spotify.com/track/0TA7wZdw4qgksyzu2Oav5d
Spotdl 3.9 found resulted in:

Info
Results

Video Title
Lexapro Delirium (metaroom remix) - Metaroom

Channel Name
Metaroom l

YT Link
REMOVED (I remember this song)

Spotdl 4.0.5 found resulted in:

Info
Results

Video Title
CARLOT32 (METAROOM REMIX)

Channel Name
Metaroom l

YT Link
https://music.youtube.com/watch?v=3xJJAv_kaDQ

Assumed it going for Metaroom Remix as it seems to be pulling that more than anything else
Temp fix (Would use the original https://www.youtube.com/watch?v=d3dOhFRgku0 but it is private, hence the issue)
spotdl download "https://youtu.be/K-QnVmJYmQg|https://open.spotify.com/track/0TA7wZdw4qgksyzu2Oav5d"
Also weird request but could you possibly add a --overwrite command to just overwrite old music. I have a tone of stuff from v3.9 that has low res art and I could somehow re-scrape and re-tag all of them manually but just re-downloading the ones that I can and overwriting them would be awesome 🙏🙏.

@xnetcat
Sorry if I caused confusion with the whole metaroom song issue.
I was more trying to get across that the songs data can be found but the song itself is almost fully removed from yt/yt-music. I wasn't expecting a fix to find these kinds of obscure missing songs. More just to bring to light that spotdl doesn't give up (as it should considering it won't find the correct song) and throw a "song not found" error, instead it just finds the next best metaroom song (CARLOT32 METAROOM REMIX) and pastes the data for M.I.L.F on whatever it can get its hands on.
I'm not going to pretend like I know what I'm talking about, nor tell you what to do cause you are way more knowledgeable in this then I am 😅. I was wondering tho, why searching for music with this kind of issue (Data on spotify, no song on yt/yt-music) spotdl throws the "song not found" but not with this specific song? Is it a confidence thing?
Thanks, I completely overlooked --overwrite {force,skip,metadata}. Just checked dev branch and the same behavior as the described in the first paragraph (the same as the original issue) is happening. It's not a huge issue as it seems kinda like a freak case, tho I'll see if I can find any other songs that do this 👍
One more thing, you never answered my other details 😂. Is discord easier for these song accuracy issues or are you cool with these github issues?

@xnetcat
Sorry if I caused confusion with the whole metaroom song issue.
I was more trying to get across that the songs data can be found but the song itself is almost fully removed from yt/yt-music. I wasn't expecting a fix to find these kinds of obscure missing songs. More just to bring to light that spotdl doesn't give up (as it should considering it won't find the correct song) and throw a "song not found" error, instead it just finds the next best metaroom song (CARLOT32 METAROOM REMIX) and pastes the data for M.I.L.F on whatever it can get its hands on.
I'm not going to pretend like I know what I'm talking about, nor tell you what to do cause you are way more knowledgeable in this then I am 😅. I was wondering tho, why searching for music with this kind of issue (Data on spotify, no song on yt/yt-music) spotdl throws the "song not found" but not with this specific song? Is it a confidence thing?
Thanks, I completely overlooked --overwrite {force,skip,metadata}. Just checked dev branch and the same behavior as the described in the first paragraph (the same as the original issue) is happening. It's not a huge issue as it seems kinda like a freak case, tho I'll see if I can find any other songs that do this 👍
One more thing, you never answered my other details 😂. Is discord easier for these song accuracy issues or are you cool with these github issues?

yep you're right, it's a confidence thing, half of the title is correct that's why it gets marked as a correct result. It's really extreme edge case because the author's name is correct.
Let's keep using github for song issues, there's too much messages coming in on discord for me to keep track of specific messages, but you for sure can paste new messages on discord and mention me so that I reply faster. Also sorry for such late response I was focusing on other issues first. Which details from your message did I omit?

yep you're right, it's a confidence thing, half of the title is correct that's why it gets marked as a correct result. It's really extreme edge case because the author's name is correct.

Huh, that super interesting in how that works.

Let's keep using github for song issues, there's too much messages coming in on discord for me to keep track of specific messages, but you for sure can paste new messages on discord and mention me so that I reply faster.

Yeah fs, sounds good. Thanks for getting back to me so quickly 👌

Also sorry for such late response I was focusing on other issues first. Which details from your message did I omit?

Nothing was missed, I was more just clarifying my rather short song entries. The other details was in ref to the layout of the first comment under the Other details header, sorry. Should have been more specific. In saying that would a single issue with a comment for each song be easier or is having an issue per song easier?


Permissions not applying immediately - LP v4.2.12

So, I noticed when editing permissions on my server, they are not applying immediately. I have to disconnect and reconnect my Member (default) account for the permission to take effect.
Example:
Default inherits mem_essentials. mem_essentials has essentials.help set to true. Member has access to help. Owner runs /lp group mem_essentials permission unset essentials.help. Member still has access to essentials /help command. Both players are on the same server. Bungeecord is setup properly. Messaging goes through with no errors. Member loses access to essentials /help when they reconnect.
Also, both clients are running on the same computer... not sure is this will be an issue but worth mentioning.

Same problem here on Spigot 1.12.2. You cannot sync the permissions with /lp sync.
You need to reload/restart the whole server to apply permissions.

Thanks for reporting, should be fixed in the latest version


HashSet and ListSet

In a process of getting something usable by users as quickly as possible, I’m starting by replacing triple question marks by actual implementations.
This PR adds immutable HashSet and ListSet. I mostly copy-pasted the current implementation from 2.12.

Another performance regression revealed by the benchmark:

(the blue line shows Scala’s current HashSet)
Actually several operations are 1.5 to 2 times slower in our new HashSet.

I haven't been able to eyeball where the performance regressions come from.  First step is to pick the cleanest of the benchmarks and/or make them cleaner, so we believe that the effect is real.  foreach seems like a good choice because it's pretty simple in the old implementation.  Change the benchmark to be decent--consume every element with Blackhole.consume, for instance. Maybe the effect will go away.
Next, assuming not, we need to benchmark parts of the implementation to see where the difference comes from.  One suspect: it's TrieIterator (but I don't know why, yet).  In the old implementation, foreach was overridden for HashTrieSet; if you do the equivalent operation on the iterator (a simple sum, for instance), you get a ~15% performance penalty.  What if it's overridden here?  If it shows a big difference, it may be that TrieIterator is having trouble keeping up.  If it doesn't, that suggests that more of the difference is at the leaves.  I think within a few rounds we should have an answer.
(Needless to say, a 2x performance decrease is not acceptable when we already get dinged by not keeping up with java.util.)

Note that Scala releases are built with -opt:l:classpath, it seems this repo is not

Some news: I pushed some more commits and now we have about the same performance as 2.12 collections. The main change is that now splitAt (which is used by TrieIterator) is now implemented in terms of take and drop, by default, and benefits from optimizations brought to these methods.
Here is the chart for concat:

Remember that the vertical axis is logarithmic… In the worst case (282 elements) we are still ~1.6x slower than 2.12.
And here is the chart for cons:

Looks much better!  Nice work!

What's the margin of error for these benchmarks? Can we add this to the plots? The performance going back and forth in the higher element count measurements doesn't make much sense.

The margin of error is actually drawn. But in the images I posted the error bar was too small so we don’t even see it. The uncons benchmark has a higher error bar, for instance:

I think we should merge the PR as it is, so that we can move forward to implementing other collection types. We can still improve these collections later.


Do not use address if it has an existing label

You can currently see the list of all addresses from the addresses tab. You can go to the next unused address and "reserve" it for a specific purpose by adding a label to an address that still hasn't received any funds.
"Reserving" addresses is typically done to pre-share addresses with third parties. I want John to pay me, I will send him this addess. I want Alice to pay me, I will send Alice this other address. I type "payment from John" and "payment form Alices" in their respective Label fields. However, I don't control when they are going to make the payment. They may wait until fees get a bit lower, or until they themselves get paid for another job or whatever.
However, these addresses are just "unused" addresses, and Sparrow doesn't treat unlabeled unused addresses any different than labeled unused addresses.
Say, in the example above, after I share those addresses with John and Alice, I want to consolidate two coins. I go to the coins, I Send Selected, I select Pay to: this same wallet (Consolidation), and the suggested address is the next unused address, labeled or not. This means I will consolidate to an address I decided to label while it was empty, and when John or Alice pay me, I will be incurring in address reuse, because I shared them the address before I did the consolidation
The suggestion here is that Sparrow understands that unused labeled addresses are different from unused unlabeled addresses. If it is labeled, the user probably already shared it, or has a usecase in mind, and it is therefore NOT safe to use by Sparrow. EXCLUDE this address form the list of usable addresses for change, consolidation, or receive form other wallets.

I thought about that too... But the extra user friction added to a checkbox makes it almost painful. Besides, I couldn't think of a single example where you would want to add some text in the Label of an unused address but not reserve it, the fact that you add text means you have some use in mind for that address after all, no point on adding text otherwise.
Can you think of an example where you would want to add a label to an unused address, but you would be ok with the app using it for a consolidation and overwriting your previous label?

I was thinking more in the addresses view, but I guess in the receive makes sense too. If I add a label in the receive screen I also have a plan for it, so for all purposes treat it as "consumed".
I don't really know how the "Get Next Address" works, but you got the gist of it, if I add a label to an empty address Sparrow should not suggest it as a valid receive address, and should treat it as consumed and non-usable in the future. I will make sure to use it myself outside of sparrow (that is why I added a label while it was empty after all).
We can go a step further and differentiate labeled empty addresses from actually used addresses. Addresses used at least once should never be used again in the future, period. Labeled empty addresses should never be used, as long as they remain labeled and unused. If a user removes a label from an empty labeled address, I would interpret that whatever goal they had in mind for that address, they no longer do. So the address can be used once again by Sparrow. Again, this might be too convoluted, and if it's easier to go with "just consume the address forever" it's fine too. It's just an evolution of the proposal to try and improve the automation to user needs

Yes I see your point entirely.

If a user removes a label from an empty labeled address, I would interpret that whatever goal they had in mind for that address, they no longer do. So the address can be used once again by Sparrow.

Maybe not, since this address might now be more or less known/public to outsiders so it's good practice to still treat it as non usable in the future.
A remaining question mark for me is how this feature will be handled if you manage the same wallet on different instances e.g. on Sparrow GUI and Sparrow server as it's solely based on labels and these are instance specific. But I guess that's also rather a niche edge case.

This is an interesting idea - I'm considering the implementation.

A remaining question mark for me is how this feature will be handled if you manage the same wallet on different instances

This is one case where an integration into labelbase.space would be useful.


Dev to Main Sync

Date: 04 Dec 2024

Developer Name: @VaibhavSingh8 @vikhyat187 @vinit717

Issue Ticket Number

Closes #2280
https://github.com/Real-Dev-Squad/website-backend/issues/2246

PR's to Sync

https://github.com/Real-Dev-Squad/website-backend/pull/2271
#2281
#2226
#2248

Documentation Updated?

[ ] Yes
[x] No

Under Feature Flag

[ ] Yes
[x] No

Database Changes

[ ] Yes
[x] No

Breaking Changes

[ ] Yes
[x] No

Development Tested?

[x] Yes
[ ] No

Screenshots

Screenshot 1

Proof for #2226 and #2248

Proof for #2280
https://github.com/user-attachments/assets/72ba9174-c80c-473d-8604-d58e09203493

Proof for #2257
https://github.com/user-attachments/assets/f858503b-594b-4e49-bf66-17a0023a6428

Proof for https://github.com/Real-Dev-Squad/website-backend/pull/2267 and https://github.com/Real-Dev-Squad/website-backend/pull/2268
https://github.com/Real-Dev-Squad/website-backend/pull/2267:

https://github.com/Real-Dev-Squad/website-backend/pull/2268:

Staging Evidence #2289


Update items.js

Added speed-lowering items for use in VGC Trick Room. Power Anklet, Power Band, Power Belt, Power Bracer, Power Lens, and Power Weight are all clone items of Macho Brace, but have competitive use on Trick Room teams in metagames with Item Clause, like VGC.

Thanks!


optimize time wasted in passing argument and fetching return

While discussing #96 I was able to identify a bottleneck
there was needlessly large time wasted in passing the arguments and retrieving the return
basically I made a simple 32-bit hash function cdb_djp_hash.c
in pure python the time is proportional to string length
in wasm it was almost constant time ~40ms regardless of string length 13 bytes to 1300 bytes (100x)
which means that most of those 40ms are in passing the arguments not in the actual loop (if it was the loop it would be proportional to string length or a large fraction of that).
This was confirmed using
pr=Profile()
pr.enable()
for i in range(10000):
        cdb_djp_hash_wasm(large_a)
pr.disable()
#pr.print_stats()
#pr.print_stats('cumulative')
pr.print_stats('calls')

the first note that the actual WASM call is fast (169ms out of 800ms)
which means that we might able to squeeze ~650ms of 800ms making it 4x faster
and I was able to identify bottleneck

things that take too much cumulative time
things that are called more than 10k (number of iterations)

examples of such things

too many calls to isinstance which is 170k (in a 10k iteration benchmark), that is 17 times per call
converting the argument _value.py:129(_convert) too ~200ms out of 800ms
we got dynamically sized lists operations like {method 'append' of 'list' objects}

Are we sure that passing arguments / converting can be made faster?
Yes
I can confirm _value.py:129(_convert)  that is too slow
I've moved the conversion outside the loop and confirmed it was the bottleneck
    i32_start = Val.i32(start)
    i32_size = Val.i32(size)
    for i in range(10000):
        np_mem[start:stop]=input
        hash_wasm = ctypes.c_uint32(_cdb_djp_hash_wasm(i32_start, i32_size)).value

also I can confirm that this time is just waste because passing parameter should do the following

convert little endian (which should not take time see below)
set memory just after the stack pointer (which is now fast using #135 #81 #134 )
move the stack pointer (which should not take time)

to proof that we can convert in almost no time
in_struct=Struct('<LL')
in_pack=in_struct.pack
for i in range(10000):
    b=pack(start, size)

in _value._convert
we see a lot of isinstance() and _func.call do a lot of work on each call despite the fact that the signature of the function does not change at runtime
I believe in the constructor of  class Func we need to set a property
in_fmt = ''.join([i.struct_code for i in ty])
self._in_struct=Struct('<'+in_fmt) # `<` because WASM is little endian
self._in_pack=self._in_struct.pack
self._out_struct=Struct('<'+out_fmt)
self._out_unpack=self._in_struct.unpack

where Val.struct_code is b, B, l, L, q, Q,  f, d  for i8, u8, i32, u32, i64, u64, f32, f64 respectively
and this should be done once on Func constructor not on every code
then when we want to encode the arguments
b=self._in_pack(...args)

I was able to make it 4x faster
running 10k  iteration of this hash function typically took ~350ms and now ~80ms
old:  0.3466089940011443
new:  0.0788318810009514

here is the code
def cdb_djp_hash_wasm(input: bytearray):
    size = len(input)
    start = hb
    stop = start + size
    np_mem[start:stop]=input
    params = (start, size)
    raw=(wasmtime_val_raw_t*len(params))()
    for row_i, param in zip(raw, params): row_i.i32=param
    raw_ptr_casted = ctypes.cast(raw, ctypes.POINTER(wasmtime_val_raw_t))
    with enter_wasm(store) as trap:
            error = ffi.wasmtime_func_call_unchecked(
                store._context,
                ctypes.byref(_cdb_djp_hash_wasm_in._func),
                raw_ptr_casted,
                trap)
            if error:
                raise WasmtimeError._from_ptr(error)
    return ctypes.c_uint32(raw[0].i32).value

and there is still more room from improvement

now it's ~66ms instead of ~80ms (compared to old 350ms)
by doing things once outside of the loop (the function won't change it's prototype/signature inside the loop)
def func_init(func, store):
    ty = func.type(store)
    ty_params = ty.params
    ty_results = ty.results
    params_str = (str(i) for i in ty_params)
    params_n = len(ty_params)
    results_n = len(ty_results)
    n = max(params_n, results_n)
    raw_type = wasmtime_val_raw_t*n
    func.raw_type = raw_type
    def _create_raw(params):
        raw = raw_type()
        for i, param_str in enumerate(params_str):
            setattr(raw[i], param_str, params[i])
        return raw
    func._create_raw = _create_raw

func_init(_cdb_djp_hash_wasm_in, store)
#....
    raw = _cdb_djp_hash_wasm_in._create_raw(params)
    raw_ptr_casted = ctypes.cast(raw, ctypes.POINTER(wasmtime_val_raw_t))

using struct.Struct gave ~80ms that is no extra benefit
each wasmtime_val_raw_t is 16 bytes (that is each one is 4xi32)
since our function takes two i32 we need a struct of <LLLLLLLL
# outside the loop
st=Struct('<LLLLLLLL')
raw_ptr_type = ctypes.c_uint8*st.size
st_ret=Struct('<L')
# inside the loop
    raw = bytearray(st.pack(start,0,0,0, size, 0,0,0))
    raw_ptr = raw_ptr_type.from_buffer(raw)
    raw_ptr_casted = ctypes.cast(raw_ptr, ctypes.POINTER(wasmtime_val_raw_t))

I'll continue using the previous func_init with wasmtime_val_raw_t

when profiler is enabled old method took ~700ms
and new method takes ~110ms
of which the actual wasm took less than 20ms (that is _bindings.py:2485(wasmtime_func_call_unchecked) or _bindings.py:2479(wasmtime_func_call) )
the profile of new method is very clean and does not seem to be possible to optimize it further
here are the report
old:  0.3560021289958968
new:  0.07202652499836404
         180001 function calls in 0.112 seconds

   Ordered by: standard name

   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
    10000    0.011    0.000    0.011    0.000 __init__.py:509(cast)
    10000    0.016    0.000    0.016    0.000 _bindings.py:2485(wasmtime_func_call_unchecked)
    20000    0.007    0.000    0.009    0.000 _func.py:256(enter_wasm)
    10000    0.004    0.000    0.004    0.000 cdb_djp_hash.py:72(_create_raw)
    10000    0.039    0.000    0.112    0.000 cdb_djp_hash.py:85(cdb_djp_hash_wasm)
    10000    0.008    0.000    0.010    0.000 contextlib.py:102(__init__)
    10000    0.004    0.000    0.014    0.000 contextlib.py:130(__enter__)
    10000    0.007    0.000    0.011    0.000 contextlib.py:139(__exit__)
    10000    0.004    0.000    0.013    0.000 contextlib.py:279(helper)
    20000    0.002    0.000    0.002    0.000 {built-in method _ctypes.POINTER}
    20000    0.003    0.000    0.003    0.000 {built-in method _ctypes.byref}
    10000    0.002    0.000    0.002    0.000 {built-in method builtins.getattr}
    10000    0.001    0.000    0.001    0.000 {built-in method builtins.len}
    20000    0.005    0.000    0.014    0.000 {built-in method builtins.next}
        1    0.000    0.000    0.000    0.000 {method 'disable' of '_lsprof.Profiler' objects}

         180001 function calls in 0.112 seconds

   Ordered by: cumulative time

   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
    10000    0.039    0.000    0.112    0.000 cdb_djp_hash.py:85(cdb_djp_hash_wasm)
    10000    0.016    0.000    0.016    0.000 _bindings.py:2485(wasmtime_func_call_unchecked)
    20000    0.005    0.000    0.014    0.000 {built-in method builtins.next}
    10000    0.004    0.000    0.014    0.000 contextlib.py:130(__enter__)
    10000    0.004    0.000    0.013    0.000 contextlib.py:279(helper)
    10000    0.011    0.000    0.011    0.000 __init__.py:509(cast)
    10000    0.007    0.000    0.011    0.000 contextlib.py:139(__exit__)
    10000    0.008    0.000    0.010    0.000 contextlib.py:102(__init__)
    20000    0.007    0.000    0.009    0.000 _func.py:256(enter_wasm)
    10000    0.004    0.000    0.004    0.000 cdb_djp_hash.py:72(_create_raw)
    20000    0.003    0.000    0.003    0.000 {built-in method _ctypes.byref}
    20000    0.002    0.000    0.002    0.000 {built-in method _ctypes.POINTER}
    10000    0.002    0.000    0.002    0.000 {built-in method builtins.getattr}
    10000    0.001    0.000    0.001    0.000 {built-in method builtins.len}
        1    0.000    0.000    0.000    0.000 {method 'disable' of '_lsprof.Profiler' objects}

         180001 function calls in 0.112 seconds

   Ordered by: call count

   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
    20000    0.007    0.000    0.009    0.000 _func.py:256(enter_wasm)
    20000    0.005    0.000    0.014    0.000 {built-in method builtins.next}
    20000    0.002    0.000    0.002    0.000 {built-in method _ctypes.POINTER}
    20000    0.003    0.000    0.003    0.000 {built-in method _ctypes.byref}
    10000    0.016    0.000    0.016    0.000 _bindings.py:2485(wasmtime_func_call_unchecked)
    10000    0.011    0.000    0.011    0.000 __init__.py:509(cast)
    10000    0.008    0.000    0.010    0.000 contextlib.py:102(__init__)
    10000    0.004    0.000    0.014    0.000 contextlib.py:130(__enter__)
    10000    0.007    0.000    0.011    0.000 contextlib.py:139(__exit__)
    10000    0.004    0.000    0.013    0.000 contextlib.py:279(helper)
    10000    0.039    0.000    0.112    0.000 cdb_djp_hash.py:85(cdb_djp_hash_wasm)
    10000    0.004    0.000    0.004    0.000 cdb_djp_hash.py:72(_create_raw)
    10000    0.002    0.000    0.002    0.000 {built-in method builtins.getattr}
    10000    0.001    0.000    0.001    0.000 {built-in method builtins.len}
        1    0.000    0.000    0.000    0.000 {method 'disable' of '_lsprof.Profiler' objects}

I just wonder why enter_wasm was called twice per iteration

this is a great enhancement from 43 ms to 6 ms in @alexprengere question in #96
yes the pure python implementation beats that at 1ms
although this is a huge improvement we have long way to beat pure python (not to mention C)
but I believe according to "Profile" this is as fast as python binding can go, any further optimization should be in the wasmtime itself not in the binding
0.0002523580042179674 # math_gcd
0.0014094869984546676 # python_gcd
0.043804362998344004  #  wasm_gcd
0.005873051006346941  # wasm_gcd_alt <-------- my change


Making tide::server private has broken testing

It seems to me that making tide::server private broke the example of testing as shown in realworld-tide repository. I can't call into_http_service() anymore. I'm very fresh to Rust and I probably am missing something.
I come from the C# background and it seems to me that being testable is an essential feature of a web-framework. Could you give me an idea of how to test tide? I haven't found it in the examples folder in this repo.
It would seem ideal if all the middle-ware\routing was testable in a synchronous manner without engaging any I\O or OS network stack. Is such a thing possible\planned with tide?

@marhoily tide::Server implements the HttpService trait directly in<EMAIL_ADDRESS>So there's no need to call into_http_service anymore since tide::Server already provides all it needs! In the next version (out today, if I can manage haha) we get rid of the trait entirely and expose Server::respond directly which replaces the use of the mock server. Example of the new API in use:
https://github.com/http-rs/tide/blob/9a143b3098c93ecc9f4ecd5d69d57a8a3244ecc6/tests/nested.rs#L74-L78
(commit that introduced it, replacing the old API)
Hope this helps!

Compiler still complains that the method Request::new is private. Am I missing something?

Found it. I should have reference http-types 2.0.0 crate explicitly. God Rust messes up with my assumptions of possible!


Terminal: text wraps over multiple lines (insiders regression)

VSCode Version: Code - Insiders 1.18.0-insider (4b01451cea60f32412098735709fddcac567b33d, 2017-10-19T08:29:07.096Z)
OS Version: Windows_NT x64 10.0.17017
Extensions:

Extension
Author (truncated)
Version

vscode-eslint
dba
1.3.2

gitlens
eam
5.6.5

tslint
eg2
1.0.11

vscode-great-icons
emm
2.1.16

prettier-vscode
esb
0.24.0

docthis
joe
0.5.0

debugger-for-chrome
msj
3.4.0

material-icon-theme
PKi
2.2.2

java
red
0.12.0

ActiveFileInStatusBar
Ros
1.0.3

vscode-hexdump
sle
1.4.0

quokka-vscode
Wal
1.0.72

(4 theme extensions excluded)

Steps to Reproduce:

Open the integrated terminal

What happens?
Windows version incorrectly spans over three lines

This didn't happen a few days ago and started behaving like this when I updated today morning.

I saw this today and suspect it's related to https://github.com/Microsoft/vscode/issues/35798


Survey section changes

Removal of ‘Description’ column
Add ‘Status’ column and to include options: ‘Overdue’, ‘In Progress’, ‘Complete’
Reformat dates shown in ‘Issued’, ‘Submitted By’ and ‘Approved By’ columns to ‘DD/MM/YYYY’
Inclusion of issued but incomplete survey (does not include the name of the person the survey is in progress with)

This can be closed


Cargo fails in Linux chroot without /proc

...
running: /tmp/rust-1.19-1.19.0-0/build/x86_64-unknown-linux-gnu/stage0/bin/cargo build \
    --manifest-path /tmp/rust-1.19-1.19.0-0/src/bootstrap/Cargo.toml --verbose
error: couldn't get the path to cargo executable

This is due to this code:
    pub fn cargo_exe(&self) -> CargoResult<&Path> {
        self.cargo_exe.get_or_try_init(||
            env::current_exe().and_then(|path| path.canonicalize())
            .chain_err(|| "couldn't get the path to cargo executable")
        ).map(AsRef::as_ref)
    }

Which ultimately calls this code:
#[cfg(any(target_os = "linux", target_os = "android", target_os = "emscripten"))]
pub fn current_exe() -> io::Result<PathBuf> {
    let selfexe = PathBuf::from("/proc/self/exe");
    if selfexe.exists() {
        ::fs::read_link(selfexe)
    } else {
        Err(io::Error::new(io::ErrorKind::Other, "no /proc/self/exe available. Is /proc mounted?"))
    }
}

Is the project open to modifying this logic to allow the full path to the executable to be specified via config or environment variable if /proc intentionally does not exist?
Something along the lines of CARGO_EXE or [build] cargo = "/path/to/cargo"...

Hm I sort of forget at this point what we're even using that for. Maybe we can just remove the dependence on calling current_exe?

@alexcrichton found it! https://github.com/rust-lang/cargo/issues/3778#issuecomment-283448233
Maybe we could use a method other than env::current_exe for this case? Or just let the user specify CARGO and check if that's present, and if so, use it instead of calling current_exe?

I need to read more context first. We're only setting this for external subcommands so we don't use it ourselves per se, but yeah; we could just check if it's set already and not do anything if so, letting the environment propagate.

Example of the latter at #4634.


Remove scroll jump when applying filters

Currently when you apply a filter, it immediately it scrolls up to the top of the filter, making it disorienting for users to use and breaking their concentration.
https://github.com/user-attachments/assets/2a9d9fe1-c22a-4ba7-b748-1d869c40ac2d
When a user clicks on a filter it should not scroll at all, but stay exactly where it was before, so users can have a smooth experience.

From my initial investigation, this occurs because the filters are being mapped with a unique key, causing React to re-render each time a filter option is selected (and its state is updated). As a result, the scroll position resets to the top of the element after every re-render.
I can look more into this and give it a try. @nlebovits

Thank you! I'll assign you now.
Btw, we'll have high fidelity mocks for the contact page by this weekend. Haven't forgotten that.


ask ors link should go to maps client category

The link from the info dropdown which goes to the ask forum should point to
https://ask.openrouteservice.org/c/maps/20
So people coming from the maps client will post in the maps client section

Fixed via 97f1be1cee9365cb327aa3de4509ad0022b1712c

The link is now fixed on the about page.
The link in the info dropdown still goes to the main ask page 🔗

You are right, the drop-down had not been updated. It was fixed via e948e4a8fe421f58adc50667ec1935033ef6c914


builder feature: union

UNION feature & tests

I find this PR is not been merged yet. Is there anything I need to do for this PR?

I'm strange why the CI is always waiting. I will run test locally.

BTW, do you need UNION feature in xorm?

Maybe someone need but PRs are always welcome! :)


Duplicated displaying of group PMs

After clicking into some group PMs, I'm getting them displayed twice in the list of conversations. Example:

That's one conversation, the link is identical, but it gets rendered twice for some reason.

Interesting!  Definitely worth investigating.

I suspect this was fixed by https://github.com/zulip/zulip/pull/13595.  @showell FYI.


As a User, I Want to Create a Central Games Table from Sports Data API

SportsDataAPI gem installed
Games table created
Rake task built to import Regular Season schedule, by year
Import is idempotent

@wonderwoman13, thank you! 🎉

You are very welcome! 💃


My account is no longer showing up

My account justinvos is no longer showing up on the commits.top list even though I have enough followers and commits to be in the teens of the New Zealand list.

https://github.com/lauripiispanen/most-active-github-users-counter/issues/40

There was a recent change to include only public contributions on the main page of each country. If you have mostly private contributions, you'll probabl find yourself on the subpage with private contributions included.

Ah I see, thanks @lauripiispanen!


@mixin not working with autoprefixer v7.1.6

_rem.scss @mixin not working with autoprefixer v7.1.6. But it work with autoprefixer v7.1.5.
Please check the link error: http://prntscr.com/hebaqx

Hi,
mh strange, I can't see how it's related with autoprefixer since it works on the compiled code.
Are you sure that you're importing the lib properly ?

I guess you sorted it out.

It's fix. Thanks.


fix broken link

On this page, this link is broken "Follow instructions from the [getting started chapter](https://openscapes.github.io/quarto-website-tutorial/first-observations.md#set-up-github-publishing)."
@jules32 I'm not sure where it should be pointing and I feel like I just followed these instructions.

Ah yes it should pint here: https://openscapes.github.io/quarto-website-tutorial/explore.html#set-up-github-publishing!

@jules32 do you mind changing my permissions so I don't have to fork?

Yes, done!