Apple TV errors filling up logs

Home Assistant release (hass --version): 0.40.2
Python release (python3 --version): 3.4.2
Component/platform: Apple TV
Description of problem: I don't want to add Apple TV to HA, but it is detected by discovery. The problem then is that the logs are full of ATV exceptions. If ATV is not configured, these error messages should be suppressed.
cc: @postlund
17-03-24 22:34:30 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/home/hass/.homeassistant/deps/aiohttp/web_server.py", line 62, in handle_request
    resp = yield from self._handler(request)
  File "/home/hass/.homeassistant/deps/aiohttp/web.py", line 270, in _handle
    resp = yield from handler(request)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/http/ban.py", line 58, in ban_middleware_handler
    return (yield from handler(request))
  File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro
    res = yield from res
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/http/__init__.py", line 417, in handle
    result = yield from result
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/media_player/__init__.py", line 924, in get
    data, content_type = yield from player.async_get_media_image()
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/media_player/apple_tv.py", line 227, in async_get_media_image
    return (yield from self._atv.metadata.artwork()), 'image/png'
  File "/home/hass/.homeassistant/deps/pyatv/internal/apple_tv.py", line 64, in artwork
    art = yield from self.daap.get(_ARTWORK_CMD, daap_data=False)
  File "/home/hass/.homeassistant/deps/pyatv/daap.py", line 135, in get
    return (yield from self._do(_get_request, is_daap=daap_data))
  File "/home/hass/.homeassistant/deps/pyatv/daap.py", line 168, in _do
    action, False, is_login=is_login, is_daap=is_daap))
  File "/home/hass/.homeassistant/deps/pyatv/daap.py", line 171, in _do
    'failed to login: ' + str(status))
pyatv.exceptions.AuthenticationError: failed to login: 400
17-03-24 22:35:00 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/home/hass/.homeassistant/deps/aiohttp/web_server.py", line 62, in handle_request
    resp = yield from self._handler(request)
  File "/home/hass/.homeassistant/deps/aiohttp/web.py", line 270, in _handle
    resp = yield from handler(request)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/http/ban.py", line 58, in ban_middleware_handler
    return (yield from handler(request))
  File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro
    res = yield from res
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/http/__init__.py", line 417, in handle
    result = yield from result
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/media_player/__init__.py", line 924, in get
    data, content_type = yield from player.async_get_media_image()
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/media_player/apple_tv.py", line 227, in async_get_media_image
    return (yield from self._atv.metadata.artwork()), 'image/png'
  File "/home/hass/.homeassistant/deps/pyatv/internal/apple_tv.py", line 64, in artwork
    art = yield from self.daap.get(_ARTWORK_CMD, daap_data=False)
  File "/home/hass/.homeassistant/deps/pyatv/daap.py", line 135, in get
    return (yield from self._do(_get_request, is_daap=daap_data))
  File "/home/hass/.homeassistant/deps/pyatv/daap.py", line 168, in _do
    action, False, is_login=is_login, is_daap=is_daap))
  File "/home/hass/.homeassistant/deps/pyatv/daap.py", line 171, in _do
    'failed to login: ' + str(status))
pyatv.exceptions.AuthenticationError: failed to login: 400

Expected: Don't fill up logs if the component is not configured.

I'm having another problem related with Apple TV, it gets automatically turned on (and so does my TV) when I execute HA and go to the web ui o.O

These "400"-errors it something I yet have to understand why they are happening. They are still a mystery to me I'm afraid.
Your problem, @jcastro, however is known. See this PR https://github.com/home-assistant/home-assistant/pull/5962.

@postlund I was thinking that discovery detects the ATV and tries to configure it. However, given that it is not configured (due to missing hsgid), it gives the 400 errors.

@arsaboo The discovery will autodiscover your device if you have Home Sharing enabled. In this case it will figure out hsgid by itself, so you don't have to care about it (it's called login_id now, too). But for some reason it usually works for a while and then ends up giving these errors. Then it recovers and starts all over again.
If you don't want to autodiscover it, just add apple_tv to ignoreunder discovery:.

I do have Home Sharing enabled. BTW, those errors go away after I add the login_id. Let me know if I can help you in debugging the error.

@jcastro Yeah, the turning on of the appletv is maddening. Gonna have to turn off some features for now..

Any solutions for this?


Buliding the Astrobee API with Ubuntu 20.04

The Astrobee ROS instructions for building the ROS packages recommend Ubuntu 20.04. However, the Astrobee Android API build instructions indicate that users need to install ros-kinetic-rosjava in order to build the ff_msgs jar, which cannot be installed properly on Ubuntu 20.04 (or possibly 18.04).
When using Ubuntu 20.04 I can only install ROS Noetic, so I tried to install ros-kinetic-rosjava from source from this repo found using the ROS Wiki Source Installation Instructions. When I try to build ff_msgs using the command make ff_msgs_generate_messages_java_gradle, I get the following output:
ERROR: the following packages/stacks could not have their rosdep keys resolved to system dependencies:
rosjava_messages: Cannot locate rosdep definition for [world_canvas_msgs]
genjava: No definition of [python-catkin-pkg] for OS version [focal]
The error output indicates that the issue is caused by dependencies that have changed between the two ROS versions. The Astrobee ROS instructions indicate that the robot hardware on ISS currently runs Ubuntu 16.04, which is supported by ROS Kinetic. I am currently trying Ubuntu 16.04 to see if that works.

Our approach to addressing this issue with other users so far has been to provide/generate the necessary JAR files (built with Ubuntu 16) and use kinetic on Android while keeping the simulator on Ubuntu 20 (noetic).
Of course, this might not work for all use cases (and it's inconvenient) so we are looking into other options as well.
Documentation is lagging behind but we are working on it, so we appreciate your feedback.

I would add that we have an example on how to generate these jar files with docker on Ubuntu 20.04 in https://github.com/nasa/isaac/blob/master/scripts/docker/build_apk.Dockerfile and it is part of the isaac CI in https://github.com/nasa/isaac/blob/master/.github/workflows/apk.yaml (meaning it runs every time someone does a commit).
I would also point out that in 18.04 I only built the jars and the apk compiled natively, but in 20.04 I had to put the entire flow inside the Docker image. (https://github.com/nasa/isaac/blob/v0.2.5/scripts/docker/build_msgs_jar.Dockerfile and https://github.com/nasa/isaac/blob/v0.2.5/.github/workflows/apk.yaml)

We believe Ruben fixed this.


Pre commit

@sandeepkulange Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


All links to Github are broken on website

Link to Windows installation instructions does not work.  Link to Github issues does not work.  Are there instructions for installing on Windows anywhere?

Thank you, I see that GitHub blocks links inside s frame indeed.
You can use this link while I fix this : https://tissuumaps.github.io/TissUUmaps-docs/docs/intro/installation.html

Fixed now on the webpage also: https://tissuumaps.github.io/installation/


Permission error in IE11

Sharing causes a console error in IE11 - Error in v-on handler: "Error: Permission denied"
This can be observed by visiting this fiddle in IE11 http://jsfiddle.net/2b5fzrj9/1/embedded/result clicking the facebook link and opening javascript console. The window opens, but with console error seen in the below screenshot.

This appears to be caused by assigning window.open to this.popup.window  in https://github.com/nicolasbeauvais/vue-social-sharing/blob/master/src/social-sharing.js#L217. Assigning to a variable instead fixes the issue, Example fiddle here http://jsfiddle.net/2b5fzrj9/2/embedded/result.
As you are not using this.popup.window outside of openSharer, the workaround I have is to assign to a local variable, I will add this to a PR.

I closed the issue as the pull request is merged.
Feel free to re-open the issue if needed!


Bugfix/fix animated arrow

Move the set state call to an earlier position so that is does not clash with the animation.
Otherwise there are some edge cases, where the icon does not match with the opened/close state of the dropdown.
This was also a problem for #5. So only moving the iconRef did not help

Any updates on this one? :)

Sorry for late release :)
Thank you so much for contribution tho @mariomurrent-softwaresolutions
Release 0.4.1

No worries :) Everything is fine.
Finally I can remove my patch-package.
Thx for review and merging


Add NgenApplication so that default (vsn.exe.config) is not used...

Description
...when attempting to ngen testhost(.x86).exe.  Some dependent
assemblies not normally loaded in VS will fail to load during ngen
install when vsn.exe.config is used.
Related issue
https://devdiv.visualstudio.com/DevDiv/_workitems?id=571813&_a=edit

FYI @cltshivash @abhishekkumawat23


Fix sandbox exit monitor

Wire up sandbox controller to sandbox exit monitor. This will make sure that pod sandbox status is up to date and kubelet will not retry stopping sandbox.
Signed-off-by: Maksym Pavlenko<EMAIL_ADDRESS>

/test pull-containerd-sandboxed-node-e2e


remove unused packages in vendor/manifest

Signed-off-by: WangQilin<EMAIL_ADDRESS>

Coverage increased (+0.07%) to 62.581% when pulling 82892a842a3d34ca3b34194a7062e9b2682038a3 on wangkirin:optimize-dependency into 910c4aece3ab13705a79a1b00a7c625352569e9f on ServiceComb:master.


#78: module-info should export package 'com.sun.xml.fastinfoset.dom'

Fixes #78

additional changes:

complete module descriptor for main artifact + utilities
updated configurations for copyright, spotbugs, coverage
fixed javadoc generation errors in main artifacts


Consider exposing FullProgramABI either by making it public or taking it out to fuel-abi-types

