control transfer failed (IDFGH-13040)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.4-dev-826-g8760e6d2a7
Espressif SoC revision.
esp32-s3
Operating System used.
Windows
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
CMD
Development Kit.
wroom32 devkitc
Power Supply used.
USB
What is the expected behavior?
No control transfer errors.
What is the actual behavior?
depends;
sometimes it works
other times:
E (21420) USBH: Dev 1 EP 0 STALL
E (21420) ENUM: [0:0] Control transfer failed, status=1
some device I always get
E (21420) USBH: Dev 1 EP 0 STALL
E (21420) ENUM: [0:0] Control transfer failed, status=4
Steps to reproduce.

I ran the usb host lib exmaple
ran monitor
plugged in a device
...

Debug Logs.
PS C:\Users\Administrator\Desktop\usb2llapi\usb_host_lib> set IDF_PATH=c:\Users\Administrator\Desktop\esp\esp-idf
PS C:\Users\Administrator\Desktop\usb2llapi\usb_host_lib> C:\Users\Administrator\.espressif\python_env\idf5.4_py3.11_env\Scripts\python.exe c:\Users\Administrator\Desktop\esp\esp-idf\tools\idf_monitor.py -p COM9 -b 115200 --toolchain-prefix xtensa-esp32s3-elf- --target esp32s3 c:\Users\Administrator\Desktop\usb2llapi\usb_host_lib\build\usb_host_lib_example.elf
--- WARNING: GDB cannot open serial ports accessed as COMx
--- Using \\.\COM9 instead...
--- esp-idf-monitor 1.4.0 on \\.\COM9 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x8 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce2810,len:0x1790
load:0x403c8700,len:0x4
load:0x403c8704,len:0xcf0
load:0x403cb700,len:0x2d88
entry 0x403c8928
I (27) boot: ESP-IDF v5.4-dev-826-g8760e6d2a7 2nd stage bootloader
I (27) boot: compile time Jun 14 2024 17:48:55
I (27) boot: Multicore bootloader
I (31) boot: chip revision: v0.2
I (35) boot.esp32s3: Boot SPI Speed : 80MHz
I (40) boot.esp32s3: SPI Mode       : DIO
I (45) boot.esp32s3: SPI Flash Size : 2MB
I (49) boot: Enabling RNG early entropy source...
I (55) boot: Partition Table:
I (58) boot: ## Label            Usage          Type ST Offset   Length
I (66) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (73) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (81) boot:  2 factory          factory app      00 00 00010000 00100000
I (88) boot: End of partition table
I (92) esp_image: segment 0: paddr=00010020 vaddr=3c020020 size=0bbd4h ( 48084) map
I (109) esp_image: segment 1: paddr=0001bbfc vaddr=3fc92800 size=028f4h ( 10484) load
I (112) esp_image: segment 2: paddr=0001e4f8 vaddr=40374000 size=01b20h (  6944) load
I (119) esp_image: segment 3: paddr=00020020 vaddr=42000020 size=1e160h (123232) map
I (148) esp_image: segment 4: paddr=0003e188 vaddr=40375b20 size=0cc1ch ( 52252) load
I (166) boot: Loaded app from partition at offset 0x10000
I (166) boot: Disabling RNG early entropy source...
I (178) cpu_start: Multicore app
I (187) cpu_start: Pro cpu start user code
I (187) cpu_start: cpu freq: 160000000 Hz
I (187) app_init: Application information:
I (190) app_init: Project name:     usb_host_lib_example
I (196) app_init: App version:      1
I (200) app_init: Compile time:     Jun 14 2024 17:48:23
I (206) app_init: ELF file SHA256:  febbb507c...
I (212) app_init: ESP-IDF:          v5.4-dev-826-g8760e6d2a7
I (218) efuse_init: Min chip rev:     v0.0
I (223) efuse_init: Max chip rev:     v0.99
I (228) efuse_init: Chip rev:         v0.2
I (233) heap_init: Initializing. RAM available for dynamic allocation:
I (240) heap_init: At 3FC95958 len 00053DB8 (335 KiB): RAM
I (246) heap_init: At 3FCE9710 len 00005724 (21 KiB): RAM
I (252) heap_init: At 3FCF0000 len 00008000 (32 KiB): DRAM
I (258) heap_init: At 600FE100 len 00001EE8 (7 KiB): RTCRAM
I (265) spi_flash: detected chip: generic
I (269) spi_flash: flash io: dio
W (273) spi_flash: Detected size(16384k) larger than the size in the binary image header(2048k). Using the size in the binary image header.
I (286) sleep: Configure to isolate all GPIO pins in sleep state
I (293) sleep: Enable automatic switching of GPIO sleep configuration
I (300) main_task: Started on CPU0
I (310) main_task: Calling app_main()
I (310) gpio: GPIO[48]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (320) gpio: GPIO[0]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:2
I (330) USB host lib: Installing USB Host Library
I (360) CLASS: Registering Client
(((plugged in device here )))
E (21420) USBH: Dev 1 EP 0 STALL
E (21420) ENUM: [0:0] Control transfer failed, status=4
I (21800) USB host lib: No more devices

More Information.
I have many USB devices so it maybe common for this issue to occur. but I do not know the code well enough to know where to look. If I knew where to add some debug I may be able to see what is causing this issue.  With one device I always get the status 4, so that maybe a device problem but I will need to know what initialed this request. Where did it fail, on what control transfer?
My device board had a otg jumper I have to use to get power to the OTG port. I am running  the jtag via the other USB com port. Since I see debug messages I assume that is all done correctly. I'm new to platform.io so I will not know much about how its set up. Let em know what else I need here.
NOTE: my devices with the issue be it seldom or always have boot loaders. These boot loaders must load first then the device loads. Maybe I can add a delay somewhere to circumvent the two usb enumerations? It could just be too fast for this code.
also noticed the vendor name tacks on another character
example 1
I (443615) CLASS: Getting Manufacturer string descriptor
Sony8  <--- should be Sony
example 2
I (443615) CLASS: Getting Manufacturer string descriptor
Bliss-Box$<--- should be Bliss-Box

Hi @ulao,
Thanks for reporting the problem.
You are right, this is a regression which has been added recently. Sorry for any inconvenience.
We have already fix it internally, so the next iteration of updating the esp-idf here will solve the problem.
When device doesn‘t have a descriptor (for example String Descriptor) it could STALL the EP during control transfer.
This is not the issue for string descriptors (probably one of your devices or bootloaders don‘t have some string descriptors, that is why the control request is STALLed) .
Please, stay updated and try again when the fix will be available.
Regarding the extra symbol in the end of the string descriptor - I will take a look ASAP.

wow thx for the update! I was debug the heck out of this but glad to know I can stop. yes I do not have a serial or version
//case 0x03: no serial
//case 0x04: no version
in my devices.
So I'm new to this repo, when should I expect updates? Are they on a weekly/nightly or other rotation?

Hello @ulao , the master branch is always considered to be work in progress, we advise users to start working with latest stable version, which is v5.2.2 at the time of writing.
The fix is already in master branch, so just update your local repo with git pull. See fix commit https://github.com/espressif/esp-idf/commit/d214c482f64c90deb7e55576adcf1a4a4cfe4bb3
More details about esp-idf release plan are in official docs

yes the latest code does work nice work, also the last charter changed now, so something altered that bug, but  I know you have not looked in to to yet.
One other slightly off topic question. For my genera ESP question I find esp32.com  useless, for platform.io I find community.platformio.org exceptional but for this repo I'm lost when I need help I do not want to open bugs. Is there no way to chat about how the overall culture works? This repo changes the way things work and confuses anyone trying to help me.  I have so many small but much needed question I find that are specific to this repo. Is there any means of help out there?

well its adding up too much for me, so I guess I will just make more bug reports but I personalty feel that incredible inefficient. Please consider a chat group maybe a discord?

For my general ESP questions I find esp32.com useless, for platform.io I find community.platformio.org exceptional but for this repo I'm lost when I need help. I do not want to open bugs. Is there no way to chat about how the overall culture works?

The way we want it to be is:

Use esp32.com forum for general questions, ideas and so on
Use GitHub issues for bug reports

But I see your confusion. The developers are overloaded with similar requests and we often prioritize GH issues...


Setting cookie expiry with moment().toDate()

I recently tried setting a cookie with an expiry of a particular date using the moment().toDate() function. The Express docs state that the value for the expires option has to be a date which moment returns, sounds good but the cookies expiry date just wasn't being set properly when I checked in the browser.
var cookieDate = moment().add(6, 'months').toDate();
res.cookie('foo', 'bar', { expires: cookieDate });

After some messing about I found out that I had to wrap the toDate object in a new Date like below to get it to work.
var cookieDate = new Date(moment().add(6, 'months').toDate());
res.cookie('foo', 'bar', { expires: cookieDate });

Is there a reason why the date object returned by moment isn't valid?

It seems to be working when I just tried it. Can you provide the following information:

The version of Node.js you are using.
The version of this module you are using.
The version of Moment.js you are using.
A mini Express app that just has one route that sets the cookie with your code. This will help make sure that we are using exactly the same code to remove as much variables as possible between our tests.

I can't replicate the issue inside a mini Express app example on the same environment. It's must be something specific to my app not express.

I can't seem to replicate the issue in an example app with the same set up. It must be something I've done within my application itself. I'll do some more debugging within my app over the next couple days and post any solutions I find here, just in case someone else has a similar issue.

@silverlight513 any updates? If you couldn't find anything interesting, can we close this?

This can be closed, I returned to the bug I had and re-wrote that section and now it's working as desired.
Thanks for being willing to help and making a great community.


Remove workaround for 'fn run' scoping.

Fixed by https://github.com/kubernetes-sigs/kustomize/pull/2165

Nice! LGTM


pip install sequence-jacobian does not work for me

Dear all,
thank you for making your amazing codes publicly available.
I learned so much already, not only from your paper, but especially also from your code =) (so far from the old version).
Just wanted to say that, for me,
pip install sequence-jacobian
keeps returning
ERROR: Could not find a version that satisfies the requirement sequence-jacobian
ERROR: No matching distribution found for sequence-jacobian.
Any recommendation on what to do would be appreciated.
Many greetings and thanks again,
Marlon

Hi Marlon,
Yes, I'm afraid I got ahead of myself with that. We decided to do a bit more polishing and sequence_jacobian is not on PyPI yet. It's a matter of 1-2 days. In the meantime, please install from git via:
pip install git+https://github.com/shade-econ/sequence-jacobian@master

Best,
Bence


add tabbar for matches

fixes #152

Use TabBar component for matches
Restructure pages for matches/players
Externalize some strings
Add headings to some elements

Reviewers:
@mike-robertson
@nicholashh
@albertcui

Approved pending comments


Can I change the jump height?

Hi, really good GM tool, but I wonder if I can set the parameters? I can't jump up and grab the rope.. thanks

You must modify the source and recompile.
In MapleCharacter.cs-> line 133,134
JumpSpeed
JumpHeight


[feature request]: export load_workspaces function

Hi! Nice plugin :+1:
Could you make load_workspaces function public or add to api something similar like get_workspaces? I started using this as section in https://github.com/sidebar-nvim/sidebar.nvim but I had to replicate that function as there is no way to get list of workspaces. Only print them. :)

