Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
LONG RANT AHEAD!
In my workplace (dev company) I am the only dev using Linux on my workstation. I joined project XX, a senior dev onboarded me. Downloaded the code, built the source, launched the app,.. BAM - an exception in catalina.out. ORM framework failed to map something.
mvn clean && mvn install
same thing happens again. I address this incident to sr dev and response is "well.... it works on my machine and has worked for all other devs. It must be your environment issue. Prolly linux is to blame?" So I spend another hour trying to dig up the bug. Narrowed it down to a single datamodel with ORM mapping annotation looking somewhat off. Fixed it.
mvn clean && mvn install
the app now works perfectly. Apparently this bug has been in the codebase for years and Windows used to mask it somehow w/o throwing an exception. God knows what undefined behaviour was happening in the background...
Months fly by and I'm invited to join another project. Sounds really cool! I get accesses, checkout the code, build it (after crossing the hell of VPNs on Linux). Run component 1/4 -- all goocy. run component 2,3/4 -- looks perfect. Run component 4/4 -- BAM: LinkageError. Turns out there is something wrong with OSGi dependencies as ClassLoader attempts to load the same class twice, from 2 different sources. Coworkers with Windows and MACs have never seen this kind of exception and lead dev replies with "I think you should use a normal environment for work rather than playing with your Linux". Wtf... It's java. Every env is "normal env" for JVM! I do some digging. One day passes by.. second one.. third.. the weekend.. The next Friday comes and I still haven't succeeded to launch component #4. Eventually I give up (since I cannot charge a client for a week I spent trying to set up my env) and walk away from that project. Ever since this LinkageError was always in my mind, for some reason I could not let it go. It was driving me CRAZY! So half a year passes by and one of the project devs gets a new MB pro. 2 days later I get a PM: "umm.. were you the one who used to get LinkageError while starting component #4 up?". You guys have NO IDEA how happy his message made me. I mean... I was frickin HIGH: all smiling, singing, even dancing behind my desk!! Apparently the guy had the same problem I did. Except he was familiar with the project quite well. It took 3 more days for him to figure out what was wrong and fix it. And it indeed was an error in the project -- not my "abnormal Linux env"! And again for some hell knows what reason Windows was masking a mistake in the codebase and not popping an error where it must have popped. Linux on the other hand found the error and crashed the app immediatelly so the product would not be shipped with God knows what bugs...
I do not mean to bring up a flame war or smth, but It's obvious I've kind of saved 2 projects from "undefined magical behaviour" by just using Linux. I guess what I really wanted to say is that no matter how good dev you are, whether you are a sr, lead or chief dev, if your coworker (let it be another sr or a jr dev) says he gets an error and YOU cannot figure out what the heck is wrong, you should not blame the dev or an environment w/o knowing it for a fact. If something is not working - figure out the WHATs and WHYs first. Analyze, compare data to other envs,... Not only you will help a new guy to join your team but also you'll learn something new. And in some cases something crucial, e.g. a serious messup in the codebase.11 -
I don't know what's wrong with my project. But somehow, this is the screening when you debugs a React Native app within DevTools.
10 -
me: deletes comment from pom file
eclipse: there is a problem...
me: refresh project manually
eclipse: ok.. its all good now.
¯\_(ツ)_/¯6 -
Gah gets me every time I open an image I want to share with friends on messages later.
Share dialog ain't cutting it.
1 -
I've been using Ubuntu 14.04 since it was first released until this moment (June 2018). What a stable OS i've ever used. Thank's Linux, you're free & awesome.
Thank Mr. Trusty & Tahr1 -
>mvn clean install
[ERROR] Bruh, couldn't find any of these classes you're talking about.
>mvn clean install
[INFO] The job has completed without errors.
Seriously, why is Java/Maven/Spring so temperamental. It's like it has to be in a good mood to compile for me.4 -
If AI can create an email address, register to instagram, post a photo randomly based on AI feeling or conditions, then reply a comment. I will follow that account.3
-
wtf eclipse... fuck you
synchronize project in eclipse. no changes...
mvn relase:prepare
BUILD FAILED: you have local modifications pending...2 -
I like a Product Manager/Owner/CTO who invites coffee when a dev burnout. This is not a story, a hope seems to be.2
-
GitHub Packages Sucks. Like, it REALLY sucks.
It sounds like the best thing in the world - being able to host your project packages alongside your code! It has full support for Maven, Gradle, Ruby Gems, Node packages, Docker images and even dotnet CLI applications. It even lets you view statistics on how many developers have downloaded a given package! For public repositories, the packages are free to host as well!
So, I decide to use it for my Maven project since it's "so great". I've never used a public Maven repository before, so this was all very new to me. I follow the documentation - simply run "mvn deploy ...." and use a generated GitHub personal access token. No problems there. Deployment is a success and I feel a wave of happiness seeing my packages online. I follow through the various links and it even adds automatically generated usage information for other Maven users - fantastic!
That was, until I decide to try and download one of the files from this package repository. In order to download a file, you must have a GitHub access token. Okay, makes sense I guess? What if another developer wants to use my library? To do so, they have to generate their own GitHub access token, store it in their local ~/.m2/settings.xml file and only THEN can they use my library. So clearly, this is significantly inferior to other public Maven repositories where you don't have to get an access token to simply USE a library.
Upon discovering this, I decide to simply delete all of the packages and continue using whatever previous system I was using. Except of course, they forbid the deletion of public packages because "other projects could depend on it". The only way to delete public packages is to either:
[0] Make the repository private (losing all stargazers and watchers), delete the packages and then make the repository public again
[1] Contact support and ask them to delete the public packages. They say that they'll only do this for "special cases", such as legal issues or GDPR breaches.
I've sent a contact form and I'm currently hoping that they see things in my favor. I mean seriously - a public package repository where in order to use it you have to have a GitHub account and then generate an authentication token - it's absurd!3 -
I just woke up and on my computer screen there’s big announcement.
Github launching code package registry beta program.
Available repositories: npm, gem, mvn, docker, nuget.1 -
Once upon a time, I'm in the process of going to a new job. But in the middle of the recruitment process, it turns out I don't like that company, for reasons I didn't know before.
Anyone have a good idea how to escape this pit?
*My CV has been thrown there6 -
mvn clean install: all tests pass
run all tests in IntelliJ: the same 6 tests fail every time
run those 6 tests in IntelliJ: they pass
-_-4 -
I encountered some strange programming languages here =>
https://codegolf.stackexchange.com/...
Then scroll to the bottom.6 -
I have tried so hard to add some dependencies on react-native (android). Always fails when build gradle, many dependencies are mismatch.
Go fuck my project.2 -
And there I was thinking Maven is going to make life simpler, with this granular dependency management and IDE independence (no extraneous classpath and module management required). But wait, it turns out that to run simple Ant task I need all my dependencies to have *.pom. Every. Fricking. Dependency.
I mean, sure, only if I knew which sub-dependencies they all had, but that seems like heck a lot of work to make external JAR libraries to work with Maven process.
WHY TODAY? Yesterday I had no issue: uploaded few libraries in corporate repository, refreshed index, dependencies downloaded, even had time appending javadoc to one of them and it worked. But today is the day, right? I just run simple task with maven-antrun-plugin (mvn antrun:run@<executionID>), and it starts scanning each dependency for *.pom file. I DON'T WANT THIS. Google, help me. Oh, no direct answers and clues?
Just... fuck you, Maven. With all 2 days effort I could just litter in IDE's classpath, write build.xml in no time, make normal webservice, but that would require me to also litter sources with required libraries. FML!4 -
Almost stuck with manual state management for JS. Dealing server side rendering manually. [almost crazy]
-
I didn't use Windows, but my friend encountered this problem. Anyone knows how to handle it? Thank you
(I am afraid to post to stackoverflow)
13 -
>$ mvn clean test
>$ [INFO] Building project-name
>$ ....
>$ ....
>$ ....
>Results:
>Tests in error:
> Test.test:75
aauaauugh -
Today's achievement, has successfully told my friend to create an account in Devrant. Guess what? My friend instantly love it.2
-
I have just allowed '*' on the rack-cors host configuration. Yiiiiihhhhaaaaa.. no cors problems on Rails again.
But hackers will go fuck my api. -
Immutable.js, Immutable
rb, Immutable.py, Immutable.java, Immutable.php.
Immutable.jpeg, Immutable.mp4. Love you Immutable.
Top Tags
Weekly Rant
View