Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 7 112 | repo_url stringlengths 36 141 | action stringclasses 3 values | title stringlengths 1 744 | labels stringlengths 4 574 | body stringlengths 9 211k | index stringclasses 10 values | text_combine stringlengths 96 211k | label stringclasses 2 values | text stringlengths 96 188k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
700,891 | 24,077,214,098 | IssuesEvent | 2022-09-18 23:46:45 | naia-lib/naia | https://api.github.com/repos/naia-lib/naia | closed | Client should emit an AuthFailed event | naia bug feature high priority | If a Client fails to Auth, it currently will just keep trying to connect to the Server with the same Auth payload ... forever ...
Instead, the Server should repeatedly send back an "AuthFailed" message to the Client, and the Client should stop the handshaking process until you call `Client.connect()` again (hopefully with a new and working Auth payload) | 1.0 | Client should emit an AuthFailed event - If a Client fails to Auth, it currently will just keep trying to connect to the Server with the same Auth payload ... forever ...
Instead, the Server should repeatedly send back an "AuthFailed" message to the Client, and the Client should stop the handshaking process until you call `Client.connect()` again (hopefully with a new and working Auth payload) | non_process | client should emit an authfailed event if a client fails to auth it currently will just keep trying to connect to the server with the same auth payload forever instead the server should repeatedly send back an authfailed message to the client and the client should stop the handshaking process until you call client connect again hopefully with a new and working auth payload | 0 |
16,685 | 21,791,064,560 | IssuesEvent | 2022-05-14 22:52:20 | keras-team/keras-cv | https://api.github.com/repos/keras-team/keras-cv | closed | Support `RandomChoice` - randomly pick from list! | contribution-welcome preprocessing | **Short Description**
Let's say in your training, you want to use all of the follows:
- `cutmix-mixup-fmix-mosaic`
- `gaussian_blur-zoom_blur-motion_blur-median-blur`
- `optical_distortion-elastic-transform-grid_distortion`
- `equalization-clahe`
- `grid_mask-cutput`
- etc.
then it's required to randomly pick one among others (in general) in a single pass during training, for example: `[cutmix-zoom_blur-optical_distortion-clahe-cutput]`. So, it would be nice to have a functionality to feasibly do this task.
**Papers**
Most of the top used libraries/frameworks offer similar strategies.
**Existing Implementations**
- https://pytorch.org/vision/main/generated/torchvision.transforms.RandomChoice.html
**Other Information**
In the title, the name `RandomChoice` is picked for demonstration purposes. The thing is, we may need to introduce or modify any of the existing functionality if it's reasonable to take.
| 1.0 | Support `RandomChoice` - randomly pick from list! - **Short Description**
Let's say in your training, you want to use all of the follows:
- `cutmix-mixup-fmix-mosaic`
- `gaussian_blur-zoom_blur-motion_blur-median-blur`
- `optical_distortion-elastic-transform-grid_distortion`
- `equalization-clahe`
- `grid_mask-cutput`
- etc.
then it's required to randomly pick one among others (in general) in a single pass during training, for example: `[cutmix-zoom_blur-optical_distortion-clahe-cutput]`. So, it would be nice to have a functionality to feasibly do this task.
**Papers**
Most of the top used libraries/frameworks offer similar strategies.
**Existing Implementations**
- https://pytorch.org/vision/main/generated/torchvision.transforms.RandomChoice.html
**Other Information**
In the title, the name `RandomChoice` is picked for demonstration purposes. The thing is, we may need to introduce or modify any of the existing functionality if it's reasonable to take.
| process | support randomchoice randomly pick from list short description let s say in your training you want to use all of the follows cutmix mixup fmix mosaic gaussian blur zoom blur motion blur median blur optical distortion elastic transform grid distortion equalization clahe grid mask cutput etc then it s required to randomly pick one among others in general in a single pass during training for example so it would be nice to have a functionality to feasibly do this task papers most of the top used libraries frameworks offer similar strategies existing implementations other information in the title the name randomchoice is picked for demonstration purposes the thing is we may need to introduce or modify any of the existing functionality if it s reasonable to take | 1 |
784,562 | 27,576,415,080 | IssuesEvent | 2023-03-08 13:20:48 | SeldonIO/alibi | https://api.github.com/repos/SeldonIO/alibi | closed | Eager mode support in Counterfactuals and CEM | Priority: High internal-mle | Hi,
I'm finding that my ONNX image classification model (loaded with the ONNX package and converted to TensorFlow) works with AnchorImage but not with Counterfactuals or CEM. I've tried providing the model directly to the CounterFactual object, but I've also tried with a predict function (since the model expects inputs of a different shape). Neither way is successful, but the latter approach is shown below.
Is there a reason that AnchorImage and Counterfactuals/CEM would treat this model differently under the hood?
Here is the failing code, followed by the error.
Thank you for your help.
```
tf.compat.v1.disable_eager_execution()
tf.compat.v1.reset_default_graph()
model = onnx.load('./model.onnx')
tf_model = prepare(model)
shape = (1,) + img_stack.shape[1:] # replace first dimension with 1 (one explanation at a time)
target_proba = 1.0
tol = 0.01 # want counterfactuals with p(class)>0.99
target_class = 'other' # any class other than the predicted one will do
max_iter = 1000
lam_init = 1e-1
max_lam_steps = 10
learning_rate_init = 0.1
feature_range = (img_stack.min(),img_stack.max())
def predict_fn(img_stack):
img_stack = img_stack.transpose(0,3,1,2)
img_stack = np.asarray(img_stack, dtype=np.float32)
return tf_model.run(img_stack)[0] #Inference
cf = CounterFactual(predict_fn, shape=shape, target_proba=target_proba, tol=tol,
target_class=target_class, max_iter=max_iter, lam_init=lam_init,
max_lam_steps=max_lam_steps, learning_rate_init=learning_rate_init,
feature_range=feature_range)
```
---------------------------------------------------------------------------
RuntimeError Traceback (most recent call last)
<ipython-input-12-c5f566747f16> in <module>
12 target_class=target_class, max_iter=max_iter, lam_init=lam_init,
13 max_lam_steps=max_lam_steps, learning_rate_init=learning_rate_init,
---> 14 feature_range=feature_range)
15
16 start_time = time()
/.../lib/python3.7/site-packages/alibi/explainers/counterfactual.py in __init__(self, predict_fn, shape, distance_fn, target_proba, target_class, max_iter, early_stop, lam_init, max_lam_steps, tol, learning_rate_init, feature_range, eps, init, decay, write_dir, debug, sess)
177 self.model = False
178
--> 179 self.n_classes = self.predict_fn(np.zeros(shape)).shape[1]
180
181 # flag to keep track if explainer is fit or not
<ipython-input-5-4c525538c54f> in predict_img(img_stack)
3 # img = img.reshape(1,3,224,224) # Transform to Input Tensor
4 img_stack = np.asarray(img_stack, dtype=np.float32)
----> 5 return tf_model.run(img_stack)[0] #Inference
/.../lib/python3.7/site-packages/onnx_tf/backend_rep.py in run(self, inputs, **kwargs)
91 input_dict = dict([(x[0], tf.constant(x[1])) for x in feed_dict.items()])
92
---> 93 output_values = self.tf_module(**input_dict)
94 output_values = [
95 val.numpy() if isinstance(val, tf.Tensor) else val
/.../lib/python3.7/site-packages/tensorflow/python/eager/def_function.py in __call__(self, *args, **kwds)
826 tracing_count = self.experimental_get_tracing_count()
827 with trace.Trace(self._name) as tm:
--> 828 result = self._call(*args, **kwds)
829 compiler = "xla" if self._experimental_compile else "nonXla"
830 new_tracing_count = self.experimental_get_tracing_count()
/.../lib/python3.7/site-packages/tensorflow/python/eager/def_function.py in _call(self, *args, **kwds)
860 # In this case we have not created variables on the first call. So we can
861 # run the first trace but we should fail if variables are created.
--> 862 results = self._stateful_fn(*args, **kwds)
863 if self._created_variables:
864 raise ValueError("Creating variables on a non-first call to a function"
/.../lib/python3.7/site-packages/tensorflow/python/eager/function.py in __call__(self, *args, **kwargs)
2941 filtered_flat_args) = self._maybe_define_function(args, kwargs)
2942 return graph_function._call_flat(
-> 2943 filtered_flat_args, captured_inputs=graph_function.captured_inputs) # pylint: disable=protected-access
2944
2945 @property
/.../lib/python3.7/site-packages/tensorflow/python/eager/function.py in _call_flat(self, args, captured_inputs, cancellation_manager)
1930 {"PartitionedCall": self._get_gradient_function(),
1931 "StatefulPartitionedCall": self._get_gradient_function()}):
-> 1932 flat_outputs = forward_function.call(ctx, args_with_tangents)
1933 forward_backward.record(flat_outputs)
1934 return self._build_call_outputs(flat_outputs)
/.../lib/python3.7/site-packages/tensorflow/python/eager/function.py in call(self, ctx, args, cancellation_manager)
587 executing_eagerly=executing_eagerly,
588 config=config,
--> 589 executor_type=executor_type)
590
591 for i, func_graph_output in enumerate(self._func_graph_outputs):
/...t/lib/python3.7/site-packages/tensorflow/python/ops/functional_ops.py in partitioned_call(args, f, tout, executing_eagerly, config, executor_type)
1187 # The generated binding returns an empty list for functions that don't
1188 # return any Tensors, hence the need to use `create_op` directly.
-> 1189 args = [ops.convert_to_tensor(x) for x in args]
1190 tin_attr = attr_value_pb2.AttrValue(
1191 list=attr_value_pb2.AttrValue.ListValue(
/.../lib/python3.7/site-packages/tensorflow/python/ops/functional_ops.py in <listcomp>(.0)
1187 # The generated binding returns an empty list for functions that don't
1188 # return any Tensors, hence the need to use `create_op` directly.
-> 1189 args = [ops.convert_to_tensor(x) for x in args]
1190 tin_attr = attr_value_pb2.AttrValue(
1191 list=attr_value_pb2.AttrValue.ListValue(
/.../lib/python3.7/site-packages/tensorflow/python/profiler/trace.py in wrapped(*args, **kwargs)
161 with Trace(trace_name, **trace_kwargs):
162 return func(*args, **kwargs)
--> 163 return func(*args, **kwargs)
164
165 return wrapped
/.../lib/python3.7/site-packages/tensorflow/python/framework/ops.py in convert_to_tensor(value, dtype, name, as_ref, preferred_dtype, dtype_hint, ctx, accepted_result_types)
1497 graph = get_default_graph()
1498 if not graph.building_function:
-> 1499 raise RuntimeError("Attempting to capture an EagerTensor without "
1500 "building a function.")
1501 return graph.capture(value, name=name)
RuntimeError: Attempting to capture an EagerTensor without building a function. | 1.0 | Eager mode support in Counterfactuals and CEM - Hi,
I'm finding that my ONNX image classification model (loaded with the ONNX package and converted to TensorFlow) works with AnchorImage but not with Counterfactuals or CEM. I've tried providing the model directly to the CounterFactual object, but I've also tried with a predict function (since the model expects inputs of a different shape). Neither way is successful, but the latter approach is shown below.
Is there a reason that AnchorImage and Counterfactuals/CEM would treat this model differently under the hood?
Here is the failing code, followed by the error.
Thank you for your help.
```
tf.compat.v1.disable_eager_execution()
tf.compat.v1.reset_default_graph()
model = onnx.load('./model.onnx')
tf_model = prepare(model)
shape = (1,) + img_stack.shape[1:] # replace first dimension with 1 (one explanation at a time)
target_proba = 1.0
tol = 0.01 # want counterfactuals with p(class)>0.99
target_class = 'other' # any class other than the predicted one will do
max_iter = 1000
lam_init = 1e-1
max_lam_steps = 10
learning_rate_init = 0.1
feature_range = (img_stack.min(),img_stack.max())
def predict_fn(img_stack):
img_stack = img_stack.transpose(0,3,1,2)
img_stack = np.asarray(img_stack, dtype=np.float32)
return tf_model.run(img_stack)[0] #Inference
cf = CounterFactual(predict_fn, shape=shape, target_proba=target_proba, tol=tol,
target_class=target_class, max_iter=max_iter, lam_init=lam_init,
max_lam_steps=max_lam_steps, learning_rate_init=learning_rate_init,
feature_range=feature_range)
```
---------------------------------------------------------------------------
RuntimeError Traceback (most recent call last)
<ipython-input-12-c5f566747f16> in <module>
12 target_class=target_class, max_iter=max_iter, lam_init=lam_init,
13 max_lam_steps=max_lam_steps, learning_rate_init=learning_rate_init,
---> 14 feature_range=feature_range)
15
16 start_time = time()
/.../lib/python3.7/site-packages/alibi/explainers/counterfactual.py in __init__(self, predict_fn, shape, distance_fn, target_proba, target_class, max_iter, early_stop, lam_init, max_lam_steps, tol, learning_rate_init, feature_range, eps, init, decay, write_dir, debug, sess)
177 self.model = False
178
--> 179 self.n_classes = self.predict_fn(np.zeros(shape)).shape[1]
180
181 # flag to keep track if explainer is fit or not
<ipython-input-5-4c525538c54f> in predict_img(img_stack)
3 # img = img.reshape(1,3,224,224) # Transform to Input Tensor
4 img_stack = np.asarray(img_stack, dtype=np.float32)
----> 5 return tf_model.run(img_stack)[0] #Inference
/.../lib/python3.7/site-packages/onnx_tf/backend_rep.py in run(self, inputs, **kwargs)
91 input_dict = dict([(x[0], tf.constant(x[1])) for x in feed_dict.items()])
92
---> 93 output_values = self.tf_module(**input_dict)
94 output_values = [
95 val.numpy() if isinstance(val, tf.Tensor) else val
/.../lib/python3.7/site-packages/tensorflow/python/eager/def_function.py in __call__(self, *args, **kwds)
826 tracing_count = self.experimental_get_tracing_count()
827 with trace.Trace(self._name) as tm:
--> 828 result = self._call(*args, **kwds)
829 compiler = "xla" if self._experimental_compile else "nonXla"
830 new_tracing_count = self.experimental_get_tracing_count()
/.../lib/python3.7/site-packages/tensorflow/python/eager/def_function.py in _call(self, *args, **kwds)
860 # In this case we have not created variables on the first call. So we can
861 # run the first trace but we should fail if variables are created.
--> 862 results = self._stateful_fn(*args, **kwds)
863 if self._created_variables:
864 raise ValueError("Creating variables on a non-first call to a function"
/.../lib/python3.7/site-packages/tensorflow/python/eager/function.py in __call__(self, *args, **kwargs)
2941 filtered_flat_args) = self._maybe_define_function(args, kwargs)
2942 return graph_function._call_flat(
-> 2943 filtered_flat_args, captured_inputs=graph_function.captured_inputs) # pylint: disable=protected-access
2944
2945 @property
/.../lib/python3.7/site-packages/tensorflow/python/eager/function.py in _call_flat(self, args, captured_inputs, cancellation_manager)
1930 {"PartitionedCall": self._get_gradient_function(),
1931 "StatefulPartitionedCall": self._get_gradient_function()}):
-> 1932 flat_outputs = forward_function.call(ctx, args_with_tangents)
1933 forward_backward.record(flat_outputs)
1934 return self._build_call_outputs(flat_outputs)
/.../lib/python3.7/site-packages/tensorflow/python/eager/function.py in call(self, ctx, args, cancellation_manager)
587 executing_eagerly=executing_eagerly,
588 config=config,
--> 589 executor_type=executor_type)
590
591 for i, func_graph_output in enumerate(self._func_graph_outputs):
/...t/lib/python3.7/site-packages/tensorflow/python/ops/functional_ops.py in partitioned_call(args, f, tout, executing_eagerly, config, executor_type)
1187 # The generated binding returns an empty list for functions that don't
1188 # return any Tensors, hence the need to use `create_op` directly.
-> 1189 args = [ops.convert_to_tensor(x) for x in args]
1190 tin_attr = attr_value_pb2.AttrValue(
1191 list=attr_value_pb2.AttrValue.ListValue(
/.../lib/python3.7/site-packages/tensorflow/python/ops/functional_ops.py in <listcomp>(.0)
1187 # The generated binding returns an empty list for functions that don't
1188 # return any Tensors, hence the need to use `create_op` directly.
-> 1189 args = [ops.convert_to_tensor(x) for x in args]
1190 tin_attr = attr_value_pb2.AttrValue(
1191 list=attr_value_pb2.AttrValue.ListValue(
/.../lib/python3.7/site-packages/tensorflow/python/profiler/trace.py in wrapped(*args, **kwargs)
161 with Trace(trace_name, **trace_kwargs):
162 return func(*args, **kwargs)
--> 163 return func(*args, **kwargs)
164
165 return wrapped
/.../lib/python3.7/site-packages/tensorflow/python/framework/ops.py in convert_to_tensor(value, dtype, name, as_ref, preferred_dtype, dtype_hint, ctx, accepted_result_types)
1497 graph = get_default_graph()
1498 if not graph.building_function:
-> 1499 raise RuntimeError("Attempting to capture an EagerTensor without "
1500 "building a function.")
1501 return graph.capture(value, name=name)
RuntimeError: Attempting to capture an EagerTensor without building a function. | non_process | eager mode support in counterfactuals and cem hi i m finding that my onnx image classification model loaded with the onnx package and converted to tensorflow works with anchorimage but not with counterfactuals or cem i ve tried providing the model directly to the counterfactual object but i ve also tried with a predict function since the model expects inputs of a different shape neither way is successful but the latter approach is shown below is there a reason that anchorimage and counterfactuals cem would treat this model differently under the hood here is the failing code followed by the error thank you for your help tf compat disable eager execution tf compat reset default graph model onnx load model onnx tf model prepare model shape img stack shape replace first dimension with one explanation at a time target proba tol want counterfactuals with p class target class other any class other than the predicted one will do max iter lam init max lam steps learning rate init feature range img stack min img stack max def predict fn img stack img stack img stack transpose img stack np asarray img stack dtype np return tf model run img stack inference cf counterfactual predict fn shape shape target proba target proba tol tol target class target class max iter max iter lam init lam init max lam steps max lam steps learning rate init learning rate init feature range feature range runtimeerror traceback most recent call last in target class target class max iter max iter lam init lam init max lam steps max lam steps learning rate init learning rate init feature range feature range start time time lib site packages alibi explainers counterfactual py in init self predict fn shape distance fn target proba target class max iter early stop lam init max lam steps tol learning rate init feature range eps init decay write dir debug sess self model false self n classes self predict fn np zeros shape shape flag to keep track if explainer is fit or not in predict img img stack img img reshape transform to input tensor img stack np asarray img stack dtype np return tf model run img stack inference lib site packages onnx tf backend rep py in run self inputs kwargs input dict dict tf constant x for x in feed dict items output values self tf module input dict output values val numpy if isinstance val tf tensor else val lib site packages tensorflow python eager def function py in call self args kwds tracing count self experimental get tracing count with trace trace self name as tm result self call args kwds compiler xla if self experimental compile else nonxla new tracing count self experimental get tracing count lib site packages tensorflow python eager def function py in call self args kwds in this case we have not created variables on the first call so we can run the first trace but we should fail if variables are created results self stateful fn args kwds if self created variables raise valueerror creating variables on a non first call to a function lib site packages tensorflow python eager function py in call self args kwargs filtered flat args self maybe define function args kwargs return graph function call flat filtered flat args captured inputs graph function captured inputs pylint disable protected access property lib site packages tensorflow python eager function py in call flat self args captured inputs cancellation manager partitionedcall self get gradient function statefulpartitionedcall self get gradient function flat outputs forward function call ctx args with tangents forward backward record flat outputs return self build call outputs flat outputs lib site packages tensorflow python eager function py in call self ctx args cancellation manager executing eagerly executing eagerly config config executor type executor type for i func graph output in enumerate self func graph outputs t lib site packages tensorflow python ops functional ops py in partitioned call args f tout executing eagerly config executor type the generated binding returns an empty list for functions that don t return any tensors hence the need to use create op directly args tin attr attr value attrvalue list attr value attrvalue listvalue lib site packages tensorflow python ops functional ops py in the generated binding returns an empty list for functions that don t return any tensors hence the need to use create op directly args tin attr attr value attrvalue list attr value attrvalue listvalue lib site packages tensorflow python profiler trace py in wrapped args kwargs with trace trace name trace kwargs return func args kwargs return func args kwargs return wrapped lib site packages tensorflow python framework ops py in convert to tensor value dtype name as ref preferred dtype dtype hint ctx accepted result types graph get default graph if not graph building function raise runtimeerror attempting to capture an eagertensor without building a function return graph capture value name name runtimeerror attempting to capture an eagertensor without building a function | 0 |
59,548 | 7,260,090,155 | IssuesEvent | 2018-02-18 04:31:40 | insanewolfhd2/portfolio | https://api.github.com/repos/insanewolfhd2/portfolio | opened | [Re-Design] Add price estimator | Design enhancement | For corporations and businesses, increase the prices, individuals get cheaper.
Full-time and part-time seekers will get an estimated hourly rate, quick website will get set price. | 1.0 | [Re-Design] Add price estimator - For corporations and businesses, increase the prices, individuals get cheaper.
Full-time and part-time seekers will get an estimated hourly rate, quick website will get set price. | non_process | add price estimator for corporations and businesses increase the prices individuals get cheaper full time and part time seekers will get an estimated hourly rate quick website will get set price | 0 |
4,100 | 4,795,451,016 | IssuesEvent | 2016-11-01 01:09:15 | LOZORD/xanadu | https://api.github.com/repos/LOZORD/xanadu | opened | Set up Codacy coverage reporting | enhancement help wanted infrastructure | See #79 for Codacy addition. I have already registered this repo with Codacy. The only thing we need is the coverage reporting (via Istanbul) shown here:
https://github.com/codacy/node-codacy-coverage#installation | 1.0 | Set up Codacy coverage reporting - See #79 for Codacy addition. I have already registered this repo with Codacy. The only thing we need is the coverage reporting (via Istanbul) shown here:
https://github.com/codacy/node-codacy-coverage#installation | non_process | set up codacy coverage reporting see for codacy addition i have already registered this repo with codacy the only thing we need is the coverage reporting via istanbul shown here | 0 |
12,232 | 14,743,638,174 | IssuesEvent | 2021-01-07 14:12:22 | kdjstudios/SABillingGitlab | https://api.github.com/repos/kdjstudios/SABillingGitlab | closed | Site 068 Portland - Unable to process Credit Card Transactions | parent:1554 | anc-process anp-important ant-bug ant-child/secondary | In GitLab by @kdjstudios on Sep 6, 2019, 10:49
**Submitted by:** <jeffrey.casey@answernet.com>
**Helpdesk:** http://www.servicedesk.answernet.com/profiles/ticket/9262551
**Server:** Internal
**Client/Site:** Portland
**Account:** Multiple
**Issue:**
Portland has just attempted to run Credit card payments on two different accounts (068-B01111 and 068-C02267). Both accounts state “something went wrong”.
Please look into this as soon as possible. The clock is ticking on some of these temporary credit card numbers. When the clock runs out the cards become invalid for collection. | 1.0 | Site 068 Portland - Unable to process Credit Card Transactions | parent:1554 - In GitLab by @kdjstudios on Sep 6, 2019, 10:49
**Submitted by:** <jeffrey.casey@answernet.com>
**Helpdesk:** http://www.servicedesk.answernet.com/profiles/ticket/9262551
**Server:** Internal
**Client/Site:** Portland
**Account:** Multiple
**Issue:**
Portland has just attempted to run Credit card payments on two different accounts (068-B01111 and 068-C02267). Both accounts state “something went wrong”.
Please look into this as soon as possible. The clock is ticking on some of these temporary credit card numbers. When the clock runs out the cards become invalid for collection. | process | site portland unable to process credit card transactions parent in gitlab by kdjstudios on sep submitted by helpdesk server internal client site portland account multiple issue portland has just attempted to run credit card payments on two different accounts and both accounts state “something went wrong” please look into this as soon as possible the clock is ticking on some of these temporary credit card numbers when the clock runs out the cards become invalid for collection | 1 |
22,484 | 31,395,272,913 | IssuesEvent | 2023-08-26 21:21:30 | lynnandtonic/nestflix.fun | https://api.github.com/repos/lynnandtonic/nestflix.fun | closed | Add Father Ben from Father Ted (has screenshots) | suggested title in process | Please add as much of the following info as you can:
Title: Father Ben
Type (film/tv show):
TV show
Film or show in which it appears: Father Ted
Is the parent film/show streaming anywhere?
All 4 (UK)
About when in the parent film/show does it appear? S2E6 (The Plague), at start of episode
Actual footage of the film/show can be seen (yes/no)? Yes
| 1.0 | Add Father Ben from Father Ted (has screenshots) - Please add as much of the following info as you can:
Title: Father Ben
Type (film/tv show):
TV show
Film or show in which it appears: Father Ted
Is the parent film/show streaming anywhere?
All 4 (UK)
About when in the parent film/show does it appear? S2E6 (The Plague), at start of episode
Actual footage of the film/show can be seen (yes/no)? Yes
| process | add father ben from father ted has screenshots please add as much of the following info as you can title father ben type film tv show tv show film or show in which it appears father ted is the parent film show streaming anywhere all uk about when in the parent film show does it appear the plague at start of episode actual footage of the film show can be seen yes no yes | 1 |
92,730 | 3,873,193,251 | IssuesEvent | 2016-04-11 16:07:50 | Esri/solutions-geoprocessing-toolbox | https://api.github.com/repos/Esri/solutions-geoprocessing-toolbox | opened | Range RIng tools in Visibility & Range toolbox should pull spatial ref from map | B - Enhancement F - Visibility G - Defense Team N - Visibility and Range priority-moderate V - ArcGIS Pro V - ArcMap | This is a question from Clark, could the Range Ring tools in Visibility and Range pull the spatial reference from the map if they are being run in ArcMap or ArcGIS Pro?
Have to research. Should be easy in ArcMap, not sure about Pro. | 1.0 | Range RIng tools in Visibility & Range toolbox should pull spatial ref from map - This is a question from Clark, could the Range Ring tools in Visibility and Range pull the spatial reference from the map if they are being run in ArcMap or ArcGIS Pro?
Have to research. Should be easy in ArcMap, not sure about Pro. | non_process | range ring tools in visibility range toolbox should pull spatial ref from map this is a question from clark could the range ring tools in visibility and range pull the spatial reference from the map if they are being run in arcmap or arcgis pro have to research should be easy in arcmap not sure about pro | 0 |
702,059 | 24,120,570,869 | IssuesEvent | 2022-09-20 18:19:09 | googleapis/nodejs-dlp | https://api.github.com/repos/googleapis/nodejs-dlp | closed | metadata: should list info types failed | type: bug priority: p1 api: dlp flakybot: issue | This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot).
If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.
---
commit: 7c53b9fb61d90cbc3e592070fcf577289d54ba21
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/146260ea-01e2-4622-a770-b7111df00aa4), [Sponge](http://sponge2/146260ea-01e2-4622-a770-b7111df00aa4)
status: failed
<details><summary>Test output</summary><br><pre>Command failed: node metadata.js long-door-651 infoTypes
16 UNAUTHENTICATED: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.
Error: Command failed: node metadata.js long-door-651 infoTypes
16 UNAUTHENTICATED: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.
at checkExecSyncError (child_process.js:635:11)
at Object.execSync (child_process.js:671:15)
at execSync (system-test/metadata.test.js:22:28)
at Context.<anonymous> (system-test/metadata.test.js:32:20)
at processImmediate (internal/timers.js:461:21)</pre></details> | 1.0 | metadata: should list info types failed - This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot).
If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.
---
commit: 7c53b9fb61d90cbc3e592070fcf577289d54ba21
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/146260ea-01e2-4622-a770-b7111df00aa4), [Sponge](http://sponge2/146260ea-01e2-4622-a770-b7111df00aa4)
status: failed
<details><summary>Test output</summary><br><pre>Command failed: node metadata.js long-door-651 infoTypes
16 UNAUTHENTICATED: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.
Error: Command failed: node metadata.js long-door-651 infoTypes
16 UNAUTHENTICATED: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.
at checkExecSyncError (child_process.js:635:11)
at Object.execSync (child_process.js:671:15)
at execSync (system-test/metadata.test.js:22:28)
at Context.<anonymous> (system-test/metadata.test.js:32:20)
at processImmediate (internal/timers.js:461:21)</pre></details> | non_process | metadata should list info types failed this test failed to configure my behavior see if i m commenting on this issue too often add the flakybot quiet label and i will stop commenting commit buildurl status failed test output command failed node metadata js long door infotypes unauthenticated request had invalid authentication credentials expected oauth access token login cookie or other valid authentication credential see error command failed node metadata js long door infotypes unauthenticated request had invalid authentication credentials expected oauth access token login cookie or other valid authentication credential see at checkexecsyncerror child process js at object execsync child process js at execsync system test metadata test js at context system test metadata test js at processimmediate internal timers js | 0 |
321,642 | 9,806,758,580 | IssuesEvent | 2019-06-12 12:14:59 | SAP/cloud-commerce-spartacus-storefront | https://api.github.com/repos/SAP/cloud-commerce-spartacus-storefront | opened | Update Cypress | priority/LOW | Cypress released 3.3.1 some time ago.
Might be worth upgrading to potentially fix some bugs and improve perf. | 1.0 | Update Cypress - Cypress released 3.3.1 some time ago.
Might be worth upgrading to potentially fix some bugs and improve perf. | non_process | update cypress cypress released some time ago might be worth upgrading to potentially fix some bugs and improve perf | 0 |
478,259 | 13,776,135,372 | IssuesEvent | 2020-10-08 09:02:13 | AY2021S1-CS2103-T16-3/tp | https://api.github.com/repos/AY2021S1-CS2103-T16-3/tp | closed | As a OHS Admin I can allocate a room to a student | priority.High type.Story | so that I can allocate a student to room before the semester starts. | 1.0 | As a OHS Admin I can allocate a room to a student - so that I can allocate a student to room before the semester starts. | non_process | as a ohs admin i can allocate a room to a student so that i can allocate a student to room before the semester starts | 0 |
10,611 | 13,436,747,031 | IssuesEvent | 2020-09-07 14:49:57 | jgraley/inferno-cpp2v | https://api.github.com/repos/jgraley/inferno-cpp2v | closed | Force variables in CSPs | Constraint Processing bug | Add a `force_assignments` arg to `Solver::Start()`, and force the following:
**Root variable**
Force the variable corresponding to the root agent to the given `start_x`.
**Master boundary couplings**
`AndRuleEngine` leaves master-coupled agents out of `my_agents` and deals explicitly with master couplings inside `DecidedCompare()`. CSP solvers will have no such knowledge. For them, we need to include the "master boundary" agents in the list of variables (luckily, deriving them from the systemic constraints does this successfully (most of the time; see #126)) and then "Force" the master boundary variables to the values determined from master couplings.
These should also be included in coupling residuals. | 1.0 | Force variables in CSPs - Add a `force_assignments` arg to `Solver::Start()`, and force the following:
**Root variable**
Force the variable corresponding to the root agent to the given `start_x`.
**Master boundary couplings**
`AndRuleEngine` leaves master-coupled agents out of `my_agents` and deals explicitly with master couplings inside `DecidedCompare()`. CSP solvers will have no such knowledge. For them, we need to include the "master boundary" agents in the list of variables (luckily, deriving them from the systemic constraints does this successfully (most of the time; see #126)) and then "Force" the master boundary variables to the values determined from master couplings.
These should also be included in coupling residuals. | process | force variables in csps add a force assignments arg to solver start and force the following root variable force the variable corresponding to the root agent to the given start x master boundary couplings andruleengine leaves master coupled agents out of my agents and deals explicitly with master couplings inside decidedcompare csp solvers will have no such knowledge for them we need to include the master boundary agents in the list of variables luckily deriving them from the systemic constraints does this successfully most of the time see and then force the master boundary variables to the values determined from master couplings these should also be included in coupling residuals | 1 |
13,317 | 15,784,179,219 | IssuesEvent | 2021-04-01 14:50:41 | zammad/zammad | https://api.github.com/repos/zammad/zammad | closed | mention in email body breaks email parsing | bug mail processing ticket verified | <!--
Hi there - thanks for filing an issue. Please ensure the following things before creating an issue - thank you! 🤓
Since november 15th we handle all requests, except real bugs, at our community board.
Full explanation: https://community.zammad.org/t/major-change-regarding-github-issues-community-board/21
Please post:
- Feature requests
- Development questions
- Technical questions
on the board -> https://community.zammad.org !
If you think you hit a bug, please continue:
- Search existing issues and the CHANGELOG.md for your issue - there might be a solution already
- Make sure to use the latest version of Zammad if possible
- Add the `log/production.log` file from your system. Attention: Make sure no confidential data is in it!
- Please write the issue in english
- Don't remove the template - otherwise we will close the issue without further comments
- Ask questions about Zammad configuration and usage at our mailinglist. See: https://zammad.org/participate
Note: We always do our best. Unfortunately, sometimes there are too many requests and we can't handle everything at once. If you want to prioritize/escalate your issue, you can do so by means of a support contract (see https://zammad.com/pricing#selfhosted).
* The upper textblock will be removed automatically when you submit your issue *
-->
### Infos:
* Used Zammad version: 4.0
* Installation method (source, package, ..): Repo https://dl.packager.io/srv/rpm/zammad/zammad/stable/el/7/x86_64/
* Operating system: CentOS 7
* Database + version: postgresql 9.2.24-4.el7_8
* Elasticsearch version: 7.12.0-1
* Browser + version: Firefox 78.9.0esr (64-Bit)
### Expected behavior:
* missing rights for mentions should not break the email parsing
* the email should not show up under /opt/zammad/tmp/unprocessable_mail, if it contains a mention with '@...'
### Actual behavior:
* parsing the mail generates an error: "ERROR: Can't process email, you will find it for bug reporting under /opt/zammad/tmp/unprocessable_mail/edd73f695ee7517e0ea3bd0143832594.eml, please create an issue at https://github.com/zammad/zammad/issues"
"ERROR: #<RuntimeError: User 23490 has no permission to mention other Users!>"
* running this command: zammad run rails r 'Channel::EmailParser.process_unprocessable_mails'
repeates the error again and again
* temporarily assigning the role 'agent' to the mentioned user makes the email run through
### Steps to reproduce the behavior:
* probably sending an email with a mention in the body, but I did not try a second time.
Yes I'm sure this is a bug and no feature request or a general question.
Complete output attached.
[zammad_mention_error.txt](https://github.com/zammad/zammad/files/6241453/zammad_mention_error.txt)
| 1.0 | mention in email body breaks email parsing - <!--
Hi there - thanks for filing an issue. Please ensure the following things before creating an issue - thank you! 🤓
Since november 15th we handle all requests, except real bugs, at our community board.
Full explanation: https://community.zammad.org/t/major-change-regarding-github-issues-community-board/21
Please post:
- Feature requests
- Development questions
- Technical questions
on the board -> https://community.zammad.org !
If you think you hit a bug, please continue:
- Search existing issues and the CHANGELOG.md for your issue - there might be a solution already
- Make sure to use the latest version of Zammad if possible
- Add the `log/production.log` file from your system. Attention: Make sure no confidential data is in it!
- Please write the issue in english
- Don't remove the template - otherwise we will close the issue without further comments
- Ask questions about Zammad configuration and usage at our mailinglist. See: https://zammad.org/participate
Note: We always do our best. Unfortunately, sometimes there are too many requests and we can't handle everything at once. If you want to prioritize/escalate your issue, you can do so by means of a support contract (see https://zammad.com/pricing#selfhosted).
* The upper textblock will be removed automatically when you submit your issue *
-->
### Infos:
* Used Zammad version: 4.0
* Installation method (source, package, ..): Repo https://dl.packager.io/srv/rpm/zammad/zammad/stable/el/7/x86_64/
* Operating system: CentOS 7
* Database + version: postgresql 9.2.24-4.el7_8
* Elasticsearch version: 7.12.0-1
* Browser + version: Firefox 78.9.0esr (64-Bit)
### Expected behavior:
* missing rights for mentions should not break the email parsing
* the email should not show up under /opt/zammad/tmp/unprocessable_mail, if it contains a mention with '@...'
### Actual behavior:
* parsing the mail generates an error: "ERROR: Can't process email, you will find it for bug reporting under /opt/zammad/tmp/unprocessable_mail/edd73f695ee7517e0ea3bd0143832594.eml, please create an issue at https://github.com/zammad/zammad/issues"
"ERROR: #<RuntimeError: User 23490 has no permission to mention other Users!>"
* running this command: zammad run rails r 'Channel::EmailParser.process_unprocessable_mails'
repeates the error again and again
* temporarily assigning the role 'agent' to the mentioned user makes the email run through
### Steps to reproduce the behavior:
* probably sending an email with a mention in the body, but I did not try a second time.
Yes I'm sure this is a bug and no feature request or a general question.
Complete output attached.
[zammad_mention_error.txt](https://github.com/zammad/zammad/files/6241453/zammad_mention_error.txt)
| process | mention in email body breaks email parsing hi there thanks for filing an issue please ensure the following things before creating an issue thank you 🤓 since november we handle all requests except real bugs at our community board full explanation please post feature requests development questions technical questions on the board if you think you hit a bug please continue search existing issues and the changelog md for your issue there might be a solution already make sure to use the latest version of zammad if possible add the log production log file from your system attention make sure no confidential data is in it please write the issue in english don t remove the template otherwise we will close the issue without further comments ask questions about zammad configuration and usage at our mailinglist see note we always do our best unfortunately sometimes there are too many requests and we can t handle everything at once if you want to prioritize escalate your issue you can do so by means of a support contract see the upper textblock will be removed automatically when you submit your issue infos used zammad version installation method source package repo operating system centos database version postgresql elasticsearch version browser version firefox bit expected behavior missing rights for mentions should not break the email parsing the email should not show up under opt zammad tmp unprocessable mail if it contains a mention with actual behavior parsing the mail generates an error error can t process email you will find it for bug reporting under opt zammad tmp unprocessable mail eml please create an issue at error running this command zammad run rails r channel emailparser process unprocessable mails repeates the error again and again temporarily assigning the role agent to the mentioned user makes the email run through steps to reproduce the behavior probably sending an email with a mention in the body but i did not try a second time yes i m sure this is a bug and no feature request or a general question complete output attached | 1 |
94,211 | 27,146,898,519 | IssuesEvent | 2023-02-16 20:44:51 | microsoft/vscode-cpptools | https://api.github.com/repos/microsoft/vscode-cpptools | opened | "Select a debug configuration" drop down list doesn't update after a new compilerPath is used | bug Language Service tasks/build/debug | 1. Use the "Debug C/C++" button in the top right of a file to see the "Select a debug configuration" drop down.
2. Change the compilerPath in the c_cpp_properties.json.
3. Repeat step 1.
Bug: The drop down list isn't updated until a Reload Window is done.
| 1.0 | "Select a debug configuration" drop down list doesn't update after a new compilerPath is used - 1. Use the "Debug C/C++" button in the top right of a file to see the "Select a debug configuration" drop down.
2. Change the compilerPath in the c_cpp_properties.json.
3. Repeat step 1.
Bug: The drop down list isn't updated until a Reload Window is done.
| non_process | select a debug configuration drop down list doesn t update after a new compilerpath is used use the debug c c button in the top right of a file to see the select a debug configuration drop down change the compilerpath in the c cpp properties json repeat step bug the drop down list isn t updated until a reload window is done | 0 |
11,246 | 14,015,436,483 | IssuesEvent | 2020-10-29 13:19:48 | AlexsLemonade/refinebio-examples | https://api.github.com/repos/AlexsLemonade/refinebio-examples | closed | Make diagrams that explain the two-branch set up for PR processes | images process | ### Background
#297 has made our PR process better, but also more complicated. #313 is adding a lot of information about our two-branch PR process in our CONTRIBUTING.md and it can be a lot to absorb and visualize in your head.
@jaclyn-taroni had the idea of making illustrations that describe this process so we can save our brain energy for elsewhere but so we can still leave the CONTRIBUTING.md doc with the idea of how PRs on this repository should work.
### Problem
There's a lot of different branch names, github actions, and steps for our PR process now that we are implementing #297
We need a diagram to explain this so contributors don't have to spend a lot of time learning how this works.
#### What items should be incorporated into the diagram?
The diagram should explain/include
- The branches: staging, gh-pages-stages, master, gh-pages and what are they, what are their purposes, what do they matter to me?
- What's do the github actions robots do in between each step? When are things being triggered?
- What's happening with the Docker image at each step?
- What do the two scenarios describe for staging changes - > master look like (specifically about the cherry commits).
- How do master and staging relate throughout?
### What are the recommended next steps?
- Let's take a look at other places on the web where they have these diagrams and they do it well for inspiration:
- https://www.atlassian.com/git/tutorials/comparing-workflows
- https://nvie.com/posts/a-successful-git-branching-model/
- Post a rough sketch of what this should look like here.
- Maybe make a prettier one using a graphic making app of some sort. Also post here.
- Finally add the diagram to CONTIRBUTING.md
| 1.0 | Make diagrams that explain the two-branch set up for PR processes - ### Background
#297 has made our PR process better, but also more complicated. #313 is adding a lot of information about our two-branch PR process in our CONTRIBUTING.md and it can be a lot to absorb and visualize in your head.
@jaclyn-taroni had the idea of making illustrations that describe this process so we can save our brain energy for elsewhere but so we can still leave the CONTRIBUTING.md doc with the idea of how PRs on this repository should work.
### Problem
There's a lot of different branch names, github actions, and steps for our PR process now that we are implementing #297
We need a diagram to explain this so contributors don't have to spend a lot of time learning how this works.
#### What items should be incorporated into the diagram?
The diagram should explain/include
- The branches: staging, gh-pages-stages, master, gh-pages and what are they, what are their purposes, what do they matter to me?
- What's do the github actions robots do in between each step? When are things being triggered?
- What's happening with the Docker image at each step?
- What do the two scenarios describe for staging changes - > master look like (specifically about the cherry commits).
- How do master and staging relate throughout?
### What are the recommended next steps?
- Let's take a look at other places on the web where they have these diagrams and they do it well for inspiration:
- https://www.atlassian.com/git/tutorials/comparing-workflows
- https://nvie.com/posts/a-successful-git-branching-model/
- Post a rough sketch of what this should look like here.
- Maybe make a prettier one using a graphic making app of some sort. Also post here.
- Finally add the diagram to CONTIRBUTING.md
| process | make diagrams that explain the two branch set up for pr processes background has made our pr process better but also more complicated is adding a lot of information about our two branch pr process in our contributing md and it can be a lot to absorb and visualize in your head jaclyn taroni had the idea of making illustrations that describe this process so we can save our brain energy for elsewhere but so we can still leave the contributing md doc with the idea of how prs on this repository should work problem there s a lot of different branch names github actions and steps for our pr process now that we are implementing we need a diagram to explain this so contributors don t have to spend a lot of time learning how this works what items should be incorporated into the diagram the diagram should explain include the branches staging gh pages stages master gh pages and what are they what are their purposes what do they matter to me what s do the github actions robots do in between each step when are things being triggered what s happening with the docker image at each step what do the two scenarios describe for staging changes master look like specifically about the cherry commits how do master and staging relate throughout what are the recommended next steps let s take a look at other places on the web where they have these diagrams and they do it well for inspiration post a rough sketch of what this should look like here maybe make a prettier one using a graphic making app of some sort also post here finally add the diagram to contirbuting md | 1 |
12,443 | 14,933,777,088 | IssuesEvent | 2021-01-25 09:40:03 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | reopened | TestOnExecuteCustomCommand fails with Assert.Equal | area-System.ServiceProcess untriaged | Platform: Windows_NT x64/x86 Release
Pipeline: runtime-libraries outerloop
Example builds:
- https://dev.azure.com/dnceng/public/_build/results?buildId=482386
- https://dev.azure.com/dnceng/public/_build/results?buildId=481223
- https://dev.azure.com/dnceng/public/_build/results?buildId=483118
Proximate diagnostic info:
<pre>
Starting: System.ServiceProcess.ServiceController.Tests (parallel test collections = on, max threads = 2)
System.ServiceProcess.Tests.ServiceBaseTests.TestOnExecuteCustomCommand [FAIL]
Assert.Equal() Failure
Expected: 128
Actual: 129
Stack Trace:
/_/src/libraries/System.ServiceProcess.ServiceController/tests/ServiceBaseTests.cs(156,0): at System.ServiceProcess.Tests.ServiceBaseTests.TestOnExecuteCustomCommand()
Finished: System.ServiceProcess.ServiceController.Tests
=== TEST EXECUTION SUMMARY ===
System.ServiceProcess.ServiceController.Tests Total: 22, Errors: 0, Failed: 1, Skipped: 0, Time: 23.417s
</pre>
| 1.0 | TestOnExecuteCustomCommand fails with Assert.Equal - Platform: Windows_NT x64/x86 Release
Pipeline: runtime-libraries outerloop
Example builds:
- https://dev.azure.com/dnceng/public/_build/results?buildId=482386
- https://dev.azure.com/dnceng/public/_build/results?buildId=481223
- https://dev.azure.com/dnceng/public/_build/results?buildId=483118
Proximate diagnostic info:
<pre>
Starting: System.ServiceProcess.ServiceController.Tests (parallel test collections = on, max threads = 2)
System.ServiceProcess.Tests.ServiceBaseTests.TestOnExecuteCustomCommand [FAIL]
Assert.Equal() Failure
Expected: 128
Actual: 129
Stack Trace:
/_/src/libraries/System.ServiceProcess.ServiceController/tests/ServiceBaseTests.cs(156,0): at System.ServiceProcess.Tests.ServiceBaseTests.TestOnExecuteCustomCommand()
Finished: System.ServiceProcess.ServiceController.Tests
=== TEST EXECUTION SUMMARY ===
System.ServiceProcess.ServiceController.Tests Total: 22, Errors: 0, Failed: 1, Skipped: 0, Time: 23.417s
</pre>
| process | testonexecutecustomcommand fails with assert equal platform windows nt release pipeline runtime libraries outerloop example builds proximate diagnostic info starting system serviceprocess servicecontroller tests parallel test collections on max threads system serviceprocess tests servicebasetests testonexecutecustomcommand assert equal failure expected actual stack trace src libraries system serviceprocess servicecontroller tests servicebasetests cs at system serviceprocess tests servicebasetests testonexecutecustomcommand finished system serviceprocess servicecontroller tests test execution summary system serviceprocess servicecontroller tests total errors failed skipped time | 1 |
390,718 | 11,561,971,819 | IssuesEvent | 2020-02-20 00:55:36 | openmsupply/mobile | https://api.github.com/repos/openmsupply/mobile | closed | Cash register throws error if no payment types defined | Bug: development Effort: small Module: dispensary Priority: normal | ## Describe the bug
If no payment types are defined, the cash register throws an error. Arguably is a config issue, but could theoretically occur due to an incomplete sync etc. In any case, best to play it safe and add some defensive code.
### To reproduce
Steps to reproduce the behavior:
1. Setup a datafile with no payment types defined.
2. Enable mobile cash register (`usesCashRegisterModule`).
3. Open cash register on mobile.
4. See error
### Expected behaviour
My current thinking is that the cash register is pretty tightly bound to payment types, so probably shouldn't appear as a module unless there is at least one payment type defined?
### Proposed Solution
Small change to `modulesReducer`:
```
const usingPaymentTypes = UIDatabase.objects('PaymentType').length > 0;
const usingCashRegister = checkModule(SETTINGS_KEYS.CASH_REGISTER_MODULE) && usingPaymentTypes;
```
### Version and device info
- App version: v4.0.0
- Tablet model: Emulator
- OS version: API 29.
### Additional context
N/A.
| 1.0 | Cash register throws error if no payment types defined - ## Describe the bug
If no payment types are defined, the cash register throws an error. Arguably is a config issue, but could theoretically occur due to an incomplete sync etc. In any case, best to play it safe and add some defensive code.
### To reproduce
Steps to reproduce the behavior:
1. Setup a datafile with no payment types defined.
2. Enable mobile cash register (`usesCashRegisterModule`).
3. Open cash register on mobile.
4. See error
### Expected behaviour
My current thinking is that the cash register is pretty tightly bound to payment types, so probably shouldn't appear as a module unless there is at least one payment type defined?
### Proposed Solution
Small change to `modulesReducer`:
```
const usingPaymentTypes = UIDatabase.objects('PaymentType').length > 0;
const usingCashRegister = checkModule(SETTINGS_KEYS.CASH_REGISTER_MODULE) && usingPaymentTypes;
```
### Version and device info
- App version: v4.0.0
- Tablet model: Emulator
- OS version: API 29.
### Additional context
N/A.
| non_process | cash register throws error if no payment types defined describe the bug if no payment types are defined the cash register throws an error arguably is a config issue but could theoretically occur due to an incomplete sync etc in any case best to play it safe and add some defensive code to reproduce steps to reproduce the behavior setup a datafile with no payment types defined enable mobile cash register usescashregistermodule open cash register on mobile see error expected behaviour my current thinking is that the cash register is pretty tightly bound to payment types so probably shouldn t appear as a module unless there is at least one payment type defined proposed solution small change to modulesreducer const usingpaymenttypes uidatabase objects paymenttype length const usingcashregister checkmodule settings keys cash register module usingpaymenttypes version and device info app version tablet model emulator os version api additional context n a | 0 |
71,790 | 9,538,650,935 | IssuesEvent | 2019-04-30 15:09:22 | FreeUKGen/FreeBMD2 | https://api.github.com/repos/FreeUKGen/FreeBMD2 | closed | Bluelight issue (Review wishlist/survey feedback) | documentation in progress user experience | To review what has been suggested. Initially UX requirements to be extracted and looked at - to then add to requirements/roadmap. | 1.0 | Bluelight issue (Review wishlist/survey feedback) - To review what has been suggested. Initially UX requirements to be extracted and looked at - to then add to requirements/roadmap. | non_process | bluelight issue review wishlist survey feedback to review what has been suggested initially ux requirements to be extracted and looked at to then add to requirements roadmap | 0 |
148,806 | 23,385,762,404 | IssuesEvent | 2022-08-11 13:38:26 | GCTC-NTGC/TalentCloud | https://api.github.com/repos/GCTC-NTGC/TalentCloud | closed | Spike - Targeted Emails to Applicants | Design Spike | # Description
Enter the spike description here. What will we be researching?
We'd like to know the complexities behind sending targeted emails to applicants that show them jobs that match skills in their profile. We'd need an opt-in/opt-out UI on both the registration and the profile. | 1.0 | Spike - Targeted Emails to Applicants - # Description
Enter the spike description here. What will we be researching?
We'd like to know the complexities behind sending targeted emails to applicants that show them jobs that match skills in their profile. We'd need an opt-in/opt-out UI on both the registration and the profile. | non_process | spike targeted emails to applicants description enter the spike description here what will we be researching we d like to know the complexities behind sending targeted emails to applicants that show them jobs that match skills in their profile we d need an opt in opt out ui on both the registration and the profile | 0 |
135,119 | 12,675,297,109 | IssuesEvent | 2020-06-19 01:13:01 | bradtaniguchi/discord-bot-test | https://api.github.com/repos/bradtaniguchi/discord-bot-test | closed | Update docs to go over how to add the bot to only select channels | documentation enhancement | **Is your feature request related to a problem? Please describe.**
During development we will probably only want the bot to be available in certain channels rather than the entire server.
This can be done using discord itself, but this process should be documented.
**Describe the solution you'd like**
Update the README with information on limiting the discord bot to select channels.
| 1.0 | Update docs to go over how to add the bot to only select channels - **Is your feature request related to a problem? Please describe.**
During development we will probably only want the bot to be available in certain channels rather than the entire server.
This can be done using discord itself, but this process should be documented.
**Describe the solution you'd like**
Update the README with information on limiting the discord bot to select channels.
| non_process | update docs to go over how to add the bot to only select channels is your feature request related to a problem please describe during development we will probably only want the bot to be available in certain channels rather than the entire server this can be done using discord itself but this process should be documented describe the solution you d like update the readme with information on limiting the discord bot to select channels | 0 |
8,908 | 12,014,309,665 | IssuesEvent | 2020-04-10 11:05:16 | ClickHouse/ClickHouse | https://api.github.com/repos/ClickHouse/ClickHouse | closed | DB::Exception: Pipeline stuck. Current state: digraph | comp-processors question | Hi all,when i do my query，sometimes i will get this exception.how can i fix it or avoid it.is it related to any settings？
and this is my sql
[abc.txt](https://github.com/ClickHouse/ClickHouse/files/4448936/abc.txt)
| 1.0 | DB::Exception: Pipeline stuck. Current state: digraph - Hi all,when i do my query，sometimes i will get this exception.how can i fix it or avoid it.is it related to any settings？
and this is my sql
[abc.txt](https://github.com/ClickHouse/ClickHouse/files/4448936/abc.txt)
| process | db exception pipeline stuck current state digraph hi all when i do my query，sometimes i will get this exception how can i fix it or avoid it is it related to any settings？ and this is my sql | 1 |
11,002 | 13,791,087,149 | IssuesEvent | 2020-10-09 11:32:58 | kubeflow/pipelines | https://api.github.com/repos/kubeflow/pipelines | opened | Make sample tests more flexible regarding sample pipeline locations and names | area/samples area/samples/notebooks area/testing help wanted kind/feature kind/process priority/p1 | Currently all tested samples must have flat structure and the code files must have the same names as the enclosing directories. It would be great to lift these constraints and make it possible to specify the full paths to sample programs/notebooks, so that the samples can be organized. | 1.0 | Make sample tests more flexible regarding sample pipeline locations and names - Currently all tested samples must have flat structure and the code files must have the same names as the enclosing directories. It would be great to lift these constraints and make it possible to specify the full paths to sample programs/notebooks, so that the samples can be organized. | process | make sample tests more flexible regarding sample pipeline locations and names currently all tested samples must have flat structure and the code files must have the same names as the enclosing directories it would be great to lift these constraints and make it possible to specify the full paths to sample programs notebooks so that the samples can be organized | 1 |
5,421 | 8,257,371,269 | IssuesEvent | 2018-09-13 04:36:53 | googleapis/nodejs-tasks | https://api.github.com/repos/googleapis/nodejs-tasks | closed | Master branch not synced with `npm published module` | type: process | Master branch not synced with `npm published module`
# Example
Master branch client has `projectPath` method and `npm published module` do not.
| 1.0 | Master branch not synced with `npm published module` - Master branch not synced with `npm published module`
# Example
Master branch client has `projectPath` method and `npm published module` do not.
| process | master branch not synced with npm published module master branch not synced with npm published module example master branch client has projectpath method and npm published module do not | 1 |
6,038 | 8,850,809,996 | IssuesEvent | 2019-01-08 14:16:23 | redhat-developer/vscode-java | https://api.github.com/repos/redhat-developer/vscode-java | closed | Issues with Micronaut and Visual Studio Code with Java | Gradle Maven annotation-processing bug | I had a chat with @fbricon at CodeOne and we got the basics of Micronaut working with Code however there are a couple of areas that I can't seem to get to work.
1. Gradle support doesn't seem to work at all, the annotation processors are simply not applied.
2. Maven support partially works. Annotation processors are applied to sources in `src/main/java`, but tests don't work because the processors are not applied to `src/test/java`.
##### Environment
- Operating System: OS X
- JDK version: Java 8 or 11
- Visual Studio Code version: 1.28.2 (1.28.2)
- Java extension version: Extension Package 0.4.0
##### Steps To Reproduce for Gradle
1. Clone the repo https://github.com/micronaut-projects/micronaut-examples
2. `cd hello-world-java`
3. Run `gradle eclipse`
4. Run `code .`
##### Current Result
The application can be run but if you hit `http://localhost:8080/hello/john` you receive a 404 and although the tests pass they pass because the test is skipped because it isn't configure as a bean.
##### Expected Result
The test should not be skipped and `http://localhost:8080/hello/john` should not 404
##### Steps To Reproduce for Maven
1. Clone the repo https://github.com/micronaut-projects/micronaut-examples
2. `cd hello-world-java`
3. Remove the `build.gradle` (so that VSC uses the `pom.xml`)
4. Run `code .`
##### Current Result
The result is better than with Gradle, the application can be run and if you hit `http://localhost:8080/hello/john` you get the right result. This means the annotation processors are applied to `src/main/java`.
However if you run a test the test is skipped because the annotation processor are not applied. If you however run `./mvnw test` the test is not skipped because the processors are applied
##### Expected Result
The test should not be skipped because annotation processors should be applied to test sources. | 1.0 | Issues with Micronaut and Visual Studio Code with Java - I had a chat with @fbricon at CodeOne and we got the basics of Micronaut working with Code however there are a couple of areas that I can't seem to get to work.
1. Gradle support doesn't seem to work at all, the annotation processors are simply not applied.
2. Maven support partially works. Annotation processors are applied to sources in `src/main/java`, but tests don't work because the processors are not applied to `src/test/java`.
##### Environment
- Operating System: OS X
- JDK version: Java 8 or 11
- Visual Studio Code version: 1.28.2 (1.28.2)
- Java extension version: Extension Package 0.4.0
##### Steps To Reproduce for Gradle
1. Clone the repo https://github.com/micronaut-projects/micronaut-examples
2. `cd hello-world-java`
3. Run `gradle eclipse`
4. Run `code .`
##### Current Result
The application can be run but if you hit `http://localhost:8080/hello/john` you receive a 404 and although the tests pass they pass because the test is skipped because it isn't configure as a bean.
##### Expected Result
The test should not be skipped and `http://localhost:8080/hello/john` should not 404
##### Steps To Reproduce for Maven
1. Clone the repo https://github.com/micronaut-projects/micronaut-examples
2. `cd hello-world-java`
3. Remove the `build.gradle` (so that VSC uses the `pom.xml`)
4. Run `code .`
##### Current Result
The result is better than with Gradle, the application can be run and if you hit `http://localhost:8080/hello/john` you get the right result. This means the annotation processors are applied to `src/main/java`.
However if you run a test the test is skipped because the annotation processor are not applied. If you however run `./mvnw test` the test is not skipped because the processors are applied
##### Expected Result
The test should not be skipped because annotation processors should be applied to test sources. | process | issues with micronaut and visual studio code with java i had a chat with fbricon at codeone and we got the basics of micronaut working with code however there are a couple of areas that i can t seem to get to work gradle support doesn t seem to work at all the annotation processors are simply not applied maven support partially works annotation processors are applied to sources in src main java but tests don t work because the processors are not applied to src test java environment operating system os x jdk version java or visual studio code version java extension version extension package steps to reproduce for gradle clone the repo cd hello world java run gradle eclipse run code current result the application can be run but if you hit you receive a and although the tests pass they pass because the test is skipped because it isn t configure as a bean expected result the test should not be skipped and should not steps to reproduce for maven clone the repo cd hello world java remove the build gradle so that vsc uses the pom xml run code current result the result is better than with gradle the application can be run and if you hit you get the right result this means the annotation processors are applied to src main java however if you run a test the test is skipped because the annotation processor are not applied if you however run mvnw test the test is not skipped because the processors are applied expected result the test should not be skipped because annotation processors should be applied to test sources | 1 |
19,304 | 25,466,626,828 | IssuesEvent | 2022-11-25 05:30:48 | GoogleCloudPlatform/fda-mystudies | https://api.github.com/repos/GoogleCloudPlatform/fda-mystudies | closed | [IDP] [PM] Not able to add non-organizational admins in the participant manager | Bug Blocker P0 Participant manager Process: Fixed Process: Tested QA Process: Tested dev | Not able to add non-organizational admins in the participant manager | 3.0 | [IDP] [PM] Not able to add non-organizational admins in the participant manager - Not able to add non-organizational admins in the participant manager | process | not able to add non organizational admins in the participant manager not able to add non organizational admins in the participant manager | 1 |
20,671 | 27,335,051,667 | IssuesEvent | 2023-02-26 04:35:39 | bazelbuild/bazel | https://api.github.com/repos/bazelbuild/bazel | closed | Release X.Y.Z - $MONTH $YEAR | P1 type: process release team-OSS | # Status of Bazel X.Y.Z
<!-- The first item is only needed for major releases (X.0.0) -->
- Target baseline: [date]
- Expected release date: [date]
- [List of release blockers](link-to-milestone)
To report a release-blocking bug, please add a comment with the text `@bazel-io flag` to the issue. A release manager will triage it and add it to the milestone.
To cherry-pick a mainline commit into X.Y.Z, simply send a PR against the `release-X.Y.Z` branch.
**Task list:**
<!-- The first three items are only needed for major releases (X.0.0) -->
- [ ] Pick release baseline: [link to base commit]
- [ ] Create release candidate: X.Y.Zrc1
- [ ] Check downstream projects
- [ ] Create [draft release announcement](https://docs.google.com/document/d/1pu2ARPweOCTxPsRR8snoDtkC9R51XWRyBXeiC6Ql5so/edit) <!-- Note that there should be a new Bazel Release Announcement document for every major release. For minor and patch releases, use the latest open doc. -->
- [ ] Send the release announcement PR for review: [link to bazel-blog PR] <!-- Only for major releases. -->
- [ ] Push the release and notify package maintainers: [link to comment notifying package maintainers]
- [ ] Update the documentation
- [ ] Push the blog post: [link to blog post] <!-- Only for major releases. -->
- [ ] Update the [release page](https://github.com/bazelbuild/bazel/releases/)
| 1.0 | Release X.Y.Z - $MONTH $YEAR - # Status of Bazel X.Y.Z
<!-- The first item is only needed for major releases (X.0.0) -->
- Target baseline: [date]
- Expected release date: [date]
- [List of release blockers](link-to-milestone)
To report a release-blocking bug, please add a comment with the text `@bazel-io flag` to the issue. A release manager will triage it and add it to the milestone.
To cherry-pick a mainline commit into X.Y.Z, simply send a PR against the `release-X.Y.Z` branch.
**Task list:**
<!-- The first three items are only needed for major releases (X.0.0) -->
- [ ] Pick release baseline: [link to base commit]
- [ ] Create release candidate: X.Y.Zrc1
- [ ] Check downstream projects
- [ ] Create [draft release announcement](https://docs.google.com/document/d/1pu2ARPweOCTxPsRR8snoDtkC9R51XWRyBXeiC6Ql5so/edit) <!-- Note that there should be a new Bazel Release Announcement document for every major release. For minor and patch releases, use the latest open doc. -->
- [ ] Send the release announcement PR for review: [link to bazel-blog PR] <!-- Only for major releases. -->
- [ ] Push the release and notify package maintainers: [link to comment notifying package maintainers]
- [ ] Update the documentation
- [ ] Push the blog post: [link to blog post] <!-- Only for major releases. -->
- [ ] Update the [release page](https://github.com/bazelbuild/bazel/releases/)
| process | release x y z month year status of bazel x y z target baseline expected release date link to milestone to report a release blocking bug please add a comment with the text bazel io flag to the issue a release manager will triage it and add it to the milestone to cherry pick a mainline commit into x y z simply send a pr against the release x y z branch task list pick release baseline create release candidate x y check downstream projects create send the release announcement pr for review push the release and notify package maintainers update the documentation push the blog post update the | 1 |
16,655 | 21,726,582,752 | IssuesEvent | 2022-05-11 08:14:14 | 2i2c-org/team-compass | https://api.github.com/repos/2i2c-org/team-compass | closed | Team process for support using FreshDesk | type: enhancement :label: team-process :label: administration | # Summary
In #151 we converged on using FreshDesk to handle our support requests for 2i2c Hubs. This issue will keep track of our progress in setting up FreshDesk and building a team process around support.
# User Stories
- As a Hub Representative, I want to know where to ask questions or provide requests about my hub, and where to look for updates as things are resolved.
- As the Support Steward, I want to minimize the places I have to look for support conversations and interact with Hub Representatives.
- As a Hub Engineer, I want to know when deliverables should be prioritized because they are related to support questions.
# Important links
- [Support steward process draft](https://docs.google.com/document/d/17Kj_FbtVMl32TEcfvCp18fF1SEiBjVOhCswdidUytgM/edit#)
# Questions to answer
- When we create a ticket after a support request, do we still expect Community Representatives to communicate via FreshDesk, or is it OK for them to start responding in the GitHub issue?
# Actions
- [x] Set up a FreshDesk account for 2i2c
- [x] #169
- [x] Write up a process that suggests the Support Steward should use `#hub-support` to signal boost items for other team members
- [x] Write up a short guide for the 2i2c team
- [ ] Designate our first Support Steward to try it out
- [x] Designate a Community Representative to prototype FreshDesk questions
- [ ] ...add extra steps as necessary to refine this process
- [ ] Write up a support workflow in the Team Compass
| 1.0 | Team process for support using FreshDesk - # Summary
In #151 we converged on using FreshDesk to handle our support requests for 2i2c Hubs. This issue will keep track of our progress in setting up FreshDesk and building a team process around support.
# User Stories
- As a Hub Representative, I want to know where to ask questions or provide requests about my hub, and where to look for updates as things are resolved.
- As the Support Steward, I want to minimize the places I have to look for support conversations and interact with Hub Representatives.
- As a Hub Engineer, I want to know when deliverables should be prioritized because they are related to support questions.
# Important links
- [Support steward process draft](https://docs.google.com/document/d/17Kj_FbtVMl32TEcfvCp18fF1SEiBjVOhCswdidUytgM/edit#)
# Questions to answer
- When we create a ticket after a support request, do we still expect Community Representatives to communicate via FreshDesk, or is it OK for them to start responding in the GitHub issue?
# Actions
- [x] Set up a FreshDesk account for 2i2c
- [x] #169
- [x] Write up a process that suggests the Support Steward should use `#hub-support` to signal boost items for other team members
- [x] Write up a short guide for the 2i2c team
- [ ] Designate our first Support Steward to try it out
- [x] Designate a Community Representative to prototype FreshDesk questions
- [ ] ...add extra steps as necessary to refine this process
- [ ] Write up a support workflow in the Team Compass
| process | team process for support using freshdesk summary in we converged on using freshdesk to handle our support requests for hubs this issue will keep track of our progress in setting up freshdesk and building a team process around support user stories as a hub representative i want to know where to ask questions or provide requests about my hub and where to look for updates as things are resolved as the support steward i want to minimize the places i have to look for support conversations and interact with hub representatives as a hub engineer i want to know when deliverables should be prioritized because they are related to support questions important links questions to answer when we create a ticket after a support request do we still expect community representatives to communicate via freshdesk or is it ok for them to start responding in the github issue actions set up a freshdesk account for write up a process that suggests the support steward should use hub support to signal boost items for other team members write up a short guide for the team designate our first support steward to try it out designate a community representative to prototype freshdesk questions add extra steps as necessary to refine this process write up a support workflow in the team compass | 1 |
48,049 | 13,067,414,753 | IssuesEvent | 2020-07-31 00:22:44 | icecube-trac/tix2 | https://api.github.com/repos/icecube-trac/tix2 | closed | [release] IceRec L2 Season 2015 (Trac #1707) | Migrated from Trac combo reconstruction defect | A new release is required with the following fixes:
* CascadeVariables bug, see #1666 (last comment)
* IceAct:
* The new I3Db release (V16-05-00) is required to get the IceAct geometry
* The new BadDomList project is required since the old one does not handle string 0 / IceAct
* Updates in dataclasses required for I3Db, IceAct, and the new BadDomList:
* http://code.icecube.wisc.edu/projects/icecube/changeset/145779/IceCube/projects/dataclasses/trunk
* http://code.icecube.wisc.edu/projects/icecube/changeset/145752/IceCube/projects/dataclasses/trunk
* http://code.icecube.wisc.edu/projects/icecube/changeset/145417/IceCube/projects/dataclasses/trunk
* Pybindings in icetray: http://code.icecube.wisc.edu/projects/icecube/changeset/2562/IceTray/projects/icetray/trunk
Migrated from https://code.icecube.wisc.edu/ticket/1707
```json
{
"status": "closed",
"changetime": "2019-02-13T14:12:58",
"description": "A new release is required with the following fixes:\n\n* CascadeVariables bug, see #1674 (last comment)\n* IceAct:\n * The new I3Db release (V16-05-00) is required to get the IceAct geometry\n * The new BadDomList project is required since the old one does not handle string 0 / IceAct\n * Updates in dataclasses required for I3Db, IceAct, and the new BadDomList:\n * http://code.icecube.wisc.edu/projects/icecube/changeset/145779/IceCube/projects/dataclasses/trunk\n * http://code.icecube.wisc.edu/projects/icecube/changeset/145752/IceCube/projects/dataclasses/trunk\n * http://code.icecube.wisc.edu/projects/icecube/changeset/145417/IceCube/projects/dataclasses/trunk\n * Pybindings in icetray: http://code.icecube.wisc.edu/projects/icecube/changeset/2562/IceTray/projects/icetray/trunk",
"reporter": "joertlin",
"cc": "",
"resolution": "fixed",
"_ts": "1550067178841456",
"component": "combo reconstruction",
"summary": "[release] IceRec L2 Season 2015",
"priority": "blocker",
"keywords": "",
"time": "2016-05-17T15:12:58",
"milestone": "",
"owner": "olivas",
"type": "defect"
}
```
| 1.0 | [release] IceRec L2 Season 2015 (Trac #1707) - A new release is required with the following fixes:
* CascadeVariables bug, see #1666 (last comment)
* IceAct:
* The new I3Db release (V16-05-00) is required to get the IceAct geometry
* The new BadDomList project is required since the old one does not handle string 0 / IceAct
* Updates in dataclasses required for I3Db, IceAct, and the new BadDomList:
* http://code.icecube.wisc.edu/projects/icecube/changeset/145779/IceCube/projects/dataclasses/trunk
* http://code.icecube.wisc.edu/projects/icecube/changeset/145752/IceCube/projects/dataclasses/trunk
* http://code.icecube.wisc.edu/projects/icecube/changeset/145417/IceCube/projects/dataclasses/trunk
* Pybindings in icetray: http://code.icecube.wisc.edu/projects/icecube/changeset/2562/IceTray/projects/icetray/trunk
Migrated from https://code.icecube.wisc.edu/ticket/1707
```json
{
"status": "closed",
"changetime": "2019-02-13T14:12:58",
"description": "A new release is required with the following fixes:\n\n* CascadeVariables bug, see #1674 (last comment)\n* IceAct:\n * The new I3Db release (V16-05-00) is required to get the IceAct geometry\n * The new BadDomList project is required since the old one does not handle string 0 / IceAct\n * Updates in dataclasses required for I3Db, IceAct, and the new BadDomList:\n * http://code.icecube.wisc.edu/projects/icecube/changeset/145779/IceCube/projects/dataclasses/trunk\n * http://code.icecube.wisc.edu/projects/icecube/changeset/145752/IceCube/projects/dataclasses/trunk\n * http://code.icecube.wisc.edu/projects/icecube/changeset/145417/IceCube/projects/dataclasses/trunk\n * Pybindings in icetray: http://code.icecube.wisc.edu/projects/icecube/changeset/2562/IceTray/projects/icetray/trunk",
"reporter": "joertlin",
"cc": "",
"resolution": "fixed",
"_ts": "1550067178841456",
"component": "combo reconstruction",
"summary": "[release] IceRec L2 Season 2015",
"priority": "blocker",
"keywords": "",
"time": "2016-05-17T15:12:58",
"milestone": "",
"owner": "olivas",
"type": "defect"
}
```
| non_process | icerec season trac a new release is required with the following fixes cascadevariables bug see last comment iceact the new release is required to get the iceact geometry the new baddomlist project is required since the old one does not handle string iceact updates in dataclasses required for iceact and the new baddomlist pybindings in icetray migrated from json status closed changetime description a new release is required with the following fixes n n cascadevariables bug see last comment n iceact n the new release is required to get the iceact geometry n the new baddomlist project is required since the old one does not handle string iceact n updates in dataclasses required for iceact and the new baddomlist n pybindings in icetray reporter joertlin cc resolution fixed ts component combo reconstruction summary icerec season priority blocker keywords time milestone owner olivas type defect | 0 |
169,278 | 13,132,234,690 | IssuesEvent | 2020-08-06 18:31:03 | elyra-ai/elyra | https://api.github.com/repos/elyra-ai/elyra | opened | Add jest unit tests for frontend | area:front-end component:test | The frontend Elyra code currently only has cypress integration tests - we should also include unit tests using jest (which is what Jupyterlab uses). | 1.0 | Add jest unit tests for frontend - The frontend Elyra code currently only has cypress integration tests - we should also include unit tests using jest (which is what Jupyterlab uses). | non_process | add jest unit tests for frontend the frontend elyra code currently only has cypress integration tests we should also include unit tests using jest which is what jupyterlab uses | 0 |
6,998 | 10,144,170,529 | IssuesEvent | 2019-08-04 18:28:59 | googleapis/google-cloud-node | https://api.github.com/repos/googleapis/google-cloud-node | closed | Add Node.js 12 to the CI | type: process | Looks like Node.js 12 was just released! Let's get it added to the kokoro configs. | 1.0 | Add Node.js 12 to the CI - Looks like Node.js 12 was just released! Let's get it added to the kokoro configs. | process | add node js to the ci looks like node js was just released let s get it added to the kokoro configs | 1 |
145,902 | 13,164,582,790 | IssuesEvent | 2020-08-11 04:07:23 | Gwynbl31dd/nso_controller | https://api.github.com/repos/Gwynbl31dd/nso_controller | closed | Load String doc example incorrect | documentation | SHould change the example as it used load() instead of loadString() | 1.0 | Load String doc example incorrect - SHould change the example as it used load() instead of loadString() | non_process | load string doc example incorrect should change the example as it used load instead of loadstring | 0 |
410,724 | 27,799,169,264 | IssuesEvent | 2023-03-17 14:40:14 | gematik/api-erp | https://api.github.com/repos/gematik/api-erp | closed | ChargeItem.subject.system GKV? | bug documentation | Hallo,
in dem Beispiel unter https://github.com/gematik/api-erp/blob/master/docs/erp_chargeItem.adoc#anwendungsfall-pkv-abrechnungsinformationen-durch-den-abgebenden-leistungserbringer-bereitstellen
wird die Versichertennummer als System http://fhir.de/sid/gkv/kvid-10 angegeben.
Sollte das nicht eher http://fhir.de/sid/pkv/kvid-10 sein? | 1.0 | ChargeItem.subject.system GKV? - Hallo,
in dem Beispiel unter https://github.com/gematik/api-erp/blob/master/docs/erp_chargeItem.adoc#anwendungsfall-pkv-abrechnungsinformationen-durch-den-abgebenden-leistungserbringer-bereitstellen
wird die Versichertennummer als System http://fhir.de/sid/gkv/kvid-10 angegeben.
Sollte das nicht eher http://fhir.de/sid/pkv/kvid-10 sein? | non_process | chargeitem subject system gkv hallo in dem beispiel unter wird die versichertennummer als system angegeben sollte das nicht eher sein | 0 |
15,475 | 19,685,292,729 | IssuesEvent | 2022-01-11 21:22:01 | darktable-org/darktable | https://api.github.com/repos/darktable-org/darktable | closed | NaNs in RCD opencl demosaicing most likely make the surface blur module crash | scope: image processing | I was suffering a lot of crashes when using the surface blur module lately. See https://github.com/darktable-org/darktable/issues/10082 for reference.
While it wasn't quite obvious where the issue came from it seems that NaNs cause the module to crash as per the last stacktrace and comment here: https://discuss.pixls.us/t/amd-opencl-problems-in-surface-blur-darktable-module/28507/12
I suspect the NaNs are coming from RCD (opencl version) as when using AMAZE, I don't see green blocks at the border regions and also can't reproduce the crashes I had in the surface blue module so far.
This is happening since a while now. I will try to bisect RCD changes to see if there was a specific commit introducing the bug as I was able to use surface blur without issues before in the 3.8 development cycle. I am happy for further input on how to help providing more information that could be helpful.
Since when: In the 3.8 development cycle
Graphics card: AMD Radeon RX 580 Series (POLARIS10, DRM 3.42.0, 5.15.12-arch1-1, LLVM 13.0.0) running the latest opencl-amd driver available on Arch (OpenCL 2.0 AMD-APP (3354.7)
Gnome 41.2 on Wayland
Intel i5-7600K CPU
Darktable compiled as Release build (also happens in the Arch 3.8.0 build) | 1.0 | NaNs in RCD opencl demosaicing most likely make the surface blur module crash - I was suffering a lot of crashes when using the surface blur module lately. See https://github.com/darktable-org/darktable/issues/10082 for reference.
While it wasn't quite obvious where the issue came from it seems that NaNs cause the module to crash as per the last stacktrace and comment here: https://discuss.pixls.us/t/amd-opencl-problems-in-surface-blur-darktable-module/28507/12
I suspect the NaNs are coming from RCD (opencl version) as when using AMAZE, I don't see green blocks at the border regions and also can't reproduce the crashes I had in the surface blue module so far.
This is happening since a while now. I will try to bisect RCD changes to see if there was a specific commit introducing the bug as I was able to use surface blur without issues before in the 3.8 development cycle. I am happy for further input on how to help providing more information that could be helpful.
Since when: In the 3.8 development cycle
Graphics card: AMD Radeon RX 580 Series (POLARIS10, DRM 3.42.0, 5.15.12-arch1-1, LLVM 13.0.0) running the latest opencl-amd driver available on Arch (OpenCL 2.0 AMD-APP (3354.7)
Gnome 41.2 on Wayland
Intel i5-7600K CPU
Darktable compiled as Release build (also happens in the Arch 3.8.0 build) | process | nans in rcd opencl demosaicing most likely make the surface blur module crash i was suffering a lot of crashes when using the surface blur module lately see for reference while it wasn t quite obvious where the issue came from it seems that nans cause the module to crash as per the last stacktrace and comment here i suspect the nans are coming from rcd opencl version as when using amaze i don t see green blocks at the border regions and also can t reproduce the crashes i had in the surface blue module so far this is happening since a while now i will try to bisect rcd changes to see if there was a specific commit introducing the bug as i was able to use surface blur without issues before in the development cycle i am happy for further input on how to help providing more information that could be helpful since when in the development cycle graphics card amd radeon rx series drm llvm running the latest opencl amd driver available on arch opencl amd app gnome on wayland intel cpu darktable compiled as release build also happens in the arch build | 1 |
232,790 | 7,675,434,442 | IssuesEvent | 2018-05-15 08:41:00 | DigitalCampus/django-oppia | https://api.github.com/repos/DigitalCampus/django-oppia | closed | Activity upload - show message if user is not found | enhancement lmh-activity-xfer medium priority | For example if an activity log file from different app/implementation has been uploaded | 1.0 | Activity upload - show message if user is not found - For example if an activity log file from different app/implementation has been uploaded | non_process | activity upload show message if user is not found for example if an activity log file from different app implementation has been uploaded | 0 |
88,812 | 17,669,285,975 | IssuesEvent | 2021-08-23 02:03:35 | PyTorchLightning/pytorch-lightning | https://api.github.com/repos/PyTorchLightning/pytorch-lightning | opened | [RFC] Deprecate `weights_summary` off the Trainer constructor | enhancement help wanted refactors / code health deprecation | ## Proposed refactoring or deprecation
- Introduce a new ModelSummary callback, which calls `summarize`: https://github.com/PyTorchLightning/pytorch-lightning/blob/8a931732ae5135e3e55d9c7b7031d81837e5798a/pytorch_lightning/utilities/model_summary.py#L437-L439
- Deprecate `weights_summary` off the Trainer constructor
<!-- A clear and concise description of the code improvement -->
### Motivation
We are auditing the Lightning components and APIs to assess opportunities for improvements:
- https://github.com/PyTorchLightning/pytorch-lightning/issues/7740
- https://docs.google.com/document/d/1xHU7-iQSpp9KJTjI3As2EM0mfNHHr37WZYpDpwLkivA/edit#
This is a followup to https://github.com/PyTorchLightning/pytorch-lightning/issues/8478 and https://github.com/PyTorchLightning/pytorch-lightning/discussions/9006
Why do we want to remove this from the core trainer logic?
- We need a way for users to customize more of the inputs to the model summary over time without affecting the trainer API. Today, changes to the model summary API also require changes in the core trainer (e.g. the addition of `max_depth` ). This gives model summarization more room to grow without cascading changes elsewhere.
- Users may want to configure this summarization for different points of execution. For instance, calling this at the start of `trainer.fit()`, `trainer.validate()`, `trainer.test()` or `trainer.predict()`. Right now, this is hardcoded to be run only during `fit()`.
- Users may want to customize where they save the summary. Right now, it's printed to stdout, but this could also be useful to save to a file or upload to another service for tracking the run.
- The current implementation runs on global rank 0 only in order to avoid printing out multiple summary tables. However, running this on rank 0 will break for model parallel use cases that require communication across ranks. This can lead to subtle failures if `example_input_array` is set as a property on the LightningModule. For instance, a model wrapped with FSDP will break because parameters need to be all-gathered across layers across ranks.
- In case the LightningModule leverages PyTorch LazyModules, users may want to generate this summary only after the first batch is processed in order to get accurate parameter estimations. Estimates of parameter sizes with lazy modules would be misleading.
### Pitch
A callback in Lightning naturally fits this extension purpose. It generalizes well across lightning modules, has great flexibility for when it can be called, and allows users to customize the summarization logic (e.g. integrate other libraries more easily).
- https://github.com/tyleryep/torchinfo
- https://github.com/facebookresearch/fvcore/blob/master/fvcore/nn/flop_count.py
- With this callback available, this logic can be removed from the core Trainer in order to be more pluggable:
- https://github.com/PyTorchLightning/pytorch-lightning/blob/6604fc1344e1b8a459c45a5a2157aa7fc60d950d/pytorch_lightning/trainer/trainer.py#L1000-L1004
AFAICT, this is the only piece of logic that runs in between `on_pretrain_routine_start/end` hooks. Would we still need these hooks if the summarization logic was removed from the trainer? Why doesn't this happen in `on_train_start` today?
https://github.com/PyTorchLightning/pytorch-lightning/blob/8a931732ae5135e3e55d9c7b7031d81837e5798a/pytorch_lightning/trainer/trainer.py#L1103-L1113
### Additional context
The model summary is by default enabled right now. This is likely the core issue we have to resolve as to whether this is opt-in or opt-out: https://github.com/PyTorchLightning/pytorch-lightning/issues/8478#issuecomment-884533398
Seeking @edenafek @tchaton 's input on this
<!-- Add any other context or screenshots here. -->
______________________________________________________________________
#### If you enjoy Lightning, check out our other projects! ⚡
<sub>
- [**Metrics**](https://github.com/PyTorchLightning/metrics): Machine learning metrics for distributed, scalable PyTorch applications.
- [**Flash**](https://github.com/PyTorchLightning/lightning-flash): The fastest way to get a Lightning baseline! A collection of tasks for fast prototyping, baselining, finetuning and solving problems with deep learning
- [**Bolts**](https://github.com/PyTorchLightning/lightning-bolts): Pretrained SOTA Deep Learning models, callbacks and more for research and production with PyTorch Lightning and PyTorch
- [**Lightning Transformers**](https://github.com/PyTorchLightning/lightning-transformers): Flexible interface for high performance research using SOTA Transformers leveraging Pytorch Lightning, Transformers, and Hydra.
</sub>
| 1.0 | [RFC] Deprecate `weights_summary` off the Trainer constructor - ## Proposed refactoring or deprecation
- Introduce a new ModelSummary callback, which calls `summarize`: https://github.com/PyTorchLightning/pytorch-lightning/blob/8a931732ae5135e3e55d9c7b7031d81837e5798a/pytorch_lightning/utilities/model_summary.py#L437-L439
- Deprecate `weights_summary` off the Trainer constructor
<!-- A clear and concise description of the code improvement -->
### Motivation
We are auditing the Lightning components and APIs to assess opportunities for improvements:
- https://github.com/PyTorchLightning/pytorch-lightning/issues/7740
- https://docs.google.com/document/d/1xHU7-iQSpp9KJTjI3As2EM0mfNHHr37WZYpDpwLkivA/edit#
This is a followup to https://github.com/PyTorchLightning/pytorch-lightning/issues/8478 and https://github.com/PyTorchLightning/pytorch-lightning/discussions/9006
Why do we want to remove this from the core trainer logic?
- We need a way for users to customize more of the inputs to the model summary over time without affecting the trainer API. Today, changes to the model summary API also require changes in the core trainer (e.g. the addition of `max_depth` ). This gives model summarization more room to grow without cascading changes elsewhere.
- Users may want to configure this summarization for different points of execution. For instance, calling this at the start of `trainer.fit()`, `trainer.validate()`, `trainer.test()` or `trainer.predict()`. Right now, this is hardcoded to be run only during `fit()`.
- Users may want to customize where they save the summary. Right now, it's printed to stdout, but this could also be useful to save to a file or upload to another service for tracking the run.
- The current implementation runs on global rank 0 only in order to avoid printing out multiple summary tables. However, running this on rank 0 will break for model parallel use cases that require communication across ranks. This can lead to subtle failures if `example_input_array` is set as a property on the LightningModule. For instance, a model wrapped with FSDP will break because parameters need to be all-gathered across layers across ranks.
- In case the LightningModule leverages PyTorch LazyModules, users may want to generate this summary only after the first batch is processed in order to get accurate parameter estimations. Estimates of parameter sizes with lazy modules would be misleading.
### Pitch
A callback in Lightning naturally fits this extension purpose. It generalizes well across lightning modules, has great flexibility for when it can be called, and allows users to customize the summarization logic (e.g. integrate other libraries more easily).
- https://github.com/tyleryep/torchinfo
- https://github.com/facebookresearch/fvcore/blob/master/fvcore/nn/flop_count.py
- With this callback available, this logic can be removed from the core Trainer in order to be more pluggable:
- https://github.com/PyTorchLightning/pytorch-lightning/blob/6604fc1344e1b8a459c45a5a2157aa7fc60d950d/pytorch_lightning/trainer/trainer.py#L1000-L1004
AFAICT, this is the only piece of logic that runs in between `on_pretrain_routine_start/end` hooks. Would we still need these hooks if the summarization logic was removed from the trainer? Why doesn't this happen in `on_train_start` today?
https://github.com/PyTorchLightning/pytorch-lightning/blob/8a931732ae5135e3e55d9c7b7031d81837e5798a/pytorch_lightning/trainer/trainer.py#L1103-L1113
### Additional context
The model summary is by default enabled right now. This is likely the core issue we have to resolve as to whether this is opt-in or opt-out: https://github.com/PyTorchLightning/pytorch-lightning/issues/8478#issuecomment-884533398
Seeking @edenafek @tchaton 's input on this
<!-- Add any other context or screenshots here. -->
______________________________________________________________________
#### If you enjoy Lightning, check out our other projects! ⚡
<sub>
- [**Metrics**](https://github.com/PyTorchLightning/metrics): Machine learning metrics for distributed, scalable PyTorch applications.
- [**Flash**](https://github.com/PyTorchLightning/lightning-flash): The fastest way to get a Lightning baseline! A collection of tasks for fast prototyping, baselining, finetuning and solving problems with deep learning
- [**Bolts**](https://github.com/PyTorchLightning/lightning-bolts): Pretrained SOTA Deep Learning models, callbacks and more for research and production with PyTorch Lightning and PyTorch
- [**Lightning Transformers**](https://github.com/PyTorchLightning/lightning-transformers): Flexible interface for high performance research using SOTA Transformers leveraging Pytorch Lightning, Transformers, and Hydra.
</sub>
| non_process | deprecate weights summary off the trainer constructor proposed refactoring or deprecation introduce a new modelsummary callback which calls summarize deprecate weights summary off the trainer constructor motivation we are auditing the lightning components and apis to assess opportunities for improvements this is a followup to and why do we want to remove this from the core trainer logic we need a way for users to customize more of the inputs to the model summary over time without affecting the trainer api today changes to the model summary api also require changes in the core trainer e g the addition of max depth this gives model summarization more room to grow without cascading changes elsewhere users may want to configure this summarization for different points of execution for instance calling this at the start of trainer fit trainer validate trainer test or trainer predict right now this is hardcoded to be run only during fit users may want to customize where they save the summary right now it s printed to stdout but this could also be useful to save to a file or upload to another service for tracking the run the current implementation runs on global rank only in order to avoid printing out multiple summary tables however running this on rank will break for model parallel use cases that require communication across ranks this can lead to subtle failures if example input array is set as a property on the lightningmodule for instance a model wrapped with fsdp will break because parameters need to be all gathered across layers across ranks in case the lightningmodule leverages pytorch lazymodules users may want to generate this summary only after the first batch is processed in order to get accurate parameter estimations estimates of parameter sizes with lazy modules would be misleading pitch a callback in lightning naturally fits this extension purpose it generalizes well across lightning modules has great flexibility for when it can be called and allows users to customize the summarization logic e g integrate other libraries more easily with this callback available this logic can be removed from the core trainer in order to be more pluggable afaict this is the only piece of logic that runs in between on pretrain routine start end hooks would we still need these hooks if the summarization logic was removed from the trainer why doesn t this happen in on train start today additional context the model summary is by default enabled right now this is likely the core issue we have to resolve as to whether this is opt in or opt out seeking edenafek tchaton s input on this if you enjoy lightning check out our other projects ⚡ machine learning metrics for distributed scalable pytorch applications the fastest way to get a lightning baseline a collection of tasks for fast prototyping baselining finetuning and solving problems with deep learning pretrained sota deep learning models callbacks and more for research and production with pytorch lightning and pytorch flexible interface for high performance research using sota transformers leveraging pytorch lightning transformers and hydra | 0 |
16,373 | 21,089,198,430 | IssuesEvent | 2022-04-04 01:30:28 | nodejs/node | https://api.github.com/repos/nodejs/node | closed | Check cwd before spawning child process | child_process feature request libuv stale | <!--
Thank you for reporting an issue.
This issue tracker is for bugs and issues found within Node.js core.
If you require more general support please file an issue on our help
repo. https://github.com/nodejs/help
Please fill in as much of the template below as you're able.
Version: output of `node -v`
Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)
Subsystem: if known, please specify affected core module name
If possible, please provide code that demonstrates the problem, keeping it as
simple and free of external dependencies as you are able.
-->
* **Version**: v7.6.0
* **Platform**: Darwin Pecorino.local 16.4.0 Darwin Kernel Version 16.4.0: Thu Dec 22 22:53:21 PST 2016; root:xnu-3789.41.3~3/RELEASE_X86_64 x86_64
When a cwd is passed to `child_process.spawn()` that does not exist, node just reports `ENOENT`:
```javascript
const spawn = require("child_process").spawn
spawn(process.execPath, { cwd: "/does/not/exist" });
```
```
> Error: spawn /usr/local/bin/node ENOENT
at exports._errnoException (util.js:1028:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:359:16)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickDomainCallback (internal/process/next_tick.js:122:9)
```
This error message is very confusing because it reads like `/usr/local/bin/node` does not exist. It took me several hours to debug this issue, including serious doubts in my sanity 😁.
Do you think it is feasible to check the cwd before spawning the process, or is there a use-case/is it possible to spawn a process with a non-existent cwd? If it's not feasible, would it be an option to include the cwd in the error message to give a slight hint in the right direction? | 1.0 | Check cwd before spawning child process - <!--
Thank you for reporting an issue.
This issue tracker is for bugs and issues found within Node.js core.
If you require more general support please file an issue on our help
repo. https://github.com/nodejs/help
Please fill in as much of the template below as you're able.
Version: output of `node -v`
Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)
Subsystem: if known, please specify affected core module name
If possible, please provide code that demonstrates the problem, keeping it as
simple and free of external dependencies as you are able.
-->
* **Version**: v7.6.0
* **Platform**: Darwin Pecorino.local 16.4.0 Darwin Kernel Version 16.4.0: Thu Dec 22 22:53:21 PST 2016; root:xnu-3789.41.3~3/RELEASE_X86_64 x86_64
When a cwd is passed to `child_process.spawn()` that does not exist, node just reports `ENOENT`:
```javascript
const spawn = require("child_process").spawn
spawn(process.execPath, { cwd: "/does/not/exist" });
```
```
> Error: spawn /usr/local/bin/node ENOENT
at exports._errnoException (util.js:1028:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:359:16)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickDomainCallback (internal/process/next_tick.js:122:9)
```
This error message is very confusing because it reads like `/usr/local/bin/node` does not exist. It took me several hours to debug this issue, including serious doubts in my sanity 😁.
Do you think it is feasible to check the cwd before spawning the process, or is there a use-case/is it possible to spawn a process with a non-existent cwd? If it's not feasible, would it be an option to include the cwd in the error message to give a slight hint in the right direction? | process | check cwd before spawning child process thank you for reporting an issue this issue tracker is for bugs and issues found within node js core if you require more general support please file an issue on our help repo please fill in as much of the template below as you re able version output of node v platform output of uname a unix or version and or bit windows subsystem if known please specify affected core module name if possible please provide code that demonstrates the problem keeping it as simple and free of external dependencies as you are able version platform darwin pecorino local darwin kernel version thu dec pst root xnu release when a cwd is passed to child process spawn that does not exist node just reports enoent javascript const spawn require child process spawn spawn process execpath cwd does not exist error spawn usr local bin node enoent at exports errnoexception util js at process childprocess handle onexit internal child process js at onerrornt internal child process js at combinedtickcallback internal process next tick js at process tickdomaincallback internal process next tick js this error message is very confusing because it reads like usr local bin node does not exist it took me several hours to debug this issue including serious doubts in my sanity 😁 do you think it is feasible to check the cwd before spawning the process or is there a use case is it possible to spawn a process with a non existent cwd if it s not feasible would it be an option to include the cwd in the error message to give a slight hint in the right direction | 1 |
27,535 | 7,977,935,894 | IssuesEvent | 2018-07-17 16:43:49 | zooniverse/Panoptes-Front-End | https://api.github.com/repos/zooniverse/Panoptes-Front-End | closed | viewing subject info in project builder should show hidden values | project builder stale ui | When viewing subjects and info in the project builder, if I'm a collaborator, I'd like to be able to see the _full_ set of values, with the ones that will be hidden from public view marked in some way.
This just came up because I thought some essential columns were missing from a gold-standard dataset in the pulsar SGL project, but in fact the project builder is just showing what the classifiers will, so the only way I can see all the columns is to download the subject export. (I don't have the original manifest because I'm a collaborator, not the project owner.)
| 1.0 | viewing subject info in project builder should show hidden values - When viewing subjects and info in the project builder, if I'm a collaborator, I'd like to be able to see the _full_ set of values, with the ones that will be hidden from public view marked in some way.
This just came up because I thought some essential columns were missing from a gold-standard dataset in the pulsar SGL project, but in fact the project builder is just showing what the classifiers will, so the only way I can see all the columns is to download the subject export. (I don't have the original manifest because I'm a collaborator, not the project owner.)
| non_process | viewing subject info in project builder should show hidden values when viewing subjects and info in the project builder if i m a collaborator i d like to be able to see the full set of values with the ones that will be hidden from public view marked in some way this just came up because i thought some essential columns were missing from a gold standard dataset in the pulsar sgl project but in fact the project builder is just showing what the classifiers will so the only way i can see all the columns is to download the subject export i don t have the original manifest because i m a collaborator not the project owner | 0 |
560,622 | 16,600,656,981 | IssuesEvent | 2021-06-01 18:57:38 | BCDevOps/developer-experience | https://api.github.com/repos/BCDevOps/developer-experience | closed | Deploy github org membership github app | SRE app-development high priority | ## Summary
Deploy the github app github.com/patricksimonian/just-ask and install for bcgov orgs
## To Do
- deploy app and test install
- update request tron issues for github org invites :)
- setup continuous deployment for the app | 1.0 | Deploy github org membership github app - ## Summary
Deploy the github app github.com/patricksimonian/just-ask and install for bcgov orgs
## To Do
- deploy app and test install
- update request tron issues for github org invites :)
- setup continuous deployment for the app | non_process | deploy github org membership github app summary deploy the github app github com patricksimonian just ask and install for bcgov orgs to do deploy app and test install update request tron issues for github org invites setup continuous deployment for the app | 0 |
14,012 | 16,816,526,002 | IssuesEvent | 2021-06-17 08:03:48 | GoogleCloudPlatform/fda-mystudies | https://api.github.com/repos/GoogleCloudPlatform/fda-mystudies | closed | [iOS] Data sharing > HTML breakage in iOS mobile for the data sharing learn more section | Bug P1 Process: Fixed Process: Tested dev iOS | Steps:
1. Add data sharing section from SB
2. Publish the updates
4. Open the study from iOS mobile
5. Navigate to data sharing section in consent process
6. Observe the screen
Actual: HTML breakage in iOS mobile for the data sharing learn more section
Expected: Consent document should display properly
Note: Issue not observed in Android
| 2.0 | [iOS] Data sharing > HTML breakage in iOS mobile for the data sharing learn more section - Steps:
1. Add data sharing section from SB
2. Publish the updates
4. Open the study from iOS mobile
5. Navigate to data sharing section in consent process
6. Observe the screen
Actual: HTML breakage in iOS mobile for the data sharing learn more section
Expected: Consent document should display properly
Note: Issue not observed in Android
| process | data sharing html breakage in ios mobile for the data sharing learn more section steps add data sharing section from sb publish the updates open the study from ios mobile navigate to data sharing section in consent process observe the screen actual html breakage in ios mobile for the data sharing learn more section expected consent document should display properly note issue not observed in android | 1 |
819,501 | 30,738,857,205 | IssuesEvent | 2023-07-28 09:48:48 | testomatio/app | https://api.github.com/repos/testomatio/app | closed | A company name can be created with an empty name field | bug priority high ui\ux | **Describe the bug**
The user can create a company name without any name.
The user sees a created company but can go “inside” because the title of the company is empty.
**To Reproduce**
Steps to reproduce the behavior:
1. Click on the blue button “Create”.
2. Clear the title field.
3. Click on the “Create” blue button.
4. Click on the “Companies” button in the header.
**Expected behavior**
The system shouldn’t allow to create a company without any name.
**Desktop**
- OS: Windows10
- Browser chrome
- Browser Version 114.0.5735.199
- Application: production
| 1.0 | A company name can be created with an empty name field - **Describe the bug**
The user can create a company name without any name.
The user sees a created company but can go “inside” because the title of the company is empty.
**To Reproduce**
Steps to reproduce the behavior:
1. Click on the blue button “Create”.
2. Clear the title field.
3. Click on the “Create” blue button.
4. Click on the “Companies” button in the header.
**Expected behavior**
The system shouldn’t allow to create a company without any name.
**Desktop**
- OS: Windows10
- Browser chrome
- Browser Version 114.0.5735.199
- Application: production
| non_process | a company name can be created with an empty name field describe the bug the user can create a company name without any name the user sees a created company but can go “inside” because the title of the company is empty to reproduce steps to reproduce the behavior click on the blue button “create” clear the title field click on the “create” blue button click on the “companies” button in the header expected behavior the system shouldn’t allow to create a company without any name desktop os browser chrome browser version application production | 0 |
11,694 | 14,544,156,822 | IssuesEvent | 2020-12-15 17:47:47 | MicrosoftDocs/azure-devops-docs | https://api.github.com/repos/MicrosoftDocs/azure-devops-docs | closed | How to Inject pipeline variable into bash environment? | Pri2 devops-cicd-process/tech devops/prod doc-enhancement | Hello,
I can't see a complete example of how to use a pipeline variable within a bash script. There is some piece of examples but insufficient for beginners.
I defined a variable in a pipeline, and I am trying to use it in a script that is run by yaml. The variable is always empty when it's printed within a bash script.
In Pipeline variables:
VARIABLE_NAME: 1234
**In yaml**
```
restore:
commands:
- !!defaultcommand
name: 'Restore SDK'
command: '.pipelines/restore.sh'
```
In **.pipelines/restore.sh**:
```echo "VARIABLE_NAME: $VARIABLE_NAME"```
VARIABLE_NAME is always empty. How can I make this work?
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: dd7e0bd3-1f7d-d7b6-cc72-5ef63c31b46a
* Version Independent ID: dae87abd-b73d-9120-bcdb-6097d4b40f2a
* Content: [Define variables - Azure Pipelines](https://docs.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch)
* Content Source: [docs/pipelines/process/variables.md](https://github.com/MicrosoftDocs/azure-devops-docs/blob/master/docs/pipelines/process/variables.md)
* Product: **devops**
* Technology: **devops-cicd-process**
* GitHub Login: @juliakm
* Microsoft Alias: **juliakm** | 1.0 | How to Inject pipeline variable into bash environment? - Hello,
I can't see a complete example of how to use a pipeline variable within a bash script. There is some piece of examples but insufficient for beginners.
I defined a variable in a pipeline, and I am trying to use it in a script that is run by yaml. The variable is always empty when it's printed within a bash script.
In Pipeline variables:
VARIABLE_NAME: 1234
**In yaml**
```
restore:
commands:
- !!defaultcommand
name: 'Restore SDK'
command: '.pipelines/restore.sh'
```
In **.pipelines/restore.sh**:
```echo "VARIABLE_NAME: $VARIABLE_NAME"```
VARIABLE_NAME is always empty. How can I make this work?
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: dd7e0bd3-1f7d-d7b6-cc72-5ef63c31b46a
* Version Independent ID: dae87abd-b73d-9120-bcdb-6097d4b40f2a
* Content: [Define variables - Azure Pipelines](https://docs.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch)
* Content Source: [docs/pipelines/process/variables.md](https://github.com/MicrosoftDocs/azure-devops-docs/blob/master/docs/pipelines/process/variables.md)
* Product: **devops**
* Technology: **devops-cicd-process**
* GitHub Login: @juliakm
* Microsoft Alias: **juliakm** | process | how to inject pipeline variable into bash environment hello i can t see a complete example of how to use a pipeline variable within a bash script there is some piece of examples but insufficient for beginners i defined a variable in a pipeline and i am trying to use it in a script that is run by yaml the variable is always empty when it s printed within a bash script in pipeline variables variable name in yaml restore commands defaultcommand name restore sdk command pipelines restore sh in pipelines restore sh echo variable name variable name variable name is always empty how can i make this work document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id bcdb content content source product devops technology devops cicd process github login juliakm microsoft alias juliakm | 1 |
19,405 | 25,545,758,638 | IssuesEvent | 2022-11-29 18:39:18 | bazelbuild/bazel | https://api.github.com/repos/bazelbuild/bazel | opened | Stop using absl flags in python based helpers | type: process | ### Description of the bug:
We depend on absl flags instead of argparse in many android helpers.
We could switch to argparse to reduce footprint.
### What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
_No response_
### Which operating system are you running Bazel on?
_No response_
### What is the output of `bazel info release`?
_No response_
### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.
_No response_
### What's the output of `git remote get-url origin; git rev-parse master; git rev-parse HEAD` ?
_No response_
### Have you found anything relevant by searching the web?
_No response_
### Any other information, logs, or outputs that you want to share?
_No response_ | 1.0 | Stop using absl flags in python based helpers - ### Description of the bug:
We depend on absl flags instead of argparse in many android helpers.
We could switch to argparse to reduce footprint.
### What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
_No response_
### Which operating system are you running Bazel on?
_No response_
### What is the output of `bazel info release`?
_No response_
### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.
_No response_
### What's the output of `git remote get-url origin; git rev-parse master; git rev-parse HEAD` ?
_No response_
### Have you found anything relevant by searching the web?
_No response_
### Any other information, logs, or outputs that you want to share?
_No response_ | process | stop using absl flags in python based helpers description of the bug we depend on absl flags instead of argparse in many android helpers we could switch to argparse to reduce footprint what s the simplest easiest way to reproduce this bug please provide a minimal example if possible no response which operating system are you running bazel on no response what is the output of bazel info release no response if bazel info release returns development version or non git tell us how you built bazel no response what s the output of git remote get url origin git rev parse master git rev parse head no response have you found anything relevant by searching the web no response any other information logs or outputs that you want to share no response | 1 |
19,357 | 25,490,976,114 | IssuesEvent | 2022-11-27 03:22:19 | hsmusic/hsmusic-wiki | https://api.github.com/repos/hsmusic/hsmusic-wiki | opened | getColors util doesn't accept #rgb short format | type: bug scope: data processing | Oops. This probably means any `Color: #rgb` codes don't work (need to confirm though). | 1.0 | getColors util doesn't accept #rgb short format - Oops. This probably means any `Color: #rgb` codes don't work (need to confirm though). | process | getcolors util doesn t accept rgb short format oops this probably means any color rgb codes don t work need to confirm though | 1 |
129,508 | 5,097,749,688 | IssuesEvent | 2017-01-03 22:31:39 | material-components/material-components-ios | https://api.github.com/repos/material-components/material-components-ios | closed | Look into services for suggesting "duplicate" bugs | priority:wishlist Triaged type:Feature request | As our issues grow it will be increasingly important that we triage and identify duplicates. We will do this as part of our weekly triaging, but having an automated service that can provide suggestions will reduce our overhead in identifying duplicates.
| 1.0 | Look into services for suggesting "duplicate" bugs - As our issues grow it will be increasingly important that we triage and identify duplicates. We will do this as part of our weekly triaging, but having an automated service that can provide suggestions will reduce our overhead in identifying duplicates.
| non_process | look into services for suggesting duplicate bugs as our issues grow it will be increasingly important that we triage and identify duplicates we will do this as part of our weekly triaging but having an automated service that can provide suggestions will reduce our overhead in identifying duplicates | 0 |
22,079 | 30,598,298,202 | IssuesEvent | 2023-07-22 03:29:44 | h4sh5/pypi-auto-scanner | https://api.github.com/repos/h4sh5/pypi-auto-scanner | opened | roblox-pyc 1.21.86 has 5 GuardDog issues | guarddog silent-process-execution | https://pypi.org/project/roblox-pyc
https://inspector.pypi.io/project/roblox-pyc
```{
"dependency": "roblox-pyc",
"version": "1.21.86",
"result": {
"issues": 5,
"errors": {},
"results": {
"silent-process-execution": [
{
"location": "roblox-pyc-1.21.86/robloxpyc/robloxpy.py:127",
"code": " subprocess.call([\"npm\", \"--version\"], stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL, stdin=subprocess.DEVNULL)",
"message": "This package is silently executing an external binary, redirecting stdout, stderr and stdin to /dev/null"
},
{
"location": "roblox-pyc-1.21.86/robloxpyc/robloxpy.py:133",
"code": " subprocess.call([\"rbxtsc\", \"--version\"], stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL, stdin=subprocess.DEVNULL)",
"message": "This package is silently executing an external binary, redirecting stdout, stderr and stdin to /dev/null"
},
{
"location": "roblox-pyc-1.21.86/robloxpyc/robloxpy.py:171",
"code": " subprocess.call([\"wally\", \"--version\"], stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL, stdin=subprocess.DEVNULL)",
"message": "This package is silently executing an external binary, redirecting stdout, stderr and stdin to /dev/null"
},
{
"location": "roblox-pyc-1.21.86/robloxpyc/robloxpy.py:181",
"code": " subprocess.call([\"luarocks\", \"--version\"], stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL, stdin=subprocess.DEVNULL)",
"message": "This package is silently executing an external binary, redirecting stdout, stderr and stdin to /dev/null"
},
{
"location": "roblox-pyc-1.21.86/robloxpyc/robloxpy.py:188",
"code": " subprocess.call([\"moonc\", \"--version\"], stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL, stdin=subprocess.DEVNULL)",
"message": "This package is silently executing an external binary, redirecting stdout, stderr and stdin to /dev/null"
}
]
},
"path": "/tmp/tmpyy_2ls8m/roblox-pyc"
}
}``` | 1.0 | roblox-pyc 1.21.86 has 5 GuardDog issues - https://pypi.org/project/roblox-pyc
https://inspector.pypi.io/project/roblox-pyc
```{
"dependency": "roblox-pyc",
"version": "1.21.86",
"result": {
"issues": 5,
"errors": {},
"results": {
"silent-process-execution": [
{
"location": "roblox-pyc-1.21.86/robloxpyc/robloxpy.py:127",
"code": " subprocess.call([\"npm\", \"--version\"], stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL, stdin=subprocess.DEVNULL)",
"message": "This package is silently executing an external binary, redirecting stdout, stderr and stdin to /dev/null"
},
{
"location": "roblox-pyc-1.21.86/robloxpyc/robloxpy.py:133",
"code": " subprocess.call([\"rbxtsc\", \"--version\"], stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL, stdin=subprocess.DEVNULL)",
"message": "This package is silently executing an external binary, redirecting stdout, stderr and stdin to /dev/null"
},
{
"location": "roblox-pyc-1.21.86/robloxpyc/robloxpy.py:171",
"code": " subprocess.call([\"wally\", \"--version\"], stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL, stdin=subprocess.DEVNULL)",
"message": "This package is silently executing an external binary, redirecting stdout, stderr and stdin to /dev/null"
},
{
"location": "roblox-pyc-1.21.86/robloxpyc/robloxpy.py:181",
"code": " subprocess.call([\"luarocks\", \"--version\"], stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL, stdin=subprocess.DEVNULL)",
"message": "This package is silently executing an external binary, redirecting stdout, stderr and stdin to /dev/null"
},
{
"location": "roblox-pyc-1.21.86/robloxpyc/robloxpy.py:188",
"code": " subprocess.call([\"moonc\", \"--version\"], stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL, stdin=subprocess.DEVNULL)",
"message": "This package is silently executing an external binary, redirecting stdout, stderr and stdin to /dev/null"
}
]
},
"path": "/tmp/tmpyy_2ls8m/roblox-pyc"
}
}``` | process | roblox pyc has guarddog issues dependency roblox pyc version result issues errors results silent process execution location roblox pyc robloxpyc robloxpy py code subprocess call stdout subprocess devnull stderr subprocess devnull stdin subprocess devnull message this package is silently executing an external binary redirecting stdout stderr and stdin to dev null location roblox pyc robloxpyc robloxpy py code subprocess call stdout subprocess devnull stderr subprocess devnull stdin subprocess devnull message this package is silently executing an external binary redirecting stdout stderr and stdin to dev null location roblox pyc robloxpyc robloxpy py code subprocess call stdout subprocess devnull stderr subprocess devnull stdin subprocess devnull message this package is silently executing an external binary redirecting stdout stderr and stdin to dev null location roblox pyc robloxpyc robloxpy py code subprocess call stdout subprocess devnull stderr subprocess devnull stdin subprocess devnull message this package is silently executing an external binary redirecting stdout stderr and stdin to dev null location roblox pyc robloxpyc robloxpy py code subprocess call stdout subprocess devnull stderr subprocess devnull stdin subprocess devnull message this package is silently executing an external binary redirecting stdout stderr and stdin to dev null path tmp tmpyy roblox pyc | 1 |
8,726 | 11,861,987,198 | IssuesEvent | 2020-03-25 17:11:37 | aiidateam/aiida-core | https://api.github.com/repos/aiidateam/aiida-core | closed | Allow `self.exit_codes` to be callable with keyword and custom message | priority/nice-to-have requires discussion topic/processes type/feature request | The use case was presented where one would like to define a generic exit code for a missing file, where one would always want to use the same exit status, but have a customized exit message that includes for example the exact filename. Currently this is not possible, but maybe it would be possible to extend the syntax to be able to do both:
```
exit_code_default = self.exit_codes.ERROR_MISSING_FILE
exit_code_custom = self.exit_codes(ERROR_MISSING_FILE, 'File `aiida.out` is missing')
```
we would have to make the `exit_codes` property callable and override the behavior to construct a new `ExitCode` instance with the custom message.
Or maybe even better, we make the `ExitCode` callable which allows to change the message. This would require the `ExitCode` to be changed from a named tuple into a class, e.g.:
```
class ExitCode(object):
def __init__(self, status, message):
self.status = status
self.message = message
def __call__(self, message):
self.message = message
return self
``` | 1.0 | Allow `self.exit_codes` to be callable with keyword and custom message - The use case was presented where one would like to define a generic exit code for a missing file, where one would always want to use the same exit status, but have a customized exit message that includes for example the exact filename. Currently this is not possible, but maybe it would be possible to extend the syntax to be able to do both:
```
exit_code_default = self.exit_codes.ERROR_MISSING_FILE
exit_code_custom = self.exit_codes(ERROR_MISSING_FILE, 'File `aiida.out` is missing')
```
we would have to make the `exit_codes` property callable and override the behavior to construct a new `ExitCode` instance with the custom message.
Or maybe even better, we make the `ExitCode` callable which allows to change the message. This would require the `ExitCode` to be changed from a named tuple into a class, e.g.:
```
class ExitCode(object):
def __init__(self, status, message):
self.status = status
self.message = message
def __call__(self, message):
self.message = message
return self
``` | process | allow self exit codes to be callable with keyword and custom message the use case was presented where one would like to define a generic exit code for a missing file where one would always want to use the same exit status but have a customized exit message that includes for example the exact filename currently this is not possible but maybe it would be possible to extend the syntax to be able to do both exit code default self exit codes error missing file exit code custom self exit codes error missing file file aiida out is missing we would have to make the exit codes property callable and override the behavior to construct a new exitcode instance with the custom message or maybe even better we make the exitcode callable which allows to change the message this would require the exitcode to be changed from a named tuple into a class e g class exitcode object def init self status message self status status self message message def call self message self message message return self | 1 |
21,216 | 28,298,336,471 | IssuesEvent | 2023-04-10 02:00:08 | lizhihao6/get-daily-arxiv-noti | https://api.github.com/repos/lizhihao6/get-daily-arxiv-noti | opened | New submissions for Mon, 10 Apr 23 | event camera white balance isp compression image signal processing image signal process raw raw image events camera color contrast events AWB | ## Keyword: events
There is no result
## Keyword: event camera
There is no result
## Keyword: events camera
There is no result
## Keyword: white balance
There is no result
## Keyword: color contrast
There is no result
## Keyword: AWB
There is no result
## Keyword: ISP
### Multispectral Imaging for Differential Face Morphing Attack Detection: A Preliminary Study
- **Authors:** Raghavendra Ramachandra, Sushma Venkatesh, Naser Damer, Narayan Vetrekar, Rajendra Gad
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV)
- **Arxiv link:** https://arxiv.org/abs/2304.03510
- **Pdf link:** https://arxiv.org/pdf/2304.03510
- **Abstract**
Face morphing attack detection is emerging as an increasingly challenging problem owing to advancements in high-quality and realistic morphing attack generation. Reliable detection of morphing attacks is essential because these attacks are targeted for border control applications. This paper presents a multispectral framework for differential morphing-attack detection (D-MAD). The D-MAD methods are based on using two facial images that are captured from the ePassport (also called the reference image) and the trusted device (for example, Automatic Border Control (ABC) gates) to detect whether the face image presented in ePassport is morphed. The proposed multispectral D-MAD framework introduce a multispectral image captured as a trusted capture to capture seven different spectral bands to detect morphing attacks. Extensive experiments were conducted on the newly created datasets with 143 unique data subjects that were captured using both visible and multispectral cameras in multiple sessions. The results indicate the superior performance of the proposed multispectral framework compared to visible images.
### Embodied Concept Learner: Self-supervised Learning of Concepts and Mapping through Instruction Following
- **Authors:** Mingyu Ding, Yan Xu, Zhenfang Chen, David Daniel Cox, Ping Luo, Joshua B. Tenenbaum, Chuang Gan
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV)
- **Arxiv link:** https://arxiv.org/abs/2304.03767
- **Pdf link:** https://arxiv.org/pdf/2304.03767
- **Abstract**
Humans, even at a very early age, can learn visual concepts and understand geometry and layout through active interaction with the environment, and generalize their compositions to complete tasks described by natural languages in novel scenes. To mimic such capability, we propose Embodied Concept Learner (ECL) in an interactive 3D environment. Specifically, a robot agent can ground visual concepts, build semantic maps and plan actions to complete tasks by learning purely from human demonstrations and language instructions, without access to ground-truth semantic and depth supervisions from simulations. ECL consists of: (i) an instruction parser that translates the natural languages into executable programs; (ii) an embodied concept learner that grounds visual concepts based on language descriptions; (iii) a map constructor that estimates depth and constructs semantic maps by leveraging the learned concepts; and (iv) a program executor with deterministic policies to execute each program. ECL has several appealing benefits thanks to its modularized design. Firstly, it enables the robotic agent to learn semantics and depth unsupervisedly acting like babies, e.g., ground concepts through active interaction and perceive depth by disparities when moving forward. Secondly, ECL is fully transparent and step-by-step interpretable in long-term planning. Thirdly, ECL could be beneficial for the embodied instruction following (EIF), outperforming previous works on the ALFRED benchmark when the semantic label is not provided. Also, the learned concept can be reused for other downstream tasks, such as reasoning of object states. Project page: this http URL
## Keyword: image signal processing
There is no result
## Keyword: image signal process
There is no result
## Keyword: compression
There is no result
## Keyword: RAW
### Rethinking Evaluation Protocols of Visual Representations Learned via Self-supervised Learning
- **Authors:** Jae-Hun Lee, Doyoung Yoon, ByeongMoon Ji, Kyungyul Kim, Sangheum Hwang
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV); Machine Learning (cs.LG)
- **Arxiv link:** https://arxiv.org/abs/2304.03456
- **Pdf link:** https://arxiv.org/pdf/2304.03456
- **Abstract**
Linear probing (LP) (and $k$-NN) on the upstream dataset with labels (e.g., ImageNet) and transfer learning (TL) to various downstream datasets are commonly employed to evaluate the quality of visual representations learned via self-supervised learning (SSL). Although existing SSL methods have shown good performances under those evaluation protocols, we observe that the performances are very sensitive to the hyperparameters involved in LP and TL. We argue that this is an undesirable behavior since truly generic representations should be easily adapted to any other visual recognition task, i.e., the learned representations should be robust to the settings of LP and TL hyperparameters. In this work, we try to figure out the cause of performance sensitivity by conducting extensive experiments with state-of-the-art SSL methods. First, we find that input normalization for LP is crucial to eliminate performance variations according to the hyperparameters. Specifically, batch normalization before feeding inputs to a linear classifier considerably improves the stability of evaluation, and also resolves inconsistency of $k$-NN and LP metrics. Second, for TL, we demonstrate that a weight decay parameter in SSL significantly affects the transferability of learned representations, which cannot be identified by LP or $k$-NN evaluations on the upstream dataset. We believe that the findings of this study will be beneficial for the community by drawing attention to the shortcomings in the current SSL evaluation schemes and underscoring the need to reconsider them.
### Local Rose Breeds Detection System Using Transfer Learning Techniques
- **Authors:** Amena Begum Farha, Md. Azizul Hakim, Mst. Eshita Khatun
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV); Artificial Intelligence (cs.AI)
- **Arxiv link:** https://arxiv.org/abs/2304.03509
- **Pdf link:** https://arxiv.org/pdf/2304.03509
- **Abstract**
Flower breed detection and giving details of that breed with the suggestion of cultivation processes and the way of taking care is important for flower cultivation, breed invention, and the flower business. Among all the local flowers in Bangladesh, the rose is one of the most popular and demanded flowers. Roses are the most desirable flower not only in Bangladesh but also throughout the world. Roses can be used for many other purposes apart from decoration. As roses have a great demand in the flower business so rose breed detection will be very essential. However, there is no remarkable work for breed detection of a particular flower unlike the classification of different flowers. In this research, we have proposed a model to detect rose breeds from images using transfer learning techniques. For such work in flowers, resources are not enough in image processing and classification, so we needed a large dataset of the massive number of images to train our model. we have used 1939 raw images of five different breeds and we have generated 9306 images for the training dataset and 388 images for the testing dataset to validate the model using augmentation. We have applied four transfer learning models in this research, which are Inception V3, ResNet50, Xception, and VGG16. Among these four models, VGG16 achieved the highest accuracy of 99%, which is an excellent outcome. Breed detection of a rose by using transfer learning methods is the first work on breed detection of a particular flower that is publicly available according to the study.
## Keyword: raw image
### Local Rose Breeds Detection System Using Transfer Learning Techniques
- **Authors:** Amena Begum Farha, Md. Azizul Hakim, Mst. Eshita Khatun
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV); Artificial Intelligence (cs.AI)
- **Arxiv link:** https://arxiv.org/abs/2304.03509
- **Pdf link:** https://arxiv.org/pdf/2304.03509
- **Abstract**
Flower breed detection and giving details of that breed with the suggestion of cultivation processes and the way of taking care is important for flower cultivation, breed invention, and the flower business. Among all the local flowers in Bangladesh, the rose is one of the most popular and demanded flowers. Roses are the most desirable flower not only in Bangladesh but also throughout the world. Roses can be used for many other purposes apart from decoration. As roses have a great demand in the flower business so rose breed detection will be very essential. However, there is no remarkable work for breed detection of a particular flower unlike the classification of different flowers. In this research, we have proposed a model to detect rose breeds from images using transfer learning techniques. For such work in flowers, resources are not enough in image processing and classification, so we needed a large dataset of the massive number of images to train our model. we have used 1939 raw images of five different breeds and we have generated 9306 images for the training dataset and 388 images for the testing dataset to validate the model using augmentation. We have applied four transfer learning models in this research, which are Inception V3, ResNet50, Xception, and VGG16. Among these four models, VGG16 achieved the highest accuracy of 99%, which is an excellent outcome. Breed detection of a rose by using transfer learning methods is the first work on breed detection of a particular flower that is publicly available according to the study.
| 2.0 | New submissions for Mon, 10 Apr 23 - ## Keyword: events
There is no result
## Keyword: event camera
There is no result
## Keyword: events camera
There is no result
## Keyword: white balance
There is no result
## Keyword: color contrast
There is no result
## Keyword: AWB
There is no result
## Keyword: ISP
### Multispectral Imaging for Differential Face Morphing Attack Detection: A Preliminary Study
- **Authors:** Raghavendra Ramachandra, Sushma Venkatesh, Naser Damer, Narayan Vetrekar, Rajendra Gad
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV)
- **Arxiv link:** https://arxiv.org/abs/2304.03510
- **Pdf link:** https://arxiv.org/pdf/2304.03510
- **Abstract**
Face morphing attack detection is emerging as an increasingly challenging problem owing to advancements in high-quality and realistic morphing attack generation. Reliable detection of morphing attacks is essential because these attacks are targeted for border control applications. This paper presents a multispectral framework for differential morphing-attack detection (D-MAD). The D-MAD methods are based on using two facial images that are captured from the ePassport (also called the reference image) and the trusted device (for example, Automatic Border Control (ABC) gates) to detect whether the face image presented in ePassport is morphed. The proposed multispectral D-MAD framework introduce a multispectral image captured as a trusted capture to capture seven different spectral bands to detect morphing attacks. Extensive experiments were conducted on the newly created datasets with 143 unique data subjects that were captured using both visible and multispectral cameras in multiple sessions. The results indicate the superior performance of the proposed multispectral framework compared to visible images.
### Embodied Concept Learner: Self-supervised Learning of Concepts and Mapping through Instruction Following
- **Authors:** Mingyu Ding, Yan Xu, Zhenfang Chen, David Daniel Cox, Ping Luo, Joshua B. Tenenbaum, Chuang Gan
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV)
- **Arxiv link:** https://arxiv.org/abs/2304.03767
- **Pdf link:** https://arxiv.org/pdf/2304.03767
- **Abstract**
Humans, even at a very early age, can learn visual concepts and understand geometry and layout through active interaction with the environment, and generalize their compositions to complete tasks described by natural languages in novel scenes. To mimic such capability, we propose Embodied Concept Learner (ECL) in an interactive 3D environment. Specifically, a robot agent can ground visual concepts, build semantic maps and plan actions to complete tasks by learning purely from human demonstrations and language instructions, without access to ground-truth semantic and depth supervisions from simulations. ECL consists of: (i) an instruction parser that translates the natural languages into executable programs; (ii) an embodied concept learner that grounds visual concepts based on language descriptions; (iii) a map constructor that estimates depth and constructs semantic maps by leveraging the learned concepts; and (iv) a program executor with deterministic policies to execute each program. ECL has several appealing benefits thanks to its modularized design. Firstly, it enables the robotic agent to learn semantics and depth unsupervisedly acting like babies, e.g., ground concepts through active interaction and perceive depth by disparities when moving forward. Secondly, ECL is fully transparent and step-by-step interpretable in long-term planning. Thirdly, ECL could be beneficial for the embodied instruction following (EIF), outperforming previous works on the ALFRED benchmark when the semantic label is not provided. Also, the learned concept can be reused for other downstream tasks, such as reasoning of object states. Project page: this http URL
## Keyword: image signal processing
There is no result
## Keyword: image signal process
There is no result
## Keyword: compression
There is no result
## Keyword: RAW
### Rethinking Evaluation Protocols of Visual Representations Learned via Self-supervised Learning
- **Authors:** Jae-Hun Lee, Doyoung Yoon, ByeongMoon Ji, Kyungyul Kim, Sangheum Hwang
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV); Machine Learning (cs.LG)
- **Arxiv link:** https://arxiv.org/abs/2304.03456
- **Pdf link:** https://arxiv.org/pdf/2304.03456
- **Abstract**
Linear probing (LP) (and $k$-NN) on the upstream dataset with labels (e.g., ImageNet) and transfer learning (TL) to various downstream datasets are commonly employed to evaluate the quality of visual representations learned via self-supervised learning (SSL). Although existing SSL methods have shown good performances under those evaluation protocols, we observe that the performances are very sensitive to the hyperparameters involved in LP and TL. We argue that this is an undesirable behavior since truly generic representations should be easily adapted to any other visual recognition task, i.e., the learned representations should be robust to the settings of LP and TL hyperparameters. In this work, we try to figure out the cause of performance sensitivity by conducting extensive experiments with state-of-the-art SSL methods. First, we find that input normalization for LP is crucial to eliminate performance variations according to the hyperparameters. Specifically, batch normalization before feeding inputs to a linear classifier considerably improves the stability of evaluation, and also resolves inconsistency of $k$-NN and LP metrics. Second, for TL, we demonstrate that a weight decay parameter in SSL significantly affects the transferability of learned representations, which cannot be identified by LP or $k$-NN evaluations on the upstream dataset. We believe that the findings of this study will be beneficial for the community by drawing attention to the shortcomings in the current SSL evaluation schemes and underscoring the need to reconsider them.
### Local Rose Breeds Detection System Using Transfer Learning Techniques
- **Authors:** Amena Begum Farha, Md. Azizul Hakim, Mst. Eshita Khatun
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV); Artificial Intelligence (cs.AI)
- **Arxiv link:** https://arxiv.org/abs/2304.03509
- **Pdf link:** https://arxiv.org/pdf/2304.03509
- **Abstract**
Flower breed detection and giving details of that breed with the suggestion of cultivation processes and the way of taking care is important for flower cultivation, breed invention, and the flower business. Among all the local flowers in Bangladesh, the rose is one of the most popular and demanded flowers. Roses are the most desirable flower not only in Bangladesh but also throughout the world. Roses can be used for many other purposes apart from decoration. As roses have a great demand in the flower business so rose breed detection will be very essential. However, there is no remarkable work for breed detection of a particular flower unlike the classification of different flowers. In this research, we have proposed a model to detect rose breeds from images using transfer learning techniques. For such work in flowers, resources are not enough in image processing and classification, so we needed a large dataset of the massive number of images to train our model. we have used 1939 raw images of five different breeds and we have generated 9306 images for the training dataset and 388 images for the testing dataset to validate the model using augmentation. We have applied four transfer learning models in this research, which are Inception V3, ResNet50, Xception, and VGG16. Among these four models, VGG16 achieved the highest accuracy of 99%, which is an excellent outcome. Breed detection of a rose by using transfer learning methods is the first work on breed detection of a particular flower that is publicly available according to the study.
## Keyword: raw image
### Local Rose Breeds Detection System Using Transfer Learning Techniques
- **Authors:** Amena Begum Farha, Md. Azizul Hakim, Mst. Eshita Khatun
- **Subjects:** Computer Vision and Pattern Recognition (cs.CV); Artificial Intelligence (cs.AI)
- **Arxiv link:** https://arxiv.org/abs/2304.03509
- **Pdf link:** https://arxiv.org/pdf/2304.03509
- **Abstract**
Flower breed detection and giving details of that breed with the suggestion of cultivation processes and the way of taking care is important for flower cultivation, breed invention, and the flower business. Among all the local flowers in Bangladesh, the rose is one of the most popular and demanded flowers. Roses are the most desirable flower not only in Bangladesh but also throughout the world. Roses can be used for many other purposes apart from decoration. As roses have a great demand in the flower business so rose breed detection will be very essential. However, there is no remarkable work for breed detection of a particular flower unlike the classification of different flowers. In this research, we have proposed a model to detect rose breeds from images using transfer learning techniques. For such work in flowers, resources are not enough in image processing and classification, so we needed a large dataset of the massive number of images to train our model. we have used 1939 raw images of five different breeds and we have generated 9306 images for the training dataset and 388 images for the testing dataset to validate the model using augmentation. We have applied four transfer learning models in this research, which are Inception V3, ResNet50, Xception, and VGG16. Among these four models, VGG16 achieved the highest accuracy of 99%, which is an excellent outcome. Breed detection of a rose by using transfer learning methods is the first work on breed detection of a particular flower that is publicly available according to the study.
| process | new submissions for mon apr keyword events there is no result keyword event camera there is no result keyword events camera there is no result keyword white balance there is no result keyword color contrast there is no result keyword awb there is no result keyword isp multispectral imaging for differential face morphing attack detection a preliminary study authors raghavendra ramachandra sushma venkatesh naser damer narayan vetrekar rajendra gad subjects computer vision and pattern recognition cs cv arxiv link pdf link abstract face morphing attack detection is emerging as an increasingly challenging problem owing to advancements in high quality and realistic morphing attack generation reliable detection of morphing attacks is essential because these attacks are targeted for border control applications this paper presents a multispectral framework for differential morphing attack detection d mad the d mad methods are based on using two facial images that are captured from the epassport also called the reference image and the trusted device for example automatic border control abc gates to detect whether the face image presented in epassport is morphed the proposed multispectral d mad framework introduce a multispectral image captured as a trusted capture to capture seven different spectral bands to detect morphing attacks extensive experiments were conducted on the newly created datasets with unique data subjects that were captured using both visible and multispectral cameras in multiple sessions the results indicate the superior performance of the proposed multispectral framework compared to visible images embodied concept learner self supervised learning of concepts and mapping through instruction following authors mingyu ding yan xu zhenfang chen david daniel cox ping luo joshua b tenenbaum chuang gan subjects computer vision and pattern recognition cs cv arxiv link pdf link abstract humans even at a very early age can learn visual concepts and understand geometry and layout through active interaction with the environment and generalize their compositions to complete tasks described by natural languages in novel scenes to mimic such capability we propose embodied concept learner ecl in an interactive environment specifically a robot agent can ground visual concepts build semantic maps and plan actions to complete tasks by learning purely from human demonstrations and language instructions without access to ground truth semantic and depth supervisions from simulations ecl consists of i an instruction parser that translates the natural languages into executable programs ii an embodied concept learner that grounds visual concepts based on language descriptions iii a map constructor that estimates depth and constructs semantic maps by leveraging the learned concepts and iv a program executor with deterministic policies to execute each program ecl has several appealing benefits thanks to its modularized design firstly it enables the robotic agent to learn semantics and depth unsupervisedly acting like babies e g ground concepts through active interaction and perceive depth by disparities when moving forward secondly ecl is fully transparent and step by step interpretable in long term planning thirdly ecl could be beneficial for the embodied instruction following eif outperforming previous works on the alfred benchmark when the semantic label is not provided also the learned concept can be reused for other downstream tasks such as reasoning of object states project page this http url keyword image signal processing there is no result keyword image signal process there is no result keyword compression there is no result keyword raw rethinking evaluation protocols of visual representations learned via self supervised learning authors jae hun lee doyoung yoon byeongmoon ji kyungyul kim sangheum hwang subjects computer vision and pattern recognition cs cv machine learning cs lg arxiv link pdf link abstract linear probing lp and k nn on the upstream dataset with labels e g imagenet and transfer learning tl to various downstream datasets are commonly employed to evaluate the quality of visual representations learned via self supervised learning ssl although existing ssl methods have shown good performances under those evaluation protocols we observe that the performances are very sensitive to the hyperparameters involved in lp and tl we argue that this is an undesirable behavior since truly generic representations should be easily adapted to any other visual recognition task i e the learned representations should be robust to the settings of lp and tl hyperparameters in this work we try to figure out the cause of performance sensitivity by conducting extensive experiments with state of the art ssl methods first we find that input normalization for lp is crucial to eliminate performance variations according to the hyperparameters specifically batch normalization before feeding inputs to a linear classifier considerably improves the stability of evaluation and also resolves inconsistency of k nn and lp metrics second for tl we demonstrate that a weight decay parameter in ssl significantly affects the transferability of learned representations which cannot be identified by lp or k nn evaluations on the upstream dataset we believe that the findings of this study will be beneficial for the community by drawing attention to the shortcomings in the current ssl evaluation schemes and underscoring the need to reconsider them local rose breeds detection system using transfer learning techniques authors amena begum farha md azizul hakim mst eshita khatun subjects computer vision and pattern recognition cs cv artificial intelligence cs ai arxiv link pdf link abstract flower breed detection and giving details of that breed with the suggestion of cultivation processes and the way of taking care is important for flower cultivation breed invention and the flower business among all the local flowers in bangladesh the rose is one of the most popular and demanded flowers roses are the most desirable flower not only in bangladesh but also throughout the world roses can be used for many other purposes apart from decoration as roses have a great demand in the flower business so rose breed detection will be very essential however there is no remarkable work for breed detection of a particular flower unlike the classification of different flowers in this research we have proposed a model to detect rose breeds from images using transfer learning techniques for such work in flowers resources are not enough in image processing and classification so we needed a large dataset of the massive number of images to train our model we have used raw images of five different breeds and we have generated images for the training dataset and images for the testing dataset to validate the model using augmentation we have applied four transfer learning models in this research which are inception xception and among these four models achieved the highest accuracy of which is an excellent outcome breed detection of a rose by using transfer learning methods is the first work on breed detection of a particular flower that is publicly available according to the study keyword raw image local rose breeds detection system using transfer learning techniques authors amena begum farha md azizul hakim mst eshita khatun subjects computer vision and pattern recognition cs cv artificial intelligence cs ai arxiv link pdf link abstract flower breed detection and giving details of that breed with the suggestion of cultivation processes and the way of taking care is important for flower cultivation breed invention and the flower business among all the local flowers in bangladesh the rose is one of the most popular and demanded flowers roses are the most desirable flower not only in bangladesh but also throughout the world roses can be used for many other purposes apart from decoration as roses have a great demand in the flower business so rose breed detection will be very essential however there is no remarkable work for breed detection of a particular flower unlike the classification of different flowers in this research we have proposed a model to detect rose breeds from images using transfer learning techniques for such work in flowers resources are not enough in image processing and classification so we needed a large dataset of the massive number of images to train our model we have used raw images of five different breeds and we have generated images for the training dataset and images for the testing dataset to validate the model using augmentation we have applied four transfer learning models in this research which are inception xception and among these four models achieved the highest accuracy of which is an excellent outcome breed detection of a rose by using transfer learning methods is the first work on breed detection of a particular flower that is publicly available according to the study | 1 |
12,593 | 14,992,343,987 | IssuesEvent | 2021-01-29 09:44:18 | spring-projects/spring-hateoas | https://api.github.com/repos/spring-projects/spring-hateoas | closed | RepresentationModelProcessor<CollectionModel<CustomModel>> didn't come into effect when CustomModel directly inherit from RepresentationModel | in: core process: waiting for feedback | I have a class ProjectNodeModel which subclass from RepresentationModel , but when I defined a bean RepresentationModelProcessor<CollectionModel<ProjectNodeModel>> in Configuration , this bean didn't come into effect,
I look into org.springframework.hateoas.server.mvc.RepresentationModelProcessorInvoker.CollectionModelProcessorWrapper#isValueTypeMatch , which doesn't cover this situation | 1.0 | RepresentationModelProcessor<CollectionModel<CustomModel>> didn't come into effect when CustomModel directly inherit from RepresentationModel - I have a class ProjectNodeModel which subclass from RepresentationModel , but when I defined a bean RepresentationModelProcessor<CollectionModel<ProjectNodeModel>> in Configuration , this bean didn't come into effect,
I look into org.springframework.hateoas.server.mvc.RepresentationModelProcessorInvoker.CollectionModelProcessorWrapper#isValueTypeMatch , which doesn't cover this situation | process | representationmodelprocessor didn t come into effect when custommodel directly inherit from representationmodel i have a class projectnodemodel which subclass from representationmodel but when i defined a bean representationmodelprocessor in configuration this bean didn t come into effect i look into org springframework hateoas server mvc representationmodelprocessorinvoker collectionmodelprocessorwrapper isvaluetypematch which doesn t cover this situation | 1 |
9,686 | 12,686,475,501 | IssuesEvent | 2020-06-20 11:09:35 | prisma/e2e-tests | https://api.github.com/repos/prisma/e2e-tests | opened | Document branches and connected Npm dist tags | kind/improvement process/candidate | This repository runs automation for multiple branches. This should be documented in the README so people can discover these branches and understand what they are doing. | 1.0 | Document branches and connected Npm dist tags - This repository runs automation for multiple branches. This should be documented in the README so people can discover these branches and understand what they are doing. | process | document branches and connected npm dist tags this repository runs automation for multiple branches this should be documented in the readme so people can discover these branches and understand what they are doing | 1 |
3,431 | 6,529,945,103 | IssuesEvent | 2017-08-30 13:35:51 | allinurl/goaccess | https://api.github.com/repos/allinurl/goaccess | closed | static files with paremeters should not be in the "requested files" | log-processing question | ```
> goaccess --version
GoAccess - 1.2.
```
```
> lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
```
for example, from my site's recent log, I got:
```
2 - Requested Files (URLs) Total: 366/630
Hits h% Vis. v% Bandwidth Mtd Proto Data
---- ----- ---- ----- ----------- ---- -------- ----
316 8.86% 11 0.39% 0.0 B HEAD HTTP/1.1 /
147 4.12% 80 2.81% 1.33 MiB GET HTTP/1.1 /
112 3.14% 30 1.05% 339.14 KiB GET HTTP/1.1 /feed
64 1.80% 33 1.16% 245.41 KiB GET HTTP/1.1 /wp-login.php
63 1.77% 61 2.14% 35.56 KiB GET HTTP/1.1 /wp-includes/js/comment-reply.min.js?ver=4.8.1
61 1.71% 59 2.07% 37.18 KiB GET HTTP/1.1 /wp-content/themes/twentytwelve/js/navigation.js?ver=20140711
61 1.71% 59 2.07% 43.09 KiB GET HTTP/1.1 /wp-includes/js/wp-embed.min.js?ver=4.8.1
```
Those files like `xxx.js?ver=x.y.z` should not be recognized as requested files, they are actually static files too. | 1.0 | static files with paremeters should not be in the "requested files" - ```
> goaccess --version
GoAccess - 1.2.
```
```
> lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
```
for example, from my site's recent log, I got:
```
2 - Requested Files (URLs) Total: 366/630
Hits h% Vis. v% Bandwidth Mtd Proto Data
---- ----- ---- ----- ----------- ---- -------- ----
316 8.86% 11 0.39% 0.0 B HEAD HTTP/1.1 /
147 4.12% 80 2.81% 1.33 MiB GET HTTP/1.1 /
112 3.14% 30 1.05% 339.14 KiB GET HTTP/1.1 /feed
64 1.80% 33 1.16% 245.41 KiB GET HTTP/1.1 /wp-login.php
63 1.77% 61 2.14% 35.56 KiB GET HTTP/1.1 /wp-includes/js/comment-reply.min.js?ver=4.8.1
61 1.71% 59 2.07% 37.18 KiB GET HTTP/1.1 /wp-content/themes/twentytwelve/js/navigation.js?ver=20140711
61 1.71% 59 2.07% 43.09 KiB GET HTTP/1.1 /wp-includes/js/wp-embed.min.js?ver=4.8.1
```
Those files like `xxx.js?ver=x.y.z` should not be recognized as requested files, they are actually static files too. | process | static files with paremeters should not be in the requested files goaccess version goaccess lsb release a no lsb modules are available distributor id ubuntu description ubuntu lts release codename xenial for example from my site s recent log i got requested files urls total hits h vis v bandwidth mtd proto data b head http mib get http kib get http feed kib get http wp login php kib get http wp includes js comment reply min js ver kib get http wp content themes twentytwelve js navigation js ver kib get http wp includes js wp embed min js ver those files like xxx js ver x y z should not be recognized as requested files they are actually static files too | 1 |
9,702 | 12,702,106,996 | IssuesEvent | 2020-06-22 19:30:08 | unicode-org/icu4x | https://api.github.com/repos/unicode-org/icu4x | closed | Make scope more explicit in the charter | A-scope C-process T-docs | The charter currently says:
> OmnICU will provide an ECMA-402-compatible API surface in the target client-side platforms
and:
> **What if clients need a feature that is not in ECMA-402?**
> Clients of OmnICU may need features beyond those recommended by ECMA-402. The subcommittee is not ruling out the option of adding additional features in the same style as ECMA-402 to cover additional client needs. The details for how to determine what features belong in OmnICU that aren't already in ECMA-402 will be discussed at a future time.
The caption in ecosystem.md says:
> This document tracks the crates that already exist in the ecosystem that cover functionality that we may wish to cover in OmnICU.
I added the word "may" in #41.
I think it's important that we be more explicit about the use cases that ICU4X is supporting. This will guide our discussions, such as https://github.com/unicode-org/icu4x/pull/43#discussion_r413329507, when deciding whether a certain API or functional unit belongs in ICU4X.
We could start by making an explicit list of use cases that warrant APIs and functional units not covered by 402, and adding that list to the charter. It might be best to do this on a case-by-case basis: if proposing a feature not explicitly sanctioned by the charter, then propose a change to the charter adding the corresponding use case to the charter, such that we can agree on that change in the subcommittee meeting.
@zbraniecki | 1.0 | Make scope more explicit in the charter - The charter currently says:
> OmnICU will provide an ECMA-402-compatible API surface in the target client-side platforms
and:
> **What if clients need a feature that is not in ECMA-402?**
> Clients of OmnICU may need features beyond those recommended by ECMA-402. The subcommittee is not ruling out the option of adding additional features in the same style as ECMA-402 to cover additional client needs. The details for how to determine what features belong in OmnICU that aren't already in ECMA-402 will be discussed at a future time.
The caption in ecosystem.md says:
> This document tracks the crates that already exist in the ecosystem that cover functionality that we may wish to cover in OmnICU.
I added the word "may" in #41.
I think it's important that we be more explicit about the use cases that ICU4X is supporting. This will guide our discussions, such as https://github.com/unicode-org/icu4x/pull/43#discussion_r413329507, when deciding whether a certain API or functional unit belongs in ICU4X.
We could start by making an explicit list of use cases that warrant APIs and functional units not covered by 402, and adding that list to the charter. It might be best to do this on a case-by-case basis: if proposing a feature not explicitly sanctioned by the charter, then propose a change to the charter adding the corresponding use case to the charter, such that we can agree on that change in the subcommittee meeting.
@zbraniecki | process | make scope more explicit in the charter the charter currently says omnicu will provide an ecma compatible api surface in the target client side platforms and what if clients need a feature that is not in ecma clients of omnicu may need features beyond those recommended by ecma the subcommittee is not ruling out the option of adding additional features in the same style as ecma to cover additional client needs the details for how to determine what features belong in omnicu that aren t already in ecma will be discussed at a future time the caption in ecosystem md says this document tracks the crates that already exist in the ecosystem that cover functionality that we may wish to cover in omnicu i added the word may in i think it s important that we be more explicit about the use cases that is supporting this will guide our discussions such as when deciding whether a certain api or functional unit belongs in we could start by making an explicit list of use cases that warrant apis and functional units not covered by and adding that list to the charter it might be best to do this on a case by case basis if proposing a feature not explicitly sanctioned by the charter then propose a change to the charter adding the corresponding use case to the charter such that we can agree on that change in the subcommittee meeting zbraniecki | 1 |
74,893 | 7,451,427,592 | IssuesEvent | 2018-03-29 02:54:05 | mattstuhring/fused_glass | https://api.github.com/repos/mattstuhring/fused_glass | closed | Test add product component | Front End Testing | Test what does and does not work on **ProductAdd** component.
Begin by writing down action plan for each button/dropdown. | 1.0 | Test add product component - Test what does and does not work on **ProductAdd** component.
Begin by writing down action plan for each button/dropdown. | non_process | test add product component test what does and does not work on productadd component begin by writing down action plan for each button dropdown | 0 |
6,280 | 9,257,045,462 | IssuesEvent | 2019-03-17 01:20:57 | kmycode/sangokukmy | https://api.github.com/repos/kmycode/sangokukmy | closed | 密偵 | enhancement process-pending | 三国志NET KMY Versionでは、密偵システムの実装を検討しています。これは、以前あった謀略を置き換えるものです。
## 趣旨・目的
他国の都市に対して調略を実行し、自国が戦略的に優位に立てるようにする
## できること
* 武将は、他国の都市１つを指定して、「密偵」コマンド（仮）を実行することで密偵を放ちます
* 密偵は、３ヶ月の準備期間のあと、密偵コマンド実行時に指定された謀略を実行し続けます（焼き討ち、扇動の２種類）
* 武将が特定の謀略コマンドを実行し続ける必要はありません。密偵が勝手に実行します。ただし、実行する謀略を変更する場合、潜伏する都市を変更する場合は、武将がコマンドを実行する必要があります
* 謀略は、武将の知力にもよりますが、低い確率で成功し、かつわずかな結果しかもたらしません。ただし、２００年に一度くらいの確率で、大きな結果をもたらします。
* ２０００年に１回の確率で、クリティカルな効果をもたらします。（都市がほぼ廃墟になる、農民反乱が起きるなど）
* ただし、その都市に誰か敵国の武将がいる場合、確率はさらに下がります
* この確率は低すぎるように思いますが、１人の武将が実行したときの確率なので、複数の武将が一度に実行したら確率は実質的に上がります
* 毎年１月と７月に、密偵が都市情報を持ち帰ってきます
* 自分の国の都市、同盟中の国の都市に密偵を放つと、２～３００年に１度の確率で、その都市にいる敵国の密偵を始末します（始末はマップログに出ます）
* 一度自分の密偵が始末されると、再度密偵コマンドを実行する必要があります
## 制限事項
* 謀略を実行できる国は、戦争準備中・交戦中の国のみです。それ以外の国は諜報のみとなります（同盟国の場合は、自分または同盟国が戦争準備中または交戦中の密偵を排除）
* １つの都市に、同じ国の武将が３人を越えて密偵を放つことは出来ません。たとえ自国の都市であってもです。その場合、密偵コマンドは失敗します（大国と小国が戦争するときのバランス調整）
## 以前との違い
* 敵国が謀略を妨害する手段ができました（農民反乱を阻止する手段はありましたが、謀略自体を妨害する手段はこれまでありませんでした）
* 謀略が、武将がコマンドを実行しなくても実行されるようになりました。ただし、その代償として、成功確率が抑えられています
* 自分がその都市へ移動しなくても、その都市の情報を入手する手段が用意されました。スパンは長いけど定期的に情報を送ってくるので、戦略上重要なコマンドになると思います | 1.0 | 密偵 - 三国志NET KMY Versionでは、密偵システムの実装を検討しています。これは、以前あった謀略を置き換えるものです。
## 趣旨・目的
他国の都市に対して調略を実行し、自国が戦略的に優位に立てるようにする
## できること
* 武将は、他国の都市１つを指定して、「密偵」コマンド（仮）を実行することで密偵を放ちます
* 密偵は、３ヶ月の準備期間のあと、密偵コマンド実行時に指定された謀略を実行し続けます（焼き討ち、扇動の２種類）
* 武将が特定の謀略コマンドを実行し続ける必要はありません。密偵が勝手に実行します。ただし、実行する謀略を変更する場合、潜伏する都市を変更する場合は、武将がコマンドを実行する必要があります
* 謀略は、武将の知力にもよりますが、低い確率で成功し、かつわずかな結果しかもたらしません。ただし、２００年に一度くらいの確率で、大きな結果をもたらします。
* ２０００年に１回の確率で、クリティカルな効果をもたらします。（都市がほぼ廃墟になる、農民反乱が起きるなど）
* ただし、その都市に誰か敵国の武将がいる場合、確率はさらに下がります
* この確率は低すぎるように思いますが、１人の武将が実行したときの確率なので、複数の武将が一度に実行したら確率は実質的に上がります
* 毎年１月と７月に、密偵が都市情報を持ち帰ってきます
* 自分の国の都市、同盟中の国の都市に密偵を放つと、２～３００年に１度の確率で、その都市にいる敵国の密偵を始末します（始末はマップログに出ます）
* 一度自分の密偵が始末されると、再度密偵コマンドを実行する必要があります
## 制限事項
* 謀略を実行できる国は、戦争準備中・交戦中の国のみです。それ以外の国は諜報のみとなります（同盟国の場合は、自分または同盟国が戦争準備中または交戦中の密偵を排除）
* １つの都市に、同じ国の武将が３人を越えて密偵を放つことは出来ません。たとえ自国の都市であってもです。その場合、密偵コマンドは失敗します（大国と小国が戦争するときのバランス調整）
## 以前との違い
* 敵国が謀略を妨害する手段ができました（農民反乱を阻止する手段はありましたが、謀略自体を妨害する手段はこれまでありませんでした）
* 謀略が、武将がコマンドを実行しなくても実行されるようになりました。ただし、その代償として、成功確率が抑えられています
* 自分がその都市へ移動しなくても、その都市の情報を入手する手段が用意されました。スパンは長いけど定期的に情報を送ってくるので、戦略上重要なコマンドになると思います | process | 密偵 三国志net kmy versionでは、密偵システムの実装を検討しています。これは、以前あった謀略を置き換えるものです。 趣旨・目的 他国の都市に対して調略を実行し、自国が戦略的に優位に立てるようにする できること 武将は、 、「密偵」コマンド（仮）を実行することで密偵を放ちます 密偵は、 、密偵コマンド実行時に指定された謀略を実行し続けます（焼き討ち、 ） 武将が特定の謀略コマンドを実行し続ける必要はありません。密偵が勝手に実行します。ただし、実行する謀略を変更する場合、潜伏する都市を変更する場合は、武将がコマンドを実行する必要があります 謀略は、武将の知力にもよりますが、低い確率で成功し、かつわずかな結果しかもたらしません。ただし、 、大きな結果をもたらします。 、クリティカルな効果をもたらします。（都市がほぼ廃墟になる、農民反乱が起きるなど） ただし、その都市に誰か敵国の武将がいる場合、確率はさらに下がります この確率は低すぎるように思いますが、 、複数の武将が一度に実行したら確率は実質的に上がります 、密偵が都市情報を持ち帰ってきます 自分の国の都市、同盟中の国の都市に密偵を放つと、 ～ 、その都市にいる敵国の密偵を始末します（始末はマップログに出ます） 一度自分の密偵が始末されると、再度密偵コマンドを実行する必要があります 制限事項 謀略を実行できる国は、戦争準備中・交戦中の国のみです。それ以外の国は諜報のみとなります（同盟国の場合は、自分または同盟国が戦争準備中または交戦中の密偵を排除） 、 。たとえ自国の都市であってもです。その場合、密偵コマンドは失敗します（大国と小国が戦争するときのバランス調整） 以前との違い 敵国が謀略を妨害する手段ができました（農民反乱を阻止する手段はありましたが、謀略自体を妨害する手段はこれまでありませんでした） 謀略が、武将がコマンドを実行しなくても実行されるようになりました。ただし、その代償として、成功確率が抑えられています 自分がその都市へ移動しなくても、その都市の情報を入手する手段が用意されました。スパンは長いけど定期的に情報を送ってくるので、戦略上重要なコマンドになると思います | 1 |
31,653 | 11,965,011,948 | IssuesEvent | 2020-04-05 21:42:26 | Moonlet/wallet-app | https://api.github.com/repos/Moonlet/wallet-app | opened | [Critical] Remove Copy/Paste buttons from screens with sensitive data | enhancement security | For testing purposes these options are quite handy, so let's make them available for DEV_TOOLS feature.
Remove copy option from:
- create flow, mnemonic copy
- account options, reveal private key
Remove paste option from:
- recover flow, paste menmonic
| True | [Critical] Remove Copy/Paste buttons from screens with sensitive data - For testing purposes these options are quite handy, so let's make them available for DEV_TOOLS feature.
Remove copy option from:
- create flow, mnemonic copy
- account options, reveal private key
Remove paste option from:
- recover flow, paste menmonic
| non_process | remove copy paste buttons from screens with sensitive data for testing purposes these options are quite handy so let s make them available for dev tools feature remove copy option from create flow mnemonic copy account options reveal private key remove paste option from recover flow paste menmonic | 0 |
52,668 | 27,717,810,724 | IssuesEvent | 2023-03-14 18:08:32 | fako1024/slimcap | https://api.github.com/repos/fako1024/slimcap | opened | Provide direct access to IPLayer | enhancement performance | Instead of having to retrieve a full packet, then call `IPLayer()` it would be beneficial to provide direct access to the IPLayer without additional overhead / complexity. | True | Provide direct access to IPLayer - Instead of having to retrieve a full packet, then call `IPLayer()` it would be beneficial to provide direct access to the IPLayer without additional overhead / complexity. | non_process | provide direct access to iplayer instead of having to retrieve a full packet then call iplayer it would be beneficial to provide direct access to the iplayer without additional overhead complexity | 0 |
43,556 | 9,460,551,859 | IssuesEvent | 2019-04-17 11:17:49 | dOpensource/dsiprouter | https://api.github.com/repos/dOpensource/dsiprouter | closed | Unable to delete Mapped PBX(s) | 0.521 bug code committed | After a domain has been created it is not able to be deleted when you click yes to delete entry.
This bug has been recognized and a update is targeted for Friday. | 1.0 | Unable to delete Mapped PBX(s) - After a domain has been created it is not able to be deleted when you click yes to delete entry.
This bug has been recognized and a update is targeted for Friday. | non_process | unable to delete mapped pbx s after a domain has been created it is not able to be deleted when you click yes to delete entry this bug has been recognized and a update is targeted for friday | 0 |
218,893 | 16,777,691,185 | IssuesEvent | 2021-06-15 00:47:13 | anthofflab/MimiDICE2010.jl | https://api.github.com/repos/anthofflab/MimiDICE2010.jl | closed | fix `pulse_size` documentation | documentation | - fix docstrings that reference constants like `model_years`
- confirm units of `pulse_size` and explain it somewhere (we want the provided value to be interpreted as total tons of additional CO2) | 1.0 | fix `pulse_size` documentation - - fix docstrings that reference constants like `model_years`
- confirm units of `pulse_size` and explain it somewhere (we want the provided value to be interpreted as total tons of additional CO2) | non_process | fix pulse size documentation fix docstrings that reference constants like model years confirm units of pulse size and explain it somewhere we want the provided value to be interpreted as total tons of additional | 0 |
149,555 | 19,581,062,193 | IssuesEvent | 2022-01-04 21:23:42 | Tim-sandbox/ngtest | https://api.github.com/repos/Tim-sandbox/ngtest | opened | CVE-2017-18077 (High) detected in brace-expansion-1.1.6.tgz | security vulnerability | ## CVE-2017-18077 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>brace-expansion-1.1.6.tgz</b></p></summary>
<p>Brace expansion as known from sh/bash</p>
<p>Library home page: <a href="https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.6.tgz">https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.6.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/read-package-json/node_modules/glob/node_modules/minimatch/node_modules/brace-expansion/package.json,/node_modules/npm/node_modules/node-gyp/node_modules/minimatch/node_modules/brace-expansion/package.json,/node_modules/npm/node_modules/fstream-npm/node_modules/fstream-ignore/node_modules/minimatch/node_modules/brace-expansion/package.json,/node_modules/npm/node_modules/glob/node_modules/minimatch/node_modules/brace-expansion/package.json,/node_modules/npm/node_modules/init-package-json/node_modules/glob/node_modules/minimatch/node_modules/brace-expansion/package.json,/node_modules/nyc/node_modules/brace-expansion/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- read-package-json-2.0.4.tgz
- glob-6.0.4.tgz
- minimatch-3.0.3.tgz
- :x: **brace-expansion-1.1.6.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Tim-sandbox/ngtest/commit/3d9cf3172608713f73f3f479f2229bd9ff9fffa6">3d9cf3172608713f73f3f479f2229bd9ff9fffa6</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
index.js in brace-expansion before 1.1.7 is vulnerable to Regular Expression Denial of Service (ReDoS) attacks, as demonstrated by an expand argument containing many comma characters.
<p>Publish Date: 2018-01-27
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-18077>CVE-2017-18077</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-18077">https://nvd.nist.gov/vuln/detail/CVE-2017-18077</a></p>
<p>Release Date: 2018-01-27</p>
<p>Fix Resolution: 1.1.7</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"brace-expansion","packageVersion":"1.1.6","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;read-package-json:2.0.4;glob:6.0.4;minimatch:3.0.3;brace-expansion:1.1.6","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.1.7","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-18077","vulnerabilityDetails":"index.js in brace-expansion before 1.1.7 is vulnerable to Regular Expression Denial of Service (ReDoS) attacks, as demonstrated by an expand argument containing many comma characters.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-18077","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2017-18077 (High) detected in brace-expansion-1.1.6.tgz - ## CVE-2017-18077 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>brace-expansion-1.1.6.tgz</b></p></summary>
<p>Brace expansion as known from sh/bash</p>
<p>Library home page: <a href="https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.6.tgz">https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.6.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/read-package-json/node_modules/glob/node_modules/minimatch/node_modules/brace-expansion/package.json,/node_modules/npm/node_modules/node-gyp/node_modules/minimatch/node_modules/brace-expansion/package.json,/node_modules/npm/node_modules/fstream-npm/node_modules/fstream-ignore/node_modules/minimatch/node_modules/brace-expansion/package.json,/node_modules/npm/node_modules/glob/node_modules/minimatch/node_modules/brace-expansion/package.json,/node_modules/npm/node_modules/init-package-json/node_modules/glob/node_modules/minimatch/node_modules/brace-expansion/package.json,/node_modules/nyc/node_modules/brace-expansion/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- read-package-json-2.0.4.tgz
- glob-6.0.4.tgz
- minimatch-3.0.3.tgz
- :x: **brace-expansion-1.1.6.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Tim-sandbox/ngtest/commit/3d9cf3172608713f73f3f479f2229bd9ff9fffa6">3d9cf3172608713f73f3f479f2229bd9ff9fffa6</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
index.js in brace-expansion before 1.1.7 is vulnerable to Regular Expression Denial of Service (ReDoS) attacks, as demonstrated by an expand argument containing many comma characters.
<p>Publish Date: 2018-01-27
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-18077>CVE-2017-18077</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-18077">https://nvd.nist.gov/vuln/detail/CVE-2017-18077</a></p>
<p>Release Date: 2018-01-27</p>
<p>Fix Resolution: 1.1.7</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"brace-expansion","packageVersion":"1.1.6","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;read-package-json:2.0.4;glob:6.0.4;minimatch:3.0.3;brace-expansion:1.1.6","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.1.7","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-18077","vulnerabilityDetails":"index.js in brace-expansion before 1.1.7 is vulnerable to Regular Expression Denial of Service (ReDoS) attacks, as demonstrated by an expand argument containing many comma characters.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-18077","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_process | cve high detected in brace expansion tgz cve high severity vulnerability vulnerable library brace expansion tgz brace expansion as known from sh bash library home page a href path to dependency file package json path to vulnerable library node modules npm node modules read package json node modules glob node modules minimatch node modules brace expansion package json node modules npm node modules node gyp node modules minimatch node modules brace expansion package json node modules npm node modules fstream npm node modules fstream ignore node modules minimatch node modules brace expansion package json node modules npm node modules glob node modules minimatch node modules brace expansion package json node modules npm node modules init package json node modules glob node modules minimatch node modules brace expansion package json node modules nyc node modules brace expansion package json dependency hierarchy grunt npm install tgz root library npm tgz read package json tgz glob tgz minimatch tgz x brace expansion tgz vulnerable library found in head commit a href found in base branch master vulnerability details index js in brace expansion before is vulnerable to regular expression denial of service redos attacks as demonstrated by an expand argument containing many comma characters publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree grunt npm install npm read package json glob minimatch brace expansion isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails index js in brace expansion before is vulnerable to regular expression denial of service redos attacks as demonstrated by an expand argument containing many comma characters vulnerabilityurl | 0 |
77,448 | 3,506,385,682 | IssuesEvent | 2016-01-08 06:21:10 | OregonCore/OregonCore | https://api.github.com/repos/OregonCore/OregonCore | closed | Kil'Jaedan (BB #493) | migrated Priority: Medium Type: Bug | This issue was migrated from bitbucket.
**Original Reporter:** Flameshot
**Original Date:** 08.02.2014 01:11:32 GMT+0000
**Original Priority:** major
**Original Type:** bug
**Original State:** invalid
**Direct Link:** https://bitbucket.org/oregon/oregoncore/issues/493
<hr>
Hi guys, sorry for posting this on issue but i see that the forum is not working anymore. How can i summon kill'jaedan and that 3 mobs i see that hist script is not crashing server anymore.. I tried with .npc add etc but i want to add all things from there anyone have any query?. | 1.0 | Kil'Jaedan (BB #493) - This issue was migrated from bitbucket.
**Original Reporter:** Flameshot
**Original Date:** 08.02.2014 01:11:32 GMT+0000
**Original Priority:** major
**Original Type:** bug
**Original State:** invalid
**Direct Link:** https://bitbucket.org/oregon/oregoncore/issues/493
<hr>
Hi guys, sorry for posting this on issue but i see that the forum is not working anymore. How can i summon kill'jaedan and that 3 mobs i see that hist script is not crashing server anymore.. I tried with .npc add etc but i want to add all things from there anyone have any query?. | non_process | kil jaedan bb this issue was migrated from bitbucket original reporter flameshot original date gmt original priority major original type bug original state invalid direct link hi guys sorry for posting this on issue but i see that the forum is not working anymore how can i summon kill jaedan and that mobs i see that hist script is not crashing server anymore i tried with npc add etc but i want to add all things from there anyone have any query | 0 |
771,748 | 27,091,311,265 | IssuesEvent | 2023-02-14 21:19:58 | gamefreedomgit/Maelstrom | https://api.github.com/repos/gamefreedomgit/Maelstrom | closed | [Client Crash] [Dungeon] Siamat | Dungeon Client Priority: Critical Status: Confirmed | **How to reproduce:**while fighting siamat everyone's client crashed
it was during his storm which kicks players around.
(we did a second try and it didnt cause crash)
**How it should work:** it should not crash players clients
| 1.0 | [Client Crash] [Dungeon] Siamat - **How to reproduce:**while fighting siamat everyone's client crashed
it was during his storm which kicks players around.
(we did a second try and it didnt cause crash)
**How it should work:** it should not crash players clients
| non_process | siamat how to reproduce while fighting siamat everyone s client crashed it was during his storm which kicks players around we did a second try and it didnt cause crash how it should work it should not crash players clients | 0 |
3,306 | 6,401,780,167 | IssuesEvent | 2017-08-06 00:58:21 | KantaraInitiative/wg-uma | https://api.github.com/repos/KantaraInitiative/wg-uma | closed | Consider updating the IETF I-Ds when UMA2 specs are complete | process V2.0 | The current I-Ds, both pointing to V1.0.1-related Recommendations, are:
- [draft-hardjono-oauth-umacore-14](https://tools.ietf.org/html/draft-hardjono-oauth-umacore-14) (expired)
- [draft-hardjono-oauth-resource-reg-07](https://tools.ietf.org/html/draft-hardjono-oauth-resource-reg-07) (expired) | 1.0 | Consider updating the IETF I-Ds when UMA2 specs are complete - The current I-Ds, both pointing to V1.0.1-related Recommendations, are:
- [draft-hardjono-oauth-umacore-14](https://tools.ietf.org/html/draft-hardjono-oauth-umacore-14) (expired)
- [draft-hardjono-oauth-resource-reg-07](https://tools.ietf.org/html/draft-hardjono-oauth-resource-reg-07) (expired) | process | consider updating the ietf i ds when specs are complete the current i ds both pointing to related recommendations are expired expired | 1 |
46,727 | 24,692,581,680 | IssuesEvent | 2022-10-19 09:37:47 | Dystopia-user181/The-Second-Alterhistorian | https://api.github.com/repos/Dystopia-user181/The-Second-Alterhistorian | opened | Game occasionally takes up a lot of system time | performance | 
Not really sure what's going on here, but it's pretty consistent. If you record a few profiles you'll eventually stumble upon one where the game is absolutely eating up system time for whatever reason. Possibly due to using some event listener or hacky fix that isn't well optimised in JS (https://stackoverflow.com/questions/58409575/chrome-performance-analysis-with-long-system-self-time) | True | Game occasionally takes up a lot of system time - 
Not really sure what's going on here, but it's pretty consistent. If you record a few profiles you'll eventually stumble upon one where the game is absolutely eating up system time for whatever reason. Possibly due to using some event listener or hacky fix that isn't well optimised in JS (https://stackoverflow.com/questions/58409575/chrome-performance-analysis-with-long-system-self-time) | non_process | game occasionally takes up a lot of system time not really sure what s going on here but it s pretty consistent if you record a few profiles you ll eventually stumble upon one where the game is absolutely eating up system time for whatever reason possibly due to using some event listener or hacky fix that isn t well optimised in js | 0 |
21,978 | 3,930,015,287 | IssuesEvent | 2016-04-25 05:10:56 | neovim/neovim | https://api.github.com/repos/neovim/neovim | closed | os_breackcheck() crashes | tests | See https://github.com/neovim/neovim/pull/4070#discussion_r50626558
I've started investigating from a symptoms point of view. If you look at https://github.com/neovim/neovim/blob/master/test/unit/buffer_spec.lua#L96, there are 3 calls to `eq`. The third produces the crash (well, I've confirmed it actually the call to `buflist_findpath`, of course), but _only_ if the other 2 happen before. If you comment out 1 or 2 of them, everything passes (I tried all possible combinations).
Slightly below, there's https://github.com/neovim/neovim/blob/master/test/unit/buffer_spec.lua#L110. The crash happens at line 117, but _only_ if line 114 is there. If you comment out line 114 (and ofc 127 and 131 so you don't get a lua error), the test passes.
The crash does not happen at https://github.com/neovim/neovim/blob/master/test/unit/buffer_spec.lua#L134.
I've run the tests selectively using TEST_FILTER. I'll try to produce a minimal example later on. | 1.0 | os_breackcheck() crashes - See https://github.com/neovim/neovim/pull/4070#discussion_r50626558
I've started investigating from a symptoms point of view. If you look at https://github.com/neovim/neovim/blob/master/test/unit/buffer_spec.lua#L96, there are 3 calls to `eq`. The third produces the crash (well, I've confirmed it actually the call to `buflist_findpath`, of course), but _only_ if the other 2 happen before. If you comment out 1 or 2 of them, everything passes (I tried all possible combinations).
Slightly below, there's https://github.com/neovim/neovim/blob/master/test/unit/buffer_spec.lua#L110. The crash happens at line 117, but _only_ if line 114 is there. If you comment out line 114 (and ofc 127 and 131 so you don't get a lua error), the test passes.
The crash does not happen at https://github.com/neovim/neovim/blob/master/test/unit/buffer_spec.lua#L134.
I've run the tests selectively using TEST_FILTER. I'll try to produce a minimal example later on. | non_process | os breackcheck crashes see i ve started investigating from a symptoms point of view if you look at there are calls to eq the third produces the crash well i ve confirmed it actually the call to buflist findpath of course but only if the other happen before if you comment out or of them everything passes i tried all possible combinations slightly below there s the crash happens at line but only if line is there if you comment out line and ofc and so you don t get a lua error the test passes the crash does not happen at i ve run the tests selectively using test filter i ll try to produce a minimal example later on | 0 |
72,291 | 24,039,106,134 | IssuesEvent | 2022-09-15 22:33:39 | idaholab/moose | https://api.github.com/repos/idaholab/moose | closed | FVConvectionCorrelationInterface does not consider face orientation | T: defect P: normal C: Modules/Navier Stokes | ## Bug Description
This can lead to problems where the object heats the fluid instead of cooling it on certain parts (and vica-versa). This has been reported in:
https://github.com/idaholab/moose/discussions/22070
## Steps to Reproduce
Use the input files provided in:
https://github.com/idaholab/moose/discussions/22070
## Impact
Will allow reliable surface-heat-exchange process modeling. | 1.0 | FVConvectionCorrelationInterface does not consider face orientation - ## Bug Description
This can lead to problems where the object heats the fluid instead of cooling it on certain parts (and vica-versa). This has been reported in:
https://github.com/idaholab/moose/discussions/22070
## Steps to Reproduce
Use the input files provided in:
https://github.com/idaholab/moose/discussions/22070
## Impact
Will allow reliable surface-heat-exchange process modeling. | non_process | fvconvectioncorrelationinterface does not consider face orientation bug description this can lead to problems where the object heats the fluid instead of cooling it on certain parts and vica versa this has been reported in steps to reproduce use the input files provided in impact will allow reliable surface heat exchange process modeling | 0 |
12,983 | 15,356,242,561 | IssuesEvent | 2021-03-01 12:10:11 | GoogleCloudPlatform/fda-mystudies | https://api.github.com/repos/GoogleCloudPlatform/fda-mystudies | closed | In consistency in the email formate | Bug P2 Participant manager datastore Process: Fixed Process: Release 2 Process: Tested QA Process: Tested dev Unknown backend | When the email is triggered for the mobile app the org name is displayed as <Org name>
whereas when email for PM is triggered has org name and this is inconsistency when the actual org name is in place. Attaching screenshots:
Mobile :
for PM:
| 4.0 | In consistency in the email formate - When the email is triggered for the mobile app the org name is displayed as <Org name>
whereas when email for PM is triggered has org name and this is inconsistency when the actual org name is in place. Attaching screenshots:
Mobile :
for PM:
| process | in consistency in the email formate when the email is triggered for the mobile app the org name is displayed as whereas when email for pm is triggered has org name and this is inconsistency when the actual org name is in place attaching screenshots mobile for pm | 1 |
226,639 | 24,985,580,413 | IssuesEvent | 2022-11-02 14:51:11 | brave-experiments/star-randsrv | https://api.github.com/repos/brave-experiments/star-randsrv | closed | Limit number of points that server is willing to process. | security | We should implement an upper limit to protect against computational DoS. | True | Limit number of points that server is willing to process. - We should implement an upper limit to protect against computational DoS. | non_process | limit number of points that server is willing to process we should implement an upper limit to protect against computational dos | 0 |
327,308 | 9,973,829,984 | IssuesEvent | 2019-07-09 09:13:16 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.redbubble.com - see bug description | browser-firefox-mobile engine-gecko priority-normal | <!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 7.1.1; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://www.redbubble.com/shop/clothing?ref=global-nav-menu
**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android 7.1.1
**Tested Another Browser**: Yes
**Problem type**: Something else
**Description**: very very slow. click on one thing and it loads an incorrect page
**Steps to Reproduce**:
Happened immediately upon visiting the site
[](https://webcompat.com/uploads/2019/7/f953fb12-f98d-4554-9b46-c54b91568e80.jpeg)
[](https://webcompat.com/uploads/2019/7/dd206fb5-7cfb-4d2c-8329-e0734bb8424b.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>mixed active content blocked: false</li><li>image.mem.shared: true</li><li>buildID: 20190703180654</li><li>tracking content blocked: false</li><li>gfx.webrender.blob-images: true</li><li>hasTouchScreen: true</li><li>mixed passive content blocked: false</li><li>gfx.webrender.enabled: false</li><li>gfx.webrender.all: false</li><li>channel: nightly</li>
</ul>
<p>Console Messages:</p>
<pre>
[u'[JavaScript Warning: "A call to document.write() from an asynchronously-loaded external script was ignored." {file: "https://www.googleadservices.com/pagead/conversion.js" line: 49}]']
</pre>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.redbubble.com - see bug description - <!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 7.1.1; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://www.redbubble.com/shop/clothing?ref=global-nav-menu
**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android 7.1.1
**Tested Another Browser**: Yes
**Problem type**: Something else
**Description**: very very slow. click on one thing and it loads an incorrect page
**Steps to Reproduce**:
Happened immediately upon visiting the site
[](https://webcompat.com/uploads/2019/7/f953fb12-f98d-4554-9b46-c54b91568e80.jpeg)
[](https://webcompat.com/uploads/2019/7/dd206fb5-7cfb-4d2c-8329-e0734bb8424b.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>mixed active content blocked: false</li><li>image.mem.shared: true</li><li>buildID: 20190703180654</li><li>tracking content blocked: false</li><li>gfx.webrender.blob-images: true</li><li>hasTouchScreen: true</li><li>mixed passive content blocked: false</li><li>gfx.webrender.enabled: false</li><li>gfx.webrender.all: false</li><li>channel: nightly</li>
</ul>
<p>Console Messages:</p>
<pre>
[u'[JavaScript Warning: "A call to document.write() from an asynchronously-loaded external script was ignored." {file: "https://www.googleadservices.com/pagead/conversion.js" line: 49}]']
</pre>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_process | see bug description url browser version firefox mobile operating system android tested another browser yes problem type something else description very very slow click on one thing and it loads an incorrect page steps to reproduce happened immediately upon visiting the site browser configuration mixed active content blocked false image mem shared true buildid tracking content blocked false gfx webrender blob images true hastouchscreen true mixed passive content blocked false gfx webrender enabled false gfx webrender all false channel nightly console messages from with ❤️ | 0 |
39,221 | 10,316,804,992 | IssuesEvent | 2019-08-30 10:58:08 | jOOQ/jOOQ | https://api.github.com/repos/jOOQ/jOOQ | closed | Cannot build Javadoc in jOOQ-checker under Java 11 | C: Build E: All Editions P: Urgent R: Fixed T: Defect | When building jOOQ 3.12 with Java 11, the Javadoc for the `jOOQ-checker` module cannot be built:
A workaround (to be able to release 3.12 now) is to skip Javadoc generation for this module. We'll find out later what the problem is, here. | 1.0 | Cannot build Javadoc in jOOQ-checker under Java 11 - When building jOOQ 3.12 with Java 11, the Javadoc for the `jOOQ-checker` module cannot be built:
A workaround (to be able to release 3.12 now) is to skip Javadoc generation for this module. We'll find out later what the problem is, here. | non_process | cannot build javadoc in jooq checker under java when building jooq with java the javadoc for the jooq checker module cannot be built a workaround to be able to release now is to skip javadoc generation for this module we ll find out later what the problem is here | 0 |
20,366 | 27,023,284,095 | IssuesEvent | 2023-02-11 09:02:16 | googleapis/google-cloud-php-datacatalog-lineage | https://api.github.com/repos/googleapis/google-cloud-php-datacatalog-lineage | opened | Your .repo-metadata.json file has a problem 🤒 | type: process repo-metadata: lint | You have a problem with your .repo-metadata.json file:
Result of scan 📈:
* release_level must be equal to one of the allowed values in .repo-metadata.json
* api_shortname 'datacatalog-lineage' invalid in .repo-metadata.json
☝️ Once you address these problems, you can close this issue.
### Need help?
* [Schema definition](https://github.com/googleapis/repo-automation-bots/blob/main/packages/repo-metadata-lint/src/repo-metadata-schema.json): lists valid options for each field.
* [API index](https://github.com/googleapis/googleapis/blob/master/api-index-v1.json): for gRPC libraries **api_shortname** should match the subdomain of an API's **hostName**.
* Reach out to **go/github-automation** if you have any questions. | 1.0 | Your .repo-metadata.json file has a problem 🤒 - You have a problem with your .repo-metadata.json file:
Result of scan 📈:
* release_level must be equal to one of the allowed values in .repo-metadata.json
* api_shortname 'datacatalog-lineage' invalid in .repo-metadata.json
☝️ Once you address these problems, you can close this issue.
### Need help?
* [Schema definition](https://github.com/googleapis/repo-automation-bots/blob/main/packages/repo-metadata-lint/src/repo-metadata-schema.json): lists valid options for each field.
* [API index](https://github.com/googleapis/googleapis/blob/master/api-index-v1.json): for gRPC libraries **api_shortname** should match the subdomain of an API's **hostName**.
* Reach out to **go/github-automation** if you have any questions. | process | your repo metadata json file has a problem 🤒 you have a problem with your repo metadata json file result of scan 📈 release level must be equal to one of the allowed values in repo metadata json api shortname datacatalog lineage invalid in repo metadata json ☝️ once you address these problems you can close this issue need help lists valid options for each field for grpc libraries api shortname should match the subdomain of an api s hostname reach out to go github automation if you have any questions | 1 |
136,859 | 18,751,492,413 | IssuesEvent | 2021-11-05 02:58:18 | Dima2022/Resiliency-Studio | https://api.github.com/repos/Dima2022/Resiliency-Studio | opened | CVE-2019-17571 (High) detected in log4j-1.2.17.jar | security vulnerability | ## CVE-2019-17571 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>log4j-1.2.17.jar</b></p></summary>
<p>Apache Log4j 1.2</p>
<p>Path to dependency file: Resiliency-Studio/resiliency-studio-agent/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.17/log4j-1.2.17.jar,/home/wss-scanner/.m2/repository/log4j/log4j/1.2.17/log4j-1.2.17.jar,/home/wss-scanner/.m2/repository/log4j/log4j/1.2.17/log4j-1.2.17.jar</p>
<p>
Dependency Hierarchy:
- sdk-java-rest-6.2.0.4-oss.jar (Root Library)
- :x: **log4j-1.2.17.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Dima2022/Resiliency-Studio/commit/9809d9b7bfdc114eafb0a14d86667f3a76a014e8">9809d9b7bfdc114eafb0a14d86667f3a76a014e8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.
<p>Publish Date: 2019-12-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17571>CVE-2019-17571</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"log4j","packageName":"log4j","packageVersion":"1.2.17","packageFilePaths":["/resiliency-studio-agent/pom.xml","/resiliency-studio-service/pom.xml","/resiliency-studio-security/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"com.att.ajsc:sdk-java-rest:6.2.0.4-oss;log4j:log4j:1.2.17","isMinimumFixVersionAvailable":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-17571","vulnerabilityDetails":"Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17571","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2019-17571 (High) detected in log4j-1.2.17.jar - ## CVE-2019-17571 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>log4j-1.2.17.jar</b></p></summary>
<p>Apache Log4j 1.2</p>
<p>Path to dependency file: Resiliency-Studio/resiliency-studio-agent/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.17/log4j-1.2.17.jar,/home/wss-scanner/.m2/repository/log4j/log4j/1.2.17/log4j-1.2.17.jar,/home/wss-scanner/.m2/repository/log4j/log4j/1.2.17/log4j-1.2.17.jar</p>
<p>
Dependency Hierarchy:
- sdk-java-rest-6.2.0.4-oss.jar (Root Library)
- :x: **log4j-1.2.17.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Dima2022/Resiliency-Studio/commit/9809d9b7bfdc114eafb0a14d86667f3a76a014e8">9809d9b7bfdc114eafb0a14d86667f3a76a014e8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.
<p>Publish Date: 2019-12-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17571>CVE-2019-17571</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"log4j","packageName":"log4j","packageVersion":"1.2.17","packageFilePaths":["/resiliency-studio-agent/pom.xml","/resiliency-studio-service/pom.xml","/resiliency-studio-security/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"com.att.ajsc:sdk-java-rest:6.2.0.4-oss;log4j:log4j:1.2.17","isMinimumFixVersionAvailable":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-17571","vulnerabilityDetails":"Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17571","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_process | cve high detected in jar cve high severity vulnerability vulnerable library jar apache path to dependency file resiliency studio resiliency studio agent pom xml path to vulnerable library home wss scanner repository jar home wss scanner repository jar home wss scanner repository jar dependency hierarchy sdk java rest oss jar root library x jar vulnerable library found in head commit a href found in base branch master vulnerability details included in is a socketserver class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data this affects versions up to up to publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree com att ajsc sdk java rest oss isminimumfixversionavailable false basebranches vulnerabilityidentifier cve vulnerabilitydetails included in is a socketserver class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data this affects versions up to up to vulnerabilityurl | 0 |
1,317 | 3,868,890,023 | IssuesEvent | 2016-04-10 08:19:22 | nodejs/node | https://api.github.com/repos/nodejs/node | closed | child_process.spawn sh not killable | child_process doc | Comming from here:
https://github.com/keithamus/parallelshell/issues/22
(btw: Usecase for #1009)
Everytime I need to spawn a process I do it like this
```js
if (process.platform === 'win32') {
sh = 'cmd';
shFlag = '/c';
} else {
sh = 'sh';
shFlag = '-c';
}
var child = spawn(sh,[shFlag,cmd], {
cwd: process.cwd,
env: process.env,
stdio: ['pipe', process.stdout, process.stderr]
})
```
The problem: `child` is unkillable on unix.
Example in coffee-script:
```coffee
spawn = require("child_process").spawn
child = spawn "sh", ["-c", "node -e 'setTimeout(function(){},10000);'"]
child.on "close", process.exit
child.kill()
child.kill("SIGINT")
child.kill("SIGTERM")
child.kill("SIGHUP")
spawn "sh",["-c","kill -TERM "+child.pid]
spawn "sh",["-c","kill -INT "+child.pid]
spawn "sh",["-c","kill -HUP "+child.pid]
```
(on windows it works fine with sh replaced by cmd)
Even when I exit the process with `process.exit()`, the child stays alive.
Workaround I found:
```coffee
spawn = require("child_process").spawn
child = spawn "sh", ["-c", "node -e 'setTimeout(function(){},10000);'"], detached: true
child.on "close", process.exit
spawn "sh",["-c","kill -INT -"+child.pid]
```
Killing by pgid works, by pid works not. Sending ^C from console works also, I assume it uses pgid always. | 1.0 | child_process.spawn sh not killable - Comming from here:
https://github.com/keithamus/parallelshell/issues/22
(btw: Usecase for #1009)
Everytime I need to spawn a process I do it like this
```js
if (process.platform === 'win32') {
sh = 'cmd';
shFlag = '/c';
} else {
sh = 'sh';
shFlag = '-c';
}
var child = spawn(sh,[shFlag,cmd], {
cwd: process.cwd,
env: process.env,
stdio: ['pipe', process.stdout, process.stderr]
})
```
The problem: `child` is unkillable on unix.
Example in coffee-script:
```coffee
spawn = require("child_process").spawn
child = spawn "sh", ["-c", "node -e 'setTimeout(function(){},10000);'"]
child.on "close", process.exit
child.kill()
child.kill("SIGINT")
child.kill("SIGTERM")
child.kill("SIGHUP")
spawn "sh",["-c","kill -TERM "+child.pid]
spawn "sh",["-c","kill -INT "+child.pid]
spawn "sh",["-c","kill -HUP "+child.pid]
```
(on windows it works fine with sh replaced by cmd)
Even when I exit the process with `process.exit()`, the child stays alive.
Workaround I found:
```coffee
spawn = require("child_process").spawn
child = spawn "sh", ["-c", "node -e 'setTimeout(function(){},10000);'"], detached: true
child.on "close", process.exit
spawn "sh",["-c","kill -INT -"+child.pid]
```
Killing by pgid works, by pid works not. Sending ^C from console works also, I assume it uses pgid always. | process | child process spawn sh not killable comming from here btw usecase for everytime i need to spawn a process i do it like this js if process platform sh cmd shflag c else sh sh shflag c var child spawn sh cwd process cwd env process env stdio the problem child is unkillable on unix example in coffee script coffee spawn require child process spawn child spawn sh child on close process exit child kill child kill sigint child kill sigterm child kill sighup spawn sh spawn sh spawn sh on windows it works fine with sh replaced by cmd even when i exit the process with process exit the child stays alive workaround i found coffee spawn require child process spawn child spawn sh detached true child on close process exit spawn sh killing by pgid works by pid works not sending c from console works also i assume it uses pgid always | 1 |
39,104 | 8,580,118,039 | IssuesEvent | 2018-11-13 11:01:32 | galtspace/galtproject-contracts | https://api.github.com/repos/galtspace/galtproject-contracts | closed | Contract library for Bentley Ottman algorithm | codetree-epic | Sources:
- [Bentley Ottman javascript implemetation](https://github.com/ggolikov/bentley-ottman/)
- [Bentley Ottman python implemetation](https://github.com/splichte/lsi)
- [Bentley Ottman wiki](https://ru.wikipedia.org/wiki/%D0%90%D0%BB%D0%B3%D0%BE%D1%80%D0%B8%D1%82%D0%BC_%D0%91%D0%B5%D0%BD%D1%82%D0%BB%D0%B8_%E2%80%94_%D0%9E%D1%82%D1%82%D0%BC%D0%B0%D0%BD%D0%BD%D0%B0)
- [Sweep-line algorithms, an video example](https://www.youtube.com/watch?v=phrSBwaBs7o)
- [Red-black tree implementation in Solidity for Bentley Ottman implemetation](https://github.com/AtlantPlatform/rbt-solidity)
- [Weiler-Atherton video tutorial](https://www.youtube.com/watch?v=LCMyWFxeuro)
- [Weiler-Atherton rust implemetation](https://github.com/lempiy/Weiler-Atherton-Clipping)
- [Explain Weiler-Atherton polygon clipping algorithm on ques10](http://www.ques10.com/p/22055/explain-weiler-atherton-polygon-clipping-algorit-2/)
- [Student's research about Weiler-Atherton](https://www.cg.tuwien.ac.at/research/publications/2014/WINKLER-2013-AMO/WINKLER-2013-AMO-Thesis.pdf)
- [Princeton University Algorithms course](https://www.coursera.org/learn/algorithms-part1/home/welcome)
- http://www.ams.sunysb.edu/~jsbm/courses/345/13/bentley-ottmann.pdf
- https://bl.ocks.org/1wheel/464141fe9b940153e636 | 1.0 | Contract library for Bentley Ottman algorithm - Sources:
- [Bentley Ottman javascript implemetation](https://github.com/ggolikov/bentley-ottman/)
- [Bentley Ottman python implemetation](https://github.com/splichte/lsi)
- [Bentley Ottman wiki](https://ru.wikipedia.org/wiki/%D0%90%D0%BB%D0%B3%D0%BE%D1%80%D0%B8%D1%82%D0%BC_%D0%91%D0%B5%D0%BD%D1%82%D0%BB%D0%B8_%E2%80%94_%D0%9E%D1%82%D1%82%D0%BC%D0%B0%D0%BD%D0%BD%D0%B0)
- [Sweep-line algorithms, an video example](https://www.youtube.com/watch?v=phrSBwaBs7o)
- [Red-black tree implementation in Solidity for Bentley Ottman implemetation](https://github.com/AtlantPlatform/rbt-solidity)
- [Weiler-Atherton video tutorial](https://www.youtube.com/watch?v=LCMyWFxeuro)
- [Weiler-Atherton rust implemetation](https://github.com/lempiy/Weiler-Atherton-Clipping)
- [Explain Weiler-Atherton polygon clipping algorithm on ques10](http://www.ques10.com/p/22055/explain-weiler-atherton-polygon-clipping-algorit-2/)
- [Student's research about Weiler-Atherton](https://www.cg.tuwien.ac.at/research/publications/2014/WINKLER-2013-AMO/WINKLER-2013-AMO-Thesis.pdf)
- [Princeton University Algorithms course](https://www.coursera.org/learn/algorithms-part1/home/welcome)
- http://www.ams.sunysb.edu/~jsbm/courses/345/13/bentley-ottmann.pdf
- https://bl.ocks.org/1wheel/464141fe9b940153e636 | non_process | contract library for bentley ottman algorithm sources | 0 |
38,158 | 5,167,938,050 | IssuesEvent | 2017-01-17 20:10:15 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | github.com/cockroachdb/cockroach/pkg/sql: (unknown) failed under stress | Robot test-failure | SHA: https://github.com/cockroachdb/cockroach/commits/ffc0c336351e06b68e7982b5ac6008ba75aa0a66
Parameters:
```
COCKROACH_PROPOSER_EVALUATED_KV=false
TAGS=
GOFLAGS=-race
```
Stress build found a failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=119495&tab=buildLog
```
E170116 09:39:59.145495 141402 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:39:59.193560 141407 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:39:59.267833 141398 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:39:59.326207 141405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:39:59.361401 141400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:00.612949 141400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:00.673718 141405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:00.903153 141405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.003218 141461 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.107782 141407 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.209946 141409 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.307056 141400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.402830 141460 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.485420 141408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.555953 141403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.673509 141461 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.741634 141403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.817707 141404 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.915225 141405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.996606 141406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:02.040963 141400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:02.090348 141458 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:02.157079 141398 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:02.203265 141402 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:02.290084 141409 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:02.334657 141401 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:02.399310 141460 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:02.493137 141399 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:02.572317 141400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:02.623571 141459 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:04.161478 141408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:04.245207 141400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:04.536036 141400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:04.688898 141460 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:04.740872 141406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:04.834113 141402 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:04.901316 141409 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:04.968991 141458 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.044471 141409 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.122019 141458 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.208382 141405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.327259 141407 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.417570 141406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.520818 141408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.576297 141406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.652787 141460 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.731286 141406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.810859 141408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.913781 141458 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.962210 141400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:06.040294 141407 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:06.092258 141403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:06.183671 141458 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:06.242503 141399 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:06.311394 141460 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
--- PASS: TestSchemaChangeRetry (13.68s)
=== RUN TestSchemaChangeRetryOnVersionChange
E170116 09:40:07.423139 143522 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c422858000] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:07.624598 143522 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c423cdb500] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:07.739357 143522 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c4206d4c00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
E170116 09:40:10.674023 143495 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:10.770451 143400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.075663 143492 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.100779 143405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.142761 143409 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.177770 143494 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.224070 143403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.258176 143492 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.294062 143405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.349841 143409 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.428575 143494 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.493958 143403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.581846 143407 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.637728 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.689410 143409 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.742921 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.780510 143492 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.824144 143405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.877555 143400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.919056 143491 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.981409 143406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.019240 143494 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.058346 143491 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.085116 143400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.122778 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.157218 143401 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.195474 143493 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.241976 143403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.276339 143406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.320796 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.346919 143401 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.403950 143495 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.462695 143403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.520574 143406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.571377 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.621927 143401 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.661721 143406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.754149 143402 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.792168 143405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.915683 143407 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.970915 143491 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:13.001617 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:13.064013 143494 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:13.116015 143400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:13.165718 143490 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:13.210850 143404 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:13.244447 143409 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:13.280553 143492 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:13.306571 143406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:13.398187 143494 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:14.567453 143495 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:14.637468 143403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.052339 143406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.200599 143409 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.284223 143403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.344751 143490 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.418787 143493 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.519289 143490 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.582154 143493 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.695523 143402 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.763052 143400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.808326 143495 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.876474 143406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.965468 143402 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.040108 143492 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.118538 143490 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.189392 143401 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.262106 143493 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.327904 143403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.404620 143495 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.474136 143405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.556436 143495 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.644294 143405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.758971 143491 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.882718 143494 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:18.280362 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:18.326701 143403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:18.704800 143494 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:18.774463 143409 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:18.848708 143490 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:18.887900 143493 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:18.933384 143402 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:18.979846 143407 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.023913 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.084685 143495 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.132289 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.177585 143400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.219313 143407 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.310699 143404 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.417175 143403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.487409 143490 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.561744 143494 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.618409 143490 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.669523 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.711822 143492 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.803132 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.889641 143406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.949746 143405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:20.009873 143407 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:20.127574 143495 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
--- PASS: TestSchemaChangeRetryOnVersionChange (13.94s)
=== RUN TestSchemaChangePurgeFailure
E170116 09:40:21.410222 145277 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c42487e900] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:21.521994 145277 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c422234600] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:21.657085 145277 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c42272e000] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestSchemaChangePurgeFailure (2.78s)
=== RUN TestSchemaChangeReverseMutations
E170116 09:40:24.351305 146487 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c422141200] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:24.484823 146487 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c422270f00] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:24.894900 146487 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c42071f200] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestSchemaChangeReverseMutations (5.62s)
=== RUN TestParseSentinelValueWithNewColumnInSentinelFamily
E170116 09:40:29.814227 147746 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c42487e000] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:29.907739 147746 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c4232f0900] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:29.973627 147746 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c421434c00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestParseSentinelValueWithNewColumnInSentinelFamily (1.54s)
=== RUN TestUpdateDuringColumnBackfill
E170116 09:40:31.594395 147936 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c421434000] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:31.702807 147936 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c422365200] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:31.840194 147936 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c421435b00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestUpdateDuringColumnBackfill (2.51s)
=== RUN TestSessionFinishRollsBackTxn
E170116 09:40:33.875334 148822 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c422364300] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:34.011622 148822 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c422fe1800] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:34.108483 148822 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c421a1e000] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
=== RUN TestSessionFinishRollsBackTxn/Open
=== RUN TestSessionFinishRollsBackTxn/RestartWait
=== RUN TestSessionFinishRollsBackTxn/CommitWait
--- PASS: TestSessionFinishRollsBackTxn (1.86s)
--- PASS: TestSessionFinishRollsBackTxn/Open (0.25s)
--- PASS: TestSessionFinishRollsBackTxn/RestartWait (0.36s)
--- PASS: TestSessionFinishRollsBackTxn/CommitWait (0.09s)
=== RUN TestShowCreateTable
E170116 09:40:35.782269 149291 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c422141500] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:35.948575 149291 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c422364f00] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:36.080921 149291 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c421a1e900] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestShowCreateTable (6.12s)
=== RUN TestShowCreateView
E170116 09:40:42.168265 150806 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c422a78600] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:42.286854 150806 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c423ea8f00] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:42.448300 150806 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c42487fb00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestShowCreateView (9.77s)
=== RUN TestOrderByRandom
E170116 09:40:51.609102 153730 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c42116c000] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:51.784818 153730 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c4237e8900] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:51.859114 153730 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c420db2c00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestOrderByRandom (0.72s)
=== RUN TestSplitAt
E170116 09:40:52.392880 153909 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c420aee300] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:52.488387 153909 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c423cdaf00] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:52.827389 153909 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c42218fb00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestSplitAt (2.06s)
=== RUN TestSplitOnTableBoundaries
E170116 09:40:54.388224 154568 storage/queue.go:599 [replicate,n1,s1,r1/1:/{Min-Table/11},@c42487e000] range requires a replication change, but lacks a quorum of live replicas (0/1)
E170116 09:40:54.398944 154567 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c42487e000] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:54.526146 154567 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c42071f500] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:54.638867 154567 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c4232f0600] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestSplitOnTableBoundaries (1.91s)
=== RUN TestInitialKeys
E170116 09:40:56.084019 154827 sql/sqlbase/metadata.go:99 adding descriptor with duplicate ID: name:"x" id:11 parent_id:1 version:1 up_version:false modification_time:<wall_time:0 logical:0 > columns:<name:"val" id:1 type:<kind:INT width:0 precision:0 > nullable:false hidden:false > next_column_id:2 families:<name:"primary" id:0 column_names:"val" column_ids:1 default_column_id:0 > next_family_id:1 primary_index:<name:"primary" id:1 unique:true column_names:"val" column_directions:ASC column_ids:1 foreign_key:<table:0 index:0 name:"" validity:Validated > interleave:<> > next_index_id:2 privileges:<users:<user:"root" privileges:2 > > next_mutation_id:1 format_version:InterleavedFormatVersion state:PUBLIC view_query:""
--- PASS: TestInitialKeys (0.04s)
=== RUN TestSystemTableLiterals
--- PASS: TestSystemTableLiterals (0.01s)
=== RUN TestSplitAtTableBoundary
E170116 09:40:56.556946 154785 storage/queue.go:610 [replicate,n1,s1,r1/1:/{Min-Table/11},@c420aee000] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.567725 154784 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c420aee000] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:56.569828 155059 storage/queue.go:610 [replicate,n1,s1,r1/1:/{Min-Table/11},@c420aee000] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.709654 154784 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c42218f200] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:56.731853 155059 storage/queue.go:610 [replicate,n1,s1,r1/1:/{Min-Table/11},@c420aee000] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.732168 154785 storage/queue.go:610 [replicate,n1,s1,r2/1:/Table/1{1-2},@c42218f200] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.832831 155059 storage/queue.go:610 [replicate,n1,s1,r1/1:/{Min-Table/11},@c420aee000] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.834357 155059 storage/queue.go:610 [replicate,n1,s1,r2/1:/Table/1{1-2},@c42218f200] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.843990 154784 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c42272e000] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
E170116 09:40:56.844231 154785 storage/queue.go:610 [replicate,n1,s1,r3/1:/Table/1{2-3},@c42272e000] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.946946 154785 storage/queue.go:610 [replicate,n1,s1,r4/1:/Table/1{3-4},@c421b26300] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.952628 154785 storage/queue.go:610 [replicate,n1,s1,r5/1:/{Table/14-Max},@c422141800] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.952874 155059 storage/queue.go:610 [replicate,n1,s1,r1/1:/{Min-Table/11},@c420aee000] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.953527 155059 storage/queue.go:610 [replicate,n1,s1,r2/1:/Table/1{1-2},@c42218f200] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.954056 155059 storage/queue.go:610 [replicate,n1,s1,r3/1:/Table/1{2-3},@c42272e000] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:57.203457 155059 storage/queue.go:610 [replicate,n1,s1,r4/1:/Table/1{3-4},@c421b26300] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:57.204149 155059 storage/queue.go:610 [replicate,n1,s1,r5/1:/{Table/14-Max},@c422141800] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:57.209820 155059 storage/queue.go:610 [replicate,n1,s1,r1/1:/{Min-Table/11},@c420aee000] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:57.210741 155059 storage/queue.go:610 [replicate,n1,s1,r2/1:/Table/1{1-2},@c42218f200] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:57.214522 155059 storage/queue.go:610 [replicate,n1,s1,r3/1:/Table/1{2-3},@c42272e000] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
--- PASS: TestSplitAtTableBoundary (3.30s)
=== RUN TestExplainTrace
E170116 09:40:59.708426 155808 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c42299cc00] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:59.849187 155808 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c422ef3800] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:59.955134 155808 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c421b37b00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestExplainTrace (1.03s)
=== RUN TestTxnAutoRetry
E170116 09:41:00.657097 156291 storage/queue.go:599 [replicate,n1,s1,r1/1:/{Min-Table/11},@c422234000] range requires a replication change, but lacks a quorum of live replicas (0/1)
E170116 09:41:00.657883 156290 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c422234000] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:00.731496 156290 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c42071f200] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:00.787712 156290 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c422270f00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestTxnAutoRetry (3.15s)
=== RUN TestAbortedTxnOnlyRetriedOnce
E170116 09:41:04.124136 156802 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c421435200] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:04.129635 156718 storage/consistency_queue.go:89 [replica consistency checker,n1,s1,r1/1:/{Min-Table/11},@c421435200] key range /Min-/Max outside of bounds of range /Min-/Table/11
E170116 09:41:04.332379 156802 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c42230f800] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:04.503696 156802 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c422364900] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestAbortedTxnOnlyRetriedOnce (1.62s)
=== RUN TestTxnUserRestart
E170116 09:41:05.459142 157197 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c4208e9200] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:05.591011 157197 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c4215ba900] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:05.702950 157197 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c420481b00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestTxnUserRestart (1.60s)
=== RUN TestCommitWaitState
E170116 09:41:06.998791 157618 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c422140900] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:07.067912 157618 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c422fe1800] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:07.164558 157618 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c4204ecc00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
E170116 09:41:07.596728 157618 storage/queue.go:599 [split,n1,s1,r6/1:/{Table/50-Max},@c42071fb00] unable to split [n1,s1,r6/1:/{Table/50-Max}] at key "/Table/51/0": storage/replica_command.go:2433: split at key /Table/51 failed: result is ambiguous (server shutdown)
--- PASS: TestCommitWaitState (0.81s)
=== RUN TestErrorOnCommitFinalizesTxn
E170116 09:41:07.926381 157830 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c4206d4900] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:08.003486 157830 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c42083f500] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:08.174731 157830 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c4218fcf00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
E170116 09:41:08.814195 158088 internal/client/txn.go:333 [client=127.0.0.1:51054,user=root,n1] failure aborting transaction: internal/client/txn.go:643: attempting to use transaction with wrong status or finalized: ABORTED; abort caused by: txn aborted "sql/executor.go:588 sql txn" id=9c265c6d key=/Table/51/1/0/0 rw=true pri=46.56612871 iso=SERIALIZABLE stat=ABORTED epo=0 ts=1484559668.755082750,1 orig=1484559668.497669082,0 max=1484559668.997669082,0 wto=false rop=false
--- PASS: TestErrorOnCommitFinalizesTxn (1.34s)
=== RUN TestRollbackToSavepointStatement
E170116 09:41:09.150365 158076 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c422fe0600] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:09.355114 158076 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c422fe1500] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:09.467409 158076 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c423535b00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestRollbackToSavepointStatement (0.78s)
=== RUN TestNonRetriableError
E170116 09:41:10.135841 158319 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c42071fb00] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:10.282604 158319 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c422234600] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:10.436914 158319 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c422141b00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestNonRetriableError (1.30s)
=== RUN TestRollbackInRestartWait
E170116 09:41:11.616658 158840 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c42340e300] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:11.783525 158840 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c422365800] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:11.915357 158840 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c422fe1200] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestRollbackInRestartWait (1.55s)
=== RUN TestNonRetryableError
E170116 09:41:12.951546 159347 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c4218fcc00] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:13.164127 159347 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c4232f0900] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:13.304310 159347 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c4206d4900] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
E170116 09:41:13.867800 159347 internal/client/txn.go:333 [split,n1,s1,r6/1:/{Table/50-Max},@c4211c4300] failure aborting transaction: writing transaction timed out or ran on multiple coordinators; abort caused by: node unavailable; try another peer
E170116 09:41:13.868218 159347 storage/queue.go:599 [split,n1,s1,r6/1:/{Table/50-Max},@c4211c4300] unable to split [n1,s1,r6/1:/{Table/50-Max}] at key "/Table/51/0": storage/replica_command.go:2433: split at key /Table/51 failed: node unavailable; try another peer
--- PASS: TestNonRetryableError (1.30s)
=== RUN TestNonRetryableErrorOnCommit
E170116 09:41:14.203608 159695 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c42340fb00] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:14.265986 159695 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c421434c00] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:14.363371 159695 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c42487ec00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
E170116 09:41:14.602279 159831 internal/client/txn.go:333 [client=127.0.0.1:50583,user=root,n1] failure aborting transaction: testError; abort caused by: testError
--- PASS: TestNonRetryableErrorOnCommit (0.74s)
=== RUN TestReacquireLeaseOnRestart
E170116 09:41:14.863869 159898 storage/queue.go:599 [replicate,n1,s1,r1/1:/{Min-Table/11},@c4204ec300] range requires a replication change, but lacks a quorum of live replicas (0/1)
E170116 09:41:14.865023 159897 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c4204ec300] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:15.053727 159897 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c4221c6900] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:15.158709 159897 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c422235800] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestReacquireLeaseOnRestart (1.18s)
PASS
Found 1 data race(s)
ERROR: exit status 66
make: *** [stress] Error 1
7 runs completed, 1 failures, over 10m30s
FAIL
Makefile:147: recipe for target 'stress' failed
``` | 1.0 | github.com/cockroachdb/cockroach/pkg/sql: (unknown) failed under stress - SHA: https://github.com/cockroachdb/cockroach/commits/ffc0c336351e06b68e7982b5ac6008ba75aa0a66
Parameters:
```
COCKROACH_PROPOSER_EVALUATED_KV=false
TAGS=
GOFLAGS=-race
```
Stress build found a failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=119495&tab=buildLog
```
E170116 09:39:59.145495 141402 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:39:59.193560 141407 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:39:59.267833 141398 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:39:59.326207 141405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:39:59.361401 141400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:00.612949 141400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:00.673718 141405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:00.903153 141405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.003218 141461 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.107782 141407 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.209946 141409 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.307056 141400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.402830 141460 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.485420 141408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.555953 141403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.673509 141461 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.741634 141403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.817707 141404 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.915225 141405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:01.996606 141406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:02.040963 141400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:02.090348 141458 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:02.157079 141398 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:02.203265 141402 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:02.290084 141409 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:02.334657 141401 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:02.399310 141460 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:02.493137 141399 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:02.572317 141400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:02.623571 141459 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:04.161478 141408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:04.245207 141400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:04.536036 141400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:04.688898 141460 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:04.740872 141406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:04.834113 141402 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:04.901316 141409 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:04.968991 141458 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.044471 141409 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.122019 141458 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.208382 141405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.327259 141407 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.417570 141406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.520818 141408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.576297 141406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.652787 141460 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.731286 141406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.810859 141408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.913781 141458 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:05.962210 141400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:06.040294 141407 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:06.092258 141403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:06.183671 141458 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:06.242503 141399 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:06.311394 141460 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c42218e900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
--- PASS: TestSchemaChangeRetry (13.68s)
=== RUN TestSchemaChangeRetryOnVersionChange
E170116 09:40:07.423139 143522 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c422858000] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:07.624598 143522 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c423cdb500] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:07.739357 143522 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c4206d4c00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
E170116 09:40:10.674023 143495 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:10.770451 143400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.075663 143492 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.100779 143405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.142761 143409 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.177770 143494 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.224070 143403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.258176 143492 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.294062 143405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.349841 143409 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.428575 143494 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.493958 143403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.581846 143407 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.637728 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.689410 143409 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.742921 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.780510 143492 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.824144 143405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.877555 143400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.919056 143491 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:11.981409 143406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.019240 143494 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.058346 143491 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.085116 143400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.122778 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.157218 143401 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.195474 143493 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.241976 143403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.276339 143406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.320796 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.346919 143401 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.403950 143495 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.462695 143403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.520574 143406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.571377 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.621927 143401 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.661721 143406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.754149 143402 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.792168 143405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.915683 143407 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:12.970915 143491 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:13.001617 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:13.064013 143494 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:13.116015 143400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:13.165718 143490 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:13.210850 143404 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:13.244447 143409 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:13.280553 143492 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:13.306571 143406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:13.398187 143494 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:14.567453 143495 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:14.637468 143403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.052339 143406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.200599 143409 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.284223 143403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.344751 143490 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.418787 143493 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.519289 143490 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.582154 143493 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.695523 143402 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.763052 143400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.808326 143495 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.876474 143406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:15.965468 143402 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.040108 143492 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.118538 143490 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.189392 143401 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.262106 143493 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.327904 143403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.404620 143495 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.474136 143405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.556436 143495 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.644294 143405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.758971 143491 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:16.882718 143494 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:18.280362 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:18.326701 143403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:18.704800 143494 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:18.774463 143409 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:18.848708 143490 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:18.887900 143493 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:18.933384 143402 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:18.979846 143407 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.023913 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.084685 143495 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.132289 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.177585 143400 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.219313 143407 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.310699 143404 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.417175 143403 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.487409 143490 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.561744 143494 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.618409 143490 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.669523 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.711822 143492 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.803132 143408 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.889641 143406 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:19.949746 143405 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:20.009873 143407 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
E170116 09:40:20.127574 143495 storage/replica_command.go:866 [n1,s1,r7/1:/{Table/51-Max},@c420480900] System configuration span was modified, but the modification trigger is executing on a non-system range. Configuration changes will not be gossiped.
--- PASS: TestSchemaChangeRetryOnVersionChange (13.94s)
=== RUN TestSchemaChangePurgeFailure
E170116 09:40:21.410222 145277 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c42487e900] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:21.521994 145277 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c422234600] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:21.657085 145277 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c42272e000] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestSchemaChangePurgeFailure (2.78s)
=== RUN TestSchemaChangeReverseMutations
E170116 09:40:24.351305 146487 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c422141200] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:24.484823 146487 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c422270f00] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:24.894900 146487 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c42071f200] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestSchemaChangeReverseMutations (5.62s)
=== RUN TestParseSentinelValueWithNewColumnInSentinelFamily
E170116 09:40:29.814227 147746 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c42487e000] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:29.907739 147746 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c4232f0900] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:29.973627 147746 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c421434c00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestParseSentinelValueWithNewColumnInSentinelFamily (1.54s)
=== RUN TestUpdateDuringColumnBackfill
E170116 09:40:31.594395 147936 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c421434000] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:31.702807 147936 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c422365200] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:31.840194 147936 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c421435b00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestUpdateDuringColumnBackfill (2.51s)
=== RUN TestSessionFinishRollsBackTxn
E170116 09:40:33.875334 148822 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c422364300] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:34.011622 148822 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c422fe1800] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:34.108483 148822 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c421a1e000] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
=== RUN TestSessionFinishRollsBackTxn/Open
=== RUN TestSessionFinishRollsBackTxn/RestartWait
=== RUN TestSessionFinishRollsBackTxn/CommitWait
--- PASS: TestSessionFinishRollsBackTxn (1.86s)
--- PASS: TestSessionFinishRollsBackTxn/Open (0.25s)
--- PASS: TestSessionFinishRollsBackTxn/RestartWait (0.36s)
--- PASS: TestSessionFinishRollsBackTxn/CommitWait (0.09s)
=== RUN TestShowCreateTable
E170116 09:40:35.782269 149291 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c422141500] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:35.948575 149291 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c422364f00] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:36.080921 149291 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c421a1e900] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestShowCreateTable (6.12s)
=== RUN TestShowCreateView
E170116 09:40:42.168265 150806 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c422a78600] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:42.286854 150806 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c423ea8f00] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:42.448300 150806 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c42487fb00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestShowCreateView (9.77s)
=== RUN TestOrderByRandom
E170116 09:40:51.609102 153730 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c42116c000] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:51.784818 153730 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c4237e8900] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:51.859114 153730 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c420db2c00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestOrderByRandom (0.72s)
=== RUN TestSplitAt
E170116 09:40:52.392880 153909 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c420aee300] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:52.488387 153909 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c423cdaf00] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:52.827389 153909 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c42218fb00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestSplitAt (2.06s)
=== RUN TestSplitOnTableBoundaries
E170116 09:40:54.388224 154568 storage/queue.go:599 [replicate,n1,s1,r1/1:/{Min-Table/11},@c42487e000] range requires a replication change, but lacks a quorum of live replicas (0/1)
E170116 09:40:54.398944 154567 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c42487e000] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:54.526146 154567 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c42071f500] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:54.638867 154567 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c4232f0600] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestSplitOnTableBoundaries (1.91s)
=== RUN TestInitialKeys
E170116 09:40:56.084019 154827 sql/sqlbase/metadata.go:99 adding descriptor with duplicate ID: name:"x" id:11 parent_id:1 version:1 up_version:false modification_time:<wall_time:0 logical:0 > columns:<name:"val" id:1 type:<kind:INT width:0 precision:0 > nullable:false hidden:false > next_column_id:2 families:<name:"primary" id:0 column_names:"val" column_ids:1 default_column_id:0 > next_family_id:1 primary_index:<name:"primary" id:1 unique:true column_names:"val" column_directions:ASC column_ids:1 foreign_key:<table:0 index:0 name:"" validity:Validated > interleave:<> > next_index_id:2 privileges:<users:<user:"root" privileges:2 > > next_mutation_id:1 format_version:InterleavedFormatVersion state:PUBLIC view_query:""
--- PASS: TestInitialKeys (0.04s)
=== RUN TestSystemTableLiterals
--- PASS: TestSystemTableLiterals (0.01s)
=== RUN TestSplitAtTableBoundary
E170116 09:40:56.556946 154785 storage/queue.go:610 [replicate,n1,s1,r1/1:/{Min-Table/11},@c420aee000] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.567725 154784 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c420aee000] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:56.569828 155059 storage/queue.go:610 [replicate,n1,s1,r1/1:/{Min-Table/11},@c420aee000] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.709654 154784 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c42218f200] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:56.731853 155059 storage/queue.go:610 [replicate,n1,s1,r1/1:/{Min-Table/11},@c420aee000] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.732168 154785 storage/queue.go:610 [replicate,n1,s1,r2/1:/Table/1{1-2},@c42218f200] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.832831 155059 storage/queue.go:610 [replicate,n1,s1,r1/1:/{Min-Table/11},@c420aee000] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.834357 155059 storage/queue.go:610 [replicate,n1,s1,r2/1:/Table/1{1-2},@c42218f200] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.843990 154784 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c42272e000] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
E170116 09:40:56.844231 154785 storage/queue.go:610 [replicate,n1,s1,r3/1:/Table/1{2-3},@c42272e000] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.946946 154785 storage/queue.go:610 [replicate,n1,s1,r4/1:/Table/1{3-4},@c421b26300] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.952628 154785 storage/queue.go:610 [replicate,n1,s1,r5/1:/{Table/14-Max},@c422141800] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.952874 155059 storage/queue.go:610 [replicate,n1,s1,r1/1:/{Min-Table/11},@c420aee000] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.953527 155059 storage/queue.go:610 [replicate,n1,s1,r2/1:/Table/1{1-2},@c42218f200] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:56.954056 155059 storage/queue.go:610 [replicate,n1,s1,r3/1:/Table/1{2-3},@c42272e000] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:57.203457 155059 storage/queue.go:610 [replicate,n1,s1,r4/1:/Table/1{3-4},@c421b26300] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:57.204149 155059 storage/queue.go:610 [replicate,n1,s1,r5/1:/{Table/14-Max},@c422141800] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:57.209820 155059 storage/queue.go:610 [replicate,n1,s1,r1/1:/{Min-Table/11},@c420aee000] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:57.210741 155059 storage/queue.go:610 [replicate,n1,s1,r2/1:/Table/1{1-2},@c42218f200] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
E170116 09:40:57.214522 155059 storage/queue.go:610 [replicate,n1,s1,r3/1:/Table/1{2-3},@c42272e000] purgatory: 0 of 1 store with an attribute matching []; likely not enough nodes in cluster
--- PASS: TestSplitAtTableBoundary (3.30s)
=== RUN TestExplainTrace
E170116 09:40:59.708426 155808 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c42299cc00] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:40:59.849187 155808 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c422ef3800] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:40:59.955134 155808 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c421b37b00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestExplainTrace (1.03s)
=== RUN TestTxnAutoRetry
E170116 09:41:00.657097 156291 storage/queue.go:599 [replicate,n1,s1,r1/1:/{Min-Table/11},@c422234000] range requires a replication change, but lacks a quorum of live replicas (0/1)
E170116 09:41:00.657883 156290 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c422234000] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:00.731496 156290 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c42071f200] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:00.787712 156290 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c422270f00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestTxnAutoRetry (3.15s)
=== RUN TestAbortedTxnOnlyRetriedOnce
E170116 09:41:04.124136 156802 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c421435200] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:04.129635 156718 storage/consistency_queue.go:89 [replica consistency checker,n1,s1,r1/1:/{Min-Table/11},@c421435200] key range /Min-/Max outside of bounds of range /Min-/Table/11
E170116 09:41:04.332379 156802 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c42230f800] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:04.503696 156802 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c422364900] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestAbortedTxnOnlyRetriedOnce (1.62s)
=== RUN TestTxnUserRestart
E170116 09:41:05.459142 157197 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c4208e9200] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:05.591011 157197 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c4215ba900] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:05.702950 157197 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c420481b00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestTxnUserRestart (1.60s)
=== RUN TestCommitWaitState
E170116 09:41:06.998791 157618 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c422140900] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:07.067912 157618 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c422fe1800] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:07.164558 157618 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c4204ecc00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
E170116 09:41:07.596728 157618 storage/queue.go:599 [split,n1,s1,r6/1:/{Table/50-Max},@c42071fb00] unable to split [n1,s1,r6/1:/{Table/50-Max}] at key "/Table/51/0": storage/replica_command.go:2433: split at key /Table/51 failed: result is ambiguous (server shutdown)
--- PASS: TestCommitWaitState (0.81s)
=== RUN TestErrorOnCommitFinalizesTxn
E170116 09:41:07.926381 157830 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c4206d4900] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:08.003486 157830 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c42083f500] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:08.174731 157830 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c4218fcf00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
E170116 09:41:08.814195 158088 internal/client/txn.go:333 [client=127.0.0.1:51054,user=root,n1] failure aborting transaction: internal/client/txn.go:643: attempting to use transaction with wrong status or finalized: ABORTED; abort caused by: txn aborted "sql/executor.go:588 sql txn" id=9c265c6d key=/Table/51/1/0/0 rw=true pri=46.56612871 iso=SERIALIZABLE stat=ABORTED epo=0 ts=1484559668.755082750,1 orig=1484559668.497669082,0 max=1484559668.997669082,0 wto=false rop=false
--- PASS: TestErrorOnCommitFinalizesTxn (1.34s)
=== RUN TestRollbackToSavepointStatement
E170116 09:41:09.150365 158076 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c422fe0600] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:09.355114 158076 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c422fe1500] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:09.467409 158076 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c423535b00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestRollbackToSavepointStatement (0.78s)
=== RUN TestNonRetriableError
E170116 09:41:10.135841 158319 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c42071fb00] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:10.282604 158319 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c422234600] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:10.436914 158319 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c422141b00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestNonRetriableError (1.30s)
=== RUN TestRollbackInRestartWait
E170116 09:41:11.616658 158840 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c42340e300] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:11.783525 158840 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c422365800] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:11.915357 158840 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c422fe1200] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestRollbackInRestartWait (1.55s)
=== RUN TestNonRetryableError
E170116 09:41:12.951546 159347 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c4218fcc00] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:13.164127 159347 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c4232f0900] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:13.304310 159347 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c4206d4900] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
E170116 09:41:13.867800 159347 internal/client/txn.go:333 [split,n1,s1,r6/1:/{Table/50-Max},@c4211c4300] failure aborting transaction: writing transaction timed out or ran on multiple coordinators; abort caused by: node unavailable; try another peer
E170116 09:41:13.868218 159347 storage/queue.go:599 [split,n1,s1,r6/1:/{Table/50-Max},@c4211c4300] unable to split [n1,s1,r6/1:/{Table/50-Max}] at key "/Table/51/0": storage/replica_command.go:2433: split at key /Table/51 failed: node unavailable; try another peer
--- PASS: TestNonRetryableError (1.30s)
=== RUN TestNonRetryableErrorOnCommit
E170116 09:41:14.203608 159695 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c42340fb00] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:14.265986 159695 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c421434c00] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:14.363371 159695 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c42487ec00] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
E170116 09:41:14.602279 159831 internal/client/txn.go:333 [client=127.0.0.1:50583,user=root,n1] failure aborting transaction: testError; abort caused by: testError
--- PASS: TestNonRetryableErrorOnCommit (0.74s)
=== RUN TestReacquireLeaseOnRestart
E170116 09:41:14.863869 159898 storage/queue.go:599 [replicate,n1,s1,r1/1:/{Min-Table/11},@c4204ec300] range requires a replication change, but lacks a quorum of live replicas (0/1)
E170116 09:41:14.865023 159897 storage/queue.go:599 [split,n1,s1,r1/1:/{Min-Table/11},@c4204ec300] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170116 09:41:15.053727 159897 storage/queue.go:599 [split,n1,s1,r2/1:/Table/1{1-2},@c4221c6900] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170116 09:41:15.158709 159897 storage/queue.go:599 [split,n1,s1,r3/1:/Table/1{2-3},@c422235800] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
--- PASS: TestReacquireLeaseOnRestart (1.18s)
PASS
Found 1 data race(s)
ERROR: exit status 66
make: *** [stress] Error 1
7 runs completed, 1 failures, over 10m30s
FAIL
Makefile:147: recipe for target 'stress' failed
``` | non_process | github com cockroachdb cockroach pkg sql unknown failed under stress sha parameters cockroach proposer evaluated kv false tags goflags race stress build found a failed test storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped pass testschemachangeretry run testschemachangeretryonversionchange storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped storage replica command go system configuration span was modified but the modification trigger is executing on a non system range configuration changes will not be gossiped pass testschemachangeretryonversionchange run testschemachangepurgefailure storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max pass testschemachangepurgefailure run testschemachangereversemutations storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max pass testschemachangereversemutations run testparsesentinelvaluewithnewcolumninsentinelfamily storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max pass testparsesentinelvaluewithnewcolumninsentinelfamily run testupdateduringcolumnbackfill storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max pass testupdateduringcolumnbackfill run testsessionfinishrollsbacktxn storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max run testsessionfinishrollsbacktxn open run testsessionfinishrollsbacktxn restartwait run testsessionfinishrollsbacktxn commitwait pass testsessionfinishrollsbacktxn pass testsessionfinishrollsbacktxn open pass testsessionfinishrollsbacktxn restartwait pass testsessionfinishrollsbacktxn commitwait run testshowcreatetable storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max pass testshowcreatetable run testshowcreateview storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max pass testshowcreateview run testorderbyrandom storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max pass testorderbyrandom run testsplitat storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max pass testsplitat run testsplitontableboundaries storage queue go range requires a replication change but lacks a quorum of live replicas storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max pass testsplitontableboundaries run testinitialkeys sql sqlbase metadata go adding descriptor with duplicate id name x id parent id version up version false modification time columns nullable false hidden false next column id families next family id primary index interleave next index id privileges next mutation id format version interleavedformatversion state public view query pass testinitialkeys run testsystemtableliterals pass testsystemtableliterals run testsplitattableboundary storage queue go purgatory of store with an attribute matching likely not enough nodes in cluster storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go purgatory of store with an attribute matching likely not enough nodes in cluster storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go purgatory of store with an attribute matching likely not enough nodes in cluster storage queue go purgatory of store with an attribute matching likely not enough nodes in cluster storage queue go purgatory of store with an attribute matching likely not enough nodes in cluster storage queue go purgatory of store with an attribute matching likely not enough nodes in cluster storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go purgatory of store with an attribute matching likely not enough nodes in cluster storage queue go purgatory of store with an attribute matching likely not enough nodes in cluster storage queue go purgatory of store with an attribute matching likely not enough nodes in cluster storage queue go purgatory of store with an attribute matching likely not enough nodes in cluster storage queue go purgatory of store with an attribute matching likely not enough nodes in cluster storage queue go purgatory of store with an attribute matching likely not enough nodes in cluster storage queue go purgatory of store with an attribute matching likely not enough nodes in cluster storage queue go purgatory of store with an attribute matching likely not enough nodes in cluster storage queue go purgatory of store with an attribute matching likely not enough nodes in cluster storage queue go purgatory of store with an attribute matching likely not enough nodes in cluster storage queue go purgatory of store with an attribute matching likely not enough nodes in cluster pass testsplitattableboundary run testexplaintrace storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max pass testexplaintrace run testtxnautoretry storage queue go range requires a replication change but lacks a quorum of live replicas storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max pass testtxnautoretry run testabortedtxnonlyretriedonce storage queue go unable to split at key table key range table table outside of bounds of range min max storage consistency queue go key range min max outside of bounds of range min table storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max pass testabortedtxnonlyretriedonce run testtxnuserrestart storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max pass testtxnuserrestart run testcommitwaitstate storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table storage replica command go split at key table failed result is ambiguous server shutdown pass testcommitwaitstate run testerroroncommitfinalizestxn storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max internal client txn go failure aborting transaction internal client txn go attempting to use transaction with wrong status or finalized aborted abort caused by txn aborted sql executor go sql txn id key table rw true pri iso serializable stat aborted epo ts orig max wto false rop false pass testerroroncommitfinalizestxn run testrollbacktosavepointstatement storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max pass testrollbacktosavepointstatement run testnonretriableerror storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max pass testnonretriableerror run testrollbackinrestartwait storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max pass testrollbackinrestartwait run testnonretryableerror storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max internal client txn go failure aborting transaction writing transaction timed out or ran on multiple coordinators abort caused by node unavailable try another peer storage queue go unable to split at key table storage replica command go split at key table failed node unavailable try another peer pass testnonretryableerror run testnonretryableerroroncommit storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max internal client txn go failure aborting transaction testerror abort caused by testerror pass testnonretryableerroroncommit run testreacquireleaseonrestart storage queue go range requires a replication change but lacks a quorum of live replicas storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max pass testreacquireleaseonrestart pass found data race s error exit status make error runs completed failures over fail makefile recipe for target stress failed | 0 |
9,327 | 12,339,807,461 | IssuesEvent | 2020-05-14 18:46:47 | elastic/beats | https://api.github.com/repos/elastic/beats | opened | Beats fingerprint processor should generate same fingerprints as Logstash fingerprint filter | :Processors Team:Services bug libbeat | According to https://discuss.elastic.co/t/integrity-issue-between-winlogbeat-and-logstash-fingerprint/232654, it appears the [Beats fingerprint processor](https://www.elastic.co/guide/en/beats/winlogbeat/current/fingerprint.html) does not generate the same fingerprints (for the same fields, with the same hashing algorithm) as the [Logstash fingerprint filter](https://www.elastic.co/guide/en/logstash/current/plugins-filters-fingerprint.html).
Looking at the two implementations, specifically the concatenation code ([Beats](https://github.com/elastic/beats/blob/ea8a649e3fe20f5c616508fca13f5caa1a672a80/libbeat/processors/fingerprint/fingerprint.go#L106-L109) | [Logstash](https://github.com/logstash-plugins/logstash-filter-fingerprint/blob/da8a4842f7e24bd089721e930e1fe1e38105ed81/lib/logstash/filters/fingerprint.rb#L120-L130)), it looks like the intent was for the two fingerprints to be the same. | 1.0 | Beats fingerprint processor should generate same fingerprints as Logstash fingerprint filter - According to https://discuss.elastic.co/t/integrity-issue-between-winlogbeat-and-logstash-fingerprint/232654, it appears the [Beats fingerprint processor](https://www.elastic.co/guide/en/beats/winlogbeat/current/fingerprint.html) does not generate the same fingerprints (for the same fields, with the same hashing algorithm) as the [Logstash fingerprint filter](https://www.elastic.co/guide/en/logstash/current/plugins-filters-fingerprint.html).
Looking at the two implementations, specifically the concatenation code ([Beats](https://github.com/elastic/beats/blob/ea8a649e3fe20f5c616508fca13f5caa1a672a80/libbeat/processors/fingerprint/fingerprint.go#L106-L109) | [Logstash](https://github.com/logstash-plugins/logstash-filter-fingerprint/blob/da8a4842f7e24bd089721e930e1fe1e38105ed81/lib/logstash/filters/fingerprint.rb#L120-L130)), it looks like the intent was for the two fingerprints to be the same. | process | beats fingerprint processor should generate same fingerprints as logstash fingerprint filter according to it appears the does not generate the same fingerprints for the same fields with the same hashing algorithm as the looking at the two implementations specifically the concatenation code it looks like the intent was for the two fingerprints to be the same | 1 |
128,102 | 27,190,580,112 | IssuesEvent | 2023-02-19 18:54:39 | oakestra/dashboard | https://api.github.com/repos/oakestra/dashboard | opened | Refactor graph in the frontend. | bug help wanted code structure | In a previous version of the frontend there was a graph. Here all services in this application are displayed and you can create connections between the services and define different requirements for the connection.
However, this function is currently written in javascript and not well built into the frontend. It needs refactoring. | 1.0 | Refactor graph in the frontend. - In a previous version of the frontend there was a graph. Here all services in this application are displayed and you can create connections between the services and define different requirements for the connection.
However, this function is currently written in javascript and not well built into the frontend. It needs refactoring. | non_process | refactor graph in the frontend in a previous version of the frontend there was a graph here all services in this application are displayed and you can create connections between the services and define different requirements for the connection however this function is currently written in javascript and not well built into the frontend it needs refactoring | 0 |
275,425 | 8,575,869,974 | IssuesEvent | 2018-11-12 18:34:35 | AC287/cambridge-wptheme | https://api.github.com/repos/AC287/cambridge-wptheme | closed | Things left to do | Project Priority | - [x] Align image thumbnail @ item page. (Styling mod at slick.js?)
- [ ] Gray wire connector image need to remove saturation; make more gray?
- [x] Darker highlight color for active product accordion.
- [ ] Adding "alt" description for **ALL** images.
- [ ] Re-design spreadsheet database.
* Create description column in product legend database.
* Revise php code to take description column from product legend database in prod-page2.php
- [ ] Finish filling product data in spreadsheet.
- [ ] Finish taking images of each product.
- [ ] Adding in keyword.
* Check searchpage.php to see if php code include search from keyword.
- [ ] Need to change contact us forwarding address before going live. | 1.0 | Things left to do - - [x] Align image thumbnail @ item page. (Styling mod at slick.js?)
- [ ] Gray wire connector image need to remove saturation; make more gray?
- [x] Darker highlight color for active product accordion.
- [ ] Adding "alt" description for **ALL** images.
- [ ] Re-design spreadsheet database.
* Create description column in product legend database.
* Revise php code to take description column from product legend database in prod-page2.php
- [ ] Finish filling product data in spreadsheet.
- [ ] Finish taking images of each product.
- [ ] Adding in keyword.
* Check searchpage.php to see if php code include search from keyword.
- [ ] Need to change contact us forwarding address before going live. | non_process | things left to do align image thumbnail item page styling mod at slick js gray wire connector image need to remove saturation make more gray darker highlight color for active product accordion adding alt description for all images re design spreadsheet database create description column in product legend database revise php code to take description column from product legend database in prod php finish filling product data in spreadsheet finish taking images of each product adding in keyword check searchpage php to see if php code include search from keyword need to change contact us forwarding address before going live | 0 |
487,696 | 14,050,806,720 | IssuesEvent | 2020-11-02 12:22:39 | AY2021S1-CS2103T-W16-2/tp | https://api.github.com/repos/AY2021S1-CS2103T-W16-2/tp | closed | [PE-D] Sorting behavior places small letters behind capital letters | priority.Medium severity.Medium | reproduce using : `sort reversegerman`
list should contain a german word that is not first-letter-capitalised and starts with 'a', as well as a german word that contains a german word that IS first-letter-capitalised and starts with 'Z'. this results in the word with 'a' as first letter being seen as being behind a word with first letter 'Z'. this is not very intuitve as the user may have words that start with small letters and words starting with capital letters. And the desired behavior should be a sorting that does not care about the case of the letters
<!--session: 1604045399626-1ccdd2a1-a42c-4648-9a17-00c5c0bbe831-->
-------------
Labels: `severity.High` `type.FeatureFlaw`
original: cwenling/ped#4 | 1.0 | [PE-D] Sorting behavior places small letters behind capital letters - reproduce using : `sort reversegerman`
list should contain a german word that is not first-letter-capitalised and starts with 'a', as well as a german word that contains a german word that IS first-letter-capitalised and starts with 'Z'. this results in the word with 'a' as first letter being seen as being behind a word with first letter 'Z'. this is not very intuitve as the user may have words that start with small letters and words starting with capital letters. And the desired behavior should be a sorting that does not care about the case of the letters
<!--session: 1604045399626-1ccdd2a1-a42c-4648-9a17-00c5c0bbe831-->
-------------
Labels: `severity.High` `type.FeatureFlaw`
original: cwenling/ped#4 | non_process | sorting behavior places small letters behind capital letters reproduce using sort reversegerman list should contain a german word that is not first letter capitalised and starts with a as well as a german word that contains a german word that is first letter capitalised and starts with z this results in the word with a as first letter being seen as being behind a word with first letter z this is not very intuitve as the user may have words that start with small letters and words starting with capital letters and the desired behavior should be a sorting that does not care about the case of the letters labels severity high type featureflaw original cwenling ped | 0 |
21,154 | 28,129,709,609 | IssuesEvent | 2023-03-31 21:17:40 | USGS-R/lake-temp-lstm-static-data-release | https://api.github.com/repos/USGS-R/lake-temp-lstm-static-data-release | closed | Fix wording in process description | process-description | From Sam:
> Not sure what “this data release used these methods to aggregate additional cooperator data” means. | 1.0 | Fix wording in process description - From Sam:
> Not sure what “this data release used these methods to aggregate additional cooperator data” means. | process | fix wording in process description from sam not sure what “this data release used these methods to aggregate additional cooperator data” means | 1 |
6,220 | 9,160,365,306 | IssuesEvent | 2019-03-01 07:07:07 | SymeonChen/SymeonChen.github.io | https://api.github.com/repos/SymeonChen/SymeonChen.github.io | opened | Build a Visual Music Player With Arduino and Processing | Arduino Processing | date: 2016-09-08 17:41:17
## Foreword
This is a small thing that was spent half a day with a classmate six months ago. Recently, I got the components and reproduced the production process, that's why I recorded some procedures and experience here.
## Result
The actual operation diagram is as follows, the finger uses different gestures on the Touch Sensor to slide different operations.
<!-- more -->
Operating gif is as follows
The number of lines is changing following the rhythm.
## Used Hardware
- Arduino Uno R3
- I2C Touch Sensor
- DuPont line
## Introduce of Hardware
### Arduino Uno R3
> [Arduino is an open-source electronics platform based on easy-to-use hardware and software](https://www.arduino.cc/en/Guide/Introduction?setlang=en#)
Arduino includes hardware (development board) and software (IDE), and the developer has packaged many functions, making the Arduino easier to use than the 51 series. Arduino hardware and software are open source, everyone can copy, modify, sell Arduino development board, so in the internet super market you can buy a lot of low-cost compatible board. Thanks to the heat of the Arduino, you can easily get the modules you want. It can be said that Arduino is very good as a prototyping tool.
Compared to another common Raspberry Pi, the Arduino expansion module is much cheaper and more comprehensive.
Among the many Arduino development boards, the most famous is the Arduino Uno series, which is based on the ATmega328p microprocessor, 14 IO pins, including 6 PWM outputs, supporting TTL, USB, I2C, SPI communication.
### I2C Touch Sensor
Online shopping malls in mainland China are sold less, which is a less common Touch Sensor。Parameters are [here](http://wiki.seeedstudio.com/wiki/Grove_-_I2C_Touch_Sensor)
It should be noted that the wiring at `INT` is easy to fall off and needs to be fixed.
The Touch Sensor can connect multiple sensor blades at the same time, and the sensor is also very sensitive and has high playability.
## Used Software
- [Arduino Software (IDE)](https://www.arduino.cc/en/Main/Software)
- [Processing](https://processing.org/download/?processing)
Both software are cross-platform and are recommended for use on Windows. If you are installing on Linux, you may need to deal with the Arduino driver problem, which is a bit of a hassle.
## Introduce of Software
###Arduino IDE
When installing on Windows, the driver will be included. After connecting the Arduino, check whether the device manager has an unidentified device to determine that the driver is properly installed.
You need to select the port before running the program, as shown below:
### Processing
`Processing` is also a good tool for interactive design and visualization, performance is not bad, but also cross-platform. It also has extensions, such as `Processing.js`, which are convenient to use overall.
## Design of Programming
### Part of Arduino
First import the [Library](https://github.com/Seeed-Studio/Grove_I2C_Touch_Sensor) of the `I2C Touch Sensor`，than import the [Library](https://github.com/wendellinfinity/GroveMultiTouch) of MultiTouch for test. After that, connect the I2C Touch Sensor and Arduino, the `INT` connecting to port 7, `VCC` to 5V。
Then open the example and select `GroveI2CTouchTest`,
Run the sample program to test if the I2C Touch Sensor is working properly.
Then gently fix the four sensor pieces
If the accuracy is not high, then GroveI2CTouchTest can be used directly. If you want to consider anti-missing and other issues, you need to make some optimizations, such as making a gesture every two seconds, rather than triggering a gesture.
### Part of Processing
Because you want to decode the music, you need to import the `Minim Library`, After that , reading the [Document](http://code.compartmental.net/minim/) to know usage.
Then for the realization of the dynamic effect, the code implements five kinds, here is a brief introduction:
#### First, the wavy lines
```java
void drawPic1() {
background(0);
stroke(255);
musicName(musicNumber);
for (int i=0; i<player.bufferSize()-1; i++)
{
strokeWeight(abs(player.left.get(i)*20));
line(i, 150+player.left.get(i)*100, i+1,150+player.left.get(i+1)*100);
}
}
```
Where player.left is the left channel, you can also use the right channel player.right, mix player.mix, player.left.get() will return a value between -1 and 1, so multiply by a few multiples to see The comparison is clear. The above code is a diagram of the waveform diagram. The next few principles are the same, except that the graphics are drawn differently.
#### Second, concentric circles
```java
void drawPic2() {
int n;
int i;
float v;
stroke(255);
background(0);
musicName(musicNumber);
fft.forward(player.mix);
n = fft.specSize() / 4;
for (i = 0; i < n; i++) {
stroke(100.0*i/n, 100, 100, 50);
// Magnified multiple
v = fft.getBand(i) * 3;
ellipse(width/2, height/2, v, v);
}
}
```
`Ellipse` was originally used to draw ellipse, which can alse used to draw standard circles.
#### Third, non-concentric circles
```java
void drawPic3() {
float v;
float x, y;
int n;
int i;
stroke(255);
background(0);
musicName(musicNumber);
fft.forward(player.mix);
n = fft.specSize() / 4;
for (i = 0; i < n; i++) {
fill(100.0*i/n, 100, 100, 50);
v = fft.getBand(i) * 4;
x = random(0, width);
y = random(0, height);
ellipse(x, y, v, v);
}
```
#### Fourth, two lines
```java
void drawPic4()
{
float v;
float x1, y1, x2, y2;
int n;
int i;
background(0);
musicName(musicNumber);
fft.forward(player.mix);
n = fft.specSize() / 4;
for (i = 0; i < n; i++) {
stroke(100.0*i/n, 100, 100);
v = fft.getBand(i) * 4;
x1 = random(-v, v) + width / 2;
y1 = random(-v, v) + height / 2;
x2 = random(-v, v) + width / 2;
y2 = random(-v, v) + height / 2;
line(x1, y1, x2, y2);
}
}
```
```java
void drawPic5()
{
float v;
float x1, y1, x2, y2;
float dx1, dy1, dx2, dy2;
int u1, v1, u2, v2;
int n;
int i, j;
background(0);
musicName(musicNumber);
fft.forward(player.mix);
n = fft.specSize() / 4;
for (i = 0; i < n; i++) {
stroke(100.0*i/n, 100, 100, 50);
v = fft.getBand(i) * 4;
x1 = random(-v, v) + width / 2;
y1 = random(-v, v) + height / 2;
x2 = random(-v, v) + width / 2;
y2 = random(-v, v) + height / 2;
dx1 = (x1 - width/2) / 10;
dy1 = (y1 - height/2) / 10;
dx2 = (x2 - width/2) / 10;
dy2 = (y2 - height/2) / 10;
for (j = 0; j <= 9; j++) {
u1 = (int)(width/2 + j * dx1);
v1 = (int)(height/2 + j * dy1);
u2 = (int)(width/2 + j * dx2);
v2 = (int)(height/2 + j * dy2);
line(u1, v1, u2, v2);
}
}
}
```
The code of several kinds of graphics is relatively simple, so I won't go into details. I will mention a few pits that I might encounter. When I draw the song name, it is easy to be covered by the graphic. Here, I use the font to draw the song name every time I draw the graph. To ensure that the song name is always visible, you can also split on the interface, but it is more troublesome to implement.
When the sensor was fixed on the protective case, the wire fell off, so I found a box to re-fix. Because there is no extended version on hand, I can only connect the I2C Touch Sensor directly to the Arduino. This has a problem, DuPont. The line is too thick and there is no way to access the four ports of the Touch Sensor.
So we removed the DuPont line
Before and after the comparison, the occupied space is much smaller.
Then tie it with black tape and do insulation treatment.
This will insert the interface normally.
Song and code package download at [here](https://drive.google.com/open?id=0B5ty2n_fxNiVS0ZTTm8xcnZmTEU)（Google Drive），Incidentally, the songs in the file are public copyright-free songs, and the code format is also very messy, because it is written in a hurry, only for trial run. | 1.0 | Build a Visual Music Player With Arduino and Processing - date: 2016-09-08 17:41:17
## Foreword
This is a small thing that was spent half a day with a classmate six months ago. Recently, I got the components and reproduced the production process, that's why I recorded some procedures and experience here.
## Result
The actual operation diagram is as follows, the finger uses different gestures on the Touch Sensor to slide different operations.
<!-- more -->
Operating gif is as follows
The number of lines is changing following the rhythm.
## Used Hardware
- Arduino Uno R3
- I2C Touch Sensor
- DuPont line
## Introduce of Hardware
### Arduino Uno R3
> [Arduino is an open-source electronics platform based on easy-to-use hardware and software](https://www.arduino.cc/en/Guide/Introduction?setlang=en#)
Arduino includes hardware (development board) and software (IDE), and the developer has packaged many functions, making the Arduino easier to use than the 51 series. Arduino hardware and software are open source, everyone can copy, modify, sell Arduino development board, so in the internet super market you can buy a lot of low-cost compatible board. Thanks to the heat of the Arduino, you can easily get the modules you want. It can be said that Arduino is very good as a prototyping tool.
Compared to another common Raspberry Pi, the Arduino expansion module is much cheaper and more comprehensive.
Among the many Arduino development boards, the most famous is the Arduino Uno series, which is based on the ATmega328p microprocessor, 14 IO pins, including 6 PWM outputs, supporting TTL, USB, I2C, SPI communication.
### I2C Touch Sensor
Online shopping malls in mainland China are sold less, which is a less common Touch Sensor。Parameters are [here](http://wiki.seeedstudio.com/wiki/Grove_-_I2C_Touch_Sensor)
It should be noted that the wiring at `INT` is easy to fall off and needs to be fixed.
The Touch Sensor can connect multiple sensor blades at the same time, and the sensor is also very sensitive and has high playability.
## Used Software
- [Arduino Software (IDE)](https://www.arduino.cc/en/Main/Software)
- [Processing](https://processing.org/download/?processing)
Both software are cross-platform and are recommended for use on Windows. If you are installing on Linux, you may need to deal with the Arduino driver problem, which is a bit of a hassle.
## Introduce of Software
###Arduino IDE
When installing on Windows, the driver will be included. After connecting the Arduino, check whether the device manager has an unidentified device to determine that the driver is properly installed.
You need to select the port before running the program, as shown below:
### Processing
`Processing` is also a good tool for interactive design and visualization, performance is not bad, but also cross-platform. It also has extensions, such as `Processing.js`, which are convenient to use overall.
## Design of Programming
### Part of Arduino
First import the [Library](https://github.com/Seeed-Studio/Grove_I2C_Touch_Sensor) of the `I2C Touch Sensor`，than import the [Library](https://github.com/wendellinfinity/GroveMultiTouch) of MultiTouch for test. After that, connect the I2C Touch Sensor and Arduino, the `INT` connecting to port 7, `VCC` to 5V。
Then open the example and select `GroveI2CTouchTest`,
Run the sample program to test if the I2C Touch Sensor is working properly.
Then gently fix the four sensor pieces
If the accuracy is not high, then GroveI2CTouchTest can be used directly. If you want to consider anti-missing and other issues, you need to make some optimizations, such as making a gesture every two seconds, rather than triggering a gesture.
### Part of Processing
Because you want to decode the music, you need to import the `Minim Library`, After that , reading the [Document](http://code.compartmental.net/minim/) to know usage.
Then for the realization of the dynamic effect, the code implements five kinds, here is a brief introduction:
#### First, the wavy lines
```java
void drawPic1() {
background(0);
stroke(255);
musicName(musicNumber);
for (int i=0; i<player.bufferSize()-1; i++)
{
strokeWeight(abs(player.left.get(i)*20));
line(i, 150+player.left.get(i)*100, i+1,150+player.left.get(i+1)*100);
}
}
```
Where player.left is the left channel, you can also use the right channel player.right, mix player.mix, player.left.get() will return a value between -1 and 1, so multiply by a few multiples to see The comparison is clear. The above code is a diagram of the waveform diagram. The next few principles are the same, except that the graphics are drawn differently.
#### Second, concentric circles
```java
void drawPic2() {
int n;
int i;
float v;
stroke(255);
background(0);
musicName(musicNumber);
fft.forward(player.mix);
n = fft.specSize() / 4;
for (i = 0; i < n; i++) {
stroke(100.0*i/n, 100, 100, 50);
// Magnified multiple
v = fft.getBand(i) * 3;
ellipse(width/2, height/2, v, v);
}
}
```
`Ellipse` was originally used to draw ellipse, which can alse used to draw standard circles.
#### Third, non-concentric circles
```java
void drawPic3() {
float v;
float x, y;
int n;
int i;
stroke(255);
background(0);
musicName(musicNumber);
fft.forward(player.mix);
n = fft.specSize() / 4;
for (i = 0; i < n; i++) {
fill(100.0*i/n, 100, 100, 50);
v = fft.getBand(i) * 4;
x = random(0, width);
y = random(0, height);
ellipse(x, y, v, v);
}
```
#### Fourth, two lines
```java
void drawPic4()
{
float v;
float x1, y1, x2, y2;
int n;
int i;
background(0);
musicName(musicNumber);
fft.forward(player.mix);
n = fft.specSize() / 4;
for (i = 0; i < n; i++) {
stroke(100.0*i/n, 100, 100);
v = fft.getBand(i) * 4;
x1 = random(-v, v) + width / 2;
y1 = random(-v, v) + height / 2;
x2 = random(-v, v) + width / 2;
y2 = random(-v, v) + height / 2;
line(x1, y1, x2, y2);
}
}
```
```java
void drawPic5()
{
float v;
float x1, y1, x2, y2;
float dx1, dy1, dx2, dy2;
int u1, v1, u2, v2;
int n;
int i, j;
background(0);
musicName(musicNumber);
fft.forward(player.mix);
n = fft.specSize() / 4;
for (i = 0; i < n; i++) {
stroke(100.0*i/n, 100, 100, 50);
v = fft.getBand(i) * 4;
x1 = random(-v, v) + width / 2;
y1 = random(-v, v) + height / 2;
x2 = random(-v, v) + width / 2;
y2 = random(-v, v) + height / 2;
dx1 = (x1 - width/2) / 10;
dy1 = (y1 - height/2) / 10;
dx2 = (x2 - width/2) / 10;
dy2 = (y2 - height/2) / 10;
for (j = 0; j <= 9; j++) {
u1 = (int)(width/2 + j * dx1);
v1 = (int)(height/2 + j * dy1);
u2 = (int)(width/2 + j * dx2);
v2 = (int)(height/2 + j * dy2);
line(u1, v1, u2, v2);
}
}
}
```
The code of several kinds of graphics is relatively simple, so I won't go into details. I will mention a few pits that I might encounter. When I draw the song name, it is easy to be covered by the graphic. Here, I use the font to draw the song name every time I draw the graph. To ensure that the song name is always visible, you can also split on the interface, but it is more troublesome to implement.
When the sensor was fixed on the protective case, the wire fell off, so I found a box to re-fix. Because there is no extended version on hand, I can only connect the I2C Touch Sensor directly to the Arduino. This has a problem, DuPont. The line is too thick and there is no way to access the four ports of the Touch Sensor.
So we removed the DuPont line
Before and after the comparison, the occupied space is much smaller.
Then tie it with black tape and do insulation treatment.
This will insert the interface normally.
Song and code package download at [here](https://drive.google.com/open?id=0B5ty2n_fxNiVS0ZTTm8xcnZmTEU)（Google Drive），Incidentally, the songs in the file are public copyright-free songs, and the code format is also very messy, because it is written in a hurry, only for trial run. | process | build a visual music player with arduino and processing date foreword this is a small thing that was spent half a day with a classmate six months ago recently i got the components and reproduced the production process that s why i recorded some procedures and experience here result the actual operation diagram is as follows the finger uses different gestures on the touch sensor to slide different operations operating gif is as follows the number of lines is changing following the rhythm used hardware arduino uno touch sensor dupont line introduce of hardware arduino uno arduino includes hardware development board and software ide and the developer has packaged many functions making the arduino easier to use than the series arduino hardware and software are open source everyone can copy modify sell arduino development board so in the internet super market you can buy a lot of low cost compatible board thanks to the heat of the arduino you can easily get the modules you want it can be said that arduino is very good as a prototyping tool compared to another common raspberry pi the arduino expansion module is much cheaper and more comprehensive among the many arduino development boards the most famous is the arduino uno series which is based on the microprocessor io pins including pwm outputs supporting ttl usb spi communication touch sensor online shopping malls in mainland china are sold less which is a less common touch sensor。parameters are it should be noted that the wiring at int is easy to fall off and needs to be fixed the touch sensor can connect multiple sensor blades at the same time and the sensor is also very sensitive and has high playability used software both software are cross platform and are recommended for use on windows if you are installing on linux you may need to deal with the arduino driver problem which is a bit of a hassle introduce of software arduino ide when installing on windows the driver will be included after connecting the arduino check whether the device manager has an unidentified device to determine that the driver is properly installed you need to select the port before running the program as shown below processing processing is also a good tool for interactive design and visualization performance is not bad but also cross platform it also has extensions such as processing js which are convenient to use overall design of programming part of arduino first import the of the touch sensor ，than import the of multitouch for test after that connect the touch sensor and arduino the int connecting to port vcc to 。 then open the example and select run the sample program to test if the touch sensor is working properly then gently fix the four sensor pieces if the accuracy is not high then can be used directly if you want to consider anti missing and other issues you need to make some optimizations such as making a gesture every two seconds rather than triggering a gesture part of processing because you want to decode the music you need to import the minim library after that reading the to know usage then for the realization of the dynamic effect the code implements five kinds here is a brief introduction first the wavy lines java void background stroke musicname musicnumber for int i i player buffersize i strokeweight abs player left get i line i player left get i i player left get i where player left is the left channel you can also use the right channel player right mix player mix player left get will return a value between and so multiply by a few multiples to see the comparison is clear the above code is a diagram of the waveform diagram the next few principles are the same except that the graphics are drawn differently second concentric circles java void int n int i float v stroke background musicname musicnumber fft forward player mix n fft specsize for i i n i stroke i n magnified multiple v fft getband i ellipse width height v v ellipse was originally used to draw ellipse which can alse used to draw standard circles third non concentric circles java void float v float x y int n int i stroke background musicname musicnumber fft forward player mix n fft specsize for i i n i fill i n v fft getband i x random width y random height ellipse x y v v fourth two lines java void float v float int n int i background musicname musicnumber fft forward player mix n fft specsize for i i n i stroke i n v fft getband i random v v width random v v height random v v width random v v height line java void float v float float int int n int i j background musicname musicnumber fft forward player mix n fft specsize for i i n i stroke i n v fft getband i random v v width random v v height random v v width random v v height width height width height for j j j int width j int height j int width j int height j line the code of several kinds of graphics is relatively simple so i won t go into details i will mention a few pits that i might encounter when i draw the song name it is easy to be covered by the graphic here i use the font to draw the song name every time i draw the graph to ensure that the song name is always visible you can also split on the interface but it is more troublesome to implement when the sensor was fixed on the protective case the wire fell off so i found a box to re fix because there is no extended version on hand i can only connect the touch sensor directly to the arduino this has a problem dupont the line is too thick and there is no way to access the four ports of the touch sensor so we removed the dupont line before and after the comparison the occupied space is much smaller then tie it with black tape and do insulation treatment this will insert the interface normally song and code package download at drive），incidentally the songs in the file are public copyright free songs and the code format is also very messy because it is written in a hurry only for trial run | 1 |
5,601 | 8,461,354,364 | IssuesEvent | 2018-10-22 21:33:24 | hashicorp/packer | https://api.github.com/repos/hashicorp/packer | closed | Feature Request: Local Shell Provisioner: Detect OS / Optionally execute or not | enhancement good first issue post-processor/shell-local provisioner/shell-local windows-host | I'm running Packer builds on AWS to create AMIs from a Jenkins Server, the OS is CentOS7.
I develop primarily on a Window Laptop, and would like to specify a Local Shell Provisioner step to run, but only when the OS is Linux. To put it another way, I don't want the Local Shell Provisioner step to run on Windows.
There might be a way to do this using WSL but I'd like to prevent execution without requiring WSL to be installed.
A code suggestion would be to support something like:
```
{
"type": "shell-local",
"inline": ["echo 'hello packer'"]
"runon": "linux"
}
```
...where the "runon" argument would support "linux" "windows" or "any" (the current situation). | 1.0 | Feature Request: Local Shell Provisioner: Detect OS / Optionally execute or not - I'm running Packer builds on AWS to create AMIs from a Jenkins Server, the OS is CentOS7.
I develop primarily on a Window Laptop, and would like to specify a Local Shell Provisioner step to run, but only when the OS is Linux. To put it another way, I don't want the Local Shell Provisioner step to run on Windows.
There might be a way to do this using WSL but I'd like to prevent execution without requiring WSL to be installed.
A code suggestion would be to support something like:
```
{
"type": "shell-local",
"inline": ["echo 'hello packer'"]
"runon": "linux"
}
```
...where the "runon" argument would support "linux" "windows" or "any" (the current situation). | process | feature request local shell provisioner detect os optionally execute or not i m running packer builds on aws to create amis from a jenkins server the os is i develop primarily on a window laptop and would like to specify a local shell provisioner step to run but only when the os is linux to put it another way i don t want the local shell provisioner step to run on windows there might be a way to do this using wsl but i d like to prevent execution without requiring wsl to be installed a code suggestion would be to support something like type shell local inline runon linux where the runon argument would support linux windows or any the current situation | 1 |
65,363 | 16,243,331,009 | IssuesEvent | 2021-05-07 12:12:07 | NOAA-EMC/UFS_UTILS | https://api.github.com/repos/NOAA-EMC/UFS_UTILS | opened | Find a way to distribute the data in the fix subdirectory | build | In the fix subdirectory we have a script which creates links to directories of data on our machines.
This won't work for the end user. ;-)
We need to make this data available as a (versioned) tarball on the ftp site. | 1.0 | Find a way to distribute the data in the fix subdirectory - In the fix subdirectory we have a script which creates links to directories of data on our machines.
This won't work for the end user. ;-)
We need to make this data available as a (versioned) tarball on the ftp site. | non_process | find a way to distribute the data in the fix subdirectory in the fix subdirectory we have a script which creates links to directories of data on our machines this won t work for the end user we need to make this data available as a versioned tarball on the ftp site | 0 |
5,929 | 8,752,700,108 | IssuesEvent | 2018-12-14 04:39:21 | nodejs/node | https://api.github.com/repos/nodejs/node | opened | Investigate flaky test-child-process-execFile on AIX | CI / flaky test aix child_process | https://ci.nodejs.org/job/node-test-commit-aix/19688/nodes=aix61-ppc64/consoleText
test-osuosl-aix61-ppc64_be-1
```console
ot ok 217 parallel/test-child-process-execfile
---
duration_ms: 4.640
severity: fail
exitcode: 1
stack: |-
assert.js:86
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
null !== 42
at common.mustCall (/home/iojs/build/workspace/node-test-commit-aix/nodes/aix61-ppc64/test/parallel/test-child-process-execfile.js:20:14)
at /home/iojs/build/workspace/node-test-commit-aix/nodes/aix61-ppc64/test/common/index.js:335:15
at ChildProcess.exithandler (child_process.js:301:5)
at ChildProcess.emit (events.js:189:13)
at maybeClose (internal/child_process.js:978:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:265:5)
...
``` | 1.0 | Investigate flaky test-child-process-execFile on AIX - https://ci.nodejs.org/job/node-test-commit-aix/19688/nodes=aix61-ppc64/consoleText
test-osuosl-aix61-ppc64_be-1
```console
ot ok 217 parallel/test-child-process-execfile
---
duration_ms: 4.640
severity: fail
exitcode: 1
stack: |-
assert.js:86
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
null !== 42
at common.mustCall (/home/iojs/build/workspace/node-test-commit-aix/nodes/aix61-ppc64/test/parallel/test-child-process-execfile.js:20:14)
at /home/iojs/build/workspace/node-test-commit-aix/nodes/aix61-ppc64/test/common/index.js:335:15
at ChildProcess.exithandler (child_process.js:301:5)
at ChildProcess.emit (events.js:189:13)
at maybeClose (internal/child_process.js:978:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:265:5)
...
``` | process | investigate flaky test child process execfile on aix test osuosl be console ot ok parallel test child process execfile duration ms severity fail exitcode stack assert js throw new assertionerror obj assertionerror expected values to be strictly equal null at common mustcall home iojs build workspace node test commit aix nodes test parallel test child process execfile js at home iojs build workspace node test commit aix nodes test common index js at childprocess exithandler child process js at childprocess emit events js at maybeclose internal child process js at process childprocess handle onexit internal child process js | 1 |
20,385 | 27,043,727,030 | IssuesEvent | 2023-02-13 08:10:50 | darktable-org/darktable | https://api.github.com/repos/darktable-org/darktable | closed | In some specific resolutions, the left pixel column of an image is copied to the right | understood: clear reproduce: confirmed scope: image processing bug: pending | /EDIT/ Bug reproduced by ptilopteri.
Main points:
- some specific sizes so use the reference image below
- export with scaling by factor = 1 (the bug will not occur with scaling pixel = 0 0)
______________________________
Hello guys,
I'm happy to work with Darktable and put #darktable and #darktableedit in my pictures. I made a two-year pose and resumed two month ago to work with Darktable 3.8 for a small dance school show project. I encountered a show stopper.
This project has more than 3000 usable pictures. Most of them need reframing. The scene are sometime about subject against dark backgrounds. I noticed something odd on the right side of some pictures. After some investigation, I noticed that, **at some resolutions, the left column of pixels is copied to the right column of pixels at export**. This can be very obvious when there are some dancers cut on the left side in colorful dresses and a black background on the right.
I use a regular Ubuntu 22.04 installation with the stock Darktable 3.8. Seeing the bug happening I installed the ppa version 4.0, but it is still there. I have an NVidia 2080S but it happens with or without Open CL and I deactivated all processing modules.
To reproduce the bug I created a specific JPG image with a specific size that you can load and export in Darktable (I tested on 3.8 and 4.0) to see for yourselves.
The TEST IMAGE (I hope it's in native resolution of 1108x720):
- Import it in Darktable 3.8 or 4.0
- Export it in PNG or high quality JPG **EDIT: Using Set size by FACTOR=1 instead of Pixel sized 0 0** (I didn't have the time to test other settings but I use allow upscaling: yes (but the output image is the same size) and high quality resampling: yes)
Look closely at the right part of the original (gray line on the right part), and the export (full of colors from the left side). It happens only for some resolutions and doesn't depend of the content. It also do not depend of the input format (tested with NEF, PNG, JPG) and the bug is at export: in Darktable, the image is like the original.
On some software or some scaling process this one pixel line (that is very visible on a 4K screen) will be even more obvious. This is a **major issue**.
Good luck, and thank you for this wonderful software. | 1.0 | In some specific resolutions, the left pixel column of an image is copied to the right - /EDIT/ Bug reproduced by ptilopteri.
Main points:
- some specific sizes so use the reference image below
- export with scaling by factor = 1 (the bug will not occur with scaling pixel = 0 0)
______________________________
Hello guys,
I'm happy to work with Darktable and put #darktable and #darktableedit in my pictures. I made a two-year pose and resumed two month ago to work with Darktable 3.8 for a small dance school show project. I encountered a show stopper.
This project has more than 3000 usable pictures. Most of them need reframing. The scene are sometime about subject against dark backgrounds. I noticed something odd on the right side of some pictures. After some investigation, I noticed that, **at some resolutions, the left column of pixels is copied to the right column of pixels at export**. This can be very obvious when there are some dancers cut on the left side in colorful dresses and a black background on the right.
I use a regular Ubuntu 22.04 installation with the stock Darktable 3.8. Seeing the bug happening I installed the ppa version 4.0, but it is still there. I have an NVidia 2080S but it happens with or without Open CL and I deactivated all processing modules.
To reproduce the bug I created a specific JPG image with a specific size that you can load and export in Darktable (I tested on 3.8 and 4.0) to see for yourselves.
The TEST IMAGE (I hope it's in native resolution of 1108x720):
- Import it in Darktable 3.8 or 4.0
- Export it in PNG or high quality JPG **EDIT: Using Set size by FACTOR=1 instead of Pixel sized 0 0** (I didn't have the time to test other settings but I use allow upscaling: yes (but the output image is the same size) and high quality resampling: yes)
Look closely at the right part of the original (gray line on the right part), and the export (full of colors from the left side). It happens only for some resolutions and doesn't depend of the content. It also do not depend of the input format (tested with NEF, PNG, JPG) and the bug is at export: in Darktable, the image is like the original.
On some software or some scaling process this one pixel line (that is very visible on a 4K screen) will be even more obvious. This is a **major issue**.
Good luck, and thank you for this wonderful software. | process | in some specific resolutions the left pixel column of an image is copied to the right edit bug reproduced by ptilopteri main points some specific sizes so use the reference image below export with scaling by factor the bug will not occur with scaling pixel hello guys i m happy to work with darktable and put darktable and darktableedit in my pictures i made a two year pose and resumed two month ago to work with darktable for a small dance school show project i encountered a show stopper this project has more than usable pictures most of them need reframing the scene are sometime about subject against dark backgrounds i noticed something odd on the right side of some pictures after some investigation i noticed that at some resolutions the left column of pixels is copied to the right column of pixels at export this can be very obvious when there are some dancers cut on the left side in colorful dresses and a black background on the right i use a regular ubuntu installation with the stock darktable seeing the bug happening i installed the ppa version but it is still there i have an nvidia but it happens with or without open cl and i deactivated all processing modules to reproduce the bug i created a specific jpg image with a specific size that you can load and export in darktable i tested on and to see for yourselves the test image i hope it s in native resolution of import it in darktable or export it in png or high quality jpg edit using set size by factor instead of pixel sized i didn t have the time to test other settings but i use allow upscaling yes but the output image is the same size and high quality resampling yes look closely at the right part of the original gray line on the right part and the export full of colors from the left side it happens only for some resolutions and doesn t depend of the content it also do not depend of the input format tested with nef png jpg and the bug is at export in darktable the image is like the original on some software or some scaling process this one pixel line that is very visible on a screen will be even more obvious this is a major issue good luck and thank you for this wonderful software | 1 |
13,184 | 2,736,228,652 | IssuesEvent | 2015-04-19 07:23:07 | primefaces/primefaces | https://api.github.com/repos/primefaces/primefaces | opened | GMap not visible on an invisible page of Mobile | defect | If gmap is placed inside a view that is not the first of a mobile page, then it can't be displayed. | 1.0 | GMap not visible on an invisible page of Mobile - If gmap is placed inside a view that is not the first of a mobile page, then it can't be displayed. | non_process | gmap not visible on an invisible page of mobile if gmap is placed inside a view that is not the first of a mobile page then it can t be displayed | 0 |
15,968 | 20,177,466,784 | IssuesEvent | 2022-02-10 15:35:28 | ooi-data/CE04OSPS-SF01B-3D-SPKIRA102-streamed-spkir_data_record | https://api.github.com/repos/ooi-data/CE04OSPS-SF01B-3D-SPKIRA102-streamed-spkir_data_record | opened | 🛑 Processing failed: GroupNotFoundError | process | ## Overview
`GroupNotFoundError` found in `processing_task` task during run ended on 2022-02-10T15:35:27.921779.
## Details
Flow name: `CE04OSPS-SF01B-3D-SPKIRA102-streamed-spkir_data_record`
Task name: `processing_task`
Error type: `GroupNotFoundError`
Error message: group not found at path ''
<details>
<summary>Traceback</summary>
```
Traceback (most recent call last):
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/ooi_harvester/processor/pipeline.py", line 165, in processing
final_path = finalize_data_stream(
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/ooi_harvester/processor/__init__.py", line 64, in finalize_data_stream
final_group = zarr.open_group(final_store, mode='r+')
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/zarr/hierarchy.py", line 1168, in open_group
raise GroupNotFoundError(path)
zarr.errors.GroupNotFoundError: group not found at path ''
```
</details>
| 1.0 | 🛑 Processing failed: GroupNotFoundError - ## Overview
`GroupNotFoundError` found in `processing_task` task during run ended on 2022-02-10T15:35:27.921779.
## Details
Flow name: `CE04OSPS-SF01B-3D-SPKIRA102-streamed-spkir_data_record`
Task name: `processing_task`
Error type: `GroupNotFoundError`
Error message: group not found at path ''
<details>
<summary>Traceback</summary>
```
Traceback (most recent call last):
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/ooi_harvester/processor/pipeline.py", line 165, in processing
final_path = finalize_data_stream(
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/ooi_harvester/processor/__init__.py", line 64, in finalize_data_stream
final_group = zarr.open_group(final_store, mode='r+')
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/zarr/hierarchy.py", line 1168, in open_group
raise GroupNotFoundError(path)
zarr.errors.GroupNotFoundError: group not found at path ''
```
</details>
| process | 🛑 processing failed groupnotfounderror overview groupnotfounderror found in processing task task during run ended on details flow name streamed spkir data record task name processing task error type groupnotfounderror error message group not found at path traceback traceback most recent call last file srv conda envs notebook lib site packages ooi harvester processor pipeline py line in processing final path finalize data stream file srv conda envs notebook lib site packages ooi harvester processor init py line in finalize data stream final group zarr open group final store mode r file srv conda envs notebook lib site packages zarr hierarchy py line in open group raise groupnotfounderror path zarr errors groupnotfounderror group not found at path | 1 |
163,484 | 25,824,133,265 | IssuesEvent | 2022-12-12 11:42:18 | dotnet/aspnetcore | https://api.github.com/repos/dotnet/aspnetcore | opened | Support for AuthN with JWT stored in session http-only cookies | design-proposal | <!--
This template is useful to build consensus about whether work should be done, and if so, the high-level shape of how it should be approached. Use this before fixating on a particular implementation.
-->
## Summary
Create in-box support for Authn with JWT stored in http-only cookies
## Motivation and goals
Then we develop SPA application with ASP.NET Core (for ex. with React at frontend) we very often think about how we implement authentication in our application. There is currently two ways to do it: with session cookie, and with JWT. As devs, we prefer to use jwt, because it does not require for a DB lookup.
If we decided to use jwt, there is 3 ways to do request with it:
- Set as authorization header (`Authorization: Bearer <token>`) and store it locally in memory (`.AddJwtBearer()`
- Set as authorization header (`Authorization: Bearer <token>`) and store it in browser local storage (`.AddJwtBearer()`)
- Pass jwt token in http-only cookie
The third option is currently the most secure way to pass and store jwt tokens, because we become immutable to __XSS__ attack, because attacker cannot read our token from cookie. Still, we became vulnerable to CSRF, but this we can fix this by providing XSRF token on a client side. By the end of a day, we can see why JWT with http-only secure cookie is preferred as authn solution using jwt's.
However this way is most secure, ASP.NET Core does not provide in-box solution for this, so we need to add custom middleware to any project which uses this technique. Currently, we implement this logic by this sort of middleware:
```cs
app.UseCookiePolicy(cookiePolicyOptions); // making cookie http-only, strict, e.t.c
app.Use(async (context, next) =>
{
var token = context.Request.Cookies[".AspNetCore.Application.Id"];
if (!string.IsNullOrEmpty(token))
context.Request.Headers.Add("Authorization", "Bearer " + token);
await next();
});
app.UseAuthentication();
```
Futhermore, a lot of other tech solutions (such as [NextAuth](https://next-auth.js.org/configuration/options)) already have support for this feature.
Goals:
- [ ] Create Solution to support JWT in Session token support in-box
## In scope
A list of major scenarios, perhaps in priority order.
## Out of scope
Scenarios you explicitly want to exclude.
## Risks / unknowns
There is security concern, and we need to be careful about reviewing PR for this. Also,
## Examples
### Design proposal No.1: New middleware
We can add new middleware, which will
```cs
app.UseCookiePolicy(cookiePolicyOptions);
app.UseJwtInCookie(jwtInCookiePolicyOptions);
```
### Design proposal No.2: Different authentication scheme?
I'm not sure, if that can be considered as a different authn scheme. If so, we would be able to add jwt in cookie alongside with default jwt bearer and cookies:
```cs
builder.Services.AddAuthentication(CookieAuthenticationDefaults.AuthenticationScheme)
.AddCookie(options =>
{
// some cookie settings
})
.AddJwtBearer(options =>
{
// some jwt settings
})
.AddJwtInCookie(options =>
{
// There is an options for both cookie and jwt configuration for this?
});
```
<!--
# Detailed design
It's often best not to fill this out until you get basic consensus about the above. When you do, consider adding an implementation proposal with the following headings:
Detailed design
Drawbacks
Considered alternatives
Open questions
References
If there's one clear design you have consensus on, you could do that directly in a PR.
-->
| 1.0 | Support for AuthN with JWT stored in session http-only cookies - <!--
This template is useful to build consensus about whether work should be done, and if so, the high-level shape of how it should be approached. Use this before fixating on a particular implementation.
-->
## Summary
Create in-box support for Authn with JWT stored in http-only cookies
## Motivation and goals
Then we develop SPA application with ASP.NET Core (for ex. with React at frontend) we very often think about how we implement authentication in our application. There is currently two ways to do it: with session cookie, and with JWT. As devs, we prefer to use jwt, because it does not require for a DB lookup.
If we decided to use jwt, there is 3 ways to do request with it:
- Set as authorization header (`Authorization: Bearer <token>`) and store it locally in memory (`.AddJwtBearer()`
- Set as authorization header (`Authorization: Bearer <token>`) and store it in browser local storage (`.AddJwtBearer()`)
- Pass jwt token in http-only cookie
The third option is currently the most secure way to pass and store jwt tokens, because we become immutable to __XSS__ attack, because attacker cannot read our token from cookie. Still, we became vulnerable to CSRF, but this we can fix this by providing XSRF token on a client side. By the end of a day, we can see why JWT with http-only secure cookie is preferred as authn solution using jwt's.
However this way is most secure, ASP.NET Core does not provide in-box solution for this, so we need to add custom middleware to any project which uses this technique. Currently, we implement this logic by this sort of middleware:
```cs
app.UseCookiePolicy(cookiePolicyOptions); // making cookie http-only, strict, e.t.c
app.Use(async (context, next) =>
{
var token = context.Request.Cookies[".AspNetCore.Application.Id"];
if (!string.IsNullOrEmpty(token))
context.Request.Headers.Add("Authorization", "Bearer " + token);
await next();
});
app.UseAuthentication();
```
Futhermore, a lot of other tech solutions (such as [NextAuth](https://next-auth.js.org/configuration/options)) already have support for this feature.
Goals:
- [ ] Create Solution to support JWT in Session token support in-box
## In scope
A list of major scenarios, perhaps in priority order.
## Out of scope
Scenarios you explicitly want to exclude.
## Risks / unknowns
There is security concern, and we need to be careful about reviewing PR for this. Also,
## Examples
### Design proposal No.1: New middleware
We can add new middleware, which will
```cs
app.UseCookiePolicy(cookiePolicyOptions);
app.UseJwtInCookie(jwtInCookiePolicyOptions);
```
### Design proposal No.2: Different authentication scheme?
I'm not sure, if that can be considered as a different authn scheme. If so, we would be able to add jwt in cookie alongside with default jwt bearer and cookies:
```cs
builder.Services.AddAuthentication(CookieAuthenticationDefaults.AuthenticationScheme)
.AddCookie(options =>
{
// some cookie settings
})
.AddJwtBearer(options =>
{
// some jwt settings
})
.AddJwtInCookie(options =>
{
// There is an options for both cookie and jwt configuration for this?
});
```
<!--
# Detailed design
It's often best not to fill this out until you get basic consensus about the above. When you do, consider adding an implementation proposal with the following headings:
Detailed design
Drawbacks
Considered alternatives
Open questions
References
If there's one clear design you have consensus on, you could do that directly in a PR.
-->
| non_process | support for authn with jwt stored in session http only cookies this template is useful to build consensus about whether work should be done and if so the high level shape of how it should be approached use this before fixating on a particular implementation summary create in box support for authn with jwt stored in http only cookies motivation and goals then we develop spa application with asp net core for ex with react at frontend we very often think about how we implement authentication in our application there is currently two ways to do it with session cookie and with jwt as devs we prefer to use jwt because it does not require for a db lookup if we decided to use jwt there is ways to do request with it set as authorization header authorization bearer and store it locally in memory addjwtbearer set as authorization header authorization bearer and store it in browser local storage addjwtbearer pass jwt token in http only cookie the third option is currently the most secure way to pass and store jwt tokens because we become immutable to xss attack because attacker cannot read our token from cookie still we became vulnerable to csrf but this we can fix this by providing xsrf token on a client side by the end of a day we can see why jwt with http only secure cookie is preferred as authn solution using jwt s however this way is most secure asp net core does not provide in box solution for this so we need to add custom middleware to any project which uses this technique currently we implement this logic by this sort of middleware cs app usecookiepolicy cookiepolicyoptions making cookie http only strict e t c app use async context next var token context request cookies if string isnullorempty token context request headers add authorization bearer token await next app useauthentication futhermore a lot of other tech solutions such as already have support for this feature goals create solution to support jwt in session token support in box in scope a list of major scenarios perhaps in priority order out of scope scenarios you explicitly want to exclude risks unknowns there is security concern and we need to be careful about reviewing pr for this also examples design proposal no new middleware we can add new middleware which will cs app usecookiepolicy cookiepolicyoptions app usejwtincookie jwtincookiepolicyoptions design proposal no different authentication scheme i m not sure if that can be considered as a different authn scheme if so we would be able to add jwt in cookie alongside with default jwt bearer and cookies cs builder services addauthentication cookieauthenticationdefaults authenticationscheme addcookie options some cookie settings addjwtbearer options some jwt settings addjwtincookie options there is an options for both cookie and jwt configuration for this detailed design it s often best not to fill this out until you get basic consensus about the above when you do consider adding an implementation proposal with the following headings detailed design drawbacks considered alternatives open questions references if there s one clear design you have consensus on you could do that directly in a pr | 0 |
10,000 | 4,698,303,143 | IssuesEvent | 2016-10-12 12:30:39 | mitchellh/packer | https://api.github.com/repos/mitchellh/packer | closed | Packer should not delete docker container if provisioning fails. | builder/docker enhancement | I would like a option for save container even if provisioning fails.
If provisioning fails packer will stop provision and commit the container. If would be great if will be configurable option for this.
This will be helpfull for debugging e.g. puppet provisioning fails. | 1.0 | Packer should not delete docker container if provisioning fails. - I would like a option for save container even if provisioning fails.
If provisioning fails packer will stop provision and commit the container. If would be great if will be configurable option for this.
This will be helpfull for debugging e.g. puppet provisioning fails. | non_process | packer should not delete docker container if provisioning fails i would like a option for save container even if provisioning fails if provisioning fails packer will stop provision and commit the container if would be great if will be configurable option for this this will be helpfull for debugging e g puppet provisioning fails | 0 |
12,069 | 14,739,792,547 | IssuesEvent | 2021-01-07 07:56:24 | kdjstudios/SABillingGitlab | https://api.github.com/repos/kdjstudios/SABillingGitlab | closed | Medical Gas Specialist Double Payment | anc-process anp-1 ant-support has attachment | In GitLab by @kdjstudios on Sep 19, 2018, 13:20
**Submitted by:** <griselda.hernandez@answernet.com>
**Helpdesk:** http://www.servicedesk.answernet.com/profiles/ticket/2018-09-19-43644
**Server:** Internal
**Client/Site:** El Paso
**Account:** Medical Gas Specialists 025-M2725
**Issue:**
We have a client whose echeck payment was charged twice but it posted on SAB only once. Can you please tell me why? Please see below. It has been confirmed both payments were charged in our system. The account is Medical Gas Specialists 025-M2725.
Full email: [original_message__15_.html](/uploads/aa283e0b67bd38233487df2189e5543f/original_message__15_.html) | 1.0 | Medical Gas Specialist Double Payment - In GitLab by @kdjstudios on Sep 19, 2018, 13:20
**Submitted by:** <griselda.hernandez@answernet.com>
**Helpdesk:** http://www.servicedesk.answernet.com/profiles/ticket/2018-09-19-43644
**Server:** Internal
**Client/Site:** El Paso
**Account:** Medical Gas Specialists 025-M2725
**Issue:**
We have a client whose echeck payment was charged twice but it posted on SAB only once. Can you please tell me why? Please see below. It has been confirmed both payments were charged in our system. The account is Medical Gas Specialists 025-M2725.
Full email: [original_message__15_.html](/uploads/aa283e0b67bd38233487df2189e5543f/original_message__15_.html) | process | medical gas specialist double payment in gitlab by kdjstudios on sep submitted by helpdesk server internal client site el paso account medical gas specialists issue we have a client whose echeck payment was charged twice but it posted on sab only once can you please tell me why please see below it has been confirmed both payments were charged in our system the account is medical gas specialists full email uploads original message html | 1 |
10,587 | 13,396,097,127 | IssuesEvent | 2020-09-03 09:24:55 | MicrosoftDocs/azure-devops-docs | https://api.github.com/repos/MicrosoftDocs/azure-devops-docs | closed | Any condition I can use for pull requests from/to certain branches? | Pri1 devops-cicd-process/tech devops/prod doc-enhancement | Hey there,
was wondering if there was a condition I can use for pull requests from/to certain branches?
Something like:
`condition: and(succeeded(), eq(variables['Build.Reason'], 'PullRequest'), eq(variables['PullRequest.TargetBranch'], 'refs/heads/master'))`
Cheers,
Robin
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 3f151218-9a11-0078-e038-f96198a76143
* Version Independent ID: 09c4d032-62f3-d97c-79d7-6fbfd89910e9
* Content: [Conditions - Azure Pipelines](https://docs.microsoft.com/en-us/azure/devops/pipelines/process/conditions?view=azure-devops&tabs=yaml)
* Content Source: [docs/pipelines/process/conditions.md](https://github.com/MicrosoftDocs/azure-devops-docs/blob/master/docs/pipelines/process/conditions.md)
* Product: **devops**
* Technology: **devops-cicd-process**
* GitHub Login: @juliakm
* Microsoft Alias: **jukullam** | 1.0 | Any condition I can use for pull requests from/to certain branches? - Hey there,
was wondering if there was a condition I can use for pull requests from/to certain branches?
Something like:
`condition: and(succeeded(), eq(variables['Build.Reason'], 'PullRequest'), eq(variables['PullRequest.TargetBranch'], 'refs/heads/master'))`
Cheers,
Robin
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 3f151218-9a11-0078-e038-f96198a76143
* Version Independent ID: 09c4d032-62f3-d97c-79d7-6fbfd89910e9
* Content: [Conditions - Azure Pipelines](https://docs.microsoft.com/en-us/azure/devops/pipelines/process/conditions?view=azure-devops&tabs=yaml)
* Content Source: [docs/pipelines/process/conditions.md](https://github.com/MicrosoftDocs/azure-devops-docs/blob/master/docs/pipelines/process/conditions.md)
* Product: **devops**
* Technology: **devops-cicd-process**
* GitHub Login: @juliakm
* Microsoft Alias: **jukullam** | process | any condition i can use for pull requests from to certain branches hey there was wondering if there was a condition i can use for pull requests from to certain branches something like condition and succeeded eq variables pullrequest eq variables refs heads master cheers robin document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source product devops technology devops cicd process github login juliakm microsoft alias jukullam | 1 |
252,270 | 27,235,649,166 | IssuesEvent | 2023-02-21 16:08:07 | samqws-devdemo/easybuggy-groupedfindings | https://api.github.com/repos/samqws-devdemo/easybuggy-groupedfindings | opened | bootstrap-3.3.7.min.js: 6 vulnerabilities (highest severity is: 6.1) | Mend: dependency security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bootstrap-3.3.7.min.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js</a></p>
<p>Path to dependency file: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>Path to vulnerable library: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/samqws-devdemo/easybuggy-groupedfindings/commit/a509a3cbdf42888a2acceed26b22aa4b8f244207">a509a3cbdf42888a2acceed26b22aa4b8f244207</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (bootstrap version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2019-8331](https://www.mend.io/vulnerability-database/CVE-2019-8331) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.7.min.js | Direct | bootstrap - 3.4.1,4.3.1;bootstrap-sass - 3.4.1,4.3.1 | ❌ |
| [CVE-2018-14040](https://www.mend.io/vulnerability-database/CVE-2018-14040) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.7.min.js | Direct | org.webjars.npm:bootstrap:4.1.2,org.webjars:bootstrap:3.4.0 | ❌ |
| [CVE-2018-20677](https://www.mend.io/vulnerability-database/CVE-2018-20677) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.7.min.js | Direct | Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0 | ❌ |
| [CVE-2018-20676](https://www.mend.io/vulnerability-database/CVE-2018-20676) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.7.min.js | Direct | bootstrap - 3.4.0 | ❌ |
| [CVE-2018-14042](https://www.mend.io/vulnerability-database/CVE-2018-14042) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.7.min.js | Direct | org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0 | ❌ |
| [CVE-2016-10735](https://www.mend.io/vulnerability-database/CVE-2016-10735) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.7.min.js | Direct | 3.4.0 | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2019-8331</summary>
### Vulnerable Library - <b>bootstrap-3.3.7.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js</a></p>
<p>Path to dependency file: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>Path to vulnerable library: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.7.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samqws-devdemo/easybuggy-groupedfindings/commit/a509a3cbdf42888a2acceed26b22aa4b8f244207">a509a3cbdf42888a2acceed26b22aa4b8f244207</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 3.4.1 and 4.3.x before 4.3.1, XSS is possible in the tooltip or popover data-template attribute.
<p>Publish Date: 2019-02-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-8331>CVE-2019-8331</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2019-02-20</p>
<p>Fix Resolution: bootstrap - 3.4.1,4.3.1;bootstrap-sass - 3.4.1,4.3.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-14040</summary>
### Vulnerable Library - <b>bootstrap-3.3.7.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js</a></p>
<p>Path to dependency file: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>Path to vulnerable library: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.7.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samqws-devdemo/easybuggy-groupedfindings/commit/a509a3cbdf42888a2acceed26b22aa4b8f244207">a509a3cbdf42888a2acceed26b22aa4b8f244207</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 4.1.2, XSS is possible in the collapse data-parent attribute.
<p>Publish Date: 2018-07-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-14040>CVE-2018-14040</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2018-07-13</p>
<p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2,org.webjars:bootstrap:3.4.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-20677</summary>
### Vulnerable Library - <b>bootstrap-3.3.7.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js</a></p>
<p>Path to dependency file: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>Path to vulnerable library: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.7.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samqws-devdemo/easybuggy-groupedfindings/commit/a509a3cbdf42888a2acceed26b22aa4b8f244207">a509a3cbdf42888a2acceed26b22aa4b8f244207</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property.
<p>Publish Date: 2019-01-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-20677>CVE-2018-20677</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677</a></p>
<p>Release Date: 2019-01-09</p>
<p>Fix Resolution: Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-20676</summary>
### Vulnerable Library - <b>bootstrap-3.3.7.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js</a></p>
<p>Path to dependency file: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>Path to vulnerable library: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.7.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samqws-devdemo/easybuggy-groupedfindings/commit/a509a3cbdf42888a2acceed26b22aa4b8f244207">a509a3cbdf42888a2acceed26b22aa4b8f244207</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute.
<p>Publish Date: 2019-01-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-20676>CVE-2018-20676</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20676">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20676</a></p>
<p>Release Date: 2019-01-09</p>
<p>Fix Resolution: bootstrap - 3.4.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-14042</summary>
### Vulnerable Library - <b>bootstrap-3.3.7.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js</a></p>
<p>Path to dependency file: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>Path to vulnerable library: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.7.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samqws-devdemo/easybuggy-groupedfindings/commit/a509a3cbdf42888a2acceed26b22aa4b8f244207">a509a3cbdf42888a2acceed26b22aa4b8f244207</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip.
<p>Publish Date: 2018-07-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-14042>CVE-2018-14042</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2018-07-13</p>
<p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2016-10735</summary>
### Vulnerable Library - <b>bootstrap-3.3.7.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js</a></p>
<p>Path to dependency file: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>Path to vulnerable library: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.7.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samqws-devdemo/easybuggy-groupedfindings/commit/a509a3cbdf42888a2acceed26b22aa4b8f244207">a509a3cbdf42888a2acceed26b22aa4b8f244207</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap 3.x before 3.4.0 and 4.x-beta before 4.0.0-beta.2, XSS is possible in the data-target attribute, a different vulnerability than CVE-2018-14041.
<p>Publish Date: 2019-01-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-10735>CVE-2016-10735</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2019-01-09</p>
<p>Fix Resolution: 3.4.0</p>
</p>
<p></p>
</details> | True | bootstrap-3.3.7.min.js: 6 vulnerabilities (highest severity is: 6.1) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bootstrap-3.3.7.min.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js</a></p>
<p>Path to dependency file: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>Path to vulnerable library: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/samqws-devdemo/easybuggy-groupedfindings/commit/a509a3cbdf42888a2acceed26b22aa4b8f244207">a509a3cbdf42888a2acceed26b22aa4b8f244207</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (bootstrap version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2019-8331](https://www.mend.io/vulnerability-database/CVE-2019-8331) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.7.min.js | Direct | bootstrap - 3.4.1,4.3.1;bootstrap-sass - 3.4.1,4.3.1 | ❌ |
| [CVE-2018-14040](https://www.mend.io/vulnerability-database/CVE-2018-14040) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.7.min.js | Direct | org.webjars.npm:bootstrap:4.1.2,org.webjars:bootstrap:3.4.0 | ❌ |
| [CVE-2018-20677](https://www.mend.io/vulnerability-database/CVE-2018-20677) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.7.min.js | Direct | Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0 | ❌ |
| [CVE-2018-20676](https://www.mend.io/vulnerability-database/CVE-2018-20676) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.7.min.js | Direct | bootstrap - 3.4.0 | ❌ |
| [CVE-2018-14042](https://www.mend.io/vulnerability-database/CVE-2018-14042) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.7.min.js | Direct | org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0 | ❌ |
| [CVE-2016-10735](https://www.mend.io/vulnerability-database/CVE-2016-10735) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.7.min.js | Direct | 3.4.0 | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2019-8331</summary>
### Vulnerable Library - <b>bootstrap-3.3.7.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js</a></p>
<p>Path to dependency file: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>Path to vulnerable library: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.7.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samqws-devdemo/easybuggy-groupedfindings/commit/a509a3cbdf42888a2acceed26b22aa4b8f244207">a509a3cbdf42888a2acceed26b22aa4b8f244207</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 3.4.1 and 4.3.x before 4.3.1, XSS is possible in the tooltip or popover data-template attribute.
<p>Publish Date: 2019-02-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-8331>CVE-2019-8331</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2019-02-20</p>
<p>Fix Resolution: bootstrap - 3.4.1,4.3.1;bootstrap-sass - 3.4.1,4.3.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-14040</summary>
### Vulnerable Library - <b>bootstrap-3.3.7.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js</a></p>
<p>Path to dependency file: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>Path to vulnerable library: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.7.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samqws-devdemo/easybuggy-groupedfindings/commit/a509a3cbdf42888a2acceed26b22aa4b8f244207">a509a3cbdf42888a2acceed26b22aa4b8f244207</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 4.1.2, XSS is possible in the collapse data-parent attribute.
<p>Publish Date: 2018-07-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-14040>CVE-2018-14040</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2018-07-13</p>
<p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2,org.webjars:bootstrap:3.4.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-20677</summary>
### Vulnerable Library - <b>bootstrap-3.3.7.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js</a></p>
<p>Path to dependency file: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>Path to vulnerable library: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.7.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samqws-devdemo/easybuggy-groupedfindings/commit/a509a3cbdf42888a2acceed26b22aa4b8f244207">a509a3cbdf42888a2acceed26b22aa4b8f244207</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property.
<p>Publish Date: 2019-01-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-20677>CVE-2018-20677</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677</a></p>
<p>Release Date: 2019-01-09</p>
<p>Fix Resolution: Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-20676</summary>
### Vulnerable Library - <b>bootstrap-3.3.7.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js</a></p>
<p>Path to dependency file: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>Path to vulnerable library: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.7.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samqws-devdemo/easybuggy-groupedfindings/commit/a509a3cbdf42888a2acceed26b22aa4b8f244207">a509a3cbdf42888a2acceed26b22aa4b8f244207</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute.
<p>Publish Date: 2019-01-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-20676>CVE-2018-20676</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20676">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20676</a></p>
<p>Release Date: 2019-01-09</p>
<p>Fix Resolution: bootstrap - 3.4.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-14042</summary>
### Vulnerable Library - <b>bootstrap-3.3.7.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js</a></p>
<p>Path to dependency file: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>Path to vulnerable library: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.7.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samqws-devdemo/easybuggy-groupedfindings/commit/a509a3cbdf42888a2acceed26b22aa4b8f244207">a509a3cbdf42888a2acceed26b22aa4b8f244207</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip.
<p>Publish Date: 2018-07-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-14042>CVE-2018-14042</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2018-07-13</p>
<p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2016-10735</summary>
### Vulnerable Library - <b>bootstrap-3.3.7.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js</a></p>
<p>Path to dependency file: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>Path to vulnerable library: /src/main/webapp/dfi/style_bootstrap.html</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.7.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samqws-devdemo/easybuggy-groupedfindings/commit/a509a3cbdf42888a2acceed26b22aa4b8f244207">a509a3cbdf42888a2acceed26b22aa4b8f244207</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap 3.x before 3.4.0 and 4.x-beta before 4.0.0-beta.2, XSS is possible in the data-target attribute, a different vulnerability than CVE-2018-14041.
<p>Publish Date: 2019-01-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-10735>CVE-2016-10735</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2019-01-09</p>
<p>Fix Resolution: 3.4.0</p>
</p>
<p></p>
</details> | non_process | bootstrap min js vulnerabilities highest severity is vulnerable library bootstrap min js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to dependency file src main webapp dfi style bootstrap html path to vulnerable library src main webapp dfi style bootstrap html found in head commit a href vulnerabilities cve severity cvss dependency type fixed in bootstrap version remediation available medium bootstrap min js direct bootstrap bootstrap sass medium bootstrap min js direct org webjars npm bootstrap org webjars bootstrap medium bootstrap min js direct bootstrap nordron angulartemplate dynamic net express projecttemplates dotnetng template znxtapp core module theme beta jmeter medium bootstrap min js direct bootstrap medium bootstrap min js direct org webjars npm bootstrap org webjars bootstrap medium bootstrap min js direct details cve vulnerable library bootstrap min js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to dependency file src main webapp dfi style bootstrap html path to vulnerable library src main webapp dfi style bootstrap html dependency hierarchy x bootstrap min js vulnerable library found in head commit a href found in base branch master vulnerability details in bootstrap before and x before xss is possible in the tooltip or popover data template attribute publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version release date fix resolution bootstrap bootstrap sass cve vulnerable library bootstrap min js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to dependency file src main webapp dfi style bootstrap html path to vulnerable library src main webapp dfi style bootstrap html dependency hierarchy x bootstrap min js vulnerable library found in head commit a href found in base branch master vulnerability details in bootstrap before xss is possible in the collapse data parent attribute publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version release date fix resolution org webjars npm bootstrap org webjars bootstrap cve vulnerable library bootstrap min js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to dependency file src main webapp dfi style bootstrap html path to vulnerable library src main webapp dfi style bootstrap html dependency hierarchy x bootstrap min js vulnerable library found in head commit a href found in base branch master vulnerability details in bootstrap before xss is possible in the affix configuration target property publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution bootstrap nordron angulartemplate dynamic net express projecttemplates dotnetng template znxtapp core module theme beta jmeter cve vulnerable library bootstrap min js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to dependency file src main webapp dfi style bootstrap html path to vulnerable library src main webapp dfi style bootstrap html dependency hierarchy x bootstrap min js vulnerable library found in head commit a href found in base branch master vulnerability details in bootstrap before xss is possible in the tooltip data viewport attribute publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution bootstrap cve vulnerable library bootstrap min js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to dependency file src main webapp dfi style bootstrap html path to vulnerable library src main webapp dfi style bootstrap html dependency hierarchy x bootstrap min js vulnerable library found in head commit a href found in base branch master vulnerability details in bootstrap before xss is possible in the data container property of tooltip publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version release date fix resolution org webjars npm bootstrap org webjars bootstrap cve vulnerable library bootstrap min js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to dependency file src main webapp dfi style bootstrap html path to vulnerable library src main webapp dfi style bootstrap html dependency hierarchy x bootstrap min js vulnerable library found in head commit a href found in base branch master vulnerability details in bootstrap x before and x beta before beta xss is possible in the data target attribute a different vulnerability than cve publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version release date fix resolution | 0 |
253,739 | 19,178,157,547 | IssuesEvent | 2021-12-04 00:43:28 | Level/bench | https://api.github.com/repos/Level/bench | closed | Formulate goals and non-goals | discussion documentation | Because this can get unwieldy, tricky to maintain as interfaces change, and could then suffer the same fate as other level benchmarks out there. | 1.0 | Formulate goals and non-goals - Because this can get unwieldy, tricky to maintain as interfaces change, and could then suffer the same fate as other level benchmarks out there. | non_process | formulate goals and non goals because this can get unwieldy tricky to maintain as interfaces change and could then suffer the same fate as other level benchmarks out there | 0 |
10,444 | 13,223,043,765 | IssuesEvent | 2020-08-17 16:31:33 | prisma/prisma | https://api.github.com/repos/prisma/prisma | opened | Stability Re-Introspection and integrate it into normal `introspect` | kind/improvement process/candidate team/engines team/typescript topic: cli-introspect topic: introspection topic: re-introspection | https://github.com/prisma/prisma/issues/2829 is coming to an end, so we want to stabilize and release this for all users as the normal, default `prisma introspect` workflow 🚀 | 1.0 | Stability Re-Introspection and integrate it into normal `introspect` - https://github.com/prisma/prisma/issues/2829 is coming to an end, so we want to stabilize and release this for all users as the normal, default `prisma introspect` workflow 🚀 | process | stability re introspection and integrate it into normal introspect is coming to an end so we want to stabilize and release this for all users as the normal default prisma introspect workflow 🚀 | 1 |
230,559 | 7,611,630,461 | IssuesEvent | 2018-05-01 14:39:44 | datproject/dat-node | https://api.github.com/repos/datproject/dat-node | closed | dat.resumed is incorrect for empty archives | Priority: Low Type: Bug | `dat.resumed` is false if an archive was previously created but nothing written to it. Should be true. | 1.0 | dat.resumed is incorrect for empty archives - `dat.resumed` is false if an archive was previously created but nothing written to it. Should be true. | non_process | dat resumed is incorrect for empty archives dat resumed is false if an archive was previously created but nothing written to it should be true | 0 |
3,080 | 6,096,957,892 | IssuesEvent | 2017-06-20 01:03:35 | ncbo/bioportal-project | https://api.github.com/repos/ncbo/bioportal-project | closed | SCTO: latest submission failed to parse | ontology processing problem | Latest submission of the [SCTO ontology](http://bioportal.bioontology.org/ontologies/SCTO) (upload date June 12, 2017) failed to parse. Error log file shows:
```
2017-06-19T11:29:01 [main] INFO o.s.ncbo.oapiwrapper.OntologyParser - Serializing ontology in RDF ...
2017-06-19T11:29:01 [main] ERROR o.s.ncbo.oapiwrapper.OntologyParser - https://bioportal.bioontology.org/ontologies/SCTO#DTO:0001709
```
The parsing code failed to serialize the ontology source to RDF/XML format. At first glance, I believe this is the same underlying problem described in #16, which caused parsing failures for the DMTO ontology. There's an annotation declaration in the ontology source file with an invalid IRI:
```
<Declaration>
<AnnotationProperty IRI="#DTO:0001709"/>
</Declaration>
```
If the ':' character is changed to an '_', the file should parse successfully. | 1.0 | SCTO: latest submission failed to parse - Latest submission of the [SCTO ontology](http://bioportal.bioontology.org/ontologies/SCTO) (upload date June 12, 2017) failed to parse. Error log file shows:
```
2017-06-19T11:29:01 [main] INFO o.s.ncbo.oapiwrapper.OntologyParser - Serializing ontology in RDF ...
2017-06-19T11:29:01 [main] ERROR o.s.ncbo.oapiwrapper.OntologyParser - https://bioportal.bioontology.org/ontologies/SCTO#DTO:0001709
```
The parsing code failed to serialize the ontology source to RDF/XML format. At first glance, I believe this is the same underlying problem described in #16, which caused parsing failures for the DMTO ontology. There's an annotation declaration in the ontology source file with an invalid IRI:
```
<Declaration>
<AnnotationProperty IRI="#DTO:0001709"/>
</Declaration>
```
If the ':' character is changed to an '_', the file should parse successfully. | process | scto latest submission failed to parse latest submission of the upload date june failed to parse error log file shows info o s ncbo oapiwrapper ontologyparser serializing ontology in rdf error o s ncbo oapiwrapper ontologyparser the parsing code failed to serialize the ontology source to rdf xml format at first glance i believe this is the same underlying problem described in which caused parsing failures for the dmto ontology there s an annotation declaration in the ontology source file with an invalid iri if the character is changed to an the file should parse successfully | 1 |
18,064 | 10,869,362,874 | IssuesEvent | 2019-11-15 07:18:18 | terraform-providers/terraform-provider-azurerm | https://api.github.com/repos/terraform-providers/terraform-provider-azurerm | closed | Support for Azure SQL Server Managed Identity | duplicate enhancement service/mysql | <!--- Please keep this note for the community --->
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
### Description
Add support for assigning a managed identity to a SQL server.
### New or Affected Resource(s)
* azurerm_sql_server
<!--- Information about code formatting: https://help.github.com/articles/basic-writing-and-formatting-syntax/#quoting-code --->
```hcl
resource "azurerm_sql_server" "test" {
name = "mysqlserver"
resource_group_name = "${azurerm_resource_group.test.name}"
location = "${azurerm_resource_group.test.location}"
version = "12.0"
administrator_login = "mradministrator"
administrator_login_password = "thisIsDog11"
identity {
type = "SystemAssigned"
}
tags = {
environment = "production"
}
}
```
| 1.0 | Support for Azure SQL Server Managed Identity - <!--- Please keep this note for the community --->
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
### Description
Add support for assigning a managed identity to a SQL server.
### New or Affected Resource(s)
* azurerm_sql_server
<!--- Information about code formatting: https://help.github.com/articles/basic-writing-and-formatting-syntax/#quoting-code --->
```hcl
resource "azurerm_sql_server" "test" {
name = "mysqlserver"
resource_group_name = "${azurerm_resource_group.test.name}"
location = "${azurerm_resource_group.test.location}"
version = "12.0"
administrator_login = "mradministrator"
administrator_login_password = "thisIsDog11"
identity {
type = "SystemAssigned"
}
tags = {
environment = "production"
}
}
```
| non_process | support for azure sql server managed identity community note please vote on this issue by adding a 👍 to the original issue to help the community and maintainers prioritize this request please do not leave or me too comments they generate extra noise for issue followers and do not help prioritize the request if you are interested in working on this issue or have submitted a pull request please leave a comment description add support for assigning a managed identity to a sql server new or affected resource s azurerm sql server hcl resource azurerm sql server test name mysqlserver resource group name azurerm resource group test name location azurerm resource group test location version administrator login mradministrator administrator login password identity type systemassigned tags environment production | 0 |
21,336 | 29,041,783,507 | IssuesEvent | 2023-05-13 03:15:50 | gqylpy/gqylpy-dict | https://api.github.com/repos/gqylpy/gqylpy-dict | reopened | deepsetdefault执行后应该返回原值还是转为gdict实例后的值 | question Processed | `gdict.deepsetdefault` 与 `dict.setdefault` 功能相似，值不存在则设置值并返回值。若设置的值是一个 `dict` 实例且不存在，我们会先将这个 `dict` 实例转为 `gdict` 实例再执行设置，从而保证 `gdict` 实例的正确性（`gdict` 实例内层绝不包含 `dict` 实例，这是我们对 `gdict` 的理念，也是原则）。那么在返回值时，我们应该返回原 `dict` 实例还是转换后的 `gdict` 实例呢，问题的关键在于此。 | 1.0 | deepsetdefault执行后应该返回原值还是转为gdict实例后的值 - `gdict.deepsetdefault` 与 `dict.setdefault` 功能相似，值不存在则设置值并返回值。若设置的值是一个 `dict` 实例且不存在，我们会先将这个 `dict` 实例转为 `gdict` 实例再执行设置，从而保证 `gdict` 实例的正确性（`gdict` 实例内层绝不包含 `dict` 实例，这是我们对 `gdict` 的理念，也是原则）。那么在返回值时，我们应该返回原 `dict` 实例还是转换后的 `gdict` 实例呢，问题的关键在于此。 | process | deepsetdefault执行后应该返回原值还是转为gdict实例后的值 gdict deepsetdefault 与 dict setdefault 功能相似，值不存在则设置值并返回值。若设置的值是一个 dict 实例且不存在，我们会先将这个 dict 实例转为 gdict 实例再执行设置，从而保证 gdict 实例的正确性（ gdict 实例内层绝不包含 dict 实例，这是我们对 gdict 的理念，也是原则）。那么在返回值时，我们应该返回原 dict 实例还是转换后的 gdict 实例呢，问题的关键在于此。 | 1 |
20,800 | 27,553,801,176 | IssuesEvent | 2023-03-07 16:31:32 | open-telemetry/opentelemetry-collector-contrib | https://api.github.com/repos/open-telemetry/opentelemetry-collector-contrib | closed | Bump resource detection OpenShift semconv version to 1.18.0 | enhancement processor/resourcedetection/internal/openshift | ### Component(s)
processor/resourcedetection/internal/openshift
### Is your feature request related to a problem? Please describe.
We fixed the google/gcp naming in semconv 1.17.0.
### Describe the solution you'd like
Bump version to 1.17.0 or higher.
### Describe alternatives you've considered
_No response_
### Additional context
_No response_ | 1.0 | Bump resource detection OpenShift semconv version to 1.18.0 - ### Component(s)
processor/resourcedetection/internal/openshift
### Is your feature request related to a problem? Please describe.
We fixed the google/gcp naming in semconv 1.17.0.
### Describe the solution you'd like
Bump version to 1.17.0 or higher.
### Describe alternatives you've considered
_No response_
### Additional context
_No response_ | process | bump resource detection openshift semconv version to component s processor resourcedetection internal openshift is your feature request related to a problem please describe we fixed the google gcp naming in semconv describe the solution you d like bump version to or higher describe alternatives you ve considered no response additional context no response | 1 |
132 | 2,571,968,139 | IssuesEvent | 2015-02-10 19:36:51 | JarodCoding/LiseApp | https://api.github.com/repos/JarodCoding/LiseApp | closed | Offline caching for News | Feedback needed Local Processing News Optimisation | Caches all news offline and keeps them until the they aren't relevant anymore.
Speichern von News offline bis sie irrelevant werden. | 1.0 | Offline caching for News - Caches all news offline and keeps them until the they aren't relevant anymore.
Speichern von News offline bis sie irrelevant werden. | process | offline caching for news caches all news offline and keeps them until the they aren t relevant anymore speichern von news offline bis sie irrelevant werden | 1 |
202,825 | 15,303,012,117 | IssuesEvent | 2021-02-24 15:20:53 | rstudio/rstudio | https://api.github.com/repos/rstudio/rstudio | closed | Close All Others context menu command not closing all others | source editor test | ### System details
RStudio Edition : Desktop or Server
RStudio Version : 1.4.1532
OS Version : any
R Version : any
### Steps to reproduce the problem
Found by @valerie-rstudio during verification of #1664
Close All Others context menu option fails to function as expected for documents in Source Editor.
1. Open multiple documents in original Source Editor Pane.
2. Click View -> Panes -> Add Source Column, and open multiple documents in the secondary Source Editor Column.
3. Left-click on a document in the secondary column to bring it into focus.
4. Right-click on any of the document tabs in the original column and choose Close All Others
### Describe the problem in detail
- All documents close.
### Describe the behavior you expected
- All documents except the one that you right-clicked on should close.
<!--
Please keep the below portion in your issue, and check `[x]` the applicable boxes.
-->
- [x] I have read the guide for [submitting good bug reports](https://github.com/rstudio/rstudio/wiki/Writing-Good-Bug-Reports).
- [x] I have installed the latest version of RStudio, and confirmed that the issue still persists.
- [x] If I am reporting a RStudio crash, I have included a [diagnostics report](https://support.rstudio.com/hc/en-us/articles/200321257-Running-a-Diagnostics-Report).
- [x] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
| 1.0 | Close All Others context menu command not closing all others - ### System details
RStudio Edition : Desktop or Server
RStudio Version : 1.4.1532
OS Version : any
R Version : any
### Steps to reproduce the problem
Found by @valerie-rstudio during verification of #1664
Close All Others context menu option fails to function as expected for documents in Source Editor.
1. Open multiple documents in original Source Editor Pane.
2. Click View -> Panes -> Add Source Column, and open multiple documents in the secondary Source Editor Column.
3. Left-click on a document in the secondary column to bring it into focus.
4. Right-click on any of the document tabs in the original column and choose Close All Others
### Describe the problem in detail
- All documents close.
### Describe the behavior you expected
- All documents except the one that you right-clicked on should close.
<!--
Please keep the below portion in your issue, and check `[x]` the applicable boxes.
-->
- [x] I have read the guide for [submitting good bug reports](https://github.com/rstudio/rstudio/wiki/Writing-Good-Bug-Reports).
- [x] I have installed the latest version of RStudio, and confirmed that the issue still persists.
- [x] If I am reporting a RStudio crash, I have included a [diagnostics report](https://support.rstudio.com/hc/en-us/articles/200321257-Running-a-Diagnostics-Report).
- [x] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
| non_process | close all others context menu command not closing all others system details rstudio edition desktop or server rstudio version os version any r version any steps to reproduce the problem found by valerie rstudio during verification of close all others context menu option fails to function as expected for documents in source editor open multiple documents in original source editor pane click view panes add source column and open multiple documents in the secondary source editor column left click on a document in the secondary column to bring it into focus right click on any of the document tabs in the original column and choose close all others describe the problem in detail all documents close describe the behavior you expected all documents except the one that you right clicked on should close please keep the below portion in your issue and check the applicable boxes i have read the guide for i have installed the latest version of rstudio and confirmed that the issue still persists if i am reporting a rstudio crash i have included a i have done my best to include a minimal self contained set of instructions for consistently reproducing the issue | 0 |
17,237 | 22,960,537,750 | IssuesEvent | 2022-07-19 15:01:55 | chillkang/smartflix | https://api.github.com/repos/chillkang/smartflix | opened | Render shows to the homepage | 01-the-basics Rails/File processing Rails/Haml | You have just set up a Rails application with a test-driven dummy view! 🎉
In this challenge, you will update the application so the root route renders the shows from the [provided CSV file](https://www.dropbox.com/s/iqqbb64z8eogqxb/netflix_titles.zip?dl=0).
Here's how it should look by the end of this ticket:
## To complete this ticket, you will have to:
- [ ] Write a new acceptance test that asserts: when the user visits the homepage, the page content should include each show title in the [provided CSV file](https://www.dropbox.com/s/iqqbb64z8eogqxb/netflix_titles.zip?dl=0).
- [ ] Configure your Rails app to use [Haml](https://haml.info/) for the views.
- [ ] Create a new controller to show all shows. Make sure you're following the [Rails naming conventions](https://guides.rubyonrails.org/action_controller_overview.html)!
- [ ] Create a new route so that users visiting the root of your application are directed to the index action of your new controller. Make sure you're following the [Rails routing conventions](https://guides.rubyonrails.org/routing.html)!
- [ ] Pass the acceptance test by displaying all shows from the [provided CSV file](https://www.dropbox.com/s/iqqbb64z8eogqxb/netflix_titles.zip?dl=0) file.
## Tips
- There are a lot of shows in the [provided CSV file](https://www.dropbox.com/s/iqqbb64z8eogqxb/netflix_titles.zip?dl=0)! You may need to limit the number you render to the view. | 1.0 | Render shows to the homepage - You have just set up a Rails application with a test-driven dummy view! 🎉
In this challenge, you will update the application so the root route renders the shows from the [provided CSV file](https://www.dropbox.com/s/iqqbb64z8eogqxb/netflix_titles.zip?dl=0).
Here's how it should look by the end of this ticket:
## To complete this ticket, you will have to:
- [ ] Write a new acceptance test that asserts: when the user visits the homepage, the page content should include each show title in the [provided CSV file](https://www.dropbox.com/s/iqqbb64z8eogqxb/netflix_titles.zip?dl=0).
- [ ] Configure your Rails app to use [Haml](https://haml.info/) for the views.
- [ ] Create a new controller to show all shows. Make sure you're following the [Rails naming conventions](https://guides.rubyonrails.org/action_controller_overview.html)!
- [ ] Create a new route so that users visiting the root of your application are directed to the index action of your new controller. Make sure you're following the [Rails routing conventions](https://guides.rubyonrails.org/routing.html)!
- [ ] Pass the acceptance test by displaying all shows from the [provided CSV file](https://www.dropbox.com/s/iqqbb64z8eogqxb/netflix_titles.zip?dl=0) file.
## Tips
- There are a lot of shows in the [provided CSV file](https://www.dropbox.com/s/iqqbb64z8eogqxb/netflix_titles.zip?dl=0)! You may need to limit the number you render to the view. | process | render shows to the homepage you have just set up a rails application with a test driven dummy view 🎉 in this challenge you will update the application so the root route renders the shows from the here s how it should look by the end of this ticket to complete this ticket you will have to write a new acceptance test that asserts when the user visits the homepage the page content should include each show title in the configure your rails app to use for the views create a new controller to show all shows make sure you re following the create a new route so that users visiting the root of your application are directed to the index action of your new controller make sure you re following the pass the acceptance test by displaying all shows from the file tips there are a lot of shows in the you may need to limit the number you render to the view | 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.