Sorry. I'm blind. :)

No worries! I forgot to add it to the readme. It is in the workspaces.txt doc though :)

Added to readme!


doesnot work with exe files compiled with pyinstaller

It works before compilation, but after compilation the key_received function is not executed
Any ideas?
I tried with python 3.11.5 and 3.12.0 and both did not work.

It works before compilation, but after compilation the key_received function is not executed Any ideas? I tried with python 3.11.5 and 3.12.0 and both did not work.

I managed to make it work by changing this piece of code on sdl2.py:
if check_os('win') and is_64_bit():
    with SDL2_WIN64.as_file() as sdl_dll:
        os.environ.setdefault('PYSDL2_DLL_PATH', os.path.dirname(str(sdl_dll)))
        import sdl2
elif check_os('win'):
    with SDL2_WIN32.as_file() as sdl_dll:
        os.environ.setdefault('PYSDL2_DLL_PATH', os.path.dirname(str(sdl_dll)))
        import sdl2
else:
    import sdl2

with:
def sdl_dll_path(dll):
    """Get absolute path to resource, works for dev and for PyInstaller"""
    try:
        # PyInstaller creates a temp folder and stores path in _MEIPASS
        base_path = sys._MEIPASS
        return os.path.join(base_path, dll)
    except Exception:
        return os.path.dirname(dll)

if check_os('win') and is_64_bit():
    with SDL2_WIN64.as_file() as sdl_dll:
        # os.environ.setdefault('PYSDL2_DLL_PATH', os.path.dirname(str(sdl_dll)))
        os.environ.setdefault('PYSDL2_DLL_PATH', sdl_dll_path(str(sdl_dll)))
        import sdl2
elif check_os('win'):
    with SDL2_WIN32.as_file() as sdl_dll:
        os.environ.setdefault('PYSDL2_DLL_PATH', os.path.dirname(str(sdl_dll)))
        import sdl2
else:
    import sdl2

Then, in the pyinstaller command I added this:
--add-binary "<venv folder>\Lib\site-packages\pyjoystick\sdl2_win64\SDL2.dll:."
It only works for 64bits. If you need for 32bit change the pyinstaller command with:
--add-binary "<venv folder>\Lib\site-packages\pyjoystick\sdl2_win32\SDL2.dll:."
It's a dirty solution, but I hope it works for you too.
Greetings

It worked!!!
Thanks for the reply.
I respect you!!!


Remote url for "associated revisions" on issue page is empty

Good plugin !  :smiley: :+1:
The remote url for "associated revisions" on issue page is empty.

So if checked option "Replace the Redmine Revision Links", revision links will disappear.

Hm, not sure why this is happening without seeing the values saved with configuration.  Can you provide additional information?

Figured out what was happening.  You did not yet enter the URL for the remote repository as specified in the README section Repository Settings.
see: https://github.com/tleish/redmine_remote_revision_url#repository-settings
Note: I also updated the plugin to handle entries left blank.  When there is no URL, the plugin will not make any changes to the page.

@tleish here is my setting, use new version but still not showing url on issue page.
Did i miss something?

I just tested 2.6.5 didn't have any problems?  Take a look at your repositories table in the database.  Is there more than one entry for your git repo?

@tleish your are correct, i do have same repo in two project because it's a common sub-module included by two project

Then you may have edited the URL for one, but not the other

Nice! the url shows now!!
So can it be fixed? e.g. select repo by it's project id or other methods?

You have a good suggestion, however I think sometimes we try to get too smart with software.  If for some reason you want the URL to show in one project but not another, then being to smart with the code would not allow a user to disable it and only show it in the one repo.
Another scenario.  Let's also assume for a minute that there were 2 repository entries, and only one contained the Remote URL.  Then the Remote URL displayed for both repositories all over the site.  Then later, the repository with the URL was deleted and all of the sudden the Remote URL disappeared from all projects.  Unexpected behavior.
Redmine treats the repos completely separate in the database, even if they share the same path.  Each one has their own set of changes in the database, etc.  The current remote URL model follows the same pattern that Redmine has set.  Each repo entry has it's own copy of a remote URL.  If you want the remote URL to show up in both, simply enter it twice to again add that same URL to the same linked repo in another project.
Glad we solved the problem.  Enjoy!


gen-payload: Add sleep between image sync and tagging

Codecov Report
Base: 35.45% // Head: 35.40% // Decreases project coverage by -0.05% :warning:

Coverage data is based on head (c6db34c) compared to base (29fc1c0).
Patch coverage: 26.31% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #731      +/-   ##
==========================================
- Coverage   35.45%   35.40%   -0.05%
==========================================
  Files          47       47
  Lines       11779    11831      +52
  Branches     2576     2519      -57
==========================================
+ Hits         4176     4189      +13
- Misses       7311     7349      +38
- Partials      292      293       +1

Impacted Files
Coverage Δ

doozerlib/cli/__main__.py
0.00% <ø> (ø)

doozerlib/cli/images_streams.py
0.00% <ø> (ø)

doozerlib/image.py
33.20% <0.00%> (-0.14%)
:arrow_down:

doozerlib/metadata.py
58.13% <0.00%> (-1.25%)
:arrow_down:

doozerlib/runtime.py
26.31% <20.00%> (-0.06%)
:arrow_down:

doozerlib/cli/release_gen_payload.py
59.77% <36.36%> (-1.63%)
:arrow_down:

doozerlib/assembly.py
73.61% <100.00%> (+0.16%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

/lgtm


Move config path generation into the service config for reusability

As of now, if a node wants to store its own information in the configuration directory chose through the cli, it has no way of knowing which directory that is supposed to be. This PR refactors the Configuration and its helper functions into a single entity that a) decides upon all directories by using its base directory, b) means every other component now only needs access to config to figure out the correct place to store stuff and c) allow nodes to store their own specific configuration and cache files.

waiting for resolving and @bkchr's signoff.

addressing some minor refactor. please wait before merging.

finally pushed.


CHANGELOG & pyproject file edits.

↪ Pull Request

💻 Examples

✔ PR Todo

[ ] Added/updated testing for this change
[ ] Included links to related issues/PRs
[ ] Update relevant docs + docstrings
[ ] Update the CHANGELOG under the current -dev version:

Add changelog entries under any that apply: BREAKING CHANGES, NEW FEATURES, BUG FIXES.
 I'm going to close this PR and re-cut the branch correctly


Copying PULDatacite service class from PDC Describe

Adjusting the classes to not publish the DOI since there is no current requirement for that functionality
refs #257

Nice!


Vue JS version 3

Hi! any plans for an upgrade to CLI v4?

Heya, been off for a while, and somehow my mail client lost the mail. ^_^
I'll work on CLI v4 soon, expect a new update to master. :)

@StefanPostma hello
"@vue/cli-service": "^4.5.4" is an installed version, did you mean perhaps an upgrade to the Vue version?

sorry i meant Vue JS version 3 :)

@StefanPostma Gotcha, I'll work on that ^_^

Closing the issue due to inactivity


Update UI and Styling for Contact Management App

Closes: #823

Title: Update UI and Styling for Contact Management App
Name: Mouhamadou Awalou
Idenitfy yourself: Contributor in Hacktoberfest

Describe the add-ons or changes you've made 📃
In this contribution, I have updated the UI and styling of the Contact Management App located in the advanced section of the Angular-js projects. The changes include improved visual elements for better user experience, including a responsive layout, updated color schemes, and enhanced component styling.
Also,  updated the readme.md file of this project by replacing the screenshots with the new look.
Screenshots 📷

Type of change ☑
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist: ☑

[x] My code follows the Contributing Guidelines & Code of Conduct of this project.
[x] This PR does not contain plagiarized content.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] My changes generate no new warnings.

Note to reviewers 📄
Please review the UI changes and provide feedback on the overall design and usability improvements. I appreciate your input!. The background image used is a free picture downloaded from freepik.com.

Can you tell what you have improved except bg addition?

Can you tell what you have improved except bg addition?

I've made serceral improvements beyond just adding the background image. Here are the changes and improvements I made:

[x] Added toastr notifications for all operations ( Add, Update, Delete).
[x] Updated the subscription syntax to follow best practices.
[x]  Removed unnecessary full-page reloads by notifying the contact list component via the contact service, ensuring smooth updates.
[x]  Added meaningful comments to help other developers understand the changes.
[x]  Improved UI layout by making the header fixed and placing the search bar in the header.
[x] Added a "No contact found" message when the contact list is empty.
[x] Updated the README.md for better documentation and understanding.

Delete all the .angular cache files and other any un-necessary files.

Hi @Avdhesh-Varshney. Done, I've pushed the requested changes, and all feedback has been implemented.


'Type conversion functions' page requires scrub

I'm aiming to make a PR in respect of this ISSUE at some point. The changes I have made in my fork so far for this ISSUE  do not at this time represent a full scrub.
It seems quite likely that the 'Returns for CStr' section on the 'Data type summary' page should be moved to a different page. Moving it to the 'Type conversion functions' page, as part of the implementation for this ISSUE, perhaps is the right thing to do.
You can see what progress I've made so far for this ISSUE, at the following address {the commit message(s) provide explanations of the changes}:

'type-conversion-functions.md' changes.

If you would like me to PR these changes straight-away, or by a certain date, let me know.

@MarkFern If you're absolutely sure that the changes you're making are accurate, go ahead and submit all the updates for this page as one PR. Also, if you think the Returns for CStr section on the data type summary page should go on this page, feel free to move it. Thanks.

So you have a preference for me to PR what changes I have now rather than after a period in which I'm able to mature & increase the changes (assuming I've checked the current changes thoroughly)?

@MarkFern Well, if you're not finished yet, please wait. It's better to submit these as PRs when you're absolutely sure of the changes.
So for all the issues that you submitted, are you saying that you're still working on them? If so, I'll disregard them for now. When you're ready for changes to go live, go ahead and submit them as PRs. Thanks. I'm not sure who else is actively monitoring this repo, so you may want to get feedback from folks on Stack Overflow or elsewhere if you're not sure about your changes.
Tip: I've noticed that you tend to put apostrophes around links or sections; that is not necessary, and I'll have to eventually edit them out. So just a note for the future.

@MarkFern By the way, I just fixed the Fix and Int functions link that was formatted incorrectly, so you can remove that fix from your PR when you submit it. Thanks for catching that.

Off-topic
To: @Linda-Editor.

...
So for all the issues that you submitted, are you saying that you're still working on them? If so, I'll disregard them for now. When you're ready for changes to go live, go ahead and submit them as PRs.
...

Yes, I'm still working on them. I've tried to put time-frames on how long it will take for the related PRs to be made.

Tip: I've noticed that you tend to put apostrophes around links or sections; that is not necessary, and I'll have to eventually edit them out. So just a note for the future.

Thanks for pointing it out. I had a look at some of your edit passes and noticed that you were make corrections according to a certain convention used. I'll try to follow that convention.

@MarkFern Thanks. As I may have mentioned before, I'm doing a page-by-page scrub of this repo. I've done all the Language Reference topics already, so thanks for following the formatting that's on those pages. For API topics, I've done Access and half of Excel already. Let me know if you have any questions.

