Got a Question?
Can't find what you're looking for? Ask it here!
- 8 Topics
- 6 Replies
Magento 2 store owners might be familiar with the backend grids and how they can be exported to CSV files. The store admins are frequently required to export the data into CSV format for multiple purposes.There can be custom columns in the backend grid that the admin may also want to include in the exported CSV file. However, sometimes you may face problem to include the custom column in export to the CSV file in Magento 2, which may put the store admin in a troubling situation.Suppose you are a Magento 2 store owner selling food items and have added a custom product attribute for flavours, then you may face difficulties while exporting products grid along with the newly created product attribute.The solution to deal with such an issue is to tweak the source codes. You can learn the complete solution at https://meetanshi.com/blog/include-custom-column-in-export-to-csv-in-magento-2/
Hi, Am not able to record a process, not sure why it is not able to do so. can you please help on how to debug it.[root@VM-228 undo-6.6.0-dev.850b22880926]# ./live-record -p 11027live-record: Termination recording will be written to /opt/cfg/undo-6.6.0-dev.850b22880926/11027-2022-05-14T16-57-41.771.undo if requiredlive-record: Maximum event log size is 1GError: Cannot enable recordinglive-record: No child processes (-10:ECHILD) Thank you,Rajesh
Particularly for the benefit of new users, it might be useful to have a “Tip of the day” feature which gives suggestions like “use ugo end to get to the end of a recording, rather than continue”.I think it makes sense to restrict this to running once at UDB startup, or when run/attach/uload is used; to show suggestions in the middle of a session would be too obtrusive.
I am trying the live debugging guide for java , in intellij an unable to get to workam seeing the following error with my demo project, any help as to what’s going wrong ?18:05:32.962 [main] DEBUG io.undo.jdwp.UdbJVMDebugger - type database created18:05:33.012 [main] ERROR io.undo.jdwp.UdbJDWPBridge - startup errorjava.lang.Exception: Please make sure debug symbols are installed! at io.undo.jdwp.UdbJDWPBridge.<init>(UdbJDWPBridge.java:230) [undo-jdwp-java-1.0.jar:?] at io.undo.jdwp.UdbJDWPBridge.main(UdbJDWPBridge.java:121) [undo-jdwp-java-1.0.jar:?]18:05:33.016 [main] DEBUG io.undo.jdwp.UdbJDWPBridge - agent has been notified on port 4168318:05:33.016 [main] DEBUG io.undo.jdwp.UdbJDWPBridge - wait for JDWP thread to connect
If, while recording through the API, one of the undolr_stop() or undolr_discard() functions fails (e.g. returns -1), what does that imply for the debugged program?What measures should a programmer take when such failures are met?
If I run a reverse operation such as reverse-continue then interrupt it, I will find myself at some point in the recording earlier than I was previously at, but later than the earliest I might have ended up. So far, so expected.If I then repeat the command, is UDB guaranteed to stop at the same point it would have if the original command was not interrupted (because of a breakpoint say), or might it skip that instance and stop at some earlier point in the recording?Put another way, does repeating a reverse command carry on in a human sense, or could some of the search space in the recording be missed? Or do I need to go back to the point where I was before and start the operation all over again?
Recently while investigating an issue for a customer I noticed the following: (udb) ugo event prev name=='write'going to: ref=0x1fc054f4c170 in_code=0 time_bbcount=223466223298 time_extra=18446744073709551615 code=write size=80 result=70x00007f4fc89e0c0b in write () from /tmp/undodb.8444.1617966303.9400325.18ca8bac04951ecc/debuggee-1-bamqf2b_/symbol-files/lib64/libpthread.so.0OK(udb) ugo event prev name=='write'going to: ref=0x1fc054f4c0b8 in_code=0 time_bbcount=223466223040 time_extra=18446744073709551615 code=write size=80 result=6[Switching to Thread 12978.12978]0x00007f4fc3843f81 in epoll_wait () from /tmp/undodb.8444.1617966303.9400325.18ca8bac04951ecc/debuggee-1-bamqf2b_/symbol-files/lib64/libc.so.6WHAT?(udb) ugo event prev name=='write'going to: ref=0x1fc0540a8d00 in_code=0 time_bbcount=223403831487 time_extra=18446744073709551615 code=write size=80 result=8[Switching to Thread 12978.13072]0x00007f4fc38367ab in write () from /tmp/undodb.8444.1617966303.9400325.18ca8bac04951ecc/d
Currently ugo 1,234 gives an error as you should use ugo time 1,234. Anecdotal evidence shows that even experienced users often forget to spell the full command.It would be possible to make the ugo command smarter when it can infer what the user meant, so ugo 1,234 would be treated as ugo time 1,234 and ugo my-bookmark-name as ugo bookmark my-bookmark-name.To make this work properly we would also need to modify other commands to be more helpful. For instance, if you use ubookmark start to create a bookmark called start, then the command could warn you that you will have to use the full ugo bookmark start form to avoid ambiguity with the ugo start command. (Details on how this would work are still undecided.)
Already have an account? Login
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.