primordic/IssueDupesLite huggingface dataset:
Repository: ant-media/Ant-Media-Server

Issue #6756: VP8 Flutter SDK issue
Created: 2024-11-04T10:21:31Z
Short description
When trying to publish from our sample applications when VP8 is not enabled the app crashes after 5 seconds
Environment

Operating system and version: Android 14
Java version: 17
Ant Media Server version: Enterprise Edition 2.11.3 20240906_0602

Steps to reproduce

Launch one of the sample applications that uses the publish method from our sdk
Publish to a application that has the h.264 webrtc codec support enabled
On the Ant Media dashboard you will see the stream preparing for a few seconds and from the app's side it return an exception

Expected behavior
Publish a stream without issues
Actual behavior
Crash after a few seconds

Duplicate issue #6666: [Flutter] Mute audio not working fine
Created: 2024-09-24T08:36:49Z
Short description
When clicked on mute while broadcasting, the viewers' stream is paused without any exception until the broadcaster unmutes himself
Environment

Operating system and version: Android 13, iOS 15.2
Java version: JDK 17
Ant Media Server version: Enterprise Edition 2.10.0 20240705_1152
Browser name and version: Chrome 128.0.6613.139

Steps to reproduce

Publish a Webrtc stream using antmedia_flutter
Start watching the stream (using mobile or Antmedia sample)
Mute the microphone on broadcaster side
The viewers' stream is paused without any exception. The broadcaster is unaware.

Expected behavior
Muting of microphone should not pause the stream on viewer's end
Actual behavior
The viewers' stream is paused without any exception. The broadcaster is unaware.
This happens for every viewer atleast once
Logs
NA
Ask your questions on Ant Media Github Discussions

Closing comment (2024-11-04T10:57:33Z): Could this be related to #6756 ?
Repository: ant-media/Ant-Media-Server

Issue #3677: Provide options to have different permissions on uploading S3 objects
Created: 2021-10-16T14:47:01Z
Ant Media Server uploads ts and mp4 file to S3 with public-read access. However, it should be configurable through settings.  The following values should be supported
* public-read
* private
* public-read-write
* authenticated-read
* log-delivery-write
* bucket-owner-read
* bucket-owner-full-control
* aws-exec-read
Describe the solution you'd like
There should be a configuration parameter that we can set the permission of the files to be uploaded in Application settings

Duplicate issue #3483: Make configurable S3 Access control permission
Created: 2021-07-28T14:05:31Z
Make configurable S3 Access control permission. It's public-read by default.

Closing comment (2021-10-18T08:52:21Z): Duplicate #3677
Repository: ant-media/Ant-Media-Server

Issue #2155: Force WebRTC Player to play the specified quality in adaptive bitrates
Created: 2020-05-13T10:11:49Z

Duplicate issue #2154: Force WebRTC Player to play the specified quality 
Created: 2020-05-13T10:11:41Z

Closing comment (2020-08-10T10:59:40Z): Duplicate #2155
Repository: antlr/antlr4

Issue #118: No viable alternative can be incorrectly thrown for start rules without explicit EOF
Created: 2013-01-02T15:17:01Z
If the start rule does not contain an explicit EOF transition, ParserATNSimulator.adaptivePredict may fail to return a viable alternative.
Grammar:
start : ID | ID INT ID;
ID : [a-z]+;
INT : [0-9]+;
WS : [ \t]+ -> skip;

Input: x 1

Duplicate issue #509: Incorrect rule chosen in unambiguous grammar
Created: 2014-03-22T18:06:50Z
The following grammar:
grammar TA;
prog: statement*;
statement: letterA | statement letterA 'b' ;
letterA: 'a';

Correctly parses the string a as a single statement, and correctly parses aab as (prog (statement (statement (letterA 'a')) (letterA 'a') 'b')).
I would expect that aa would be parsed as two separate statements:
(prog (statement (letterA 'a')) (statement (letterA 'a')))

Since that is the only possible choice. However the parser does not choose this rule, and the parse of aa fails with the following error:
line 1:2 missing 'b' at '<EOF>'

The following grammar, which replaces letterA with a lexer rule LetterA, parses aa correctly:
grammar TA;
prog: statement*;
statement: LetterA | statement LetterA 'b' ;
LetterA: 'a';

I would expect both grammars to produce the same result.

Closing comment (2014-03-22T23:44:15Z): Change prog: statement*; to prog: statement* EOF;. If the result is a successful parse, then this is a duplicate of #118. Otherwise, reopen the issue since it's something else.
Repository: antlr/antlr4

Issue #3266: Drop Python2 runtime support
Created: 2021-09-04T14:59:09Z
Python2 is not officially supported since January 1st, 2020: https://www.python.org/doc/sunset-python-2/
I think now it's time to stop supporting it in ANTLR because it consumes additional resources.
Also, there are a lot of code in common between Python2 and Python3 runtimes.

Duplicate issue #4325: [CI testing] Build fails because Python2 is no longer supported on Github Actions.
Created: 2023-06-21T11:46:25Z
From the build:
 Warning: The support for python 2.7 will be removed on June 19. Related issue: https://github.com/actions/setup-python/issues/672
  Version 2.x was not found in the local cache
  Error: The version '2.x' with architecture 'x64' was not found for macOS 11.7.7.
  The list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json

Yes, what day is it today?? June 21.
We can't test the Python2 Antlr target anymore. We really should not be trying to support Python 2 with Antlr. Drop the target.

Closing comment (2023-06-21T13:01:31Z): It's duplicate: #3266
Repository: antlr/antlr4

Issue #994: Another poor performance about expression parsing
Created: 2015-09-15T13:13:12Z
I'm using ANTLR-4.4 with a grammar file modified from sqlite.g4,and find  some complex expressions cost too much time to parse.And then I found  issue#192 .
That grammar file works fast with the antlr version I'm using now.But when I add some rules I used in my grammar file,it get slow down.
To make the issue simple,the grammar I use is just like this:
grammar expr;

