matplotlib basemap colorbar exception : Given element not contained in the stack

please see it at https://github.com/matplotlib/matplotlib/issues/23186

Hi @redstoneleo! Sorry for the late reply. I have taken your example snippet and I paste it here for the record:
import sys

import numpy as np
from matplotlib import cm
from matplotlib.backends.backend_qt5agg import FigureCanvasQTAgg as FigureCanvas
from matplotlib.backends.backend_qt5agg import NavigationToolbar2QT as NavigationToolbar
from matplotlib.figure import Figure
from mpl_toolkits.basemap import Basemap
from PyQt5 import QtWidgets

class MainWindow(QtWidgets.QMainWindow):

    def __init__(self, parent=None):

        super().__init__(parent)

        button1 = QtWidgets.QPushButton("button1")
        button2 = QtWidgets.QPushButton("button2")

        self.map_canvas = FigureCanvas(Figure(figsize=(20, 20)))
        self.map_toolbar = NavigationToolbar(self.map_canvas, self)

        central_widget = QtWidgets.QWidget()
        self.setCentralWidget(central_widget)
        lay = QtWidgets.QGridLayout(central_widget)
        lay.addWidget(button1, 0, 0)
        lay.addWidget(button2, 0, 1)
        lay.addWidget(self.map_canvas, 1, 0, 1, 2)

        self.addToolBar(self.map_toolbar)

        button1.clicked.connect(self.update_plot)
        button2.clicked.connect(self.update_plot)

        self.ax = self.map_canvas.figure.subplots()
        self.ax.set_axis_off()

    def update_plot(self):

        self.ax.clear()

        m = Basemap(width=12000000, height=9000000, projection="lcc",
                    resolution="c", lat_0=19., lon_0=73., ax=self.ax)
        m.drawcoastlines(linewidth=1)

        x, y, z = np.random.rand(3, 1000000)
        x *= 12e6
        y *= 9e6
        z *= 20000

        gridsize = 100
        m.hexbin(x, y, C=z, gridsize=gridsize, cmap=cm.YlGnBu)

        # cb = m.colorbar()
        self.map_canvas.draw()

if __name__ == "__main__":

    app = QtWidgets.QApplication.instance()
    if app is None:
        app = QtWidgets.QApplication(sys.argv)

    window = MainWindow()
    window.show()

    sys.exit(app.exec_())

If cb = m.colorbar() is commented as above, then your snippet is working for me on Windows x64 with Python 3.11, basemap 1.4.0-dev and matplotlib 3.7.4 (image below is after clicking the left button):

If I uncomment cb = m.colorbar(), I get an error after clicking the left button, but it is different from the one reported in your other issue:
Traceback (most recent call last):
  File "C:\Users\vic\OneDrive\Workspace\github\example.py", line 55, in update_plot
    cb = m.colorbar()
         ^^^^^^^^^^^^
  File "C:\ProgramData\pyenv-win\pyenv-win\versions\py311\Lib\site-packages\mpl_toolkits\basemap\__init__.py", line 4707, in colorbar
    fig.sca(ax) # reset parent axes as current axes.
    ^^^^^^^^^^^
  File "C:\ProgramData\pyenv-win\pyenv-win\versions\py311\Lib\site-packages\matplotlib\figure.py", line 1645, in sca
    self._axstack.bubble(a)
  File "C:\ProgramData\pyenv-win\pyenv-win\versions\py311\Lib\site-packages\matplotlib\figure.py", line 97, in bubble
    raise ValueError("Axes has not been added yet")
ValueError: Axes has not been added yet

So I can confirm you that something is not working with Basemap.colorbar as expected. I do not think a bugfix can be made for basemap 1.4.0, because I want to release today or tomorrow, but I will try to inspect the issue when I get some time.


fix(a11y): accessible name for text inputs on settings page

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Not sure when this happened, but the text inputs on the Settings page don't have accessible names because both the input and the div wrapping the input (and label) are using the same id, which is preventing the label from doing its job properly. This PR merely creates a new unique id for each input so that its label can point to it properly.

@naomi-lgbt Thank you for fixing that test for me.

Glad to help! Wanted to get this in so I could do one last deploy :3


SensorManager unit tests

Fixes #23  partly.
There is no CI integration but I ran following successfully locally:-
./gradlew spotlessapply
./gradlew check

Thanks @MJ1998 for the changes. If possible, try to attach the test coverage report snapshot in the description (I am assuming it could be created from IDE).


Create full dump transmission dag

Supply vendor as config at runtime when triggering DAG:
e.g.

{
    "vendors": [
    	"",
      	"",
      	""
    ],
    "bucket": ""
}

Provide a bucket default in dag (configured as airflow Variable)?
Dag should use the existing tasks for transmitting the data in the bucket.
Transmission tasks should be configured to be able to pull from bucket or filesystem as needed.

Maybe need a new method or function to interrogate S3 instead of using pathlib? Use s3Path

Call exiting transmission tasks according to list of vendors in config.
No archiving needed at this time
POD will PULL from S3
Vendors which need a PUSH:

ShareVDE?

others?

Here is an s3 url for dev:
s3://folio-data-export-development/data-export-files/full-dump/marc-files/99000_100000.mrc

For supplying a configuration (params) when triggering the DAG, wouldn't we just need to know the vendor? Presumably the S3 bucket with the files wouldn't be different, it'd always be the path data-export-files/full-dump/marc-files. If the params is a list of vendors, then one DAG run would be responsible for sending the files to a list of vendors? I think maybe a DAG run should be sending files to one vendor. Or should a list of vendors equate to multiple DAG runs, one for each vendor? Is there a default vendor we should use when triggering the DAG or should it fail if there are no vendor params passed?

For supplying a configuration (params) when triggering the DAG, wouldn't we just need to know the vendor? Presumably the S3 bucket with the files wouldn't be different, it'd always be the path data-export-files/full-dump/marc-files. If the params is a list of vendors, then one DAG run would be responsible for sending the files to a list of vendors? I think maybe a DAG run should be sending files to one vendor. Or should a list of vendors equate to multiple DAG runs, one for each vendor? Is there a default vendor we should use when triggering the DAG or should it fail if there are no vendor params passed?

The bucket would just be (e.g.) folio0data-export-development or folio-data-export-prod, but yes the path would be the same for all of them.


SQL Server Connectivity feature

