Consider renaming the extension

The current extension name is fairly constraining: "GitHub Pull Requests."  I think, ultimately, we'd like to have the freedom to implement non-pull-request-related functionality - issue management, repository discovery and creation, something with projects or GitHub Actions maybe. How would everyone feel about renaming this repository and extension to be more general?
Note that there is already a "GitHub" extension on the Marketplace, but its README has a note directing users to install this one instead.
One alternative would be to create several distinct extensions ("GitHub Repositories", "GitHub Issues") but I feel like that would interfere with discoverability and not provide much benefit. I'm not sure why someone would want to install repository management but not the pull request features, for example. Another would be to leave the name as it is and grow the scope regardless, which feels somewhat misleading.

I see that VSCode extensions have a distinct name and ID. Will we cause any problems if we collide in name but not ID? Will we cause more confusion than it's worth if there are two extensions called "GitHub"? Are there any other names we should use instead?
How difficult mechanically is renaming an extension in the Marketplace? Is there a way to accomplish this without losing reviews, ratings, and download counts? Will existing users be upgraded to the renamed extension seamlessly?

cc @queerviolet @kuychaco @vanessayuenn @RMacfarlane @rebornix for comments, thoughts, and feedback.

Yessss 💯

Will we cause more confusion than it's worth if there are two extensions called "GitHub"?

Perhaps the existing "GitHub" extension author would be willing/happy to cede the name to us. He's already suggesting that folks use this extension instead.

Additionally, I agree that distinct extensions would interfere with discoverability. Furthermore, it would create unnecessary friction and complexity for both our users and developers, hindering progress toward getting features into the hands of users.
And I also agree that leaving the name as-is would be misleading and cause some confusion.
Best case scenario in my mind -- there is one "GitHub" extension, and it is this one.

@smashwilson thanks for starting this conversation. I am in total agreement that we rename the extension from "GitHub Pull Request" to "GitHub".  I don't think we should just limit ourselves to Pull Request functionality when there are a wealth of other GitHub features that we can bring into the extension to create a richer experience.
I'm not sure about the technical limitations of this, and need someone else (@RMacfarlane, @rebornix) to chime in there.
If it is pretty straightforward to rename the extension, I am happy to reach out to the author, KnisterPeter, to see if he's up for us taking over the "GitHub" extension name. Alternatively, we could follow a similar approach as the VS extension and name it "GitHub Extension for VS Code".

You know, even though I'm usually one to prefer brevity, I do like how Official-Sounding "GitHub Extension for VS Code" sounds. 🤔 Granted, every word but "GitHub" is self-evident by the places you're likely to discover it (i.e. the VS Code extension marketplace)...

What about having a GitHub extension pack that bundles together a number of GitHub extensions? Then users could either install that and get a complete GitHub feature set, or pick and choose what integrations they want. One monolithic extension could feel bloated.

It seems we are discussing two items here in this issue: 1. if we should extend this extension to be a generic GitHub extension, and 2. if we want to do that, how difficult to do the migration. I'll suggest we focus on the first one here.
At this point GitHub Pull Request is the right name for this extension. It supports pull request browsing and code review but it doesn't manage github repositories (like GitHub Desktop), or issues/actions/wikis/etc. The viewlet (I called it tree view on Tuesday but viewlet is the name we use in VS Code) is already bloated as it has multiple categories/queries for filtering pull requests and it will also changes in local pr if users are reviewing.
Besides, we don't have a good answer where should new features fit into VS Code UI yet, for example, should we have a dedicated viewlet for GitHub issues or actions? Or probably we can use a web view for that? IMO we may do some experiments and even go back and forth, it may confuse existing users who currently only reviews pull requests in VS Code.
I prefer the approach @RMacfarlane recommended, that we can have a GitHub extension pack and every individual extension serves its own purpose. If we go this route, we may need to change the extension icon to something like below

What about having a GitHub extension pack that bundles together a number of GitHub extensions?

Oh! I wasn't aware that this was a possibility. I'm 👍 on going that route. (Here are the docs to save the others a Google :wink:)

Cool, the GitHub extension pack route sounds promising! I have a couple questions to consider, mainly around getting a full sense of the friction and complexity that this path might involve.
Say we publish a new extension and add it to the pack. What would users need to do, if anything, to get the new extension installed? I'm assuming/hoping the extension pack will automatically upgrade (would love to verify this). If not, then using an extension pack could introduce unnecessary friction/complexity for our users.
What tradeoffs would we be making in terms of adding friction/complexity to our development process? Having all of the GitHub integration code in one repo seems like it would give us maximum dexterity. If we go with the modular approach, we'd want to think about how to extract and share functionality that all extensions would need (authentication, user identity, etc). And some extensions might need access to the same information (for example, the issues extension and PR extension would both want access to a list of mentionable users) or share components (assignees and labels for issues and PRs).
A modular approach is great for encapsulation and separation of concerns, but less great if there's significant interdependency or if you’re fixing bugs or making changes that require first fixing a shared dependency.
We can certainly tolerate increased friction and complexity in the development process. I'd simply like to wrap our heads around the tradeoffs involved as much as reasonably possible before making a decision.

Discussion summary from today's sync-up on this topic:
Currently our extension is called "GitHub Pull Requests" and only has pull request features.
It's just a matter of time until we will want to support other basic GitHub features like viewing issues in the editor, or creating a repository. These are non-PR features, but still core GitHub features that users would reasonable expect and want to use alongside PR features. Separating them out into other extensions would introduce complexity and friction without clear justification from a UX standpoint.
On the other hand, more "stand-alone" features like project boards and actions seem like decent candidates for separate extensions. Many GitHub users don't use these features. Depending on the level of coupling and impact on bundle size, it might still make sense to include these in the core extension. We'll want to consider things on a case-by-case basis.
We talked about a philosophy of breaking things out when it makes sense. That is, waiting until we have a clear and compelling use case rather than preemptively doing so.
With regards to naming and extension pack usage, these are two separate but related decisions.
The driving force for renaming the current extension to a more general name like "GitHub" is to

improve the current extension discovery process (search "GitHub", find a third party extension, hopefully see the note at the top of the readme saying to install "GitHub Pull Requests" instead)
widen the extension's scope and accommodate features pertaining to issues, repositories, etc

According to the extension pack documentation, the driving force for using an extension pack is to bundle extensions, so users can easily disable and enable individual extensions.
In our case, some users may not use GitHub projects or actions. The question is, would they care enough to want to disable or uninstall the code that implements these features?
Or perhaps from the developers perspective, would we want to implement these in a separate extension in order to minimize complexity and bloat in our core package?
If we decide the answer to either of these questions is yes, then it makes sense to discuss creating an extension pack. Which is simply a package that has other packages listed as dependencies. Users that install our extension pack will get all new packages that we add to it, and can choose to disable packages as they wish.
We also discussed practical limitations... We can rename the extension, however changing the extension ID github.vscode-pull-request-github could be a pain if other extensions reference ours by ID. Is there an easy way to get a sense of how many packages would be affected by this? If it's a small enough number of extensions we can submit PRs for the renames to make the transition easier for extension authors.
I think that summarizes what was discussed.
Now I'll shift gears and share some personal thoughts I've fleshed out in writing this summary...

Let's consider all of this through the lens of discoverability
One of our main priorities is to get features into the hands of users.  We want to simplify discoverability and minimize friction for users accessing our new features, and very intentionally introduce friction only when there is a clear and compelling reason.
My 2 cents is that the simplest discovery process with the least amount of friction would be to have a single package published by GitHub called "GitHub". When a user types "GitHub" in the extensions marketplace it's obvious which package to install and they need not choose from a collection of packages that implement different features, or some extension pack that installs them all.
Currently dozens of extensions come up when you type "GitHub", only one of which is owned by GitHub. Let's imagine that KnisterPeter has kindly ceded the name "GitHub" to us, so the top result is "GitHub" by GitHub. There's simplicity and minimal cognitive overhead in having a single clear choice.

Now imagine we decide to implement separate "GitHub Actions" and "GitHub Project" extensions (note that there is already a "GitHub Actions" extension)... A new user wanting our features would have to sift through the many "GitHub" results and decide what extensions to install. Hmm do I install this "GitHub core features" extension, or this "GitHub extension pack"? It looks like there are two packages for "GitHub Actions", which do I choose? Oh, probably the one that's by GitHub... But I haven't used Actions yet, so maybe I don't need it... But who knows, maybe I will! Oh, I guess the extension pack has it bundled. So maybe I'll just install that..."
In addition to additional cognitive overhead when installing our extension(s), we risk having our newly-released features fall through the cracks. If users opt to install individual extensions instead of the extension pack, then new features we release as separate extensions bundled in the extension pack will never reach their finger tips. Thus limiting our impact and leading to missed opportunities.
Sidenote -- funnily enough, looking at that screenshot I just realized that our "GitHub Pull Requests" extension is listed as uninstalled for me. Yet clearly the extension is installed for me based on the tree view icon. Having multiple GitHub extensions has confused even me!

Where to go from here...
We discussed a lot of options and tradeoffs and in service of grounding/focusing our conversation and walking a linear path towards a solution together, I'm going to throw something out as a starting point for us to move forward from. To be clear, I'm not saying that I think this is the final decision we should make. Just a launching point for further discussion.
Priority: Getting features into users' hands (package discoverability and new feature discoverability)
Solution proposal: Have a single extension with all GitHub features we choose to support
Drawbacks from a users' standpoint: Disk space limitations. Increased installation/load time.
Drawbacks from developers' standpoint: Increased code complexity (though I suppose we can still develop in separate modules as we see fit...)
@meaghanlewis @queerviolet @rebornix @RMacfarlane @smashwilson @StanleyGoldman please feel free to fill in things I might have missed, or share your thoughts on where to go from here 💭. For new solution proposals, please explicitly state the priority that is driving the proposal, and the tradeoffs involved.

@kuychaco thanks for the thorough summary about our discussion about this.

Priority: Getting features into users' hands (package discoverability and new feature discoverability)

I totally agree that getting features into users' hands is a priority. It's also important that they like the features we build and use what we build.

Solution proposal: Have a single extension with all GitHub features we choose to support

It seems this is where we are split. Half of us are interested in the extension pack route and half of us are interested in having a single extension with all the GitHub features we want to build.
With the extension pack, the main drawback from a user's standpoint I see is discoverability since there are already so many GitHub related extensions.
From a developer's standpoint I think that there will still be increased code complexity-- especially when we are trying to figure out the best way to share code between extensions. I know one point that came up last week was in regards to authentication and how we will share authentication or a connection between the extensions.

It appears that discussion has slowed down in this issue so I propose we extend next week's sync by 30 minutes to discuss the pros and cons of each solution and then come to a shared agreement about how we want to move forward.

Closing this issue since extending the functionality of this extension to other GitHub uses is not in scope for the foreseeable future


Fastlane init doesn't find app in ITC