I started some work on main argument encoding for scripts with forc-run which makes use of FullProgramABI abstraction sdk defines(https://github.com/FuelLabs/sway/pull/4603). Either I need to expose it via making it public or I can take it out to our shared crate: https://github.com/FuelLabs/fuel-abi-types. I am opening this issue to discuss which approach would be preferable for the sdk.

My opinion is that it's a good candidate for an extraction into the fuel-abi-types crate, since it's an abstraction that makes sense outside of the SDK and is essential to Fuel itself. @FuelLabs/sdk-rust wdyt?

abi-types seems like a logical destination - I agree.


Symbolic links in sftp are not loading

I can confirm that this is the case on iPadOS 16 as well…

Hi,
For projects in which data and code are stored in different paths, it is a critical foundational feature, and we hope the bug can be fixed soon.

Hi,
For projects in which data and code are stored in different paths, it is a critical foundational feature, and we hope the bug can be fixed soon.

Thanks for the heads up. I will work on this next week.

This should be fixed in the latest TestFlight build. See https://github.com/thebaselab/NMSSH/commit/68d4728ba2e284c587fa62bbfb349b5d43a05109.

TODO: Also resolve symlink directories

TODO: Also resolve symlink directories

Fixed in https://github.com/thebaselab/codeapp/commit/c527110d515c30df44d582b28ea405eb119e1a7d. This feature will be released on App Store shortly in 1.5.2.


Travis builds are failing

The Travis build is failing after raising the PR with below error message
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">=10.15.1"

Docusaurus have issue working on node 10.9.0 or below  .

Travis Failing Issue solved by upgrading the node version (10.9.0 --> 10.16.0)


Hide toolbars

Is it possible to hide both toolbars? Left and bottom...

FYI I'm bumping this up in priority. Should get to it soon-ish.

Fixed by the new toolbarPosition: 'hidden' option (currently in master).


Newrelic is adding 66k of script to each page

Description
I'm using the Newrelic gem on many of my projects and I've just noticed (with surprise) that each page has way bigger size than what I was expecting. Checking it out, it seems that the Newrelic gem it's inlining its script at the top of the head which causes the page size to increase by 66k, that's multiple times the total size of the page itself. In other
Expected Behavior
It'd be great if it wasn't doing that, but instead doing the minimum required and then loading an external script async.
I might need to remove it otherwise to lower the page size.
Steps to Reproduce
Include the Newrelic gem, open any page, you can see the Newrelic script at the top that includes a lot of code
Your Environment
Include as many relevant details about your environment as possible including the running version of the Ruby agent, the Ruby version being used and any other relevant environment information
Newrelic 9.0.0
Rails 3.2.1
Standard Newrelic generated config
For Maintainers Only or Hero Triaging this bug
Suggested Priority (P1,P2,P3,P4,P5):
Suggested T-Shirt size (S, M, L, XL, Unknown):

Hi @xdmx! Thanks for reaching out.
The script is New Relic's Browser Agent.
There isn't a current path to load the browser agent asynchronously, but this would make a great feature request. Feature requests are now accepted through issues.newrelic.com. Please point the request to the Browser agent team.
In the meantime, there are smaller builds of the browser agent available. In the Application Settings section of the Browser app in NR1, there is a spot to select which build of the agent to get. Both the Pro and Lite builds of the agent are smaller. Lite currently has a size of 34kb. You'll have to restart your agent (usually done by restarting your app) to make the changes take effect.
https://user-images.githubusercontent.com/87386821/224834050-89bff24d-47ea-4724-9331-afa73ecb7802.mov
By default, the Ruby agent automatically injects the browser agent into applications. If you'd prefer the agent not inject browser agent, you can update your newrelic.yml to:
browser_monitoring.auto_instrument: false


Add variables to better customize plugin directories

Still loads all plugins from the plugins directory as before

But now PLUGIN_DIR will set that directory instead of being used to specify an individual plugin
This is the directory I envision being used for distributing code-server with plugins or where plugins would be placed for running instances of code-server in production by users

PLUGIN_DIRS can be used to set multiple individual plugins if you don't want to move them into a single directory

Really only intended for development

Lemme know if we wanna change this up, this is just based off the VS Code plugin structure (except they use command line flags and not environment variables).

Default plugin dir should actually use XDG I think. Thoughts? Having it inside code-server is weird, except maybe for built-in plugins. So maybe we should load both.

I went ahead and did that.

Should note this isn't backwards compatible with the previous method so maybe it would be better keep maintain the old PLUGIN_DIR behavior and use different variables for the new stuff (or use command line flags instead).

CS_PLUGIN_PATH is a much better name.


Port telemetry to use dedicated project

Analytics to allow roadmap prioritization based on usage data.

I added a new instrumentation key to the repository secret section.


AFP 338 replace glob with jobsite

Used jobsite here instead of get-workspaces is because the former had options to filter, find, expand etc which we can use to filter packages based on docs.config.js

I am so confused that deploy succeeded but install failed.
Also, the deployed website here shows no packages at all.

This PR is being parked atm since the usage of chdir seems to be not fully appropriate and solution would be jobsite package needs to support passing in a working directory. The ideal scenario is jobsite using get-workspaces.


throw ObjectGenerationException when a Randomizer can not be created …

…(fixes #131)

Coverage increased (+0.1%) to 93.052% when pulling 04a4f4ea4eb630b215bba34c741f82e90e11c12d on PascalSchumacher:ObjectGenerationException into e534c0009e55585083e3379d995faf1afb0221a5 on benas:master.

No comments.. That's great! Thanks


Update dependency for aiomqtt from asyncio-mqtt

Update to use the renamed aiomqtt, now asyncio-mqtt and remove depreciated filtered_messages call.
Fixes #107
References:

https://sbtinstruments.github.io/aiomqtt/migration-guide-v2.html
https://eclipse.dev/paho/files/paho.mqtt.python/html/migrations.html

I fixed the asyncio-mqtt in my fork: https://github.com/ftrueck/bluetti_mqtt/
In case someone wants to use it I try to keep it uptodate as much as my time allows.


teuthology/misc: do not fail when pull_directory(a_dir_does_not_exist)

there is chance that /var/log/ceph (and other directories) is not
created when cephadm fails, but we always try to collect /var/log/ceph
by tar the directory on the test node and transfer it back for archiving
it. when we fail to do so, an exception is thrown, and this exception is
in turn logged as the cause of the failure instead of the one which
fails the test.
in this change, all tarfile.TarErrors are caught in
misc.pull_directory(), as normally, we don't consider it a fatal
failure when misc.pull_directory() fails because of tar.
two types of failures are caught here. we could use tarfile.TarError
here, as both of them inherit from this class, but it'd be easier to
understand to be explicit. as only these two types are expected.
Signed-off-by: Kefu Chai<EMAIL_ADDRESS>

see also http://pulpito.ceph.com/nojha-2020-05-19_00:53:41-rados-wip-revert-34894-distro-basic-smithi/5068077/

makes sense. will ignore these Error on the caller side.


Weighted validators (BFT-408, BFT-424)

What ❔
Add weights to the validator set and change the consensus threshold rules to require >80% of weight.
Why ❔
We need for the L1 contracts to only accept blocks that were built by our node (which is the single leader). We can give more weight to our node, so that a QC isn't valid unless it signs. In turn this will be useful in the future

Last commits fix BFT-424. This is ready for a new review


[AutoDiff] Reproducer for BatchNorm compiler crasher #2

Refer to https://github.com/apple/swift/pull/41437 for the relevant discussion. This test passes when rebased onto main. The previous pull request had to be closed because of a technical error.

CC: @BradLarson

@swift-ci Please test.

Transcribing context here for reference: SR-15849 has been impacting our internal code for a few months. Philip was able to isolate a single-file reproducer in this test case, which we had been using to diagnose the issue.
In the process of doing so, the issue stopped reproducing in top-of-tree Swift. My speculation is that PR #41294 is what ended up preventing the assertion failure we had been seeing, but it's still being investigated. To prevent against a recurrence of the issue, it seemed like a good idea to put in place a regression test based in the reproducer Philip isolated from the Swift for TensorFlow codebase. This is that test.

Thanks @BradLarson for the ping.


fix test and method for Number / Complex

I noticed one of the tests for the Complex class wasn't using the appropriate operator so I fixed it. I then fixed a bug in  Number / Complex

Thanks!


Tooltip colors don't use the color pattern option

Example:
{
            bindto: '#chart',
            data: {
                columns: columns,
                type: 'bar'
            },
            axis: {
                rotated: true,
                x: {
                    type: 'category',
                    categories: categories
                },
                y: {
                    max: 90
                }
            },
            color: {
                  pattern: ['red', 'green', 'blue']
            }
        }

The tooltip color boxes will be blank instead of using the pattern. data.color is not an option here because I need a pattern that works on arbitrary data points.

Looks like I need to prepend the colors with # for the legend to work, but that did not break the bars colors. Closing.


bump kubernetes to 1.21.5 for CVE-2021-25741

Bump kubernetes to 1.21.5 to avoid CVE-2021-25741. See https://groups.google.com/g/kubernetes-announce/c/-e9OlTcED5E for more information from the Kubernetes project.

Please link your related planet PR for tracking purposes. :smile:


UnixPB: Don't validate certs for wget-ting the git source

ref: https://ci.adoptopenjdk.net/view/Tooling/job/VagrantPlaybookCheck/OS=SUSE12,label=vagrant/658/console
SUSE has been consistently failing due to the SSL cert not being able to be validated. Unfortunately, attempting to install the python modules suggested failed due to not being able to find them, therefore I opted for not validating_certs - as we have the checksum in place, (AFAIK) there's no added security risk of this.

Closing as a new PR will be made when a solution is found.


Mopidy fails to load extensions with additional dependencies

Mopidy fails to load extensions that have additional dependencies. mopidy-spotify fails because it depends on pyspotify:
mopidy[2776]: INFO     Disabled extension spotify: Dependency The 'pyspotify<1.999,>=1.9' distribution was not found and is required by the application not found

I guess this is because only the extension path is added to PYTHONPATH and not the path of any sub-dependencies, but I don't know much about Python.

I suggest using http://nixos.org/nixpkgs/manual/#ssec-python-build-env

I got mopidy-spotify working at home a couple days ago but haven't made a PR for the changes yet. I'll do that tonight (~8hrs from now)

@spwhit That is great to hear :+1:

@jgillich Just ran into this problem by rebasing onto a more recent nixpkgs, I see what you're talking about now. I'm working around it for now by adding the extra dependencies to mopidy's package, but I'll look into @domenkozar 's suggestion if I find time..


Update Dagster code to use Pythonic Config

User Story

As a data engineer I want to stay up to date with Dagster's API design

Description/Context
Dagster recently updated their APIs to support Pydantic-based config models and are promoting them in place of the previous dictionary objects passed into decorators. This is a more robust and easy to use/understand interface that we would like to adopt. They have created a migration guide here
Acceptance Criteria

[ ] All Dagster code uses the new Pythonic config interface

Updated all ops and jobs, working on updating resources.

Are there PRs that we can link in here?


🏗 Add optional title to carousel

Add the ability to provide a title to the carousel component which will be displayed on top of the carousel.

Closed by #681


Problem when trying to test on your pretrain model

Hi dvornikita,
First of all thanks for this amazing work! :)
I have some problems when I trying to test the pretrain BlitzNet512 model.
The following message appears and I don't know how to deal with it.. maybe you have some solution for me :)
"InvalidArgumentError (see above for traceback): Assign requires shapes of both tensors to match. lhs shape= [3,3,512,64] rhs shape= [1,1,512,64]"

can you please send the command you are running?

Sure :) Thanks for the quick response!ץ
python test.py --run_name=BlitzNet512_COCO+VOC07+12 --dataset=voc07 --split=test --image_size=512 --detect --segment --ckpt=1
Without the --segment flag everything works well

