| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
- We effectively stopped providing it runtime since
https://github.com/vespa-engine/vespa/pull/7696
|
|
|
|
|
| |
Error message:
Error fetching link: /Users/gv/git/vespa/testutil/target/site/apidocs/package-list. Ignored it.
|
| |
|
| |
|
|
|
|
| |
- Uses asm 7
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This reverts commit cd470d8ac8a58c943748f028a37d864507628e99.
|
| |
|
|\
| |
| | |
Enable ABI checking on modules with public APIs
|
| |
| |
| |
| |
| | |
Instead of configuring in each module separately, put all configuration
to parent and let the relevant modules just enable the plugin.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds a new ZooKeeper backed flag source. It is defined in a new module
configserver-flags to allow as many as possible config server modules to depend
on it by minimizing dependencies.
The content of the ZK backed flag source can be viewed and modified through
REST API on the config server/controller. The data stored per flag looks like
{
"rules": [
{
"conditions": [
{ "type": "whitelist", "dimension": "hostname", "values": ["host1"] }
],
"value": true
}
]
}
typical for enabling a feature flag on host1.
2 types of conditions are so far supported: whitelist and blacklist. All the
conditions must match in order for the value to apply. If the value is null (or
absent), the default value will be used. At the time the flag's value is
retrieved, it is resolved against the conditions with the current zone,
hostname, and/or application.
The same data structure is used for FileFlagSource for files in
/etc/vespa/flags with the ".2" extension.
The FlagSource component injected in the config server is changed to:
1. Return the flag value if specified in /etc/vespa/flags, or otherwise
2. return flag value from ZooKeeper (same as REST API)
The current flags (module) is also changed:
- All flags must be defined in com.yahoo.vespa.flags.Flags. This allows the ZK
backed flag source additional sanity checking when modifying flags.
- If it makes sense to have different flag value depending on e.g. the
application, then at some point before the value is retrieved, one has to
bind the flag to that application (using with() to set up the fetch vector).
Future changes would be to 0. make a merged FlagSource in host admin, 1. add
support for viewing and modifying feature flags in dashboard, 2. in hv tool.
|
|
|
|
|
|
|
|
|
| |
- Update FastCharStream method names to follow changes in
generated CharStream class.
- Update expected test output due to improvements in generated
code.
- Improve ability to debug tests by more clearly printing out
the diff between expected and actual output.
|
|
|
|
| |
+ Remove unused management for old javacc plugin.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
https://github.com/vespa-engine/vespa/issues/6403
|
| |
|
|\
| |
| | |
Add version management for enforcer-plugin.
|
| | |
|
|/ |
|
|
|
|
| |
- This fell out of an earlier commit that claimed to do the same.
|
|
|
|
| |
Workaround for: Require-Capability: osg.ee=UNKNONWN
|
|
|
|
|
|
|
|
|
| |
Problem shading JAR vespa-http-client.jar entry
com/yahoo/vespa/http/client/Result$ResultType.class:
java.lang.IllegalArgumentException
IllegalArgumentException
at org.objectweb.asm.ClassReader.<init> (ClassReader.java:160)
|
|
|
|
|
|
| |
* NPE was thrown
* Set html version for javadoc-plugin to avoid warning.
(jdk-based activation of profile)
|
|
|
|
|
| |
- IllegalArgumentException: Failed to analyze
com/yahoo/config/codegen/LeafCNode$NoClassNoDefaultLeafCNode.class
|
| |
|
| |
|
|
|
|
|
|
| |
- asm-debug-all does not yet exist in a Java 9 compatible version.
- aries.spifly (pulls in aries-util and asm-debug-all) is no
longer required by jetty-util.
|