On one of my projects when I run fastlane init it doesn't find the App Name or App Identifier.
[14:10:21]: This app identifier doesn't exist on iTunes Connect yet, it will be created for you
[14:10:21]: This app identifier doesn't exist on the Apple Developer Portal yet, it will be created for you
I'm not sure why this is occurring, anything I should be looking at to help troubleshoot?
Thank you

To confirm, your app has already been created manually (pre-fastlane)?

Yes, it's been in the Appstore for almost a year.

Can you double check you're using the same Apple Id and App Id?

Apple ID is the same, I'm not setting an AppID, The detected Values for App Name and App Identifier is empty. In other projects, fast lane detects this info correctly.

Can you please share the full output of fastlane init? Also, what are your user roles on Dev Center and iTC?

I figured it out!
I saw this error: [12:50:24]: xcrun xcodebuild -list -workspace './Simply Smoothies.xcworkspace'
xcodebuild: error: Scheme Smoothie Creator is not currently configured for the build action.
That scheme was from the original name of the project and no longer valid. Once I removed that scheme, fast lane detected everything correctly!
Thanks for your help.


Problems running on Ubuntu 23.04 (lunar)

Ubuntu 23.04 comes with a new version of Python (default is 3.11) that makes howdy not run properly.
The first issue is line 10 in pam.py:
import ConfigParser
The module is now called configparser so howdy can't properly import it.
Then the python 'dlib' module was missing, I installed it via sudo pip install --break-system-packages dlib.
Doing a mitigation by changing that line to import configparser as ConfigParser makes howdy work in GDM for login but when using it in sudo creates a funky error:
Traceback (most recent call last):
  File "/lib/security/howdy/compare.py", line 23, in <module>
    from recorders.video_capture import VideoCapture

The strange thing is: If you add import recorders to the file there is no problem. Just importing that submodule fails and seemingly only while trying it via sudo.

Linux distribution (if applicable): Ubuntu 23.04
Howdy version (sudo howdy version): Howdy 2.6.1

After changing the configparser import I had a different issue:
ModuleNotFoundError: No module named 'ConfigParser'

After installing dlib with sudo pip install --break-system-packages dlib everything is working now.

@ashkop You made my day.
Howdy is working fine in my Kubuntu 23.04 now.
sudo apt install -y python3-opencv
sudo pip install --break-system-packages dlib
sudo howdy add

@kimhongsu I'm glad that helped. Would still be nice if howdy can be fully updated to python 3.

Purge and reinstall seems to have run into errors:
Setting up howdy (2.6.1) ...

>>> Upgrading pip to the latest version

error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
    python3-xyz, where xyz is the package you are trying to
    install.

    If you wish to install a non-Debian-packaged Python package,
    create a virtual environment using python3 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
    sure you have python3-full installed.

    If you wish to install a non-Debian packaged Python application,
    it may be easiest to use pipx install xyz, which will manage a
    virtual environment for you. Make sure you have pipx installed.

    See /usr/share/doc/python3.11/README.venv for more information.

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
Error while running last command
dpkg: error processing package howdy (--configure):
 installed howdy package post-installation script subprocess returned error exit status 1
Processing triggers for man-db (2.11.2-1) ...
Processing triggers for libc-bin (2.37-0ubuntu2) ...
Errors were encountered while processing:
 howdy
E: Sub-process /usr/bin/dpkg returned an error code (1)

Here's my ugly hack workaround that also works for fresh install of howdy on 23.04, just skip the "apt remove howdy" command.
sudo -i
mv /usr/lib/python3.11/EXTERNALLY-MANAGED /usr/lib/python3.11/DISABLED-EXTERNALLY-MANAGED
apt remove howdy
pip3 install dlib
apt install howdy
nano /lib/security/howdy/pam.py # Change ConfigParser to configparser on 2 lines
mv /usr/lib/python3.11/DISABLED-EXTERNALLY-MANAGED /usr/lib/python3.11/EXTERNALLY-MANAGED

nano /lib/security/howdy/pam.py # Change ConfigParser to configparser on 2 lines

note: You also need to change it elsewhere, or just change the line to import configparser as ConfigParser

This is an annoying one, using --break-system-packages should help but it's really not the clean way to do it. Maybe a venv for Howdy would be better

I've recently updated to Ubuntu 23.04 and Howdy is not working on the lock screen. I tried to reinstall it but it didn't work.
I can still add new faces and Howdy seems to work fine in the terminal and gives me no errors.

--break-system-packages is not a good practice. Maybe howdy could use virtual environments to install this package.

Purge and reinstall seems to have run into errors:
Setting up howdy (2.6.1) ...

>>> Upgrading pip to the latest version

error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
    python3-xyz, where xyz is the package you are trying to
    install.

    If you wish to install a non-Debian-packaged Python package,
    create a virtual environment using python3 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
    sure you have python3-full installed.

    If you wish to install a non-Debian packaged Python application,
    it may be easiest to use pipx install xyz, which will manage a
    virtual environment for you. Make sure you have pipx installed.

    See /usr/share/doc/python3.11/README.venv for more information.

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
Error while running last command
dpkg: error processing package howdy (--configure):
 installed howdy package post-installation script subprocess returned error exit status 1
Processing triggers for man-db (2.11.2-1) ...
Processing triggers for libc-bin (2.37-0ubuntu2) ...
Errors were encountered while processing:
 howdy
E: Sub-process /usr/bin/dpkg returned an error code (1)

I've got the exact same issue with a fresh install of Ubuntu 23.04 Linux 6.2.0-20-generic 64-bit. Wrapping howdy inside of it's own venv would be the optimal solution here and for isolating its install further from the host.

@nate3D  Thanks for the solution, could you please share an example of how to do the "Wrapping howdy inside of it's own venv"?

I've found a solution to the ModuleNotFoundError: No module named 'ConfigParser' error, the fix is in the https://github.com/boltgolt/howdy/issues/799

To those who are not willing to use --break-system-packages:
sudo pip install -t /lib/security/howdy dlib

Tested on the beta branch, should work on master.

This is an annoying one, using --break-system-packages should help but it's really not the clean way to do it. Maybe a venv for Howdy would be better

@boltgolt Could you let us know how to wrap howdy up with venv? Or is it possible to wrap howdy up with docker?

To those who are not willing to use --break-system-packages:
sudo pip install -t /lib/security/howdy dlib

Tested on the beta branch, should work on master.

@boltgolt Perhaps this fix can be incorporated in release or at least beta?

To those who are not willing to use --break-system-packages:
sudo pip install -t /lib/security/howdy dlib

Tested on the beta branch, should work on master.

@boltgolt Perhaps this fix can be incorporated in release or at least beta?

Tried on ubuntu 23.10 Could install howdy after installing dlib like this, but could not run howdy.

Purge and reinstall seems to have run into errors:
Setting up howdy (2.6.1) ...

>>> Upgrading pip to the latest version

error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
    python3-xyz, where xyz is the package you are trying to
    install.

    If you wish to install a non-Debian-packaged Python package,
    create a virtual environment using python3 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
    sure you have python3-full installed.

    If you wish to install a non-Debian packaged Python application,
    it may be easiest to use pipx install xyz, which will manage a
    virtual environment for you. Make sure you have pipx installed.

    See /usr/share/doc/python3.11/README.venv for more information.

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
Error while running last command
dpkg: error processing package howdy (--configure):
 installed howdy package post-installation script subprocess returned error exit status 1
Processing triggers for man-db (2.11.2-1) ...
Processing triggers for libc-bin (2.37-0ubuntu2) ...
Errors were encountered while processing:
 howdy
E: Sub-process /usr/bin/dpkg returned an error code (1)

I am also get the same problem on Ubuntu version 23.10.1
Howdy Installation Issue on Ubuntu 23.10.1
Problem:
I encountered an issue with Howdy installation on Ubuntu version 23.10.1. The provided solutions seemed to have complications.
Workaround:
I found a workaround that worked for me, even on a fresh install of Ubuntu 23.10.1. Skip the "apt remove howdy" command to avoid additional errors during sudo authentication.

Open a root shell:
sudo -i

Move the EXTERNALLY-MANAGED directory:
  mv /usr/lib/python3.11/EXTERNALLY-MANAGED /usr/lib/python3.11/DISABLED-EXTERNALLY-MANAGED

Remove Howdy (skip if fresh install):
 apt remove howdy

Install dlib using pip3:
pip3 install dlib
If pip3 doesn't work, try pip install dlib. If that also fails, attempt:
sudo pip install --break-system-packages dlib

Reinstall Howdy:
 apt install howdy

Edit pam.py to fix import error:
 nano /lib/security/howdy/pam.py

Change import ConfigParser to import configparser as ConfigParser you can find on lines 2 to 11.

Restore EXTERNALLY-MANAGED directory: mv /usr/lib/python3.11/DISABLED-EXTERNALLY-MANAGED /usr/lib/python3.11/EXTERNALLY-MANAGED

This workaround should help resolve the installation issues in my case.
While adding face some time you will get device_path problem but i am solve it like this.
 # Should be set automatically by an installer if your distro has one
 # device_path = /dev/v4l/by-path/pci-0000:00:14.0-usb-0:6:1.2-video-index1 # default in my config comment it add new below like this
 device_path = /dev/video0

https://github.com/boltgolt/howdy/issues/851
I also have a silution without breaking system packages. This solution depends on a dep package which is not released yet.


[Nomination] I would like to nominate Jacob (Faddat)

Who are you nominating?
Jacob aka Faddat
What are you nominating them for?
Being an active contributor in the discord and helping update the Juno code to the latest versions.
Helping smaller validators with issues.
Please provide links to their work.
https://github.com/CosmosContracts/Juno/commit/c0e7cf894e90dad8c650bbc3fff9b7b2ab87168a
https://github.com/CosmosContracts/Juno/commit/2b03ba3234b4870dafe9992eb1d00f74360b3e1e
https://github.com/CosmosContracts/Juno/commit/d4cc921c5d6a60cde4dad5d6e328e4c13c41f9f4
https://github.com/CosmosContracts/Juno/commit/213ab84803113517e035c9f5f5858e65c146b199
https://github.com/CosmosContracts/Juno/commit/dd0a95b272690f9e0581ac9a736425d6462cbf2e
https://github.com/CosmosContracts/Juno/commit/854faed2c0e91592543386386b9274f4895428c2
https://github.com/CosmosContracts/Juno/commit/b509b0db7a13d16ea4e2dce0dfa12f4962c5cd8d
https://github.com/CosmosContracts/Juno/commit/53ff6aaae486f0cf09f0e7550c1e108e777c5fc5

Second!

He also help test taking down a juno validator on akash

Also 0.43 upgrade + dockerization

@faddat has been awesome! Extremely helpful in getting IBC relayers setup so we can connect to Osmosis.


Fix typo

GitHub action -> GitHub Action

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

@rwike77,
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge. Thanks.


Update azure-stack-deploy-template-powershell.md