Off-topic
To: @Linda-Editor.

@MarkFern Thanks. As I may have mentioned before, I'm doing a page-by-page scrub of this repo. I've done all the Language Reference topics already, so thanks for following the formatting that's on those pages. For API topics, I've done Access and half of Excel already. ...

Yes, actually it's because I realised that others might be doing things to the documentation and that those things might interfere with my own planned changes, that I decided to start making these in-progress ISSUEs. Good to know you've already finished with the Language docs as at the moment, I only have proposals for those docs (so hopefully we won't "step on each other's toes"). :relaxed:

@MarkFern Posting these as issues vs. PRs is a good idea; otherwise, your fork will get out of sync with the updates I'm making everyday. I'm not working in the Language Reference section right now, but will occasionally make a random fix, so when it's time to submit your PRs, please do a fresh clone of the master repo for your fork, and then submit the PRs right away. Also, like I mentioned before, wait to submit the PRs when you know everything is final (when you don't have any plans to keep updating the topic). Obviously there could be changes later, but as far as you know for now, your changes will be ready to go live and not need further editing. Let me know if you have any questions about that. Also feel free to post your questions on Stack Overflow to get some more collaboration if you don't hear from anyone in this repo. Thanks!

VBA's type-conversion functions are documented here in the VBA language specification. The content is useful content that doesn't currently appear in VBA's main documentation.

[ ] Make sure 'Probably same range as Double for numerics' text is correct. A larger range may in fact be available because of the Variant Decimal sub-type.


Add docker support

Added docker support to run slate. Please check and merge this pull request.
Thanks  :octocat:

I submitted a pull request for Docker Support a while back, and it was rejected.  See: https://github.com/lord/slate/pull/761

Yup, thanks for the suggestion, but we don't keep the docker image in the main repo for the reasons listed there. We love edits/fixes to the Docker wiki page though!

@lord Sorry.  I missed to noticed the previous PR.

@derks  I missed to notice .


The result problem

I have tried to reproduce the code. The code ran smoothly but the result was far below the ones as you mentioned in the paper, I used the weights you provide and max mIoU was 0.11. When I visualize it, it's totally messy. I was wondering the reason.

Hi,
Thanks for contacting us, this is a well-known issue: https://github.com/BCV-Uniandes/DMS/issues/21. Could you please try and follow the instructions posted there? That should fix the issue. If you keep experiencing problems, feel free to continue the discussion here.

@andfoy Great thanks for your timely reply. I followed the instruction to update the SRU to 2.1.3 which already support Prnvrtc 9.2. But my problem is still there.
python -u -m dmn_pytorch.train_gai --data referit_data --dataset referit --val val --backend dpn92 --num-filters 10 --lang-layers 3 --mix-we --save-folder weights --snapshot dmn_referit_weights.pth --epochs 0 --eval-first
Evaluation done. Elapsed time: 1035.489 (s)
Maximum IoU: 0.1528985351324 - Threshold: 0.0000000000000
I couldn't add --high-res because of out of memory problem, I had nvidia 2080 with 8G memory. I don't know the reason why it's so easy to leak.
Thanks for your consideration.

P.S: Dependency:
Python 3.6,8
Pytorch 1.0.1
CUDA 10
sru 2.1.3
prnvrtc 9.2
Window 10

I'm closing this one in favour of #21


[GLUTEN-5775][CELEBORN] Fix invoke celebornShuffleId exception

What changes were proposed in this pull request?
Fix invoke celebornShuffleId exception.
(Fixes: https://github.com/apache/incubator-gluten/issues/5775)
How was this patch tested?
Manual test.

LGTM. Thanks!


feat: properly handling repository inheritance (with specific-to-gene…

…ric precedence)

Codecov Report

Merging #116 (1003821) into main (d57eae1) will decrease coverage by 0.11%.
The diff coverage is 81.81%.

@@             Coverage Diff              @@
##               main     #116      +/-   ##
============================================
- Coverage     85.82%   85.70%   -0.12%
  Complexity       35       35
============================================
  Files            31       31
  Lines          2546     2553       +7
  Branches        280      281       +1
============================================
+ Hits           2185     2188       +3
- Misses          244      247       +3
- Partials        117      118       +1

Impacted Files
Coverage Δ

...a/com/decathlon/tzatziki/steps/SpringJPASteps.java
77.60% <81.81%> (-1.22%)
:arrow_down:

.../main/java/com/decathlon/tzatziki/utils/Types.java
61.70% <0.00%> (-2.13%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


mxnet-cu100 vs mxnet-cu100mkl vs mxnet

I'm a bit confused as to which packages i need and the benefits of one vs the others.
Currently i have mxnet 1.4.1 installed and the project i have runs fine on a CPU,
I'm using a machine with a GPU that has NVIDIA 418.40.04 drivers and CUDA 10.1  installed.
So ideally id like to use that.
Do i need both mxnet in addition to mxnet-cu100/mkl installed ?
What are the differences mxnet-cu100 vs mxnet-cu100mkl ?
Hoping this answer clears up questions others might have as well.

It's a good question.
mxnet-cuXX with cuDNN acceleration, good performance on GPU
mxnet-cuXXmkl with both cuDNN and MKL-DNN library acceleration, good performance on both CPU and GPU.
http://mxnet.incubator.apache.org/versions/master/install/index.html?platform=Linux&language=Python&processor=CPU

mxnet-cu92mkl means the package is built with CUDA/cuDNN and MKL-DNN enabled and the CUDA version is 9.2.

Suppose the question is answered. Closing now and feel free to re-open.


 Latest version is currently 6.0.0
Is your question already answered in the tutorials and guides —> https://patchthecode.github.io/
If you just upgraded from version 5.0.1 or from the swift3 branch, function names have changed. So please make sure they match.

Like this project? Consider supporting by leaving a star rating. :)
Thanks,
Jay

http://www.media.tv?/mediaTVNetwork/http://www.Doctype.com?/Elgato-Avea-Adroid-EyeTV-network-For-IpadTouch-Power’s-by-iOS-hp-cloud-Companies-links-with-A-Googlemaps-in-all-the-Dells-smart-Drives-computers-upgrades-for-TV’s-apps-wifi’s-in-links-to-all-myself-Accounts-Banks-online-myAccounts-publics-Accounts-and-bank’s-Accounts-online-in-public-accounts-linked-in-to-all-myself-Banks-into-My-Business-onlines-in-Public’s-Accounts-Too/Elgato-Network/https://gaming.youtube.com/watch?v=IjQ_1C6xfUc&mweb=1/Gamingyoutube-live-Broadcastin-playlists-autoplay-links-flashplayers-on-my-youtube-channels/Digital-3D-HD-directvNetwork/Links-Xfinity-x1-platforms-live-connection-it-is-now-update-for-use-Haiti.net/http://www.Doctype.com?/http://www.media.tv?/https://gaming

Invalid issue.


use underscore impls where we can

aren't those the default in synstructure now? https://docs.rs/synstructure/latest/synstructure/struct.Structure.html#method.underscore_const


Create delete_deployment.rst

How to delete obsolete binder repo #150

@choldgraf I noticed this open PR, is this something I can help bring to the finish line, or is this one stale?  Let me know just trying to find places to help!

oops! arg it looks like we missed this one. Sorry @garej ! I think what we'd need to do is add a reference to this page in the toctree of an index file somewhere so that Sphinx picks it up (the content looks correct to me). Though this might be tough as the branch no longer exists 🤔🤔🤔


Compressor patch example

I'm going to merge the new compressor version which does end up making this really loud on the patch with the improved auto makeup gain feature added.
You should be able to hack around it by just setting the output to 0.5 after the compressor. Since there's an extra 6dB of headroom on the patch. Might also be a bit more dB accurate if you multiply the input by 2 going in. (If you do add these little hack-fixes I'd document why in comments so we can fix it if/when we add a nominal 0dBfs setter to DaisySP).


Can not build in simulator on mac m1 device

It is working fine on device but when i run for simulator on my m1 device it gives me this error.
Could not find module 'DynamicColor' for target 'x86_64-apple-ios-simulator'; found: arm64, arm64-apple-ios-simulator

How do you import the library?

Using cocoapod. Note that it was working fine before m1.

Okay i solved this problem when I used pod 'DynamicColor', '~> 5.0.0' this in my podfile. Previously I was only using pod 'DynamicColor' as a result it was getting 4.2 version. But to update i have to change my deployment target to ios 11. Thank you @yannickl


version 1.4.0 not in tags.

hello ,
when I try bower install<EMAIL_ADDRESS>I get failes message, show result
Available versions in https://github.com/imulus/retinajs.git: 1.3.0, 1.2.0, 1.1.0, 1.0.1, 1.0.0.
pls add 1.4.0 too tags ,thx u.

Hi @hetz we are planning on releasing version 2.0 soon and will make sure both 1.4 and 2.0 are available on Bower.


Weapon that passes through walls at certain levels

I don't know if other people have reported this problem, but on the Carrington Villa level, the weapons go through walls, regardless of the NTSC, PAL or JPN version.

Does that still happen on the very latest build?

That's alright, thanks for checking.


TES3Merge serious error?

TES3Merge.log

So apparently I was using both MCA names 8.1 and MCA 8 by abot. I disabled MCA names 8.1, which solved the issue.

You're also using a very old version of TES3Merge. 0.8 shouldn't give you the issues 0.6 did.


Identify level attribute by key

While the a.Value.Kind() is probably more type-safe, I would still prefer the use of a.Key, since we can compare it against constant string.

Should have used TZ="" go test ./... -tags=faketime instead of go test ./... to test this.
After recheck on code, let's forget this.


Add feature request template

Signed-off-by: Ruchi<EMAIL_ADDRESS>Pull Request Template
Description
Added a feature request template so that any d=contributor who has an idea and wants to create a issue for the same it would be created under feature request template
CC: @joewxboy
Fixes #146
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Additional Context (Please include any Screenshots/gifs if relevant)
...
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented on my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have checked my code and corrected any misspellings
[ ] I have tagged the reviewers in a comment below in case my pull request is ready for a review
[ ] I have signed the commit message to agree to Developer Certificate of Origin (DCO) (to certify that you wrote or otherwise have the right to submit your contribution to the project.) by adding "--signoff" to my git commit command.

@joewxboy @unnati914  plz review my PR, thanks.

Thanks. In the future, let's:

Decouple the Gemfile updates from the feature request updates.  This should be two separate fixes.
Add Issue-146:  to the beginning of the PR title.

Sure, could you please elaborate more on the first point so that I could get a clear idea of what actually has to be done?


Update Debug Information Files Documentation

Currently, there's a lot of in depth documentation about uploading our own debug files. However, as mentioned over in sentry-cli, this issue has been mostly resolved by adding electron to the debug frameworks.
This is a great solution - however, this is not mentioned anywhere in the current Electron docs, which led me on a long quest to find and unsuccessfully upload dSYM files to Sentry.
For future users, can we please update the documentation to include information about this very important option?
And even better, is there a way to have this auto-enabled for all electron projects? :)

Ah, I didn't see it there! Apologies on my end for missing that.
I was looking in this section here:
https://docs.sentry.io/platforms/javascript/guides/electron/data-management/debug-files/
When I searched for 'debug' in the docs, this section was pulled up, and actually I don't see the section you're linking to anywhere in the top results.