Try to specify the flag --seg_filter_size=3.
I guess I have slightly different architectures for different datasets so the default configurations don't always work. Need to re-upload the right ones.

Works great! Thank you :)


change ui to arc-green dark mode does not work on 1.11

Gitea version (or commit ref): 1.11.4
Git version:
Operating system: Linux
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ x] Yes (provide example URL)
[ ] No
[x ] Not relevant

Log gist:

Description
in app.in set:
[ui]
DEFAULT_THEME = arc-green

then restart gitea and use browser to access its pages, theme not changed.
Screenshots
same color as original default "gitea" theme, as nothing changes in color.

Changing the default will not affect users who already have a default theme. You will need to change your users default theme.

Thanks! I did not even know I can choose default theme in user settings. Just did it and it works.


RangeError: Invalid array length

Describe the bug
It is normal in the development environment, and an error is reported in the production environment. There is no problem with the same code being built by vue-cli5, so this should not be a problem of vuejs/core
Steps to reproduce
pnpm preview

open page
http://localhost:4173/vite-vue3-admin/#/demos/form/basic
Reproduction
https://github.com/renqian805/vite-vue3-admin/tree/main
System Info
System:
    OS: macOS 12.5.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 1.22 GB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.15.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 8.11.0 - /usr/local/bin/npm
  Browsers:
    Safari: 15.6.1
  npmPackages:
    @vitejs/plugin-legacy: ~2.0.1 => 2.0.1
    @vitejs/plugin-vue: ~3.0.3 => 3.0.3
    @vitejs/plugin-vue-jsx: ~2.0.1 => 2.0.1
    vite: ~3.1.0-beta.2 => 3.1.0-beta.2

Used Package Manager
pnpm
Logs
runtime-core.esm-bundler.js:226 RangeError: Invalid array length
at Ke (runtime-core.esm-bundler.js:5923:43)
at Re (runtime-core.esm-bundler.js:5777:21)
at Ae (runtime-core.esm-bundler.js:5457:17)
at pe (runtime-core.esm-bundler.js:5051:17)
at Ke (runtime-core.esm-bundler.js:5834:17)
at Re (runtime-core.esm-bundler.js:5777:21)
at Ae (runtime-core.esm-bundler.js:5457:17)
at pe (runtime-core.esm-bundler.js:5051:17)
at Ke (runtime-core.esm-bundler.js:5834:17)
at Re (runtime-core.esm-bundler.js:5777:21)
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Please provide a minimal reproduction. It's hard to debug an entire project with many dependencies.


Force Player to start exe at timeline-position 0 after loading

Describe the bug
Sometimes an exe starts a few seconds after timeline-position 0. This leads to cut off-problems when the soundtrack starts at 0.
Please complete the following information):

OS: win
Version: 3.2.2

Expected behavior
Start the exe at second 0 after loading.

i had a similar problem .. but at the other end the player was cutting off at the end 11 seconds early .. i think @pixtur is adressing this in player in general and has solved the problem for the next update of Standalone!

I believe this should be fixed in the upcoming release.


Building instructions

Hello, first of all, I want to thank you for open sourcing this awesome idea.
I am looking forward to contribute and extend this repo, but I cant get the storybook script to run properly:
after "npm start" I get:

Error: Can't resolve styled-bootstrap/utils

Am I missing something obvious ? I already install all dependencies. and "lerna ls" throws me:

styled-bootstrap/alert      v0.1.6-6
styled-bootstrap/button     v0.1.6-6
styled-bootstrap/close-icon v0.1.6-6
styled-bootstrap/utils      v0.1.6-3

Hi @juanitoddd, I didn't notice about this issue before, just to let you know, I'm rebuilding all the components
Soon we will have a new/better version of this library

is this still the case?

@adamchenwei this problem could be considered as deprecated


execution/timeouts (PR F)

The timeout is checked on lookup of a pending transaction. If the configured timeout is passed then the future is moved to the timeout state via a message.
Resolves #293.

This looks good. I left a few comments, of which the only one I consider somewhat important is this. We can create an issue for that and merge this.


UI/Data: Indicator (at taxonomy tab) whether a species is extinct or alive and a possibility to download only alive species table.

Use the IUCN categories for recent species.

Checklist
Delete
0%
Need to discuss about this further
Add an item
Activity
Show details
Write a comment…
Kari Lintulaakso Jun 4, 2019 12:52 PM (edited)
The IUCN categories can be found from here https://portals.iucn.org/library/sites/library/files/documents/RL-2001-001-2nd.pdf
Extinct, EX
Extinct in the Wild, EW
Critically Endangered, CR
Endangered, EN
Vulnerable, VU
Near Threatened, NT
Least Concern, LC
Data Deficient, DD
Not Evaluated, NE
ASM Mammal Diversity Database ASM Mammal Diversity Database
Lists 6,399 extant, 96 recently extinct mammals
MSW3 lists 5416 species https://www.departments.bucknell.edu/biology/resources/msw3/ with a field "Extinct?"
extant, recently extinct, fossil


The CPU memory usage of 100,000 circles is too high.

When drawing 100,000 or a million circles. How Do I Reduce the CPU Memory Usage?

If you're asking this type of question, please provide a concrete examples of what you're trying to do. At the margins of performance, details matter a lot. This question is not worth answering without those details.
Also, there are a few past issues that resemble this question. Please do a little digging first through old issues. I'm sure you'll find some useful information.

如果您问这种类型的问题，请提供您要尝试做的具体示例。在性能方面，细节至关重要。没有这些细节，这个问题就不值得回答。
另外，过去有一些与此问题类似的问题。请先对旧问题进行一些深入研究。我相信您会找到一些有用的信息。

I create a geometry object, use geometry.drawShape(shap, fillStyle, lineStyle, matrix) to add circles or line segments, and graphics = new PIXI.Graphics(geometry). Then, convert it to a sprite image and add it to the PIXI object. The CPU usage reaches 1 GB.

It should work. Please provide a demo.

Doesn't should.
Because this will allocate a a lot of VRAM If enabled cacheAsBitmap on all of 100k circles separately.
Then, any case, case of 100k circles is not solved naive because 1 circle can allocate buffer at 100+vertices (100 * (2 + 2 + 4 + 1) * 4 = 3600 bytes).
100k circles already allocated a 360mb in vram.
Welcome!

Please close this thread if you're done @Tangkkk. 🙏


Async control flow

There's a couple of places where we rely on async/await logic without a need to it, given these functions are either synchronous or rely on callbacks for control flow. Specifically:
fs.writeFile
fs.writeFile is a callback based mehod meaning awaiting on it will not produce any effect. An alternative if we want to use async/await would be to use util.promisify
https://github.com/iamanishroy/netlify-plugin-js-obfuscator/blob/ca7d29c28849b0066756dc0e6f43c2dae1a3ca6b/index.js#L26
However if we want to rely on its callback interface then we need correctly handle its control flow as well as its error:
https://github.com/iamanishroy/netlify-plugin-js-obfuscator/blob/main/index.js#L29
A possible solution using async/await and util.promisify:
const fs = require("fs");
const util = require("util");
const readFile = util.promisify(fs.readFile)
const writeFile = util.promisify(fs.writeFile)

(...)

// Reading the files -> obfuscating the code -> Writing the obfuscated code
const obfuscateCode = async (filePath, custom) => {
  const file = await readFile(filePath, "utf8");
  const obfuscationResult = JavaScriptObfuscator.obfuscate(file, {
    compact: custom[0],
    controlFlowFlattening: true,
    controlFlowFlatteningThreshold: 1,
    numbersToExpressions: custom[1],
    simplify: custom[2],
    shuffleStringArray: custom[3],
    splitStrings: custom[4],
  });
  await writeFile(
    filePath,
    obfuscationResult.getObfuscatedCode(),
  );
};

Note: Since Node 10 there's also the ability to use the fs.promises however, we still need to support Node 8.
JavaScriptObfuscator.obfuscate
Reading through its docs doesn't seem like the javascript-obfuscator is an asynchronous function. As such, await won't be necessary here:
https://github.com/iamanishroy/netlify-plugin-js-obfuscator/blob/ca7d29c28849b0066756dc0e6f43c2dae1a3ca6b/index.js#L17

Thanks for the fix 👍

Thanks for the fix 👍


Getting message: VBox(children=(HTML(value=''), IntProgress(value=0)))

I ran this code:
import time
from time import sleep

def check_url(url):
    sleep(0.1)

urls = range(100)

for url in log_progress(urls, every=1):
    check_url(url)

for index in log_progress(range(100), every=1):
#     print("testing")
    sleep(0.1)

and it resulted in:
VBox(children=(HTML(value=''), IntProgress(value=0)))

Am I missing something?
Running on Windows 10:
anaconda                  custom           py36h363777c_0
anaconda-client           1.7.2                    py36_0
anaconda-navigator        1.9.7                    py36_0
anaconda-project          0.8.2                    py36_0

Are you running in JupyterLab or JupyterNotebook?
I seem to have the same problem in Lab but no problem in Notebook. Unsure of solution however.

I am running Jupyter Lab.
On Mon, Oct 14, 2019 at 16:03 Ian Fraser<EMAIL_ADDRESS>wrote:

Are you running in JupyterLab or JupyterNotebook?
I seem to have the same problem in Lab but no problem in Notebook. Unsure
of solution however.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kuk/log-progress/issues/19?email_source=notifications&email_token=AEEPRHREL7AJLU5UJ3GJEQLQOT3FJA5CNFSM4HPJ7AM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBG4HBI#issuecomment-541967237,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEEPRHTBMJS2RGPCPRMGPQTQOT3FJANCNFSM4HPJ7AMQ
.

dupe of #14 i think.


Error building Expo app on iOS with "sharp" package