expr: ID
    | 'not' expr
    | expr 'and' expr
    | expr 'or' expr
    | expr 'between' expr 'and' expr
    ;

ID: [a-zA-Z_][a-zA-Z_0-9]*;
WS: [ \t\n\r\f]+ -> skip;
ERROR: .;

and the sample file is just same like
not X1 and not X2 and not X3 and not X4 and not X5 and not X6 and not X7 and not X8 and not X9 and not X10 and not X11 and not X12 or
    X1 and not X2 and not X3 and not X4 and not X5 and not X6 and not X7 and not X8 and not X9 and not X10 and not X11 and not X12 or
not X1 and     X2 and not X3 and not X4 and not X5 and not X6 and not X7 and not X8 and not X9 and not X10 and not X11 and not X12

I tried this with the antlr plugin in IDEA,just 3 lines of the expressions will make the parsing time unacceptable.

Duplicate issue #1323: Issue with Antlr4 Java 7 Grammar expression Parser rule
Created: 2016-11-05T14:07:19Z
I found this issue for the following input
public String publishAbsencesApprovalsEvent(Map<String,Object> absenceValues) {
// inside this method there is a pretty much long string which spans around 150 lines.
}
When I try to create a ParseTree for this input file, it's got hanged like forever. I guess there is a decision-making issue for the grammar for the below two rules.
typeArguments
: '<' typeArgument (',' typeArgument)* '>'
;
expression
: //many alternatives
| expression ('<=' | '>=' | '>' | '<') expression #logical
When I commented out the #logical alternative and re-ran it's worked.
I guess there is a token matching decision from lexer to Parser level which makes it hang forever.
Please let me know if there is a solution for this without altering much of the grammar file.

Closing comment (2016-11-22T22:57:33Z): Dup of #994
Repository: antlr/antlr4

Issue #337: Antlr4 code generator throws exception under java 8
Created: 2013-10-02T09:30:08Z
I'm getting IndexOutOfBoundsException while trying to generate classes with Antlr Tool under Java 8.Under Java 7 same command with same grammar run's without issues.
This command:
java -cp antlr-4.1-complete.jar org.antlr.v4.Tool %* antlr4.bat MidasMain.g4 -package some.pkg.name  -visitor  -o ..\src\antlr4folder
Causes following exception:
 Exception in thread "main" java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
        at java.util.ArrayList.rangeCheck(Unknown Source)
        at java.util.ArrayList.get(Unknown Source)
        at org.antlr.v4.misc.OrderedHashMap.getElement(OrderedHashMap.java:46)
        at org.antlr.v4.analysis.LeftRecursiveRuleTransformer.setAltASTPointers(LeftRecursiveRuleTransformer.java:241)
        at org.antlr.v4.analysis.LeftRecursiveRuleTransformer.translateLeftRecursiveRule(LeftRecursiveRuleTransformer.java:162)
        at org.antlr.v4.analysis.LeftRecursiveRuleTransformer.translateLeftRecursiveRules(LeftRecursiveRuleTransformer.java:89)
        at org.antlr.v4.semantics.SemanticPipeline.process(SemanticPipeline.java:94)
        at org.antlr.v4.Tool.processNonCombinedGrammar(Tool.java:399)
        at org.antlr.v4.Tool.process(Tool.java:384)
        at org.antlr.v4.Tool.processGrammarsOnCommandLine(Tool.java:343)
        at org.antlr.v4.Tool.main(Tool.java:190)
Issue can be reproduced with antlr 4.0 and antlr 4.1 under java 8
java version "1.8.0-ea"
Java(TM) SE Runtime Environment (build 1.8.0-ea-b108)
Java HotSpot(TM) 64-Bit Server VM (build 25.0-b50, mixed mode)

Duplicate issue #446: NullPointerException using JRE8
Created: 2014-01-24T00:05:54Z
Running 'java org.antlr.v4.Tool tour/Expr.g4'
Throws this:
Exception in thread "main" java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.rangeCheck(Unknown Source)
at java.util.ArrayList.get(Unknown Source)
at org.antlr.v4.misc.OrderedHashMap.getElement(OrderedHashMap.java:46)
at org.antlr.v4.analysis.LeftRecursiveRuleTransformer.setAltASTPointers(LeftRecursiveRuleTransformer.java:241)
at org.antlr.v4.analysis.LeftRecursiveRuleTransformer.translateLeftRecursiveRule(LeftRecursiveRuleTransformer.java:162)
at org.antlr.v4.analysis.LeftRecursiveRuleTransformer.translateLeftRecursiveRules(LeftRecursiveRuleTransformer.java:89)
at org.antlr.v4.semantics.SemanticPipeline.process(SemanticPipeline.java:94)
at org.antlr.v4.Tool.processNonCombinedGrammar(Tool.java:399)
at org.antlr.v4.Tool.process(Tool.java:384)
at org.antlr.v4.Tool.processGrammarsOnCommandLine(Tool.java:343)
at org.antlr.v4.Tool.main(Tool.java:190)
The problem is the java version, I used JRE 8:
java version "1.8.0-ea"
Java(TM) SE Runtime Environment (build 1.8.0-ea-b121)
Java HotSpot(TM) 64-Bit Server VM (build 25.0-b63, mixed mode)
When run java -version:1.7 org.antlr.v4.Tool tour/Expr.g4, no problem.
tour/Expr.g4 code is in https://github.com/stfairy/learn-antlr4/blob/master/tpantlr2-code/tour/Expr.g4
Thanks.

Closing comment (2014-01-24T00:21:47Z): duplicate of #337
Repository: antlr/antlr4

Issue #2860: Stack overflow using a grammar that has an extraneous | in a token definition
Created: 2020-07-04T16:05:46Z
Minimal grammar:
grammar test;                                                                            
                                                                                        
TILDE: '~';                                                                              
                                                                                         
