132 Matching Annotations
  1. Jul 2021
  2. Jun 2021
  3. 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!
  4. Apr 2021
  5. 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. Open tools tab on Incredimail and selects Accounts in this tab. Choose your account and click on properties. Now, in the servers tab of Incredimail not sending emails account, ensure that incoming and outgoing mail server is set to ‘pop.oricom.ca’ and ‘smtp.oricom.ca’ respectively. Ensure the password is correct and that ‘My server requires authentication’ box is unchecked. Open the Advanced tab next and make sure that outgoing server for SMTP is set on ‘25’ with ‘This server requires an encrypted connection (ssl)’ box unchecked while the incoming server is set on ‘110’ and the same box is unchecked. Finally, click OK to save. For more details: How to Fix Incredimail 2.5 Crashing Issue Incredimail Password recovery

    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.
  6. 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

  7. 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.
  8. Dec 2020
  9. 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.
  10. 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
  11. 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).
  12. 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
  13. Jul 2020
  14. 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.
  15. 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
  16. Apr 2020
  17. Feb 2020
  18. 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)

  19. 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.
  20. 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.
  21. Oct 2019
    1. Probably some context-setting is in order. This meeting is primarily devoted to getting yes-or-no decisions made on suggestions which have fairly clear outcomes. In other words, it's effectively a "shortest job first" throughput-maximizing endeavor where we try to pay down some of the massive triage debt we have while also getting as many suggestions accepted or declined in a short turnaround time.
    1. This issue is already known to us since yesterday. Our engineers are now working diligently to fix this behavior. I'd recommend you contact our Customer Care team and let them know that you're one of the affected users of INV36818. That way, they will link your company to the case. You will then receive a notification via email for its updates. 
  22. Sep 2019
  23. Aug 2019
  24. Apr 2019
    1. Being a teenager is hard; there are constant social and emotional pressures that have just been introduced into the life of a middle or high schooler, which combines with puberty to create a ticking time bomb. By looking at the constant exposure to unreasonable expectations smartphones and social media create, we can see that smartphones are leading to an increased level of depression and anxiety in teenagers, an important issue because we need to find a safe way to use smartphones for the furture generations that are growing up with them. Social media is a large part of a majority of young adults life, whether it includes Instagram, Facebook, Snapchat, Twitter, or some combination of these platforms, most kids have some sort of presence online. Sites like Facebook and Instagram provide friends with a snapshot of an event that happened in your life, and people tend to share the positive events online, but this creates a dangerous impact on the person scrolling.​ When teens spend hours scrolling through excluisvely happy posts, it creates an unrealistic expectation for how real life should be. Without context, teenagers often feel as if their own life is not measuring up to all of their happy friends, but real-life will never measure up to the perfect ones expressed online. Picture Picture Furthermore, social media sites create a way for teenagers to seek external validation from likes and comments, but when the reactions online are not perceived as enough it dramatically alters a young adults self-confidence. This leads to the issue of cyberbullying. There are no restrictions on what you can say online, sometimes even annonimously, so often people choose to send negative messages online. Bullying is not a new concept, but with online bullying, there is little to no escape as a smartphone can be with a teenager everywhere, and wherever the smartphone goes the bullying follows.This makes cyberbullying a very effective way to decrease a youth's mental health, in fact, cyberbullying triples the risk of suicide in adolescents, which is already the third leading cause of death for this age group.

  25. Sep 2018
    1. An important and difficult issue in the creation of feature models is deciding which problem space features torepresent.
  26. Dec 2017
    1. Collaboration and QA

      I think it would be better to work in the QA time into the story above. That way we don't have a bunch of solo QA time stories that aren't very useful.

  27. Oct 2017
  28. Jun 2017
  29. Apr 2017
    1. so that the blessed news had to circulate from individual to individual

      On plantations slaves were often not allowed to practice religion or anything of their choice because they were not looked at a people. They had to find other ways to do this, so instead of having things like churches or massing they usually told stories that passed down from person to person