I've been involved in migrating SUSDB from WID to a SQL Server box and we followed all steps provided, but at the end Server Manager was keeping alterting of uncompleted WSUS configuration. Though we try to run the configuration was failing due to an error resembling the folliwing entries:
2013-07-23 11:03:18  Postinstall started
2013-07-23 11:03:18  Detected role services: Api, UI, WidDatabase, Services 2013-07-23 11:03:18  Start: LoadSettingsFromXml
2013-07-23 11:03:18  Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentLocal 2013-07-23 11:03:18  Value is true
2013-07-23 11:03:18  End: GetConfigValue
2013-07-23 11:03:18  Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentDirectory 2013-07-23 11:03:18  Config file did not contain a value "ContentDirectory" 2013-07-23 11:03:18  Microsoft.UpdateServices.Administration.CommandException: A required configuration value was not found in the system. This is usually caused by installing WSUS through PowerShell and not specifying a configuration file. Review the article Managing WSUS Using PowerShell at TechNet Library (http://go.microsoft.com/fwlink/?LinkId=235499) for more information on the recommended steps to perform WSUS installation using PowerShell.
at Microsoft.UpdateServices.Administration.PostInstall.GetConfigValue(String filename, String item)
at Microsoft.UpdateServices.Administration.PostInstall.LoadSettingsFromXml()
at Microsoft.UpdateServices.Administration.PostInstall.Initalize(Parameters parameters)
at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
Fatal Error: A required configuration value was not found in the system. This is usually caused by installing WSUS through PowerShell and not specifying a configuration file. Review the article Managing WSUS Using PowerShell at TechNet Library (http://go.microsoft.com/fwlink/?LinkId=235499) for more information on the recommended steps to perform WSUS installation using PowerShell.
We were able to resolve the issue, by removing the WID feature and installing the SQL Server Connectivity upon restart. At that point, Server Manager was asking to complete the configuration but the this time the configuration gone smoothly.

@robinharwood, @Xelu86
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Fix heartbeat channel subscriptions

Automatically adds the heartbeat channel if not already subscribed
Removes redundant keepalive ping on the socket

Fixes #113

I like the change, just one comment

Rebased. Let me know if the automatic heartbeat channel is a show stopper.  I'm in favor of keeping the automatic heartbeat. Without it, I suspect we'll need to add the keepalive socket ping back in (i.e all the deleted code from this pull-request and all the extra liability of 100+ lines of code that comes with it).

Rebased again to resolve new conflicts.

Thanks a lot @rmm5t!


[backport] bump github.com/hashicorp/go-getter to v1.7.4 (#25040)

(cherry picked from commit 50b1032013b22111baba1fce7e0e4705c0a855d8)

What does this PR do?

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Lost Packs in the AWS.pidx update

Hi,
is there a reason to drop some of the packs from the pidx ?
  <pdsc url="https://github.com/FreeRTOS/CMSIS/releases/download/Beta/" vendor="AWS" name="FreeRTOS_LTS" version="2020.12.1-Beta"/>
    <pdsc url="https://github.com/FreeRTOS/CMSIS/releases/download/Beta/" vendor="AWS" name="FreeRTOS-Plus-TCP" version="2.3.2-Beta"/>

Are you planning to update/replace/add them in one way or another?
The trouble with those versions is that they refer to versions of packs that you have removed from the release history and therefore can no longer be located by the pack managers.
e.g.: Required packs not installed for AWS.FreeRTOS_LTS.2020.12.1-Beta ( AWS.AWS_IoT_Device_Defender.[1.1.0-Beta] )

Problem got resolved. Thank you.


Update to node 12

Hey @znarf can we bump it to
Node 12.13.0
npm 6.12.0

As 12.13.0 is now an LTS version

@maddhruv yes we can, thank you for spotting that. I didn't check properly what was the latest

in package-lock.json some of the package resolvers are resolved to https:// which is good but some are resolved to http:// 😕 which I don't understand
@znarf can you do a fresh install

@maddhruv no, it's npm buggy behavior that is like that for many years, we're living with that

npm buggy behavior

😕 I don't get it, what sort of buggy behavior

@maddhruv https://npm.community/t/some-packages-have-dist-tarball-as-http-and-not-https/285/39

https://npm.community/t/some-packages-have-dist-tarball-as-http-and-not-https/285/53
Do we have to do this?
I don't think http vs https for npm registry will make more difference but still?

Removing the modifications to package-lock.json because they were out of scope in the first place.


build: fix delta_generator and enable by default

Missed this in 918a9d80, I thought I was building everything but
overlooked that configure wasn't enabling this option.

LGTM


Fix miscellaneous errors in "Filter Pattern" section of GitHub Actions / Reference / Workflow syntax

What article on docs.github.com is affected?
This pertains to https://docs.github.com/en/free-pro-team@latest/actions/reference/workflow-syntax-for-github-actions.  (I could have updated issue #825 but chose to make a new issue instead.)
What part(s) of the article would you like to see updated?
This issue has to do with the File pattern cheat sheet section of the article.

The third sentence in the explanation of the meaning of [] is "For example, the range[0-9a-f] matches any digits or lowercase letter."  This, of course, is not true; it doesn't match "g" for example.  Either the range should be changed to [0-9a-z], or the explanation should read "any digit or any of the lowercase letters a through f."  Note that in any case, strictly speaking, it should read "any digit", not "any digits", although I doubt anyone will be particularly confused by "any digits."
In the Patterns to match branches and tags and Patterns to match file paths (sub)sections, all of the example matches appear to start with a hyphen.  For example, the very first branch-matching pattern shown is feature/*, and the example matches given appear to be -feature/my-branch and -feature/your-branch, which don't actually match the given pattern.  I'm guessing that the initial hyphen is meant to serve the function of a bullet point and not meant to be considered as part of the matched text, but this is rather confusing, especially since the matches also contain internal hyphens.  In some cases, hyphens appear at the start of the patterns themselves, but pattern examples such as -!README.md suggest that the hyphen is not meant as part of the pattern.

Thanks for opening an issue @gsrohde! I'll get this triaged so someone can take a look ⚡

Thanks for this one too, @gsrohde!

...  "For example, the range[0-9a-f] matches any digits or lowercase letter." This, of course, is not true; it doesn't match "g" for example. Either the range should be changed to [0-9a-z], or the explanation should read "any digit or any of the lowercase letters a through f."

😆 haha yep, you are totally correct. Maybe the original author was thinking in hex when they wrote that? (definitely could have been me 😁)

In the Patterns to match branches and tags and Patterns to match file paths (sub)sections, all of the example matches appear to start with a hyphen.

I think your analysis of the hyphens supposing to represent bullet points is probably correct. I agree that it is confusing;  unfortunately markdown support in table cells is too great. I think we should probably remove the hyphens and just have each example on a separate line.
Anyone can feel free to pick up and implement ☝ 🙂


Add fish ai which swim through water

Can use DoTS and boids for this and the density sensor to check if the fish are in the water


Allow execution through CLI

This PR adds a small wrapper to be able to run polyline from the CLI.

:+1: awesome, thanks!


how to set etcd username and password in gateway

I use the gateway feature of go-zero to implement the mapping from HTTP to gRPC, and use etcd as the RPC service discovery. However, when I set the username and password for etcd, the etcd client reports: "etcdserver: permission denied".
go code:
gc.Upstreams[i].Grpc.Etcd.Hosts = config.Conf.EtcdAddress gc.Upstreams[i].Grpc.Etcd.User = config.Conf.EtcdUser gc.Upstreams[i].Grpc.Etcd.Pass = config.Conf.EtcdSecret
xxx.yaml
Upstreams:

Grpc:
Etcd:
Key: user
Hosts:
- ""
proto set mode
ProtoSets:
- ./protocol/user/user_req.pb
- ./protocol/user/user_res.pb
- ./protocol/user/user_service.pb
Mappings can also be written in proto options
Mappings:
- Method: get
Path: /user
RpcPath: user.UserService/GetUser

Verify you're setting correct username/password.


Increase visibility of alternative (none VS) approach

When creating a new PR, please do the following and delete this template text:

Reference the issue number if there is one:
Fixes #Issue_Number

The "Fixes #nnn" syntax in the PR description causes
GitHub to automatically close the issue when this PR is merged.

Suggest reviewers if you know who should review the PR, using the GitHub Reviewers UI.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@Rick-Anderson I really like this PR's idea of visually separating the two options. Should we introduce tabs instead of H3 headings?

@scottaddie  Yes, tabs preferred.

@scottaddie  see my commit and merge when ready. @JosephWoodward  Thanks!

@scottaddie  changed to .NET Core CLI


How to obtain intuitive 3D results.

Dear author,
Hello. I encountered an issue when using the command ns-render to render my model results. Even though I changed the file name of the output file to .mp4 extension, the result is still a bunch of rendered images in my folder. Then, when I opened the Nerf Studio webpage using the command ns-viewer, I got an unordered green screen and a stack of overlapping photos instead of a 3D scene generation. This prevents me from confirming the 3D scene generated by my model from any perspective.
I used approximately 30 photos (lastframe-firstframe=30), trained for about 60000 iterations, and the PSNR convergence value is 24.25( The rendered pictures performance very well ). I would like to know if this issue is related to the small number of my train-set or if there may be some other problems.
Furthermore, I would like to ask if there are any other good methods to obtain visualized results of 3D scenes apart from ns-viewer. I look forward to your reply.

Hi! Thanks for your reply!

I encountered an issue when using the command ns-render to render my model results. Even though I changed the file name of the output file to .mp4 extension, the result is still a bunch of rendered images in my folder.

We kindly suggest using scripts/cicai_render.py to render your result. In this script you can easily modify the output format.

Then, when I opened the Nerf Studio webpage using the command ns-viewer, I got an unordered green screen and a stack of overlapping photos instead of a 3D scene generation. This prevents me from confirming the 3D scene generated by my model from any perspective.

You need to manually modify the output channel in niewer.

I used approximately 30 photos (lastframe-firstframe=30), trained for about 60000 iterations, and the PSNR convergence value is 24.25( The rendered pictures performance very well ). I would like to know if this issue is related to the small number of my train-set or if there may be some other problems.

The rendered results are not directly strongly correlated with the number of training images. But if you train with a longer sequence, the PSNR might be affected.

Furthermore, I would like to ask if there are any other good methods to obtain visualized results of 3D scenes apart from ns-viewer. I look forward to your reply.

We currently only support obtaining 3D visualization results through ns-viewer.

Thanks a lot for your work and reply!

Sorry for reopen the issue. I tried to solve problems following your reply, but I didn't success.
I set the ns-viewer like what you show in comment, but I still get the under result:

And I get a very little size video file ( about 300KB ) when I fix the output_format = "video" ( btw , input_frames=30, times about 60000). It's abnormal since the size of each picture I used to train from kitti image 0006 takes more than 500KB.
I'm waiting for your reply.

Hi! Thanks for your reply!

I set the ns-viewer like what you show in comment, but I still get the under result:

To obtain visualization results of the reconstructed 3D scene, you should set Output Render to rgb. For different output channels, you should modify it to corresponding options.

And I get a very little size and unplay video file ( about 300KB ) when I fix the output_format = "video" ( btw , input_frames=30, times about 60000). It's abnormal since each picture I used to train from kitti image 0006 takes more than 500KB.

Please have a try with scripts/cicai_render.py.

@xBeho1der
hello, i met the similar issue. According the latest suggestion, i have changed the ourput render to rgb. However, i sill don't get any reasonable visualization.

Hi! @gallenszl

Maybe resetting the up direction might help you better observe the scene. Click SCENE and you will find the button.
You should click one image after resetting up direction, and then you can change the viewport following the guidance. Below is an example image.

Hi! Thanks for your reply!

I set the ns-viewer like what you show in comment, but I still get the under result:

To obtain visualization results of the reconstructed 3D scene, you should set Output Render to rgb. For different output channels, you should modify it to corresponding options.

And I get a very little size and unplay video file ( about 300KB ) when I fix the output_format = "video" ( btw , input_frames=30, times about 60000). It's abnormal since each picture I used to train from kitti image 0006 takes more than 500KB.

Please have a try with scripts/cicai_render.py.

I do use command python scripts/cicai_render.py --load-config outputs/0006/nsg-kitti-car-depth-recon/2023-08-24_182319/config.yml --output-path renders/output_recon03.mp4 to render video,  and it generate output_recon03.mp4 which is a little unplay video, my cicai_render config is as follow:

As to the viwer problem, I tried the latest comment you reply and it works. However,  the scene looks a little ambiguilty and the angular is a little weired ( can I ask how to fix it btw? ).

Thanks for your all help!


Session DBTableGateway Loop ZF 2.7

Hey,
i get a endless loop in

Zend\Session\SaveHandler\DbTableGateway->read( )	...\Module.php:47
Zend\Session\SaveHandler\DbTableGateway->destroy( )	...\DbTableGateway.php:107

the read function will check if the lifetime is over if it is over it will run the destory method. destory again start the read method, i guess to check if the session is in the database, and over again...
To solve this issue for myself i just removed the
//if (! (bool) $this->read($id)) {         //    return true;         //}

Please run composer update; we pushed a new release of zend-session yesterday that resolves this issue. If you continue to experience the issue after updating, please report it against that component.


[Tooltip] Don't show if title is undefined, null or false

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
Tooltip shouldn't be shown if title property is undefined, null or boolean false.
Currently only explicit empty string works and for null / undefined / false empty screwed tooltip is still show,
Examples 🌈
https://codesandbox.io/s/basictooltip-material-demo-forked-zy0vq?file=/demo.js

Motivation 🔦
It's a common approach in React to not render undefined / null / false element, same expected from tooltip.

It makes sense. However, there could be applications that rely on the existing behavior, so I'd propose waiting for v6 with such a change.
A workaround, for now, would be to fall back to an empty string if a value is nullish or false:
function BetterTooltip(props)  {
    return <Tooltip {...props} title={(props.title != null && props.title !== false) ? props.title : '')}  />
}

Hi @michaldudak  I can't imagine how any application could use such a weird empty rudiment of tooltip as you see on screenshot.

This issue feels almost like a duplicate of #9714. There, the argument was made that no supporting, null, undefined, false would be preferable because it would force developers to be explicit about how they want to handle edge cases. Is the value undefined because the translation key for the title missing or something else?
Now, if this issue is about keeping the prop-type error and keeping the TypeScript when an invalid title is provided, then 👍. It would lead to a better fallback UX when things go wrong but, while still encouraging developers to handle the case.


Create deployment yaml to template out a non specific deployment

Current state includes a helm chart with specific reference to domain databases. We only need the definition of the horkos application database and domain databases would otherwise be referenced specific per implementation.

CI required for horkos in github.

Not required.


Index html error styling bottom page2

#69

@evanhearne looks like there are still some changes relating to both the calendar and the navigation work in here. Ideally they would be kept seperately. In this case let's go ahead and do these ones. The conflict however needs to be resolved before this can be progressed. Do you you have some time to resolve this?

@laurafitzgerald working on it now.
On Mon 3 Dec 2018 at 16:18, Laura Fitzgerald<EMAIL_ADDRESS>wrote:

@evanhearne https://github.com/evanhearne looks like there are still
some changes relating to both the calendar and the navigation work in here.
Ideally they would be kept seperately. In this case let's go ahead and do
these ones. The conflict however needs to be resolved before this can be
progressed. Do you you have some time to resolve this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MountSionCBSSecondary/SchoolWebsite/pull/71#issuecomment-443769130,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfcRr1yDfnqz3Yz9eu3P8mRjP21aQdvUks5u1U7pgaJpZM4Y7ZSG
.

@laurafitzgerald conflicts have been fixed. Feel free to look through it when you have the time. :)

If @denispop9 would like to look also, feel free to do so. :)

@laurafitzgerald thank you for requesting changes, I will take a look at them soon.

@laurafitzgerald indeed, there was something strange going on with those  tags; there were 8 opening tags, but 7 closing tags. Because of this, I have added in an extra closing tag. Feel free to review the changes when you have the time. :)

@evanhearne I'm still seeing the same issue, did you verify this new change worked on your end?

@laurafitzgerald I tested the new changes on my side and they don’t work
either. I will investigate my changes made soon.
On Fri 7 Dec 2018 at 10:56, Laura Fitzgerald<EMAIL_ADDRESS>wrote:

@evanhearne https://github.com/evanhearne I'm still seeing the same
issue, did you verify this new change worked on your end?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MountSionCBSSecondary/SchoolWebsite/pull/71#issuecomment-445197165,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfcRr6OXwg2k-mrSqAQ-OfGNHAAztvmHks5u2klLgaJpZM4Y7ZSG
.

@laurafitzgerald just an update. Sorry, but I haven't looked at the files yet to see what the problem is. What I will do though is investigate the current master branch and compare it with the branch and do some debugging. Hope the Christmas festivities are going well! ;)

@evanhearne I've verified that the change works. The index page is rendering correctly. Next step here is to reflect the change in all the other pages on the site so that there is only once copy of the navigation which get's pulled in by all the files in the same way you've done it for index.html.


Create space-cli getters for cluster level & integration config

Not sure if we should add this to space-cli get all since that works on the project level

Done

Done


Add: version number in window

It would be helpful to see what version of bolero one is using. Would it be possible to add the version number somewhere in the window, or maybe in the title bar?

I concur.


Accordion doesn't support children property

Issue:
If you use the GoAAccordion (React issue), you get an error that property children does not exist. This is with the latest version of React.

Replication Steps:

Use any of our existing Accordion code, but use it in a React 18 App

Acceptance Criteria:

GoAAccordion works correctly in the latest version of React
Should probably test the rest of our components as well. As this has been a re-occurring problem for a few of our components.

:tada: This issue has been resolved in version 4.0.0-alpha.166 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.0.0-alpha.204 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 2.0.0-alpha.18 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.0.0-alpha.23 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 2.4.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 4.13.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.5.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.13.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


rand: fix wasm global reference

Fixes this build error under GOOS=js GOARCH=wasm:
./rand_js.go:15:25: js.Global.Get undefined (type func() js.Value has no field or method Get)

Hey @paralin, thanks for the PR!
In #77, we've moved these to internal, so this PR now has conflicts - sorry about that.
That being said, we should probably update internal/rand and internal/rsa to the upstream versions, where this is apparently already fixed. Would you be interested in working on that? If not, I'm also happy to merge (a rebased version of) this, dw.
Though - this is a bit off-topic but - is your goal to have an openpgp implementation running in the browser? If so, OpenPGP.js may be a more appropriate choice.

hi @twiss - it's a 1 line change, updated the PR.

(I am not using this package heavily, but it was a dependency of one of the other dependencies, so when building for js / wasm this step failed)
So I'm not the best person to look at major changes to this, just minor fixes for now.

Alrighty :+1: thanks!


NumpyArray::getitem_next_jagged is undefined for ndim == 2

Version of Awkward Array
1.4.0
Description and code to reproduce
I think we should support this given that it works if the NumpyArray is converted into a RegularArray:
array = ak.Array(
    ak.layout.ListOffsetArray64(
        ak.layout.Index64(np.r_[0, 4, 4, 6]),
        ak.layout.NumpyArray(np.arange(4 * 6).reshape(6, 4)),
    )
)
ix = ak.Array([
    [[0], [1], [2], [3]],
    [],
    [[3], [2]]
])

This fails:
array[ix]

This succeeds:
ak.to_regular(array, axis=-1)[ix]

I would expect the result of jagged indexing into a NumpyArray to produce a jagged result (i.e. behave as it currently does for RegularArray).
The simplest solution would be to re-use the RegularArray code here, i.e. toRegularArray()->getitem_XXX but I don't know what the protocol on this is vs doing less work by implementing a solution specifically for NumpyArrays. I suspect here it's not unreasonable because the conversion to RegularArray is cheap (?)

I had thought this was related to #1022, but it's not.
Yes, we can do toRegularArray for this (that's what PR #1029 does), as toRegularArray is pretty cheap. If the NumpyArray is not contiguous, it will need to be rewritten, but otherwise it will not. ListArrays have been converted toListOffsetArray64 (more expensive) with less motivation!


Try CoordConv

https://medium.com/@Cambridge_Spark/coordconv-layer-deep-learning-e02d728c2311
Suggested by @thecapeador
The idea being that it's really important for the CNN to discriminate between based on their location.
Several combinations to try:

[ ] Location relative to the pixel boundaries of the image (i.e. the x and y locations of the pixels)
[ ] The geospatial position (lat, lon)
[ ] The clouds in the direct path between the sun and the PV system in the center of the image?!?  (actually quite excited about this idea!)

See @jacobbieker's neat implementation :) https://github.com/openclimatefix/satflow/commit/7f4d7e5397e809016b72a0f586f907fdbec7adb6


Package request: crealty-print

Project description
A cura slicer fork developed by Crealty optimized for their own 3D printers.
Metadata

homepage URL: https://www.creality.com/pages/creality-print-software
source URL: https://github.com/CrealityOfficial/CrealityPrint
license: AGPL-3.0
platforms: unix, linux, darwin

Add a :+1: reaction to issues you find important.

@ByteSudoer any updates?


Make use of ZMQ_HAS_RVALUE_REFS

Move semantics is implemented in cppzmq when this is defined.

cc @JohanMabille

It seems that cppzmq 4.3.0 which is at use now detects whether it should use that definition or not. Closing.

For reference: https://github.com/zeromq/cppzmq/blob/d641d1de4c8aa7f2dc674d80b3a71469364b9534/zmq.hpp#L80


Fixed #18 and few other improvements collected from other contributors

"This branch has conflicts that must be resolved"


Scroll to top on route change

How can we make the page scroll back to top on route change? Is there a function we can hook into the Link component? Some kind of option or something

@notangelmario The solution should probably similar to what they recommend in react-router: https://reactrouter.com/web/guides/scroll-restoration/scroll-to-top
import { useEffect } from "react";
import { useLocation } from "wouter";

export default function ScrollToTop() {
  const { pathname } = useLocation();

  useEffect(() => {
    window.scrollTo(0, 0);
  }, [pathname]);

  return null;
}

Thank you very much!

Just wanted to note that the solution above is outdated:
import { useEffect } from "react";
import { useLocation } from "wouter";

export default function ScrollToTop() {
  const  [ pathname ] = useLocation();

  useEffect(() => {
    window.scrollTo(0, 0);
  }, [pathname]);

  return null;
}

Simply change the curly braces to square brackets and you are set!

I've updated my comment, thanks for noticing the typo @xav-ie


Clean up imports. Now, examples/launch_height_baselines.py runs witho…

…ut any AWS dependencies (only requirements_noaws.txt)
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

One thing missing here: Installing syne_tune[no_aws] installs both core + no_aws, since core is always installed. It would be good to allow users to call setup.py with the no_aws dependencies only.

First (necessary) step for integration into AutoGluon

OK, I will redo this one


Dev Drive w/ WSL Integration

Suggested new feature or improvement
Heya! WSL is a nice addition to my workflow alongside Dev Home. Yet, this is one of the thing specific to Dev Home I somehow would love to have.
I know this is already a feature esp in Windows though I would love for it to be accessible and editable in WSL2. I tried mounting things and I always get read-only errors when I edit or use git.
Scenario
This feature would be very useful especially if you've came from Machine Configuration page as it would greatly speedup the development process.
Additional details
No response

Duplicate of #748


Question about Barreto-Naehrig precompiles

The Barreto-Naehrig precompiles in geth are called bn256*. See here https://github.com/ethereum/go-ethereum/blob/3c46f557/core/vm/contracts.go#L75-L77
But the ones in Frontier are called bn128*. See here https://github.com/paritytech/frontier/tree/master/frame/evm/precompile/bn128
Why is that? Are they computing the same thing in all cases?

Lol, I also just learned what the bn actually stands for


Grad of int

It is currently not possible to take a gradient with respect to integer inputs in Jax. When an integer in- or output is encountered a hard error is thrown. The aim of this PR is to support integers in AD by returning a zero-vector in a trivial vector space when taking the gradient with respect to an integer. More concretely: if the primal value is integer or boolean, the tangent value will be a zero-vector with a trivial dtype (float0).
Steps:

[x] Add new float0 dtype representing a trivial vector space, along with a Float0Array to represent the arrays that will be returned as tangent values
[x] Support jvp of the identity function with integer primal and float0 tangent
[x] Ignore float0 args in jvp rules (either by replacing them with ad.Zero at the jvp boundary or special casing the rules) and test jvp of non-identity functions
[x]  Support grad of integers
[x] Support jit in presence of float0s
[x] Make all tests pass
[x] Add method to cast Float0Arrays to float zero-vectors
[x] Add a clear error explaining float0s and differentiating wrt int/bool inputs. Ideally it would be an error on any unsupported operation on the Float0Array (and maybe where the float0 originated?).

This is looking really good! I checked through everything except the xla.py changes, which might need to be tweaked a little for compatibility with #3983 if that one goes in first.

@cgarciae  I don't think we plan to support automatic dtype promotion, or even necessarily to support any jax.numpy functions with this dtype. So you won't be able to do much with a float0 array! It's basically a dummy.

Hmm. But if by mistake one of the parameters of the network is an int32 and its gradient is of type float0, a library like optix/optax will try to add them up.

But if by mistake one of the parameters of the network is an int32 and its gradient is of type float0

Yes, all the more reason not to silently promote the dtype, and instead require users be explicit about what they want! Users/libraries who differentiate with respect to integer dtypes should know what they're doing.

It makes sense. It will be a bit weird for users however that the error appears in the optimizer code and not directly on grad, might get hard to debug.
Can grad be modified to give an error or warning via a flag?

Yeah, there's a comment I left on this PR today to that effect; on master, there is such an error.
But maybe we can do a good enough job of raising a good error when operating on a float0 array. We could even track that the value arose from a particular grad evaluation...

I think all tests pass now!

Our new Copybara flow requires that any squashing we want be done manually (and it looks like this PR should probably be squashed); can you do that? (Or maybe we want a change to the CL export script?)

I've squashed the commits. The CL export script works correctly in that it always amends and force pushes one commit but I switched to a git workflow in the middle of the PR.

Other edge cases that came up in my testing:

Both jacfwd and jacrev raise errors.
np.array(Float0Array) returns a 0d object dtype array. If you decide to keep Float0Array, you should define a __array__ method to fix this. It should probably either return a NumPy array with float0 dtype or raise an error.

Added a allow_int flag to grad so you have to opt-in to the grad-of-int behavior. For jvp and vjp no checks are done. This means most accidental use of integer arguments in a grad context will still be captured by the current input data-type checks.


Bump version to v0.6.1

This PR bumps CastSponsorSkip version to v0.6.1, which contains a pretty important bugfix to improve reconnection when a Cast device is rebooted.

Thanks!


400 Bad Request using Oauth

Having a really strange issue but I'm not sure how to recreate the issue.  My client has a woocommerce site using 2.5.5.  When connecting using oauth, any request that I attempt to make from my server will get a 400 bad request.
After investigation into what causes this issue it seems like the culprit is:
    def do_request method, endpoint, data = {}
      url = get_url(endpoint, method)
      options = {
        format: :json,
        verify: @verify_ssl,
        headers: {
          "User-Agent" => "WooCommerce API Client-Ruby/#{WooCommerce::VERSION}",
          "Content-Type" => "application/json;charset=utf-8",
          "Accept" => "application/json"
        }
      }
      if @is_ssl
        options.merge!(basic_auth: {
          username: @consumer_key,
          password: @consumer_secret
        })
      end
      options.merge!(body: data.to_json) if data
      HTTParty.send(method, url, options)
    end

When it merges the data.to_json it seems to encode the body as "{}"
perhaps modifying the line to be
options.merge!(body: data.to_json) if data.present
will be a better approach since "{}" will always be truthy

Using wrong version.  bundler kept install .10 instead of .12


npm start fails

There is an npm start script defined for the compound project but running it fails since there is no start script for the frontend.

Thinking about it again, we probably don't need a startup script for the frontend. However, we should start thinking about how we'll deploy this application.


Error when using library in webpage

When trying to include the script directly inside a webpage with <script src="node_modules/highlightjs-graphql/graphql.js"></script> I have an error Uncaught ReferenceError: module is not defined.

One workaround is to add:
<script>
const module = {}
</script>

In the page.


TypeError: 'NoneType' object is not subscriptable

I managed to get as far as successfully configuring the component but then it gets the below error which repeats approximately every 50 seconds.
018-08-08 18:27:45 DEBUG (SyncWorker_14) [custom_components.media_player.alexa] Using cookies to log in.
2018-08-08 18:27:47 DEBUG (SyncWorker_14) [custom_components.media_player.alexa] Logged in.
2018-08-08 18:27:47 DEBUG (SyncWorker_14) [custom_components.media_player.alexa] Log in successful with cookies
2018-08-08 18:27:47 DEBUG (SyncWorker_14) [custom_components.media_player.alexa] Setting up Alexa devices
2018-08-08 18:27:54 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/media_player/alexa.py", line 192, in setup_alexa
    update_devices()
  File "/usr/local/lib/python3.6/site-packages/homeassistant/util/__init__.py", line 325, in wrapper
    result = method(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/util/__init__.py", line 325, in wrapper
    result = method(*args, **kwargs)
  File "/config/custom_components/media_player/alexa.py", line 164, in update_devices
    update_devices, url)
  File "/config/custom_components/media_player/alexa.py", line 228, in __init__
    self.refresh(device)
  File "/config/custom_components/media_player/alexa.py", line 267, in refresh
    self._media_is_muted = self._session['volume']['muted']
TypeError: 'NoneType' object is not subscriptable

If there is any further info you require let me know.
Regards,
Michal

I downloaded the current version and this is what I get now.

2018-08-14 17:47:17 DEBUG (SyncWorker_17) [custom_components.media_player.alexa] Log in successful with cookies
2018-08-14 17:47:17 DEBUG (SyncWorker_17) [custom_components.media_player.alexa] Setting up Alexa devices
2018-08-14 17:47:22 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/media_player/alexa.py", line 217, in setup_alexa
    update_devices()
  File "/usr/local/lib/python3.6/site-packages/homeassistant/util/__init__.py", line 325, in wrapper
    result = method(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/util/__init__.py", line 325, in wrapper
    result = method(*args, **kwargs)
  File "/config/custom_components/media_player/alexa.py", line 189, in update_devices
    update_devices, url)
  File "/config/custom_components/media_player/alexa.py", line 253, in __init__
    self.refresh(device)
  File "/config/custom_components/media_player/alexa.py", line 295, in refresh
    if 'muted' in self._session['volume']
TypeError: argument of type 'NoneType' is not iterable
2018-08-14 17:47:35 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/media_player/alexa.py", line 167, in <lambda>
    track_utc_time_change(hass, lambda now: update_devices(), second=30)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/util/__init__.py", line 325, in wrapper
    result = method(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/util/__init__.py", line 325, in wrapper
    result = method(*args, **kwargs)
  File "/config/custom_components/media_player/alexa.py", line 189, in update_devices
    update_devices, url)
  File "/config/custom_components/media_player/alexa.py", line 253, in __init__
    self.refresh(device)
  File "/config/custom_components/media_player/alexa.py", line 295, in refresh
    if 'muted' in self._session['volume']
TypeError: argument of type 'NoneType' is not iterable

Always ready to test a new version :)


Correct test in empty()

Resolves #745

Coverage increased (+0.01%) to 81.916% when pulling e556d07fb43a28dadec5a6a258f734a1bd8b4097 on issue745 into e214bc0ac87df00c29215d81229807fe71cf6231 on maint-1.7.


Allow dexie to be referenced in typescript projects.

e.g.
import * as Dexie from 'dexie';

Dexie will now be properly typed without having to reference Dexie.d.ts in DefinitelyTyped or through src/Dexie.d.ts (which isn't exposed in npm anyways)
If you don't want to duplicate Dexie.d.ts then you could also change the typings line to point to src/Dexie.d.ts but you would also need to add an exception to .npmignore

Sounds good. Didn't know that was possible. Does that mean that Definitelytyped and tsd aren't needed and I could delete Dexie from Definitelytyped? Does it work the same in various IDEs and Typescript versions?

This should work with Typescript >= 1.6. It is working for me in Atom (atom-typescript plugin) and in WebStorm. I haven't tried other IDEs.
https://github.com/Microsoft/TypeScript/wiki/Typings-for-npm-packages

Yeah, if you use the module this way, you won't need definitely typed typings anymore. But I would probably leave them there as well for people that prefer to do it that way. :)

Note: Need to update the typescript samples for this change + make them module based and TS1.6 compatible.

I'm pointing my NPM to the master branch of this repo to test this out and I see that when I do the following, the build seems to be fine but the code itself fails:
import * as Dexie from 'dexie';
export class MyDB extends Dexie {
...
    constructor() {
        super('MyDB');
    }
...

Like I said Typescript likes it just fine but actually loading the page leads to an error about calling super due to it being an object not a function. Looking at what Dexie actually is upon export, it is in fact an object (with a key default that looks like what I want). For some reason, there appears to be a discrepancy between what the typings say and what the actual code has, although I'm fairly new to Typescript so I'm not sure if I'm running into something else.
I'm running Browserify, Typescript 1.6 -> ES6, Babelify.

@samuelhorwitz: __esModule sounds like something that typescript adds.
When it comes down to it, I am doing it the same way:
import * as Dexie from 'dexie';
export class AppDatabase extends Dexie {

  static databaseName = "AppDatabase";
  public $injector: ng.auto.IInjectorService;
  private initialized = false;
  private initializedCallbacks: Array<Function>;

  static migrations: {
    [version: number]: Array<{name: string, migration: IDBMigration}>
  } = Object.create(null);

  constructor() {
    super(AppDatabase.databaseName);
  }

My workflow is using Browserify, Typescript -> ES5.

It's definitely something to do with Typescript to ES6. I'll try and look into it a bit more, my solution for just ignoring it for now is really bad, but involves adding that super value of Dexie.__esModule = true right below the version setter in the node_modules Dexie file. Obviously this is not actually a solution but a stopgap.

Hey guys quick update:
I have a slightly and I mean slightly better hack for this right now.
In my Gulpfile I define the following transform on my Browserify instance:
b.transform (file) ->
    through (buf, enc, next) ->
        key = null

        if (_.find forceEs6FileNames, (f) -> key = f ; !!file.match f)
            buf = handleModule buf, key

        @push buf
        next()
        return
, global: true

This calls a function:
handleModule = (buf, file) ->
    str = buf.toString 'utf8'
    str = str.replace new RegExp("#{forceEs6ModuleMap[file].lineMatcher}.*"), (str) -> "#{str}\n#{forceEs6ModuleMap[file].global}.__esModule = true;\n"
    return new Buffer str

And at the top of the file, I need to declare some mappings (in this case, just for Dexie):
forceEs6ModuleMap =
    'Dexie.js':
        lineMatcher: 'Dexie.version'
        global: 'Dexie'

forceEs6FileNames = _.map forceEs6ModuleMap, (v, k) -> k

Anyway, the better solution here is to support ES6 modules natively I suppose or maybe there is something that does this and I just rewrote it :D Anyway it's kind of painful to watch these ecosystems become more and more of a mess (nothing against the Dexie team, more a comment on JS in general). Hopefully it's just the rough patch before the golden dawn of native browser modules "just working".


Bump minor version of num dependency in Cargo.toml

bump version of num from 0.1 to 0.2,
to remove the indirect dependency on the deprecated rustc-serialize crate
maybe it could also be directly bumped to 0.3 , which is the latest version of num, https://docs.rs/crate/num/0.3.0. I decided to only bump to 0.2 to keep the changes smaller and 0.2 has already some patch releases, and 0.3 does not have any patch releases yet.
this change will allow other crates to compile rust-compress to wasm
(currently it does not compile to wasm, because of the dependency on the rustc-serialize crate

I executed locally the 4 commands of the .travis.yml file, with the following cargo and rustc version:
cargo 1.45.0-nightly (258c89644 2020-04-30) , ustc 1.45.0-nightly (1836e3b42 2020-05-06)
and got this outputs:

cargo build --verbose
Finished dev [unoptimized + debuginfo] target(s) ...
cargo test --verbose
test result: ok. 6 passed; 0 failed; 3 ignored; 0 measured; 0 filtered out
rustdoc --test src/lib.rs -L target
error[E0463]: can't find crate for byteorder
cargo doc
Finished dev [unoptimized + debuginfo] target(s) ...

Thank you!
is num a private dependency?

I am not sure if I understand the concept of private/public depedency correctly,
but there is no direct export like pub use self::num in the code that would re-export num.
However the traits might leak (if this is even possible) via functions like this:
https://github.com/alexcrichton/rust-compress/blob/3f6394cf896ceb47bca7cd2536b48c09c6f0ab86/src/bwt/mod.rs#L207
The num crate is used in these places:
https://github.com/alexcrichton/rust-compress/search?q=num%3A%3Atraits&unscoped_q=num%3A%3Atraits
// src/bwt/mod.rs
extern crate num;
use self::num::traits::{NumCast, ToPrimitive};
// src/bwt/dc.rs
use super::num::traits::{NumCast, ToPrimitive};
// src/entropy/ari/apm.rs
extern crate num;
use self::num::traits::{Float, ToPrimitive};

Yeah, looks like it's public then.
It's been a while since I was involved in this project.
@alexcrichton how do you feel about just handing it over to @rusty-shell ?

Yes this crate hasn't really been maintained for quite some time now. I would be fine handing it off. @rusty-shell would you be interested in taking over this crate?

@alexcrichton @kvark I might be interested in taking over this crate.
However I only have limited experience with Rust. I have been using it since 7 months in after work projects.
Maybe I could create a branch called target_0_2_0. There I would start with fixing the compiler warnings.  There are currently about ~70 warnings, when compiling with current rust compiler.
Then I would update num and other depedencies to more recent versions, where possible.
In places where I will do a lot of changes, (for example to adapt to updated depedencies),
I will add some tests.
It would be great if one of you could go over this target_0_2_0 branch, and check if it looks good.
Then we could merge it in master, and release a 0.2.0 version and I could take over
(minor version bump because depedencies change, wich might be public).
I will use the next 1-2 weeks to get a better overview over the code, and then give you my final decision.

@alexcrichton @kvark Sorry, it took me a bit longer than 2 weeks, but finally I created these 2 PRs:

https://github.com/alexcrichton/rust-compress/pull/62 (remove compiler warnings)
https://github.com/alexcrichton/rust-compress/pull/63 (update dependencies)
I decided to now upgrate directly to num 0.3, instead of only num 0.2, what I planned previously

Sorry I don't have bandwidth to review and/or maintain this crate, but it can be transferred to you if you'd like!

@alexcrichton Yes, thank you. I'd like this. You can transfer it to me.

Ah it looks like you need to delete/rename your fork first before transferring

@alexcrichton I renamed it : https://github.com/rusty-shell/rust-compress_old_fork

rusty-shell already has a repository in the alexcrichton/rust-compress network

Hm maybe you have to delete your fork?

@alexcrichton I deleted it now

@kvark @alexcrichton When i tried to publish the 0.2.0 version, I recived an API owner error.
Can someone add me to the owners please:
cargo owner --add rusty-shell
Logs:
rust-compress$ cargo publish
...
 Finished dev [unoptimized + debuginfo] target(s) in 30.89s
   Uploading compress v0.2.0 (/mnt/c/Users/Daniel/code/rust-compress)
error: api errors (status 200 OK): this crate exists but you don't seem to be an owner.
If you believe this is a mistake, perhaps you need to accept an invitation to be an owner before publishing.

Done


ImportError: No module named yapsy.PluginManager

I tried to run the code
sudo python user.py -p /dev/ttyUSB0
But it shows the error -

Traceback (most recent call last):
File "user.py", line 12, in
from yapsy.PluginManager import PluginManager
ImportError: No module named yapsy.PluginManager

I tried to install yapsy after that also the same error is showing . If I use the code without sudo, then its shows like

serial.serialutil.SerialException: [Errno 13] could not open port /dev/ttyUSB0: [Errno 13] Permission denied: '/dev/ttyUSB0'

Thats why I used the sudo command.
Kindly help me in solving this error

hello .Have you solved  the problems ? Can you give me some advice. thank you


mod causes serious lag issues

cshadow.com.neovisionaries.ws.client.WebSocketInputStream.readBytes()100.00%26388ms(dcintegration)
this is constant. with tihs mod. using forge 1.16.5 . with java 8 and java 11. both give same results.
websocket fails all the time.. always missing heartbeats.. causing tremendous lag amounts.
been goin on for a few versions, but coudlnt track it down .  caught it in a spark report finally.
https://spark.lucko.me/nRVjJnRwF5
i have no idea what this entails and it may not be the mod but some other outside factor.
usin the latest version of dcintergration for my forge. believe its 2.2 now. also happened on the version before this.  and on mutiple modpacks.
any feedback be great. thanks :)

https://spark.lucko.me/CBBESzSaj2
Brand new server. Put mod on.. server lags out and no one can do anything.  Without mod, server stable.  Been 2 weeks and no response.

Can confirm this is still an issue via Spark, which reports is causing over 30 SECONDS of delay. Although an extremely useful mod, disabling it significantly improved performance on my ATM6 server. https://spark.lucko.me/u0X5aosyyx
The problematic function seems to be dcshadow.com.neovisionaries.ws.client.WebSocketInputStream.readBytes()100.00%34720ms(dcintegration)
more specifically
java.net.SocketInputStream.socketRead0()100.00%34720ms (self: 34720ms - 100.00%)

@TheRanker @Reinitialized If you have command block systems running regularly, see if the mod is configured to send command output to discord. If it is (even if no commands show on discord), try disabling the option to send command info do Discord. it seems like the rate limiter will start gobbling up RAM if rate limiting starts kicking in faster than the queue can clear out. I have been experiencing massive lag in connection to excessive RAM usage that I linked back to the rate limiter (see #326 )


Did data statistics implemented in version 5?

according #1482 .
i want to implement this feature by myself，but it will add a lot of works,such data collect,api develope,ui develope,and it will not to common to use (the redis way),and it may make more upgrade coast,im request to official to implement a simple statistics such use filelock and sqlite etc.,and web api.

I'm not sure whether I understood correctly, but please feel free to rephrase your question in any case. I don't aim to create statistics, rather create the API so anyone can do it, that's what I meant on #1482 .

Hooks will be improved in Verdaccio 5, but that is next year hopefully, depends of the available resources, but that is my wish. So things as you suggest will be more easy to address.

sorry,i got wrong understood,hook just mean callback hooks in logs

I don't know what sort of metrics you need, but the logger is the best way to get some. Eg: you might interpret Nginx logs with any third party tool (eg: kibana + logstash) and then get interesting data from there like file downloads, access to a specific package, and version, but all of that is made out of the verdaccio world (theoretically <-- I never tried myself) .
So, as the final answer, it won't be data statitics implementation within Verdaccio 5, but we want to allow others to do it.
I'm closing this, feel free to ask more if you have any doubt.


Which services are not supported

It would be very helpful to detail what this means
"Session hosts on Azure Stack HCI don't support certain cloud-only Azure services."
You guys obviously know what you're referring to here, but someone who is reading this trying to gather requirements for a deployment and seeing if this is vital will have this as a big unknown.  What cloud-only Azure services are you talking about, is this only related to AVD, and how AVD works with Azure, or am I not able to use things like storage accounts file shares, etc.
Being explicit about what is not supported in this scenario is important.

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

ID: f0afe503-0c4c-e744-afe6-1da5c77793e8
Version Independent ID: e732b930-321c-0e04-18f2-9ddad252ac34
Content: Azure Virtual Desktop for Azure Stack HCI (preview)
Content Source: articles/virtual-desktop/azure-stack-hci-overview.md
Service: virtual-desktop
GitHub Login: @dknappettmsft
Microsoft Alias: daknappe

It could be that this statement needs to be entirely removed.  Because the first bullet lists what it doesn't support and those look like Azure only specific features you wouldn't find in HCI. Which is why the presence of this line, is concerning.  You have a very specific list first, and then mention this very vague sentence shortly after.

Hi @johnwildes - thanks for the feedback. I've removed this sentence (it had been like that for a couple of years for some reason) and tidied the section.  The changes should be visible later today.
#please-close


Making forge run anywhere

Previously, I have been unable to run forge on any box outside of AWS. Forge supports ENV vars, but whenever I tried used just ENV vars, I kept failing out.
The changes I made still work on AWS, but forge can now also be used outside of AWS. I've tested the changes inside of AWS to make sure the original functionality was still there and everything worked.
You can test it out yourself on any forge enabled AWS box by ammending the file at /usr/local/sbin/reforge to be
#!/bin/sh

curl https://raw.githubusercontent.com/noqcks/forge/master/bootstrap.py | python

and running sudo reforge.
The only difference when running forge on a machine outside of AWS, is that the following ENV vars will need to be added to your env.
FORGE_REGION
FORGE_BUCKET
ENVIRONMENT
PROJECT
ROLE

Forge usually infers these from EC2 instance tags.
@telusdigital/guild-devops plz review :100:

Comments added. The objective is sound, but the implementation is unsafe to merge. I've noted the issues that I saw. Still waking up, so a second set of eyes might be worthwhile, in case I missed anything.

closing for now. will revisit when I have more time.


Release/0.17.1

Collector RC versions needs to be updated before final release.

Moved here, closing this one.


Keybase APP won't start

The background processes seem to be fine, for instance keybase id works ok.
Two issues I can see:

The Keybase App doesn't start
The /keybase folder won't mount / can't be created

my log id: 67c2f3fc3bfe8bdde6dc851c

Same here.  GUI app won't open, keybase id does work, keybase folder won't mount, but I can push to a git via keybase.  Win7.  No problems prior to a week or so.  log id 6211dcc6650e470c5f04c61c

@Essque That log send is not from a Windows machine, is that the right one?
@ineptech I understand you can click the tray icon, but nothing pops up, is that right? We have a few users reporting such on Win7 but haven't reproduced. Did you recently have a second monitor plugged in?

Hey @zanderz that's the right one. ineptech appears to be on Windows, I'm on Mac.
Cheers for having a look into it, it's much appreciated.

@zanderz Yes, you got it.  I see the tray icon, clicking on it refreshes the taskbar icon but does not open the client app, and I do indeed have two monitors.  Disabling (via windows settings) one display and restarting keybase did not affect the issue.  Here's a log with one display disabled on the offchance it's useful: 7ef42106ce389cfb768be11c
Let me know how I can help troubleshoot.


Restrict OAuth access to specific email domain

What I'm trying to achieve is something similar to Issue #57. I'd like to allow my users to login with Google but restrict access to our G suite domain.
I was considering just forking the repo and adding a step in the login flow that checks if the user's email domain matches a domain passed to loginsrv as an optional config variable. But before I do that, I just thought I'd ask and see if this feature sounds like something generic enough that it could be useful for everyone.
In the Issue linked above, it was mentioned that this restriction could be added by configuring caddy in a certain way.. but we aren't using caddy so I was hoping this check could be added to the loginsrv service itself.
Let me know what you think. I could possibly create a PR if it's a welcome feature. If it seems out of scope, I'll close this issue

Maybe the best currently supported approach is to allow login for all google users and add a users file to give certain claims only to the users of your domain. In the code that authorizes the user through the JWT you only have to check the claims part of the token.

Yeah, I suppose something like that could work for my use case. So then I just have to modify the token verification code part in my fork of the repo to assert a known claim for @mycompany.com users and reject any users that don't have that.

There should be no need to fork loginsrv. It is no problem if somebody can authenticate to your application, if he isn't authorized to do anything. Simply verify the JWT in the http handlers of your application (or in a filter) and you are done. This has to be done either way.
@georgevarghese185 I will close this issue.


endpoints: endure chain before writing any rule

fix https://github.com/coreos/kenc/issues/15

Still verifying it

It fixed the problem


⚠ Empornium has degraded performance

In d82c510, Empornium ($EMP) experienced degraded performance:

HTTP code: 200
Response time: 1376 ms

Resolved: Empornium performance has improved in 09b8123.


Difference between local and imported definition

Local definition:
package b

foo :: {
  a: *"x" | string
}

bar :: foo & {
  baz :: string
  a: foo.a | "y\(baz)"
}

baz: bar & {
  baz :: "me"
}

bazz: bar

$ cue export b.cue
{
    "baz": {
        "a": "x"
    },
    "bazz": {
        "a": "x"
    }
}

Imported definition:
package a

foo :: {
  a: *"x" | string
}

package b

import "x.ai/a"

bar :: a.foo & {
  baz :: string
  a: a.foo.a | "y\(baz)"
}

baz: bar & {
  baz :: "me"
}

bazz: bar

$ cue export b.cue
{
    "baz": {
        "a": "yme"
    },
    "bazz": {
        "a": "x"
    }
}

The cause for this is a bug in the second version, namely at: a: a.foo.a. This is a cyclic reference, as the RHS may refer to the LHS. Because there is a disjunction, however, the error is not reported, but rather the alternative value is reported ("yme").
There is still a very subtle bug in CUE here: technically speaking, this cycle is a "incomplete reference" (the value for a could be a struct, meaning a.foo.a is still resolvable). But arguably, as that value will not unify with the other values anyway and will result in a failure anyway, and thus would result in the same outcome (yme).
I'm marking this with the evaluator and errors tags to see if we can somehow improve the error reporting or lint warnings in such cases once we do the round of improvements in this area.

Thanks for the explanation. Did you really mean to close this bug?

I closed it because the reported issue is not a bug. There is another bug related to this, but that has no direct effect on the outcome here and is already known. This is why I closed it. The added tags will ensure this example is used for verification once these issues are addressed.

This issue has been migrated to https://github.com/cue-lang/cue/issues/238.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


Add test cases to verify yo-BJ(Yoruba -Benin), yo-NG(Yoruba -Nigeria) locales

Checklist

[x] At least one test case is included for this feature or bug fix.
[x] ReleaseNotes has added or is not needed.
[x] This PR has passed all of the test cases on Nodejs and Chrome Browser.
[x] This PR has passed all of the test cases on QT/QML.
[ ] This is an API breaking change.
[ ] Requires a major version change.

Issue Resolved / Feature Added

Added test cases to verify yo-NG (Yoruba -Nigeria), yo-BJ(Yoruba -Benin)
Added test case feature: LocaleInfo,Script, String(plural) LocaleMatch, DateFmt, DurFmt, DateRngFmt, List, Unit, firstDayofWeek, clock, calendar,Month/Weekday Translation, NumFmt,
or translation  and some unitfmt translations are manually updated by google translate's help for ListFmt

Resolution
Links

@ehoogerbeets Could you please to review?


Notification Sound Issue

notification sound does not played

it should play the default notification sound actually, can you confirm the phone is in the ringing mode not in a silent or a not disturb mode?

Hello,
Yes, my phone is in the ringing mode and not in a silent or a DND mode. All
types of volumes are at level 100%. still doesn't working
On Thu, Apr 6, 2023 at 9:02 PM Özgür Taş @.***> wrote:

it should play the default notification sound actually, can you confirm
the phone is in the ringing mode not in a silent or a not disturb
mode?
—
Reply to this email directly, view it on GitHub
https://github.com/10zgurr/NotificationMan/issues/6#issuecomment-1499258771,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE573WNRN3HVJ2KEXYQ2EZTW73O2TANCNFSM6AAAAAAWKDF4FA
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Regards,
Parth JadavMobile No: +91<PHONE_NUMBER>Email Id: @.**
@.**>

if you try it in a different phone or brand you can see that the default ringtone will ring. your issue can be device-specific. so, it is not fixable at the moment.


Adding Sound Postcreation throws error?

I just realized that GitHub wont alert if a user comments on a closed ticket but im asking about an error that is thrown when adding sound to a container that is already created. This is my original comment: https://github.com/dockur/windows/issues/108#issuecomment-1975228342

@kroese I was hoping to add sound in the web tunnel localhost:8006 , when I tried to play any default music on WinXP, it threw an error because there was no sound card, that is why I am asking about it.


Updated COS util

What changes were proposed in this pull request?

Removed dummy operator
Updated cos util (moved to python script, renamed operations to upload and download, and added relative paths to sync operations)

@romeokienzler I think that the automated build is not working. After approval, we need to updated the container image manually.

thanks @blumenstiel
merged


using treat_external: :include + treat_inline causes unwanted behavior

cmock:
treat_external: :include
treat_inline: :include
will cause the original header to be copied over to mocks folder
will check later this day if version issue...

The latest versions of CMock do this when using :treat_inline: :include. In order to mock an inline function, the original inline version can't be included in the header... so the entire file is copied with the inline body replaced with just a declaration. This file is used for testing instead of the original.
Is it causing a problem for you?

not really just wanted to know if its intended i think... forgot the problem already. completely agree... was testing header of someone else... I will try to remember what caused it... maybe there a setting needed in some edge cases...


Multipart/form-data is not supporting file upload in Isolated Workers Net7

I have this endpoint and expect to be able to upload multiple files to test upload function, but swagger do not show file upload button for me; if I use content-type application/octet-stream, it show only one upload file place, which don't meet my expectation.
[OpenApiRequestBody(contentType: "multipart/form-data", bodyType: typeof(object), Required = true, Description = "Files to upload to Azure Storage")]

I think this question should be for Swagger team :)


Add token divider field support to contest voting

This pull request aims to allow educators to specify the divider for the token penalty applied when contest entries are scored. The divider will be specified in the contest XML file under the token_divider field (in ), which is compulsory and will be parsed by the XML parser before later being referenced when calculating the formula score. If the token_divider field is not specified, the BE will not allow the XML contest voting file to be uploaded.

coverage: 94.977% (-0.3%) from 95.246%
when pulling ddc874cc0dd929ba7c3a7b36cae15183b71e2f2c on kjw142857:master
into f46a9cd99805a097c5184dfa2afcefa27b87248b on source-academy:master.


Easy ability to return the current state of the aggregate as part of an aggregate handler workflow or start new stream action

Problem statement
Folks frequently want the current state of the aggregate that is having events captured as a result of an aggregate handler workflow. We need the final state of the aggregate as either:

HTTP response for Wolverine HTTP endpoints
Response as part of IMessageBus.InvokeAsync(message) where "T" is the aggregate

Thoughts

Might need a lighter weight "read only" version of FetchForWriting()

Proposal for Inline Handlers
No change in client's code
Make it magic in the inline handler if using InvokeAsync<T> with extra codegen to get at the current aggregate state.
[AggregateHandler(PublishResult = true)] -- this can be done at the class level. Generate this the most efficient way possible:

If aggregate is Inline, pull it out of the identity map of the current session
If live, gotta do aggregate stream async
If async, be nice to have a lighter weight version of FetchForWriting.

Proposal for HTTP
New convention maybe to express a different response than what comes out of the main endpoint handler method
Respond() : Whatever, and whatever is the actual response? Or Write() : REeponse, and Response is the return.
Alternative 1, use response type
public static class SomeEndpoint
{
    public static (CurrentState, Events) Handle(SomeCommand, Order)
    {
        return (new CurrentState(order), [some events]);
    }
}

And Wolverine "knows" to write out the order in its current state.
public static class SomeEndpoint
{
    public static IEnumerable<object> Handle(SomeCommand, [Aggregate(RespondWithCurrentState = true)] Order)
    {
        return [some events];
    }
}

or
public static class SomeEndpoint
{
    [RespondWithCurrentState]
    public static IEnumerable<object> Handle(SomeCommand, [Aggregate(RespondWithCurrentState = true)] Order)
    {
        return [some events];
    }
}

What happens if command execution succeeds, but aggregate state retrieval fails?

@erdtsieck Meh, good catch. We'll have to beat this by documentation that users will have to handle this by idempotency checks. I don't think it's going to be very likely though with the FetchLatest API coming in Marten

Notes

In HttpChain, look for IResponse in the tryFindResourceType method, look for a response that implements IResponseAware and use that to alter the chain. Nah, let's say it's just a static IResponse interface that will configure the chain
Might have to have a generic way to mark a chain as having an aggregate type. Use IChain.Tags?
Maybe a generic IChain.UseReturnAsResponse(MethodCall). That would allow us to create the response type for HttpChain & the HandlerChain
Latest implements IResponseAware and adds an IDocumentSession.Events.FetchLatest()

Test Cases

[ ] Latest from HttpChain, that's the response
[ ] Latest from HandlerChain, used as a response message for InvokeAsync()
[ ] Latest from handler, used as a cascading message


chore(deps): bump typescript-eslint monorepo to 5.14.0

Summary

close https://github.com/facebook/jest/issues/12530
Test plan

e2e/__tests__/detectOpenHandles.ts is flaky on macOS/node 14 and macOS/node 12. do you know what is the problem is?

No, unfortunately 🙁


Overleaf - Fatal error occurred, no output PDF file produced!

I have created the project as indicated but still getting this error:
/usr/share/texlive/texmf-dist/tex/luatex/luaotfload/luaotfload.sty:49:
==> Fata
l error occurred, no output PDF file produced!

Quick fix: use pdflatex. There should be a setting somewhere.
Am 15.03.2018 21:08 schrieb "Tugay Yentur"<EMAIL_ADDRESS>I have created the project as indicated but still getting this error:
/usr/share/texlive/texmf-dist/tex/luatex/luaotfload/luaotfload.sty:49:
==> Fata
l error occurred, no output PDF file produced!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/latextemplates/scientific-thesis-template/issues/77,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABTafvgEPEujUFZgJj-EJWJ0yml9OCBEks5tesoigaJpZM4SszhN
.

Thanks for your fast reply. It worked with your hint and after I set in the config compat to 1.14.

Thank you. I updated the howto at http://latextemplates.github.io/scientific-thesis-template/overleaf.html and set pgfplot compatibility level to 1.14 (see https://github.com/latextemplates/scientific-thesis-template/commit/11a4ee03732b8eefd264f7e7ddb65ab36bd499be).

Quick fix: use pdflatex. There should be a setting somewhere.

How do I do that?


Get Distribution List in AAD user table

AAD user table is not showing groups and especially Distribution Lists. There is no mention of this limitation in the documentation.
Is it an upcoming feature?

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

ID: bc2e3627-c28e-9baa-61f6-6353b52f81a4
Version Independent ID: bc2e3627-c28e-9baa-61f6-6353b52f81a4
Content: Azure Active Directory user (AADUser) table (Microsoft Dataverse) - Power Apps
Content Source: powerapps-docs/developer/data-platform/aaduser-entity.md
Service: powerapps
Sub-service: dataverse-developer
GitHub Login: @NHelgren
Microsoft Alias: nhelgren

Thanks for your comment, @Papa-Cho. This issue has been assigned to the doc author for review.

Updated #close


IGNITE-1794 Added support of Hibernate 5.1.2.Final

IGNITE-1794 | Resolved
closing PR, feel free to reopen if needed


[AMLII-1521] Add new YYYY/MM/DD HH:MM:SS automultiline pattern

What does this PR do?
Adds an additional pattern (YYYY/MM/DD HH:MM:SS) to the formatsToTry in the auto_multi_line handler

Motivation
Previous logs of this format were not parsed by the existing patterns.

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes
Emit multi-line logs that start with the pattern and verify that auto_multi_line_detection is working properly.
Example log creation script below:
import argparse
import logging
import random
from time import sleep

parser = argparse.ArgumentParser(description='Random Multiline logger.')
parser.add_argument('--log-file', dest='log_filename', default="/tmp/random.log", help='Set logger to output to a logfile rather than stout')

timestamp_format = '%Y/%m/%d %H:%M:%S'

args = parser.parse_args()

logging.basicConfig(filename=args.log_filename, format='%(asctime)s %(message)s', level=logging.DEBUG, datefmt=timestamp_format)

toggle = False
while True:
    if toggle:
        logging.debug('This is a debug log that shows a log that can be ignored.')
    else:
        logging.error('An error is \nusually an exception that \nhas been caught and not handled.')
    toggle = not toggle
    sleep(random.uniform(0, 1))

/merge


add : add Medium TopBar

change Topbar beacuse Staff Screen TobBar not matched
Issue

close #702

Overview (Required)

change LargeTobBar into MediumTobBar

Links

https://github.com/DroidKaigi/conference-app-2024/issues/702

Screenshot (Optional if screenshot test is present or unrelated to UI)

Before
After

Movie (Optional)

Before
After

Thank you for your pull request!
We have many screens like this. I'd like to maintain consistency here. It might be challenging, but could you take a look?

Okay. I try it!

Thanks!

@takahirom
i fix it

@choi-woo-sung, could you please check the failing tests? 🙏

@choi-woo-sung, 실패한 테스트를 확인해 주시겠어요? 🙏

ok sorry..

i fix it !!


[BUG] stream: Setting timeout to float does not set connect timeout in 0.6.0b9

Describe the bug
A clear and concise description of what the bug is.
When using stream mode and pass a float to the timeout parameter, it only sets the read timeout and not connect timeout (CURL_OPT_CONNECTTIMEOUT_MS).
Previously in 0.5.10 it set the connect timeout and not read timeout (read timeout was addressed in https://github.com/yifeikong/curl_cffi/commit/c5f840c538c623361c80f2dce40d3c620afb3b13).
Per requests timeout handling, which curl_cffi appears to be following:
https://requests.readthedocs.io/en/latest/user/advanced/#timeouts

If you specify a single value for the timeout, like this:
r = requests.get('https://github.com', timeout=5)
The timeout value will be applied to both the connect and the read timeouts. Specify a tuple if you would like to set the values separately:
r = requests.get('https://github.com', timeout=(3.05, 27))

https://github.com/yifeikong/curl_cffi/blob/bf563184065e13860ee7fa9e89c7e6fbfcbff619/curl_cffi/requests/session.py#L345-L363
0.5.10: https://github.com/yifeikong/curl_cffi/blob/bb7ceba1e1bb046c0b9f53e68b3e7892f7bfa017/curl_cffi/requests/session.py#L312-L327
See last line - it sets CONNECTTIMEOUT for stream
To Reproduce
def test_stream_connect_timeout():
    s = requests.Session()
    with pytest.raises(requests.RequestsError) as e:
        # hangs for curl default CONNECTTIMEOUT
        s.get("http://<IP_ADDRESS>", stream=True, timeout=1.0)

Expected behavior
A clear and concise description of what you expected to happen.
Both read and connect timeout should be set to the float value passed to timeout in stream mode (with a tuple used to specify each individually).
Versions

OS: linux
curl_cffi==0.6.0b9
pip freeze dump

annotated-types==0.6.0
anyio==4.2.0
async-generator==1.10
attrs==23.2.0
autoflake==1.4
black==22.8.0
certifi==2024.2.2
cffi==1.16.0
click==8.1.7
coverage==6.4.1
cryptography==38.0.3
curl_cffi==0.6.0b9
fastapi==0.109.0
flake8==6.0.0
flake8-bugbear==22.7.1
flake8-pie==0.15.0
h11==0.14.0
httpcore==0.16.3
httpx==0.23.1
idna==3.6
iniconfig==2.0.0
isort==5.10.1
mccabe==0.7.0
mypy==0.971
mypy-extensions==1.0.0
outcome==1.3.0.post0
packaging==23.2
pathspec==0.12.1
platformdirs==4.2.0
pluggy==1.4.0
proxy.py==2.4.3
py==1.11.0
pycodestyle==2.10.0
pycparser==2.21
pydantic==2.6.0
pydantic_core==2.16.1
pyflakes==3.0.1
pytest==7.1.2
pytest-asyncio==0.19.0
pytest-trio==0.7.0
python-multipart==0.0.6
rfc3986==1.5.0
ruff==0.1.14
sniffio==1.3.0
sortedcontainers==2.4.0
starlette==0.35.1
tomli==2.0.1
trio==0.21.0
trio-typing==0.7.0
trustme==0.9.0
types-certifi==2<IP_ADDRESS>
typing_extensions==4.9.0
uvicorn==0.18.3
websockets==11.0.3

Additional context

Which session are you using? async or sync?
If using async session, which loop implementation are you using?

sync

Things were messed up a little bit, I will add it back.

Fixed in 0.6.0


drag/drop meshes into viewport

The new drag/drop features are brilliant! Would be great if you could also drag/drop a .msh file from the filesystem into the 3d viewport or the scene tree(where it would automatically create a new meshinstance node). Would make populating a 3d world much quicker then having to manually make new mesh instances each time.

This could be done for meshes, scenes, etc. But what would the logic be for the "depth" of where this is placed? If dragged over another mesh I can imagine that the collision point can be taken into account, but what if this is done over nothing?

Good question! I would tend to do this in a top down orthographic view to quickly populate a scene. Was envisaging dragging from the browser to the top down viewport and having the mesh be placed where the cursor is in xz space and 0 on the y axis. Not sure how this could work with a non-orthographic view though?
I like your idea of the collision point being taken into account...similar to how primitives are added in 3dsmax. Another idea is to a use a null or other pointer object to be used for the new co-ordinates similar to how the 3d cursor is used in Blender. This 3d pointer object could be defined and moved around as needed.
Even if the new co-ordinates for each new instance were just to default to the origin(0,0,0) then it would still be a useful addition. Drag from the browser to the viewport origin and then move from there. This is still quicker than creating a mesh instance node manually each time for every new object.

Not critical for the upcoming 2.1, so moving to the next milestone.

Just to be sure, this still needs to be implemented in 3.0+?

@akien-mga this issue can now be closed due to d3cb8d1

@fracteed you can close it.

@djrm ...I am not sure how to do this?

I think it's next to the Comment button? :b

close it now.

@HummusSamurai ...hehe, now I see it...doh :)


Domain name for site hosting docs expired

The Berkeley Analytics site is down - currently there is a GoDaddy splash page instead. Any chance the site could be renewed or better yet the docs could be hosted on rtd?

I tried github pages: https://kwgoodman.github.io/bottleneck-doc
Any know how to recover the sphinx theme?

Formatting fixed. Bottleneck docs are now at https://kwgoodman.github.io/bottleneck-doc
Thanks for the report @delgadom


[FIX] source_slippage should default to zero

A SendMax value is calculated using source_slippage, but that is an
optional parameter.

Typical client error:

{
   "success": false,
   "error_type": "transaction",
   "error": "plus() not a number: undefined"
}

LGTM

Coverage remained the same at 86.13% when pulling 2ff5c62b7a990a7b8b3a42dd757e17b60a6493e8 on lumberj:fix/source-slippage into 2323be8b959e1beeefc44a6e612724465ba5be7a on ripple:develop.

LGTM


⚠ ZV800.com has degraded performance

In f41f7f0, ZV800.com (https://www.zv800.com//) experienced degraded performance:

HTTP code: 200
Response time: 1778 ms

Resolved: ZV800.com performance has improved in 0175437 after 26 minutes.


Add Flow-GAN

Hey, I added Flow-GAN.
Since it was too difficult to decide where to put it (considering lexicographic order), I issued vim's :sort i, which swapped around some other lines as well. I hope you don't mind.
Btw, as a bonus, the .tsv table (as we discussed #10) is also included in this PR.
Best regards, Lukas

Thanks for the PR! Regarding the lines getting swapped, it's OK. They will now be in a strict alphabetical order. :)
Also, the table is super useful addition 👍


Move from php-cs-fixer v1 to php-cs-fixer v2

For anyone interested:

all the available style rules are described here

the default Symfony style rules are enabled. with the exceptions reported in the .php-cs.dist file

👍


Move this to Astropy project?

We no longer have a maintainer for this at STScI. Since this is used heavily by Astropy, why not?
c/c @perrygreenfield @pv @astrofrog

Is this used by astropy more than other projects though? What about just making a dedicated asv organization?

I don't think asv is at the moment closely associated with a specific
existing project.
So if it has to move, I think it either should be in a new github org,
or one of the lead devs adopts it as a personal project. A new org
sounds easiest ("asv" is taken, but "asv-dev" is free).

What about airspeed-velocity as the org name?

👍 to its own org

Project moved to a separate org.

Thank you for handling this, @pv.


Darksiders II Deathinitive Edition Resolution Problem Regression

The game suffers from this error every time I initialize it, test it with DXVK 1.5.4 and it works without problems, I have tried compiling the last commit and the problem persists.
I also tried version 1.5.5 and I have the same problem.
I found that starting from this commit causes resolution problems
commit:
[d3d9] Don't expose formats with alpha as adapter formats
https://github.com/doitsujin/dxvk/commit/cf6142e78225373809286765d681d447e5f7bf68

This should be fixed in master now.