fragment                                                                                 
QSTRING: (TILDE|)+;                                                                      
                                                                                         
QUOTED_VALUE:  '\'' QSTRING? '\'' ;                                                      
                                                                                     
single_value: QUOTED_VALUE ;                                                             

Building and running results in a stack overflow.
I saw this first on the Python runtime and then the same issue on the Java runtime (using grun).
This is using antlr-4.8-complete.jar.
antlr4 *.g4 && javac *.java && echo -n "'~'" |  grun test single_value -tokens
Exception in thread "main" java.lang.StackOverflowError                                  
        at org.antlr.v4.runtime.misc.Array2DHashSet.getOrAdd(Array2DHashSet.java:59)     
        at org.antlr.v4.runtime.atn.ATNConfigSet.add(ATNConfigSet.java:146)              
        at org.antlr.v4.runtime.atn.ATNConfigSet.add(ATNConfigSet.java:122)              
        at org.antlr.v4.runtime.atn.LexerATNSimulator.closure(LexerATNSimulator.java:446)
        at org.antlr.v4.runtime.atn.LexerATNSimulator.closure(LexerATNSimulator.java:455)
        at org.antlr.v4.runtime.atn.LexerATNSimulator.closure(LexerATNSimulator.java:455)

Duplicate issue #1105: avoid java.lang.StackOverflowError
Created: 2016-02-05T22:21:45Z
see http://stackoverflow.com/questions/31193527/stackoverflowerror-in-antlr4
The LexerATNSimulator should IMHO give up after a certain number of recursions before the StackOverflowError happens and spit out some information what is going on to help debug the grammer that causes the problem.
java.lang.StackOverflowError
    at org.antlr.v4.runtime.atn.LexerATNSimulator.getEpsilonTarget(LexerATNSimulator.java:499)
    at org.antlr.v4.runtime.atn.LexerATNSimulator.closure(LexerATNSimulator.java:480)
    at org.antlr.v4.runtime.atn.LexerATNSimulator.closure(LexerATNSimulator.java:482)
    at org.antlr.v4.runtime.atn.LexerATNSimulator.closure(LexerATNSimulator.java:482)
...

Closing comment (2021-11-09T17:00:16Z): Seems like it's related to #2860
Also, I don't think it's about a halting problem rather a bug in runtime. Because there is stack overflow even for such a simple sample (for input 'x'):
TOKEN1: '\'' FRAGMENT1 '\'';
fragment FRAGMENT1: ('x'|)+;
But everything works fine if an empty alternative is replaced with optional:
TOKEN2: '\'' FRAGMENT2 '\'';
fragment FRAGMENT2: 'x'*;
Repository: antlr/antlr4

Issue #118: No viable alternative can be incorrectly thrown for start rules without explicit EOF
Created: 2013-01-02T15:17:01Z
If the start rule does not contain an explicit EOF transition, ParserATNSimulator.adaptivePredict may fail to return a viable alternative.
Grammar:
start : ID | ID INT ID;
ID : [a-z]+;
INT : [0-9]+;
WS : [ \t]+ -> skip;

Input: x 1

Duplicate issue #605: Whitespace skips accept "3 3" as (expr 3)
Created: 2014-06-05T09:31:01Z
A very simple grammar to understand:
grammar Expr;
expr : INT;
INT  : [0-9]+ ;
WS   : [ \t\r\n]+ -> skip;
accepts "3 3" and it parses the string as (expr 3).
Fortunately if one try with one as the example in the home page:
grammar Expr;        
expr:   expr ('*'|'/') expr
    |   expr ('+'|'-') expr
    |   INT
    |   '(' expr ')'
    ;
INT     : [0-9]+ ;
WS : [ \t\r\n]+ -> skip;
it returns the error "line 1:2 extraneous input '3' expecting {, '+', '*', '-', '/'}" and seems to work.
But, despite of that, with the strategy BailErrorStrategy no error are thrown.
Thank you. ANTLR4 it's very powerful and simple!

Closing comment (2014-06-05T12:53:05Z): That last example is absolutely correct. You would need to provide input "ab" to get it to use the second alternative.
The first example is also correct. The only error is the grammar with operators, and the bug is either a duplicate of #118, or it's one that we fixed in the latest release. Are you using 4.2.2?
ANTLR is allowed to parse only part of the input sequence of you do not start parsing at a rule that ends with an explicit EOF.
Repository: antlr/antlr4

Issue #1295: $e.v yields incorrect value 0 in "e returns [int v] : '1' {$v = 1;} | '(' e ')' {$v = $e.v;} ;"
Created: 2016-09-28T04:21:29Z
The incorrect result can be seen in the Interactive Calculator example (actions/tools/Expr.g4) in chapter 10 of the ANTLR4 book, page 181, in which parenthesized expressions always yield 0.
When a rule invokes itself recursively, and no label is used, incorrect code is generated when an action references either a variable returned by the recursive call, or any of the subexpression's predefined attributes text, start, stop, or ctx. The generated code refers to the current rule's context;  instead it should refer to the child's context. In the calculator example, $e.v incorrectly accesses _localctx.v (the field where the current rule should put its result, which is initially 0 if numeric or null if a reference type). Thus, the example action assigns the uninitialized field to itself. Instead it should access _localctx.e.v (the result from the recursive invocation).
The problem does not occur when the grammar assigns a label renaming the self-invocation - for example, it would be ok if changed to '(' ee=e ')' {$v = $ee.v;} ;

Duplicate issue #1096: Bug in generated JavaScript for recursive rule action
Created: 2016-01-23T17:33:44Z
I have a LISP-style recursive list construct in my grammar like so:
// we do this the old-fashioned way because that's what the compiler wants
statement_list returns [retVal]
    : statement {$retVal = {type: "stmt_list", head: $statement.retVal, tail: null};}
    | statement statement_list {$retVal = {type: "stmt_list", head: $statement.retVal, tail: $statement_list.retVal};}
    ;
