154 Matching Annotations
  1. Jul 2022
    1. raise StandardError.new "No authentication is configured for ActiveStorage"

      forces the issue by requiring end-dev to edit/override this method to avoid getting this error

    1. What were (or still are) the relative attitudes towards issues related to gender at our respective institutions? What did the students at our respective institutions think about the gender issues of their day? We take particular focus on trans, queer, and women’s issues where they arise.

      Viewing group 2's project pitch, I believe that this group and my group (group 1) share a similar research question with some distinct variations. In group 1, we plan to go through the digital collections as well as publications from institutions that our members attend to find out about the students' attitude towards women during different gender discrimination eras. Meanwhile, this group covers a broader range of research in the study of genders. I am impressed with the meticulous explanation of the timeline that this group narrows down and also with the media that the group bases on for their sources of research. I hope that the research will be a success and I can learn new, interesting aspect of group 2's research to apply on my group's future research.

    1. Stop autoclosing of PRs While the idea of cleaning up the the PRs list by nudging reviewers with the stale message and closing PRs that didn't got a review in time cloud work for the maintainers, in practice it discourages contributors to submit contributions. Keeping PRs open and not providing feedback also doesn't help with contributors motivation, so while I'm disabling this feature of the bot we still need to come up with a process that will help us to keep the number of PRs in check, but celebrate the work contributors already did instead of ignoring it, or dismissing in the form of a "stale" alerts, and automatically closing PRs.

      Yes!! Thank you!!

      typo: cloud work -> could work

    1. I don't understand why it should be so hard to keep issues open / reopen them. That's just going to cause people to open a duplicate issue/PR — or (if they notice in time) cause people to add extra "not stale" noise when the bot warns it's about to be closed. Wouldn't it be preferable to keep the discussion together in one place instead of spreading across duplicate issues? (Similarly, moving the meta conversation about an issue out to a completely separate system (Discord) seems like the wrong direction, because it wouldn't be visible to/discoverable by those arriving at the closed issue.) I get how it's useful to have stale issues not cluttering the list. But if interes/activity later picks up again, then "stale" is no longer accurate and its status should be automatically updated to reflect its newfound freshness... like it did back here:
  2. Mar 2022
  3. Jan 2022
    1. To be perfectly frank, this proposal seems far more about creating the appearance of safety than addressing an actual deficit in application correctness. I'm not questioning the value in detecting unhandled promises (resolved OR rejected) as a development tool for calling attention to a potentially undesired flow... but just like other lint rules, this belongs in tooling and NOT the execution environment.
  4. Nov 2021
    1. may always

      The first amendment does not prohibit

    2. Dissent

      He had a concurring opinion

    3. the Second Amendment

      It should be the first amendment

    4. painted an American flag on his bare chest, but painted it upside down.

      It was over the fact that there was a burning of the Flag not a painting on his chest

    5. Arthur Smith

      Gregory Lee Johnson is the protestor in this case

    1. Info for maintainers Triage this issue by using labels. If information is missing, add a helpful comment and then I-issue-template label. If the issue is a question, add the I-question label. If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label. After troubleshooting the issue, please add the R-awaiting answer label. Thank you!
  5. Oct 2021
  6. Sep 2021
    1. webpack-bot commented on Nov 13, 2020 For maintainers only: webpack-4 webpack-5 bug critical-bug enhancement documentation performance dependencies question
    1. One complicating issue when trying to make sense across multiple communities is that not only do different communities have different cultures and practices, but also different epistemologies: different languages to describe their community and the soci(et)al context it operates in, with often different meanings attached to the terminologies used.
  7. Aug 2021
  8. Jul 2021
  9. Jun 2021
  10. May 2021
    1. My advice is if you are looking for a quick and accurate answer ask to have the trouble ticket elevated immediately and to speak with an engineer that will recognize your knowledge and speak with you on your level.
    2. "Put as much information about the problem itself into the email". This is where you show your ability to know what is important and relevant and establish your technical level. Don't be brief, don't imply, and break it down Barney style so the person receiving it knows to escalate your ticket.
    3. Look for certain questions that have been asked every time, and put those answers into the initial email you send about the new problem. Try to add things that make the potential problem sound local. The more information you give them that you know they will be asking for in their script, the faster you will get someone who can help you. And they will thank you for it.
    4. And if your answers tell me it's something too advanced for me, only then would I escalate it.
    5. In one of my internship, I got to befriend a level 2 tech support, so learned a couple thing of how it worked (in that company). Level 1 was out-sourced, and they had a script to go from, regularly updated. From statistics, this took care of 90% of issues. Level 2 was a double handful of tech people, they had basic troubleshooting tools and knowledge and would solve 90% of the remaining issues. Level 3 was the engineering department (where I was), and as a result of level 1 and 2 efficiency less than 1% of issues ever got escalated. The process worked!
  11. Apr 2021
  12. Mar 2021
    1. However, since you haven't yet provided any details about how you built with Qt (Qt isn't officially supported, so you must have used a third party derivative of vim), and you haven't provided any detailed information about what error messages or malfunctions you're having with python-complete, it's not really possible to tell you how to fix the problem and get vim working with Qt.
    1. Yes, but honestly, and no offense intended, but I don't see the harm in these type questions, nor why some people are offended when they are asked. If I owed a website, I wouldn't mind it because it just creates more pages that can be indexed. I see it as helping the website. But, I did look and didn't see a simple answer. Again, no offense is intended. I've just never understood the complaints.
  13. Feb 2021
    1. (To clarify, I'm not personally needing / waiting on this change (not currently anyway). I was just looking at all the open issues in this project while deciding whether I should start using ActiveIntegration in my project...)
    1. opt out of certain data collection.

      Representation

    2. Arizona University’s assistant provost for institutional research suggested that, should the use of student ID card tracking eventually become part of student retention efforts, such a move would be preceded by a “campus conversation” and students “should be given the choice to opt out of being tracked if they wish.”

      Consent

    3. One of the principles highlighted in the article was transparency.

      Transparency

    4. unaware that any of their CatCard data would have been collected

      Students unaware that this is something that is happening

  14. Jan 2021
    1. When there are imperfections, we rely on users and our active community to tell us how the software is not working correctly, so we can fix it. The way we do that, and have done for 15 years now, is via bug reports. Discussion is great, but detailed bug reports are better for letting developers know what’s wrong.
  15. Dec 2020
  16. Nov 2020
    1. If the goal of this is purely to avoid showing a runtime warning (and isn't needed for other functionality) I think we should try to consider other ways of dealing with the root issue. See also #4652, which has been opened for just this concern.
  17. Oct 2020
    1. Issue grooming: This seems like an ancient configuration issue which based on the comment traffic people aren't seeing today, so I'm going to speculatively close. If this is still happening with modern versions then we can reopen (but please provide full details of the modern case). If you are still seeing this and you aren't the original submitter then please create a new issue with full details.
    1. Issue grooming: There appears to be a variety of different failure modes and user error/misconfiguration scenarios (all largely historic) described here.
    1. first sighting: use of superscripts like this

      I like it. Nice and concise and understandable.

      • s¹  critical
      • s²  important
      • s³  nice to have
      • s⁴  low
      • s⁵  inconvenient

      But in other cases, the abbreviation is quite unclear and ambiguity:

      Like, what does "pr" mean in these cases?

      priority? Doubt it.

      • pr¹  chore
      • pr²  docs
      • pr³  feature
      • pr⁴  fix
      • pr⁵  performance
      • pr⁶  refactor
      • pr⁷  style

      Pull Request? Doubt it. But maybe?


      For axes that are quantifiable, like severity, using a number makes sense. But what benefit is there in including a number in these (platform?) labels?:

      • p¹ ⋅ browser
      • p² ⋅ linux
      • p³ ⋅ mac
      • p⁴ ⋅ windows

      I think this would have been better and clearer (in that fewer people would be like huh? and wonder what it means):

      • platform: browser
      • platform: linux
      • platform: mac
      • platform: windows
  18. Sep 2020
    1. If you would like to delete your account, please email us at support@hypothes.is

      This reminds me of closed systems, pretty much the opposite of what Dan Whaley (Founder, CEO of Hypothes.is) is talking about here:

      https://youtu.be/RYjOfTv0Tjs?t=603

    1. The other possible route would depend on #640 (dynamic components), plus the ability to pass around element names as strings in place of components, plus #195 (spread).
  19. Aug 2020
    1. If this issue is proposing a new feature, please can you verify whether the feature proposal is still relevant. Thanks for your help! 🖤 /cc Triage specialists @gitlab-org/issue-triage
  20. Jul 2020
  21. Jun 2020
    1. It would be better if you asked a new question. In the worst case scenario, it would be marked as a duplicate (which still means you would probably get some sort of resolution).
    1. If you've found a problem in Ruby on Rails which is not a security risk, do a search on GitHub under Issues in case it has already been reported. If you are unable to find any open GitHub issues addressing the problem you found, your next step will be to open a new one.
  22. May 2020
    1. put it in our %Backlog (meaning GitLab, Inc. currently doesn't prioritize it over other items that are scheduled
    2. This issue is going backwards in the process, not forwards. Surely, Gitlab should be focusing on things that have already been allocated milestones, especially ones that have had milestones pushed continuously for 3 years. You can argue that it shouldn't have had a milestone added in the first place, but maybe Gitlab should focus on clearing the "backlog" of issues that have already been issued milestones, and backlog new issues until some of the older issues have been solved.
    1. Despite our best efforts to deal with all of those issues, over the course of time we fall behind. When you look at an issue it's sometimes unclear whether or not we intent to provide the functionality you propose, whether or not we fix the bug, whether or not the issue is a duplicate of another one. In order to restore a reasonable level of clarity we annually perform a House Keeping Iteration in which we go through all open issues. We categorize, label, fix, and close issues. This results in a wave of notification which is hard to deal with (our apologies) but in the end there is better understanding of what will happen to your ideas.
    2. Labeling Issues
    1. Peer must maintain a staffed 24x7 operational center, with knowledge or direct escalation privileges to knowledgable personal to resolve any issues efficiently
  23. Apr 2020
  24. Feb 2020
  25. Jan 2020
    1. But the reason is that, if your host system does not have the vm.overcommit_memory=1 enabled, you will not be able to switch it inside container.

      Fixed redis issue on harbor: "Can't save in background: fork: Cannot allocate memory"

      Added on /root/harbor/docker-compose.yml:

      command: sh -c 'echo 1 > /proc/sys/vm/overcommit_memory'

      Also executed command: sh -c 'echo 1 > /proc/sys/vm/overcommit_memory' on the main server harbor (not only on the container)

  26. Dec 2019
    1. If none of this worked, please comment in this issue and we’ll try to help. Try to create a small reproducing example — you might discover the problem as you’re doing it.
    1. is more detailed than the discussion in #1269, so I wanted to create a separate discussion for it. If the maintainers disagree with this split please feel free to mark as a duplicate of 1269.
  27. Nov 2019
    1. Feature requests are great, but they usually end up lying around the issue tracker indefinitely. Sending a pull request is a much better way of getting a particular feature into Capybara.
  28. github.com github.com