Also, in the section you referenced, I don't want to be too elementary, but it helped to have the screenshot to help give some extra emphasis to it. It would be easy to miss as it is. :)

I think there might have also been some discussions over whether we can have these debug repositories automatically enabled when users select Electron as a project type.

@tsekiguchi cool, thanks!
For images, you can create an img folder relative to the mdx file and use markdown image syntax. For example: https://github.com/getsentry/sentry-docs/blob/1715fe49162cc3b55a2ddafb8f3f251a524afa35/docs/product/codecov/how-it-works.mdx
Let me know if you need any help.

I think there might have also been some discussions over whether we can have these debug repositories automatically enabled when users select Electron as a project type.

The new Sentry project setup should now automatically enable these repositories by default if you select Electron.


Release Roadmap for .net core 3.1

Hello,
Currently, the latest NuGet package for .net Core 3.1 is in Preview mode. To be exact it is "3.1.0-preview.1.4".
Do you have a release date of Final/Production Release for .net core 3.1?
I'm starting a new project which should be Production Ready until end of the February.2020 and I must choose between going with .net core 3.0 or 3.1.
Thank you,
Best Regards,
Ghodrat

Found it:
https://github.com/IdentityServer/IdentityServer4/milestones
Thanks and sorry for an extra ticket.


Out of memory: Kill process 3155 (goofys)

this error :Feb 11 12:50:11 localhost kernel: Out of memory: Kill process 3155 (goofys) score 202 or sacrifice child
is about buffer memory?
How I can fixit manually?
Thanks

What version are you using?

goofys version 0.0.3.
Logs:
Feb 11 12:50:11 localhost kernel: [ 3155]     0  3155   164285    57782     202       5     8768             0 goofys
Feb 11 12:50:11 localhost kernel: Out of memory: Kill process 3155 (goofys) score 202 or sacrifice child
Feb 11 12:50:11 localhost kernel: Killed process 3155 (goofys) total-vm:657140kB, anon-rss:231128kB, file-rss:0kB
Feb 11 20:31:22 localhost /usr/bin/goofys[378]: s3.INFO Switching from region 'us-west-2' to 'us-east-1'
Feb 11 20:31:22 localhost /usr/bin/goofys[378]: main.FATAL Mounting file system: Mount: mount: fusermount: exit status 1
Feb 11 20:53:49 localhost /usr/bin/goofys[3600]: s3.INFO Switching from region 'us-west-2' to 'us-east-1'
Feb 11 20:53:49 localhost /usr/bin/goofys[3600]: main.INFO File system has been successfully mounted.
Feb 11 20:53:55 localhost /usr/bin/goofys[3600]: main.INFO Successfully exiting.
Feb 11 20:55:38 localhost /usr/bin/goofys[11736]: s3.INFO Switching from region 'us-west-2' to 'us-east-1'
Feb 11 20:55:38 localhost /usr/bin/goofys[11736]: main.INFO File system has been successfully mounted.
Feb 11 20:59:00 localhost /usr/bin/goofys[11736]: main.INFO Successfully exiting.
Feb 11 20:59:08 localhost /usr/bin/goofys[22555]: s3.INFO Switching from region 'us-west-2' to 'us-east-1'
Feb 11 20:59:08 localhost /usr/bin/goofys[22555]: main.INFO File system has been successfully mounted.
I love the speed of goofys, but I want to know if is enough stable for production.
Thanks for your project.

This should be fixed in 0.0.4

Ok, I'll try it.
Thanks again.


Package idea: ida.plugins.vm

Add package to install ida plugins such as capa explorer.

Should we have a package per plugin or just for all? I tend to think one is enough as ida plugins are normally not that big.
Which plugins should we install?

I would like to install the capa plugin using FLARE-VM (adding it to the plugins directory) so that when you install IDA Pro, it is already there. The capa.vm package installs capa using the standalone binary. But to use it as a plugin, we need to install it as a python library using pip. @mr-tz @williballenthin @mike-hunhoff does it make sense to install it as both standalone binary and Python library? Or should we change to install it only as a Python library? The same applies to floss.
If we install it as both a standalone binary and as a Python library, should the Python package installation go into the libraries.python3.vm package and be required as dependency in the plugin package or should it go into the package that install the plugin? The difference is if we want it to always be installed in Python even if we don't install the plugin.
I am also not sure which package should install the capa plugin. Several options:
Option 1
We add it to the capa.vm package. We can do the same for other tools like floss, but we would have to have a different ways for plugins without a standalone binary.
Option 2
We create a plugin.capa.vm package. This implies one package per plugin, but allows users to decide which ones they want.
Option 3
We create a plugin.vm package with several plugins. Users can't decide which plugins to install. But the simplification may be good and we can always split it in the future if needed.
@vm-packages opinions?

i love the idea of being able to use flarevm as an IDA Pro package manager (option 2)! i hadn't considered using flarevm selectively for only IDA but it makes so much sense.
the capa plugin should include the pip library, the rules, and the plugin entry script. we should also try to pre-configure the rules location setting for ease of use.
finally, i think capa.exe and the plugin should be separate. capa.exe comes with the embedded rules, signatures, etc that make it much easier to use than the source/library distribution.

