37 Matching Annotations
  1. Apr 2021
    1. unbuffer is able to pass along the return code of a process under normal circumstance, but if the process you are unbuffering is killed, for instance with a segfault, I see $? as 0 while I expect 139. How can I get it to pass along the 139?
    2. The expect wait command returns more arguments if the spawned process is killed but unbuffer just always returns the 3rd argument.
  2. Mar 2021
    1. With all this “monetization” happening around Trailblazer, we will also make sure that all free and paid parts of the project grow adult and maintan an LTS - or long-term support - status. Those are good news to all you users out there having been scared to use gems of this project, not knowing whether or not they’re being maintained, breaking code in the future or making your developers addicted to and then cutting off the supply chain. Trailblazer 2.1 onwards is LTS, and the last 1 ½ years of collaboration have proven that.
  3. Feb 2021
    1. Personally, I'm starting to think that the feature where it automatically adds xray.js to the document is more trouble than it's worth. I propose that we remove that automatic feature and just make it part of the install instructions that you need to add this line to your template/layout: <%= javascript_include_tag 'xray', nonce: true if Rails.env.development? %>
  4. Jan 2021
    1. Personally, I think you are perhaps blowing up a fairly medium-sized (and fixable) bug discovered during routine testing into extreme-case hyperbole. Again, engagement and participation will get the bug fixed faster. The entire point of testing is to discover and fix precisely these kinds of pain points before release.
  5. Dec 2020
  6. Nov 2020
    1. If I use import { createEventDispatcher } from 'svelte/internal'; instead of import { createEventDispatcher } from 'svelte'; then it seems to work because it's loading from the same module.
  7. Oct 2020
    1. This is a very dangerous practice as each optimization means making assumptions. If you are compressing an image you make an assumption that some payload can be cut out without seriously affecting the quality, if you are adding a cache to your backend you assume that the API will return same results. A correct assumption allows you to spare resources. A false assumption introduces a bug in your app. That’s why optimizations should be done consciously.
  8. May 2020
    1. We iterate to deliver features, so we often don't have functionality that people expect. For this reason, 'people could reasonably expect this functionality' does not make it a bug.
  9. Apr 2020
  10. Feb 2020
    1. Update 10/14/19: Proceed at your own risk. The upgrade works, but my iMac runs on high cpu on various services. I arleady disabled photoanalysisd, but now vtencoderxpcservice takes up a lot of CPU. If anywone found a solution, please post it in the comments below.

      I have this same issue. It arises when attempting to do a screen recording...

  11. Nov 2019
    1. When a user encounters a bug they look like this: 🤬Bugs grind work to a halt.Bugs cause financial harm.Every single time a bug is encountered, user trust erodes.Bugs are bad.
    2. Doesn’t play whack-a-mole with features, fixing one thing only to break another.
  12. Oct 2019
    1. bottom sheet 功能展示

      Outline 基本能保留我派文章的大部分样式,目前还转换不过来的我发现只有分割线和脚注。

  13. Feb 2019
  14. Dec 2018
  15. Apr 2018
  16. May 2017
  17. Mar 2017
  18. Dec 2016
    1. Sure, we get bad bugs, but we have a ton of contributors who can immediately work with people who log them to educate them on better practices and treat it as an opportunity to educate. This is why we have documentation on writing good bugs, in order to educate contributors, not as a barrier to entry.Creating barriers to entry just reduces the number of people there’s a chance to identify, educate and potentially grow into greater contributors.

      La frase final es clave:

      Creating barriers to entry just reduces the number of people there’s a chance to identify, educate and potentially grow into greater contributors.

    2. We know what happens to unhealthy projects over a long enough time period, more maintainers leave, contributions eventually fall, and if we’re lucky users leave it. When we aren’t so lucky adoption continues and years later we’re plagued with security and stability issues in widely adopt software that can’t be effectively maintained.The number of users a project has is a poor indicator of the health of the project, often it is the most used software that suffers the biggest contribution crisis.
  19. Jan 2015
  20. May 2014
    1. Two scroll bars is hard to understand. I expect to scroll up to the first comment using the comments bar, but it only scrolls up to the first comment that is also on the range of page I can see. (I think). Its a hard problem, I know.

      Also super helpful to have all text on page to show even if the annotation side bar is open.

    2. Clicking on the number arrows sometimes narrows the comments down to the ones indicated, and sometimes does not.

      The number 3+4 aren't super understandable. It would help to have a hover maybe that said "3 comments and 4 replies"

    3. I'm not able to resize the bar - it gives me the option but it doesn't seem to work? Edit - I'm able to resize the bar outward with ease and no issues, but not inward again. Holding it down for some time it logged me out for some reason.

    4. I don't seem to see updates until I reload the page. But the network sucks, so hey.

    5. Public/private should be selected at a higher level, not on a per annotation level. Maybe per session.

      • I now see it is per session, but that was not clear as I made the selection in a specific annotation.