I'm using actions to build up an AST in the form of nested JS objects. However, the tail property is always null for the second rule where it should be non-null. When I look at the generated code, I see
localctx.retVal =  {type: "stmt_list", head: localctx._statement.retVal, tail: localctx.retVal}
The tail property is being set to the (unset) retVal attribute of the local context, not the sub-context pertaining to the recursive statement_list rule, and that's why it's always null. The code should be generated as:
localctx.retVal =  {type: "stmt_list", head: localctx._statement.retVal, tail: localctx._statement_list.retVal}
When I make the change by hand to the generated parser, it works like a charm.

Closing comment (2016-11-22T20:31:19Z): Dup of #1295 I think.
Repository: antlr/antlr4

Issue #683: ANTLR generate code into incorrect path
Created: 2014-08-23T13:09:53Z
If I use following string to generate lexer and parser from grammar:
$ java -cp antlr4-complete-4.4-bin.jar org.antlr.v4.Tool -o src/my/package -package my.package MyGrammar.g4

code will be placed into correct path -- into src/my/package directory.
But if I use following string:
$ java -cp antlr4-complete-4.4-bin.jar org.antlr.v4.Tool -o src/my/package -package my.package grammars/MyGrammar.g4

code will be placed into src/my/package/grammars directory! Also one directory grammars will be added!

Duplicate issue #686: Tool issue: Output Directory Must Assume Package Structure
Created: 2014-08-27T13:07:27Z
Running the ANTLR4 Tool (target language is Java) as below:
org.antlr.v4.Tool -o antlr-generated -package antlr.generated Foo.g4
Running this results in build errors... the generated files are placed in the default package. I can get around this by specifying the package structure in my file output argument like this:
org.antlr.v4.Tool -o antlr-generated/antlr/generated -package antlr.generated Foo.g4
Is there a particular reason that Tool does not create this package structure for me?

Closing comment (2014-08-27T13:26:15Z): This appears to be a duplicate of #683
Repository: antlr/antlr4

Issue #546:  no viable alternative at input '..'
Created: 2014-04-13T22:43:28Z
why?
I've grammar:
    grammar Regulars;
    start : test ;
    test : 'a' .. 'z';

and can't generate anything:
log https://gist.github.com/Morgaroth/10605312
I'm using antlr-4.2.2-complete.jar

Duplicate issue #547: Error range  .. 
Created: 2014-04-13T23:15:40Z
Hello, I've a problem, I think form deep of library
grammar:
    grammar Regulars;
    start : regex ;
    regex : 'a' .. 'z' ;

And I cannot compile it
error log https://gist.github.com/Morgaroth/10605312
I'm using antlr-4.2.2-complete.jar

Closing comment (2014-04-13T23:23:33Z): Duplicate of #546
Repository: antlr/antlr4

Issue #542: First alternative cannot be right-associative
Created: 2014-04-07T01:53:30Z
The following grammar demonstrates this issue:
grammar T;
a : B | 'c' ;

e :<assoc=right> e '*' e
  | 'x'
  ;

B : 'b';
The following exception is produced:
ATNBuilder.g: node from line 4:3 no viable alternative at input 'ELEMENT_OPTIONS'
Exception in thread "main" java.lang.NullPointerException
 at org.antlr.v4.automata.ParserATNFactory.makeBlock(ParserATNFactory.java:455)
 at org.antlr.v4.automata.ParserATNFactory.block(ParserATNFactory.java:427)
 at org.antlr.v4.parse.ATNBuilder.ruleBlock(ATNBuilder.java:307)
 at org.antlr.v4.automata.ParserATNFactory._createATN(ParserATNFactory.java:184)
 at org.antlr.v4.automata.ParserATNFactory.createATN(ParserATNFactory.java:134)
 at org.antlr.v4.Tool.processNonCombinedGrammar(Tool.java:405)
 at org.antlr.v4.Tool.process(Tool.java:384)
 at org.antlr.v4.Tool.processGrammarsOnCommandLine(Tool.java:343)
 at org.antlr.v4.Tool.main(Tool.java:190)

Duplicate issue #568: crash during normal use of Antlrv4.2.2
Created: 2014-05-19T00:49:44Z
Just compiling a grammar gives this - though at least the generated files are produced. line 7 is just the grammar declaration. ELEMENT_OPTIONS and 'right' do not appear in the file.
ANTLR Tool v4.2.2 (C:\Users\dcok\AppData\Local\Temp\antlr-4.2.2-complete.jar)
ACSL.g4 -o C:\cygwin\home\sb-bj\trunk\nasa-speedy\annotationEditor\target\generated-sources\antlr4\speedy\acsl\antlr -listener -no-visitor -encoding UTF-8
org\antlr\v4\parse\ATNBuilder.g: node from line 7:10 no viable alternative at input 'ELEMENT_OPTIONS'
org\antlr\v4\parse\ATNBuilder.g: node from line 7:17 no viable alternative at input 'right'
Exception in thread "main" java.lang.NullPointerException
at org.antlr.v4.automata.ParserATNFactory.elemList(ParserATNFactory.java:484)
at org.antlr.v4.automata.ParserATNFactory.alt(ParserATNFactory.java:473)
at org.antlr.v4.parse.ATNBuilder.alternative(ATNBuilder.java:568)
at org.antlr.v4.parse.ATNBuilder.ruleBlock(ATNBuilder.java:290)
at org.antlr.v4.automata.ParserATNFactory._createATN(ParserATNFactory.java:184)
at org.antlr.v4.automata.ParserATNFactory.createATN(ParserATNFactory.java:134)
at org.antlr.v4.Tool.processNonCombinedGrammar(Tool.java:405)
at org.antlr.v4.Tool.process(Tool.java:384)
at org.antlr.v4.Tool.processGrammarsOnCommandLine(Tool.java:343)
at org.antlr.v4.Tool.main(Tool.java:190)