This is great @Ana06! +1 for everything Willi said doubly including my support for option [#]2, using FLARE VM as a IDA plugin manager (capa explorer, Diaphora, etc.). For capa explorer, follow the install instructions here and it's good to go.
@williballenthin I like your idea of pre configuring a rules directory - I suggest we code capa explorer to, by default, check a user's IDA plugins directory for capa rules if the user hasn't already configured rules. We already encourage users to install capa explorer to their IDA plugins directory so this seems like a natural location to also store the capa rules.

Thanks for the feedback @williballenthin @mike-hunhoff!
@mike-hunhoff

Diaphora
We have already a package for Diaphora, but as diaphora is not a plugin at the moment it is installed in Utilities. Diaphora documentation says it is complicated to make it a plugin but I think it should be double to install it as a plugin that wraps the diaphora script. I'll take a look into this.

pre-configure the rules location setting for ease of use
This was what I was thinking as well. Is there a way to do this at the moment? Or we need to modify the capa plugin?

We already encourage users to install capa explorer to their IDA plugins directory so this seems like a natural location to also store the capa rules.
I am not sure if ida also checks directories in the plugins directory. Does someone know? I am just thinking if this could slow down IDA loading the plugins. If not, this sounds like a good idea.

It doesn't look like there is a way to specify a path for the rules in CAPA explorer. If we want to hardcode the default, I think it is enough with adding a check for the default hardcoded path if CAPA_SETTINGS_RULE_PATH is empty and assign it. I think we can add this just after settings = ida_settings.IDASettings("capa"). Should I send a PR for this in capa?

the IDA plugin relies on ida-settings that will eventually end up using the registry, I believe. so, we could set the registry key that the plugin expects. alternatively, updating the plugin to guess a few typical paths makes sense, as long as we inform the user when making an assumption.


Integrate ssqosid extension

spec: https://github.com/riscv/riscv-ssqosid

Can you resolve the merge conflict?  (Probably a result of merging Svvptc first.)  Also, I take it that you made sure the CSR table renders correctly after the change?

@aswaterman - fixed the conflict. The CSR table renders correctly.


Overloading the term "Environment Variable" causing unnecessary confusion

Bug report
Webpack function type configurations take, as a first argument, a parameter named env & the documentation refers to this as "environment variables"
What is the expected behavior?
This parameter is set via Environment Variables.
What is the current behavior?
This parameter (env) has nothing to do with environment variables & is actually set via command line switches.
Why is this a problem?
Reusing a term that's already used in this context needlessly misdirects programmers attempting to understand webpack configuration files, leading to confusion and wasted time. Just as it would be a bad idea to call webpack an "operating system" due to the confusion it would cause, it's bad to use the term "Environment Variables" to refer to a command line argument.
This is especially so because actual Environment Variables can be and often are also used to configure webpack. In such a case, calling at CLI parameter an "environment variable" is almost certain to cause confusion when two programmers attempt to communicate about a webpack configuration.
If I ask how another programmer is switching webpack behaviour on staging & production and they reply "I use an Environment Variable", how could I know which method they are referring to?.
Proposals

Rename this webpackEnv in the code examples & replace "Environment Variables" with "Webpack Environment" in the docs or
Simply eliminate this parameter. It is also available in argv so const env = argv.env at the top of a configuration could fully replace the existing API, with the added benefits of increasing clarity & removing a needless parameter for users who use actual environment variables.

Bump

Is a pull request welcome here? May require a major version bump; is there a major release scheduled on the horizon?
Or am I missing something and this is actually a necessary feature? Thanks,

Yep you are right. The documentation should not call it "environment variables". Not sure how this happened. Instead --env should be better called env option or env CLI option.

Using argv

This is very specific for CLI usage and also depends on the CLI option parsing lib. It also makes it possible to depend on other CLI arguments.
I think it was a mistake to expose argv to the configuration. I think it's better to make it very explicit which CLI arguments are exposed to the configuration.

Using environment variables

My opinion here is similar. Using environment variables makes is less explicit which flags the configuration depends on. It's also more difficult to pass them when invoking the configuration from node.js

I also want to keep the use case calling a configuration file from node.js via script or with other CLI tools:
const config = require("./webpack.config.js")({
  mode: "production",
  product: "blah"
  // with types in webpack.config.js/ts you have completion and type check here
});
// can be called multiple times with different arguments

vs
process.env.MODE = "production";
process.env.PRODUCT = "blah";
// no completion, no type checks for typos
const config = require("./webpack.config.js");
// To call this multiple times you need to clear require.cache to require it again

To be honest I'm not sure how to verify this because I'm struggling to find documentation for the arguments passed to a webpack configuration function. I have one (working) that looks like this:
module.exports = (env, argv = {}) => {
// ...

Given this API, would it not be possible for you to load your webpack config from node.js thus?
const config = require("./webpack.config.js")(null, {
  mode: "production",
  product: "blah"
});

As an exported function, I don't see why the arguments could only be passed by CLI. Am I missing something?


Submit action should not be enabled on pristine form

Expected Results
The default action should be disabled on a newly loaded form
Actual Results
The default action is enabled and clickable

@esjaastad-isp wasn't this fixed?

Yep


Looks like ` in PHP/HTML files do not work

Hey Aaron! I've been converting my blog from WordPress to Laravel. With that I'm also switching to Torchlight.
One thing that struck me was the following code snippet:

This is a code snippet in a PHP that is rendered as HTML. In this case, the first line is just an HTML-comment, but it isn't grey like it should be.
Is this indeed a bug or should I use a different filetype than PHP?
Thanks!

Hmm that does indeed seem wrong, let me look into that really quick

Ok for files like that give php-html a try. I need to document that because it confused me too 😂

I'm working on a better solution to this.

Thank you for researching this! It works better, though it looks like the HTML-part isn't fully rendered. Do you also have that?

No problem, nothing urgent👍

Fixed! You can use php and if it notices opening tags <?php it will default under-the-hood to php-html and actually highlight the HTML properly now

Great, thank you Aaron! You absolutely did a great job with Torchlight. Initially I was somewhat skeptical of doing an API-call for highlighting, but with the caching in Laravel it's very fast and beautiful.


Project fails to build at typechecking stage with 1.6.0 and 2.0.0-beta.10

Describe the bug
Build fails with Typescript 5.4.3, Node 20.11.1
@tunarr/server:typecheck: ../node_modules/.pnpm/vite-node@2.0.0-beta.10_@types+node@20.11.1/node_modules/vite-node/dist/index-D1EszD4V.d.ts:87:14 - error TS2304: Cannot find name 'WebSocket'.
@tunarr/server:typecheck:
@tunarr/server:typecheck: 87   webSocket: WebSocket
@tunarr/server:typecheck:                 ~~~~~~~~~
@tunarr/server:typecheck:
@tunarr/server:typecheck: ../node_modules/.pnpm/vite@5.0.11_@types+node@20.11.1/node_modules/vite/types/customEvent.d.ts:26:14 - error TS2304: Cannot find name 'WebSocket'.
@tunarr/server:typecheck:
@tunarr/server:typecheck: 26   webSocket: WebSocket
@tunarr/server:typecheck:                 ~~~~~~~~~
@tunarr/server:typecheck:
@tunarr/server:typecheck: ../node_modules/.pnpm/vite@5.0.11_@types+node@20.11.1/node_modules/vite/types/importGlob.d.ts:36:11 - error TS2304: Cannot find name 'Worker'.
@tunarr/server:typecheck:
@tunarr/server:typecheck: 36   worker: Worker
@tunarr/server:typecheck:              ~~~~~~
@tunarr/server:typecheck:
@tunarr/server:typecheck:

skipLibCheck feels like a big hammer to drop here.
Reproduction
https://stackblitz.com/edit/vitest-dev-vitest-u7ffxn?file=package.json
Run pnpm tsc --noEmit
System Info
) ✗ pnpm envinfo --system --npmPackages '{vitest,@vitest/*,vite,@vitejs/*}' --binaries --browsers

  System:
    OS: macOS 14.5
    CPU: (12) x64 Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz
    Memory: 69.75 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.11.1 - ~/.nvm/versions/node/v20.11.1/bin/node
    npm: 10.2.4 - ~/.nvm/versions/node/v20.11.1/bin/npm
    pnpm: 8.15.4 - ~/Library/pnpm/pnpm
  Browsers:
    Chrome: 126.0.6478.62
    Safari: 17.5
  npmPackages:
    vitest: ^2.0.0-beta.10 => 2.0.0-beta.10

NOTE I have also tried with vitest 1.6.0

### Used Package Manager

pnpm

### Validations

- [X] Follow our [Code of Conduct](https://github.com/vitest-dev/vitest/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guidelines](https://github.com/vitest-dev/vitest/blob/main/CONTRIBUTING.md).
- [X] Read the [docs](https://vitest.dev/guide/).
- [X] Check that there isn't [already an issue](https://github.com/vitest-dev/vitest/issues) that reports the same bug to avoid creating a duplicate.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/vitest-dev/vitest/discussions) or join our [Discord Chat Server](https://chat.vitest.dev).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.

This is an issue with Vite: https://github.com/vitejs/vite/issues/9813

Ah yep. I just figured out the DOM types thing too. Hmph


OPENTHREADS download hash mismatch

While installing from source using superbuild got the following error
checking whether make sets $(MAKE)... CMake Error at OPENTHREADS-stamp/download-OPENTHREADS.cmake:9 (file):
  file DOWNLOAD HASH mismatch

    for file: [/home/eriba/software/OTB/SuperBuild-archives/OpenSceneGraph-3.2.0.zip]
      expected hash: [4980f8692712a24d4c99f363f80c6814]
        actual hash: [d41d8cd98f00b204e9800998ecf8427e]

make[2]: *** [OPENTHREADS/src/OPENTHREADS-stamp/OPENTHREADS-download] Error 1
make[1]: *** [CMakeFiles/OPENTHREADS.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....

Hi Edgar,
you're right, the URL has changed recently. The problem was reported on Mantis and fixed in branch release-5.0:
https://bugs.orfeo-toolbox.org/view.php?id=1077
To solve the issue on your side you can:

if you-re compiling the last stable release 5.0 from a git clone, checkout and update the branch release-5.0

If you're not using git clone, you can download a tarball which contains all sources for all dependencies and you set the path to the extracted archive in superbuild configuration using the DOWNLOAD_LOCATION cmake variable):

The archive is available here:
https://www.orfeo-toolbox.org/packages/SuperBuild-archives-5.0.tar.bz2
Regards,

@grizonnetm Simply solved that by modifying the hash by hand, only wanted to report that. Thanks anyway!


reindex and netCDF indexing

reindex can cause problems as long as the data is not loaded
import xarray as xr
data = xr.DataArray([1, 2, 3], dims='x').to_dataset('name')
data.to_netcdf('tst.nc')

# works fine
a = xr.open_dataset('tst.nc')
a.load()
a.reindex(x=[2, 0, 1])

# problem
b = xr.open_dataset('tst.nc')
b.reindex(x=[2, 0, 1])

Which version of netCDF4-Python are you using? This was an issue for some recent versions of netCDF4-Python but was then fixed -- see https://github.com/Unidata/netcdf4-python/issues/467 for details.

This solves the problem - thank you very much!


Add support for fallback search paths for Target frameworks

When running on Mono, target frameworks are searched for in
$mono_prefix/lib/mono/xbuild-frameworks, which becomes
/Library/Frameworks/Mono.framework/Versions/Current/lib/mono/xbuild-frameworks.
This works, but has a problem when upgrading the Mono.framework package:
a new /Library/Frameworks/Mono.framework/Versions/@VERSION@ directory
is created, so anything installed into the previous directory will be
"lost" (For example, installed by Xamarin.Android). The file is still there, but xbuild
will no longer find it.
To address this upgrade scenario, Mono's xbuild also checks a fallback path:
`/Library/Frameworks/Mono.framework/External/xbuild-frameworks`

This location is not within a versioned framework directory, and thus files
installed into it will survive Mono.framework package upgrades.
Mono would like to eventually migrate to MSBuild instead of xbuild, which
requires bringing xbuild's fallback support to MSBuild.
Implementation:

We add a new $(TargetFrameworkFallbackSearchPaths) property which
can have the list of fallback search paths and gets used by the GetReferenceAssemblyPaths.

For Mono/OSX case, we point that to /Library/Frameworks/Mono.framework/External/xbuild-frameworks
So, effectively, target frameworks are looked up, in order:

$(TargetFrameworkRootPath) or the default location, if
$(TargetFrameworkRootPath) is ''

If not found in (1), then try to find it in the fallback search
paths specified in $(TargetFrameworkFallbackSearchPaths)

I think that this PR does not support Linux. On Linux one must search /usr/local/lib/mono/xbuild-frameworks and then /usr/lib/mono/xbuild-frameworks . More path would need searching is installing mono into /opt or in a snap/flatpak.

@borgdylan This is adding support for fallback search paths. When looking for frameworks, msbuild will look in the default location first, which would be $mono_prefix/lib/mono/xbuild-frameworks and if it cannot find it there, then it will look in the fallback paths. And so, no extra search paths are required on Linux, by default. It would be incorrect to look for frameworks in other mono installations on the machine, as these frameworks are closely tied to the corresponding mono installations.
The case on OSX is slightly different.
Target frameworks are searched for in `$mono_prefix/lib/mono/xbuild-frameworks`, which becomes
`/Library/Frameworks/Mono.framework/Versions/Current/lib/mono/xbuild-frameworks`.

This works, but has a problem when upgrading the Mono.framework package:
a *new* /Library/Frameworks/Mono.framework/Versions/@VERSION@ directory
is created, so anything installed into the previous directory will be
"lost". The file is still there, but xbuild will no longer find it.

To address this upgrade scenario, Mono's xbuild also checks a fallback path:

    `/Library/Frameworks/Mono.framework/External/xbuild-frameworks`

This location is not within a versioned framework directory, and thus files
installed into it will survive Mono.framework package upgrades.

Mono would like to eventually migrate to MSBuild instead of xbuild, which
requires bringing xbuild's fallback support to MSBuild.

I adapted this from the commit message of an older PR . It would be useful to add this to the commit message here too, I think. Though the feature proposal does stand on it's own merit too.

Have you given more thought to the comments I suggested on the other thread? The two main things I need changed before this goes is are the reflection and the magic properties. By magic I mean that if you append an OS onto the property it deep down "engine" code treats it differently. I think both of these can be solved by plumbing the values through targets and having GetPathToReferenceAssemblies take a list of strings in place of targetFrameworkRootPath (new overload, and update the task as well).
The only question then is where does the overrides that set multiple values go. Without more context it's hard for me to make the case that the common targets should be aware of this (as opposed to Xamarin tool specific targets). I hadn't heard of app-local reference assemblies before so I can't speak to whether anyone else would want this functionality. If you think it will be more common then I'm not opposed to defining some of the fallback in targets or even the app.config if needed.
Can you investigate this approach and get back to us?

Heya @radical it would be great to reach an agreement on this with @AndyGerlicher so that this makes it to the next release and we don't have to workaround it by RTM ;)

BTW, @AndyGerlicher the app-local reference assemblies scenario comes from VS2017 now supporting app-local low-impact installation, which means things will more and more go into the VS install dir, rather than progfiles\Reference Assemblies. This should be the case for all the frameworks we ship, not only Xamarin, since otherwise nobody will have a good SxS story out of the box.
See the section on New Extension Capabilities for VS2017. That's the ReferenceAssemblies value in the VSIX Sub Path property. It would be quite important (I think) that that scenario is supported OOB, without target framework authors having to read even more documentation on how to provide override paths for a built-in product feature.

I agree with @AndyGerlicher's approach. And I will get back with an updated implementation.

Updated the PR with a completely new implementation. Ready for a fresh round of reviews :)

Any thoughts on this?

Sorry for the delay getting back! Most of us were out for the holidays and catching up.
Looks better. I think this approach is a lot cleaner. Thanks for changing directions.
Few things that should be fairly minor:

I prefer not to have fallback. It seems un-natural here. You're passing in a string that says look exactly here, but if that fails go ahead and look in all these other places too. It seems cleaner to just drop the fallback and pass in a list of places to look. Ideally typed as a list and if you pass in a string (legacy purposes) it would just pass that along as new List<string> { singlePath } to the new method that does the search that only takes a list.
Since you're changing the public interface make sure you build for other configurations. If you do you'll notice the ref cs files will be updated with the added methods. These need to be checked in as part of this change.
The other thing to note that does become more apparent if you look at that ref cs diff is adding an additional default property to a method changes the interface (it adds a required parameter with a default value). This means that apps compiled against the old code won't be able to provide that parameter and will break at run-time. I know it's uglier, but for changes to public methods can you please add an overload and keep all the existing methods?

Closing this for now. I'm in favor of the change in a generic way as I mentioned. Please do re-open when you'd like us to take another look. I would consider it for the 15.3 update time.

This would actually be unnecessary if https://github.com/Microsoft/msbuild/issues/1749 is implemented


Yellowbrick: explain execution plan ERROR: ERROR: cache lookup failed for type 142

System information:

Operating system (distribution) and version: Mac
$ uname -a
Darwin Offices-MacBook-Pro-3.local 18.2.0 Darwin Kernel Version 18.2.0: Thu Dec 20 20:46:53 PST 2018; root:xnu-4903.241.1~1/RELEASE_X86_64 x86_64

DBeaver version: <IP_ADDRESS>903251041

Java version
java version "1.8.0_181"
Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)

Additional extensions
Yellowbrick target

Connection specification:

Database name and version:  Yellowbrick 2.1.2-12000
Driver name: org.postgresql:postgresql:RELEASE. 42.2.0.jre7
Do you use tunnels or proxies (SSH, SOCKS, etc)? No.

Describe the problem you're observing:
EXPLAIN plan causes ERROR.
Steps to reproduce, if exist:
Highlight a query.

Right click:

"EXecute" --> "Explain Execution Plan"

Include any warning/errors/backtraces from the logs

It seems to generate: "EXPLAIN (FORMAT XML, ANALYSE) select count(*) from public.foo"
Recommendation: Generate:EXPLAIN (ANALYSE) select count(*) from public.foo
https://yellowbrick.com/docs/ybd_sqlref/explain.html?hl=explain

is it still actual?

there is no update on issue. if it is still actual - feel free to reopen the ticket


Livestream MP4 as segmented .ts files from a generated .m3u8 playlist

Hi, as you can see from the title, I have a little problem with creating a .m3u8 playlist, consisting of segmented .ts files created from an .mp4 file. This is how I've tried implementing it so far:
// worker.js
ffmpeg(inFile, {
    timeout: 432000
})
.addOptions([
    '-codec: copy',
    '-hls_time 2',
    '-hls_list_size 14',
    '-hls_flags omit_endlist', // +delete_segments
    `-hls_base_url http://localhost:1337/channels/${channel.name}/`,
    `-hls_segment_filename static/channels/${channel.name}/%05d.ts`
])
.output(outFile).run()

