the fastcgi version <=1.2.24 have rce vuln .please update.

Per subject. Useful for logging.

Hi, there!

We are a research team working on third-party library analysis. We have found that some widely-used third-party libraries in your project have major/critical bugs, which will degrade the quality of your project. We highly recommend you to update those libraries to new versions.

We have attached the buggy third-party libraries and corresponding jira issue links below for you to have more detailed information. We have analyzed the api call related to the following libraries and found one library that is using the API call that might invoke buggy methods in the library of the history.

1. commons-codec commons-codec
   version: 1.4
   API call in your project:org.apache.commons.codec.binary.Base64.setInitialBuffer(byte[],int,int)

Jira issues:
Base64InputStream#read(byte[]) incorrectly returns 0 at end of any stream which is multiple of 3 bytes long
version:1.4
ArrayIndexOutOfBoundsException when doing multiple reads() on encoding Base64InputStream
version:1.4
Base64 encoding issue for larger avi files
version:1.4
org.apache.commons.codec.net.URLCodec.ESCAPE_CHAR isn't final but should be
version:1.2;1.3;1.4
org.apache.commons.codec.language.RefinedSoundex.US_ENGLISH_MAPPING should be package protected MALICIOUS_CODE
version:1.4
org.apache.commons.codec.language.Soundex.US_ENGLISH_MAPPING should be package protected MALICIOUS_CODE
version:1.4
Caverphone encodes names starting and ending with "mb" incorrectly.
version:1.4
All links to fixed bugs in the "Changes Report" http://commons.apache.org/codec/changes-report.html point nowhere; e.g. http://issues.apache.org/jira/browse/34157. Looks as if all JIRA tickets were renumbered.
version:1.1;1.2;1.3;1.4
Regression: Base64.encode(chunk=true) has bug when input length is multiple of 76
version:1.4
DigestUtils: MD5 checksum is not calculated correctly on linux64-platforms
version:1.3;1.4
new Base64().encode() appends a CRLF; and chunks results into 76 character lines
version:1.4
Base64 encode() method is no longer thread-safe; breaking clients using it as a shared BinaryEncoder
version:1.4
Base64 default constructor behaviour changed to enable chunking in 1.4
version:1.4
Base64InputStream causes NullPointerException on some input
version:1.4
Base64.encodeBase64String() shouldn't chunk
version:1.4
2. org.apache.httpcomponents httpclient
version: 4.1.3
Jira issues:
IIS and fragments in "Location:" headers
version:4.1.3
CachingHttpClient - Erroneous revalidation response date leads to a response not being properly consumed / connection held
version:4.1.3
"Vary: Cookie" header not working
version:4.1.3
Redirect with underscore in hostname causes ProtocolException
version:4.1.3
CircularRedirectException is falsely thrown on URI case mismatch
version:4.1.3;4.2.2
3. commons-io commons-io
version: 2.1
Jira issues:
Various methods of class 'org.apache.commons.io.FileUtils' incorrectly suppress 'java.io.IOException's.
version:2.1
getPrefixLength returns null if filename has leading slashes
version:2.0.1;2.1
ArrayIndexOutOfBoundsException in BOMInputStream when reading a file without BOM multiple times
version:2.1
TeeOutputStream does not call branch.close() when main.close() throws an exception
version:2.1
The second constructor of Tailer class does not pass 'delay' to the third one
version:2.1
ReaderInputStream#read(byte[] b; int off; int len) should always return 0 for length == 0
version:2.1
ReaderInputStream#read(byte[] b; int off; int len) should check for valid parameters
version:2.1
FileUtils.sizeOfDirectory follows symbolic links.
version:2.1
Regression in FileUtils.readFileToString from 2.0.1
version:2.1;2.2;2.3;2.4
4. commons-lang commons-lang
version: 2.5
Jira issues:
Testing with JDK 1.7
version:2.5
Some StringUtils methods should take an int character instead of char to use String API features.
version:2.5
SystemUtils.getJavaVersionAsFloat throws StringIndexOutOfBoundsException on Android runtime/Dalvik VM
version:2.5
NumberUtils createNumber throws a StringIndexOutOfBoundsException when argument containing "e" and "E" is passed in
version:2.5
FastDateFormat.format() outputs incorrect week of year because locale isn't respected
version:2.5
RandomStringUtils.random(count; 0; 0; false; false; universe; random) always throws java.lang.ArrayIndexOutOfBoundsException
version:2.5;2.6;3.1
Exception when combining custom and choice format in ExtendedMessageFormat
version:2.5;2.6

Sincerely~
FDU Software Engineering Lab
Marth 14th,2019

mvn install does not work. group id needs to be

org.elasticsearch

repository needs to be added:

 <repositories>
  <repository>
     <id>sonatype-releases</id>
     <name>Sonatype Releases Repository</name>
     <url>http://oss.sonatype.org/content/repositories/releases/</url>
  </repository>
 </repositories>

