sauce lab connection is not working 5.1.1 but woring fine with 5.0.0

Bug report

Node Version: 6.9.1
Protractor Version: 5.1.1
Angular Version: 1.6.0
Browser(s): saucelab chrome
Operating System and Version OS X EI captain 10.11.6
Your protractor configuration file find below
A relevant example test: I was trying to test my test cases in sauce lab after upgrading it to 5.1.1 it did not work, but when I downgrade it to 4/5.0.0 it worked fine. It did not show any error but did not proceed with the tunnel created
Output from running the test: attached below
Steps to reproduce the bug  change the protractor version and will not run
The URL you are running your tests against (if relevant) not relevant

configuration ifle:
exports.config = {
  sauceUser: '<userid>',
  sauceKey: '<key>',
  sauceSeleniumAddress: 'localhost:4445/wd/hub',
  //webDriverProxy: '<proxyurl-commented nto required>',
  /*capabilities: {
   'browserName': 'chrome',
   'tunnel-identifier': 'shepherd',
   'build': 'build-12345',
   'name': 'Shepherd DEV functional',
   }*/

  multiCapabilities: [
    {
      'browserName': 'chrome',
      'tunnel-identifier': 'shepherd',
      'build': 'build-12345',
      'name': 'Shepherd DEV functional',
      'chromeOptions': {
        'args': ['--no-sandbox', '--test-type=browser'],
        'prefs': {
          'download': {
            'prompt_for_download': false,
            'default_directory': '/tmp'
          }
        }
      }
      // 'browserName': 'phantomjs',
      // 'phantomjs.binary.path': require('phantomjs-prebuilt').path,
      // 'phantomjs.ghostdriver.cli.args': ['--loglevel=DEBUG'],
      // 'phantomjs.page.settings.userName': 'tst_dm_adm',
      // 'phantomjs.page.settings.password': 'CAlsGSV#/HNyAX'
    }
  ],
  allScriptsTimeout: 50000,
  seleniumArgs: ['--ignore_ssl'],
  suites: {
    home: 'home/*.spec.js',
    ...
  },
  framework: 'jasmine2',
  jasmineNodeOpts: {
    // If true, print colors to the terminal.
    showColors: true,
    // Default time to wait in ms before a test fails.
    defaultTimeoutInterval: 50000,
    //remove protractor's default dot reporter
    print: function () {
    }
  },
  onPrepare: function () {
    var SpecReporter = require('jasmine-spec-reporter');
    // add jasmine spec reporter
    jasmine.getEnv().addReporter(new SpecReporter({
      displayStacktrace: 'all',
      prefixes: {success: '* ', failure: 'X ', pending: '* '}
    }));

    var jasmineReporters = require('jasmine-reporters');
    jasmine.getEnv().addReporter(
      new jasmineReporters.JUnitXmlReporter(null, true, true, 'testOutput')
    );
  }
};

*** below is the console output after running protractor -c config.js***
C429349HHY3QD:shepherd-test RF886$ ./run-in-saucelab.sh
Installing..
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN<EMAIL_ADDRESS>No license field.
Updating webdriver..
[10:50:54] I/file_manager - creating folder /Users/RF886/aniruddhadas9/develop/herd/jan30/shepherd-test/node_modules/protractor/node_modules/webdriver-manager/selenium
[10:50:55] I/downloader - curl -o /Users/RF886/aniruddhadas9/develop/herd/jan30/shepherd-test/node_modules/protractor/node_modules/webdriver-manager/selenium/geckodriver-v0.15.0.tar.gz https://github.com/mozilla/geckodriver/releases/download/v0.15.0/geckodriver-v0.15.0-macos.tar.gz
[10:50:55] I/update - geckodriver: unzipping geckodriver-v0.15.0.tar.gz
[10:50:55] I/update - geckodriver: setting permissions to 0755 for /Users/RF886/aniruddhadas9/develop/herd/jan30/shepherd-test/node_modules/protractor/node_modules/webdriver-manager/selenium/geckodriver-v0.15.0
[10:50:56] I/downloader - curl -o /Users/RF886/aniruddhadas9/develop/herd/jan30/shepherd-test/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.28.zip https://chromedriver.storage.googleapis.com/2.28/chromedriver_mac64.zip
[10:50:56] I/downloader - curl -o /Users/RF886/aniruddhadas9/develop/herd/jan30/shepherd-test/node_modules/protractor/node_modules/webdriver-manager/selenium/selenium-server-standalone-3.3.1.jar https://selenium-release.storage.googleapis.com/3.3/selenium-server-standalone-3.3.1.jar
[10:50:58] I/update - chromedriver: unzipping chromedriver_2.28.zip
[10:50:58] I/update - chromedriver: setting permissions to 0755 for /Users/RF886/aniruddhadas9/develop/herd/jan30/shepherd-test/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.28
Running tests..
[10:51:00] I/launcher - Running 1 instances of WebDriver
[10:51:00] I/sauce - Using SauceLabs selenium server at https://localhost:4445/wd/hub

Unfortunately there's not much that we can do with that information. Our own tests run on sauce; are you able to test using the example using your sauce creds and the latest version of protractor?

I am able to do the test with 4 or 5.0.0 but when I upgrade to 5.1.1 it doesn't show any error but also it does not proceed. I don't see any test cases running sauce lab site.
I will spend some more time to debug and give you more information if I can.

Do we have any update on this?
I have been seeing the following since I updated:
Error: EPROTO write EPROTO<PHONE_NUMBER>50624:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:../deps/openssl/openssl/ssl/s23_clnt.c:794:

@NickTomlin I am facing the same issue as the OP.
@aniruddhadas9 Were you able to figure a workaround ?

@NickTomlin I just degraded to 5.0.0/4 as of now. that is the work-around as of now ;)
I think the protractor team is not able to track that with the information I am provided. please add as much information you can so that they can track it.
Mean time I am working to give them more information.

I tried with the configuration in the example:
exports.config = {
  sauceUser: process.env.SAUCE_USER,
  sauceKey: process.env.SAUCE_KEY,
  sauceSeleniumAddress: process.env.SAUCE_SELENIUM_ADDRESS,
  // Capabilities to be passed to the webdriver instance.
  capabilities: {
    'browserName': 'chrome'
  },

  // Framework to use. Jasmine is recommended.
  framework: 'jasmine',

  // Spec patterns are relative to the current working directory when
  // protractor is called.
  specs: ['example_spec.js'],

  // Options to be passed to Jasmine.
  jasmineNodeOpts: {
    defaultTimeoutInterval: 30000
  }
};

I put my sauce opts as the env variables.
./bin/protractor ./conf.js --capabilities.tunnelIdentifier=tunnelId --capabilities.seleniumVersion="3.1.1"

LMK what exactly you might need @NickTomlin

@ashubham  and @aniruddhadas9
Strange that the tests are failing for you both. I have the following setup and it works:

protractor: 5.1.1
Node: 6.9.2
OSX 10.12.3
Sauce Connect 4.4.3 (higher version doesn't pull up the connection)

Config:
'use strict';
const path = require('path');
const config = require('./protractor.shared.conf').config;

const SAUCE_USERNAME = '<username>';
const SAUCE_ACCESS_KEY = '<key>';

config.baseUrl = `http://localhost:5555`;

config.seleniumAddress = 'http://localhost:4445/wd/hub';

config.multiCapabilities = [
    {
        browserName: 'chrome',
        platform: "Windows 10",
        version: "latest",
        screenResolution: "1400x1050",
        name: '<Name>',
        username: SAUCE_USERNAME,
        accessKey: SAUCE_ACCESS_KEY,
        'tunnel-identifier': '<tunnel-identifier>',
        shardTestFiles: true
    }
];
exports.config = config;

Biggest difference in the configurations is that:

I don't use sauceUser: '<userid>'
I don't use sauceKey: '<key>'
I don't use  sauceSeleniumAddress: 'localhost:4445/wd/hub'

Can you check with my configuration if it works? If so we might have an issue with the default connection that we should use of Protractor for Sauce Labs
Grtz
Wim

@wswebcreation sure. Let me try these configs

The bug root is the recent fix, see https://github.com/angular/protractor/commit/3edd62eccccb67ec7cb71b8c3d8b2c2921a6f7ca#commitcomment-22055547
The workaround is to use ```username/accessKey/tunnel-identifier" per capability indeed.

The way @wswebcreation mentioned worked for me now. Actually the protractor version 4 and 5 takes configuration in different ways.
if you are using protractor 4 then configure your sauce lab the way I did and if you are using protractor 5 or higher then use protractor config the way @wswebcreation in his post

@aniruddhadas9 this should be closed since you have your answer.

@kenisteward
You are right, it works with this "workaround". I do think there is an issue, I need to dive into it. The issue could also be that the documentation isn't correct. That's why I think it's better to keep this open

After some debugging I put myself on the wrong track, see the linked issue. The solution it pretty simple.
Cause:
Between Protractor 4.0.14 and Protractor 5.0.0 there has been a change in the driverProviders. There is now a condition here that will NOT go to the Sauce Labs runner if you provide a custom seleniumAddress.
Solution:
You need to change your seleniumAddress-property to sauceSeleniumAddress, then it will work. So don't keep the seleniumAddress in your config file!
Protractor will take care of all the connection between your tests and Sauce Labs, even update the instances in Sauce Labs with the correct status.
I'm going to close the issue for now. Feel free to add more questions in this issue.

@wswebcreation I'm trying this out tonight.  i hope it works.
In other news you guys take PR"s right?  I see in Sauce.ts it does not print out the session id so that if you are running in say jenkins / travis ci that it would asssociate the build to your job.
See here
https://wiki.saucelabs.com/display/DOCS/Setting+Up+Reporting+between+Sauce+Labs+and+Jenkins
I currently do this onComplete()
console.log("SauceOnDemandSessionId=id job-name=browser-job-name

@kenisteward
Hope it works to. Last thing you are right about. I now do this manually, printing doesn't do the trick, you need to update it yourself.
A PR would be welcome

@wswebcreation unfortunately it did not work out.
As it turns out the webDriverProxy setting is used not only in Sauce.ts but it is also used in the driverprovider to initialize the driver.
Because of this when i set that i'm able to get out of my proxy to send saucelabs requests but i'm unable to connect to my localhosted (in jenkins) selenium relayed driver.
gives me an access denied error because it looks like the password is not being appended to the username before the @ on the driver url.  I have no clue why the proxy woudl be taking that out.

@kenisteward ,
Can you place your config here, so we can check it?

const conf = require('./e2e/config/conf.e2e.json');
const { SpecReporter } = require('jasmine-spec-reporter');
const jasmineReporters = require('jasmine-reporters');

const shartTestFiles = false;
const maxInstances = 1;

exports.config = {
  SELENIUM_PROMISE_MANAGER: 0,
  sauceBuild: process.env.JENKINS_BUILD_NUMBER || 'localTestBuildNumber__00',
  sauceUser: process.env.SAUCE_USERNAME || 'test',
  sauceKey: process.env.SAUCE_ACCESS_KEY || 'test',
  sauceSeleniumUseHttp: true,
  sauceSeleniumAddress:  'localhost:4445/wd/hub', // using this with jenkins and Selenium relay 443 is not open for my env.
  webDriverProxy: http://my.proxy.org:3122,
  multiCapabilities: [
    {
      count: 1,
      "name": "Windows 7 chrome 57",
      "tunnel-identifier": "shepherd-jenkins",
      "platform": "Windows 7",
      "browserName": "chrome",
      chromeOptions: {
        prefs: {
          'credentials_enable_service': false,
          'profile': {
            'password_manager_enabled': false
          }
        },
        args: [
          '--disable-cache',
          '--disable-application-cache',
          '--disable-offline-load-stale-cache',
          '--disk-cache-size=0',
          '--v8-cache-options=off'
        ]
      },
      "version": "57",
      shartTestFiles
    }
  ],
  allScriptsTimeout: 11000,
  seleniumArgs: ['--ignore_ssl'],
  specs: [
    './e2e/app/data-objects/**/*.e2e-spec.ts',
  ],
  /*suites: [
    './e2e/!**!/!*.e2e-spec.ts'
  ],*/
  // directConnect: true,
  baseUrl: conf.baseUrl8443,
  framework: 'jasmine2',
  jasmineNodeOpts: {
    showColors: true,
    defaultTimeoutInterval: 30000,
    print: function () {
    }
  },

  onPrepare() {
    let capabilities
    require('ts-node').register({
      project: 'e2e/tsconfig.e2e.json'
    });

    jasmine.getEnv().addReporter(new SpecReporter({
      spec: { displayStacktrace: true }
    }));

    return browser.getProcessedConfig().then((c) => {
      capabilities = c.capabilities;
      // used to change the namespace for the data.
      process.env.CURRENT_BROWSER = c.capabilities.browserName.replace(new RegExp(' ', 'g'), '-');
      jasmine.getEnv().addReporter(
        new jasmineReporters.JUnitXmlReporter({
          filePrefix: c.capabilities.browserName,
          consolidateAll: true,
          modifySuiteName: function (generatedSuiteName, suite) {
            // this will produce distinct suite names for each capability,
            // e.g. 'firefox.login tests' and 'chrome.login tests'
            return c.capabilities.browserName + '.' + generatedSuiteName;
          }
        }));

      return browser.driver.get(c.baseUrl).then(function () {
        browser.sleep(2000);
      });
    });
  },

  onComplete() {
    return browser.getProcessedConfig().then(function (c) {
      return browser.getSession().then(function (session) {
        // required to be here so saucelabs picks up reports to put in jenkins
        console.log('SauceOnDemandSessionID=' + session.getId() + ' job-name=' + c.capabilities.name);
      });
    });
  }
};

also having trouble just getting  1 instance of a browser to run in sauce labs
the issue being for some reason  It takes the accesskey out of the selenium address

@kenisteward
I got a few questions, can you please answer them:

did it work with the workaround?
is the webDriverProxy a new problem?
Have you also looked at this

Tnx in advance

what work around?
webDriverProxy is the issue in my use case solely because i don't need to use the proxy to connect to my driver instance but i do need it for the sauceLabs call.  I'd prefer there just be 2 different settings like it was before.
I saw it but i don't know how it can help me

Hi @kenisteward
The workaround I referred to is this, but I understand your problem is the webDriverProxy. Looks like your issue is a different issue then the initial issue of @aniruddhadas9 . Will check it the coming days
For the sauceAgent, I thought this will give you an extra solution for the proxy problem based on what I read from the docs. How I read it is that this should not interfere with your Jenkins setup


Add new @enum tag

Hi!
Current JSDoc spec allows documenting plain objects as enumerables. This is very helpful when restricting argument types.
An abstract example:
//Season.js
/**
 * @enum {String}
 */
const Season = {
    SPRING: 'SPRING',
    SUMMER: 'SUMMER',
    AUTUMN: 'AUTUMN',
    WINTER: 'WINTER'
};

export default Season;

//Forecast.js
export default class Forecast {
    /**
     * @param {Season} season
     */
    generate(season) {
        //implementation
    }
}

//test.js
import Season from './Season.js';
import Forecast from './Forecast.js';

let forecast = new Forecast();
forecast.generate(Season.SUMMER);

Current implementation of ESDoc treats season argument of Forecast#generate as a variable import Season from './Season.js' instead of const Season inside Season.js.
Is it planned to support @enum annotations similar to @typedef?

@raveclassic Hi! Thanks for this proposal.
I think that @enum is good. I will try to support it in future version.
But now I have no time :sweat: Please wait a moment.
Thanks.

Any updates to this?

We use them a lot

Any updates to this?

Hey! Any news about this feature?

@Piroru Just switch to typedoc. TS now is able to process js-files and read jsdoc in them.

@raveclassic thanks, we will try it :)

@Piroru We went even further and rewrote our entire codebase in typescript - it's not that hard ;)

@raveclassic We had an attempt before, I guess we need one more try :D

+1 on this

+1 @enum and @event are two missing tag that will make this tool awesome

We still need this :)

Pretty interested by this feature.
Please can you also consider this kind of writing :
static get Eases() {
        return {
            LINEAR: 'Linear',
            ACCELERATE: 'Expo.easeIn',
            DECELERATE: 'Expo.easeOut',
            SINE: 'Sine.easeInOut',
            CIRCULAR: 'Circ.easeInOut',
            ELASTIC: 'Elastic',
            BOUNCE: 'Bounce',
            INERTIA: 'Back.easeOut',
            STEPPED: 'Stepped'
        }
    }

To create an enum embedded in a class. :-)

Any updates on this ?

@raveclassic That sounds like a great idea - would love some tips on how to do this. I was able to get ESDoc up and running super easily but I have been unable to figure out how to do the same with typedoc, it just spits out an empty template page.


The furure of CodeQL analysis

On this repo, there is a similar question described on DiddiLeija/aleat3/#25. We also need help here with that.
(NOTE: Please use the aleat3 issue to discuss).

As the original issue has been closed, I will close this one, too.


Consider changing the tuple on-disk format to be fixed size if all fields are fixed size

Should see if this is possible before stabilizing the file format

j/k I already implemented this in #366 =)


User-defined types in SQL Server causing crash

When a table contains a User-Defined type (including Geography or Geometry) column, the SqlSchemaProvider crashes.

Fixed, although still no actual handling for user-defined types.


Benchmark Submission: jmg764

This pull request represents a submission to the codesearchnet benchmark.
It is the main communication channel for you and the reviewers.
Wandb run results for review

Hi @jmg764
I just realized that your output has results only for Python and removed your submission from the leaderboard. Please resubmit with model_predictions.csv containing results for all languages.
Thanks!


Issue from website page Reading and Writing Files

From URL: https://flutter.io/reading-writing-files/
I created a new project with flutter create. Copy and pasted this example into main.dart.
Added path_provider: "^0.3.0" to my pubspec.yaml
It does not run in Intellij 2017.3.2
Error :
Build file '/home/david/.pub-cache/hosted/pub.dartlang.org/path_provider-0.3.0/android/build.gradle' line: 6
* What went wrong:
A problem occurred evaluating project ':path_provider'.
> Could not find method google() for arguments [] on repository container.

I just tried, and can't seem to repro this.
Can you share the output of running flutter doctor in a terminal/console, please?

@Rockvole Version 0.3.0 of the path_provider plugin does not work with current alpha branch of Flutter. The reason is that the plugin has been upgraded to Gradle 4.1, but the corresponding change to Flutter tooling and project templates are not yet on alpha branch.

Ah, that would explain it; I tried master.
@mravn-google, are we rolling alpha?

I have a few Gradle-related changes to make, then I'll do a roll.

Thanks for looking into this for me guys.

I also tried reverting to 0.2.2 as mentioned by @mravn-google but still it is pointing an error to 0.3.0
I removed the plugin, and still getting the same error:

Error running Gradle:
Exit code 1 from: /Users/macbook/Documents/flProjects/myapp/android/gradlew app:properties:
NDK is missing a "platforms" directory.
If you are using NDK, verify the ndk.dir is set to a valid NDK directory.  It is currently set to /Users/macbook/Library/Android/sdk/ndk-bundle.
If you are not using NDK, unset the NDK variable from ANDROID_NDK_HOME or local.properties to remove this warning.

NDK is missing a "platforms" directory.
If you are using NDK, verify the ndk.dir is set to a valid NDK directory.  It is currently set to /Users/macbook/Library/Android/sdk/ndk-bundle.
If you are not using NDK, unset the NDK variable from ANDROID_NDK_HOME or local.properties to remove this warning.
Incremental java compilation is an incubating feature.
NDK is missing a "platforms" directory.
If you are using NDK, verify the ndk.dir is set to a valid NDK directory.  It is currently set to /Users/macbook/Library/Android/sdk/ndk-bundle.
If you are not using NDK, unset the NDK variable from ANDROID_NDK_HOME or local.properties to remove this warning.
BUILD FAILED
Total time: 5.622 secs
FAILURE: Build failed with an exception.

Where:
Build file '/Users/macbook/.pub-cache/hosted/pub.dartlang.org/path_provider-0.3.0/android/build.gradle' line: 6

What went wrong:
A problem occurred evaluating project ':path_provider'.

Could not find method google() for arguments [] on repository container.

I am also seeing the error, even after updating the gradle files.

@ianmcxa @artAst I was able to reproduce the problem you described above. It appears that the .flutter-plugins file is not always correctly rewritten after a change to pubspec.yaml. Removing that file should fix it, as Flutter tooling will the recreate it correctly. I'll investigate a bit more, and file an issue on this.

Create Flutter project using alpha branch
Add dependency on path_provider version 0.3.0
flutter run (fails with Gradle error because the plugin is using Gradle 4.1 API)
Downgrade plugin dependency to 0.2.2
flutter run (still fails with same Gradle error, citing version 0.3.0 of plugin)
Observe: .flutter-plugins file incorrectly contains a reference to version 0.3.0.
Delete .flutter-plugins
flutter run (works)

This issue was likely fixed by https://github.com/flutter/flutter/pull/13827


A power consumption in using TensorRT

Maybe this is not the right place to ask this question.I have a problem when I use jetson nano to develop. I want to create a RIP（A sensor triggered by infrared light）camera. I hope it can operate with low power consumption when the RIP sensor is not activated，and when the sensor is activated ,Jetson nano can start the image recognition quickly to know what triggered the sensor.But it seems that if running the program after the sensor is activated , loading the retrain model takes a lot of time. So I load the models first in my Python program , and get the status of sensor after loading. However, after loading the models, Jetson nano always Operate at higher power consumption, although the sensor has not been triggered, which means recognition didn't start. What can I do to make it work at low power consumption after loading models?
I would appreciate it if you could give me any help.

Hi @MiniVanlab, you could manually change your Nano to 5W mode by running sudo nvpmodel -m 1
You can also keep an eye on the clocks with sudo tegrastats


Gyro values keeps moving?

Camera Model | { D435i }
Firmware Version | (<IP_ADDRESS>)
Operating System & Version | { Linux (Ubuntu 14/16/17)
Kernel Version (Linux Only) | (5.11.0 -38-generic )
Platform | PC
Language | {python}
Segment | {Robot/Smartphone/VR/AR/others }
For some reason my Gyro value on Y keeps going up while X & Z go down. Camera lays on a flat & steady surface with the Z axis pointing upwards.
try:
last_frame = None
while True:
f = pipeline.wait_for_frames()
for frame in f:
# gather IMU data
if frame.is_motion_frame():
if frame.get_profile().stream_type() == rs.stream.gyro:
gyro = np.array([gyro_data(frame.as_motion_frame().get_motion_data())]).T
if frame.get_profile().stream_type() == rs.stream.accel:
accelwithg = np.array([accel_data(frame.as_motion_frame().get_motion_data())]).T
            ts = f.get_timestamp()

   if first:
        first = False
        last_ts_gyro = ts
        continue

    if ts == last_ts_gyro:
        continue

    ## calculation for the second frame onwards
    # gyro-meter calculations
    dt = (ts - last_ts_gyro) / 1000
    last_ts_gyro = ts

    gyro_angle_x = gyro[0] * dt
    gyro_angle_y = gyro[1] * dt
    gyro_angle_z = gyro[2] * dt
    # totals
    total_x += gyro_angle_x
    total_y += gyro_angle_y
    total_z += gyro_angle_z

    # rad = > degree
    dtotal_x = np.rad2deg(total_x) % 360
    dtotal_y = np.rad2deg(total_y) % 360
    dtotal_z = np.rad2deg(total_z) % 360

Hi @MyOtherNamesWereTaken  Have you performed a calibration of the IMU using Intel's Python calibration tool at the link below and then saved that calibration to storage inside the camera, please?
https://github.com/IntelRealSense/librealsense/tree/master/tools/rs-imu-calibration
The IMU component inside 400 Series cameras equipped with an IMU does not have an internal calibration mechanism and so calibration is performed with software instead and saved to the camera once you are satisfied with the calibration result.
If an IMU has not had a calibration written then the Y accel value may be non-zero even when the camera is stationary.  It may also have difficulty approaching the ideal Y value of 9.80 (representing the 9.81 Newtons gravity force of the Earth) and have less accurate values such as 9.4 or 9.6 instead.

waiting for realsense device...
Device PID:  0B3A
Device name:  Intel RealSense D435I
Serial number:<PHONE_NUMBER>80
Product Line:  D400
Firmware version:  <IP_ADDRESS>
Start interactive mode:
Error: (25, 'Inappropriate ioctl for device')
Process finished with exit code 0
this is what im getting when i try to run it

That is the problem that you reported a week ago at https://github.com/IntelRealSense/librealsense/issues/10356 when asking about accel.  Did you try an RSUSB build of librealsense as suggested in that case, please?

How would i go on about doing that? I am a little clueless with this

When you built librealsense the last time, did you build it from source code using CMake and build the Python wrapper at the same time by including the CMake build term -DBUILD_PYTHON_BINDINGS:bool=true
If so then you can build librealsense in RSUSB mode by adding the term -DFORCE_RSUSB_BACKEND=true to the CMake build instruction.  For example:
cmake ../ -DFORCE_RSUSB_BACKEND=true -DBUILD_PYTHON_BINDINGS:bool=true -DCMAKE_BUILD_TYPE=release -DBUILD_EXAMPLES=true -DBUILD_GRAPHICAL_EXAMPLES=true
When building with RSUSB, you do not need to apply a patch to the kernel before you build librealsense.
In regard to checking if you were previously using RSUSB: if you built librealsense from source code on a PC and did not use  -DFORCE_RSUSB_BACKEND=true then the build was not using RSUSB.

I just used import pyrealsense2 as rs?

On Linux the Python pyrealsense2 wrapper has to be built by some method (pip install pyrealsense2, building it from source code on its own, or building librealsense and the wrapper together from source code at the same time).  A pyrealsense2 script should not work if the wrapper has not been built.
For example, if librealsense was built from packages instead of source code then it should not have pyrealsense2 included.
Can you describe the method that you use to install librealsense, please?

It was build by someone prior to me on Linux with the pip install pyrealsense2 is what ive been told if that helps..?

That is helpful, yes.
The easiest way to perform a librealsense build that has pyrealsense2 support may therefore be:

Build the SDK without pyrealsense2 included using the simple libuvc backend method in the link below.

https://github.com/IntelRealSense/librealsense/blob/master/doc/libuvc_installation.md

Once the SDK as been successfully installed, perform the pip install pyrealsense2 procedure to add the pyrealsense2 wrapper.

So i did step 1-5 from the link u send me and then did the pip install but it still gives me the same error.

Okay, thanks for testing.  So the librealsense SDK is installing correctly but the problem is occurring when installing the pyrealsense2 wrapper afterwards?

As in after trying to run the calibration tool im still getting the same error as i did before. Did i do something wrong in the process? Sorry for being this clueless.

Don't worry, it's no trouble at all.
If you installed librealsense using the libuvc_installation.md instructions then your librealsense build should now be based on RSUSB.  However, you are still experiencing the Inappropriate ioctl for device error.  This would suggest that the problem is not related to the kernel, as RSUSB should be bypassing the kernel.
I have not used this calibration tool myself.  My interpretation of the instructions for running the calibration script is as follows though:

Download the source code of the librealsense SDK.  This can be done from the 'Assets' file list of the SDK releases page by clicking on the Source code (zip) link.

Once the source code zip file is downloaded, extract the librealsense folder from it and navigate to the following folder location:

librealsense-2.50.0 > tools= > rs-imu-calibration
In this folder should be the script file rs-imu-calibration.py

Whilst in this folder, input the Python command below to launch the script.

python rs-imu-calibration.py

Is the above procedure similar to what you have been doing, please?

Thank you so much! It actually opens and does stuff now. Now I just go by the readme file included in the rs-imu-calibration folder, right?

Great news that you made significant progress!
Yes, you can use that readme.  In my opiinon though, the PDF version of the guide with more detailed instructions provides a clearer explanation of each step of the calibration process.  You can find it at page 16 onwards of the PDF.
https://dev.intelrealsense.com/docs/imu-calibration-tool-for-intel-realsense-depth-camera

Thank you so much. I managed to calibrate it thanks to you. Am i supposed to save the calibration files in a certain spot ? Or just the folder the .py is in?

So i did save it in the camera folder, however my acceleration is still measured at 9.41 and when comparing the results to those without calibration it seems like nothing has changed. Am i supposed to move the build folder into my projects folder where my python code is?

I believe that you should use the instruction RS2_OPTION_ENABLE_MOTION_CORRECTION to enable motion data correction.
The RealSense SDK's rs_imu_calibration.py script provides an example of setting the status of this option in Python, though you should set the option to '1' (enabled) instead of '0' (disabled).
https://github.com/IntelRealSense/librealsense/blob/master/tools/rs-imu-calibration/rs-imu-calibration.py#L264-L266

That fixed the issue, thanks!

When rs_imu_calibration.py asks if you want to store the IMU calibration at the end of the calibration process and you select Yes, it is saved to an internal storage space inside the camera and not to the computer.  If the calibration is not saved then it will be lost when the calibration program is closed or you perform another calibration.

That fixed the issue, thanks!
Nevermind, it seems that when putting it on different axis it measures different values for the acceleration, Varrying between 9.4 and 10.1 m/s²

I just recalibrated it, however im still facing these issues. I also enable motion correction, which did help.

IMU data can be noisy and sensitive.  It is possible to write code to weight the data towards the gyro instead of the accelerometer to make it less sensitive.  There is only a C++ example of this though, in the SDK's rs-motion IMU program.
https://github.com/IntelRealSense/librealsense/blob/master/examples/motion/rs-motion.cpp#L117-L118

Also, when using it like this
context = rs.context()
pipeline = rs.pipeline(context)
config = rs.config()
rs.option.enable_motion_correction, 1
config.enable_stream(rs.stream.gyro, rs.format.motion_xyz32f, 200)
config.enable_stream(rs.stream.accel, rs.format.motion_xyz32f, 63)
profile = pipeline.start(config)
My IDE says that the motion correction statement seems to have no effect?

The script does not seem to be informing the camera that it should be accessing the IMU component of the camera using imu_sensor.set_option to set the motion correction, as the IMU component is separate from the depth sensor inside the camera.  The script therefore needs to define which of the three separate sensor components in the D435i (depth, RGB, IMU) to access.
self.imu_sensor.set_option(rs.option.enable_motion_correction, 1)

Thanks very much for your patience while I conducted further research.  It seems that RS2_OPTION_ENABLE_MOTION_CORRECTION is a software setting that tells the script whether or not to correct the motion data and not an option that needs to access the IMU sensor.   So your original implementation rs.option.enable_motion_correction, 1 was likely correct.  I do apologize.

https://github.com/IntelRealSense/realsense-ros/issues/2268#issuecomment-1058182675 describes how VINS-Fusion, which some RealSense ROS D435i owners have used, has a parameter called g_norm to adjust the gravity magnitude value.
I understand that the robot_localization ROS module used in Intel's D435i SLAM guide can also provide gravity removal.  An example reference for this is at https://github.com/cra-ros-pkg/robot_localization/issues/501

So theres no Python implementation to get a proper rotation matrix? or any sort of method to filter out the gravity?

So: in other words theres no way to reliably track position just with gyro and accelerometer?

Even with a specialized T265 Tracking Camera (see the link below) it is unlikely that you would achieve that very fine degree of position tracking accuracy, so for a D435i I would say no.
https://support.intelrealsense.com/hc/en-us/community/posts/360036372154-T265-Tracking-Accuracy

Thanks, ill have to find a different method to make this work.
Is there any sort of implementation in the realsense library for visual odometry? I couldn't find anything related to Python

There is support for visual odometry in the RealSense SDK but it is for the T265.
https://www.intelrealsense.com/visual-inertial-tracking-case-study/
A T265 can be paired with a 400 Series camera to provide Visual SLAM navigation by the T265 whilst the 400 Series camera provides depth sensing, as the T265 does not have built-in depth sensing.
https://www.intelrealsense.com/depth-and-tracking-combined-get-started/

So the only way to achieve visual odometry with my d435i is with pairing it to a T265?

The commercial software package SLAMcore is compatible with D435i and D455.
https://www.slamcore.com/spatial-intelligence-sdk
https://www.youtube.com/watch?v=TqgwCGrqGAM
A RealSense user performed visual odometry SLAM with a D435i and RTABMAP in the YouTube video below.  Others have used RTABMAP with D435i for visual odometry too.
https://www.youtube.com/watch?v=0M_Hc0pdgcY
My understanding is that T265 is the preferred method though due to the noisiness of the D435i IMU data.

Hi @MyOtherNamesWereTaken  Do you require further assistance with this case, please?  Thanks!

Hi @MyOtherNamesWereTaken Do you require further assistance with this case, please? Thanks!

Hi, guy. I need your help. When I run the rs-imu-calibration, it asks me : Would you like to write the results to the camera?(Y/N)
I chose y. But it shows : Writing calibration to device.
Then: Error : failed to set power state.


def_field no longer exporting in subforms

"Note, no matter which fields or forms are requested, the project.def_field key will always be in the returned dicts."
This no longer appears to be true in the latest version of Redcap
Unique identifiers declared by project.def_field are no longer present in the recordset for project subforms that do not explicitly contain the 'defining field'

I've noticed this as well. In addition to project.def_field, I've also noticed redcap_event_name not being present.
Additionally, the API no longer seems to respect the export of any forms specifically -- instead it returns every form.
This seems to be a problem with the API itself (not PyCap), but I'm investigating further to try and pinpoint exactly what's going on.

Thanks for the heads up @tjrivera! I'll finally have some time to hack on PyCap this weekend at PyCon, hopefully can hit some of these issues and cut a release to PyPI.

From REDCap's 6.0.x release notes:
Change: When doing an API data export where a list of fields or forms are explicitly provided in the API request to REDCap, the record ID field will now only be included in the exported result if the record ID field is explicitly specified in the list of fields or if its form is explicitly specified in the list of forms. In previous versions, if any form or field was explicitly provided in the API request, it would return the record ID field. So for users who depend upon the Record ID field to be returned in the exported data set, they should go ahead and add the Record ID to the "fields" array parameter in their API request to maintain continuity after the upgrade to REDCap 6.0 or higher.

Should PyCap check if the associated project's version is 6.x+ and if so automatically append the def_field?

Is it possible to grab versioning info out?
I haven't had any issues when I explicitly call out form names except for the lack of the def_field. I suppose the workaround could be to get the field list and add the project.def_field and pass both in as the array.

Should PyCap check if the associated project's version is 6.x+ and if so automatically append the def_field?

Sounds like a great use for the semantic versioning recently added.

@thephillipsequation you might have something like
project = redcap.Project(url, api_key)
if project.redcap_version.major >= 6:
    project.export_records(forms=['demographics'], fields=[project.def_field])
else:
    project.export_records(forms=['demographics'])

you don't have to include the full field list

Thanks @tjrivera , I hadn't realized if you called a form and a field it wouldn't only export the def_field for that form. Will test this weekend

Maybe we don't even need the logic @tjrivera? This will be a no-op on <6.X redcap servers and >6 it will maintain backwards compatibility.


Add option to throw error instead of setting body

It can be useful to centralize all application errors in a single error handler, but currently this is not possible because the ratelimit middleware automatically handles it. My suggestion, implemented in this PR, is to pass a new option (throw: true) to throw the error instead, allowing a custom error handler to process it.
I considered making this the default option, since this.throw makes it somewhat compatible with koa's built-in error handler. However, this is not the case because all headers are removed from the response, so x-ratelimit-limit, x-ratelimit-remaining and x-ratelimit-reset would be missing from the response.

What about adding support for specifying headers in koa and making this the default? /cc @dead-horse

Related https://github.com/koajs/koa/issues/571

@koajs/ratelimit any more advice?

land abf2924a0a9873b19432940bbf8c1edcd3cc84a3

@ruimarinho<EMAIL_ADDRESS>


Handling large cases

Is your feature request related to a problem? Please describe.
An Xcompact3d user encountered problems with restarting large (600M+ mesh point) cases. @mathrack identified integer overflow as the likely issue.
Describe the solution you'd like
A discussion of how to solve this.
Describe alternatives you've considered
Discussion so far has considered:

Moving to mpi_f08 for MPI4 large data features
Rewriting low-level components in C

Both have downsides: mpi_f08 does not seem well supported by tooling; mixed-language coding is complex/error-prone, however if well-isolated may be the best solution considered so far.

Regarding large cases, the issue at hand is related to reading and writing many files. The displacement offset in bytes tends to overflow, in particular for double precision runs. Using integers with a specific kind when doing operations on the displacement can probably solve this issue without adding low-level C / the mpi_f08module (MPI3 / MPI4) .
Regarding very large cases, some similar issues might pop up and switching to low-level C or the mpi_f08 module might be mandatory.
It is now established that the first point is critical for double precision runs below 10^9 grid points. More issues might show up on finer grids, but none is known yet...


feat: build & publish Docs to Github pages in CI

Similar to https://github.com/MystenLabs/mysten-infra/pull/71
See results at https://mystenlabs.github.io/mysten-infra/
Successful run at https://github.com/huitseeker/sui/runs/6371589517?check_suite_focus=true

Shall we link from?:
https://docs.sui.io/contribute


2021 07 maintenance

Not yet ready for review, but opening PR so that Travis will run

@kmcelwee just to confirm, this includes some maintenance updates as well as a bugfix for the broken IIIF images, right? I connected it to the second issue, and edited the pr so it would be merged into develop instead of main.


UnknownHostException: localhost.localstack.cloud on mac os

I am using 0.2.15 version of the utils. The docker starts up without any issue, but the s3 client can not resolve the url.. here is the config I have:
@ExtendWith(LocalstackDockerExtension::class)
@LocalstackDockerProperties(services = [ServiceName.S3])
@SpringBootTest(classes = [Application::class, SomeControllerTest.S3TestConfiguration::class])
@TestPropertySource(
    properties = ["spring.main.allow-bean-definition-overriding=true"]
)
class SomeControllerTest : AbstractTest() {

    @Configuration
    class S3TestConfiguration {

        // override existing s3 client
        @Primary
        @Bean
        fun s3Client(): S3Client =
            S3Client.builder()
                .credentialsProvider(
                    StaticCredentialsProvider.create(
                        AwsBasicCredentials.create(
                            "key", "secret"
                        )))
                .endpointOverride(URI.create(Localstack.INSTANCE.endpointS3))
                .region(Region.AWS_GLOBAL)
                .serviceConfiguration { it.pathStyleAccessEnabled() }
                .build()
    }
   ...
}

Caused by: software.amazon.awssdk.core.exception.SdkClientException: Unable to execute HTTP request: localhost.localstack.cloud
	at software.amazon.awssdk.core.exception.SdkClientException$BuilderImpl.build(SdkClientException.java:98)
...
Caused by: java.net.UnknownHostException: localhost.localstack.cloud
	at java.base/java.net.InetAddress$CachedAddresses.get(InetAddress.java:800)

Thanks for reporting @vicmosin . This hostname should be resolvable, but I guess there's a few ISPs that may be blocking it from getting resolved.
Would it be an option for you to add an entry to the /etc/hosts file?
Alternatively, you should be able to customize the API endpoint address by setting this environment variable in your LocalStack container: LOCALSTACK_HOSTNAME=<IP_ADDRESS>. Hope that helps - please keep us posted how it goes. Thanks!

@whummer I finally had a time to check proposed solution..
Changing hosts file indeed not an option. And regarding the environment variable - can you please elaborate how exactly it must be set from the test? I tried the following way and it didn't work:
@LocalstackDockerProperties(services = [ServiceName.S3], environmentVariableProvider = DefaultEnvironmentVariableProvider::class)
...
class DefaultEnvironmentVariableProvider : IEnvironmentVariableProvider {

    override fun getEnvironmentVariables(): MutableMap<String, String> =
        mutableMapOf("LOCALSTACK_HOSTNAME" to "<IP_ADDRESS>")
}

Me too.
The endpoints are entered in a strange combination.
I am currently using mac os, and when connecting localstack and application through docker-compose, it is assembled as a strange endpoint.
The bucket name and the container name are concatenated with ., and the endpoint is passed, resulting in an UnknownHostException.

Caused by: com.amazonaws.SdkClientException: Unable to execute HTTP request:   ${bucket_name}.${containerName}
Caused by: java.net.UnknownHostException:  ${bucket_name}.${containerName}


Supported RDS version and old references

https://docs.microsoft.com/en-us/deployoffice/deploy-office-365-proplus-by-using-remote-desktop-services#what-you-need-to-get-started
Here it states that only Windows Server 2016 is supported but more versions are mentioned here;
https://products.office.com/en-us/office-system-requirements
Both listings do not include a reference to Windows Server 2019.
But even when you only support Windows Server 2016 for RDS usage, in the next section, you are providing a link to install RDS on Windows Server 2008 R2. Later you are again referencing Windows Server 2008 R2 configuration instructions, and the Related Topics section contains only links for Windows Server 2008 R2, 2012 and 2012 R2 but none for Windows Server 2016.

This recent blog post contains some interesting info which could be good to be included in the official documentation; https://www.microsoft.com/en-us/microsoft-365/blog/2019/07/01/improving-office-app-experience-virtual-environments/

I've submitted PR #811 to include the updated system requirements as well as updated the links to remove any Windows Server 2008 references. Good catch and thanks for bringing it to our attention!


website blog: add post about Kythe's command-line tool [phab:D147]

Created by schroederc at 2015-03-27 22:13:31:

jdennett commented inline (context lost during migration) at 2015-03-27 22:31:45:
Drop the "For instance" -- "as a simple example" has that covered.

jdennett commented inline (context lost during migration) at 2015-03-27 22:31:45:
I'd s/contains/gives/ here, but YMMV.

jdennett commented inline (context lost during migration) at 2015-03-27 22:31:45:
I'd write "the Kythe tool" on the line above, and then "it" here instead of repeating "the Kythe tool".

jdennett commented inline (context lost during migration) at 2015-03-27 22:31:45:
it's -> its
(possessive pronouns don't have apostrophes).

schroederc wrote at 2015-03-27 22:41:28:
Edits

schroederc commented inline (context lost during migration) at 2015-03-27 22:41:33:
✓

schroederc commented inline (context lost during migration) at 2015-03-27 22:41:33:
✓

schroederc commented inline (context lost during migration) at 2015-03-27 22:41:33:
✓

schroederc commented inline (context lost during migration) at 2015-03-27 22:41:33:
✓

schroederc wrote at 2015-03-30 16:23:25:
Pingaroo

fromberger accepted this revision at 2015-03-30 17:18:22

schroederc closed via commit 08c3c7a4c188044ebd0dcab189e9018866acfd59 at 2015-03-30 19:08:56


create possibility to delete data

I would be good to be able to delete data sets. We often want to have a quick check if all data is recorded correctly, but we do not want to clutter the backend with many "*Test" or "*Dummy" entries.
Deletion should be possible, maybe after forcing the user to input the name of the experiment to make sure that deletion does not happen by accident.

Sure. I was also thinking of adding this to the backend. Might have time to add it shortly.


⚠ Bofrost.be has degraded performance

In 1884748, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2071 ms

Resolved: Bofrost.be performance has improved in 981afe2.


Logging the full data

In GitLab by @proyan on Feb 15, 2019, 13:07
Currently we are only saving the data.cost inside the logger.
I don't see why we can't save directly the shooting.datas after the iteration.
This would be really helpful for debugging purposes.

In GitLab by @cmastalli on Feb 15, 2019, 15:24
We're copying shooting.datas each iterates. Could you explain what do you mean with data.cost?
Callbacks are aim to be flexible, and the user is free to design its own one. We have coded some general purpose callback functions, and it's always possible to have a custom one.

In GitLab by @nmansard on Feb 15, 2019, 15:46
Ok, why not. I suggest to introduce a new call back for that, as I am afraid of the computation cost when copying the data.
The question is: is copy.copy() able to directly copy a ActionData, including the pinocchio data, our should we do some specific implementation for that.

In GitLab by @proyan on Feb 15, 2019, 19:55
pinocchio data would be useful. Currently we would need to enable pickling of the pinocchio data in order to do that, and that might take some time.
Meanwhile, just copying the other data elements might be a good solution.
I would suggest Logging levels, instead of a new callback.

In GitLab by @proyan on Feb 15, 2019, 23:12
I created a PR which makes all elements of pinocchio data copyable. https://github.com/stack-of-tasks/pinocchio/pull/682/files. This should partially help towards this issue and #108

In GitLab by @cmastalli on Feb 18, 2019, 08:12
I agreed with the logging levels. It seems a simpler approach for both: users, developers and maintainers. Just keep in mind that there are action models which doesn't use Pinocchio data.


Add TheBus Honolulu dataset to End to End workflow

Please create the PR and a member of the Mobility Data team will take it from here - thanks!

[x] This PR only touches end_to_end.ym in `.github/workflows
[x] -abort_on_error to false`
[ ] Null Pointer Exception --> add bug and NPE tag
[ ] Attach the dataset and report from the workflow run to this PR

Summary:
This PR provides support to add dataset from The Honolulu Bus to the end to end workflow
Expected behavior:
Explain and/or show screenshots for how you expect the pull request to work in your testing (in case other devices exhibit different behavior).
Please make sure these boxes are checked before submitting your pull request - thanks!

[ ] Run the unit tests with gradle test to make sure you didn't break anything
[ ] Format the title like "Fix #<issue_number> - " (for example - "Fix #1111 - Check for null value before using field")
[ ] Linked all relevant issues
[ ] Include screenshot(s) showing how this pull request works and fixes the issue(s)

Created for the walkthrough during the following event.

Closing for now


Test workflows

Pick a workflow and (try to) run through it. Fix the issues as you discover them.

Galaxy 101 [Sergey]
Sequence analysis mapping [Enis]
Microbial variant calling [Nuwan]
Formation of the Super-Structures on the Inactive X [Alex]

Not scheduling jobs:

De novo transcriptome reconstruction with RNA-Seq

Comments from going through the Sequence analysis mapping tutorial:

[ ] FastQC jobs never end
[ ] Missing mm10 reference genome (along with many more; only a single .loc file seems to be loaded)

Bacterial Variant Calling comments:
[ ] Installing snippy from toolshed works, but the toolshed state is stuck at: “Installing Tool Dependencies”.
[ ] changing the data type after upload results in an endless spinning wheel with “Metadata is being detected” or a message like “Try auto-detecting datatype or set it manually”
[ ] Snippy generates an error
[09:21:51] This is snippy 4.3.6
[09:21:51] Written by Torsten Seemann
[09:21:51] Obtained from https://github.com/tseemann/snippy
[09:21:51] Detected operating system: linux
[09:21:51] Enabling bundled linux tools.
[09:21:51] Found bwa - /usr/local/bin/bwa
[09:21:51] Found bcftools - /usr/local/bin/bcftools
[09:21:51] Found samtools - /usr/local/bin/samtools
[09:21:51] Found java - /usr/local/bin/java
[09:21:51] Found snpEff - /usr/local/bin/snpEff
[09:21:51] Found samclip - /usr/local/bin/samclip
[09:21:51] Found seqtk - /usr/local/bin/seqtk
[09:21:51] Found parallel - /usr/local/bin/parallel
[09:21:51] Found freebayes - /usr/local/bin/freebayes
[09:21:51] Found freebayes-parallel - /usr/local/bin/freebayes-parallel
[09:21:51] Found fasta_generate_regions.py - /usr/local/bin/fasta_generate_regions.py
[09:21:51] Found vcfstreamsort - /usr/local/bin/vcfstreamsort
[09:21:51] Found vcfuniq - /usr/local/bin/vcfuniq
[09:21:51] Found vcffirstheader - /usr/local/bin/vcffirstheader
[09:21:51] Found gzip - /bin/gzip
[09:21:51] Found vt - /usr/local/bin/vt
[09:21:51] Found snippy-vcf_to_tab - /usr/local/bin/snippy-vcf_to_tab
[09:21:51] Found snippy-vcf_report - /usr/local/bin/snippy-vcf_report
[09:21:51] Checking version: samtools --version is >= 1.7 - ok, have 1.9
[09:21:51] Checking version: bcftools --version is >= 1.7 - ok, have 1.9
[09:21:51] Checking version: freebayes --version is >= 1.1 - ok, have 1.2
[09:21:51] Checking version: snpEff -version is >= 4.3 - ok, have 4.3
[09:21:51] Using reference: /galaxy/server/database/jobs_directory/000/11/working/ref.gbk
[09:21:51] Treating reference as 'genbank' format.
[09:21:51] Will use 1 CPU cores.
[09:21:51] Using read file: /galaxy/server/database/files/000/dataset_18.dat
[09:21:51] Using read file: /galaxy/server/database/files/000/dataset_30.dat
[09:21:51] Creating folder: out
[09:21:51] Changing working directory: out
[09:21:51] Creating reference folder: reference
[09:21:51] Extracting FASTA and GFF from reference.
[09:21:51] Wrote 1 sequences to ref.fa
[09:21:51] Wrote 171 features to ref.gff
[09:21:51] Creating reference/snpeff.config
[09:21:51] Freebayes will process 1 chunks of 200727 bp, 1 chunks at a time.
[09:21:51] Using BAM RG (Read Group) ID: out
[09:21:51] Running: samtools faidx reference/ref.fa 2>> snps.log
[09:21:51] Error running command, check out/snps.log

The most common error that came out of going through my tutorial is the fact that all the tools under the deeptools package don't work. The first problem a few days ago was that the job containers were using a galaxy image which didn't have the binaries for the tools in its path. That seems to be solved now, as mulled containers seem to be prepared for the job. However, that is not successfully happening. Specifically, one problem is that curl is not on the path, which impedes fetching involucro. I fixed that temporarily by exec-ing as root and installing curl, after which involucro started being successfully fetched. The error now seems to have to do with an inability to properly create the container, but I am not entirely sure:
[Jun 14 21:13:59] ERRO Task processing failed: Docker not reachable: Get http://unix.sock/_ping: dial unix /var/run/docker.sock: connect: no such file or directory
galaxy.jobs.runners ERROR 2019-06-14 21:14:59,484 (3) Failure preparing job
Traceback (most recent call last):
File "/galaxy/server/lib/galaxy/jobs/runners/__init__.py", line 230, in prepare_job
stderr_file=stderr_file,
File "/galaxy/server/lib/galaxy/jobs/runners/__init__.py", line 260, in build_command_line
container = self._find_container(job_wrapper)
File "/galaxy/server/lib/galaxy/jobs/runners/__init__.py", line 428, in _find_container
job_info
File "/galaxy/server/lib/galaxy/tools/deps/containers.py", line 98, in find_container
container_description = self.find_best_container_description(enabled_container_types, tool_info)
File "/galaxy/server/lib/galaxy/tools/deps/containers.py", line 50, in find_best_container_description
container_description = self.container_registry.find_best_container_description(enabled_container_types, tool_info)
File "/galaxy/server/lib/galaxy/tools/deps/containers.py", line 229, in find_best_container_description
container_description = container_resolver.resolve(enabled_container_types, tool_info)
File "/galaxy/server/lib/galaxy/tools/deps/container_resolvers/mulled.py", line 458, in resolve
)
File "/galaxy/server/lib/galaxy/tools/deps/container_resolvers/mulled.py", line 193, in docker_cached_container_description
File "/galaxy/server/lib/galaxy/tools/deps/container_resolvers/mulled.py", line 66, in list_docker_cached_mulled_images
log.warning(command)
File "/usr/lib/python2.7/subprocess.py", line 216, in check_output
process = Popen(stdout=PIPE, *popenargs, **kwargs)
File "/usr/lib/python2.7/subprocess.py", line 394, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1047, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory

This appears to be a docker-in-docker issue. Since involucro needs to build the docker image, that naturally means we will need a running docker daemon. The first question I suppose is, can we not pre-build the image instead?
If we must do this, I think mapping in the parent's docker socket (i.e the one used by kubernetes) is highly undesirable.
This article has a good discussion on alternatives: https://medium.com/hootsuite-engineering/building-docker-images-inside-kubernetes-42c6af855f25
We'll still need to run a privileged container, but only for building the containers.

With regard to the de-novo workflow: The issue is that the workflow execution manager doesn’t support db-skip-locked. Removing the db-skip-locked handler allows the workflow to execute. It looks like we'll have to have a dedicated handler with an alternative method for processing workflows.

The denovo workflow doesn't run because of the following issue
Error: Unable to access jarfile /trimmomatic.jar
readlink: invalid option -- 'e'
BusyBox v1.22.1 (2014-05-23 01:24:27 UTC) multi-call binary.

Usage: readlink [-fnv] FILE

Display the value of a symlink

	-f	Canonicalize by following all symlinks
	-n	Don

The issue is clearly caused by busybox not supporting the -e flag. It looks like trimmomatic will need a new container with this issue fixed.

the workflow execution manager doesn’t support db-skip-locked

It should support it but it's not recommended because it means multiple workflows in the same history can be scheduled concurrently, jumbling up the datasets. I mentioned to @afgane just now:

￼￼￼￼￼nate 10:48
It's supposed to handle this case and db-skip-locked is supported just not recommended (although fine in your case if you only have one handler) but anyway, keep the db-skip-locked job handler and use workflow_schedulers_conf.xml to set up a db-preassign or db-self workflow scheduler


Add type stubs for the sqlalchemy models

This means that we get real type checking for the model types, rather than the Any checking which we were previously getting.
This currently errors due to the issue which #68 fixes (though amazingly shows no other issues), so I consider this blocked until that merges.

Coverage remained the same at 100.0% when pulling 845be46d250c6792799a1a67e1b6710a04074930 on models-type-stubs into ca9d805af99e88e919a662f96469ce9e932c1088 on master.

@PeterJCLaw hope you don't mind, I've merged this. Happy to review any further changes in another PR.

@danpalmer no worries; I'd actually forgotten about this PR. (I think I wasn't sure whether your comment was blocking, hence not merging it at the time)


Column Visibility from javascript is not working

I have tried to set Column Visibility from client side.
as directed HERE
On Line 78
On this code MVCGrid.setColumnVisibility('ColumnVisibilityGrid', jsonData);
I am getting below error
Uncaught TypeError: **Cannot read property 'qsPrefix' of undefined**
    at Boolean.<anonymous> (script.js:282)
    at Function.each (jquery-2.2.3.min.js:2)
    at Object.setColumnVisibility (script.js:281)
    at HTMLDocument.<anonymous> (Receipt:73)
    at i (jquery-2.2.3.min.js:2)
    at Object.fireWith [as resolveWith] (jquery-2.2.3.min.js:2)
    at Function.ready (jquery-2.2.3.min.js:2)
    at HTMLDocument.J (jquery-2.2.3.min.js:2)

According to above link I have set the column properties as
.WithAllowChangeVisibility(true)
.WithVisibility(false)

and tried
.WithVisibility(false, true)
and
.WithVisibility(visible: false, allowChangeVisibility: true)

Any Help is highly appreciated..

I found answer to this by my self.
This code
MVCGrid.setColumnVisibility('ColumnVisibilityGrid', jsonData);
is supposed to call on click event of a button.
I was trying to call it on document ready.
because i wanted to set few columns to be visible automatically without asking user to choose columns.
I, also, tried to call jquery trigger click function on document ready but NO LUCK :(
see my not working code below

@section scripts{
    <script type="text/javascript">
        $(function () {

                var jsonData = {};
                jsonData["Col_3"] = true;
                jsonData["Col_4"] = true;
                jsonData["Col_5"] = true;
                MVCGrid.setColumnVisibility('MyGrid', jsonData);

        });
    </script>
}

There has to be a way to call this functionality on page load/ document.ready
ANY SUGGESTIONS??

Try this:


Legacy VoIP Background Mode?

Hello,  I've integrated this plugin. When my app goes to the background, I can see this in the console:
Legacy VoIP background mode is deprecated and no longer supported
Is there anyway to use the non-legacy version?

Hi,
There is a new set of Twilio clients that support the new CallKit modes for iOS, called Twilio Voice - I have a plugin that supports an older version of Twilio Voice that I need to update - it is not directly compatible with the Twilio Client project.
I think you can safely build with this version for now, and then port later to the other plugin.

Hi thanks for replying! Sorry I misunderstand your directions.  are you basically saying to just ignore it and this current plugin as for now, and then later port it when you fix it?
When you say "I have a plugin that supports an older version of Twilio Voice that I need to update" are you referring to this plugin we're commenting on?

Hi,
There's another plugin that I wrote here:
https://github.com/jefflinwood/twilio-voice-phonegap-plugin
It needs to be updated to the latest versions of the Twilio Voice SDK's.  That should solve your background issues - otherwise, you'll need to send push notifications to your app when you get an inbound call.
Thanks!

Thanks for clarifying.
What are the differences between these 2 plugins, by just reading the name it sounds more like I should have been using that plugin all along.

Hi,
Well, the big difference is the underlying libraries - the plugins just wrap the Twilio client libraries.
Also, the Voice plugin doesn't have documentation yet. It does have a sample app.
You could probably use that one, it uses access tokens, not capability tokens - like the ones in the Twilio Voice iOS quickstart.

@jefflinwood Is the plan to eventually deprecate this library in favor of twilio-voice-phonegap-plugin?

Hi,
I'm not planning to deprecate this plugin unless Twilio stops supporting the underlying client libraries (because it tracks those libraries).
Thanks!


uninitialized constant Sass::Rails::SassTemplate in production

After migrating from Rails 3.0.10 to 3.1.0 i get this error on my production server (in development app works ok):
gems/sass-rails-3.1.0/lib/sass/rails/railtie.rb:38:in `block in <class:Railtie>': uninitialized constant Sass::Rails::SassTemplate (NameError)

I already have sass-rails in my :assets group and still get this error
I tried changing my heroku config RAILS_ENV and RACK_ENV from staging to production but that didn't do it either
Any clues? Thanks!

@joemsak , so as @tracedwax said, move your sass-rails out of assets group, just instead of:
group :assets do
  gem 'sass-rails'
end

do:
gem 'sass-rails'

Wow, talk about reading comprehension! Sometimes the brain just doesn't function right when you're trying to push a demo out for a client and you start getting errors on your deploy! That worked for me, thanks again!

thanks tracedwax, worked for me! was having such a headache on heroku

Glad to hear!
On Tue, Dec 13, 2011 at 1:07 AM, stringpane <
<EMAIL_ADDRESS>
wrote:

thanks tracedwax, worked for me! was having such a headache on heroku

Reply to this email directly or view it on GitHub:
https://github.com/rails/sass-rails/issues/38#issuecomment-3119345

sip

I tracked the problem to lib/active_admin/appliaction.rb:80, generate_stylesheets should not be called on production. The solution is a two step process, first change the line to generate_stylesheets unless Rails.env.production? and then you need to add active_admin.css and active_admin.js to the list of precompiled manifests with config.assets.precompile += %w/active_admin.css active_admin.js. On my tests i did this on RAILS_ROOT/config/application.rb, but this should be done from the engine.

The ActiveAdmin issue is not related to sass-rails. I posted a possible solution to it as a comment to #GH-447

Thanks. Closing again.


Config

#13

Feature has been implemented. Testing and Documentation for configurations are requred

CI is failing because of Swift 4.2

Comparator can be potentially moved into separate repo as a package. Looks like really usable concept which could be extended with move functionality. For example converting into NSSortDescriptor.


#514 fixing composed schema parsing

Fix #514
added a test for each composedSchema

Thank you! @phiz71

@phiz71 sorry, should have merged in order. Can you resolve the conflict and then I'll merge?

Done

Thanks, @phiz71!


[Request] Indoor maps support regarding

Not an issue per se` but a request
I have been going through some angular2 libraries that support google maps and I have found yours so stable. So kudos to every contributor on the great work.
I have seen plain google-maps javascript APIs support Indoor navigation on the listed places here
https://support.google.com/maps/answer/2803784
https://support.google.com/maps/answer/1685827
I have gone through your documentation and I didn't see any module or component talking about indoor navigation.
It would be of great help if anyone throw some light on whether this indoor navigation attribute can be included in my angular 2 apps with your plugin.
Thank you.

reading the google docs i think this feature will appear in any map if it looks at a location that has a floorplan.  it does not seem to need a data layer or other special object in the map view.
the docs talk about how to upload a floor plan to a building, that is something done outside of the maps view control.

by the way:  if you wanted to create a map view in your own app that has a floor plan that would not be found by the normal google maps  you might use the GeoJSON format with a google data layer, that would be custom to your app and GeoJson let's you draw lines by lat,long coordinates, you could use that to make a very detailed plan and keep in only in your app for your users.
but you would need to spend time creating the map for that location.

Hi Sebastian,
Thanks for your quick reply.
I have already integrated AGM in my existing angular app.(with a location in the list of indoor capable locations that I've added above)
you can see the same place with similar zoom levels in the below links.
https://rajagopal28.github.io/Donna/#/google-indoor
https://www.google.co.in/maps/place/Wembley+HA9+0WS,+UK/@51.5559249,-0.2797843,19z/data=!3m1!5s0x48761181d3a805e3:0x9d43d00915aa8b10!4m5!3m4!1s0x48761181d1c44619:0x115ed5b0b451acf!8m2!3d51.5560208!4d-0.2795187
My observation is that on the google map link I see clickable hotspots in and the +/- buttons change to a list of buttons to switch between building levels. So I assumed tt has something to do with the API layer that you are using. Please correct me if I am wrong.

that maps of wembley looks like it might be a set of data layers to me, that is a just a guess.  it might also be google adding it to the map, large venus like that i suspect are treated special by google.
there used to be an app that google owned that was built for making floorplans and it was linked to google maps but they sold it.

Yeah, I felt that too. Upon similar searches around google's indoor maps I found a similar module related to NativeScript in the following URL. I've noticed(but haven't tried on my own) that they are enabling the indoor maps support with a statement something like this
this.mapview.googleMap.setIndoorEnabled(true);
this.mapview.googleMap.getUiSettings().setIndoorLevelPickerEnabled(true);

to enable indoor layer. This is the major reason I've raised this request to check whether any similar thing can be done with AMG.
http://android.wekeepcoding.com/article/11045549/Nativescript+Indoor+Ground+Map
Thanks

Hi. I have tried the above snipped on NativeScript(with Angular2) and it works absolutely fine. Is there a way I can do similar thing in plain Angular2 with AGM.
The actual code here. Will add screenshot bit later.
https://github.com/rajagopal28/Donna/blob/master/nativescript/app/google-indoor/google-indoor.component.ts

Guys , I am too looking for enabling Indoor Map with floor selection buttons in this library, Is there a way ?


body.modal-opened on modal open

Add class .modal-opened to  on opening/closing modals, to handle no scrollbars in the DOM (like prevent glitchy movement on overflow: hidden)

&.modal-opened {
padding-right: 17px;
box-shadow: inset -17px 0 0 0 @your_color;
}

&:not(.modal-opened) .modal {
right: -17px;
}


IDVA50-localisation for 'What is your date of birth?' screen.

localisation to 'What is your date of birth?' screen.

CI: No security warnings found


Keeping MEAN app user/session data segregated

I would like to use one MongoDB datastore for the UI-specific functionality (users, sessions, etc) and would like to be able to use another for everything else. What's a good and clean way to implement this? Anyone got some examples or a write up by chance?

http://stackoverflow.com/questions/19474712/mongoose-and-multiple-database-in-single-node-js-project
http://mongoosejs.com/docs/connections.html
Feel free to come back with further questions.

Thank you :) I was looking for some insights on implementing it within a mean.js build, specifically. Any input there?

What's the issue with using collections in the database? You would avoid lots of headache.


Adding date ranges in piwik charts and fixing chart drawing issues

fixes #369

Had some strange issues on my mobile, the view graph was always the same
even when I've changed the date range. Maybe got a different IP on the
way...
Seen some errors in the logs very close to my attempts
Caused by: org.dspace.authorize.AuthorizeException
        at
cz.cuni.mff.ufal.PiwikStatisticsReader.setup(PiwikStatisticsReader.java:122)

If I am already at the stats page do I get notified/asked to login again
when my session expires?
Seems good on "normal" computer, but it should at least say when the item
was added, right now you do not know if the "zeros" are there because there
was no activity or whether the item was not present yet.
2016-03-16 15:57 GMT+01:00 Amir Kamran<EMAIL_ADDRESS>
fixes #369 https://github.com/ufal/lindat-dspace/issues/369
You can view, comment on, or merge this pull request online at:
https://github.com/ufal/lindat-dspace/pull/498
Commit Summary

Adding date ranges in piwik charts and fixing chart drawing issues

File Changes

M
dspace-xmlui/src/main/java/cz/cuni/mff/ufal/PiwikStatisticsReader.java
https://github.com/ufal/lindat-dspace/pull/498/files#diff-0 (24)
A
dspace-xmlui/src/main/webapp/themes/UFAL/lib/css/daterangepicker.css
https://github.com/ufal/lindat-dspace/pull/498/files#diff-1 (232)
A
dspace-xmlui/src/main/webapp/themes/UFAL/lib/js/daterangepicker.js
https://github.com/ufal/lindat-dspace/pull/498/files#diff-2 (1542)
A dspace-xmlui/src/main/webapp/themes/UFAL/lib/js/moment.min.js
https://github.com/ufal/lindat-dspace/pull/498/files#diff-3 (7)
M dspace-xmlui/src/main/webapp/themes/UFAL/lib/js/piwik_charts.js
https://github.com/ufal/lindat-dspace/pull/498/files#diff-4 (216)
M
dspace-xmlui/src/main/webapp/themes/UFAL/lib/xsl/aspect/artifactbrowser/item-view.xsl
https://github.com/ufal/lindat-dspace/pull/498/files#diff-5 (82)
M
dspace-xmlui/src/main/webapp/themes/UFAL/lib/xsl/core/page-structure.xsl
https://github.com/ufal/lindat-dspace/pull/498/files#diff-6 (4)

Patch Links:

https://github.com/ufal/lindat-dspace/pull/498.patch
https://github.com/ufal/lindat-dspace/pull/498.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/ufal/lindat-dspace/pull/498

Piwik charts are still in beta so you can add the comments as issues/improvements and we can merge these changes if not breaking anything else.

ok, but I see some other issues
Uncaught TypeError: Cannot read property 'replot' of undefined

hm, I lost the filename and linenumber :( It was somewhere in piwik_charts.js I believe
Large ranges on the first attempt seem to take a lot of time

and I didn't see any hourglass or animation indicating that something is happening.
I still don't understand how to operate the calendar for custom ranges.
Maybe still good enough for beta, just try checking the replot issue and whether the rest I was describing is still according to your expectations...

Uncaught TypeError: Cannot read property 'replot' of undefined piwik_charts.js:241


resolve issue with numeral form for number 11.5

resolve issue with numeral form for number 11.5
whereas numeral 11 or 2011 etc are generated correctly.

Resolved by commit c84d3691ff5625a5c2aa06b91a4639a7119d0052


added titles to segmented-buttons

fixes #345

Coverage increased (+0.02%) to 87.58% when pulling 927bd5d001309f66915f9fe6a3748fb174012841 on segmented-button-title into c6376bcf6c8f57fc8797f88cd94b0553065d8d95 on master.


Hollister, CA - Letter to Revise City Budget

To<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>[INSERT UNIQUE SUBJECT LINE]
Dear Mayor Velazquez and Hollister City Council,
My name is [YOUR NAME] and I am a resident of Hollister. I am writing to demand that the Hollister City Council adopt a city budget that prioritizes community well-being, and redirects funding away from the police.
In the 2018-2019 fiscal year, the City of Hollister allocated an increase of 2.4 million dollars to our police system. In the 2019-2020 fiscal year, Hollister administered another increase of 1.6 million dollars to our police system, equating to an inordinate 44% of our total budget at 26.4 million dollars. This is compared to just 14% of the budget, $8.3 million, allocated towards community services and supplies - an 18% decrease from the 2018-2019 budget. It has been estimated that there will be a 54 billion dollar deficit in the California state budget as a result of the pandemic. Our local San Benito High School is preparing for significantly less funding following this crisis. The city may recoup some of these funds by decreasing the police budget.
I demand that the City Council begin meaningfully defunding the Hollister Police Department and re-allocate those funds to programs proven to more effectively promote a safe and equitable community. We need funding for community-based mental health services, substance abuse treatment services, and affordable housing programs, not police. I love this community and I want to see it flourish into an even better one. I demand a budget that reflects the actual needs of Hollister residents and works to improve the well being of everyone who lives in and visits this city.
History has shown that police "reform" is not enough. No more money, and more importantly, no more lives must be lost to police. We must take a hard look at the way the current system in place fails to serve - and in fact actively harms - our community, and come together to reimagine the role of police in our city.
I am urging you to completely revise the budget for the 2020-2021 fiscal year, and to invest in the people, not the police. We trust that you will do the right thing for us, because we put our trust in you when we elected you to serve us. This is a moment for you to step up and show us that you care for our community as much as we care for each other and this city.
Thank you for your time,
[YOUR NAME]
[ADDRESS]
[EMAIL]
[PHONE #]

This one is really nice!

on it


potential fix for #333

I havent forgotten, but spare time is lacking right now.

This does give me a more stable scrolling experience, but it doesn't seem to calculate to bottom of the table correctly. The original version scrolls out of frame, but you version keeps visible untill the next thead.

Hi there, I arrived by miracle on this library. Thanks! I am testing it. The little bouncing/shaking effect when scrolling using the mouse wheel still there. I'm using Microsoft Edge. Something interesting here: when I use the scroll bar instead of the mouse wheel, there is no bouncing/shaking effect.

I will really look at this soon!

sorry, this PR isn't going to happen.


add CreateTopicsRequest/Response

follows on from #852 with the necessary request/response pair for creating topics.

Thanks!


 We do need to update the URLs…

yeah i wasn't sure if i did it right, but i will try again with all the updated URLs in 1 commit instead.

submitted new pull request.


feat(api): include parameter to omit feature gate data

Hi again!
Had a scenario where I only needed feature state data returned by the API, and it was preferable to strip out the additional gate data (i.e. prevent exposing actor IDs).
It's easy enough to monkey-patch, but figured someone else may want simplified data returned as well, so here's a PR to make it an option!
Thanks!

Any thoughts on making this a param in the url (say ?exclude_gates=true or something) instead of a config option?

Any thoughts on making this a param in the url (say ?exclude_gates=true or something) instead of a config option?

Awesome idea - that makes it much more flexible 👍 . Will do!

Updated this since docs have been moved out the repo. Not sure how to update docs now, but this should be good to go as far as code goes.


Error: The module './node_modules/pcap/build/Release/pcap_binding.node'

Error: The module './node_modules/pcap/build/Release/pcap_binding.node' was compiled against a different Node.js version using NODE_MODULE_VERSION 64. This version of Node.js requires NODE_MODULE_VERSION 87. Please try re-compiling or re-installing
I'm new to both electron and pcap. Can u please help how to solve this error?

Getting the same issue, You got any idea how to resolve?


Update setup.py

Add "-fopenmp" option ,then the code can use openmp

how about users doesn't have openmp installed?


add bat

https://github.com/astaxie/bat

Could be improved by https://github.com/astaxie/bat/issues/38


stats: setReportingPeriodReq.handleCommand should never block

Ensure that *setReportingPeriodReq.handleCommand always
sends to the command's channel, even when the worker's
duration <= 0.
Fixes #150

Hmm, for some reason Travis-CI hasn't yet responded.

Can you amend and repush? Travis didn't seem to the receive the PR.

Travis seems to be down, they don't list any of the new incoming PRs: https://travis-ci.org/census-instrumentation/opencensus-go/pull_requests. I am disabling the precheck until they fix it. Appveyor CI precheck is good enough.

Awesome, thanks!


fix: fix this in ctor default param transform into undefined

Summary
Fix #5786

Require Documentation?

[x] No
[ ] Yes, the corresponding rspack-website PR is __

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I think the index.js in the test case should be as follows:
class A {
  constructor(func = () => { this.a = 1 }) {
		func()
	}
}

it('ensure top level is right in constructor', () => {
	const a = new A();
	expect(a.a).toBe(1)
	expect(typeof a).toBe('object')
})

export default '';

Added

Thanks!


Adjust the V calling convention to aid lazy binding

The whole point of this VARIANT_CC bit is that we want to be able to use
V registers in _dl_resolve without saving them.  That requires that the
interface between the caller and the callee does not rely on the values
in the V registers.  That's a bit different than how we've histrorically
defined these temporary register clobbers, which is about the the
caller-side visibility into register changes.
Signed-off-by: Palmer Dabbelt<EMAIL_ADDRESS>

Spited from #286, https://github.com/riscv-non-isa/riscv-elf-psabi-doc/pull/286/commits/eefd8b0e5a963391e63a15b65e41ee2945c80534 but slightly modification which is address by #290, @palmer-dabbelt let me know the change is look good to you :)

Changes:

Keep most of current wording, and re-write last sentence


After crash, can't start browser

OS: OSX 10.12.6
Beaker Version: Latest?
Uncaught Exception:
TypeError: Cannot read property 'getPrimaryDisplay' of null
    at defaultState (/Applications/Beaker Browser.app/Contents/Resources/app/background-process.build.js:3908:31)
    at restoreState (/Applications/Beaker Browser.app/Contents/Resources/app/background-process.build.js:3904:28)
    at createShellWindow (/Applications/Beaker Browser.app/Contents/Resources/app/background-process.build.js:3817:60)
    at ensureOneWindowExists (/Applications/Beaker Browser.app/Contents/Resources/app/background-process.build.js:3866:5)
    at App.electron.app.on (/Applications/Beaker Browser.app/Contents/Resources/app/background-process.build.js:5586:35)
    at emitTwo (events.js:106:13)
    at App.emit (events.js:194:7)

This happened immediately after forking Rotonde. 🤷♂

Ok this is a duplicate of https://github.com/beakerbrowser/beaker/issues/690. Weird bug, I'll look into it. (Closing this one as a duplicate.)


Feature request: An option to convert snake case to camel case?

Currently welcome.with_name localization key generates welcomeWith_name function. That's a weird name. I'd like to introduce an option to generate welcomeWithName function instead.

Rswift does not have options to modify the generated code.
If you require more control over the code that is generated, take a look at https://github.com/SwiftGen/SwiftGen


privacy page bug

https://gatsby-theme-netlify-identity.netlify.com/privacy

Great work anyway;) would have probably choosen this theme for my blog if MDX was supported (and if it was possible to make it less girly too :))

Thanks for bringing this up!! I've been swamped with work lately.
I'll take a look at adding in MDX because that sounds great from an editorial standpoint (carousels, lightboxes, etc.). However I think the style stays :)

Hi, I finally got a smattering of time to work on this and it's all fixed. Just a bad import statement for the SEO element. Thanks again for catching it!


Add a Gitter chat badge to README.md

benas/jPopulator now has a Chat Room on Gitter
@benas has just created a chat room. You can visit it here: https://gitter.im/benas/jPopulator.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Mahmoud Ben Hassine » jPopulator #94 SUCCESS
This pull request looks good
(what's this?)


Add option to ignore tool exit code

The current default behaviour in Tool.ProcessExitCode() is to throw an exception if the exit code is non-zero.
There may be occasions where ignoring the exit code is preferred as additional processing is needed before the underlying error is handled.
For example, when running unit tests with dotnet test (via DotNetCoreTest) in a CI pipeline, rather than failing immediately upon test failure, it might be that uploading the test results would be the way the pipeline recognises the failing tests and then fails the build.
As such, I think it would be useful to have a property in Settings that can be set to enable ignoring exit codes

Yes, it will be very much useful. Facing the issue with same problem. Whenever one of the test is failed then process stopped there it self.

Fixed by #2826


One click installer setup for MacOS

Adding setups required for building one-click installers for MacOS.
Fix #948

@pseudotensor I was able to build it successfully and run it on my Mac M1 (CPU). I will share the artifact (uploaded to our s3) with you on Slack so you can test it (if you have Mac M1). Will also ask folks from the SL team with Mac M1 to try it, and tackle the issues as they arise.
I work on the Mac M1 (MPS) installer on a separate PR.

@gumbolastima Normally it should open with the terminal by default,
After downloading, double-click on the app, "Get Info" -> "Open With" -> set to terminal
And may I know which Mac device you are using?

@gumbolastima it would take a few minutes to unbundle and run the app. Give it some time when the terminal opens
If it doesn't work, could you please attach the screenshot of the terminal?

yes, it is unsigned, I will update it on the docs.
If you stumble into any other issue please report, it is still experimental, so your feedbacks is highly appreciated


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-sandbox/eventing-writers
/assign knative-sandbox/eventing-writers
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/control-protocol 79a0b1a...7e6cdf9:
  > 7e6cdf9 upgrade to latest dependencies (# 146)
  > b3c1e1b fix call to WaitUntilJobDone + update some dependencies  (# 148)
  > f22e1be Update community files (# 147)
  > 2c5188e Update actions (# 145)
bumping knative.dev/eventing f2045b0...9590bc3:
  > 9590bc3 adding min and max nodes annotation to rekt tests entrypoint (# 6243)
  > 4252411 Increase rekt test timings and reduce concurrency (# 6221)
  > 6fabdd5 Remove a second trigger of the autoscaler (# 6203)
  > 28a968c upgrade to latest dependencies (# 6230)
  > b349443 fixed links to source.md (# 6223)
  > f40fc74 Zero placements for rebalancing (# 6204)
  > 78aae1e Update community files (# 6220)
  > fdaca85 Update actions (# 6218)
  > 7ab1b0e upgrade to latest dependencies (# 6216)
bumping knative.dev/pkg fe26417...2fdd5f2:
  > 2fdd5f2 Update actions (# 2449)
  > 76a28b0 set git user name/email prior to merging upstream (# 2448)
bumping knative.dev/reconciler-test 2c3291f...84821d2:
  > 84821d2 Retry on context deadline exceeded errors (# 305)
  > d6d7c14 Update actions (# 291)
  > e2e54d1 Update community files (# 298)
  > 1b5d730 upgrade to latest dependencies (# 296)

/retest

/test pull-knative-sandbox-eventing-kafka-integration-test-mt-source

/lgtm
/approve


Unable to bind address when using repo

I am using the repo version so my run list is[ nginx::repo, nginx::default] but it results in:
STDERR: nginx: [emerg] bind() to <IP_ADDRESS>:80 failed (98: Address already in use) from recipes/default.rb:24

Hi,
same issue.
does anyone have a workaround ?
regards

I've just run into this on Ubuntu 14.04 with the nginx repo install. Everything would install OK but when run again I would get the bind error.
The problem for me was to do with the service definition and pid files.
I found that changing the pidfile location fixed it for me. I have this in my recipe:
# Install nginx from the nginx repo
node.default['nginx']['repo_source'] = 'nginx'
# Tell nginx to use the pid file that that the Ubuntu 14.04 nginx repo defines in the init.d file
node.default['nginx']['pid'] = '/var/run/nginx.pid'

include_recipe 'nginx::default'

I think it's kind-of related to https://github.com/miketheman/nginx/issues/248

@stekershaw Thanks for help. There is related PR https://github.com/miketheman/nginx/pull/223/files which was merged and that's a bit weird because I'm using ubuntu-14.04.3-server-amd64 and /var/run/nginx.pid works instead of /run/nginx.pid.

Can you check the current release of the cookbook to see if you are still having this problem? There have been a number of updates that have been merged in recently. Please reopen if you are still seeing this problem.


Document role requirement for multi-resource metrics queries

React to feedback in https://github.com/Azure/azure-sdk-blog/pull/479#discussion_r1556370730. Also apply small changes as part of a cross-language README consistency review.

API change check
API changes are not detected in this pull request.


type 'Future' is not a subtype of type 'Widget'

Steps to Reproduce

...
...
...

Target Platform:
Target OS version/browser:
Devices:
Logs

Unfortunately, this report does not have any actionable information - it’s not clear if this is a bug in user code, a bug in the framework, or something else entirely.
Please feel free to comment and I will re-open if you can add the following information:
The version of Flutter you’re using
The output of flutter doctor -v
The full exception you see
A minimal reproduction that leads to this exception.

Flutter 1.12.13+hotfix.5
• Engine revision 2994f7e1e6
• Dart version 2.7.0
type 'Future' is not a subtype of type '() => void'
The relevant error-causing widget was
DetailBox


rage package naming

While wanting to package your rage program I realized package and binary name
will probably conflict with Rage [0] that is already available in the target
linux distribution as "rage".
Do you know if others ran into this situation as well and how they solved it?
Does this upstream project has preferences if and what alternative name I can
use instead (rustage, ager, ...) ?
Do you have experience/ideas what parts of the code have to be touched/changed
downstream to use a different name than "rage"?
Is it maintainable by replacing some strings programatically
or are issues and new bugs likely if I have to change name,
man pages, bash completetion, ... and propably more in order to make it work
with a different name?
Thank you for this software!
[0]
https://www.enlightenment.org/about-rage

I do not know how others have addressed this previously (thus far I have only been distributing this as binary tarballs and .deb packages uploaded to GitHub, as well as the rage binary crate on crates.io).

As fas as package naming goes, as long as the name includes rage then I don't have a strong care, but we should have a consistent fallback name to use where necessary.
Considered and rejected:

rustage doesn't contain rage (and feels weird).
ager nopenopenope 😝
age-rs doesn't contain rage.
rage-rs adds a redundant language indicator; if we're going to add a tag, it may as well be useful.
rage-encrypt doesn't convey the right meaning (the tool can decrypt as well).

I think I'd suggest rage-encryption as a reasonable fallback:

It conveys that it's related to encryption.
It's close to the canonical URL https://age-encryption.org/
It's a bit long, but users would only be typing that in once at install time).

As far as the binary goes, I would really prefer not to have the binaries renamed. How does the target linux distribution you are packaging for handle binary name conflicts?

[...]
Thank you very much for the answer!

As fas as package naming goes, as long as the name includes rage then I don't have a strong care, but we should have a consistent fallback name to use where necessary.
[...]

While building and packaging locally I came to the same conclusion that an
alternative name should keep starting with "rage".
In my current somehow working implementation I'm using "ragecrypt" as
package and binary name but this can be changed easily.
What is your opinion about this name?
With a small script I'm replacing most but not all references to "rage" with
"ragecrypt" in the source code.
Of course this might break on updates if upstream changes are somehow
incompatible with this script.

I think I'd suggest rage-encryption as a reasonable fallback:
[...]

With "rage-encryption" as package name I'm fine but if the binary name has
to be changed as well, it seems useful to keep both names in sync.
If the binary is not called "rage", something shorter than "rage-encryption" used
for both names might be preferred?

As far as the binary goes, I would really prefer not to have the binaries renamed. How does the target linux distribution you are packaging for handle binary name conflicts?

From this distribution point of view, as I understand it, the preferred
solution for software with different functionality but conflicting binary name is to
"Convince upstream to rename the binaries to something less generic (or just less conflicting)." [1]
;)
So, this is what I'm trying first and the downstream renaming is only
a fallback solution and probably not the most stable one.
If doing the later, it would be nice if at least the same fallback name is used
by different distributions and this is best decided and
coordinated by upstream in my opinion.
[1]
https://en.opensuse.org/openSUSE:Packaging_conflicts

"Convince upstream to rename the binaries to something less generic (or just less conflicting)." [1]

I'll rule this out right now: I will not be renaming the rage binary in this repository:

I'm intentionally keeping close to the age binary, in naming and CLI usage.
The primary audience of the rage binary is sysadmins, and I would not expect the servers they are administrating to ever have a media player installed.
The secondary audience is regular users, but CLIs

"Convince upstream to rename the binaries to something less generic (or just less conflicting)." [1]

I'll rule this out right now: I will not be renaming the rage binary in this repository:

Thank you for this clear and reasonable statement.
[...]
As packager I'll investigate which options remain:

perhaps the media player package accepts a rename,

adding explicit "Conflicts" statements to prevent parallel installation of
both packages, keeping the binary but changing the package name,

do not submit this package to the more "official" repositories,

rename package and binary downstream as described previously.

If going the last route, I'll probably follow what you propose as
package/binary alternative name.
It would be nice if you (upstream) are aware of the renaming approach [2] and
perhaps you think of it doing source code changes touching strings with "rage"
included in the future.

I'll have a bit more of a think about fallbacks. We definitely want something consistent, because even if the binary is not renamed here, OS integrations for example would need to be aware of the potential naming difference.

Very appreciated that upstream considers possible downstream issues!
[2]
https://build.opensuse.org/package/view_file/home:cunix:rust/ragecrypt/name_string_replacement.sh

I appreciate the effort you're putting into finding a solution here 🙂 Program names are an inherently uncoordinated global namespace, that downstream package managers attempt to coalesce into their personal coordinated global namespace in a variety of different ways (e.g. Gentoo using category prefixes like app-crypt/age to reduce collisions, vs Debian's purely-global repository). I'd love to see better solutions for handling this at the package manager level, because it's not a scalable solution for maintainers to be doing individualised work for every conflicting package, of which there will be a multitude more than there are package managers.
If I had a magic wand to wave, my ideal scenario would be that the user installing the package could decide how to resolve this; if they tried to install both packages at once, the package manager would ask them which they want to refer to as rage, with both having fallbacks. I guess the closest to this for your target distribution is Conflicts, but it would be nice if there were a way for the user to pick a resolution rather than requiring "either-or".

hey @cunyx I'm trying to package rage again, and I'm not exactly going to ask either party to rename things! I think we can go with a name like rage-encryption for the package, and then we need to check to see if enlighnment has any file conflicts.
@str4d If the package "zypper install rage-encryption" was how it was done, that would be okay to you? The binary it installs would still be rage and rage-keygen.

Yeah, I'm fine with rage-encryption as a fallback package name when the package manager hasn't built another form of domain separation. A little long, but it's a one-time operation per user, so I err on the side of clarity.

Excellent! In that case, did you want to put that on the readme.md so that other distros in the same boat as us also know what an appropriate alternative is too?

I figured that would naturally occur once there was a distro packaging it in this way, when I update the installation instructions 😁

@str4d rage-encryption has been accepted into openSUSE:Factory (what will be tumbleweed in a matter of days), and so I think this can be closed as "resolved" and the readme updated :)
Thanks again for your awesome work and for being so helpful! I'll try to help when I can in the future.


[mailio] Update Port mailio to 0.23.

[X] Changes comply with the maintainer guide
[X] SHA512s are updated for each updated download
[X] The "supports" clause reflects platforms that may be fixed by this new version
[ ] Any fixed CI baseline entries are removed from that file.
[X] Any patches that are no longer applied are deleted from the port's directory.
[ ] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[X] Only one version is added to each modified port's versions file.

Any help what kind of regression tests are broken?

Note: I will be converting your PR to draft status. When you respond, please revert to "ready for review". That way, I can be aware that you've responded since you can't modify the tags.

@karastojko, This is ci test error log, please take a look:
warning: DLLs should not be present in a static build, but the following DLLs were found:

    D:\packages\mailio_x64-windows-static\debug\bin\mailio.dll
    D:\packages\mailio_x64-windows-static\bin\mailio.dll

warning: There should be no bin\ directory in a static build, but D:\packages\mailio_x64-windows-static\bin is present.
warning: There should be no debug\bin\ directory in a static build, but D:\packages\mailio_x64-windows-static\debug\bin is present.
warning: If the creation of bin\ and/or debug\bin\ cannot be disabled, use this in the portfile to remove them
    if(VCPKG_LIBRARY_LINKAGE STREQUAL "static")
        file(REMOVE_RECURSE "${CURRENT_PACKAGES_DIR}/bin" "${CURRENT_PACKAGES_DIR}/debug/bin")
    endif()

error: Found 2 post-build check problem(s). To submit these ports to curated catalogs, please first correct the portfile: C:\a\1\s\ports\mailio\portfile.cmake

@karastojko, This is ci test error log, please take a look:
warning: DLLs should not be present in a static build, but the following DLLs were found:

    D:\packages\mailio_x64-windows-static\debug\bin\mailio.dll
    D:\packages\mailio_x64-windows-static\bin\mailio.dll

warning: There should be no bin\ directory in a static build, but D:\packages\mailio_x64-windows-static\bin is present.
warning: There should be no debug\bin\ directory in a static build, but D:\packages\mailio_x64-windows-static\debug\bin is present.
warning: If the creation of bin\ and/or debug\bin\ cannot be disabled, use this in the portfile to remove them
    if(VCPKG_LIBRARY_LINKAGE STREQUAL "static")
        file(REMOVE_RECURSE "${CURRENT_PACKAGES_DIR}/bin" "${CURRENT_PACKAGES_DIR}/debug/bin")
    endif()

error: Found 2 post-build check problem(s). To submit these ports to curated catalogs, please first correct the portfile: C:\a\1\s\ports\mailio\portfile.cmake

portfile.cmake now deletes the bin directory when statically building (suggested by the error log message). Is this problem now fixed?

@karastojko, please see the ci errors.
##[error]versions/m-/mailio.json(2,): error : while parsing versions for mailio from version/m-/mailio.json
0.23.0 is declared with c952f4b6ad01512faf2b8450546f19fa65fb29a0, but the local port has a different SHA a30a2352b8ec4783dc673cd3df74db04b450ec9c.

Pinging @karastojko for response. Is work still being done for this PR?

Does it still fail? I see all checks have passes.

Duplicate of https://github.com/microsoft/vcpkg/pull/34917.