This creates 14 segment files (00001 - 00013.ts), and a stream.m3u8 playlist:
// chunklist.m3u8
#EXTM3U
#EXT-X-VERSION:3
#EXT-X-TARGETDURATION:2
#EXT-X-MEDIA-SEQUENCE:0
#EXTINF:2.000000,
http://localhost:1337/channels/name/00000.ts
#EXTINF:2.000000,
http://localhost:1337/channels/name/00001.ts
#EXTINF:2.000000,
http://localhost:1337/channels/name/00002.ts
#EXTINF:2.000000,
http://localhost:1337/channels/name/00003.ts
#EXTINF:2.000000,
http://localhost:1337/channels/name/00004.ts
#EXTINF:2.000000,
http://localhost:1337/channels/name/00005.ts
#EXTINF:2.000000,
http://localhost:1337/channels/name/00006.ts
#EXTINF:2.000000,
http://localhost:1337/channels/name/00007.ts
#EXTINF:2.000000,
http://localhost:1337/channels/name/00008.ts
#EXTINF:2.000000,
http://localhost:1337/channels/name/00009.ts
#EXTINF:2.000000,
http://localhost:1337/channels/name/00010.ts
#EXTINF:2.000000,
http://localhost:1337/channels/name/00011.ts
#EXTINF:2.000000,
http://localhost:1337/channels/name/00012.ts
#EXTINF:1.901000,
http://localhost:1337/channels/name/00013.ts

Then I've created a master .m3u8 playlist, which links to the generated .m3u8 file
// playlist.m3u8
#EXTM3U
#EXT-X-VERSION:3
#EXT-X-STREAM-INF:BANDWIDTH=3694952,CODECS="avc1.100.32,mp4a.40.2",RESOLUTION=1280x720
http://localhost:1337/channels/name/stream.m3u8

What happens, is that the chunklist.m3u8 and .ts files are only generated once, so I tried calling ffmpeg every x second, with an interval to generate a new list by keeping track of segments created, then setting "-segment_start_number x", but this isn't working as it's supposed to either. There will be gaps where it skips forward in the EXT-X-MEDIA-SEQUENCE and starts buffering.

What is the correct way to do this?
Am I supposed to call ffmpeg every 2 seconds to update the chunklist.m3u8 and generate new segments?
Am I missing some options for ffmpeg?

Thank you for reading!

your code helped me to solve my problem, I have a url that returns an mp2t stream and I needed to convert it to ts chunks and m3u8 file constantly. I managed to do this from within the code with your example. thank you!


Review/michaelbassett/tristankindig

test/sync.js
‘filesMatchNameandSize’
you could add another test, in which you check whether the function returns false for non-matching lists of the same name
test/base64utils.js
‘writeBase64Encoded’
the function on line 41 looks a little cluttered, just from a readability perspective. I understand the appeal of concise code, so if this is convention then just ignore. But if not I would suggest that you consider expanding it out into a more familiar format that is easier to read quickly.
index.js
we were supposed to refactor the checkForChanges() function and functions related to Pipeline into other files. Jules chose to put them into a file called “lib/sync/sync-driver” but it doesn’t really matter where so long as they are no longer here.
this is perhaps related to the previous comment, because I think if a function is in index.js it is difficult to test directly: you didn’t test chcekForChanges(). This is an issue because it performs the operations at the heart of the dropbox implementation.
dropboxuris.js
‘getPath’
I’m not sure whether it’s good practice to test how a function behaves when it fails. If it is, though, I’d suggest that you consider a unit test in which you provide the function with invalid input and then confirm that it fails in the expected manner. Just because it’s an important function that’s close to the user in terms of the program’s workflow.

Nothing was changed. No need to add comments to this branch, especially since the merge is not a fast-forward.

No need to add comments to this branch, especially since the merge is not
a fast-forward.

Could you explain what you mean by this?
Also, slightly off-topic: might you be willing to help me debug my code
sometime today? I've been struggling with even the base assignment, and
implementing the pull requests is another matter entirely. Just going for a
shot in the dark here, haha.
Tristan
On Sep 24, 2015 9:33 PM, "bassettmb"<EMAIL_ADDRESS>wrote:

Nothing was changed. No need to add comments to this branch, especially
since the merge is not a fast-forward.
—
Reply to this email directly or view it on GitHub
https://github.com/cs4278-2015/assignment3-handin/pull/19#issuecomment-143107057
.

If the merge is a fast-forward, then there are no merge conflicts and git can automatically apply the changes without human intervention. The comments added would have to be manually merged in since you applied your changes against the original head of the branch which doesn't have the changes from the other pull request. Since there were no changes that directly alter the behavior of the code, I got lazy and opted to just close it.
I may be able to help you, but I have other commitments presently. I'll take a look at it, though.

I'm working on it at the moment. I expect to have it up and running in an
hour or so. I'll let you know when it's in a respectable state, so that you
aren't wasting your time fixing errors that I'm fixing now
On Fri, Sep 25, 2015 at 3:53 PM, bassettmb<EMAIL_ADDRESS>wrote:

If the merge is a fast-forward, then there are no merge conflicts and git
can automatically apply the changes without human intervention. The
comments added would have to be manually merged in since you applied your
changes against the original head of the branch which doesn't have the
changes from the other pull request. Since there were no changes that
directly alter the behavior of the code, I got lazy and opted to just close
it.
I may be able to help you, but I have other commitments presently. I'll
take a look at it, though.
—
Reply to this email directly or view it on GitHub
https://github.com/cs4278-2015/assignment3-handin/pull/19#issuecomment-143351772
.

And if you can't, that's totally fine. I appreciate that you're even
considering trying honestly
On Fri, Sep 25, 2015 at 4:38 PM, Tristan Kindig<EMAIL_ADDRESS>wrote:

I'm working on it at the moment. I expect to have it up and running in an
hour or so. I'll let you know when it's in a respectable state, so that you
aren't wasting your time fixing errors that I'm fixing now
On Fri, Sep 25, 2015 at 3:53 PM, bassettmb<EMAIL_ADDRESS>wrote:

If the merge is a fast-forward, then there are no merge conflicts and git
can automatically apply the changes without human intervention. The
comments added would have to be manually merged in since you applied your
changes against the original head of the branch which doesn't have the
changes from the other pull request. Since there were no changes that
directly alter the behavior of the code, I got lazy and opted to just close
it.
I may be able to help you, but I have other commitments presently. I'll
take a look at it, though.
—
Reply to this email directly or view it on GitHub
https://github.com/cs4278-2015/assignment3-handin/pull/19#issuecomment-143351772
.


App crash

Not work in 9.0
invalid region.op - only intersect and difference

Are you using the latest version?

+1

Confirmed on multiple devices the issue is solved with the 2.1.0 patch


Transition Tool Updates for EIPs 6110, 7002 and 7251

What was wrong?
For Prague, there are three EIPs where there is extra header information that the tests need to verify during generation:

Deposit requests
Withdrawal requests
Consolidation requests

These need to be included in the result object from the transition tool back to EEST in the following format:
...
    "depositRequests": [
        {
            "pubkey": "0x000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
            "withdrawalCredentials": "0x0000000000000000000000000000000000000000000000000000000000000001",
            "amount": "0x773594000",
            "signature": "0x000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002",
            "index": "0x0"
        }
    ],
    "withdrawalRequests": [
        {
            "sourceAddress": "0x0000000000000000000000000000000000001000",
            "validatorPubkey": "0x000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001",
            "amount": "0x0"
        }
    ],
    "consolidationRequests": [
        {
            "sourceAddress": "0x0000000000000000000000000000000000001000",
            "sourcePubkey": "0x000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
            "targetPubkey": "0x000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001"
        }
    ],
...

How can it be fixed?
After block execution, and EELS t8n tool has processed all transactions, this information needs to be extracted from the logs and embedded in the result object.

@marioevz Can this issue be closed?

@marioevz Can this issue be closed?

Yes! All good now


Bug: Hood buttons don't work until Ki2 data element opened

I had expected that even if I don't have a Ki2 data element on a ride profile the hood buttons should work if "Pre load ride application" setting is enabled. However, this does not seem to be the case - a Ki2 data element must be present.

That is indeed correct @judahrand, for the hood buttons to work you will need at least one Ki2 data element in the ride profile. I can try to make them work anytime inside the ride app, but I cannot guarantee it will work reliably.

I see. It's not really a bit deal as one can just have a screen with just Di2 battery or something but it would be nice for it to 'just work'. I'm familiar with these sorts of limitations as they exist with some Garmin ConnectIQ applications.


Add option to make trainer non-deterministic

I think when this is used in production, random should not be deterministic.
Adding meson option would be fine.

:octocat: cibot: Thank you for posting issue #569. The person in charge will reply soon.

Exposing a setSeed() should be good enough for this.


Counterfactual instantiation of identity contract upon first execution

Resolves #90. It is a merge from the fork. @JustynaBroniszewska @marekkirejczyk please check the TokenGrantingRelayer. I believe you've removed it but it was present in my repo and not sure how to migrate my code to the new changes

Hi @Perseverance,
I took a closer look yesterday at the PR, it will be hard to merge it all at once (failing tests, merge conflicts, etc)
I propose we split that into 3 smaller PRs:

smaller updates (readme, eslint, etc)
new classes with tests (CounterfactualIdentityService, CounterfactualTransactionsService, etc)
and integration with the application (IdentityService, Relayer, etc)

TokenGrantingRelayer was moved to src/relayer. I suspect there is no need to modify it in anyway in your PR now.
Marek


fix: dont define repo if disabled

Fixes #6

Thx, I already working on the issue #6. I took the same solution, but this will break the current behavior and has to release as v2.0.0.

Thx, I already working on the issue #6. I took the same solution, but this will break the current behavior and has to release as v2.0.0.


CRI doc in website isn't synced with master branch.

CRI doc(https://kubernetes.io/docs/concepts/architecture/cri/) in website is not synced with cri.md in master main branch.
Shouldn't it be synced?

help 😅  @saschagrunert

/priority awaiting-more-evidence
/triage not-reproducible
What doesn't seem to be current @jmyung? This k/website repository doesn't have a branch named master

site: https://kubernetes.io/docs/concepts/architecture/cri/
You need a working container runtime on each Node in your cluster, so that the kubelet can launch Pods and their containers.

The main protocol for the communication between the kubelet and Container Runtime.

The Kubernetes Container Runtime Interface (CRI) defines the main gRPC protocol for the communication between the cluster components kubelet and container runtime.

main branch: https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/architecture/cri.md

line 12-18
no contents starts with The main protocol ...

You need a working
{{<glossary_tooltip text="container runtime" term_id="container-runtime">}} on
each Node in your cluster, so that the
{{< glossary_tooltip text="kubelet" term_id="kubelet" >}} can launch
{{< glossary_tooltip text="Pods" term_id="pod" >}} and their containers.

{{< glossary_definition term_id="container-runtime-interface" length="all" >}}

@sftim @jmyung from what I can see they're not out of sync, we just reference the glossary definition into it:
{{< glossary_definition term_id="container-runtime-interface" length="all" >}}

compiles to
The main protocol for the communication between the kubelet and Container Runtime.

<!--more-->

The Kubernetes Container Runtime Interface (CRI) defines the main
[gRPC](https://grpc.io) protocol for the communication between the
[cluster components](/docs/concepts/overview/components/#node-components)
{{< glossary_tooltip text="kubelet" term_id="kubelet" >}} and
{{< glossary_tooltip text="container runtime" term_id="container-runtime" >}}.

We could enhance this by applying something like https://github.com/kubernetes/website/pull/31266

@jmyung we improved the docs, see: https://deploy-preview-31266--kubernetes-io-main-staging.netlify.app/docs/concepts/architecture/cri/
Let's close this for now, feel free to reopen if we missed anything. Thanks!
/close


The 3scale application apply/create is missing an option to set the redirect url

Fixes #178

ready for review @miguelsorianod


Add links to architecture and template docs in CONTRIBUTING.md

Easy change. Added links to the architecture doc and template doc in contributor doc.
Github noob here, please let me know if there's something I can do better.

Thank you!

@all-contributors add linshu123 for docs


Option to screenshot without spaces

I want to have the paths show in the background, but the spaces in the screenshot of the paths show in-game underneath the real spaces. I want a way to not show the spaces in a screenshot so i can just do the in-editor screenshots for a background.

Do you want the orange lines to show on top of the image without spaces, or do you just want the ability to download the plain background image?


More docs

#30 should be merged first
This is branched off #30 and has the wiki pages for Journey Maps, interviews and the ODK personas

:+1:


Unable to install mamba-ssm as a pypi dependency

Checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
# setup base environment
pixi init --pyproject
pixi add mamba-ssm

Issue description
I'm unable to install mamba-ssm as a pypi dependency, it breaks even if i add pip as a conda dep and if i add packaging as a pypi dep.
pixi add --pypi mamba-ssm
  ⠂ default:linux-64     [00:00:00] resolving mamba-ssm==2.0.4                                                                                × failed to solve the pypi requirements of 'default' 'linux-64'
  ├─▶ failed to resolve pypi dependencies
  ├─▶ Failed to download and build `mamba-ssm==2.0.4`
  ├─▶ Failed to build: `mamba-ssm==2.0.4`
  ╰─▶ Build backend failed to determine extra requires with `build_wheel()` with exit status: 1
      --- stdout:

      --- stderr:
      Traceback (most recent call last):
        File "<string>", line 14, in <module>
        File "/path/to/home/.cache/rattler/cache/uv-cache/.tmpuEioZ7/.venv/lib/python3.12/site-packages/setuptools/build_meta.py", line 325, in get_requires_for_build_wheel
          return self._get_build_requires(config_settings, requirements=['wheel'])
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/path/to/home/.cache/rattler/cache/uv-cache/.tmpuEioZ7/.venv/lib/python3.12/site-packages/setuptools/build_meta.py", line 295, in _get_build_requires
          self.run_setup()
        File "/path/to/home/.cache/rattler/cache/uv-cache/.tmpuEioZ7/.venv/lib/python3.12/site-packages/setuptools/build_meta.py", line 487, in run_setup
          super().run_setup(setup_script=setup_script)
        File "/path/to/home/.cache/rattler/cache/uv-cache/.tmpuEioZ7/.venv/lib/python3.12/site-packages/setuptools/build_meta.py", line 311, in run_setup
          exec(code, locals())
        File "<string>", line 8, in <module>
      ModuleNotFoundError: No module named 'packaging'
      ---

I'm able to get it to install using pip on top of my pixi setup (but it required that i had a properly setup cuda/torch env + installed packaging), and also am able to get it installing with uv if I follow the workaround described here. I'm not sure what work would be required for it to work in pixi?
Expected behavior
Should by added with minimal fuss (and maybe an extra flag in the pyproject.toml if required)

Indeed, if we support that flag we should be able to create a conda workspace with packaging and build without isolation using that dependency.

Should now be possible with #1909 merged, and will soon be released, documentation is here: https://pixi.sh/dev/reference/project_configuration/#no-build-isolation


Compile Error on 'master' branch

I'm encountering the following when I try to pod install on the 'master' branch
[!] CocoaPods could not find compatible versions for pod "SparkSDK":
  In snapshot (Podfile.lock):
    SparkSDK (from `https://github.com/ciscospark/spark-ios-sdk.git`, branch `develop`)

  In Podfile:
    SparkSDK (from `https://github.com/ciscospark/spark-ios-sdk.git`, branch `develop`)

Specs satisfying the `SparkSDK (from `https://github.com/ciscospark/spark-ios-sdk.git`, branch `develop`), SparkSDK (from `https://github.com/ciscospark/spark-ios-sdk.git`, branch `develop`)` dependency were found, but they required a higher minimum deployment target.

Now, if I increase the iOS version to 10.0 on the podfile on this project, it manages to execute the installation but then more issues pop up and the project doesn't compile. I've run pod update after targeting to 10.0
I'd appreciate it if you could give me a bit of guidance with regards to this issue as I'm guessing it's probably my inexperience with using CocoaPods that may be the problem.
I'm also using the latest Xcode 9.3 to try to do this.

Thanks, working great now.


Typo in Charts Block Documentation

https://www.tremor.so/blocks/charts
There's a title there with the text Card + Lin Chart + Tabs
"Lin Chart" should be Line Chart
Note: I forked the repo thinking the docs were included in it, was looking to submit a PR for this myself, but I couldn't find those 🤔

Thank you @psikoi for reaching out! You are correct, we will fix this asap!


[multitop] New bazel rules to describe HW

The goal of this experiment is to design new rules to better describe the HW and eventually get rid of our current usage of all_files targets. The idea is that each IP contains a new target created by opentitan_ip where the RTL, doc and hjson files are listed. Then, those files targets are collected by an opentitan_top rule that puts together the entire list of doc, RTL and hjson files. One this is done, we start replace all direct usages of HW files by reference to this new top target where we selectively extra only the files we need. Eventually this should apply to:

all headers (C, rust, multi-top)
fusesoc
documentation

More is possible, for example we could point to testplans, we could separate RTL from DV, etc
This change will eventually be needed for multi-top because collecting all files as we currently do will not scale.
Finally, this PR contains another change: instead of pointing to //hw/ip/... for headers, we now collect everything in a new package //hw/top. There are several reasons for that:

we can start treating all IPs the same way, whether they are in hw/ip or hw/top_/ip/..., autogenerated or not
this moves us closer to a bazel-configuration-based top selection which will be used for multi-top
it solves the problem of IPs in hw/top that have top-specifiied parameters but those are not accessible when generating headers the way we currently do.

Since there are many IPs to convert and many files to patch, the approach in this PR is to create a script to automate most of the process. All commits before [util] Add script to convert... are manual. The rest is created automatically by the script to convert IPs and uses one by one, except for the last commit is manual.
Important remark: this does not duplicate any information that fusesoc has, this is completely orthogonal and only use coarse-grained globs to gather all files.
TODO:

[ ] convert pinmux: maybe wait for #24808 and treat it like other templates

TODO in follow-up PRs:

cleanup the OTBN python: it's a complete mess, the way data files are handled and the the way it hack sys.path to point to util/ is not great. I couldn't quite get rid of all_files due to that.

After discussing with @HU90m about the documentation, I have decided to drop the doc attribute of the rules for now. Indeed, it appears that the doc is mixed with the RTL and which files get included is based on what the README.md specifies, in particular it may not be in the doc/ subdirectory.
I have also changed the rtl attribute of most IPS to include glob(["**"]) instead of more fined grained dictories to keep as close as possible to the original behaviour, in case some downstream users were relying on this.

What's the plan of converting the new IPs such as:

DMA
MBX
KeymgrDPE
SocProxy

I don't think it's worth the effort. I plan to add the top_darjeeling.hjson by the end of the week.

Following the feedback on the RFC, I have renamed the rtl attribute to files to make it clearer that (1) this is more general than hardware files, (2) this is just a bazel "visibility" thing, we not trying to reimplement fusesoc here.

Closed in favor of #25580


Add support for solc 0.6

Currently, support for solc 0.6 is not great. Specifically, the ABI JSON format has changed and not supported by ethabi crate.

Is there any more incompatibilities besides #546?

I think this can be closed. I also don't see a good way to work around conflating fallback and receive at a type level. Happy to hear if you have any ideas.

I also don't see a good way to work around conflating fallback and receive at a type level. Happy to hear if you have any ideas.

No ideas right now. I'm not sure if we need the distinction tbh.


Olivekl new install instructions

New install instructions, including screenshots.

DRAFT, DO NOT MERGE
Draft of new installation instructions. Sharing for comments before I add screenshots and links.
Questions: -Is everything accurate and easy to follow?

I think we could get rid of it.

-Do we need to include the "manual" option at the bottom? Will anyone want to set up the action values themselves, or are they useful for any other reason?

I copied this from other actions' README. But other actions out there are not available under the Security tab, so that's why they need it.
@azeemshaikh38 wdut?

DRAFT, DO NOT MERGE
Draft of new installation instructions. Sharing for comments before I add screenshots and links.
Questions: -Is everything accurate and easy to follow?

I think we could get rid of it.

-Do we need to include the "manual" option at the bottom? Will anyone want to set up the action values themselves, or are they useful for any other reason?

I copied this from other actions' README. But other actions out there are not available under the Security tab, so that's why they need it.
@azeemshaikh38 wdut?

I think its ok to keep the manual part of the setup for more advanced users.

Thanks, Azeem. I addressed your comments. I'll add screenshots for the UI section if everything else looks good.

We just need to rebase the PR.


 Please remove this directory
2015-03-24T22:27:45.08+0800 [STG/0] OUT and add it to your .gitignore. To vendor your gems with Bundler, use
2015-03-24T22:27:45.08+0800 [STG/0] OUT bundle pack instead.
2015-03-24T22:27:45.08+0800 [STG/0] OUT ###### WARNING:
2015-03-24T22:27:45.08+0800 [STG/0] OUT No Procfile detected, using the default web server (webrick)
2015-03-24T22:27:45.08+0800 [STG/0] OUT https://devcenter.heroku.com/articles/ruby-default-web-server
2015-03-24T22:27:45.17+0800 [STG/0] ERR
2015-03-24T22:27:50.38+0800 [STG/0] OUT -----> Uploading droplet (25M)
2015-03-24T22:27:54.11+0800 [DEA/0] OUT Starting app instance (index 0) with guid 3097b670-cf96-413d-9ec3-7d5c4efe6dd6
2015-03-24T22:27:57.80+0800 [DEA/0] ERR Instance (index 0) failed to start accepting connections
2015-03-24T22:27:57.81+0800 [API/0] OUT App instance exited with guid 3097b670-cf96-413d-9ec3-7d5c4efe6dd6 payload: {"cc_partition"=>"default", "droplet"=>"3097b670-cf96-413d-9ec3-7d5c4efe6dd6", "version"=>"aec72d05-d6fb-435a-a111-875213002e38", "instance"=>"f2aad186632745c0a95d3d9eea9cff4a", "index"=>0, "reason"=>"CRASHED", "exit_status"=>127, "exit_description"=>"failed to accept connections within health check timeout", "crash_timestamp"=>1427207277}
2015-03-24T22:27:57.81+0800 [API/0] OUT App instance exited with guid 3097b670-cf96-413d-9ec3-7d5c4efe6dd6 payload: {"cc_partition"=>"default", "droplet"=>"3097b670-cf96-413d-9ec3-7d5c4efe6dd6", "version"=>"aec72d05-d6fb-435a-a111-875213002e38", "instance"=>"f2aad186632745c0a95d3d9eea9cff4a", "index"=>0, "reason"=>"CRASHED", "exit_status"=>127, "exit_description"=>"failed to accept connections within health check timeout", "crash_timestamp"=>1427207277}
2015-03-24T22:28:37.67+0800 [DEA/0] OUT Starting app instance (index 0) with guid 3097b670-cf96-413d-9ec3-7d5c4efe6dd6
2015-03-24T22:28:40.54+0800 [DEA/0] ERR Instance (index 0) failed to start accepting connections
2015-03-24T22:28:40.55+0800 [API/0] OUT App instance exited with guid 3097b670-cf96-413d-9ec3-7d5c4efe6dd6 payload: {"cc_partition"=>"default", "droplet"=>"3097b670-cf96-413d-9ec3-7d5c4efe6dd6", "version"=>"aec72d05-d6fb-435a-a111-875213002e38", "instance"=>"2c154cbf0aac4b29bb2e55a8c3d185a2", "index"=>0, "reason"=>"CRASHED", "exit_status"=>127, "exit_description"=>"failed to accept connections within health check timeout", "crash_timestamp"=>1427207320}
2015-03-24T22:28:40.56+0800 [API/0] OUT App instance exited with guid 3097b670-cf96-413d-9ec3-7d5c4efe6dd6 payload: {"cc_partition"=>"default", "droplet"=>"3097b670-cf96-413d-9ec3-7d5c4efe6dd6", "version"=>"aec72d05-d6fb-435a-a111-875213002e38", "instance"=>"2c154cbf0aac4b29bb2e55a8c3d185a2", "index"=>0, "reason"=>"CRASHED", "exit_status"=>127, "exit_description"=>"failed to accept connections within health check timeout", "crash_timestamp"=>1427207320}
2015-03-24T22:28:43.85+0800 [DEA/0] OUT Removing crash for app with id 3097b670-cf96-413d-9ec3-7d5c4efe6dd6
2015-03-24T22:28:43.85+0800 [DEA/0] OUT Stopping app instance (index 0) with guid 3097b670-cf96-413d-9ec3-7d5c4efe6dd6
2015-03-24T22:28:43.85+0800 [DEA/0] OUT Stopped app instance (index 0) with guid 3097b670-cf96-413d-9ec3-7d5c4efe6dd6
2015-03-24T22:29:17.68+0800 [DEA/0] OUT Starting app instance (index 0) with guid 3097b670-cf96-413d-9ec3-7d5c4efe6dd6
2015-03-24T22:29:20.33+0800 [DEA/0] ERR Instance (index 0) failed to start accepting connections
2015-03-24T22:29:20.34+0800 [API/0] OUT App instance exited with guid 3097b670-cf96-413d-9ec3-7d5c4efe6dd6 payload: {"cc_partition"=>"default", "droplet"=>"3097b670-cf96-413d-9ec3-7d5c4efe6dd6", "version"=>"aec72d05-d6fb-435a-a111-875213002e38", "instance"=>"c5b3ae3462a24283944b3ad56acc561d", "index"=>0, "reason"=>"CRASHED", "exit_status"=>127, "exit_description"=>"failed to accept connections within health check timeout", "crash_timestamp"=>1427207360}
2015-03-24T22:29:20.34+0800 [API/0] OUT App instance exited with guid 3097b670-cf96-413d-9ec3-7d5c4efe6dd6 payload: {"cc_partition"=>"default", "droplet"=>"3097b670-cf96-413d-9ec3-7d5c4efe6dd6", "version"=>"aec72d05-d6fb-435a-a111-875213002e38", "instance"=>"c5b3ae3462a24283944b3ad56acc561d", "index"=>0, "reason"=>"CRASHED", "exit_status"=>127, "exit_description"=>"failed to accept connections within health check timeout", "crash_timestamp"=>1427207360}
2015-03-24T22:29:24.09+0800 [DEA/0] OUT Removing crash for app with id 3097b670-cf96-413d-9ec3-7d5c4efe6dd6
2015-03-24T22:29:24.09+0800 [DEA/0] OUT Stopping app instance (index 0) with guid 3097b670-cf96-413d-9ec3-7d5c4efe6dd6
2015-03-24T22:29:24.09+0800 [DEA/0] OUT Stopped app instance (index 0) with guid 3097b670-cf96-413d-9ec3-7d5c4efe6dd6
2015-03-24T22:29:57.68+0800 [DEA/0] OUT Starting app instance (index 0) with guid 3097b670-cf96-413d-9ec3-7d5c4efe6dd6
2015-03-24T22:30:00.59+0800 [DEA/0] ERR Instance (index 0) failed to start accepting connections
2015-03-24T22:30:00.61+0800 [API/0] OUT App instance exited with guid 3097b670-cf96-413d-9ec3-7d5c4efe6dd6 payload: {"cc_partition"=>"default", "droplet"=>"3097b670-cf96-413d-9ec3-7d5c4efe6dd6", "version"=>"aec72d05-d6fb-435a-a111-875213002e38", "instance"=>"e8519dc74657407ca19f20f402fd0b7b", "index"=>0, "reason"=>"CRASHED", "exit_status"=>127, "exit_description"=>"failed to accept connections within health check timeout", "crash_timestamp"=>1427207400}
2015-03-24T22:30:00.61+0800 [API/0] OUT App instance exited with guid 3097b670-cf96-413d-9ec3-7d5c4efe6dd6 payload: {"cc_partition"=>"default", "droplet"=>"3097b670-cf96-413d-9ec3-7d5c4efe6dd6", "version"=>"aec72d05-d6fb-435a-a111-875213002e38", "instance"=>"e8519dc74657407ca19f20f402fd0b7b", "index"=>0, "reason"=>"CRASHED", "exit_status"=>127, "exit_description"=>"failed to accept connections within health check timeout", "crash_timestamp"=>1427207400}
2015-03-24T22:30:04.27+0800 [DEA/0] OUT Removing crash for app with id 3097b670-cf96-413d-9ec3-7d5c4efe6dd6
2015-03-24T22:30:04.27+0800 [DEA/0] OUT Stopping app instance (index 0) with guid 3097b670-cf96-413d-9ec3-7d5c4efe6dd6
2015-03-24T22:30:04.27+0800 [DEA/0] OUT Stopped app instance (index 0) with guid 3097b670-cf96-413d-9ec3-7d5c4efe6dd6

Hi!
The MySQL service broker is not designed to be deployed to CF as an app without the rest of cf-mysql-release. If you are not familiar with service deployment patterns,  see: Services
So, in order to deploy our MySQL for Cloud Foundry service, you'll want to follow the step-by-step instructions in cf-mysql-release.
I hope this helps clarify? I'll close this issue now, please feel free to re-open if you have any questions.
-- Marco Nicosia
Product Manager
Pivotal Software, Inc.


Question: what is the difference between Azure::Core::Internal::Http and Azure::Core::Http::Internal

https://github.com/Azure/azure-sdk-for-cpp/blob/5c2d0fba17248db31751b202557a2b50554c5726/sdk/core/azure-core/inc/azure/core/http/policy.hpp#L385
https://github.com/Azure/azure-sdk-for-cpp/blob/5c2d0fba17248db31751b202557a2b50554c5726/sdk/core/azure-core/inc/azure/core/internal/http/pipeline.hpp#L19
what should go into one and what should go into the other?

They will be one.  We are cleaning up the Azure namespaces
Commonly used types for customers reside in Azure::
More advanced features for customers which ship in core are in subnamespaces Azure::<subnamespace>, i.e. Azure::Cryptography::
Features intended for use by client libraries are in or under  Azure::Core::Internal
Things private to the Azure::Core package are in Azure::Core::Details

Features intended for use by client libraries are in or under  Azure::Core::Internal

To clarify this particular aspect, are you recommending we don't have any other Azure::<subnamespace>::Internal namespaces, and all such "internal-only" APIs will live under one namespace with Internal, i.e. Azure::Core::Internal?
For example, what happens when we have some advance feature in Azure::Cryptography::, and then we have "internal-only" APIs that are specific to that namespace and would be grouped under Azure::Cryptography::Internal? Would those still live under Azure::Core::Internal?

are you recommending we don't have any other Azure::::Internal namespaces,

I would stay with the Azure::<subnamespace>::Internal, The intention is that if you include one header like http.hpp, you would get both public and internal namespaces and you can access it through Azure::Core::Http

As part of the cleanup we will address this


Add Set All button in Send Credit dialog to fill in all available balance

Is your feature request related to a problem? Please describe.
From to time, I'm sending all available balance between wallets, and I should manually to type in this amount.
Describe the solution you'd like
Would be nice to have (maybe right in the field) a button to set all available balance.

Thanks for filing the issue! This is currently blocked by https://github.com/lbryio/lbry-sdk/issues/1628


Make the code lint-clean

Before releasing, fix all lint errors.

Eslint doesn't seem to find errors in root directory, lib/, locmap/, test/ or test_helpers/.