But even then it says:

package com.sensei.search.client.json does not exist or

SolrQueryProducer.java:[7,42] cannot find symbol
symbol : class Range
location: package com.senseidb.search.client.json.req

The main README file links to https://linkedin.jira.com/browse/SENSEI which is broken

Request made from SensiClientApp:
Post data:
{"bql":"describe cars;"}:

Exception:
2012/01/23 11:38:56.792 INFO [querylog] [] bql=DESCRIBE cars;
2012/01/23 11:38:56.793 ERROR [log] [] /sensei
java.lang.NullPointerException
at com.senseidb.util.JsonTemplateProcessor.getTemplates(JsonTemplateProcessor.java:18)
at com.senseidb.util.JsonTemplateProcessor.substituteTemplates(JsonTemplateProcessor.java:38)
at com.senseidb.util.RequestConverter2.fromJSON(RequestConverter2.java:149)
at com.senseidb.search.req.SenseiRequest.fromJSON(SenseiRequest.java:626)
at com.senseidb.servlet.AbstractSenseiClientServlet.handleSenseiRequest(AbstractSenseiClientServlet.java:212)
at com.senseidb.servlet.AbstractSenseiClientServlet.doGet(AbstractSenseiClientServlet.java:400)
at com.senseidb.servlet.AbstractSenseiClientServlet.doPost(AbstractSenseiClientServlet.java:424)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1221)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:78)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:131)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:945)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
2012/01/23 11:39:41.010 INFO [ClientChannelHandler] [] Expired 0 stale entries from the request map

I am getting this :

[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building sensei core 1.5.8-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[WARNING] The POM for com.linkedin.zoie:zoie-core:jar:3.3.1-SNAPSHOT is missing, no dependency information available
[WARNING] The POM for com.linkedin.zoie:zoie-jms:jar:3.3.1-SNAPSHOT is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] sensei parent ..................................... SUCCESS [1.303s]
[INFO] sensei core ....................................... FAILURE [0.462s]
[INFO] sensei gateways ................................... SKIPPED
[INFO] sensei hadoop indexing ............................ SKIPPED
[INFO] sensei gateways ................................... SKIPPED
[INFO] sensei java client ................................ SKIPPED
[INFO] sensei war ........................................ SKIPPED
[INFO] sensei ............................................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.219s
[INFO] Finished at: Mon Aug 11 14:04:33 IST 2014
[INFO] Final Memory: 14M/218M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project sensei-core: Could not resolve dependencies for project com.linkedin.sensei:sensei-core:jar:1.5.8-SNAPSHOT: The following artifacts could not be resolved: com.linkedin.zoie:zoie-core:jar:3.3.1-SNAPSHOT, com.linkedin.zoie:zoie-jms:jar:3.3.1-SNAPSHOT: Failure to find com.linkedin.zoie:zoie-core:jar:3.3.1-SNAPSHOT in http://repo.codahale.com/ was cached in the local repository, resolution will not be reattempted until the update interval of codahale has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :sensei-core
~/Desktop/Github/sensei-master

sorry for my naive question,the com.sensei.indexing.api.Text.java produce the error:
Invalid type Field.Store for the annotation attribute Text.store; only primitive type, String, Class, annotation, enumeration are permitted or 1-dimensional arrays thereof

Can you address a couple of instances of language in the project where the wording can be made more inclusive? (example: whiltelist -> allowlist). We are trying to make the code in all LinkedIn projects more inclusive. Could you please examine whether or not these need to be updated, and make the changes? For suggested replacements see go/inclusivelanguage or google. THANK YOU!

I'm trying to build some UI components to interact with sensei, similar to those I built on https://github.com/flaptor/indextank-jquery/

I noticed there are 2 clients on sensei's tree:

• clients/javascript/sensei-client-1.0.0.js
• sensei-core/src/main/webapp/js/sensei-client.js

It seems the latter is the good one, but I want to make sure that's the case before extending it and contributing back. Maybe someone already started doing related work

is there an EBNF of the BQL language I can study ?

Hi sensei people!
Used sensei at LinkedIn a few times for NUS model builds and a hack day. I wanted to see how far the project has gone since I left so I cloned this repository and tried to build it by running mvn-install.sh followed by build.sh in the bin directory. Unfortunately build failed with the following message. Is there a workaround or hotfix you could loop me in on?

[ERROR] Failed to execute goal on project sensei-core: Could not resolve dependencies for project com.senseidb:sensei-core:jar:1.1.3-SNAPSHOT: Could not find artifact com.linkedin.zoie:zoie-jms:jar:3.2.0-SNAPSHOT in labs-consol-release (http://labs.consol.de/maven/repository) -> [Help 1]