Build/Submit details page URL
https://expo.dev/accounts/garrettg/projects/blogcast/builds/17a58368-c5a0-415a-9e98-e56c389b06c6
Summary
I am trying to build my Expo app for iOS using the eas build --platform ios command, but I am encountering an error related to the "sharp" package. The error message I receive is:
[stderr]
error /Users/expo/workingdir/build/node_modules/sharp: Command failed.
[stderr]
Exit code: 1
[stderr]
Command: (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)
[stderr]
Arguments:
[stderr]
Directory: /Users/expo/workingdir/build/node_modules/sharp
[stderr]
Output:
[stderr]
sharp: Detected globally-installed libvips v8.13.3
[stderr]
sharp: Building from source via node-gyp
[stderr]
gyp info it worked if it ends with ok
[stderr]
gyp info using<EMAIL_ADDRESS>[stderr]
gyp info using<EMAIL_ADDRESS>| darwin | arm64
[stderr]
gyp info find Python using Python version 3.9.6 found at "/Applications/Xcode.app/Contents/Developer/usr/bin/python3"
[stderr]
gyp http GET https://nodejs.org/download/release/v14.19.1/node-v14.19.1-headers.tar.gz
[stderr]
gyp http 200 https://nodejs.org/download/release/v14.19.1/node-v14.19.1-headers.tar.gz
[stderr]
gyp http GET https://nodejs.org/download/release/v14.19.1/SHASUMS256.txt
[stderr]
gyp http 200 https://nodejs.org/download/release/v14.19.1/SHASUMS256.txt
[stderr]
gyp info spawn /Applications/Xcode.app/Contents/Developer/usr/bin/python3
[stderr]
gyp info spawn args [
[stderr]
gyp info spawn args   '/Users/expo/.nvm/versions/node/v14.19.1/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
[stderr]
gyp info spawn args   'binding.gyp',
[stderr]
gyp info spawn args   '-f',
[stderr]
gyp info spawn args   'make',
[stderr]
gyp info spawn args   '-I',
[stderr]
gyp info spawn args   '/Users/expo/workingdir/build/node_modules/sharp/build/config.gypi',
[stderr]
gyp info spawn args   '-I',
[stderr]
gyp info spawn args   '/Users/expo/.nvm/versions/node/v14.19.1/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
[stderr]
gyp info spawn args   '-I',
[stderr]
gyp info spawn args   '/Users/expo/Library/Caches/node-gyp/14.19.1/include/node/common.gypi',
[stderr]
gyp info spawn args   '-Dlibrary=shared_library',
[stderr]
gyp info spawn args   '-Dvisibility=default',
[stderr]
gyp info spawn args   '-Dnode_root_dir=/Users/expo/Library/Caches/node-gyp/14.19.1',
[stderr]
gyp info spawn args   '-Dnode_gyp_dir=/Users/expo/.nvm/versions/node/v14.19.1/lib/node_modules/npm/node_modules/node-gyp',
[stderr]
gyp info spawn args   '-Dnode_lib_file=/Users/expo/Library/Caches/node-gyp/14.19.1/<(target_arch)/node.lib',
[stderr]
gyp info spawn args   '-Dmodule_root_dir=/Users/expo/workingdir/build/node_modules/sharp',
[stderr]
gyp info spawn args   '-Dnode_engine=v8',
[stderr]
gyp info spawn args   '--depth=.',
[stderr]
gyp info spawn args   '--no-parallel',
[stderr]
gyp info spawn args   '--generator-output',
[stderr]
gyp info spawn args   'build',
[stderr]
gyp info spawn args   '-Goutput_dir=.'
[stderr]
gyp info spawn args ]
[stderr]
gyp info spawn make
[stderr]
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
[stderr]
  TOUCH Release/obj.target/libvips-cpp.stamp
[stderr]
  CC(target) Release/obj.target/nothing/node_modules/node-addon-api/nothing.o
[stderr]
  LIBTOOL-STATIC Release/nothing.a
[stderr]
env: python: No such file or directory
[stderr]
make: *** [Release/nothing.a] Error 127
[stderr]
gyp ERR! build error
[stderr]
gyp ERR! stack Error: `make` failed with exit code: 2
[stderr]
gyp ERR! stack     at ChildProcess.onExit (/Users/expo/.nvm/versions/node/v14.19.1/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
[stderr]
gyp ERR! stack     at ChildProcess.emit (events.js:400:28)
[stderr]
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:282:12)
[stderr]
gyp ERR! System Darwin 21.6.0
[stderr]
gyp ERR! command "/Users/expo/.nvm/versions/node/v14.19.1/bin/node" "/Users/expo/.nvm/versions/node/v14.19.1/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
[stderr]
gyp ERR! cwd /Users/expo/workingdir/build/node_modules/sharp
[stderr]
gyp ERR! node -v v14.19.1
[stderr]
gyp ERR! node-gyp -v v5.1.0
[stderr]
gyp ERR! not ok
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
yarn exited with non-zero code: 1

Managed or bare?
bare
Environment
expo-env-info 1.0.5 environment info:
System:
OS: macOS 13.2
Shell: 3.0.2 - /usr/local/bin/fish
Binaries:
Node: 16.18.1 - /usr/local/bin/node
Yarn: 1.22.5 - ~/.yarn/bin/yarn
npm: 9.4.0 - /usr/local/bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
Android SDK:
API Levels: 30, 31, 32, 33
Build Tools: 29.0.2, 30.0.2, 30.0.3, 31.0.0, 33.0.0, 33.0.1
System Images: android-30 | Google Play Intel x86 Atom, android-33 | Google APIs ARM 64 v8a, android-33 | Google APIs Intel x86 Atom_64
IDEs:
Android Studio: 2022.1 AI-221.6008.13.2211.9514443
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
Expo Workflow: bare
Error output
No response
Reproducible demo or steps to reproduce from a blank project

Create an expo project with the sharp module installed in a separate yarn workspace package
Run eas build and choose to use the new m1 build

env: python: No such file or directory

sharp does not provide prebuilds for m1, so it tries to build from the source. Python should be installed on M1, but image you are using is on macos version that already removed python2, so you might try on the older one.
Or if you do not use sharp in mobile apps set up your project in a way that does not install dependencies. e.g you can keep everything in the same repo without using workspaces.

@mikealche did you figure out a solve for this issue?  Facing a similar issue now

Is there any solution to this? It doesn't seem to happen on every build, but it wastes a lot of builds just trying to figure out the pattern, if there is one.
Previously we never had any trouble with including Sharp in our monorepo.

Add following script in package.json
"scripts": {
    "eas-build-pre-install": "brew remove vips",
    // ...rest
}


[base-ui][docs] Add the planned Alert Dialog page

[x] I have followed (at least) the PR section of the contributing guide.

As the title says — that's one of the components we're considering for the v1 release that isn't yet on the docs marked as planned.

Yep it's too soon currently imo. We haven't discussed the API for the dialog role components yet, so we haven't "planned" anything here.


Make the parser recover from more errors

Motivation

We care far more about preserving a method def if it existed before a parse
error was introduced, than about tracking the actual contents of the method
bodies (if we see the same method / class structure, we can take the fast
path).
Test plan

See included automated tests.
I tested this on pay-server too, but pay-server is a particularly bad test for
this change: every single file / method / line in pay-server currently parses,
and this change only affects files that don't parse. I added some of the tests
that are top-of-mind for me right now, but I'm only so confident that we won't
need to revert this because it doesn't actually give us the fast path results
that we're looking for.

@jez a test failed

@DarkDimius chatted with nroman and he said that the autogen classlist failure is harmless.

I am very excited about this change.
If I understand it correctly, it's:

Reporting the same parse error.
Not throwing away the rest of the nodes.

...right? And it doesn't cause issues with things like x.\nend because this isn't a hack that changes what is/is not parseable?

If I understand it correctly, it's:

I'd say it's more like "now the parser is able to recover from errors even when there isn't a full stmt following the parse error".

But yes, this doesn't change the grammar, so it reports the same errors.


support GeoJSON data with other projections than WGS84

Proj4Leaflet adds support for GeoJSON in any projection, while Leaflet by itself assumes GeoJSON to always use WGS84 as its projection. The CRS is derived from the name property of a crs defined directly on the GeoJSON object per the spec. The relevant Proj4 definition should be defined directly via proj4.defs before loading the GeoJSON object. If it is not, Proj4leaflet will throw an error. Moreover, this PR adds ability to support widely used EPSG:3857 out of the box. For definition of custom projection it is possible to use any *.js files and add them to resource.config file.

Thanks @drnextgis. It would be great if you could add some details about this on the README at some point so other users are aware of it.


Strange issues on latest version

I'm getting some pretty cryptic errors when trying to build on the latest version.
[11:08:36]: Could not find action or lane 'options'. Check out the README for more details: https://github.com/KrauseFx/fastlane

+------+-------------------------------------+-------------+
|                     fastlane summary                     |
+------+-------------------------------------+-------------+
| Step | Action                              | Time (in s) |
+------+-------------------------------------+-------------+
| 1    | Verifying required fastlane version | 0           |
| 2    | default_platform                    | 0           |
| 3    | clean_build_artifacts               | 0           |
| 4    | xcode_select                        | 0           |
| 5    | sigh                                | 10          |
| 6    | git_branch                          | 0           |
| 7    | get_build_number                    | 3           |
| 8    | increment_build_number              | 0           |
| 9    | generate_changelog                  | 0           |
| 10   | gym                                 | 111         |
+------+-------------------------------------+-------------+

[11:08:36]: fastlane finished with errors
/Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/runner.rb:117:in `try_switch_to_lane': Could not find action or lane 'options'. Check out the README for more details: https://github.com/KrauseFx/fastlane (RuntimeError)
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/fast_file.rb:129:in `rescue in method_missing'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/fast_file.rb:124:in `method_missing'
	from (eval):136:in `block (3 levels) in parse'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/runner.rb:65:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/runner.rb:65:in `block in execute'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/runner.rb:61:in `chdir'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/runner.rb:61:in `rescue in execute'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/runner.rb:45:in `execute'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/lane_manager.rb:43:in `cruise_lane'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/command_line_handler.rb:31:in `handle'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/bin/fastlane:35:in `block (2 levels) in run'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:153:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/runner.rb:428:in `run_active_command'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/runner.rb:68:in `run!'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/delegates.rb:15:in `run!'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/bin/fastlane:136:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/bin/fastlane:142:in `<top (required)>'
	from /usr/bin/fastlane:23:in `load'
	from /usr/bin/fastlane:23:in `<main>'

The lane in question is here:
lane :buildUat do |options|

    xcode_select "/Applications/Xcode.app"

    sigh(adhoc: true, app_identifier: "blah.blah")

    # use the UDID of the newly created provisioning profile
    ENV["PROFILE_UDID"] = lane_context[SharedValues::SIGH_UDID]

    branch = git_branch[/(?:.*\/)?([\w-]*)/, 1]
    increment_build_number(build_number: "#{get_build_number}.#{options[:build_number]}-#{branch}")

    generate_changelog(previous_commit: "#{options[:previous_commit]}")

    gym(
      workspace: "App.xcworkspace",
      configuration: "Beta",
      scheme: "App",
      silent: true,
      clean: true
    )

  end

It seems to fail right at the end, it has successfully completed gym, and there are no further instructions.  Any help would be appreciated.

Do you still run into this error? I just tried and it's working fine locally.

