IssueTracker

Solved for now by adding @SuppressWarnings. We'll need to revisit if this pops up again.

Ideas include:

• Whack-a-mole overrides via NullAway Library Models
• Have an custom extract_only=true on the upstream aar targets so that they cannot be accidentally used, and then use the extracted classes.jar files only in the errorprone classpath.

I haven't been able to triage this yet, if you have a more complete example to share that would be helpful!

Doesn't seem possible to activate a DataSourceSheet:

SpreadsheetApp.enableBigQueryExecution();
const ss = SpreadsheetApp.getActiveSpreadsheet()

function insertDataSourceSheet() {
  const dataSourceSpec = SpreadsheetApp.newDataSourceSpec()
    .asBigQuery()
    .setProjectId('jpoehnelt-internal')
    .setTableProjectId('bigquery-public-data')
    .setDatasetId('ncaa_basketball')
    .setTableId('mbb_historical_teams_games')
    .build();

  // Adds the data source and its data to the spreadsheet.
  const sheet = ss.insertDataSourceSheet(dataSourceSpec).asSheet();
  sheet.setName('mbb_historical_teams_games')

  sheet.activate(); // doesn't work
}

function activateSheet() {
  // regular sheet
  ss.getSheetById(1431603180).activate(); // works
}

function activateDataSourceSheet() {
  ss.getSheetById(1973829494).activate(); // doesn't work
}

I have reported this to the engineering team and future updates will be shared here. Thank you for your patience.