Fixed typos.

Hi @alexandair, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;

@ErikjeMS - Please review this public repo PR

Thanks for the improvement, alexandair!
@tysonn - please merge these changes.


add helpful error message about not available search on development mode

fixes https://github.com/shuding/nextra/issues/3441 https://github.com/shuding/nextra/issues/2450 https://github.com/shuding/nextra/issues/3405
cc @87xie wdyt 😅
Postbuild script will be mentioned in docs, so no need to add here I guess
"postbuild": "pagefind --site .next/server/app --output-path .next/static/chunks/pagefind",

thank you ❤


miners: Add new column to show accumulated share

Accumulated mining share of all miners above (when sorted after share) would make it easier to read which mining pool that would need to get onboard for Taproot to be activated.

This new column could be hidden on mobile devices, for screens where the resolution is under 640px in the width. This can be done using CSS.

In CSS the rule would be as follows, and in the JSX, the class name "collapse-by-640" should be set.
@media only screen and (max-width: 640px) {
    .collapse-by-640 {
        display: none;
    }
}

PR updated with hiding of new column on small screens.


Add configurable serviceAnnotation to services

We've identified that certain loadbalancers have annotations that need to be passed (e.g. session connection timeouts for ssh)
We will add a configurable serviceAnnotation (similar to podAnnotation) that allows a chart user to pass the key and value into the annotation.

Sounds good, but maybe it would be better placed under <component>.service.annotations to mirror <component>.ingress.annotations?


Issue with widgetbox in Bokeh

Hi,
This repository is very useful. However, after installation of cimcb, when I tried to import it, I got the following error.
I appreciate any suggestion to tackle with it.
Traceback (most recent call last):
File "", line 1, in
File "C:\Users\user\AppData\Roaming\Python\Python311\site-packages\cimcb_init_.py", line 3, in
from . import bootstrap
File "C:\Users\user\AppData\Roaming\Python\Python311\site-packages\cimcb\bootstrap_init_.py", line 2, in
from .BC import BC
File "C:\Users\user\AppData\Roaming\Python\Python311\site-packages\cimcb\bootstrap\BC.py", line 7, in
from bokeh.layouts import widgetbox, gridplot, column, row, layout
ImportError: cannot import name 'widgetbox' from 'bokeh.layouts' (C:\ProgramData\anaconda3\Lib\site-packages\bokeh\layouts.py)
Best,

I had the same issue when trying to run a bokeh v2 code with bokeh v3
The bokeh migration guide says:
The WidgetBox model and associated convenience function widgetbox have been removed. Use row, column, and grid layouts instead.
See : https://github.com/bokeh/bokeh/wiki/Migration-Guides#remove-300
The answer is late but it may help any in their web search for the same issue


Download Error

Expected behavior
to download a container successfully.
Actual behavior
can not download, gives error.
Information about the Issue
error parsing HTTP 403 response body: invalid character '<' looking for beginning of value: "\nAccessDeniedRequest has expired2019-03-26T05:27:27Z2019-03-26T05:41:53ZE5EF891139665182waAjULeNvogcPeVyg16oHX/qzWAsaKA7aPM9dxnjrsdfQRBelNoV9W+CE8piNozqRAIzLwOcTy0="
Steps to reproduce the behavior

...Select docker file emqx-builder
...you can see error mention above

It is solved.
That was time out error.
Thanks.


test attribute predictor with a wrong result

I have download model from model zoo.
VGG-16 Global Pooling, VGG-16 Landmark Pooling, ResNet-50 Global Pooling
I put them to path checkpoint with name: vgg16_global_latest.pth, vgg16_landmark_latest.pth, model_best.pth.
then i copy img for test, the test images and attributes are:
img/Boxy_Shirt_Dress/img_00000003.jpg: boxy
img/Boxy_Shirt_Dress/img_00000014.jpg: boxy striped
img/Boxy_Shirt_Dress/img_00000025.jpg: boxy shirt
I copy the images to demo/images with name:img_00000003.jpg, img_00000014.jpg, img_00000025.jpg
then i run these cmd:
python demo/test_predictor.py --checkpoint checkpoint/vgg16_landmark_latest.pth --config configs/attribute_predict/global_predictor_vgg_attr.py --input demo/imgs/img_00000003.jpg
the top5 result is : lace knit maxi sleeve shirt
python demo/test_predictor.py --checkpoint checkpoint/vgg16_landmark_latest.pth --config configs/attribute_predict/global_predictor_vgg_attr.py --input demo/imgs/img_00000014.jpg
the top5 result is : knit striped lace maxi sleeve
python demo/test_predictor.py --checkpoint checkpoint/vgg16_landmark_latest.pth --config configs/attribute_predict/global_predictor_vgg_attr.py --input demo/imgs/img_00000025.jpg
the top5 result is :lace knit maxi sleeve print
python demo/test_predictor.py --checkpoint checkpoint/model_best.pth --config configs/attribute_predict/global_predictor_resnet_attr.py --input demo/imgs/img_00000003.jpg
the top5 result is : knit sleeve shirt striped lace
python demo/test_predictor.py --checkpoint checkpoint/model_best.pth --config configs/attribute_predict/global_predictor_resnet_attr.py --input demo/imgs/img_00000014.jpg
the top5 result is : striped stripe knit sleeve shirt
python demo/test_predictor.py --checkpoint checkpoint/model_best.pth --config configs/attribute_predict/global_predictor_resnet_attr.py --input demo/imgs/img_00000025.jpg
the top5 result is : maxi lace knit sleeve skinny
when i run: python demo/test_predictor.py --checkpoint checkpoint/vgg16_global_latest.pth --config configs/attribute_predict/global_predictor_vgg_attr.py --input demo/imgs/img_00000003.jpg,  I got an error:The model and loaded state dict do not match exactly. unexpected key in source state_dict: roi_pool.linear.0.weight, roi_pool.linear.0.bias, concat.fc_fusion.weight, concat.fc_fusion.bias
I have two questions:
1.Did i run the cmd with the wrong params? if wrong  how to run it ?
2.the model of VGG-16 Landmark Pooling, ResNet-50 Global Pooling used for attribute test seems not accurate, why?
Please help me, thank you.

I am also facing the same issue.

me too
did you solve it?

No