Running into same issue when using with gym(use_legacy_build_api: true):
[17:40:45]: Could not find action or lane 'tests_file_path'. Check out the README for more details: https://github.com/KrauseFx/fastlane
+------+-------------------------------------+-------------+
|                     fastlane summary                     |
+------+-------------------------------------+-------------+
| Step | Action                              | Time (in s) |
+------+-------------------------------------+-------------+
| 1    | Verifying required fastlane version | 0           |
| 2    | default_platform                    | 0           |
| 3    | cocoapods                           | 16          |
| 4    | increment_build_number              | 1           |
| 5    | sigh                                | 12          |
| 6    | gym                                 | 119         |
+------+-------------------------------------+-------------+
[17:40:46]: fastlane finished with errors
😨  An error occured. Please enable crash reports using fastlane enable_crash_reporting
👍  This makes resolving issues much easier and helps improving fastlane
🔒  The reports might contain personal data, but will be stored securely on getsentry.com
✨  Once crash reporting is enabled, you have much cleaner output when something goes wrong
🙊  More information about privacy: https://github.com/KrauseFx/fastlane/releases/tag/1.33.3
/Users/povi/.rvm/gems/ruby-2.2.3/gems/fastlane-1.37.0/lib/fastlane/runner.rb:117:in try_switch_to_lane': Could not find action or lane 'tests_file_path'. Check out the README for more details: https://github.com/KrauseFx/fastlane (RuntimeError) 	from /Users/povi/.rvm/gems/ruby-2.2.3/gems/fastlane-1.37.0/lib/fastlane/fast_file.rb:141:in rescue in method_missing'
from /Users/povi/.rvm/gems/ruby-2.2.3/gems/fastlane-1.37.0/lib/fastlane/fast_file.rb:136:in method_missing' 	from Fastfile:46:in block (2 levels) in parsing_binding'
from /Users/povi/.rvm/gems/ruby-2.2.3/gems/fastlane-1.37.0/lib/fastlane/lane.rb:36:in call' 	from /Users/povi/.rvm/gems/ruby-2.2.3/gems/fastlane-1.37.0/lib/fastlane/lane.rb:36:in call'
from /Users/povi/.rvm/gems/ruby-2.2.3/gems/fastlane-1.37.0/lib/fastlane/runner.rb:51:in block in execute' 	from /Users/povi/.rvm/gems/ruby-2.2.3/gems/fastlane-1.37.0/lib/fastlane/runner.rb:46:in chdir'
from /Users/povi/.rvm/gems/ruby-2.2.3/gems/fastlane-1.37.0/lib/fastlane/runner.rb:46:in execute' 	from /Users/povi/.rvm/gems/ruby-2.2.3/gems/fastlane-1.37.0/lib/fastlane/lane_manager.rb:43:in cruise_lane'
from /Users/povi/.rvm/gems/ruby-2.2.3/gems/fastlane-1.37.0/lib/fastlane/command_line_handler.rb:31:in handle' 	from /Users/povi/.rvm/gems/ruby-2.2.3/gems/fastlane-1.37.0/bin/fastlane:35:in block (2 levels) in run'
from /Users/povi/.rvm/gems/ruby-2.2.3/gems/commander-4.3.5/lib/commander/command.rb:178:in call' 	from /Users/povi/.rvm/gems/ruby-2.2.3/gems/commander-4.3.5/lib/commander/command.rb:178:in call'
from /Users/povi/.rvm/gems/ruby-2.2.3/gems/commander-4.3.5/lib/commander/command.rb:153:in run' 	from /Users/povi/.rvm/gems/ruby-2.2.3/gems/commander-4.3.5/lib/commander/runner.rb:428:in run_active_command'
from /Users/povi/.rvm/gems/ruby-2.2.3/gems/commander-4.3.5/lib/commander/runner.rb:68:in run!' 	from /Users/povi/.rvm/gems/ruby-2.2.3/gems/commander-4.3.5/lib/commander/delegates.rb:15:in run!'
from /Users/povi/.rvm/gems/ruby-2.2.3/gems/fastlane-1.37.0/bin/fastlane:152:in run' 	from /Users/povi/.rvm/gems/ruby-2.2.3/gems/fastlane-1.37.0/bin/fastlane:158:in <top (required)>'
from /Users/povi/.rvm/gems/ruby-2.2.3/bin/fastlane:23:in load' 	from /Users/povi/.rvm/gems/ruby-2.2.3/bin/fastlane:23:in '
from /Users/povi/.rvm/gems/ruby-2.2.3/bin/ruby_executable_hooks:15:in eval' 	from /Users/povi/.rvm/gems/ruby-2.2.3/bin/ruby_executable_hooks:15:in '

@povi Please share your complete Fastfile, you have an error there.

Going to close this issue for now as there has not been any activity in some time. Please feel free to reopen it if you are running into the same issue on up-to-date versions! :rabbit:


⚠ Bofrost.be has degraded performance

In e0af161, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1607 ms

Resolved: Bofrost.be performance has improved in 19debfb after 6 minutes.


⚠ Samsung has degraded performance

In 08ae5a0, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 3128 ms

Resolved: Samsung performance has improved in fed6868.


add toggle button for input group

Description
Using Toggle buttons in an input group

Motivation & Context

Type of changes

[N/A] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[N/A] Refactoring (non-breaking change)
[N/A] Breaking change (fix or feature that would change existing functionality)

Checklist

[x] I have read the contributing guidelines
[x] My code follows the code style of the project (using npm run lint)
[x] My change introduces changes to the documentation
[x] I have updated the documentation accordingly
[x] I have added tests to cover my changes
[x] All new and existing tests passed

Live previews

https://deploy-preview-39076--twbs-bootstrap.netlify.app/docs/5.3/forms/input-group/#toggle-buttons

Related issues

Going to pass on this too, thanks though!


Replacing the gnomAD data sets with mine

Hi -
I downloaded the gnomAD browser from the github and launched it on my desktop.
How do I replace the browser data with my own?

The Query component is where the browser's front end connects to the gnomAD API to fetch data. You could modify that component (and/or components that use Query) to fetch data from your own web service.


Pre-commit hook go vet correction

Required for all non-trivial PRs

[x] Rebased/mergable
[x] Tests pass
[x] CHANGELOG.md updated
[x] Sign CLA (if not already signed)

Go has deprecated invoking the vet tool through the go tool command, which flags an error in the pre-commit hook. This is a slight correction to use the go vet invocation instead.

@mattnotmitt Thanks for this.  Sorry that it has taken so long to get to this!


Issue-1059: Drop the org.apache.tomcat:catalina:6.0.53 dependency from the strongbox-event-api

Fixes #1059.
@sbespalov
@fuss86
Is this solution okay, or not? I decided to remove everything what is connected with catalina because if the there are no libraries related to it, maybe there is no sense to hold it. I ran integration tests, and everything built without any issues. Service from strongbox-distribution is also working and I was able to manage the strongbox without any other issues. If that solution is incorrect, just let me know how should it looks like and then I will improve this code.

Great! Thanks for reviewing and thanks, @adavid9 ! :)


riscv64: Further optimize constants loading

Follow-up of #7131
In some cases we can avoid an addi by using lui and shifting less

Do you have a idea of what causes the failure ? I don't understand why the sign bit is set in these tests.
A simple function loading the constant outputs the right code:
function %f() -> f64 {
block0:
  v0 = f64const 0xf64.0
  return v0
}

; VCode:
; block0:
;   lui a0,-518695
;   slli a2,a0,31
;   fmv.d.x fa0,a2
;   ret
;
; Disassembled:
; block0: ; offset 0x0
;   lui a0, 0x815d9
;   slli a2, a0, 0x1f
;   fmv.d.x fa0, a2
;   ret

I think this might be because lui for RISC-V 64bit sign extends the immediate after placing it in the register.
This is the expression that lui computes:
x[rd] = sext(immediate[31:12] << 12)

The immediate has the MSB set, and since we don't fully shift immediate all the way to the top we are observing the sign extension.

Oh I missed that ! Thanks a lot !

Note: this does not work for constants like 0xf7fff00000000000 but that would significantly complicate the code.


Vector-scalar multiplication and division

Operations to multiply and divide a vector and a scalar are missing. For a vector var A: [Double] and a scalar var s: Double I want to be able to do:

let B: [Double] = A * s
let B: [Double] = s * A
let B: [Double] = A / s

Fixed with https://github.com/aleph7/Surge/commit/b53f1288ae766ed6906e6eb52b5af1a1d256febd and https://github.com/aleph7/Surge/commit/f8b170e1098599219f883abe51d6bca93202941b


hostfw tests flake workaround

Reopening #25199 as the issue continuous to plague our CI.
For reviewers: With this change, we want to further confirm suspicions relating to https://github.com/cilium/cilium/issues/15455 that these flakes are caused by this issue.
Currently, this issue is by-far the largest cause of failures in our CI, what we're interested in seeing if this significantly affects that.

/test


Fairland RMIC06

I make u new device Fairland RMIC06 and work fine in home assistant, is possible add to repository?
https://gist.github.com/nedvedhonza/c91afe5d45a0be5c23dcc4ac691216b3

Hello any progress here?


[CodeCompletion] Don't print '_' external parameter name in filterName

in override completions. _ as a filterName is not something clients expect. This align with function call completions.
But, unlike call-site completions, we do need _ in the source text. So instead of mark the chunk "annotation", make an exception in printCodeCompletionResultFilterName().
rdar://91892610

@swift-ci Please smoke test


Upload existing OpenSCD architecture documentation

As a (potentail) developer
I would like to know the exsisting architecure decissions
So I can understand why choices are made and base my decision on these choices or challenge them.
Acceptance criteria:
Upload existing documentation of @ca-d to a docs folder in this repository.

General architecture can uploaded to .github

This is the original architecture proposal (not exactly what was implemented) from summer of 2020, converted to markdown format. Please feel free to use this as you wish.
Markdown source
> Any comment is welcome!!!

Architecture Proposal
=====================

The Web Platform
----------------

The web platform is the most ubiquitous and battle-tested technology available for user interface implementation today. Because its user interfaces may be declared using dialects of `XML`, it runs in browser environments containing the world's most reliable and optimized [`XML` parser and `DOM` API](https://developer.mozilla.org/en-US/docs/Web/API/DOMParser) implementations.

We propose to use this readily available technology throughout the next version of the `OpenSCD` `XML` editor.

Proposed Architecture
---------------------

### Overview