Closing comment (2014-05-21T19:05:00Z): Duplicate of #542
Repository: apache/accumulo

Issue #1390: Declare core.iterators package public API
Created: 2019-10-22T19:47:03Z
This is something that is long overdue but has been put off for good reasons.  Some refactoring was done in 2.0 for classes in this package to not use internal types.  SortedKeyValueIterator should be declared public API and I think this package is close to this goal where it could be done for 2.1

Duplicate issue #1415: Update Apilyzer to treat core.iterators as SPI
Created: 2019-11-07T21:44:04Z
Refactoring done for #1390 requires the Apilyzer plugin to run on core.iterators, ensuring there is no internal types in the API.

Closing comment (2020-01-21T17:03:45Z): Related to #1390
Repository: apache/accumulo

Issue #1377: Add table ID sanity checks to garbage collector
Created: 2019-09-27T17:25:09Z
Currently the Accumulo GC checks that each user table seen in the metadata table is properly formed (this check was recently improved by #1266). However there is no check to ensure all expected user tables are seen in the metadata table.  So if there is an error and nothing is seen for a user table in the metadata table, then the Accumulo GC will not know there is a problem.
The garbage collection algorithm reads a set of delete candidates into memory and then scans the metadata table to remove any candidates that a referenced.  Sanity checks could added to cross reference tables ids seen in the metadata table with zookeeper.
One possible way to do this is with the following three sets :

BSTI : Table ids in zookeeper before the scan.  Excluding some table states like NEW and DELETING.
UMTI : Table ids seen while scanning metadata table
ASTI : Table ids in zookeeper after the scan. Excluding some table states like NEW and DELETING.

If (BSTI ∩ ASTI) ⊆ UMTI  is true then all expected table ids were seen.  If its not true, then its not safe to delete files.  Building these sets and checking them in the GC before deleting could make the Accumulo GC more robust against unknown errors when scanning the metadata table.

Duplicate issue #1267: Research if Ample should have sanity checks for no tablets seen
Created: 2019-07-11T19:33:27Z
While working on #1260 I realized that Ample could possibly check for the case of no tablets for a table seen and throw an exception.  This could be done when consistency checking is requested.  Not sure if this is worthwhile.  Need to look at code that scans metadata table and see if it would behave badly if for some reason the metadata scan returned nothing.

Closing comment (2020-02-11T22:16:57Z): @milleruntime I think this is more similar to #1377.  I was thinking of the case where the master and gc scan the metadata table and the scan returns zero tablets.  I think this issue is too vague and could be closed in favor of #1377
Repository: apache/accumulo

Issue #4315: Validate Compaction services work across upgrades
Created: 2024-02-28T14:33:51Z
Is your feature request related to a problem? Please describe.
The compaction properties have undergone many changes across the 2.1/3.1/elasticity branches.
External compactions should be tested as a function of the upgrade job.
** Items to consider **

Outdated dispatcher props left defined at the table level.
Outdated compaction service props left defined.

Describe the solution you'd like
Compaction services should function after an upgrade without issue.

Duplicate issue #4587: Implement upgrade from 3.1 to 4.0
Created: 2024-05-22T18:45:48Z
The elasticity branch does not currently have functioning upgrade code.  Need to implement upgrade from 3.1 to 4.0.

Closing comment (2024-06-27T22:48:53Z): Compared the files Constants.java, MetadataSchema.java, and Property.java across  elasticity and main branches.  Analyzing  Constants.java resulted in opening #4712 and #4713.   Looking at MetadataSchema.java did not see anything to do, did notice #4637.
Looking at Property.java the only table property that was removed was table.compaction.selector.  Wondering if we want to delete this if it exists on upgrade.   There are also some properties that could have been set at the system level that were deleted.  This is related to #4315, but more general.
Repository: apache/accumulo

Issue #547: IllegalStateException: Active assignment already exists
Created: 2018-07-02T22:05:48Z
Encountered this exception while running continuous ingest on 1.9 branch.
Thread "tablet assignment 1" died Active assignment already exists for 2;7666c;759a09
	java.lang.IllegalStateException: Active assignment already exists for 2;7666c;759a09
		at org.apache.accumulo.tserver.ActiveAssignmentRunnable.run(ActiveAssignmentRunnable.java:54)
		at org.apache.htrace.wrappers.TraceRunnable.run(TraceRunnable.java:57)
		at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
		at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
		at org.apache.accumulo.fate.util.LoggingRunnable.run(LoggingRunnable.java:35)
		at java.lang.Thread.run(Thread.java:748)

Duplicate issue #563: Exception while running continuous ingest
Created: 2018-07-17T15:02:48Z
Encountered this error/exception while running continuous ingest. It looks like it could be a normal/expected behavior.  If so, the exception should stop being thrown and a debug message should be printed instead.
2018-07-17 02:52:03,429 [util.NamingThreadFactory] ERROR: Thread "tablet assignment 2" died Active assignment already exists for 2;49999;48ccf
java.lang.IllegalStateException: Active assignment already exists for 2;49999;48ccf
        at org.apache.accumulo.tserver.ActiveAssignmentRunnable.run(ActiveAssignmentRunnable.java:54)
        at org.apache.htrace.wrappers.TraceRunnable.run(TraceRunnable.java:57)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at org.apache.accumulo.fate.util.LoggingRunnable.run(LoggingRunnable.java:35)
        at java.lang.Thread.run(Thread.java:748)

Closing comment (2018-07-17T15:21:40Z): This is a duplicate of #547
Repository: apache/accumulo

Issue #2182: Make DeleteTable block future compactions
Created: 2021-06-28T18:20:09Z
PR #2175 wrapped up the task of ensuring currently running compactions are canceled. However, new compactions could still be scheduled, stalling the DeleteTable operation. It should be possible to set a value in ZK that would prevent any future compactions from being scheduled, so they are preemptively canceled and won't stall the DeleteTable operation.
See discussion in comment #2175 (comment)

Duplicate issue #2206: Add pre-emption to fate
Created: 2021-07-16T19:30:26Z
Original issue from Jira ticket: https://issues.apache.org/jira/browse/ACCUMULO-2633 and somewhat related to another Jira ticket: https://issues.apache.org/jira/browse/ACCUMULO-2119.
Snippet from the ticket:
It would be nice if FATE operations could be pre-empted. 
For example, if a compaction is running and a user issues a table delete, 
then the compaction does not need to be completed because that data will be dropped anyway.

The second ticket relates to canceling an ongoing compaction if a table delete is issued. That could be done in a separate issue but I included them together for now.

Closing comment (2021-07-16T21:01:19Z): This, and the two referenced JIRA issues seem very similar to #2182 in their intended outcome. I don't think we have a strong need to change FaTE's architecture to support preemption more generically than that.
Repository: apache/accumulo

Issue #3463: Update external compactions to support metadata and root tablet
Created: 2023-06-09T03:19:57Z
External compactions are currently only supported for user tablets.  This must be done to support removing internal compactions running in the tserver.

Duplicate issue #3518: Ensure that root and metadata table can compact externally.
Created: 2023-06-22T20:20:07Z
After #3513 is merged there theoretically should be enough basic support for compacting the root and metadata tables via external compactions, but it probably does not work.  Need to work towards getting these compacting via external compactions.  Also need to explore if some basic ITs are needed to ensure that the root and metadata tablets are compacting going forward.

Closing comment (2023-06-22T22:38:34Z): This is a duplicate of #3463.
Repository: apache/accumulo

Issue #1841: Broken or Flaky test: ConcurrentDeleteTableIT takes 30 minutes to run!!!
Created: 2020-12-17T21:07:26Z
Test name(s)

ConcurrentDeleteTableIT.testConcurrentDeleteTablesOps took 587 seconds (nearly 10 minutes)
ConcurrentDeleteTableIT.testConcurrentFateOpsWithDelete took 1,152 seconds (nearly 20 minutes)

Describe the failure observed
These tests take WAY too long to run. There has to be a better way to get the coverage needed from these tests.
Testing Environment:

Version of this project: 2.1.0-SNAPSHOT
First commit known to fail (or current commit): 243e577

Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /home/christopher/apps/maven/current
Java version: 11.0.9.1, vendor: Red Hat, Inc., runtime: /usr/lib/jvm/java-11-openjdk-11.0.9.11-4.fc32.x86_64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.9.13-100.fc32.x86_64", arch: "amd64", family: "unix"

What have you tried already?
mvn clean verify -Dtest=nosuchtest -Dit.test=ConcurrentDeleteTableIT -PskipQA -DskipTests=false -DskipITs=false

Additional context
On a Jenkins instance I run, I've seen these tests time out after 10 minutes before retrying them. I'm not sure why, though, because the test doesn't have a timeout configured. It's possible Jenkins does, though. If that's the case, it'd be weird that it wouldn't fail more often if one test takes 20 minutes to pass... it would mean that sometimes it takes less than 10 minutes to pass, which is a wide variance, even on different hardware.

Duplicate issue #2292: ConcurrentDeleteTableIT Timing Out
Created: 2021-09-28T20:21:53Z
ConcurrentDeleteTableIT is consistently failing as of late by way of timeout. The problem seems to be with testConcurrentDeleteTablesOps. Looking at the logs the Manager process did not appear to start. I did not see any errors though.

Closing comment (2021-09-28T20:23:16Z): Duplicate of #1841
Repository: apache/accumulo

Issue #3663: Always initiate log recovery for tablets
Created: 2023-07-27T20:58:13Z
Currently in the elasticity branch walog recovery is only done when tablet is hosted on a tablet server. With the introduction of on demand tablets its possible that after a tablet server fails that the tablet is never rehosted and data for the logs is never recovered from the tablets.  This has two negative consequences.  First it will prevent Accumulo GC from ever deleting those walogs.  Second it will prevent the data from ever being seen by eventual scans.  Tablets in this state should be recovered ASAP to avoid these problems.

Duplicate issue #3880: Handle tablets that have a hosting goal of never and WALs
Created: 2023-10-23T20:06:05Z
If tablets have a hosting goal of never and also have write ahead logs, it could cause problems as outlined in the following comment.
#3844 (comment)

Closing comment (2023-10-23T22:16:07Z): Closed this because it was a duplicate of #3663
Repository: apache/cordova-plugin-inappbrowser

Issue #526: Android InAppBrowser option to not use fullscreen layout
Created: 2019-08-21T15:38:23Z
Feature Request
Motivation Behind Feature
Provide an option to conditionally set FLAG_FULLSCREEN for window flags when creating main dialog.
Feature Description
On Android, defaulting to FLAG_FULLSCREEN, hides the Android title bar / status bar. It would be nice to have an InAppBrowserOption to set another flag option to show the status bar.

Duplicate issue #469: After forking the inappbroswer is covering status bar in Android.
Created: 2019-04-29T02:20:41Z
Bug Report
Problem
What is expected to happen?
What does actually happen?
Information

Command or Code

Environment, Platform, Device

Version information

Checklist


 I searched for existing GitHub issues
 I updated all Cordova tooling to most recent version
 I included all the necessary information above

Closing comment (2019-10-31T16:20:00Z): It seems that this issue is related to #526.
ec6af56 is the commit that changed this behavior between 3.0.0 and 3.1.0.
Maybe it should be an option like 'statusbar=no' rather than default behavior?
EDIT: Sorry linked the wrong issue.
Repository: apache/cordova-plugin-inappbrowser

Issue #1039: Cannot build iOS Ionic Capacitor project
Created: 2023-11-27T08:34:24Z
Building for iOS using cordova-plugin-inappbrowser 6.0.0 fails.
...
/Users/user/project/ios/capacitor-cordova-ios-plugins/sources/CordovaPluginInappbrowser/CDVWKInAppBrowser.m:22:9: fatal error: 'Cordova/CDVWebViewProcessPoolFactory.h' file not found
#import <Cordova/CDVWebViewProcessPoolFactory.h>
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/user/project/ios/capacitor-cordova-ios-plugins/sources/CordovaPluginInappbrowser/CDVWKInAppBrowser.m:22:9: note: did not find header 'CDVWebViewProcessPoolFactory.h' in
      framework 'Cordova' (loaded from
      '/Users/user/Library/Developer/Xcode/DerivedData/App-dhqnmyemtxyfryeexvhkkexwfcbw/Build/Intermediates.noindex/ArchiveIntermediates/App/BuildProductsPath/Release-iphoneos/CapacitorCordova')
1 error generated.
...
** ARCHIVE FAILED **

Ionic:
Ionic CLI                     : 7.1.5
Ionic Framework               : @ionic/angular 6.7.1
@angular-devkit/build-angular : 17.0.3
@angular-devkit/schematics    : 17.0.3
@angular/cli                  : 17.0.3
@ionic/angular-toolkit        : 10.0.0
Capacitor:
Capacitor CLI      : 5.5.1
@capacitor/android : 5.5.1
@capacitor/core    : 5.5.1
@capacitor/ios     : 5.5.1
Utility:
cordova-res                          : not installed globally
native-run (update available: 2.0.0) : 1.7.4
System:
NodeJS : v20.10.0
npm    : 10.2.3
OS     : macOS Unknown
Checklist

[x ] I searched for existing GitHub issues
 I updated all Cordova tooling to most recent version
[ x] I included all the necessary information above

Duplicate issue #1040: 6.0.0 Update throws error while archiving iOS project: "'Cordova/CDVWebViewProcessPoolFactory.h' file not found"
Created: 2023-12-05T10:57:08Z
Bug Report
Problem
What is expected to happen?
A successfully build archive within Xcode or Ionic Appflow with the newest 6.0.0 cordova-inappbrowser package.
What does actually happen?
Unable to create an archive within Xcode or Appflow. The following error occurred:
ios/capacitor-cordova-ios-plugins/sources/CordovaPluginInappbrowser/CDVWKInAppBrowser.m:22:9: 'Cordova/CDVWebViewProcessPoolFactory.h' file not found
** ARCHIVE FAILED **


Information

Updated from 5.0.0 to 6.0.0.  Using Ionic and Angular.
As the version is recently released, I could not find much info on the internet about this issue. Although I saw someone else experiencing the exact same issue on stackoverflow: https://stackoverflow.com/questions/77541592/capacitor-browser-send-callback-data-to-ionic-application
Command or Code

Install the 6.0.0 package. Sync the pods by running ionic cap sync ios. Then open Xcode and start a new Archive build.
Environment, Platform, Device

MacOS.

Version information

See above screenshot from build stack.
Checklist


 I searched for existing GitHub issues
 I updated all Cordova tooling to most recent version
 I included all the necessary information above

Closing comment (2023-12-05T13:10:41Z): Duplicate: #1039
Repository: apache/cordova-plugin-inappbrowser

Issue #372: OverrideUserAgent changes user agent for Cordova view too
Created: 2018-12-12T09:41:01Z
This bug is already known as noted on #94 and ionic-team/ionic-framework#11790 but i couldn't find any active issue to track progress.
What happened:
In our specific case we use Ionic Platform to programmatically check if platform is either "iOS" or "Android". In same time we use InAppBrowser for oauth on our server. Therefor we need to use OverrideUserAgent property.
Unfortunately as soon as we add OverrideUserAgent property Platform module doesn't work properly. It detects iOS and Android as desktop platform.
Expected behavior
Platform module should still be usable and properly detect iOS and Android platform.
Is there any progress on this issue or any suggestion how to avoid it?
EDIT: Same behavior on Android and iOS but Android can be avoided by using Crosswalk plugin.

Duplicate issue #502: Feature Request: Add Setting to Set a Custom User Agent
Created: 2019-07-06T14:14:50Z
Feature Request
Option to set the User Agent the InAppBrowser uses.
It would be nice if you could set the User Agent you want sent with requests as one of the options passed when opening the InAppBrowser.
I know you can change it in config.xml for the entire Cordova app, but we just want the requests sent in the InAppBrowser to be a custom user agent string.

Closing comment (2022-03-18T11:51:21Z): Isn't this a duplicate of #372 ?
Repository: apache/cordova-plugin-inappbrowser

Issue #328: Can not open camera when I click input type="file" on Android devices
Created: 2018-10-24T13:16:49Z
We can not open device's native camera or see any option to open it when we clicked the input type="file" in Android devices. Is there any solution ?

Duplicate issue #784: Inappbrowser on Android can not open Camera width input file
Created: 2020-09-16T06:13:24Z
Bug Report
webpage in inappbrowser can not choose file from camera width html tag 'input'
Problem
What is expected to happen?
can open camera in webpage on Android Device
What does actually happen?
can not open camera
Information

Command or Code

Environment, Platform, Device

Version information

Ionic:

   Ionic CLI                     : 6.11.8 (/Users/zhuxian/.nvm/versions/node/v12.18.3/lib/node_modules/@ionic/cli)
   Ionic Framework               : @ionic/angular 5.3.2
   @angular-devkit/build-angular : 0.1000.8
   @angular-devkit/schematics    : 10.0.8
   @angular/cli                  : 10.0.8
   @ionic/angular-toolkit        : 2.3.3

Cordova:

   Cordova CLI       : 10.0.0
   Cordova Platforms : android 9.0.0, ios 6.1.1
   Cordova Plugins   : cordova-plugin-ionic-keyboard 2.2.0, cordova-plugin-ionic-webview 5.0.0, (and 18 other plugins)

Utility:

   cordova-res                          : 0.15.1
   native-run (update available: 1.1.0) : 1.0.0

System:

   Android SDK Tools : 26.1.1 (/Users/zhuxian/Library/Android/sdk)
   ios-deploy        : 1.10.0
   ios-sim           : 8.0.2
   NodeJS            : v12.18.3 (/Users/zhuxian/.nvm/versions/node/v12.18.3/bin/node)
   npm               : 6.14.8
   OS                : macOS Catalina
   Xcode             : Xcode 11.7 Build version 11E801a

Checklist


 I searched for existing GitHub issues
 I updated all Cordova tooling to most recent version
 I included all the necessary information above

Closing comment (2020-10-01T13:33:05Z): duplicate of #328
Repository: apache/cordova-plugin-inappbrowser

Issue #709: 'Cordova/CDVUserAgentUtil.h' file not found on cordova-ios@6 
Created: 2020-06-01T07:55:49Z
cordova plugin add cordova-plugin-inappbrowser@3.2


cordova platform add ios@5.1.1


xcode build pass.


cordova platform rm ios


cordova platform add ios@6


xcode build failed.



error file: CDVWKInAppBrowser.m
error line: 27
error msg: 'Cordova/CDVUserAgentUtil.h' file not found

it seems to be related apache/cordova-ios#801

Duplicate issue #716: Incompatibility with cordova-ios@6.0.0?
Created: 2020-06-05T10:43:08Z
Bug Report
Problem
What does actually happen?
I have updated my project to cordova-ios@6.0.0, trying to build the project and it fails on a CompileC command for cordova-plugin-inappbrowser
Version information
cordova-ios@6.0.0
cordova-plugin-inappbrowser@3.2.0
Checklist


[ x ] I searched for existing GitHub issues
[ x ] I updated all Cordova tooling to most recent version
[ x ] I included all the necessary information above

Closing comment (2020-06-05T11:00:08Z): Duplicate of #709
Repository: apache/cordova-plugin-inappbrowser

Issue #328: Can not open camera when I click input type="file" on Android devices
Created: 2018-10-24T13:16:49Z
We can not open device's native camera or see any option to open it when we clicked the input type="file" in Android devices. Is there any solution ?

Duplicate issue #772: Enable camera access via the input file.
Created: 2020-09-03T16:30:07Z
I'm using InAppBrowser, to open an external form.
In this form there is an input file, so that the person can take a photo and attach it to the form.
When I access the link through the browser, the access of the cell phone camera works correctly, but when I access it via InAppBrowser or an iframe, the input file does not open the camera.
Is it necessary to enable some resource in the cord so that the camera can be accessed via InAppBrowser or iframe?
<script>
        document.addEventListener("deviceready", onDeviceReady, false);
        function onDeviceReady() {
            cordova.InAppBrowser.open('https://apps.url.com/index.php', '_blank', 'location=no');

            navigator.mediaDevices.getUserMedia({
                'audio': true,
                'video': {
                    facingMode: 'environment'
                }
            })
        }
    </script>

Plugins being used:
"cordova-plugin-camera": "^4.1.0",
"cordova-plugin-file": "^6.0.2",
"cordova-plugin-media-capture": "^3.0.3",
"cordova-plugin-whitelist": "^1.3.4"

Closing comment (2020-10-01T13:33:53Z): duplicate of #328
Repository: apache/cordova-plugin-inappbrowser

Issue #303: Android: executeScript failing for large return values (length greater than 10240)
Created: 2018-09-25T03:50:26Z
Since Android updated to webview v 69.0.3497.91, any script that runs that returns content longer than 10240 bytes fails as the message gets truncated
Bug appears here: https://github.com/apache/cordova-plugin-inappbrowser/blob/master/src/android/InAppChromeClient.java#L114
JSONException occurs as message is invalid JSON (truncated string)
Bug has been lodged with Chrome but they won't fix it:
https://bugs.chromium.org/p/chromium/issues/detail?id=884100
In the bug they report:
I don't think you should rely on prompt() as a means of passing data from JS to Java. There are other APIs that are properly suited to this task.

I am about to try a few ideas either addJavascriptInterface or evaluateJavascipt instead of prompt but would be open to suggestions of other interfaces
Note: This works OK if chrome is uninstalled and the default Android WebView is used

Duplicate issue #279: executeScript does not fire - issue ionic 3
Created: 2018-08-12T14:12:23Z
I am using this plugin in ionic 3.
Here is the piece of code
browser.on('loadstop').subscribe(event => {
    console.log(event,"event inside browser on")
 browser.executeScript({code: 'mycallback'}).then(data=>{
     console.log("script executed",data);
    },err=>{
      console.log(err,"error in executing the script");
    })

});

loadstop event is working fine, but executeScript doesnot work. Its not going to err section also.

Closing comment (2018-12-02T19:59:01Z): Closing as duplicate of #303 as it has more information
Repository: apache/cordova-plugin-inappbrowser

Issue #969: Request  voice-record inside the inappbrowser
Created: 2022-07-31T05:14:35Z
Feature Request
Android: request  voice-record (onRequestPermissionResult) (Some message such as 'default UserNotAllow...' was given )
IOS: If the NSMicrophoneUsageDescription is not added in the Info.plist, the voice-record inside the inappbrowser will make the app stuck.
Motivation Behind Feature

The page in the inappbrowser can communiate with users by the voice-record.
Feature Description

For example, the chatbox of the custom service is loaded in the inappbrowser. The user can hold the button and contact us by the voice record.
Alternatives or Workarounds

Duplicate issue #974: in _blank mode the microfon not work
Created: 2022-09-05T08:12:56Z
Feature Request
If I start the inappbrowser the microfon not work in Android. I/chromium: [INFO:CONSOLE(48)] "Uncaught (in promise) NotAllowedError: Permission denied",
I would like ask , I can use microfone in _blank mode too. I can use microfon in _self mode, but I have another problems.

Closing comment (2022-09-25T03:48:30Z): Closing as duplicate of #969