We just update a more accurate attribute and category predictor. Please download it from model_zoo.md
First you need to download our re-labeled annotations(https://drive.google.com/drive/folders/19J-FY5NY7s91SiHpQQBo2ad3xjIB42iN?usp=sharing).
The script for this category and attributes prediction is
python demo/test_cate_attr_predictor.py
python test tools/test_cate_attr_predictor.py

I have cloned the repository again and download the re-labelled annotation. When I run the code:
python3 demo/test_cate_attr_predictor.py \ --config configs/category_attribute_predict/global_predictor_vgg.py \ --checkpoint checkpoint/latest.pth
I get this error:
Traceback (most recent call last):
File "demo/test_cate_attr_predictor.py", line 8, in
from mmfashion.core import AttrPredictor, CatePredictor
ImportError: cannot import name 'CatePredictor'
Thanks for your help.

I have cloned the repository again and download the re-labelled annotation. When I run the code:
python3 demo/test_cate_attr_predictor.py \ --config configs/category_attribute_predict/global_predictor_vgg.py \ --checkpoint checkpoint/latest.pth
I get this error:
Traceback (most recent call last):
File "demo/test_cate_attr_predictor.py", line 8, in
from mmfashion.core import AttrPredictor, CatePredictor
ImportError: cannot import name 'CatePredictor'
Thanks for your help.

I cannot replicate your error. Maybe you can try "python setup.py install" again and then test.

Thank you that worked for me.

Followed the same steps suggested by @veralauee . While category predictions seem to change with input image, attribute predictions are same regardless of input images

Followed the same steps suggested by @veralauee . While category predictions seem to change with input image, attribute predictions are same regardless of input images

Sorry, I cannot replicate your error.
For demo/attr_pred_demo2.jpg, my attribute prediction results are
[ Top3 Attribute Prediction ] cotton conventional crew_neckline [ Top5 Attribute Prediction ] cotton conventional crew_neckline no_dress solid
While for demo/01_3_back.jpg, the attribute prediction are
[ Top3 Attribute Prediction ] no_dress conventional long_sleeve [ Top5 Attribute Prediction ] no_dress conventional long_sleeve crew_neckline cotton

@veralauee I have followed your instructions and downloaded Anno_fine annotation and the Fine resnet50 Global Pooling model. However, it looks like the model doesn't fit the config. Following is the output on predicting attribute and category on attr_pred_demo2.jpg, which look incorrect.
 While category predictions seem to change with input image, attribute predictions are same regardless of input images

Sorry, I cannot replicate your error.
For demo/imgs/attr_pred_demo2.jpg, my attribute prediction results are
[ Top3 Attribute Prediction ] cotton conventional crew_neckline [ Top5 Attribute Prediction ] cotton conventional crew_neckline no_dress solid
While for demo/imgs/01_3_back.jpg, the attribute prediction are
[ Top3 Attribute Prediction ] no_dress conventional long_sleeve [ Top5 Attribute Prediction ] no_dress conventional long_sleeve crew_neckline cotton

I can confirm this result on VGG-global.
Unfortunately, this is about the only model that I can run with decent performance.
All landmark-based (roi) and Resnet based models fail to generate meaningful predictions. Any help is appreciated.


elevation and flatness conditions

Hi!
flatness and elevation thresholds are updated iteratively. Therefore, they are set to zeros:
elevation_thr = {0, 0, 0, 0}; // threshold of elevation for each ring using in GLE. Those values are updated adaptively.
flatness_thr = {0, 0, 0, 0}; // threshold of flatness for each ring using in GLE. Those values are updated adaptively.
In the estimateGround member function, you compare the ground_elevation and ground_flatness variables with those thresholds using the concentric_idx:
if (concentric_idx < params_.num_rings_of_interest)
{
is_not_elevated = ground_elevation < params_.elevation_thr[concentric_idx];
is_flat         = ground_flatness < params_.flatness_thr[concentric_idx];
}
I have two observations:

Since the z-axis is upward, the  ground_elevation for ground planes should be always negative. Therefore,  is_not_elevated is always True. On the other hand, if the least significant eigenvalue of a plane ground_flatness is positive, the is_flat is always False.
concentric_idx is increaded under the ring and sector loops. Then, the threshold arrays should have more than 4 values.

At first, yes, but aren't they updated at the next step?

I did not check if they are updated or not as I am interested in a single scan pcd. Another question, why I get non orthogonal normals even though I set uprightness threshold to 0.99?
patch_normals
array([[-0.09144519,  0.05306055,  0.99439555],
[ 0.69917166, -0.604823  ,  0.3812459 ],
[-0.01123331,  0.04285617,  0.9990182 ],
[-0.09687269,  0.05675028,  0.99367774],
[-0.10806715,  0.055059  ,  0.9926178 ],
[-0.09962063,  0.06085207,  0.99316317],
[-0.06921859,  0.05507125,  0.9960804 ],
[-0.06099597,  0.05220991,  0.99677163],
[-0.04113085,  0.03393086,  0.99857754],
[-0.09267069,  0.04970804,  0.9944553 ],
[-0.09723388,  0.04760678,  0.9941223 ],
[-0.07620493,  0.06242752,  0.995136  ],
[-0.03467678,  0.0526633 ,  0.99801   ],
[-0.04037486,  0.04701625,  0.9980778 ],
[-0.06198691,  0.06860244,  0.9957165 ],
[-0.08162168,  0.01962108,  0.99647033],
[-0.07868537,  0.0243757 ,  0.99660146],
[-0.06772294,  0.02173795,  0.9974672 ],
[-0.00943837,  0.0398108 ,  0.9991627 ],
[-0.01602176,  0.03286225,  0.9993314 ],
[-0.03886676,  0.06128451,  0.9973634 ],
[-0.07812789, -0.00297109,  0.99693906],
[-0.0880304 ,  0.02805167,  0.99572283],
[-0.06525222,  0.04650887,  0.9967845 ],
[-0.6830666 , -0.7300232 ,  0.02205181]], dtype=float32)

I guess those might be filtered out later after the prediction of all normals. Could you also share the exact part that you want to discuss?


try fixes and understanding the problem ...

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

This passes?

I see a lot of clobber warnings.

The reason for this is most likely as described here, i.e. reinstallation of numpy.

Once this merges: https://github.com/JuliaPy/PyCall.jl/pull/1040 we can disable the re-installation with a build flag. Then hopefully the build warnings will disappear.

@conda-forge-admin, please rerender

Not sure if this is a clue, but with the libstdcxx-ng<13 setting in run_constraints:, the mamba build is now working, but the conda build fails:
https://github.com/MilesCranmer/PySR/actions/runs/5242217963

Once this is merged: https://github.com/JuliaRegistries/General/pull/85755
Then we can re-run these tests (need to bump build number), and see if it solves the clobber problem

Cool, it looks like the clobber issue is gone? Are there any other warnings we need to worry about?

Fingers crossed.

This looks better now, though there's what looks like a segfault in one of the linux jobs on main.
Also, this doesn't look great:
WARNING (pysr,share/pysr/depot/artifacts/9f6f87cc2114df918ff9c21dff9572f690e7dab2/lib/libLLVMExtra-14.so): runpaths ['$ORIGIN'] found in /home/conda/feedstock_root/build_artifacts/pysr_1687299957695/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeh/share/pysr/depot/artifacts/9f6f87cc2114df918ff9c21dff9572f690e7dab2/lib/libLLVMExtra-14.so
WARNING (pysr,share/pysr/depot/artifacts/9f6f87cc2114df918ff9c21dff9572f690e7dab2/lib/libLLVMExtra-14.so): $RPATH/libLLVM-14jl.so not found in packages, sysroot(s) nor the missing_dso_whitelist.
.. is this binary repackaging?
WARNING (pysr,share/pysr/depot/artifacts/9f6f87cc2114df918ff9c21dff9572f690e7dab2/lib/libLLVMExtra-14.so): /lib64/libstdc++.so.6 not found in packages, sysroot(s) nor the missing_dso_whitelist.
.. is this binary repackaging?
WARNING (pysr,share/pysr/depot/artifacts/9f6f87cc2114df918ff9c21dff9572f690e7dab2/lib/libLLVMExtra-14.so): /lib64/libm.so.6 not found in packages, sysroot(s) nor the missing_dso_whitelist.
.. is this binary repackaging?
WARNING (pysr,share/pysr/depot/artifacts/9f6f87cc2114df918ff9c21dff9572f690e7dab2/lib/libLLVMExtra-14.so): /lib64/libgcc_s.so.1 not found in packages, sysroot(s) nor the missing_dso_whitelist.
.. is this binary repackaging?
WARNING (pysr,share/pysr/depot/artifacts/9f6f87cc2114df918ff9c21dff9572f690e7dab2/lib/libLLVMExtra-14.so): /lib64/libc.so.6 not found in packages, sysroot(s) nor the missing_dso_whitelist.
.. is this binary repackaging?

I don't know where libLLVMExtra-14.so comes from - I help package LLVM for conda-forge, but I've never seen that library, and I cannot find it upstream either.

Regarding the segfault, the full set of tests is fairly compute/memory intensive compared to the compute used in the build jobs. So maybe we could use a lighter test, since we just want a smoke test for the integration all working.
I’m also unsure why the OSX jobs freeze during the precompilation: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=731490&view=logs&j=a8dee1cf-d17f-5cb0-b53f-4a93dfdbfb0c&t=d9dbf137-9a7f-5666-c60c-9e1b2fc31445 — this seems repeatable, and only occurs on Python 3.9+OSX…


Refactor WKT for reuse and speed.

What I am changing

Refactored WKT code to not instantiate new objects all the way down. The previous method had to construct and validate other geometry types to get the WKT.
Updated pre-commit versions because my local repo wouldn't let me commit without updating. Excluding pydocstyle which changed and threw a bunch of errors.

How I did it

Created shared functions to reduce code duplication and make code easier to read.
Used those functions recursively to avoid other geometries.

How you can test it

Kept existing tests, and updated as needed for additional cases.

Related Issues

Discussion #95
Issue #89

This doesn't address one issue I noticed while testing: mixed dimensionality. Shapely doesn't allow for it. So a MultiPoint(coordinates=[(0,0),(1,1,1)]) will become MULTIPOINT Z (0 0 0, 1 1 1) but we do not enforce that. Not sure where to go with that.
I would also like to use hypothesis to generate tests with the pydantic hypothesis plugin rather than having so many hard coded hard to read values. It would likely break for the above case, but it would be good to know more about where things are different.

This doesn't address one issue I noticed while testing: mixed dimensionality. Shapely doesn't allow for it. So a MultiPoint(coordinates=[(0,0),(1,1,1)]) will become MULTIPOINT Z (0 0 0, 1 1 1) but we do not enforce that. Not sure where to go with that.

I would also like to use hypothesis to generate tests with the pydantic hypothesis plugin rather than having so many hard coded hard to read values. It would likely break for the above case, but it would be good to know more about where things are different.

Let's open new issues for those case.
As far I'm concerned, this PR is good to go. @eseglem I'll let you set it to Ready for review before I merge it


How to prevent crash on unhandled errors when using streams?

Hi,
what is the recommended way of preventing a crash of the application if I'm using sharp as follows and the buffer data is undefined or has unsupported image data in it?
The 'error' event is not being fired in this case. Do I need to incorporate a try/catch block somehow?
var pipeline = sharp()
.on('error', err => console.log('error'))
.pipe(fs.createWriteStream('filename.jpg'));

var readStream = new stream.PassThrough();
readStream.end(someBuffer);

readStream.pipe(pipeline);

When someBuffer is undefined, I get this error and the app crashes.
     Error: Input file is missing or of an unsupported image format
        at Error (native)

Piping undefined into a sharp instance will (currently) result in a zero-length Buffer being processed by libvips. This situation can be improved, but I would expect it to still emit the error event. I'll need to take a closer look.

Thank you - that helped a lot.

on is chainable, but pipe returns the target (writable) stream, so the original snippet pipes the readable stream directly into the writable stream.

I'm trying to follow this example, but I am clearly missing something as I am unable to trap the error.
my pipeline looks like:
 var remoteWriteStream = bucket.file('assets/images/lead/' + file).createWriteStream({metadata: { contentType: 'image/jpeg'}});
 var pipeline = sharp('./public/images/tmp/' + file)
 .resize(1280, 800)
 .crop(sharp.gravity.north)
 .quality(85)
 .on('error', err => console.log('error');
 pipeline.pipe(remoteWriteStream)

sharp error: Error: Input file is missing or
of an unsupported image format

@afrozl Perhaps try using an absolute path instead of the relative ./public/images/... (as paths are relative to the working directory, which isn't always the same as the directory containing your script).

Thanks, looks like I was receiving the error but not handling the unpipe correctly


Default version of Wit API now changed to 20160526

Default version of Wit API now changed to 20160526.
https://wit.ai/docs/http/20160526#post--speech-link

Coverage remained the same at 50.256% when pulling 37cb28edb1eb0c7bdbc730c3ba8ed05426a228b4 on G10DRAS:jasper-dev into 6d0a81dcbf435fa6230fd9516e1093a06a937889 on jasperproject:jasper-dev.


Cannot read properties of undefined (Reading "0")

Title, this error is causing me hell when trying to convert a friend's project using Leopard.
I tracked the error down to an IO library in the converter. The exact error spot is sb-edit/src/io/leopard/toLeopard.js:927.
Full error (Glitch.me, running project Colorlens by Yuski347):
/rbd/pnpm-volume/c3f6456c-ea9a-4017-ae1c-18ff3b9a1c5b/node_modules/sb-edit/lib/io/leopard/toLeopard.js:927
})[0]
^
TypeError: Cannot read properties of undefined (reading '0')
at /rbd/pnpm-volume/c3f6456c-ea9a-4017-ae1c-18ff3b9a1c5b/node_modules/sb-edit/lib/io/leopard/toLeopard.js:927:19
at Array.map ()
at _loop_1 (/rbd/pnpm-volume/c3f6456c-ea9a-4017-ae1c-18ff3b9a1c5b/node_modules/sb-edit/lib/io/leopard/toLeopard.js:921:93)
at Project.toLeopard (/rbd/pnpm-volume/c3f6456c-ea9a-4017-ae1c-18ff3b9a1c5b/node_modules/sb-edit/lib/io/leopard/toLeopard.js:949:9)

It's probably possible to just figure out which variable would be used and discard the rest (ex. maybe only the first definition of a variable is ever used in any case) but I don't really feel comfortable making an assumption about Scratch like that. I'm going to see if it's possible to support variables of the same name within sb-edit, then do a more intelligent sweep to only remove 100% unused (duplicate) variables in the toLeopard conversion.

On 2023-02-16 11:48, (quasar) nebula wrote:> It's probably possible to just figure out which variable would be> used and discard the rest (ex. maybe only the first definition of a> variable is ever used in any case) but I don't really feel comfortable> making an assumption about Scratch like that. I'm going to see if it's> possible to support variables of the same name within sb-edit, then do> a more intelligent sweep to only remove 100% unused (duplicate)> variables in the toLeopard conversion.> > --> Reply to this email directly, view it on GitHub [1], or unsubscribe> [2].> You are receiving tCan his because you authored the thread.Message ID:> > > Links:> ------> [1] > https://github.com/leopard-js/sb-edit/issues/85#issuecomment-1433391000> [2] > https://github.com/notifications/unsubscribe-auth/AM623SMA43IYGWI4NVU63ODWXZK7DANCNFSM6AAAAAAU6MGJCMCan you give a timeline on when this will be fixed? My friend does want to convert his game, and I'll keep up with the bugs.

I've got most of the bugs fixed now — I'm working on some runtime issues (in other words, the project is converting to Leopard without any issue, but the actual behavior isn't working 100% yet).
I'm not in charge of the Leopard website or the way that repositories work together, so once I get everything working, would it be OK if I just send you a zip file of the Leopard output? You can also run off of my sb-edit branch (looks like you've already figured out most of how to get Leopard working locally). It just may take a while longer before the fixes get actually pushed to the online Leopard website.

I'll just run the local Leopard instance. Give me some time to figure out how I'm going to run your sb-edit branch with it. (Thankfully I have Cloudflare R2)

No problem. Here's a build of the project in Leopard — I'll have the sb-edit and leopard PR's open soon. If you decide to run sb-edit locally (e.g. because of further changes to the game), you might want to grab the index.html file from this zip anyway: I customized it to look a little nicer for a standalone game!
(16 MB) colorlens.zip

My friend will be very happy about this once I get it running on Glitch.
I'm using Leopard from unpkg and it's not working at all ;(
https://zircon-incongruous-tarascosaurus.glitch.me (Project link)

Yeah. Um, I assumed index.esm.js got automatically bundled into the output directory, which... it deffo does not! Oops.
Here's mine for now: dist.zip

Time to run the sed command again. Fun :D

Okay, it works now! But the font broke. Help?

No problem!

Okay, it works now! But the font broke. Help?

What browser are you working with? In Chrome the costume fonts seem to render correctly for me. There may be browser differences, that's why I'm pointing you to try Chrome if you're on another browser.
Also, that's weird. I don't see that error at all on my end. It looks like it has to do with speech/thought bubbles, which I don't think the project uses at all?

Chromebook :/
The project URL (if you want to test it, maybe?) is https://zircon-incongruous-tarascosaurus.glitch.me/

Dang, no issues at all for me running yours — just the same as when I run it locally.
Can you tell me what version of Chrome OS you're using?
Also, I feel like it's just the last 5 years or so that a new generation of young people programming on Chromebooks (usually gotten for school I'm guessing?). You guys are inspirational, and brave :P

ChromeOS 109. I also have access to a 103 chromebook (It hit AUE, it's my school loaner LMAO) and it has the same problems...

Oh, actually, sorry for the confusion here ^^;; I spent so much time looking at the version of Colorwell that loaded through Leopard that I didn't realize the fonts weren't loading in correctly.

It turns out we just don't support fonts in SVGs yet. See leopard-js/leopard#107. Sorry for the inconvenience! You'll have to make a remix with these costumes converted to bitmap if you want the fonts to show (they'll look a little pixelated, but until we add proper font support, that's probably the best you can do).
By the way, my Leopard and sb-edit pull requests are open now. See #90 (sb-edit branch compat on my fork) and leopard-js/leopard#157 (leopard branch compat-support on my fork). I use sb-edit-playground as a straightforward utility to make linking sb-edit and leopard easier, just see the README there (as long as you're familiar with the command line, assuming glitch.me gives you CLI access).
As for the "cannot destructure" issue, I looked around the code path leading there, and it seems like some sprite's costume is being set to undefined. That generally shouldn't be happening. Since I can't reproduce it, I'm guessing it's an issue with loading the costume files on your device — since we're both using basically the same web browser, maybe Glitch.me had a temporary caching issue. Can you try clearing your cached images and files (just make sure to deselect your history and other settings!!), then opening your glitch.me link again? Alternatively you could try putting the built files on a different host, like GitHub pages.

I've been getting hard-ratelimited by Glitch because of the SVGs, so Github will have to work I suppose.Can't wait to show my friend once it's all working- Wait, I found more bugs!- Player selection name (P1/P2 above the character telling you which is which) is missing- Settings back button causes the project to crash- Settings sliders all go 1-100 (I just want to be able to use my developer mode :[[[[)

Player selection name (P1/P2 above the character telling you which is which) is missing

In the version I uploaded, I hid those — Leopard doesn't support resizing monitors or positioning them properly when the display canvas is bigger than the actual stage area (e.g. a 480x360 screen showing on a 960x720 webpage view).
You can enable them by searching for .visible = true; and uncommenting the relevant lines. See MainMenu.js, under *whenIReceiveCharacterSelect() { ... }, around line 350.
The variable watchers should show up when they're supposed to, but they won't be positioned quite right if your screen isn't super low resolution. :P

Settings back button causes the project to crash
Settings sliders all go 1-100

Yeah, I spotted your report on that (https://github.com/leopard-js/leopard/issues/156). I'll check both of these out this afternoon if I can!

Settings back button causes the project to crash

This isn't a crash (no error), it's just a slight difference in the order Scratch and Leopard work with clones. In the "main menu" receiver, you broadcast "delete all clones" on the same frame as you create the new main menu clones. In Scratch, only the clones which existed at the time of the broadcast receive the message (and thus get deleted). In Leopard, everything extant on the next frame responds to the broadcast — including the ones which were just spawned! That's a compatibility issue, so I'll have a lookie at getting it resolved.

And there's a new error, walking back with any character throws it:
Uncaught TypeError: Cannot destructure property 'text' of 't' as it is undefined.
at V._renderBubble (index.esm.js:23:33728)
...

While I couldn't reproduce this in your project myself, I found another project with a similar issue. I opened a PR fixing that one (leopard-js/leopard#160), which will hopefully fix your project as well — it turned out to be a compatibility issue instead of failed costume loading.

And there's a new error, walking back with any character throws it:
Uncaught TypeError: Cannot destructure property 'text' of 't' as it is undefined.
at V._renderBubble (index.esm.js:23:33728)
...

While I couldn't reproduce this in your project myself, I found another project with a similar issue. I opened a PR fixing that one (leopard-js/leopard#160), which will hopefully fix your project as well — it turned out to be a compatibility issue instead of failed costume loading.

 Ah, whatever, can't complain- you've been really helpful in getting my friend a converted JS project. Now all I have to do is wait for your PRs to be merged...


Overscan option cropping 2px vertically for only 1px horizontally?

Hey, m4xw told me on Discord it would be a parallel-rdp issue so I guess I'm in the right place?
With either ParaLLEl or Mupen64Plus-Next core on RetroArch, with ParaLLEl-RDP the overscan option stretches the image vertically.
It's not super obvious on low values but it's definitely there, it's like for 2px vertically, it's only doing it for 1px horizontally.
Banjo-Kazooie with the option set to "14":

And for something really obvious, Super Mario 64 with the option set to "64":

edit: Another comparison with 640x480 screenshots, with overscan set at "0":

And "4":

So yeah, looks like it crops properly 4px on the left and right, however it crops 8px on top and bottom.

Fixed by https://github.com/Themaister/parallel-rdp/commit/fe30be669522aa0d9e6d32846f721c1bc5636270

Awesome, thank you! 👍


Error: Prepare console: set console mode: the parameter is not correct.

Hi, I just downloaded the file "twitch-chat-cli_Windows_x86_64.zip", extract it, write "twitch-chat-cli --channels "pokimane" and I get the following:

BTW, I'm on Win 7 x64 SP1.
Cheers.

Okey, I did the auth:
twitch-chat-cli --channels "pokimane" --accounts "username=me;user_id=123456789;client_id=secret;oauth_token=a3b2c1
and now I get:
Error: Failed to execute API request: Get "https://api.twitch.tv/helix/users?login=pokimane": x509:
 certificate signed by unknown authority

I thought that this would be easy and it turned it complex :(

hi @hellishvictor apologies on delayed response - are you behind a proxy?

hi @hellishvictor apologies on delayed response

No problem.

are you behind a proxy?

No.

Is this project dead? I'm still looking for solve this.

hello @hellishvictor it's not dead I just haven't taken the time recently to get some new features added.
I'm curious how this error is occurring, it's looks like a networking/truststore error rather than an error with the application. Can you visit this URL directly in your browser with no issues?

Can you visit this URL directly in your browser with no issues?

What URL?

Can you visit this URL directly in your browser with no issues?

Where is the URL?

https://api.twitch.tv/helix/users?login=pokimane

should show something like

That's really odd @hellishvictor any chance you can try on a different network? hotspot for example


Script Language Registry

Add registry for Script Languages. This will allow other mods to add more Language support.

This is probably how Bun support would be implemented, where .ts files are targetted by it.


Fifth Korean l10n work for release 1.18

Update to Outdated files in the dev-1.18-ko.5 branch. (#21450)
Translate tasks/run-application/run-single-instance-stateful-application in Korean (#21174)
Translate tasks/debug-application-cluster/determine-reason-pod-failure in Korean (#21515)
Translate tasks/manage-hugepages/scheduling-hugepages.md into Korean (#21337)
Translate tasks/extend-kubectl/kubectl-plugins.md into Korean (#21454)
Translate tasks/manage-daemon/rollback-daemon-set.md into Korean (#21376)
Translate contribute/generate-ref-docs/overview in Korean (#21466)
Translate reference/kubectl/overview.md into Korean (#21552)
Translate configure-pod-initialization in Korean (#21600)
Translate tasks/manage-daemon/update-daemon-set.md into Korean (#21378)

Co-authored-by: Jerry Park<EMAIL_ADDRESS>Co-authored-by: Yoon<EMAIL_ADDRESS>Co-authored-by: Yuk, Yongsu<EMAIL_ADDRESS>Co-authored-by: Seokho Son<EMAIL_ADDRESS>Co-authored-by: guslcho<EMAIL_ADDRESS>Co-authored-by: DongMoon Kim<EMAIL_ADDRESS>Co-authored-by: bluefriday<EMAIL_ADDRESS>

#21359 로 인해 발생한 conflict 을 해결한 별도의 브랜치(dev-1.18-ko.5-fix-conflict)로 PR을 생성했습니다. 본 PR이 merge되면, 현행화 작업을 위한 이슈는 conflict 해결하기 전인 dev-1.18-ko.5 브랜치와 비교해서 생성하겠습니다.

고생하셨습니다.
/lgtm
/approve


update Makefile and scrape_table.py to pull from updated data source

current Makefile produces the following error:
Traceback (most recent call last):
  File "/home/user/Documents/chicago-elections-archive/scripts/scrape_table.py", line 69, in <module>
    main()
  File "/home/user/Documents/chicago-elections-archive/scripts/scrape_table.py", line 56, in main
    candidates = get_candidates(soup)
  File "/home/user/Documents/chicago-elections-archive/scripts/scrape_table.py", line 9, in get_candidates
    headers = [v.get_text().strip() for v in soup.find("table").find_all("b")]
AttributeError: 'NoneType' object has no attribute 'find_all'

Looks like the chicagoelections.gov has updated their pages that produce these results. https://chicagoelections.gov/en/election-results-specifics.asp is now a 404 page. This is the new one https://chicagoelections.gov/elections/results/

Some color here: the new flow is that https://chicagoelections.gov/elections/results/ provides a menu of election links, then you go into an individual election which is just  https://chicagoelections.gov/elections/results/{election_id} which then gives you a menu where you pick a race/ward/precinct and then it pulls up a table of the election data and a link to download that election data as an excel file. Incidentally, you can also get the excel file through https://chicagoelections.gov/elections/results/{election_id}?contest={contest_id}&ward={ward_number}&precinct={precinct_number}`
This puts me in the rock/hard place of either using selenium to try to leverage the existing beautifulsoup code OR figuring out how to fetch/process the excel file as ergonomically as possible in the circumstances.

@yashBhosale thanks for digging into this. I think if we can get the data in excel, lets go for it. Even if it requires a significant rewrite - the new code will be much less brittle and likely a lot simpler

Yeah, that's what I was leaning towards as well. Secondary goal (or maybe an umbrella goal) will actually to be able to retire the makefile altogether, since it's actually only for building the data.

cool. the makefile may still be useful if we want to chain some commands together, but we'll see.
for the excel data, we can make use of csvkit


 Maybe i add mouse x,y controll

l3mpik can you turn on skype i want to send you something


Add a Gitter chat badge to README.md

Pitzcarraldo/reduxible now has a Chat Room on Gitter
@Pitzcarraldo has just created a chat room. You can visit it here: https://gitter.im/Pitzcarraldo/reduxible.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Add manually.


Maybe a little optimization

You could probably optimize it a little to avoid some allocation.
module.exports = (def, separator=' ') => {
  const hasOwn = Object.prototype.hasOwnProperty
  let classes
  // Iterate without allocating an array
  for (const cls in def) {
    if (hasOwn.call(def, key) && def[key]) {
      classes = classes != null ? classes + separator + cls : cls
    }
  }
  return classes
}

I'm not sure how much it'll affect performance, though.

I found strings are much faster, pretty much the same implementation: https://github.com/JedWatson/classnames/pull/140#issuecomment-329799976

thanks!


Fixed #279

Q
A

Bug fix?
[x]

New feature?
[ ]

New sample?
[ ]

Related issues?
fixes #279

What's in this Pull Request?
Resolves issue where other dropdowns on the page take the colour of the RichText dropdown.
Also fixes minor coding styles as per @estruyf  feedback

Codecov Report

Merging #280 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #280   +/-   ##
=======================================
  Coverage   72.33%   72.33%
=======================================
  Files          17       17
  Lines         759      759
  Branches      146      156   +10
=======================================
  Hits          549      549
  Misses        163      163
  Partials       47       47

Continue to review full report at Codecov.

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

Thanks @hugoabernier!


Challenge: Use CSS selectors has a bug...

Challenge Use CSS Selectors to Style Elements has an issue.
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
 The code is exactly as needed...
Here is a dropbox screenshot:
https://www.dropbox.com/s/ndv7o8pig0kln98/Screen Shot 2016-06-18 at 10.04.57 AM.png?dl=0

Please use the help chat rooms/forums when you get stuck.
The issue tracker is for reporting issue's only.
Happy Coding.

i think you shoud delete  becuase it is just closing it down

sorry for my english

h2 {color: red;} has to be changet to   h2 {color: blue;}


[BUG/REVIEW SPECS]  multiple data type property for a class

handle the case when adding a data type property to a class that already has at least one data property or object property already


Question: How should download progress be handled?

If I have a state data class called data class Downloading(val progress: Int) : DefaultState() how can I update the progress so that when I listen to state changes in the the view, I can update it accordingly?

Hi, seems that your question is not related to state machine it self, so do it the same way like Downloading is a simple data class not related with a state.
Looks that progress field should be var? Add some notification about changes of its value (observer pattern) and listen to it in view layer.
You can look at this sample https://github.com/nsk90/android-kstatemachine-sample/blob/main/app/src/main/java/ru/nsk/kstatemachinesample/ui/main/MainViewModel.kt
See how ammoLeft field is updated. Just imagine that it is a progress)
The only difference that in this sample this field is stored in another class, but it does not matter, you can store it in your Downloading state.

The thing is that if I addState this Downloading class with one value and it gets copied with a different one, then it's not the same instance registered with all it's transactions... And I get new state with processEvent... So where could I put the changing state, in an onTransition block?
You're suggesting the progress itself shouldn't be a transition in the state machine at all? Then if I'm not yet at 100 when i get another (invalid) transition what would happen?

Say I have:
// Coming from another service doing this
sealed class DownloadState : Event {
   object WaitingForDownload : DownloadState()
   data class Downloading(val progress: Int) : DownloadState()
   data class MoveTo(val location: Path) : DownloadState()
}

// The state machine needs to listen to these events and transform them to states for the compose UI
val stateFlow = MutableStateFlow<DownloadState>(...)

// Just manage transitions from state to state according to events recieved from other service
val sm = createStateMachine {
...
}

// In the viewModel -- deliver state changes to the UI from the state machine
sm.onStateChanged {
// ... update UI according to state --- but progress isn't a state...?
}

I'd like to separate the concern of updating the UI from managing the transitions, whereas in your code in the sample -- the UI should be updated directly in the state machine, or a new abstraction layer needs to be created just to provide updates to a separate flow for progress.... I was wondering if I could use the state machine to update the progress somewhere, and provide that to update the UI --- but only when in the downloading state.

sealed class DownloadState : Event {
   object WaitingForDownload : DownloadState()
   data class Downloading(val progress: Int) : DownloadState()
   data class MoveTo(val location: Path) : DownloadState()
}

I dont understand this construction, this is mistape or you want States to be Events at the same time?

I recommend to combine notifications from state machine and from progress value updates in ViewModel into a single flow.

sealed class DownloadState : Event {
   object WaitingForDownload : DownloadState()
   data class Downloading(val progress: Int) : DownloadState()
   data class MoveTo(val location: Path) : DownloadState()
}

I dont understand this construction, this is mistape or you want States to be Events at the same time?
usually there are two separate sealed classes for Events and States.

Those are really events... Coming from an older system, i'm refactoring old code. I do have a separate sealed class for states

It is not possible, additional abstraction layer is really necessary. Or you have to provide 100 states with values from 0 to 100, and switching between them. State machine itself notifies only about state changes and transitions, it does not know about states properties changes.

I realized that, I guess what I really wanted was a better way to listen to those transitions from state A back to state A outside the state machine, without having to do too muchtype checking and type casting...

As I see slack is not working in Russia any more.


Test data for #6

This issue is for testing the solution for issue #6.

Posted on behalf of Peter Monks:
foo


Add CompatibleResult

Designed to cope with Result data published to DynamoDB or JSON that could be v5 or v6.

New commit is 💯. Will pull.


Onivim2 seems to use three different fonts etc

Onivim2 seems to use three different fonts etc.
And only the fonts in the editor seem to be user-configurable.

There is a configuration for the terminal. One of the Oni devs on Discord mentioned that it might be better if the terminal font defaulted to the same as editor.
For the "third" font I assume you mean the theme? If so, I'm not sure how to update a theme font.

There is a configuration for the terminal. One of the Oni devs on Discord mentioned that it might be better if the terminal font defaulted to the same as editor.
For the "third" font I assume you mean the theme? If so, I'm not sure how to update a theme font.

One of the Oni devs on Discord mentioned that it might be better if the terminal font defaulted to the same as editor.

Indeed, we should fall back to the editor font if the terminal font isn't specified!
Right now - we default to our embedded font (JetBrains-Mono) if the editor font isn't specified.... which is confusing if "editor.fontFamily" has been set to something else.

If so, I'm not sure how to update a theme font.

Right, we use a non-monospace font for several UI elements (like the explorer, tab titles, etc), Currently we don't have a way to customize this font (it's bundled, a font called Inter UI)

One of the Oni devs on Discord mentioned that it might be better if the terminal font defaulted to the same as editor.

Indeed, we should fall back to the editor font if the terminal font isn't specified!
Right now - we default to our embedded font (JetBrains-Mono) if the editor font isn't specified.... which is confusing if "editor.fontFamily" has been set to something else.

If so, I'm not sure how to update a theme font.

Right, we use a non-monospace font for several UI elements (like the explorer, tab titles, etc), Currently we don't have a way to customize this font (it's bundled, a font called Inter UI)

Thanks I have now applied my editor fontSize and fontFamily settings to terminal.
However, the line spacing still seems different between the two?

Thanks I have now applied my editor fontSize and fontFamily settings to terminal.
However, the line spacing still seems different between the two?

However, the line spacing still seems different between the two?

Ah, it's something similar - there is an editor.lineHeight setting which defaults to 1.2. Onivim is missing the equivalent setting for the terminal, and like the fontFamily, it should fallback to editor.lineHeight.

However, the line spacing still seems different between the two?

Ah, it's something similar - there is an editor.lineHeight setting which defaults to 1.2. Onivim is missing the equivalent setting for the terminal, and like the fontFamily, it should fallback to editor.lineHeight.

Related: changing the theme changes the appearance of the chrome and the editor but not the terminal.

Related: changing the theme changes the appearance of the chrome and the editor but not the terminal.

Related: changing the theme changes the appearance of the chrome and the editor but not the terminal.

Interesting - which theme did you change from / to? I'm not reproducing the theme issue:

Working on a fix for the font-family and size fallbacks in #3077

I think it might be related to me coding colours for my normal terminal emulator in my ~/.zshrc.
My other issue about publishing a variable that allows us to detect and account for Onivim2 will be the fix for this.


ENH: Removed AMRFinderPlusAnnotation type

solves #94

Removed AMRFinderPlusAnnotation. Now there are SampleData[AMRFinderPlusAnnotations] and FeatureData[AMRFinderPlusAnnotations] that both use the same type and dir format.
Renamed files in fir format from "mutations" to "all_mutations".

Run it locally

First, clone the repo and checkout the PR branch:

git clone https://github.com/bokulich-lab/q2-amr.git
cd q2-amr
git fetch origin pull/95/head:pr-95
git checkout pr-95
pip install -e .

Download test data:
PR-94.zip

Test it out!

qiime tools import --input-path sample_data --output-path amr_annotations.qza --type "SampleData[AMRFinderPlusAnnotations]"
qiime tools import --input-path feature_data --output-path amr_annotation.qza --type "FeatureData[AMRFinderPlusAnnotations]"

Hey @VinzentRisch,
Are the changes of annotate_sample_data_amrfinderplus part of this PR? If yes can you give me the commands to test it?


Develop fix histroy content

For now the history table is fully resizeing according to the mobile view...Also the pop-up is also resizeing.
@smcgregor please review...:)
#358

Can you post a screen capture with the width being cell phone sized?

Currently looking like this...
in the chrome by changing to device mode

in my own mobile device
![screenshot_2016-03-01-02-09-35_ly priv mobile]
(https://cloud.githubusercontent.com/assets/10517011/13408247/e2908a48-df52-11e5-82e0-f97b2829346c.png)

sorry for the second and third screenshot ....they are from my mobile device...i didn't thought that they will look like this.....posting small one ....


Remember previous conversations

It would be nice for ChatGPT to remember the past questions and answers.

Sure. will be adding that soon

Also, if it isn't too much trouble could you add it to the local_setup branch? Thank you for the quick reply!

sure bud

any updates on being able to remember the chat context?

thinkin about moving this project to nextjs so that its easier to maintain, deploy and i will do regular updates on it

How would you build the logic behind it since there is a rate limit on how many token can be sent?

you can use  some tokenizer package to calculate the amount of words you send. am try that and let y'all know

added this feature to the main branch. created a promptBuilder that calculates token size before sending


Update plan-teams-lifecycle.md

Added sentence in Stage 3: End, paragraph 2 to indicate that channels are also soft deleted for 21 days and can be restored before that duration.

Confirming this change with PM Praveen Vijayaraghavan.

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

@LolaJacobsen Wanted to let you know PR has been copyedited and is ready for final review, just waiting on Praveen's confirmation. Does he have a GitHub user? I could not find him. Thanks!

New PM contact for this feature area: Anwar Ali. I'm pinging him in Teams.

@anwara-ms please review this PR and let us know whether it's OK to merge. Or give us corrections.


feat: add docker image, push to registry

Codecov Report

Merging #116 (5b97336) into main (1b37382) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #116   +/-   ##
=======================================
  Coverage   94.33%   94.33%
=======================================
  Files          15       15
  Lines         777      777
=======================================
  Hits          733      733
  Misses         44       44

Continue to review full report at Codecov.

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


[User Story] - notation generates key and corresponding certificate for testing

Summary
As a tester, I want to generate key and corresponding certificate to test notation signing and verifying features
Intended Outcome

An RSA key and corresponding self-signed certificate can be generated in an easy way.
Testers can sign OCI artifacts using the key with notation sign command
Testers can verify signed OCI artifacts against the self-signed certificate with notation verify command
The RSA key and corresponding self-signed certificate are stored locally. The directory structure should follow section Signing key store of https://github.com/notaryproject/notation/issues/167
multiple keys and certificates can be generated given different host names
Tester can select which key and certificate pair to test notation signing and verifying.
Tester can remove specific key and certificate pair when they are not used

Additional context
Tester could be developer or any person who is interested in notation project and want to try notation features.
Work items

[ ] Update notation CLI spec for this user story
[ ] Implementation of generating RSA keys and corresponding self-signed certificates
[ ] Implementation of removing specific key and certificate
[ ] Implementation of notation signing and verifying against testing keys and self-signed certificates
[ ] Implementation of directory structure for Key and certificates according to Signing key store section of https://github.com/notaryproject/notation/issues/167

Just a note this work user story is important for our getting started scenarios.
Adopters need a quick and easy means to get started, without any dependency on a cloud provider.

I'm working on this work item. The generated keys & certs will be stored in {CONFIG}/notation/localkeys/.

Implementation of directory structure for Key and certificates according to Signing key store section of https://github.com/notaryproject/notation/issues/167

But the {CONFIG}/notation/signingkeys.json doesn't exist now, signing key information is tracked in config.json, there will be a breaking change to split the config.json file. Is is another work item? Do we need to finish it in RC1, or just keep the current config.json structure? The config example is here.

@JeyJeyGao Yes, the config.json should be split into config.json and signingkeys.json. It will be another work item and is in the scope of RC.1 or before.

One bug found here https://github.com/notaryproject/notation/issues/259, which broke this feature.

@yizha1  - Please consider the changes going in this fix  to not break the "directory structure" based trust store and verification experience spec. Rakesh is working on https://github.com/notaryproject/notation-go/issues/95


"client_id" is missing from ID token

Running my tests for PR #104 , I saw that one of them failed.
It is the test_token_exchange_change_client_id_token where expects to get ID token having a "client_id" claim.
But client_id claim is not there anymore.
Is this something that you changed in purpose?
@c00kiemon5ter

This is a test coming from OIDC Frontend.

Should be fixed by now! Can you verify that !
And if it's resolved can you accept the PR.

I have to dig into the code to see that there is a patch in our codebase for the token_exchange case.
So I close this issue and will approve the PR.


Add version tag variables for java api

Now that we don't hard code the image and api versions on wedeploy.com, should we add the java api? What would be a good naming system for it?
Use case is @mdelapenya's iot blogpost (#233)
cc @eduardolundgren @igr

We do have a version for Android already, but not for the Java one. https://github.com/wedeploy/wedeploy.com/blob/master/src/site.json#L8

Are you wanting to not add a Java one?

We don't have an official Java API anymore, we need to decide what to do about it.

If we are not going to have a Java API, how are we going to use it from Java applications?

We do need a Java API for sure. In the meantime, we should add a new tab on every code block that shows an example with curl. At least other people who doesn't know JS, Swift, Android will be able to use those APIs.

Closing since the Java SDK has not been released yet. When it's released we can add it here.


Boba Gateway - Pending Transaction UI Page Number Glitch (Rinkeby)

When you have 3 pending transactions, the boba gateway will add a new page prematurely. Initially it appears that the UI is correct, It shows "page 1 of 1"... However you can click on the right arrow and it glitches to page 2 of 1 and you will get an empty page

.

Great catch - on it.


Port all tests to use libperch

Currently, all of our tests have hardcoded host interfaces (printing, termination, firmware generally). I've already ported some of our demos and it seems pretty painless
This way we can just link a static library and get all of our host interface for free (so that when it changes slightly all of our tests don't break).

Note: Nominally the stack is Application (user-level) -> PanicRoom (user-level)-> libperch (firmware).  So users most likely won't be making direct calls into the firmware.  An example of direct use would be the kernel querying hartid.

What is libperch?
On Tue, Jul 16, 2019 at 8:42 AM Dan Petrisko<EMAIL_ADDRESS>wrote:

Note: Nominally the stack is Application (user-level) -> PanicRoom
(user-level)-> libperch (firmware). So users most likely won't be making
direct calls into the firmware. An example of direct use would be the
kernel querying hartid.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/black-parrot/pre-alpha-release/issues/223?email_source=notifications&email_token=AEFG5AAGZPF7RTR4ABFVWNTP7XT77A5CNFSM4IECACJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2BIZAQ#issuecomment-511872130,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEFG5AEBAJHYA4VB3LNEECTP7XT77ANCNFSM4IECACJA
.

Firmware library for emulation, mainly, but generally for anything we want to include in M-mode

Cool. What does perch mean? Like the fish?
On Tue, Jul 23, 2019 at 9:52 AM Dan Petrisko<EMAIL_ADDRESS>wrote:

Firmware library for emulation, mainly, but generally for anything we want
to include in M-mode
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/black-parrot/pre-alpha-release/issues/223?email_source=notifications&email_token=AEFG5AGJZMCM6YCIPIX2VCTQA4ZOBA5CNFSM4IECACJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2TYCLA#issuecomment-514294060,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEFG5AGEOXMIT6UIG2ITSL3QA4ZOBANCNFSM4IECACJA
.

No, like a perch that a BlackParrot roosts on

Ah got it!
On Tue, Jul 23, 2019 at 2:02 PM Dan Petrisko<EMAIL_ADDRESS>wrote:

No, like a perch that a BlackParrot roosts on
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/black-parrot/pre-alpha-release/issues/223?email_source=notifications&email_token=AEFG5AHCKUHE6FDUG46T2H3QA5WWTA5CNFSM4IECACJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2UNXSI#issuecomment-514382793,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEFG5AF5IJDUUAQBKYBBRRTQA5WWTANCNFSM4IECACJA
.

I agree. It might be more involved than linking all the test benches to 1 set of support files though. I added some code to syscall.c for beebs to pass ./configure and call the support's main function. I also commented out code from syscall.c so it didn't have function aliasing for littlefs_test and for other programs referencing newlib. The linker files have an extra line for the bsg dram end address that is used for code that references newlib but would be undefined for code that doesn't. The crt.S is also slightly different for these programs. However, the util.h isn't needed most of the time and encoding.h is always the same.

Originally posted by @TavioGuarino in https://github.com/black-parrot/pre-alpha-release/issues/208#issuecomment-503770435
We need to modify the linker script in libperch to be more general...


Add info about List widget v2

This PR adds the info about the usage of items and currentItem to use the input widgets inside the list widget.

@jsartisan when can we close this?

@vihar The changes haven't gone live yet. Just waiting for the changes to go live.

@vihar Let's merge this. Can you check the copy once. After that, we can merge this.

Everything looks great!


⚠ Bofrost.es has degraded performance

In 62636b8, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1550 ms

Resolved: Bofrost.es performance has improved in 11f0307.


Cannot relocate fsevents binary

Platform: macOS
package.json
{
  "name": "ncc-test",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "dependencies": {
    "chokidar": "^2.1.2"
  }
}

index.js
const chokidar = require("chokidar");

chokidar.watch(".", {}).on("all", (event, path) => {
  console.log(event, path);
});

ncc build index.js

Error:
Tims-MacBook:ncc-test timfish$ ncc build index.js
ncc: Module directory "/Users/timfish/Documents/Repositories/ncc-test/node_modules/fsevents/node_modules/node-pre-gyp/lib" attempted to require "aws-sdk" but could not be resolved, assuming external.
ncc: Module directory "/Users/timfish/Documents/Repositories/ncc-test/node_modules/fsevents/node_modules/node-pre-gyp/lib" attempted to require "aws-sdk" but could not be resolved, assuming external.
ncc: Module directory "/Users/timfish/Documents/Repositories/ncc-test/node_modules/fsevents/node_modules/node-pre-gyp/lib" attempted to require "aws-sdk" but could not be resolved, assuming external.
ncc: Module directory "/Users/timfish/Documents/Repositories/ncc-test/node_modules/fsevents/node_modules/node-pre-gyp/lib/util" attempted to require "npm" but could not be resolved, assuming external.
ncc: Module directory "/Users/timfish/Documents/Repositories/ncc-test/node_modules/fsevents/node_modules/node-pre-gyp/lib/util" attempted to require "node-gyp" but could not be resolved, assuming external.
ncc: Module directory "/Users/timfish/Documents/Repositories/ncc-test/node_modules/fsevents/node_modules/node-pre-gyp/lib" attempted to require "request" but could not be resolved, assuming external.
   0kB  dist/node-pre-gyp/bin/node-pre-gyp.cmd
   0kB  dist/nw-pre-gyp/package.json
   0kB  dist/node-pre-gyp/lib/util/nw-pre-gyp/package.json
   0kB  dist/node-pre-gyp/contributing.md
   1kB  dist/node-pre-gyp/appveyor.yml
   1kB  dist/node-pre-gyp/LICENSE
   1kB  dist/nw-pre-gyp/index.html
   1kB  dist/node-pre-gyp/lib/util/nw-pre-gyp/index.html
   2kB  dist/node-pre-gyp/package.json
   2kB  dist/package.json
   3kB  dist/node-pre-gyp/bin/node-pre-gyp
  13kB  dist/node-pre-gyp/CHANGELOG.md
  24kB  dist/node-pre-gyp/lib/util/abi_crosswalk.json
  30kB  dist/node-pre-gyp/README.md
1660kB  dist/index.js
1738kB  [10697ms] - ncc 0.15.2

Suspect it's due to this in the fsevents dependency:
var path = require('path');
var binary = require('node-pre-gyp');
var Native = require(binary.find(path.join(__dirname, 'package.json')));

I just tried this case out and it is working completely fine for me.
Are you running in Windows perhaps?

Ah I see you say macOS... would be odd if this was a Mac/Linux difference.
Perhaps try reinstalling to ensure the fsevents build is running? And the code definitely works without an ncc build?

I'll take another look into this today. chokidar bundles fine on Linux and Windows because fsevents is a macOS only optional module.

I've found a cross-platform module that uses node-pre-gyp in a similar way and gives the same warnings, although it is outputting a working bundle:
package.json
{
  "name": "ncc-test",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "dependencies": {
    "bcrypt": "^3.0.4",
  }
}

index.js
const bcrypt = require('bcrypt');

bcrypt.hash('s0/\/\P4$$w0rD', 10, function(err, hash) {
    console.log('Hash:', hash)
});

Build output
λ ncc build index.js
ncc: Module directory "C:\Users\tim\Documents\Repositories\ncc-test\node_modules\bcrypt\node_modules\node-pre-gyp\lib" attempted to require "aws-sdk" but could not be resolved, assuming external.
ncc: Module directory "C:\Users\tim\Documents\Repositories\ncc-test\node_modules\bcrypt\node_modules\node-pre-gyp\lib" attempted to require "aws-sdk" but could not be resolved, assuming external.
ncc: Module directory "C:\Users\tim\Documents\Repositories\ncc-test\node_modules\bcrypt\node_modules\node-pre-gyp\lib" attempted to require "aws-sdk" but could not be resolved, assuming external.
ncc: Module directory "C:\Users\tim\Documents\Repositories\ncc-test\node_modules\bcrypt\node_modules\node-pre-gyp\lib\util" attempted to require "node-gyp" but could not be resolved, assuming external.
ncc: Module directory "C:\Users\tim\Documents\Repositories\ncc-test\node_modules\bcrypt\node_modules\node-pre-gyp\lib\util" attempted to require "npm" but could not be resolved, assuming external.
ncc: Module directory "C:\Users\tim\Documents\Repositories\ncc-test\node_modules\bcrypt\node_modules\node-pre-gyp\lib" attempted to require "request" but could not be resolved, assuming external.
   0kB  dist\node-pre-gyp/contributing.md
   0kB  dist\node-pre-gyp/lib/util/nw-pre-gyp/package.json
   0kB  dist\nw-pre-gyp/package.json
   0kB  dist\node-pre-gyp/bin/node-pre-gyp.cmd
   1kB  dist\node-pre-gyp/lib/util/nw-pre-gyp/index.html
   1kB  dist\node-pre-gyp/LICENSE
   1kB  dist\node-pre-gyp/appveyor.yml
   1kB  dist\nw-pre-gyp/index.html
   2kB  dist\node-pre-gyp/package.json
   2kB  dist\package.json
   3kB  dist\node-pre-gyp/bin/node-pre-gyp
  13kB  dist\node-pre-gyp/CHANGELOG.md
  24kB  dist\node-pre-gyp/lib/util/abi_crosswalk.json
  32kB  dist\node-pre-gyp/README.md
 162kB  dist\lib/binding/bcrypt_lib.node
 996kB  dist\index.js
1238kB  [2104ms] - ncc 0.15.2

Yeah this sounds like a Mac-specific issue. Unfortunately I just got rid of my mac, so can't easily debug this now.
Can you share the exact runtime execution error that you get? The original posted in the issue is the build output not the execution output.

@timfish just to let you know the latest version of ncc and this loader have just been published with some fixes for MacOS, which may resolve some of the issues here.

@guybedford Regarding macOS, see #5

I just tested this exact replication case with the new ncc beta release and this is building fine for me, including emitting the fsevents.node file.
Closing as resolved, but please reopen if I'm missing anything.
I'll be PR'ing the integration test into ncc itself with the next batch of changes.

Although note that for support of require('asdf.node') files, this requires setting the asset relocation loader to run for these files. See the ncc configuration as an example here - https://github.com/zeit/ncc/blob/master/src/index.js#L146.

(I also just checked bcrypt and can confirm that is working too)


Keybindings Stop working after sometime of using the wm

First of all thanks for this great wm it is awesome but i have one problem that is the keybindings stop working after using only one app for sometime. After that if i open the window using the bar it opens fine but the binds do not work.

probably numlock? you can add numlock to ignore mod in the config

Sorry i am not able to understand the issue can you explain please.


[R000580] Rep. Peter Roskam

Rep. Peter Roskam:
http://roskam.house.gov
Likely contact form URL to start with:
http://www.house.gov/writerep

YMAL file not found. I am working on it.


Turtlebot3 Cmake Error: ROS NOETIC Installation

ISSUE TEMPLATE ver. 0.4.0

Which TurtleBot3 platform do you use?

[ ] Burger

Which ROS is working with TurtleBot3?

[ ] ROS 1 Noetic Ninjemys

Which SBC(Single Board Computer) is working on TurtleBot3?

[ ] Raspberry Pi 4

Which OS you installed on SBC?

[ ] Ubuntu preinstalled server (18.04/20.04)

Which OS you installed on the Remote PC?

[ ] Ubuntu 20.04 LTS (Focal Fossa)

Specify the software and firmware version(Can be found from Bringup messages)

Software version: [x.x.x]
Firmware version: [x.x.x]

Specify the commands or instructions to reproduce the issue.
Followed the ROBOTIS Turtlebot ROS Noetic installation video on youtube.

Copy and Paste the error messages on the terminal.

CMake Error at /usr/share/cmake-3.16/Modules/CMakeFindDependencyMacro.cmake:47 (find_package):
Could not find a configuration file for package "ignition-common3-graphics"
that exactly matches requested version "3.13.1".
The following configuration files were considered but not accepted:
/usr/lib/x86_64-linux-gnu/cmake/ignition-common3-graphics/ignition-common3-graphics-config.cmake, version: 3.10.0
/lib/x86_64-linux-gnu/cmake/ignition-common3-graphics/ignition-common3-graphics-config.cmake, version: 3.10.0

Call Stack (most recent call first):
/usr/lib/x86_64-linux-gnu/cmake/ignition-common3/ignition-common3-config.cmake:203 (find_dependency)
/usr/lib/x86_64-linux-gnu/cmake/gazebo/gazebo-config.cmake:250 (find_package)
turtlebot3_simulations/turtlebot3_gazebo/CMakeLists.txt:24 (find_package)
-- Configuring incomplete, errors occurred!
See also "/home/isharm2/catkin_ws/build/CMakeFiles/CMakeOutput.log".
See also "/home/isharm2/catkin_ws/build/CMakeFiles/CMakeError.log".

Please describe the issue in detail.
I am not sure, How to work through this issue!

Hi @ishaniis.
This error seems to occur because the Ignition package is not installed.
Please Enter the command below to install the package
apt install ignition-rendering3
Additionally, there is a link below for a case similar to this issue.
Please also refer to the link.
Thank you

This issue will be closed due to prolonged inactivity.  if the issue persists, feel free to reopen it.


correct column names in caliper reader

Resolves #247

This would be confusing, so we decided not to make this change. From hatchet's point of view, average time over MPI processes is still the main time column. If we see other columns such as min, max, sum, we'll consider using Caliper's metadata to rename those columns in the new Caliper reader.


Access to User after signing in by magic link

Hey!
I use magic link to authorize users. I have client-side plugin with onAuthStateChange event. When I click the link, after redirection to my site, there is SIGNED_IN event, but user.value is null (user = useSupabaseUser()). Why? How to fix it?

I am facing the same issue. After the redirect useSupabaseUser() does not deliver me a user.value but null. If I interact once more with the page (i.e. clicking on an internal link) I can properly grab the current user via useSupabaseUser().

I am facing this same issue after Google OAuth redirects. It works every so often and then just doesn't work other times. The user value sometimes is set and sometimes is not? Is there a way to manually set the user if it times out?

A workaround for that side of the problem is using watchEffect to wait for the user.value to change, like so:
onMounted(() => {   watchEffect( () => {       if (user.value) {           navigateTo('/xyz')       }     },     {       flush: 'post',     }   ) })
The issue of the use.value not updating is also present after signing out, tho. Is anybody looking into that currently?

I am also experiencing this issue using sign in with email and password. When testing locally user.value returns a value but when running in a hosted environment in Netlify user.value is null. I have also found that unfocusing and refocusing the browser tab populates user.value.


support for gzipped csv

I have added the gzip support. Let say the file path is .../test.csv.gz.

I include the match string condition like "*.csv.gz" in the config file.
Since the table name is wrong, cut the base when it ends with .gz. As a result, the base is now test.csv and make the table name as test same as before.
Check if the path ends with .gz when the file open, then add one more step to unzip the gzipped file.

Example query results

Results
Here is the sample csv file.
> cat test.csv
a,b,c,d,e
1,2,3,4,3
1,2,1,1,2
5,4,3,2,1
a,a,a,b,c

Let us gzip the file,
> gzip test.csv.gz

and then you can find the file is now gzipped.
> ls
test.csv.gz

Now, do steampipe query and the result is here.
Welcome to Steampipe v0.16.4
For more information, type .help
> select * from test
+---+---+---+---+---+---------------------------+
| a | b | c | d | e | _ctx                      |
+---+---+---+---+---+---------------------------+
| a | a | a | b | c | {"connection_name":"csv"} |
| 5 | 4 | 3 | 2 | 1 | {"connection_name":"csv"} |
| 1 | 2 | 1 | 1 | 2 | {"connection_name":"csv"} |
| 1 | 2 | 3 | 4 | 3 | {"connection_name":"csv"} |
+---+---+---+---+---+---------------------------+

I have updated my code to deal with the BOM skip part.

Hey @daeho-ro , thanks for raising this PR! Just commenting to let you know this is on my radar to review tomorrow, sorry for the delay, I've been working through my backlog for the moment.

@daeho-ro Sorry for the long wait for the review, thanks for adding this new feature! We'll plan for a release in a new plugin version early next week.

No problem!


Fixes #476 Gets bounds and renders the image accordingly as the map view

Simple test

[ ] Check if the way map looked before while putting the marker is the same way map looks after the tweet image is rendered.

The colour of the marker changed to red and the map shifted a bit right.Nothing much.
If thats expected then its good to merge

Thats expected the color change, because the server paints it in red over the image, where as we are using a blue marker.