This is a cartoon representation of the proposed architecture of each individual [WebComponent](https://developer.mozilla.org/en-US/docs/Web/Web_Components) representing a part (e.g. editor pane, editable element, user interface element, plugin etc.) of the `OpenSCD` app, which is at the top level itself a WebComponent making use of (i.e. rendering as parts and delegating updates to) its WebComponent children:

    .          ----- action : Event <----
             /                            \
            |                              |
            v                              |
    update(action) : void      render(model) : HTML Node
            |                              ^
            |                              |
             \                            /
               ---> model : XML Node ----

The proposed architecture is inspired by `Flux`, the `Elm` architecture, `cycle.js`'s "Model, View, Intent" architecture, and reactive user interface design in general (`React`, `RxJS` etc.) . Of these, it is closest to `Elm`'s "Model, View, Update" functional architecture, the major caveat being our effectful manipulation (`update`) of the mutable state (`model`) encapsulated in WebComponent properties and attributes instead of functionally producing new immutable state as a function of old immutable state and incoming action.

> The view (represented above by `render,` a function of the `model`) represents the "query" part of **CQRS**, presenting relevant parts of the model to the user without modifying anything in the model.
>
> The `update` function above represents the "command" part of **CQRS**, modifying the model in response to user triggered events without modifying anything about the view.

`OpenSCD` would achieve modularity and encapsulation through pervasive use of [`LitElement`](https://lit-element.polymer-project.org/) WebComponents. Each WebComponent consists of an entire `model` -> `render` -> `action` -> `update` cycle -- importing, containing, and using other web components as needed (`1 to n` "has-a" relationships). The top level container element is the `<open-scd>` `LitElement`.

### Model

We store the model of each WebComponent entirely in the component's properties and attributes.

Our top level (`<open-scd>`) model is at its core just a regular **`XMLDocument`** we get from the browser's `DOMParser` Web API by parsing the `SCL` file to be edited upon opening it, decorated with a bit of extra user interface state like:

*   Which editing actions have taken place so far (`undo`/`redo` **history**) ?
*   Which view of the editor are we showing at the moment (**active tab**) ?
*   Which error, warning, and info messages have been shown and seen thus far (**error log**) ?
*   Which XML node is currently being edited (**focus**) ?

Models of individual editor components (e.g. editor panes, modules, plugins) similarly consist chiefly of collections of `XML` `Node`s representing parts of the parent element's model.

### View (`render`)

The view of each WebComponent is defined in its `LitElement` `render()` method depending exclusively on the element's attributes and properties (what would otherwise be function parameters in an Elm-like `FRP` approach). It gets called automatically whenever relevant attributes or properties change and returns the updated view in the form of pure `HTML` and `CSS`.

### Action

A user action is a semantic event representing some user intention (e.g. "change bay name") that is emitted by the WebComponent upon any one of a set of browser events (e.g. `click`, `keydown`, `touch`) and handled by the element's `update` event handler (or selection of event handlers).

### Update

Each user action `Event` is handled by an event handler appropriate to the event type (e.g. `onnamechange` handling `NameChangeEvent`s). These event handlers defined on each WebComponent with the corresponding faculty are represented in above architecture cartoon by the `update` function.

Helpful patterns
----------------

These patterns promoted by the team behind `LitElement` should prove helpful in development:

*   _view as a function of data_: Keep a `currentView` property in the top level component keeping track of the view currently being rendered.
*   _lazy loading of components_: Use a `lazyLoad` directive for importing both "internal" editor modules (e.g. views) and "external" plugins dynamically when needed.
*   _[pending state protocol](https://github.com/justinfagnani/pending-state-protocol)_: Use "pending state" events in long-running component updates to allow the app to notify the user of progress.
*   _CachedTask helper_: Cache the results of async work (like loading a `WASM` schema validator) to enable synchronous rendering of components upon completion.
*   _data down, events up_: The top-level app Component is responsible for data mutation (command transactor) and receives commands as events from its children. Resultant data is automatically communicated downward to descendants.

Any comment is welcome!!!

Architecture Proposal
The Web Platform
The web platform is the most ubiquitous and battle-tested technology available for user interface implementation today. Because its user interfaces may be declared using dialects of XML, it runs in browser environments containing the world's most reliable and optimized XML parser and DOM API implementations.
We propose to use this readily available technology throughout the next version of the OpenSCD XML editor.
Proposed Architecture
Overview
This is a cartoon representation of the proposed architecture of each individual WebComponent representing a part (e.g. editor pane, editable element, user interface element, plugin etc.) of the OpenSCD app, which is at the top level itself a WebComponent making use of (i.e. rendering as parts and delegating updates to) its WebComponent children:
.          ----- action : Event <----
         /                            \
        |                              |
        v                              |
update(action) : void      render(model) : HTML Node
        |                              ^
        |                              |
         \                            /
           ---> model : XML Node ----

The proposed architecture is inspired by Flux, the Elm architecture, cycle.js's "Model, View, Intent" architecture, and reactive user interface design in general (React, RxJS etc.) . Of these, it is closest to Elm's "Model, View, Update" functional architecture, the major caveat being our effectful manipulation (update) of the mutable state (model) encapsulated in WebComponent properties and attributes instead of functionally producing new immutable state as a function of old immutable state and incoming action.

The view (represented above by render, a function of the model) represents the "query" part of CQRS, presenting relevant parts of the model to the user without modifying anything in the model.
The update function above represents the "command" part of CQRS, modifying the model in response to user triggered events without modifying anything about the view.

OpenSCD would achieve modularity and encapsulation through pervasive use of LitElement WebComponents. Each WebComponent consists of an entire model -> render -> action -> update cycle -- importing, containing, and using other web components as needed (1 to n "has-a" relationships). The top level container element is the <open-scd> LitElement.
Model
We store the model of each WebComponent entirely in the component's properties and attributes.
Our top level (<open-scd>) model is at its core just a regular XMLDocument we get from the browser's DOMParser Web API by parsing the SCL file to be edited upon opening it, decorated with a bit of extra user interface state like:

Which editing actions have taken place so far (undo/redo history) ?
Which view of the editor are we showing at the moment (active tab) ?
Which error, warning, and info messages have been shown and seen thus far (error log) ?
Which XML node is currently being edited (focus) ?

Models of individual editor components (e.g. editor panes, modules, plugins) similarly consist chiefly of collections of XML Nodes representing parts of the parent element's model.
View (render)
The view of each WebComponent is defined in its LitElement render() method depending exclusively on the element's attributes and properties (what would otherwise be function parameters in an Elm-like FRP approach). It gets called automatically whenever relevant attributes or properties change and returns the updated view in the form of pure HTML and CSS.
Action
A user action is a semantic event representing some user intention (e.g. "change bay name") that is emitted by the WebComponent upon any one of a set of browser events (e.g. click, keydown, touch) and handled by the element's update event handler (or selection of event handlers).
Update
Each user action Event is handled by an event handler appropriate to the event type (e.g. onnamechange handling NameChangeEvents). These event handlers defined on each WebComponent with the corresponding faculty are represented in above architecture cartoon by the update function.
Helpful patterns
These patterns promoted by the team behind LitElement should prove helpful in development:

view as a function of data: Keep a currentView property in the top level component keeping track of the view currently being rendered.
lazy loading of components: Use a lazyLoad directive for importing both "internal" editor modules (e.g. views) and "external" plugins dynamically when needed.
pending state protocol: Use "pending state" events in long-running component updates to allow the app to notify the user of progress.
CachedTask helper: Cache the results of async work (like loading a WASM schema validator) to enable synchronous rendering of components upon completion.
data down, events up: The top-level app Component is responsible for data mutation (command transactor) and receives commands as events from its children. Resultant data is automatically communicated downward to descendants.

Thanks @ca-d!


Set build var to default and add script for advanced users to change them

Currently we have defined
BUILDDIR = "/workspaces/r-dev-env/build/"
TOP_SRCDIR = "/workspaces/r-dev-env/svn/"

with the idea that the basic workflow for building R should use $BUILDDIR/r-devel and $TOP_SRCDIR/r-devel and different versions of R could be built with $BUILDDIR/$LABEL and $TOP_SRCDIR/$LABEL, where $LABEL replaces "r-devel". A disadvantage of this approach is that it deviates from the approach documented in the R Dev Guide and the R-admin manual.  Also, we can no longer simply refer to "the build directory" and "the source directory", which complicates documentation.
So I think we should change the defaults to
BUILDDIR = "/workspaces/r-dev-env/build/r-devel"
TOP_SRCDIR = "/workspaces/r-dev-env/svn/r-devel"

Then the basic workflow for building R can use these environment variables directly, sticking to the objective of keeping things simple for new contributors.
To build a different version of R a user just need to redefine these variables, which could be facilitated with a script. This should have a "barebones" interface, so that it is quick to switch between multiple working copies of R. It could work as follows:
$set_build_var r-devel-raw
The build variables have been set to:
BUILDDIR = "/workspaces/r-dev-env/build/r-devel-raw"
TOP_SRCDIR = "/workspaces/r-dev-env/svn/r-devel-raw"

Just testing the GitPod (via gitpod.io/#https://github.com/r-devel/r-dev-env/tree/update/gitpod-config). Annoyingly, GitPod uses the directory "workspace" rather than "workspaces", so for the GitPod we need
BUILDDIR = "/workspace/r-dev-env/build/r-devel"
TOP_SRCDIR = "/workspace/r-dev-env/svn/r-devel"

still - another advantage of using environment variables for this, as the docs stay the same.

Not sure if this complicates things but it may be possible to define a gitpod Dockerfile and yml files to install onto Gitpod?:
https://www.gitpod.io/docs/configure/workspaces/workspace-image#using-a-custom-dockerfile
Given the conversation above, it may be easier for documentation to have a check for /workspace/ or workspaces and reset the environment variables?

I wonder if it is possible to automatically detect the name of the workspace folder. I just tried local setup from a zip file and by default the zip file is name by the branch (e.g. r-dev-env-main or r-dev-env-devel), so it unzips to a folder of the same name. If you then open that in VSCode, the workspace folder is e.g. /workspaces/r-dev-env-main/. So detecting the workspace name when the environment variables are created could deal with both the Codespaces/GitPod difference and the zip issue.
I think the postCreateCommand will be run in the root of the workspace (i.e. the workspace folder), similarly bash will open there. So you can use $PWD to access the name of the workspace folder and use that in the scripts that set up the the environment variables, VSCode settings, etc.

we had removed .git file from dev container to untrack the source code we checkout using  svn so I think using pwd we might unable to get pwd as /workspaces/r-dev-env-main/.

Not sure if this complicates things but it may be possible to define a gitpod Dockerfile and yml files to install onto Gitpod?: https://www.gitpod.io/docs/configure/workspaces/workspace-image#using-a-custom-dockerfile
Given the conversation above, it may be easier for documentation to have a check for /workspace/ or workspaces and reset the environment variables?

The files are ready but unable to get things working as expected right now.

This issue is fixed for the GitHub codespace. Fixing it in a more general way for GitPod/other situations can be moved to a separate issue.

#158 fixed this for Gitpod and should be general enough to fix for the local setup from a zip file (untested).


mod_location throws a runtime error

mod_location variable (probably just the declaration syntax) throws an "Unhandled Runtime Error"
Steps to reproduce the behavior:

Setup the application on your local machine and start the server on you local machine
Click on one of the categories and you'll be met with the error

Expected behavior
This shouldn't happen. It's just an unhandled eventuality
Screenshots

I already have a fix for this issue, didn't want to ship it out with my last PR without filing it as an issue. @kaf-lamed-beyt just let me know if I should proceed with the implementation. I basically plan to abstract the functionality into a separate function which will be private for now (only accessible within the file), if we find other usecases then we can probably create a module for it.

Thanks for reporting this. Can you try adding a ? before includes?
It's probably because the variable is undefined at first. Could be as a result of network too, not absolutely sure about that. Last time I ran it locally, everything worked fine.
Lemme know what happens when you add ?, then we can proceed 🤲🏽


Deprecate InstrumentationLibrary usages and use InstrumentationScope instead

With PR #87 is merged, it introduces the  InstrumentationScope class that is intended to replace the InstrumentationLibrary class.  We will want to consolidate the existing usages to leverage the InstrumentationScope class.

Internal usage of InstrumentationLibrary has been updated to use InstrumentationScope.


anyio/Trio compatibility

This patch (OK, three of them) adds Trio compatibility, by way of anyio.
It also fixes two minor other issues, in separate patches:

don't use iscoroutinefunction. That prevents wrapping async functions with a sync wrapper, which is perfectly legitimate Python code.
don't compare to False with "==". Either use "not", if None, zero or the empty string should be considered false, or "is" if they should not be. I opted for the latter approach.

I have to admit that I have no idea what I'm doing with the poetry.lock file … reverting that change. Somebody else (who knows their way around poetry …) can remove the dependency on pytest.asyncio; it's no longer needed.

Thank you @smurfix for the PR!
I think all we need to do is let poetry update the lock file with the new dependency. I think we can do it as part of the merge.

Ah, OK, so why do you ship the poetry.lock file in the first place, given that it's autogenerated? IMHO that's generally not a good idea …
The tests fail because it couldn't find anyio 4.1, which is strange because that has been out for some time by now.


"attrs" passes through "as" prop

Environment
System:

OS: macOS 10.14
CPU: x64 Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz
Memory: 2.14 GB / 16.00 GB
Shell: 3.2.57 - /bin/bash

Binaries:

Node: 10.11.0 - ~/.nvm/versions/node/v10.11.0/bin/node
npm: 6.4.1 - ~/.nvm/versions/node/v10.11.0/bin/npm

npmPackages:

@types/styled-components: ^4.0.1 => 4.0.1
babel-plugin-styled-components: ^1.8.0 => 1.8.0
styled-components: ^4.0.2 => 4.0.2

Reproduction
https://codesandbox.io/s/0xvjx5qq30
Steps to reproduce
Just see the console
Expected Behavior
"as" prop shouldn't be passed

Dup of #2131

@probablyup I don't really understand how it is duplicate. This problem is about different behavior of "as" prop with and without attrs

Same root problem
On Tue, Oct 23, 2018, 8:08 AM Dimitrii Rybakov<EMAIL_ADDRESS>wrote:

@probablyup https://github.com/probablyup I don't really understand how
it is duplicate. This problem is about different behavior of "as" prop with
and without attrs
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/styled-components/styled-components/issues/2135#issuecomment-432238046,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAiy1mc8907psTv9FtWITyRHmwbnUHYyks5unxTdgaJpZM4Xy-ai
.


Daemon mode

I run waifu2x.booru.pics and recently traffic been ramping up very quickly, we thankfully have coded a queue systems with workers allowing 3 threads to be launched at once without overloading our GPU memory, using cuDNN as it has a much smaller memory footprint.
We do not use the webgui from the repo but instead for every image we run a separate waifu2x command to upscale. The problem we have atm is that every time the model has to be loaded into GPU for every request. This leads to high CPU usage as its pretty inefficient.
Is there a way to demonize waifu2x, and keeping its model into memory while accepting requests?

web.lua is a REST API daemon.
You can call it from an external Web GUI or CUI program.
In waifu2x.udp.jp, two web.lua are started as systemd service on different ports(example), and load balancing with nginx(example).

Thanks for your help, and sorry for my late reply. I tried using web.lua but it seems to keep growing into memory, is there a way to limit its vram?

web.lua caches processed images on memory.
You can set the max size with -cache_max option.

But why would it cache images in vram? There is only a very limited amount of vram, why not just store the image on disk? What value do you use for the site?

Previously it was stored on disk, but writing/encoding large images was slow in my use case.

I'm using pci-e SSD's as a primary drive that have very fast write speeds, is it possible to obtain a old version where its still stored on disk instead?

https://github.com/nagadomi/waifu2x/blob/b19ad361230851c98ca0dd290a5203573b1677dc/web.lua
see also https://github.com/nagadomi/waifu2x/commits/master/web.lua
But the main reason is that PNG encoding is slow.
The current version uses snappy compression for cache instead of PNG encoding.

https://developer.nvidia.com/blog/unified-memory-cuda-beginners/
Something like that would allow the image to pushed to host RAM instead of wasting space on GPU, if their example is right, it's as simple as replacing a single function call, but if you rely on old CUDA you'd have to get everything to work on a newer cuda version.


[Feature request] Add max supply cap for cw721

To distinguish a limited NFT collection, we will need a supply cap for the minting process.
In order to allow new created contracts upon this 721 base to achieve variability, it might be useful for us to set this state upon instantiation of the contract.
To add:

max supply attribute in State & InstantiateMsg
error handling & checking in mint function
tests

I agree with this wholeheartedly, will makes PR when I get some bandwidth

up up, im wondering why max supply cap not yet implemented!

imho, this should be added to the extension, not the base.
not all NFT use cases are the 'collectables' we are currently seeing, and we are making the 'generic' cw721 non-generic anymore

gotcha

100% agree, this should not be in base, it should be an extension, possibly in the -plus repo @JakeHartnell was discussing WRT burning

100% agree, this should not be in base, it should be an extension, possibly in the -plus repo @JakeHartnell was discussing WRT burning

Yeah, maybe a cw721-plus repo might be nice. A more fully featured base to extend from. See #25 for context.

max supply seems like

imho, this should be added to the extension, not the base. not all NFT use cases are the 'collectables' we are currently seeing, and we are making the 'generic' cw721 non-generic anymore

it actually should not be part of extension, as the extension are attributes pegged to the individual NFToken. It would not make sense to have NFTokens.
Nonetheless, it is a good point to ensure that the functionality of none collectibles NFT are still held true.
As such, maybe we can consider an max_supply with a type of Option, this way, when the attribute is not in the instantiation request of the contract, we can always by default set the max_supply as 1, resulting in a non-collectible NFT.

When we say extension here, there's two meanings. One, the token-granularity Extension, and one, an extension of cw721-base with different functionality, i.e. -plus which we are discussing. I am arguing for the latter, and I guess like you say the param should probably be at contract level.

my meaning when I said 'extension' was more in the programmatic sense.
My first (naïve probably) approach of building extra functionality into my own contract  was painful, and I had to fork the base contract and modify it.
I would have preferred to just have the ability to add Exec, Query, Init, & Migrate messages and the ability to add fields (like max-supply) without having to hack the base.


Testing PR after machine update

Closing this PR. There is a fix to the unix_socket issue in another PR that was merged: https://github.com/idaholab/civet/pull/548


Update mobile-devices-overview.md

Corrected invalid link in the doc with https://docs.microsoft.com/en-us/sharepoint/administration/mobile-devices-overview

@nenonix @JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@tomresing

@tomresing Any updates in merging this PR? Changes look correct. Thanks


need-titles ending in    /
 - contenteditable strikes again

sometimes need-titles still end in   or
, due to problems with mediumjs / contenteditable.
Related to #1042

duplicate of #1052


Keybase "outdated"

Keybase prompts me with an update window thinking I'm out of date, but it does not seem to recognise my version number.

Command line says this:
PS C:\Users\Sam> keybase version
Client:  6.1.0-20220610133835+1c45eff104
Service: 6.1.0-20220610133835+1c45eff104

Lol windows

Yeah forgot to mention I'm on Windows 11.

Happens also on Win 10.


[admin] Publish

Docs Build status updates of commit 5a27f8d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/concepts/browsers-used-by-office-web-add-ins.md
:white_check_mark:Succeeded
View

docs/design/contextual-tabs.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-errors.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-overview.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-requirement-sets.md
:white_check_mark:Succeeded
View

docs/images/pnp-add-contextual-tabs-to-your-add-in.png
:white_check_mark:Succeeded
View

docs/index.yml
:white_check_mark:Succeeded
View

docs/overview/office-add-in-availability.md
:white_check_mark:Succeeded
View

docs/overview/office-add-in-code-samples.md
:white_check_mark:Succeeded
View

docs/overview/office-add-ins-community-call.md
:white_check_mark:Succeeded
View

docs/overview/patterns-and-practices-overview.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/add-in-commands-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/custom-functions-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/dialog-api-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/identity-api-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/image-coercion-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/open-browser-window-api-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/outlook-api-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/ribbon-api-requirement-sets.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/shared-runtime-requirement-sets.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


odo delete component - show warning that something was not deleted

Show warning when the component was deleted but there are still resources matching labels.
This situation can happen when the devfile was modified and something was removed from it.
It could look like this
$ odo delete component
Searching resources to delete, please wait...
This will delete "devfile-nodejs-deploy" from the namespace "myproj".
 •  The component contains the following resources that will get deleted:
	- Deployment: devfile-nodejs-deploy-app
? Are you sure you want to delete "devfile-nodejs-deploy" and all its resources? (y/N) y
The component "devfile-nodejs-deploy" is successfully deleted from namespace "myproj"

There are still resources left in the cluster that might be belonging to the deleted component.
 - Service: something

If you want to delete those, execute `odo delete component --name devfile-nodejs-deploy`

I don't have any other issue to work on for the rest of the sprint, I can take this up.


Creates new PIXI.Application class

Overview
Setting up a new PIXI scene often requires a few steps: setting up a requestAnimationFrame or Ticker, creating a PIXI.Container and creating the renderer. I would like to improve this experience by creating a very simple API for setting up PIXI, as well as create something that is extendable and object-oriented.
// creates the renderer, root and ticker
const app = new PIXI.Application();

// Add the view to the DOM
document.body.appendChild(app.view);

// ex, add display objects
const graphic = new PIXI.Graphics();
graphic.beginFill(0xff0000).drawRect(0, 0, 100, 100);
app.stage.addChild(graphic);

Documentation
http://pixijs.download/application/docs/PIXI.Application.html
Example
https://jsfiddle.net/9s002r34/

Something about ticker... can you check that shared ticker wont be used in this config?


[Feature request] Auto Update

Hi - first let say say thank you for this great work --- would it be possible to add a auto update function/button?
Kind regards Joerg

Hi @wilderkaiser auto-update is a bit of a tricky one, but possible. Currently it's recommended to upgrade via command-line (pip install --upgrade Mopidy-Spotmop) or by using the (beta) upgrade functionality within the Settings tab.
Have you tried using this Settings tab upgrade functionality?

This issue was moved to jaedb/Iris#14


Open Addresses:  Businesses in Los Angeles

https://data.lacity.org/A-Prosperous-City/Listing-of-Active-Businesses/6rrh-rzua

Thanks for submitting this! It's a great dataset, but not quite what we're looking for on OpenAddresses. We need complete addresses, not just businesses. Don't worry though, I think we already have data for LA.


DO NOT MERGE

:x: Build failed in 2m 28s
Build command:
mvn clean verify -B -e -Daudit -amd -pl core

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

script returned exit code 1

:information_source:  This is an automatic message


OSX gtop not resizing window after node upgrade

Environment

OS: OSX Sierra
Node version: v8.8.1
gtop version: 0.1.5

Description
After node upgrade (from 8.1.2 to 8.8.1) gtop does not automatically adapt to window resizes. Tried in the default OSX terminal app, iTerm, tmux. Same result. The reason I ran into this, was when I installed gtop on another machine with a recent node version. On the machine with the old node version, the app automatically adjusted to window resizes. After upgrading node also on this machine, it´s not working anymore.
Since I am not a node expert, I´m having a hard time figuring out which module might have caused this change.

I had the problem of resizing too. However, I am not sure whether it was also caused by a node upgrade.
While trying to fix the problem I added a line here, which seems to have fixed the issue:
process.on('SIGWINCH', function() {});

I won't open a pull request for this since I have no idea how or why this fix worked, but it would be nice if someone more competent would do so.

@TimothyEarley hey, works like a charm! thx a ton!!!


Can be overloading more intuitive

Summary
Add column for V & X for overloading

 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.:x: baruchiro sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@baruchiro Thanks for contributing and working to help make docs better.
I've reviewed your changes, and I'm not convinced that what you added provides new information or clarity over the text that's in the existing 2nd column.
I'm going to close this PR on that basis.  If I've mis-understood what you're trying to add, write a comment to explain your thinking and I'll help work through what changes would help.
If you find other areas that are unclear, we welcome more contributions.


RLMResults should have an invalidated property

Goals
Need a way to tell if a Results object is invalidated.
http://stackoverflow.com/questions/37201922/how-to-check-for-rlmresults-invalidated
Expected Results
Results should have an invalidated property.
Actual Results
It doesn't.
Realm version: 1.0.2
Xcode version: 7.2.1
iOS/OSX version: 10.11.4
Dependency manager + version: Carthage

@bdash can you give me some general ETA on this? If it's not going to be fixed by the time I ship, I'm going to have a lot of .map { $0 } to do, and I might as well get started.

Results are only ever invalidated if their Realm is, so why not just check Results.realm.invalidated?

@jpsim, that's not sufficient. A Results that depends on a deleted LinkView or a backlinks for a deleted row is also invalidated, but there's no way to detect that case.

When did that change? We made it so that Results that depend on a deleted LinkView are just empty a few versions back, and a change to make it instead be invalid isn't listed in the changelog.

Results::validate_read contains the following check since fb541e16:
if (m_mode == Mode::LinkView && !m_link_view->is_attached())
    throw InvalidatedException();

Ah, I think I wrote that before we made queries on deleted LinkViews not crash, and then failed to update that when merging. I think Mode::LinkView isn't actually used for anything that makes it to the user after the change to expose whether a Query uses the table order, though.
I guess the actual task here is to go through all the scenarios and make sure they're all handled sensibly, and then added Results.invalidated if it turns out to still be needed.

I'll take a crack at doing that.

Also, as far as I can tell invalidated isn't exposed on Realm either? Maybe this is an omission in Swift?

Right you are. Only RLMObject / Object and RLMArray / List can report whether they are invalidated at present.

There are two changes we should make:

Don't treat a Results that depends on a detached link view or table view as invalidated. It should instead be treated as empty.
Add an invalidated property on RLMResults and Results so it's possible to determine whether the object has been invalidated by a call to Realm.invalidate(). This is now the only way to invalidate a Results.


Versioned API, GTFS-RT Alerts

Adds a versioned API (/api/v1/...). Should be 100% identical to the existing API but now at least it's possible for us to start revising it without fear of breaking anything.
Moves the new weather API entirely under /api/v1/...
Adds ability to visualize list of agencies from the web UI
Adds GTFS-RT based alerts API

@aaronbrethorst Cool!  Are there API docs anywhere yet?


[Error]:"No Streams are selected" Occurs in Remote connection of Python [L515]

Required Info

Camera Model
L515

Firmware Version
<IP_ADDRESS>

Operating System & Version
Linux (Ubuntu 18.04) / Windows(10/11)

Kernel Version (Linux Only)
4.9.140-tegra

Platform
NVIDIA Jetson TX2

SDK Version
2.47

Language
python

Issue Description
I have two devices here: 1.Windows Laptop and 2.NVIDIA Jetson TX2. And I want to set Jetson as an rs-server, connecting to my L515 camera, and in Windows Laptop I will use the python code from "https://github.com/IntelRealSense/librealsense/blob/master/wrappers/python/examples/net_viewer.py" to start a remote session.
After I deploy all services on two computers, which is the 2.47 version, the problems come in my python running.

First, I had checked it runs in Jetson TX2 normally, included running official intel viewer locally and remotely and python connection. It's all right.

Running on Viewer locally in TX2

Running Remote Session on Viewer locally in TX2

Running Python Connection locally in TX2

Next, I started the rs-server in the Jetson TX2 and open the intel viewer in the windows Laptop to connect it and its still normal.
Running Python Connection Remotely in Windows

The only problem occurs when I run python code in the terminal, I don't know why it says no streams here and I try to restart the rs-server or close the intel-viewer so as to keep only one device to receive the streams, but it all doest works.
Can you provide some tips here for me?
I had been switched the SDK version from 2.49 to 2.47 depending on one issue, but it seems not a valid method here.

@MartyG-RealSense Thanks for your reply!
But I always keep only one client to receive the streams from the server.  Like close the Viewer and restart the rs-server or even restart all computers such methods to confirm only one client to one server.
So it may not an appropriate solution to this issue here.

Does net_viewer.py print a 'Connected' confirmation message that a network connection to the camera has been successfully made?
https://github.com/IntelRealSense/librealsense/blob/master/wrappers/python/examples/net_viewer.py#L24
I am not familiar with how the net_viewer.py program functions, but I cannot see in the code how it makes a connection to the camera like ssh'ing in the white paper does. I wonder if the program assumes that there is a network connection to the remote camera active already when the script is run.

It printed connected and camera information here which means it has successfully connect to the server. But error occurs when running pipeline.start()
dev = rsnet.net_device(ip)
print('Connected')
print('Using device 0,', dev.get_info(rs.camera_info.name), ' Serial number: ',
      dev.get_info(rs.camera_info.serial_number))
dev.add_to(ctx)
pipeline = rs.pipeline(ctx)
print('Start streaming, press ESC to quit...')
pipeline.start()

I have studied the problem very carefully but cannot see an obvious reason for this problem.  As net-viewer.py was first introduced in librealsense 2.49.0, I cannot rule out the possibility that the problem is related to something the program requires that is not included in the earlier 2.47.0 SDK that you are using.

On September 17 2021 in https://github.com/IntelRealSense/realsense-ros/issues/1804#issuecomment-921425461 a RealSense team member advised that there were no plans to support L515 in rs-server.  This may be because the L515 model has been declared end of life by Intel, with the 400 Series stereo depth camera range being the main focus of the RealSense product range from this point onward.


atsec/11 - paragraph 593 - paragraph is cut off

Comment:
paragraph 593 is cut off.
Proposal:
Please complete it.
Priority: 1

This is related to #16. It is the same issue with the link pulling in the text from section 1.4. I had already corrected this in the adoc version.


Python sdk import fails in demo colab (or any colab)

To reproduce, go to demo colab and execute cells: https://colab.research.google.com/github/stability-ai/stability-sdk/blob/main/nbs/demo_colab.ipynb

+1 - getting the same error... tried downgrading protobuf package (where DESCRIPTOR is imported from) as there was an update 2 days ago, but still got same error.

Hey got it to work with forcing protobuf version: pip install protobuf==3.20.1
Can add to your requirements/environment file

Great! Can confirm this works.

@iainmck that fixed it for me too - thanks!

@iainmck thanks so much for figuring out this fix! working on integrating it presently.

What is the grpcio-tools version you guys have that is compatible with the protobuf version hardcoded here?
I see this following error for the new version 0.2.4 one
There are incompatible versions in the resolved dependencies:
protobuf<5.0dev,>=4.21.3 (from grpcio-tools==1.49.1->stability-sdk==0.2.4->test-stability (pyproject.toml))
protobuf<4,>=3.20.2 (from stability-sdk==0.2.4->test-stability (pyproject.toml))

@polavishnu4444 You don't need to pin the protobuf version anymore, it works as is.

@dmahlow - I haven't pinned, seems like the latest stability-sdk has pinned it??


[Migration] Handle newly added claim in migration

Related to claim introduced in fix https://github.com/wso2/carbon-identity-framework/pull/2747/
<Claim> 				<ClaimURI>http://wso2.org/claims/identity/failedLoginAttemptsBeforeSuccess</ClaimURI> 				<DisplayName>Failed Attempts Before Success</DisplayName> 				<!-- If user store based identity store is used, a proper mapped attribute 				in your user store must be configured for this. --> 				<AttributeID>failedLoginAttemptsBeforeSuccess</AttributeID> 				<Description>Failed Attempts Before Success</Description> 			</Claim>

Resolved with https://github.com/wso2-extensions/identity-migration-resources/pull/42


Fix README

Command typo?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

jenkins test this please

Thank you for your contribution!


Class Name Wrong

Thanks for your great work. I visualize your Train and Val dataset using the mmdetection tool in "tools/misc/browse_dataset.py", but the people are wrongly labeled as "ice cream". Please find the example below.

Hi, @cailk has fixed the problem in this PR #7 . Please let us know if the problem persists, thank you.