If you have a lot of #GitHub repositories, migrating to #Git main branch can be tricky. I documented my experience migrating 130 of my own repositories to #main.
https://t.co/onY6aXIhYA
@JMuffington@BlueDotNOkla@andreasgal@RitchieTorres I accept that on the assumption but I wasn't in the original replay. If you have any interest in context see my other replies to your thread.
While it may not be your intent you appear to be putting a lot of effort into defending a corrupt official.
@BlueDotNOkla@JMuffington@andreasgal@RitchieTorres The primary point is this public official hasn't served, yet. They haven't built a retirement or long term benefits which would be funded by our taxes. They were elected on false pretenses. Don't pay them a sitting salary and let them build the retirement they don't deserve.
@BlueDotNOkla@Frankiejwd@JMuffington@andreasgal@RitchieTorres This guy hasn't put in years of service, yet. He was elected on false grounds. If he is allowed to stay in office and build years of service, then he'll get the salary, the benefits, and eventually the retirement. I.e. nip this corrupt official in the bud before they leech.
@JMuffington@BlueDotNOkla@andreasgal@RitchieTorres Correct me if I'm wrong. It sounds like you are OK with a corrupt official getting a full term worth of salary and any post-term benefits. What I said is pretty clear I think. Benefits do not fully end with their term.
@JMuffington@BlueDotNOkla@andreasgal@RitchieTorres They get a pension and retirement benefits if allowed to sit their term. A corrupt official who is allowed to remain because a party only cares about winning will get these benefits. i.e. republicans fail to agree on accountability which they haven't for the past decade.
@FeelTheWeightOf @BlueDotNOkla@andreasgal@RitchieTorres Maybe you meant to respond to someone else? I made no mention of a party just a desired expectation that accountability and action occur within congress to address these issues.
@Suvabbb@housecor Test the inputs you care about. In one of my projects it exercises the same code repeatedly because I test the same function with inputs I care about from docs and usage.
I've done a full refactoring with the same tests to improve extending while preserving functionality.
@julie4055_@BriannaWu You just reduced that brute force time significantly by sharing your password length. You might want to change increasing or decreasing the length
@BriannaWu@AdamConwayIE Their advice to switch to app MFA is practical. So is using a password manager like keepassxc to have unique passwords across websites
@MarkEWaite@jenkinsci I see thanks. The question was pertinent because some of the plugins I have maintained depend on a library I have been updating recently. I now target jdk11 as its bytecode.
@unixbhaskar Sometimes it depends on the requirements. If what you're doing is simple enough it makes sense to avoid supply chain attacks by reducing your dependencies.
@jamesshore I think I am using nullable stubs without realizing it. I came up with this way to test by treating network connections and files as readable writable streams. So for testing in Java I use groovy meta programming to return file contents instead of real network connections.
1/2