分类: 其它

ipify

ipify一个简单的IP地址API。你可以直接访问:https://api.ipify.org/ 查看你的IP你是否需要通过程序获取对外的IP地址?也许你正在配置新的云服务器,需要知道你的IP。也许你在公司的防火墙后面,需要tunnel信息。不管是什么原因:有一个获取可以获取公共IP地址的API是没坏处的。你值得使用 ipify是因为:你可以毫无限制地使用它(即使你每分钟做数百万个请求)。它总是在线并可用的,它的基础设施是由 Heroku 提供的,这意味着你不用管运行API的服务器是否挂掉了,如果有龙卷风摧毁了东海岸,ipify仍将运行。它兼容IPv4和IPv6地址,无论你使用什么样的技术,都不会有问题。ipify是开源的,Git仓库从不记录访问者信息最后,ipify是 Randall Degges 资助的,所以不用担心它会消失

学生机 躺枪了

刚刚WordPress群里发生的对话,新鲜热乎的。卖主机的:腾讯云学生机卖主机的:有要的没路人1:5毛钱就要管理员:(截图了一个刚进群妹子的个人资料,并且里面有4张个人照)路人2:这群要炸了路人3:射交群?路人3:100秒了妹子:神经病啊路人4:活好?妹子:有病啊,一个个跟狗似的?卖主机的:学生机妹子:就会约炮?卖主机的:有没有要的妹子:你才是学生鸡管理员:我只是想告诉你们群里来女生了妹子:神经病

You need to run build with JDK or have tools.jar on the classpath

在配置QueryDSL的时候报的这个错误,在 stackoverflow.com 上找到了2个questions,按里面给出的答案修改后可用。https://stackoverflow.com/questions/27619304/you-need-to-run-build-with-jdk-or-have-tools-jar-on-the-classpathhttps://stackoverflow.com/questions/24482259/eclipse-issue-with-maven-build-and-jdk-when-generating-qclasses-in-querydsl报错信息You need to run build with JDK or have tools.jar on the classpath.If this occures during eclipse build make sure you run eclipse under JDK as well (com.mysema.maven:apt-maven-plugin:1.1.3:process:default:generate-sources) org.apache.maven.plugin.MojoExecutionException: You need to run build with JDK or have tools.jar on the classpath.If this occures during eclipse build make sure you run eclipse under JDK as well at com.mysema.maven.apt.AbstractProcessorMojo.execute(AbstractProcessorMojo.java:362) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:331) at org.eclipse.m2e.core.internal.embedder.MavenImpl $11.call(MavenImpl.java:1362) at org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112) at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1360) at org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52) at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137) at org.eclipse.m2e.core.internal.builder.MavenBuilder $1.method(MavenBuilder.java:172) at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1) at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112) at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99) at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86) at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200) at org.eclipse.core.internal.events.BuildManager $2.run(BuildManager.java:734) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245) at org.eclipse.core.internal.events.BuildManager $1.run(BuildManager.java:300) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java: 1) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: org.apache.maven.plugin.MojoExecutionException: You need to run build with JDK or have tools.jar on the classpath.If this occures during eclipse build make sure you run eclipse under JDK as well at com.mysema.maven.apt.AbstractProcessorMojo.execute(AbstractProcessorMojo.java:310) ... 32 more方案一配置eclipse.ini

command not found

在项目中写了个启动的shell,在linux上执行报了语法错误,具体如下:[admin@sz app]$ sh start.shstart.sh: line 2: $'\r': command not found: No such file or directorystart.sh: line 4: $'\r': command not foundstart.sh: line 6: $'\r': command not foundstart.sh: line 8: $'\r': command not foundstart.sh: line 9: $'\r': command not foundstart.sh: line 12: $'\r': command not foundstart.sh: line 15: $'\r': command not foundstart.sh: line 26: syntax error: unexpected end of file

Kindle支持的格式、推送和转换文件

单反毁三代,kindle富一生,也不知道是谁说的,总之,我看了这个,立马就决定买一个,选来选去发现都有缺陷,最终买了顶配!【亚马逊Kindle Oasis电子书阅读器 斯诺克黑】,现在它已经完美的躺在床头柜里落灰了。

No space left on device

Jenkins中发布一个项目,然后就 Dead(!) ,查看详细信息提示No space left on device以前也发生过这个问题,因为备份文件比较大,而且不删除过期的备份导致的。这次删除了一个11GB的log文件之后以为就可以用了,然而后Jenkins还是 Dead。查看文件系统使用率 df -hT[root@school1024 /]# df -hTFilesystem Type Size Used Avail Use% Mounted on/dev/vda1 ext4 40G 12G 26G 100% /...