adding support for ignoring credentials in URL

Related to https://github.com/jech/polipo/issues/75
This "fix" isn't ideal in that it just ignores the credentials instead of doing something useful with them, e.g., when you curl with credentials in the url, curl adds them as a base64 encoded string to an Authorization: Basic header automatically.

Which RFC is this described in?

RFC3986 describes a "userinfo" subcomponent of the authority component. It also explains that the password portion of it is deprecated and should be ignored. It also explains instances where the username piece of the userinfo subcomponent could be used for "semantic attacks," but doesn't explicitly deprecate the use of the username piece. However, I would argue that it's both implied and a good idea to ignore both.
cf. https://tools.ietf.org/html/rfc3986#section-3.2.1, https://tools.ietf.org/html/rfc3986#appendix-A, https://tools.ietf.org/html/rfc3986#section-7.5, and https://tools.ietf.org/html/rfc3986#section-7.6

Shouldn't we be sending the user info to the server somewhere?

I think so, and the server should be allowed to handle it however it would like. I tried to address that with https://github.com/riptano/polipo/commit/37a9fef1623d8c0d3762475bb66f5cdff051bde6, so that x isn't reset to the position after the '@' char. Instead, parseUrl leaves x pointing to the start of the "authority" component (so-called by RFC-3986). E.g.:
http://user:pass@example.com:8080/foo?bar#baz
       ^ x points here

That's what I meant by "passthrough userinfo subcomponent."

@jech what do you want to do with this?

I'm still waiting for an explanation why this is useful, and why it is the business of the proxy to do that.

@jech all the information you need has been presented to you in my comments above, the pull request, in the RFCs referenced above, and in this ticket: https://github.com/jech/polipo/issues/75. If you don't agree that you should support all conforming URIs, that's not something I care to argue with you. We (DataStax) had a desire for polipo to support all types of conforming URIs, but because polipo is incomplete, rather than contort our systems around polipo's shortcomings, we chose to use a different proxy that does support the complete URI spec as per the RFC instead.


Add additional examples

Summary
Adding additional examples that may be helpful, still a WIP.

Added

examples/voice_commands.rb

Changed
Deprecated
Removed
Fixed

@swarley Looks like the specs are failing due to libsodium being missing?

Working on cleaning up my own code before repurposing them as examples. Probably will be a bit.


ES6 Style Guide Discussion

Last week I listened to episode 39 of Adventures in Angular, which was a great discussion around ES6 language features and the tooling to support it.
I've seen some posts on the web about using Angular 1.x in conjunction with ES6, but it's pretty sparse.  I'm hoping to strike up a conversation about how we can take all the great ideas in this style guide and apply them in the context of ES6.  If possible maybe an ES6 branch of this style guide could be created to help facilitate the discussion with input from the community.
After spending the week in ES6 and angular 1.x, one the most obvious pattern changes is through the use of ES6 modules.  I really like how angular modules can be isolated to just an angular module definition file and everything else (controllers, services, directives, etc...) can be plain old JS and imported in using the ES6 module loader.
// app.module.js
import AppCtrl from './app.controller';
import './survey/survey.module';
import './core/core.module';
import './services/services.module';
import 'ui-router';
import 'angular-material';

angular
  .module('app', ['app.core', 'app.services', 'app.survey'])
  .controller('AppCtrl', AppCtrl)
  .config(function() {

  });

/// survey.module.js
'use strict';

import SurveyCtrl from './survey.controller';
import MultiChoiceCtrl from './multi-choice/multi-choice.controller';
import MultiSelectCtrl from './multi-select/multi-select.controller';
import StaggeredMultiSelectCtrl from './staggered-multi-select/staggered-multi-select.controller';

angular
  .module('app.survey', [])
  .controller('SurveyCtrl', SurveyCtrl)
  .controller('MultiChoiceCtrl', MultiChoiceCtrl)
  .controller('MultiSelectCtrl', MultiSelectCtrl)
  .controller('StaggeredMultiSelectCtrl', StaggeredMultiSelectCtrl)
;

I'd be interested to hear thoughts on this approach.  In Angular 1.x we still have to inform the Angular module system about controllers, services, etc.  With this approach I like that it delegates the wiring up of Angular assets only in the module definition files.  I think this could also lend itself well to migrating to Angular 2.  Since angular.module will be going away it might be prudent to reduce the amount of angular.module references throughout the code base.

ES6 is already panning out to be fantastic, can't wait!
The scheme you've drawn up has one feature that really bugs me, and that is if I want to add a controller to the survey module I would have to create a file for it with the implementation and then "map it" in another file. With the current style we don't have to as the controller and the association to the module exist in the same file.

@jimlei Thanks for taking a look.
It's absolutely true that with this pattern you would need to map controllers, services, etc. back to a an Angular module file.  The thought process was to reduce the footprint of angular.module references in ES6 projects, and to the extent possible keep only what needs to be tied to angular.module in isolated files.  That way we can keep everything else agnostic of Angular.

We have been playing around with ES6 at my workplace.  I found the usage of imports to really get in the way as stated by @philmerrell .
That said, the use of let/const, and even classes (when used for defining data objects used in directive), are useful.
Not sure about fat arrows yet.  I like the problems that fat arrows fix, but not sure when we will need it.

I've gone both ways with this where the module file imports all the things it needs and registers them, as @philmerrell showed. Then the other way of having each file use the module registration, like what I do in ng 1.x/es5. Both work but I feel the former is cleaner for my tastes so far ... but I reserve the right to flip flop :)
I'm tinkering with some ways to write ES6 and TypeScript and use modules more wisely. If I ever get time I will post them and we can discuss more.

I see you registered all of the angular components in one file, by importing them. Another approach is to let each file register itself. I think either way works, but interesting to see both are easy in ES6

I've been using ES6 with Angular for about three months and its been a mixed bag. The overall gains from switching to ES6 were great.
However, I ran into some issues with using native classes as controllers and found the duplication of module behavior frustrating. I've written off ES6 until Angular 2, mostly due to how much Angular already provides to solve the problems ES6 tackles.

@johpapa I'd be very interested to see what patterns you come up with using ES6 or TypeScript in addition to your tooling and task automation workflow.
I tend to agree with @alexlrobertson.  After some evaluation, I don't think there's a distinct advantage to using ES6 with Angular 1.x. other than it possibly being a step to migrate from 1.x to 2. I'm excited by the new language features ES6 provides (and tooling support via TypeScript), but it seems like there is still some maturing that needs to take place.  That being said, I can't wait to use it, and I'm using it in all of my personal projects.
Maybe this is getting off topic, but after the dust settles I'll be interested to see where people land with regard to package management and task automation.  I have been really digging JSPM for its one line install jspm install angular and one line require import angular.  That is a really nice way to work. It seems like there is a lot of overlap between what jspm can do and what you can do with the combination of npm/bower/grunt or gulp.  I'd jump at the opportunity to simplify this process and use one tool instead of many if it can provide the same workflow with regard to transpiling, packaging for production, and running unit tests.

Glad to see this discussion happening here as right now, using ES6 and angular.module conventions feel a bit at odds. Let's say I have a module, app.widgets and I want to register all my widget-y directives on this module. Using ES6, you might be inclined to do something like this:
// app.module.js
import angular from 'angular';
import myWidget from './components/myWidget';

export default angular.module('app.widgets', [
  myWidget.name
]);

and:
// myWidget.directive.js
import app from '../app.module';

// app will be undefined, referenced before export
app.directive('myWidget', /* ... */);

In the above example, the intention is to use angular.module to group related functionality, but as @philmerrell points out in his first post, there is no great way to do so without chaining .controller, .directive, etc.., declarations onto the original .module declaration and importing files containing only the business logic. I've seen some other clever solutions that involve exporting a function from ES6 modules to defer lookups to angular.module but that also feels pretty dirty.
Is this just something we deal with until 2.0?

@kenkouot - importing/exporting the module definitions is the direction I first went down when exploring, but as you say, it feels dirty and is a large deviation from the practices established in this style guide.  More than anything I felt like simplicity and readability suffered as a result.
An option that would get you out of chaining multiple controllers in the module definition file would be to try option 2 that @johnpapa mentioned above–use the angular module getter syntax in your controllers, directives, services etc...
// angular is defined globally, so no need to import it
angular
  .module('app.cart')
  .controller('CartCtrl', CartCtrl);

class CartCtrl {
  constructor(SomeService) {
    this.SomeService = SomeService;
    this.items = [];
  }

  getItems() {
    return this.SomeService.getItems(results => {
      this.items = results.data;
      return this.items;
    });
  }
}

export default CartCtrl

There are two disadvantages I see to this approach, but neither is a big deal.
First, I really like the idea of Controllers and Services just being plain old javascript with no references to angular.  It feels and looks very clean to me. You could also say that this approach makes the controller more reusable and could be used outside of angular, but that's not something I'm considering.  The biggest thing probably is that since the angular module system is going away in ng2 it seems more future ready.
Second, if you use the angular module getter syntax in a controller or service (like the above code demonstrates) you have to ensure that your app loads the module definition files first.  This is typically handled in a grunt/gulp task that loads scripts starting with *.module.js before other scripts in the index.html file.
When you wire up all of a module's assets in the angular module definition file, the order that the scripts are loaded doesn't matter.  Of course it may come at the cost of chaining many controllers, services, etc to one module definition.

After toying a bit with Angular 1.X and ES6, I've come to the conclusion that the Class syntax was too much of a hassle, so I kept the good ol' function.
On the other hand, using import was a really great way to simplify the build process, and added the nice side-effect of forcing myself to break up my app into modules, so i'd avoid writing massive import blocks.
in the end, my most bloated one was looking like this :
import angular from 'angular';
import directive from './directive.js';
import webcamService from './webcamService.js';
import socketService from './socketService.js';
import templateCompositionService from './templateCompositionService.js';

export default angular.module('booth', [])
.directive('booth', directive)
.service('webcamService', webcamService)
.service('socketService', socketService)
.service('templateCompositionService', templateCompositionService);

Of course arrow functions, let/const, and so on are easy to use and don't have any real drawback that I could see.

I've been on a client project for about 2 months where we introduced jspm, es6 and a component approach to writing an angular app.  I'm also in the middle of rewriting a pet project app using this paradigm. I really dig the es6 syntactic sugar I get with writing classes with getters and setters when writing services as it makes client usage a lot easier.   I agree with what some said above about having to map angular elements (controllers, directives, etc.) to a module via a index/module file, but I personally like the fact that I can write plain javascript code for testing purposes and not have to have my unit tests depend on angular or know about angular (unless you are using an angular dep in your code...which can get complicated).
Furthermore, I think that its good to get in this mindset given whats to come in future frameworks.  It's early but the approach of importing dependencies and exporting app elements will be a staple in Angular 2 and Aurelia.
Regardless of where you register your angular entities, I think we can all agree though that module loading is the way to go. Whether you use webpack, browserify or are brave enough to tackle JSPM, having your code accessed via a module system is far superior to worrying about handling loading scripts in a certain order or even adding them to your index page via a build task.

Glad to have found this conversation; I am building a large typescript angular 1.x app with es6 modules and have been thinking about their relationship to angular modules. My thoughts:
The co-existence of two module systems is redundant and confusing, this everyone agrees on. It is not by design and the long term solution is well known - the angular module system will be retired in favor of es6 modules. However, if you are writing angular 1.x with es6 modules today, you are forced to live with both. What's the most sensible strategy?
As much as possible, I want to forget that two module systems live in my app and just work with one. The obvious choice is to pick future proof es6 modules and attempt to drop the angular module system. The only reason I can't drop it entirely is that it holds a couple of essential apis - service() and directive() mainly - for registering angular entities. I also need one module for bootstrapping. Therefore, I must register at least one angular module - my app module. After this, there is no advantage to registering additional angular modules. The rest of my code is modularized and dependencies encoded directly via es6 imports and exports. Creating a parallel track of angular modules introduces no benefit and means I have to maintain a superfluous dependency tree in my code and head. If anyone can think of a reason to use multiple angular modules in an app using es6 modules, please correct me.
Any time I need to register a service or directive, I register it on that sole angular app module. In addition, when I register a service/directive, I do so in the file defining the service or directive. That is to say, I choose option 2 wrt how @johnpapa categorized the options above. Why?  You essentially force your entire app to load up front, like the old days. (This applies even if you choose to define multiple angular modules. You force the entire module to load even if all you needed was one directive.)
Now, I understand this point might be moot right now as we are still webpacking and systemjsbuilding or whatever to produce one file. But the other way just feels architecturally wrong to me. It is your service that depends on the service() api in order to become an angular service. From an es6 modules point of view reversing that dependency makes no sense. It only makes sense if you insist on structuring your app using angular modules, but once you decide to leave them behind, the es6 app becomes much cleaner, more flexible and easier to reason about.
The cost is that you get a proliferation of the module api across your service and directory files which is a disadvantage as @philmerrell originally pointed out. But it is a much smaller cost than losing the potential for lazy loading and having to think in terms of angular modules, IMO. The affected files end up with one line at the bottom of them like module.service('myService', MyService) which could be easily removed if the time ever came.
A couple more stray observations:

When using this technique, your app module definition file should be very small. It should just declare itself and the other 3rd party modules it depends on such as ui-router, translate or whatever. Everything else is loaded (and registered with angular if necessary) on demand by the module loader.
Your app is truly modular as the dependencies are declared at the most granular level - in each file rather than in obsolete angular module files.
It is the controller's responsibility to import any directives its template uses. This feels a little strange at first, but I think it's actually pretty close to how directive dependencies are explicitly declared in metadata in angular 2 components.
When importing a directive there is no need to import anything by name, you just need a "bare import" as angular is resolving the names for you.
Again, with services you can just use a "bare import" as the handle to the service is controlled via angular's DI system.
If you are using angular router or ui-router, there is no need to register your controllers with angular at all. Just import the controller class/function directly into the router configuration code.

Disclaimer: the above is a mixture of things I have done and things I intend to do. Would love help in discovering issues with the above pattern.

@vigie interesting approach regarding "bare imports" and having controllers be in charge of what directives they utilize.

I've been following this discussion and working on converting an Angular 1.x app in es5 to Angular 1.x in es2015 with JSPM/SystemJS.
I followed this and Todd's style guide pretty closely when I began building the app and they have served me very well. But now I'm running into situations and questions that they do not answer.
One specific question I have is how should the angular global object be handled. I want to avoid global objects as much as possible.
With es2015 modules I am declaring an import statement at the top of my module file
/// module.js ///
import angular from 'angular'; // This is defined by jspm map in config.js

import commonServiceModule from 'app:commonService'; // These are defined in jspm config.js maps
import itemServiceModule from 'app:itemService';

import noteManagerService from './noteManager/service'; // These are relative path imports
import noteWizardService from './noteWizard/service';

let moduleName = 's1.note.service';

let noteServiceModule = angular.module(moduleName, [

    commonServiceModule.name,
    itemServiceModule.name])

    .service(noteManagerService.name, noteManagerService.service)
    .service(noteWizardService.name, noteWizardService.service);

export default noteServiceModule;

And my service class definition looks like this
/// noteManager/noteManagerService.js ///
import angular from 'angular'; // Should I use this import syntax?

class CampaignManagerService {
    /* @ngInject */
    constructor($q, angular, NoteModel, itemManager) { // or should I use this dependency injection?
        this.note1 = new NoteModel("A Note");
        this.note2 = angular.copy(this.note1);
    }
}

But within a controller or service class definition I sometimes use angular.copy or angular.isDefined and was wondering if it would be better to try and inject the global angular object as a parameter of the class constructor or use the import angular from 'angular'; syntax above.
I haven't ever seen anyone inject the angular object into a function via angular's dependency injection and I'm not sure this is even possible.

I'm curious what people's thoughts on the following style I've been using off-and-on recently.
Specifically, I'm putting the controllerAs controller name into a  `const, so I can reference it using templated strings in my templates, watch expressions, etc...
(function() {
    'use strict';

    angular
        .module('dkProject.projectEditor')
        .directive('myDirective', myDirective);

    const controllerName = 'ctrlName';

    const template = `

${controllerName} Template

{{${controllerName}.myProperty}}

    `;

    /* @ngInject */
    function myDirective() {
        const directive = {
            bindToController: true,
            controller: MyDirectiveController,
            controllerAs: controllerName,
            scope: {
                myProperty: '='
            },
            template: template
        };
        return directive;
    }

    /* @ngInject */
    function MyDirectiveController($scope) {
        $scope.$watch(`${controllerName}.myProperty`, someFunc);
    }
})();

What are your thoughts on dependency injection in ES6 class constructors?
Here's what I've seen in most examples around the web:
export class MyController {
  constructor ($log, $timeout, MyService) {
    // Make injected dependencies available to class methods
    // Prefix with underscore to designate them as "private"
    this._$log = $log;
    this._$timeout = $timeout;
    this._MyService = MyService;

    // Scope properties
    this.hasSomething = true;
    this.someString = 'Foo';
  }

  // Scope method
  myMethod() {
    this._MyService.doSomething();
    this._$log.debug('Must use injected deps as pseudo-private methods of the class');
  }
}

MyController.$inject = ['$log', '$timeout', 'MyService'];

I don't know if it's that I'm used to the simple way in which passing parameters to regular constructor functions practically gives you private members to the rest of the class, but it just feels too redundant and yet another place to manually define injected dependencies. Not to mention the fact that they're not really private, though that doesn't bother me too much.
There's another approach involving WeakMaps to solve the privacy problem, but it requires even more boilerplate. But as I already mentioned, I don't mind the pseudo-privacy that much.
I would like to hear your thoughts on this. Am I alone in feeling that it's too much boilerplate, or am I just too enamored with the elegant syntax used in this styleguide for es5?
Of course, if somebody has come up with other approaches please share as well.

For my money, I haven't seen an example yet of DI with the class syntax that I like. Too much boilerplate and public privates seem to be a common theme. I can deal with the latter more than the former, but I still prefer the ES5 syntax put forward in this guide.

I tried the Class syntax with angular 1.4, but the public-private properties were too much to work with. The function syntax is so much more natural. I'm not against using classes, but until we can get easier global access to DI'd components within a class, without having them accessible via the class's public API, I'm going to avoid it.
That said, the module definition approach I outlined a couple posts above has worked very well for me with the lovely benefit of keeping my Controller/Service/Model classes very clean, no angular boilerplate, no globals, only DI'd values in the function.

I agree with @mcMickJuice that the component structure for NG6-starter is great, but the only difference I have adopted is that modules are called using the same angular setter/getter variable and it doesn't have to be thrown around all throughout your app. By simply passing it through your exports us can use it to assign directives/controllers/etc.
// index.js (Entry File)

import angular from 'angular';
import appModules from './modules';
import routerConfiguration from './app.config';

const myApp = angular.module('myApp', ['ui.router']);

// Modules Entrypoint
// Angular Module is passed down through each
// module eliminating need for angular setter/getter
appModules(myApp);

// Router Configuration
routerConfiguration(myApp);

// modules/index.js

import testModule from './test.component';
import headerModule from './header.component';

export default myApp => {
  testModule(myApp);
  headerModule(myApp);
}

// test/test.component.js

import TestDirective from './test.directive.js'
// instead of new angular getter/setter the same app instance is passed down.
// import angular from 'angular';
// angular.module('myApp').directive()

export default myApp => {
  myApp.directive('directive', TestDirective);
}

This makes your components more modular as there isn't an explicit module being set, instead passing the module you want to 'set' them to.
I have a very rough example of a starter es6+angular+webpack repo that shows this type of module instantiation.  (PS. Still a work in progress cleaning out old code from it but its a working loadable repo).

@johnpapa some update about johnpapa es6 style guide? haha

I'm late to this discussion, but I converted the style guide to ES6, specifically with regards to generator-gulp-angular and using ESLint. Please feel free to contribute! https://github.com/rwwagner90/angular-styleguide-es6

@rwwagner90 I took a brief look, and I see quite a few problems and things that would warrant additional discussion. But you don't have issues enabled so I cannot easily comment on them

@zachlysobey sorry about that. I didn't mean to have issues disabled. I guess it's the default if you fork something. I have enabled them. Please feel free to start up some discussions!

@johnpapa wondering if there is a "right way" now?  We are currently grappling with this very question.

@ehartford I would recommend discussing the right way and helping build standards for ES6 over at my fork. https://github.com/rwwagner90/angular-styleguide-es6

@rwwagner90 maybe:
/* recommended */

// app.module.js
import { someService } from './some.service';

angular
    .module('app', ['ngRoute'])
    // .controller... should not be recommended
    .service('someService', someService); // since this is service, not factory

And not to use stand-alone controllers. But this is my five cents...

@fesor I am happy to discuss any suggestions you may have over on the ES6 fork. Please create issues or PRs there.

Is this code fine?
/* @ngInject */
function /* public */ PublicClass($log) {

  class /* private */ _PrivateClass {
    constructor() {
      $log.info('Hello world! Please set a Name!')
      this.name = ''
    }
    setName(name){
      this.name = name
      $log.info('Yo got name! '+name)
    }
  }

  return new _PrivateClass()
}

export default PublicClass

You can access on all dependency injection as normal and you can benefit the es6 class as normal as well, but I'm not sure if it is acceptable and a good practice

@ipiz That seems fine:
Maybe an other solution is to use destructuring?
`let $dep1, $dep2
class Controller {
constructor($dep1, $dep2) {
[$dep1, $dep2] = [$dep1, $dep2];
}
someFunction() {
$dep2.doSomething()
}
}
export {ZoekController}
`

Or maybe just do this...
function Controller($dep1, $dep2) {
  return class {
    constructor() {

    }
    someFunction() {
      $dep2.doSomething()
    }
  }
}
export default Controller

I like @ipiz 's code the best imho.
It could be very concise and clean like
export default ($log) =>
  new class PrivateClass {
    constructor() {
      $log.info('Hello world! Please set a Name!')
      this.name = ''
    }
    setName(name){
      this.name = name
      $log.info('Yo got name! '+name)
    }
  }


Implement Data Analysis Questions Logic

Implement the game logic for data analysis questions. This includes generating the questions, checking the user's answer, and providing feedback.
Acceptance Criteria:

Questions should be generated based on the code snippets.
The user's answer should be checked against the correct answer.
Feedback should be provided to the user based on their answer.

Files to be used/created:

backend/firebase_functions/game_logic.js
frontend/game_mode_selection_ui.js

switched this to daily challenge


Can I get the joint torque of the robot？

Can I get the joint torque of the robot？
I found that effort is always zero in joint publish. Can we get the joint torque information?

Hi @lichenchen1205
Can you tell me the exact topic you were checking. Did you check ROS or ignition?

Hi @Samu24
I have checked the rostopic named "/anymal_c/joint_state" and the value of effort was always zero, can you tell me how to get the effort of the joint?
Thanks

Hi @lichenchen1205
Sorry for the late reply. I checked the controller and the publishing of the torque should actually be there. However, this is done in the ignition gazebo plugin and is forwarded to ROS via a bridge node that is part of the ignition simulation stack. I suspect that it is not forwarded to ROS in the bridge node. Maybe you can check with the maintainer of the ignition simulation stack about this issue.


--network=host should assume host's hostname

when running a container with --network=host, the container should assume
the host's hostname unless otherwise specified with --hostname.
Signed-off-by: baude<EMAIL_ADDRESS>

Merged #1274 instead.


Add 'not maintained' notice

For now, what do you think?
Any continuation of this will / should require a comprehensive overhaul which I don't have the time to do 😔

yea I agree


Decouple LSTM input and recurrent parts

The RNN layers include a matrix multiplication of their input. However when the input is a trainable embedding, this linear transformation is redundant in terms of both parameters and computation, and actually creates an ill-defined optimization problem.
I suggest trimming down the RNN implementations to the recurrent part, and reusing the Dense layer for the input transformation.
Example current stack:

Input: N-vector
LSTM input part: 4 gates at NxN
LSTM recurrent part: NxN

The decoupling would allow the following use-case:

Trainable Embedding: 4N-vector
LSTM recurrent part: 4 gates at NxN

The existing full LSTM would be re-implemented as:

Input: M-vector
TimeDistributed(Dense()): 4NxM
LSTM recurrent part: NxN

This removes all redundant code involving inputs (weights, bias, regularizations, …) out of each RNN implementation, reusing the code of the Dense layer. It also allows experimenting with any other combination of layers.
I implemented it for myself, and I heard others had the same need, so I can contribute it if you are interested in this change.

so, the rnn is h = activation(K.dot(K.dot(x,W), U)).  You're suggesting replacing the K.dot(x,W) and just have a recurrent connection?
How would that work with LSTMs/GRUs which use the input to calculate the various gates?
aka, in the LSTM, x is used as
                x_i = K.dot(x * B_W[0], self.W_i) + self.b_i
                x_f = K.dot(x * B_W[1], self.W_f) + self.b_f
                x_c = K.dot(x * B_W[2], self.W_c) + self.b_c
                x_o = K.dot(x * B_W[3], self.W_o) + self.b_o

The input is split in 4 for LSTM and 3 for GRU:
            x_i = x[:, :self.output_dim]
            x_f = x[:, self.output_dim: 2 * self.output_dim]
            x_c = x[:, 2 * self.output_dim: 3 * self.output_dim]
            x_o = x[:, 3 * self.output_dim:]

Corrected the post above.

@naure, I think this is a cool suggestion, but I don't see how this could be implemented. How would the LSTM without Dense() work then? Could you provide some illustrations? As usual, I'm a bit confused: https://github.com/fchollet/keras/issues/2673
By the way, is it really a linear transformation? The LSTM activations default is a tanh. Do you mean that TimeDistributed(Dense()) should apply the tanh instead?

There are no activation on the input, so it is indeed equivalent to
TimeDistributed(Dense()). It is actually currently implemented with
time_distributed_dense().
In the architecture that I actually use, there is no input transformation,
all inputs are embeddings that are trained.
Le jeu. 12 mai 2016 à 18:24, Carl Thomé<EMAIL_ADDRESS>a écrit :

@naure https://github.com/naure, I think this is a cool suggestion, but
I don't see how this could be implemented. How would the LSTM without
Dense() work then? Could you provide some illustrations? As usual, I'm a
bit confused: #2673 https://github.com/fchollet/keras/issues/2673
By the way, is it really a linear transformation? The LSTM activations
default is a tanh. Do you mean that TimeDistributed(Dense()) should apply
the tanh instead?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/fchollet/keras/issues/2698#issuecomment-218810208

A couple more questions:

is there a computational vs representational trade off here? Aka, are you saving computation for a hit in representation?  Is there a negligible hit in either direction?
would it be safe to say that your of an embedding straight to the recurrence is akin to using a one-hot binary input to the RNN?

also: I don't really know if I'm for or against it.  I see no reason why it wouldn't work, but no reason why I'd personally use it.
You say

this linear transformation is redundant in terms of both parameters and computation, and actually creates an ill-defined optimization problem.

Is it really redundant?  Is it really ill-defined?
Under your suggestion, Embedding -> TimeDistributed(Dense) -> RNN is the same thing as Embedding -> RNN in the current implementation.   That doesn't seem redundant, but just an extra layer of dimension transformation.  So, the only reason I would see to use it is if I didn't want that middle layer, for some computational, methodological, or theoretical reason.


Move ARP handler into lookups service

Moves the ARP handler into the lookups services deprecating ARP poller in on-taskgraph.
Solves a couple known issues with existing ARP poller design:

Potential race condition when issuing a POST to /lookups on an IP change,  current ARP poller may see the ARP entry update and update the entry resulting in 500 response on the POST.
The existing poller runs as a job in on-taskgraph creating the prerequisite to run on-taskgraph on the same host that is taking the IP request from a client to ensure the hosts ARP table is current.

@RackHD/corecommitters @uppalk1 @zyoung51 @tannoa2 @keedya

test this please

*** BUILD #569 ***

@jlongever : so I would expect, with your code, every lookup CURD operation need to firstly analyze the current ARP data?

@yyscamper only on a LRU cache miss.

Unit-test failures for on-http requires https://github.com/RackHD/on-http/pull/300

Coverage increased (+0.2%) to 91.458% when pulling f95110484babeefae813579979fdcbfc02e14f2f on jlongever:feature/check_arp_cache_in_lookups into ff5cdb15c0b11910948d4561ff7f0150ae382d57 on RackHD:master.

@jlongever , thx. :+1:

*** BUILD #584 ***

test this please

👍

Why not check the cache for all conversion calls too (such as macAddressToNode, etc.)?

@benbp the LRU cache?  The original code never included it, maybe it was overlooked then?

test this please

*** BUILD #589 ***
Test Name: Encryption Instance Methods createHash should generate correct hash header
Error Details: expected '*0' to match /^\$1\$*/
Stack Trace: AssertionError: expected '*0' to match /^\$1\$*/
    at Context.<anonymous> (spec/lib/common/encryption-spec.js:83:78)

Test Name: Encryption Instance Methods createHash should generate correct hash data
Error Details: expected '*0' to equal '$1$WeJknBPk$t3LdooA1UatyI0C7pGX5F/'
Stack Trace: AssertionError: expected '*0' to equal '$1$WeJknBPk$t3LdooA1UatyI0C7pGX5F/'
    at Context.<anonymous> (spec/lib/common/encryption-spec.js:93:29)

*** BUILD #592 ***

@benbp are you OK with this being merged?

@jlongever I mean like there seems to be no reason to call validateArpCache when doing things like macAddressToNode, it's just unnecessary I/O right?

Sorry for the delay :)

@benbp updated.

*** BUILD #610 ***

test this please

👍


External theme file to control all the component's style.

Impact: major
Type: refactor
Issue
To change the style of a component, that component had to be extended and then replaced because the style for every component was inside that component.
This is a lot of effort for just changing the style of a single component.
Solution
This PR extracts the style of all the components to a single file that can be over-ridden by anyone who wants to change the theme of the app.
Breaking changes
None
Testing

Start the App, no styling should be broken.
Change some style in src/lib/theme/reactionTheme.js, the style change should be reflected in the UI.

To add to the above comment, we would need to add { name: "<some-name>" } to every component to make their styles more easily overridable.
We should make sure variables are used where needed and there are no extra, unused variables.
This is also something we should all agree on before any work is attempted, and clarify in documentation the preferred methods customization.

Created an issue for @mikemurray's comment here: https://github.com/reactioncommerce/reaction-next-starterkit/issues/279
Otherwise we will be solving this in other ways per my discussions with @zenweasel so I'm closing this PR.


Can't render the website after trying to to deploy it though netlify

Hi there, I’m a new user for the blogdown academic theme. Here is my repo: https://github.com/YuanEldaif/academic-kickstart
With instructions from (https://community.rstudio.com/t/posting-xaringan-presentation-on-blogdown/8212) to post Xaringan .rmd format slides by creating R/Build.R and put Xaringan .rmd slides in the Static folder, I was able to render my website on my local laptop. but When I deploy the netlify website, it failed to build the website.
Then I updated the Hugo version to 0.55.2 and the latest academic theme V4.5. and I couldn’t render the website on my local machine anymore. Here is the screen shot:

Could anyone kindly guide me through? Is it something wrong with my files or the theme needs to be updated with the Hugo version? Thank you in advance!

These issues are not for support. See https://github.com/gcushen/hugo-academic/blob/master/.github/support.md
The issue appears to be that you updated Academic without following all of the update instructions in the documentation - you may have updated Academic without upgrading your content/config to be compatible as per the documentation.

Thanks for your reply. I checked my content/config and it still shows "home", "section", "page" all failed.:( Is it because my hugo verson 0.58.2 is not compatible with the academic theme? Thanks for your time.


[Medals/Profiles] Long comments with no spaces break comment sections

On medals

On profiles

i thought i fixed this

mh, guess i didn't


Fix defaults to new name

Change the sed command to bring over the defaults from the new go-server.default.

Closing since we moved to https://github.com/gocd/docker-gocd-server and https://github.com/gocd/docker-gocd-agent


Jaro-Winkler Distance Algorithm Match Value Question

Firstly, a massive thank-you for putting this library together.  It's been really helpful implementing some text similarity behaviour in an application I'm currently writing.
Secondly, I just wanted to ask a question regarding the match value that is returned from the JaroWinklerDistance algorithm.  On reading the wikipedia article I definitely got the impression that a comparison between two strings that are exactly the same should return a result of 1.  I'm finding, however, that this isn't the case.
In the application I'm currently writing, I'm using the functionality to order place names in order of their match strength against an original request.  In the case of sydney, this works as expected:
> natural.JaroWinklerDistance('sydney', 'sydney');
1

However, when I did a comparison for seddon against seddon, it returns less than 1:
> natural.JaroWinklerDistance('seddon', 'seddon');
0.8933333333333334

I went on to do some other smaller tests in the node console to see if I could have the function produce a higher score for two different strings than two that were exactly the same, as realistically, this is the case that I'm worried might occur.  After a little bit of playing around I found that I could:
> natural.JaroWinklerDistance('abc', 'abc');
0.8666666666666666
> natural.JaroWinklerDistance('abcd', 'abcd');
1
> natural.JaroWinklerDistance('abcd', 'abc');
0.9416666666666667

Once I grok the algorithm, I'll have a look at forking the code and seeing if I can work out where this is happening, but I thought I'd raise an issue first to see if it was something that someone else knew how to fix quickly and simply.
Thanks again for your efforts on the library.
Cheers,
Damon.

Hi,
I would like to ask about JaroWinklerDistance algorithm.
My team made a comparison between 'jezze' and '09270000000' and it returned 0.411111111111111 value (we are expecting 0).
To be honest I am not familiar with Jaro-Winkler and it's algorithm, but upon researching about it I found out that Jaro-Winkler is really useful. My question is, maybe the implementation of the algorithm is incorrect?
Hoping for your feedback.
Thank you!

You are correct, this should be 0.

I tested this, and works like expected. See #491 for the same issue and my answer.

👍. Thanks
That was my next step, but haven't pulled this repo on years.
On Sun, May 5, 2019, 10:27 AM Hugo ter Doest<EMAIL_ADDRESS>wrote:

I tested this, and works like expected. See #491
https://github.com/NaturalNode/natural/issues/491 for the same issue
and my answer.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NaturalNode/natural/issues/44#issuecomment-489446283,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAC24C664JBX74R2P555HR3PT4KIVANCNFSM4AAJ246Q
.


Create user db

Need to create user db table to store user session information.
Basic Structure:

userID
username
query
timestamp

Corrected :
userID
emailAddress
query
timestamp


Add a MessageClipped option to change clipped message. Closes #1359

I think this one still needs to be added to the wiki, @42wim?

@xnaas yes feel free to add it please :-)
How it works is you just set the text it should display instead of the default one.
MessageClipped="<toolong>"


BUG: Home and Kitchen Page Not Found 404 Error

Related Issue
Fixes #1420 issue
Description
I added Home and Kitchen page
It does not give 404 error now
Bug is fixed
Type of PR

[x] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
[Attach any relevant screenshots or videos demonstrating the changes]
Checklist:

[x] I have performed a self-review of my code
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

Additional context:
[Include any additional information or context that might be helpful for reviewers.]

@arghadipmanna101, kindly view this PR


Running from a different working directory

Describe the bug
Not sure if this is actually an issue or something undocumented or even if there is anything wrong with this plugin or other parts of the solution. Would appreciate some pointers on what to look at/what to configure.
The problem is, when running the eslint script, from a directory different than the root of the linted project, the plugin will not give the correct output. The same configuration/rules will report errors when run in the root of the project, and will not report anything when run outside of the project.
To Reproduce
Run the lint command from parent/child directory (different working directory than the root of the linted project)
npm exec -- eslint epb-ts-example-main/

or
npm exec -- eslint ../

Expected behavior
The correct output is produced.
Logs
If applicable, add logs to help explain your problem.
** Operating system, Node.js an npm versions, and eslint version (please complete the following information):**

OS: Windows 10
Node.js: v16.13.2
npm: 9.7.1
ESLint: 7.32.0

Additional context
While at first I thought this was an issue with our monorepo configuration, I seem to have the exact same problem with the example repository: https://github.com/javierbrea/epb-ts-example
If I for example, go into the src/ directory, and run the npm exec -- eslint ../ command from there, the output is no longer correct and the error is not reported.

Hi @wadamek65 , first of all, thanks for reporting the problem 😃 .
This happens because the plugin needs to know from where to resolve paths in order to make them match with the path matchers in the element-types setting. So, it assumes that the root of the project is the process.cwd() and it removes it from the file path and import paths before executing the match patterns. It is true that it may be a wrong assumption if you execute the linter from another path, as you have explained 😞 . But, after some research, I have not found a way to determine the path to be considered the "project root". Eslint does not provide to the plugins more info at this respect than the process.cwd itself, and it may have sense, because, which other information could we use to determine the "project root"? I have thought about:

The eslint config file path - We have no information about the path of the config file being applied, and, if we had it, we couldn't use it neither, because eslint config files can be also nested, so, which one should be considered the valid one?

So, the only solution I can think of is to add a setting to the plugin in order to allow to define the root path from where micromatch patterns must be resolved. This may solve the problem, but it wouldn't be compatible with defining configuration using .json format, for example, because the root path should have to be provided programmatically in most cases (by using __dirname, for example). As an alternative for this case, maybe we should also allow to define the root path by using an environment variable (this is not the ideal scenario, because I don't like too much to use configuration methods out of the eslint configuration mechanisms, but maybe we'll have to make an exception in this case).
In short, to solve it we could add a boundaries/root-path setting that could be used like:
// Note: .eslintrc.js file in the root path of the project
{
  settings: {
    "boundaries/root-path": __dirname,
  }
}

And, in case the configuration is defined using JSON, it could be defined also by using an environment variable. In case the provided value is a relative path, it would be resolved from the current process.cwd():
ESLINT_PLUGIN_BOUNDARIES_ROOT_PATH=../ npm exec -- eslint ../

Please let me know what do you think about this proposal.

Hey @javierbrea , thanks a lot for responding and looking into it!
Since this seems like a rather niche use case, I too believe the best approach would be to keep things fully configurable via a custom rule, just in case there are more nasty edge cases where some kind of smarter file path deduction would fail.
As for your concerns regarding the JSON/JS configs, I'm not sure if there is a need to add special handling with an env variable.  Since ESLint is most of the time run under preset conditions, the users should be able to provide string paths to whatever directory they want to run from. You wouldn't be able to pass a __dirname to an environment variable unless you are willing to inline a script in the command itself to resolve the path to a static string before the runtime. So, in the end, it seems like it will be exactly the same as just specifying a static string in the JSON config. On the other hand, it may be convenient for others to configure it like that, but it could possibly add feature bloat to the plugin and one more thing for you to support and maintain.

Hi again @wadamek65 , sorry, but I don't understand how would be the plugin able to resolve the directory to work from by simply using a string containing a relative path, because If you change the working directory, then the absolute path would be calculated from there, and it may be wrong. As far as I can see, it would need an absolute path, so it could be executed from any working directory, as it would never use it to resolve anything. That's why I suggested to use "resolve" to provide the setting in a JavaScript file, to make it absolute always, so it is not affected by the working directory.
About the env variable, it's just a workaround to be able to provide another "working directory" to the plugin when you are not able to provide an absolute path. In this case, you'll be able to provide a relative path, that would be resolved with the current cwd. This way, it would be your responsibility to make the plugin point to the project root. For example, if you are running the command one level below the project root, you should provide "ESLINT_PLUGIN_BOUNDARIES_ROOT_PATH=../", if you are two paths below the project root, you should provide "../../", etc. Or you could even provide an absolute path, of course. So, there is no script implied, it is just a mechanism to allow the user to define the project root when they can't define an absolute path in the config.
I probably didn't explain it well in my previous comment, I hope now I have done it better. 😃

Ah, I see. Thanks for the explanation, I understand it now.
I assumed that the behavior that you described for the env variable would be the same for the new rule, but that's not the case. In our case, it would be enough to be able to reconfigure the path slightly, like with the env variable behavior you described. I think that most people want to run ESLint from the same directories always. It's just that in some cases, especially monorepos, it's wrong to assume it will be run from the same root directory as the source code.
Just to make it clear, I think what you are proposing sounds all good and would definitely solve our problem 👍  Just wanted to shine some light on our specific use case.

Thanks for notifying me about the problem 👍 . I didn't think in that use case, mainly because I use to use Nx as monorepo tool, and it always uses each project root as working directory when running a command on each project, no matter the repository path in which you are. But this is something to solve, because, as you said, it's wrong to assume that the lint command will be run from the same root directory always. So, I add it to the backlog and I hope to solve it soon  😃

@javierbrea Interesting, because we're also using nx and running the command nx run-many -t lint from the root of the repo and use the nx ESLint plugin within our packages, but we're not getting the correct output unless we explicitly go into package directory and run ESLint from there. Perhaps OS differences since the majority of us are working on Windows 🤔 Perhaps the configuration needs to exist in the root as well with all the paths accounted for separately for each package? 🤔
Regardless, this will definitely help us out, so thanks a lot!

@wadamek65 , mmm... I don't think it is related to the OS, because we use different OS in the team, and it works properly in all cases. We create a different "lint" command in the package.json file of each monorepo project, each one with its own eslint config (that may be reused by exporting it from another project). This way, the affected Nx command lints only affected projects. With this configuration, we have no problems, as Nx uses the project root to run the command. But anyway, there are multiple ways of doing  things, and the plugin should be able to work with any of them.


Update operatorsScore,supportedExprs for TruncDate, TruncTimestamp

This change updates operatorsScore.csv and supportedExprs.csv to include TruncDate and TruncTimestamp, for all shim versions.
This seems to have been left out of #11833.

Build

This seems to have been left out of https://github.com/NVIDIA/spark-rapids/pull/11833.

Then this needs an issue because it should not pass pre-merge this way

This seems to have been left out of #11833.

Then this needs an issue because it should not pass pre-merge this way

#11896 has been filed to address the larger problem.

Thank you for the review, @abellina, @gerashegalov.  I've merged this change.


Virus detection

I tried to download the latest Release, and even my browser refused the download.
VirusTotal answers why:
https://www.virustotal.com/gui/file/c40389ebe232674195ba0d61fcf0018e511d3ca63e5dbdca89cbfc2aaf4491e1
https://www.virustotal.com/gui/file/6ef9367ef41da14edd1be89f216e643300057c9bea69755c73dab71754ab9f3e (lpvpn.exe)

What is up with this?

To be completely honest - I don't know. The program requires administrator access and configures network interfaces, maybe that's considered high-risk for some anti-virus solutions.
The entire project is open-source including the build pipeline, so people can check that there's nothing nefarious going on here.


Adding G1ant language

I'm adding G1ant language support
Description

Checklist:

[] I am associating a language with a new file extension.

[ ] The new extension is used in hundreds of repositories on GitHub.com

Search results for each extension:

https://github.com/search?utf8=✓&type=Code&ref=searchresults&q=extension%3AFOOBAR+KEYWORDS+NOT+nothack

[X] I have included a real-world usage sample for all extensions added in this PR:

Sample source(s):

[URL to each sample source, if applicable]

Sample license(s):

[ ] I have included a change to the heuristics to distinguish my language from others using the same extension.

[X] I am adding a new language.

[X] The extension of the new language is used in hundreds of repositories on GitHub.com.

Search results for each extension:

https://github.com/search?utf8=✓&type=Code&ref=searchresults&q=extension%3Ag1ant+g1ant

[X] I have included a real-world usage sample for all extensions added in this PR:

Sample source(s):

https://github.com/DeeLucky/linguist/blob/master/samples/G1antLanguage/break.G1ANT
https://github.com/DeeLucky/linguist/blob/master/samples/G1antLanguage/continue.G1ANT
https://github.com/DeeLucky/linguist/blob/master/samples/G1antLanguage/notepad.G1ANT
https://github.com/DeeLucky/linguist/blob/master/samples/G1antLanguage/xlsxtry.G1ANT

Sample license(s):

[ ] I have included a syntax highlighting grammar: https://github-lightshow.herokuapp.com/
[ ] I have updated the heuristics to distinguish my language from others using the same extension.

[ ] I am fixing a misclassified language

[ ] I have included a new sample for the misclassified language:

Sample source(s):

[URL to each sample source, if applicable]

Sample license(s):

[ ] I have included a change to the heuristics to distinguish my language from others using the same extension.

[ ] I am changing the source of a syntax highlighting grammar

Old: https://github-lightshow.herokuapp.com/
New: https://github-lightshow.herokuapp.com/

[ ] I am updating a grammar submodule

[ ] I am adding new or changing current functionality

[ ] I have added or updated the tests for the new or changed functionality.

I'm gonna jump in here really early to potentially save you a lot of time and effort.
Your search string reveals not a single file on the whole of GitHub.com with the .g1ant extension. Even modifying it slight to https://github.com/search?q=extension%3Ag1ant+NOT+nothack&type=Code returns no results.
If this is accurate, and I don't doubt that it is, it means you are a very very very long way from meeting the very first requirement for adding a new language:

We try only to add languages once they have some usage on GitHub. In most cases we prefer that each new file extension be in use in hundreds of repositories before supporting them in Linguist.

0 == no usage 😄


Add incremental backups

What does this PR change? What problem does it solve?
This PR adds the possibility to make "incremental" backups. Basically specifying the list of files to backup (could be for example a diff files from the previous backup, created in any way), with the --merge, the new snapshot will be a merge of the parent snapshot and the new backuped files.
Example:
> exa -T dir
dir
└── other
   ├── other-file1
   └── other-file2

> export RESTIC_PASSWORD=password

> restic -r repo init
[...]

> restic -r repo backup dir/
repository 7d31e4a2 opened successfully, password is correct
created new cache in /home/gmgigi/.cache/restic
no parent snapshot found, will read all files

Files:           2 new,     0 changed,     0 unmodified
Dirs:            2 new,     0 changed,     0 unmodified
Added to the repo: 1.344 KiB

processed 2 files, 0 B in 0:00
snapshot 9adcd3fc saved

> (creating a new folder with some files inside)

> exa -T dir
dir
├── other
│  ├── other-file1
│  └── other-file2
└── subdir
   ├── bar
   └── foo

> cat list
dir/subdir/foo
dir/subdir/bar

[list contains only the new files, but can contains also deleted and updated files, see the unit tests for more examples]

> restic -r repo backup --files-from-verbatim list --parent 9adcd3fc --merge
repository 7d31e4a2 opened successfully, password is correct
using parent snapshot 9adcd3fc

Files:           2 new,     0 changed,     0 unmodified
Dirs:            1 new,     1 changed,     0 unmodified
Added to the repo: 1.690 KiB

processed 2 files, 0 B in 0:00
snapshot 950708ff saved

> restic -r repo  snapshots
repository 7d31e4a2 opened successfully, password is correct
ID        Time                 Host        Tags        Paths
--------------------------------------------------------------------------
9adcd3fc  2021-06-01 09:46:23  avatar                  /home/gmgigi/dir
950708ff  2021-06-01 09:48:34  avatar                  /home/gmgigi/dir
--------------------------------------------------------------------------
2 snapshots

[mount restic repo]

> exa -T mount/snapshots
mount/snapshots
├── 2021-06-01T09:46:23+02:00
│  └── dir
│     └── other
│        ├── other-file1
│        └── other-file2
├── 2021-06-01T09:48:34+02:00
│  └── dir
│     ├── other
│     │  ├── other-file1
│     │  └── other-file2
│     └── subdir
│        ├── bar
│        └── foo
└── latest -> 2021-06-01T09:48:34+02:00

Was the change discussed in an issue or in the forum before?
No
Closes #3118
Checklist

[x] I have read the Contribution Guidelines
[x] I have enabled maintainer edits for this PR
[x] I have added tests for all changes in this PR
[ ] I have added documentation for the changes (in the manual)
[x] There's a new file in changelog/unreleased/ that describes the changes for our users (template here)
[x] I have run gofmt on the code in all commits
[x] All commit messages are formatted in the same style as the other commits in the repo
[x] I'm done, this Pull Request is ready for review

Awesome work. For our use case, we can guess the files to backup before calling restic, and this feature will reduce drastically the time to backup ! Looking forward to see this merged!

Resolved the conflicts with the master.

Changed the library used in the tests for writing into files, in order to be compatible with previous go versions

@fd0 @MichaelEischer Any feedback for this? :)


Harvesting mushroom blocks with a BD gives the Old Mushroom block (CE 2.0.4)

Harvesting mushroom blocks with a BD gives the Old Mushroom block for all 3 mushroom block types (stem, brown and red cap)

It actually was returning the correct blocks, just the new blocks were still using the old names and did not have their own names. Fixed for next release (although I would like to do a more proper overhaul of mushroom cap blocks in the future to make them more usable as they are kinda janky right now)


add solc

Resolves #368.

https://github.com/neovim/nvim-lspconfig/pull/1623

In my opinion, the github release page mechanism is seriously flawed since it does not provide a history of changes.
I would recommend to use https://binaries.soliditylang.org instead, which is (mirrored from) a proper git repository and also allows you to get a list of releases. The structure of the repository is explained here: https://docs.soliditylang.org/en/v0.8.11/installing-solidity.html#static-binaries

Thanks for the input @chriseth! I took a quick look, shouldn't be any problems. I guess one drawback would be that installing older versions might be a bit cumbersome from an end user perspective, as you'd have to provide the full v0.3.6+commit.988fe5e5 component (:LspInstall solc@v0.3.6+commit.988fe5e5), whereas through GitHub releases the tag name alone would suffice.
Great documentation btw :+1:! If you don't mind some unsolicited feedback; one thing that wasn't immediately clear to me was how to access the files via https://binaries.soliditylang.org/ (the landing page links to the docs, which links to the landing page). Took me a minute or two to piece things together. I think hosting a file explorer (like https://c.quick-lint-js.com/) would help with self discovery!


Update survey link in the project templates for Blazor 0.9.0

Blazor 0.9.0 survey link: https://go.microsoft.com/fwlink/?linkid=2077509

@mkArtakMSFT Could you please assign so that we can get this in for the Blazor 0.9.0 release?


Dynamic locales loading

Is your feature request related to a problem?
The current approach rely on injecting namespaces, languages from getServerSideProps/getStaticProps. This has few drawbacks regarding page performance (html size, lighthouse). When using this for example

Example with getServerSideProps
import { serverSideTranslations } from 'next-i18next/serverSideTranslations';
import { useTranslation } from 'next-i18next';

export default function MyFeatureRoute(
  props: InferGetServerSidePropsType<typeof getServerSideProps>
) {
  const { t } = useTranslation();
  return <MyFeaturePage>{t('common:page.title')}</MyFeaturePage>;
}

export const getServerSideProps: GetServerSideProps<Props> = async (
  context
) => {
  return {
    props: {
      ...(await serverSideTranslations(context.locale, ['common', 'a-feature-specific-namespace'])),
    },
  };
};

The resulting html page will contain all 'common' and 'a-feature-specific-namespace' in the target language + the default language (so it can fallback). i.e:

Extract of props
<script id='__NEXT_DATA__' type='application/json'>{
  "props": {
    "pageProps": {
      "locale": "fr",
      "_nextI18Next": {
        "initialI18nStore": {
          "fr": {
            "common": {
              "general": {
                "save": "Enregistrer",
                "cancel": "Annuler"
              },

On bigger projects this can lead to a lot a waste...
Depending on features, we sometimes have > 100kb (unzipped) injected in the html.
Describe the solution you'd like
I'm wondering if we could improve that, by loading bundled namespaces part of the page loading...
i.e:
import Script from 'next/script'

export default function MyFeatureRoute({locale}) {

   // Something in the line of doing, either in app.js or per page

   <Script
      src="/mybundled-locales/?namespaces=common,a-feature-namespace/langs=en,fr"
      strategy="beforeInteractive"
    />

  return <MyFeaturePage>{t('common:page.title')}</MyFeaturePage>;
}

I'm wondering if you had some ideas about that ?
I partially see a road that I'd like to experiment

Inject some webpack config that would expose bundles locales per namespace (par of the nextjs build, nice so assets are hashed and can live on the edge / cdn).
Create a DynamicLoader (appWithDynamicTranslations for example), that would load the scripts.

@isaachinman Have you some things in mind about that problem ? And BTW thanks a lot for this package

This is already supported by i18next. Does that answer your question?

Mmm not totally, I'll need to test this out...
I know we can load locales dynamically with i18next. But It's not clear yet how to set it up with next-i18next in a getServerSideProps context. Keeping all the beautiful features of if it at the same time :smile:

But It's not clear yet how to set it up with next-i18next in a getServerSideProps context

Not sure what you mean. You simply use serverSideTranslations inside getServerSideProps.

You simply use serverSideTranslations inside getServerSideProps.

Yep I do and it's working great.
import { serverSideTranslations } from 'next-i18next/serverSideTranslations';
import { useTranslation } from 'next-i18next';

export default function MyFeatureRoute(
  props: InferGetServerSidePropsType<typeof getServerSideProps>
) {
  const { t } = useTranslation();
  return <MyFeaturePage>{t('common:page.title')}</MyFeaturePage>;
}

export const getServerSideProps: GetServerSideProps<Props> = async (
  context
) => {
  return {
    props: {
      ...(await serverSideTranslations(context.locale, ['common', 'a-feature-specific-namespace'])),
    },
  };
};

The side effect of this approach is the resulting html page size... Cause props will be inlined.

But It's not clear yet how to set it up with next-i18next in a getServerSideProps context

I see here is that weto no rely on injected props.
https://github.com/isaachinman/next-i18next/blob/93136a4f411e42059e660ec928408ca3b9619df0/src/appWithTranslation.tsx#L52
I'm wondering if an appWithDynamicallyLoadedTranslations would be an option.
In this scenario, locales (namespace / languages) would be built and present in the dist folder (.next/static/locales/ns1-NEXT_BUILD_HASH.fr.js) so we can load them up with https://www.i18next.com/how-to/add-or-load-translations#add-after-init
My question is more would it make sense in your experience ?

I don't understand what exactly you are suggesting. You already have access to addResourceBundle if you want to dynamically load a namespace on the client. Nothing needs to be "built" or "present in the dist folder" for you to use this functionality.
In general, adding translation data to page props is exactly how this package works, because that is how NextJs works. Our translation data is indeed a data dependency of the page, and is therefore handled as such.

In general, adding translation data to page props is exactly how this package works, because that is how NextJs works

I'm just suggesting something, I'm aware of the props. Just trying to figure out how to circumvent html size increase due locales inlining, in my context I have a deal with quite big locales...

You already have access to addResourceBundle if you want to dynamically load a namespace on the client.

I'll try this thanks. In this scenario we would remove "big" namespaces and load them dynamically with addResourceBundle..

Nothing needs to be "built" or "present in the dist folder" for you to use this functionality.

Maybe overseeing the thing :smile:

Just trying to figure out how to circumvent html size increase due locales inlining, in my context I have to deal with quite big locales

The current idea is to split your translations into different namespaces to address this issue. In the future, the hope is that static analysis of translation data will be possible.


chore: refresh PSS policies with latest changes

Signed-off-by: Pankaj Khushalani<EMAIL_ADDRESS>Referring to the changes made in PR#420 and PR#421 of kyverno/policies, the PSS policy pod-security/restricted/disallow-capabilities-strict/disallow-capabilities-strict.yaml required the following updates -

Sending drop[] and add[] policies to to_upper() to be case insensitive
Allowing policy to go in BACKGROUND mode if request.operation cannot be resolved

Need to walk this change back based on community updates.
https://github.com/kyverno/policies/pull/485/commits/b655dfb508edbc96c446f08cec87ec3cf0dff18f

@chipzoller
This change hasn't been merged yet.
From what I understand from https://github.com/kyverno/policies/commit/b655dfb508edbc96c446f08cec87ec3cf0dff18f, to_upper has to be removed from this patch, right?
And BACKGROUND change is still required, right?

Change is merged. Yes, just remove to_upper.


Remove youtube channel

Siraj raval's youtube channel must be removed.
He is a scammer and has looted several people.

Exactly


FEATURE: global setting for whitelisted IP

Add GlobalSetting.prometheus_trusted_ip_whitelist_regex to whitelist external IPs.
As discussed here
Err. I'll try to figure out how to squash all these commits.

overall this is fine minus a few minor corrections tests look good!

Oops. I can't tell if my latest commit will ping anyone or not, but I still need to put all of those rescues in a single block. I'll fix that shortly.

OK.
In my defense, the rescue nil I copied from the same code in is_private_ip?
I moved the multiple rescues to a single block.
It's passing tests on travis.
Thanks

We have sat on this for a bit too long ... I will merge and then do the minor bits of cleanup
Thanks @pfaffman !


 Should be read in conjunction with the matching innovation week PR: https://github.com/maxime-rainville/innovation-week/pull/2

Vanilla asset-adimn (Approach in this PR)

The routing decides which components get served ... rather than the Silverstripe PHP class
Your routes are defined in your JS and you need to hardcode the name of the PHP class somewhere to retrieve the correct config.
Your PHP class and your component doesn't have a nice one-to-one relationship like with the generic ReactBootstrap trait.

Wrap the JS routing logic into some custom Injector key

We could create a custom injector key.
Developers could register their routing config (and potentially other type of configuration in one spot)
Our wrapper could inject the section specific details as a variable in a callback.
Instead of having a "one-PHP-class-to-one-react-component" relation, we would have a "one-PHP-class-to-one-react-config" relationship.

Nested routes inside a bootstrapping component

Use the vanilla asset-admin logic to load a boostrapping component on a catch all route
Bootstrapping component would then load a component specified by the ReactAdmin implementation
The ReactAdmin custom component would then be responsible to set up it's own routing using nested routes
Preserves the "one-PHP-class-to-one-react-component" paradigme and keeps the admin section isolated from all the Silverstripe CMS admin craziness.
Not sure this is actually possible.


Allow terminal to be pinned to sidebar like file explorer and other tabs

There should be an option to integrate terminal into sidebar!

You can do this by dragging the TERMINAL panel title into the side bar (left) or side panel (right).


fix dataset explorer plot with count not displaying

Description
Fixed issue https://github.com/microsoft/responsible-ai-toolbox/issues/1453 where count plot is not displaying.
The main problem was that count uses "none" as the metadata name, which does not have any sorted categorical values (see https://github.com/microsoft/responsible-ai-toolbox/blob/bc7a9f91445db86e41784c9355bc7b9d230c7cb2/libs/core-ui/src/lib/util/JointDataset.ts#L739 which sets treatAsCategorical=True, but does not specify categorical values).  However, when creating the highchart options, we skip the step to pass the values of the "none" group, since we iterate over all categorical values.  There are several possible fixes here (another I had was to insert an array with some dummy "count" value for the categoricals values in JointDataset which also worked), but I felt this was the least intrusive and safest one.
Screenshot of fixed plot:

Checklist

[x] I have added screenshots above for all UI changes.
[ ] Documentation was updated if it was needed.
[x] New tests were added or changes were manually verified.

In the screenshot I don't see none showing up. What am I missing? [Note: I don't mean to hold this up at all. Feel free to proceed in any case.]

In the screenshot I don't see none showing up. What am I missing? [Note: I don't mean to hold this up at all. Feel free to proceed in any case.]

@romanlutz, I checked that locally, the none shows up in the pop up when you hover over each column in the chart. For other y-axis choices like categorical features, we are displaying apple: 5, banana: 8. And for Ilya's change for count, we display none


Nodepool metrics

committed txn rate
read rate
write rate
query rate
finalization rate
active WIs
active txns
abort rate
conflict abort rate

persistence flush latency
push rate
push latency
read, write, query processing latency
finalization latency

Number of keys in indexer
Total number of record versions
Total size of user data (the SKVRecord::Storage and payload size, and size of keys)

done


⚠ Bofrost.lu has degraded performance

In 46f7d21, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1564 ms

Resolved: Bofrost.lu performance has improved in 5c7ebef after 23 minutes.


Bugfix/2022 09 04 error fetching data entry by portfolio

fix for finding entry was the .first() parameter when using filter


Mixing Typescript and Javascript

This has code in Javascript for some and Typescript for others. Should really have both examples. When debugging on the browser, you are in Javascript not Typescript

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: db285f50-5770-e426-47f6-a9f78536cab3
Version Independent ID: 55778f17-2bdd-898b-41fc-e3f4e5517197
Content: Runtime for Excel custom functions
Content Source: docs/excel/custom-functions-runtime.md
Product: office 365
GitHub Login: @o365devx
Microsoft Alias: o365devx

100% agree. Having TypeScript and JavaScript documentation would be advantageous although it's probably more important to have JavaScript examples than typescript in general

Hi folks!
Many thanks for the feedback, it's very helpful for us to hear directly what developers want to see in our documentation. We've taken out the mix of TS/JS samples in the custom functions documentation and are discussing on our team about the possibility of integrating TS. :) I'm going to mark this issue as resolved for now, but wanted to let you know that we've heard your feedback and are taking it into consideration!


hack: simulated payouts ignore missing key

Closing as repo is being archived - to be raised against https://github.com/maidsafe/safe_network if still required.


Inconsistency with regex handling.

All commands should be handled within Command Handler, with some exceptions for the random rolling functions.
However isFortune, isADA, isThatcher and isNietzsche are all residing within handleEvent.hs making it extremely cluttered.
These should be migrated to CommandHandler.

True, haven't considered that we'd get to the point of having so many miscellaneous functions. I think that we should have a seperate miscellaneous folder with all the misc. functionality/REs. Files like ADAPriceFetcher.hs should also be moved there.

As it stands it should be easy for them to be moved straight into the command handler file without any loss of functionality. The files that should be allowed to be there are the ones to do with rolling and random chance.


refactor: [NPM] parsing label selector for general translation logic

Reason for Change:

This PR includes

Add comments of translation packages.
Refactor parseSelector.go before egress translation logic to better understand parseSelector code and significantly simplify codes and reduce multiple computations in translatePolicy.go

Issue Fixed:

Requirements:

[x] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests

Notes:
You can find the generic ingress translation PR (https://github.com/Azure/azure-container-networking/pull/1055)
Will delete unused codes add UTs for parseSelector.go in a next PR.
Will follow egress translation PR.

/azp run

/azp run


Open-source development monetization

In short: this PR proposes a way to monetize open-source development of your project.
The idea is similar to how free-to-play works in gamedev industry: "You are free to wait for the package download - but in case if time is money for you, please consider buying non-waiting access to the package, every cent goes to the package developer to incentive the open-source development."
For details please refer to https://github.com/Free2Wait/composer-free2wait .
According to packagist statistics of your package https://packagist.org/packages/tobscure/json-api/stats , in theory it could bring to you about 5,768 (installs per month) * 0.03 (estimated conversion installs-to-sale) * 5 (price of each non-waiting access per month) = estimated $865.2 per month.
Please do not consider it as ready-to-merge PR, it's work-in-progress: I am just willing to get your potentional or conditional (what is needed to make it suitable) consent to merge it in the future. There are already several issues/concerns (see https://github.com/Free2Wait/composer-free2wait/issues).
Please give me your feedback about the idea: what do you think? Are you interested in monetizing open-source development? Do you have any suggestions? Concerns?
Would be glad to receive any feeedback. Thank you for attention.

Close this, please?


The ownerGroup of a logbook can not be modified

When changing the ownerGroup of an existing logbook a new logbook is created instead

I just tried it but failed to reproduce the behaviour. While the logbook's owner group was not updated, I did not observe that a new logbook was created. Were you able to reproduce it?
What I noticed though: The logbook's inheritance from basesnippets also prohibits updates after the default expiration time. I think we should patch all logbooks to ensure that they don't expire. What do you think? @minottic @stephan271

I checked on the Mongo DB level, and that is what I saw, I dont know how reproducable it is.
Concerning the logbook inheritance: you mean new snippets can not be added to the logbook after the expiry ? In any case the inheritance related issue deserves its own issue entry.

I have added issue #187 for the inheritance related problem


API Revisioning

API revisioning allows API developers to maintain multiple revisions for a given API. In an environment where API changes are done rapidly, the changes can be deployed as revisions, track the changes applied, and rever back to a stable revision in a case where the API is broken.
Subtasks

[x] List revisions
[x] View all information of a revision (including docs, swagger, all)
[x] Deploy Revision
[x] Restore Revision

Closing since the feature is completed.


test_sqllogictest: Fix typos in comment from upstream

This comment had typos, and was also very confusing. Split a long
sentence into two to help clarify. These typos exist in the upstream
sqllogictest. Unfortunately, the SQLite project does not accept
contributions, so I can't fix it there.
Feel free to close this without accepting it: I understand if you don't want to diverge from the original upstream version too much. However, I have found that DuckDB's test suite seems to be excellent since it is mostly just "plain SQL", so it can be used with systems that are not DuckDB. At this point, I figure you might as well improve this tool yourselves. As I continue to play with it, I'll be sure to try and push relevant changes back to DuckDB, since I think even just having a high quality, open source, SQL test suite would be an enormous benefit to the database industry.
Thanks!

Thanks!


Issues not captured

Extension Console output in Nova
Mypy[11:54:10.797000] Running /Users/hans/.pyenv/shims/mypy simulator.py
Mypy[11:54:11.482000] Checking simulator.py
Mypy[11:54:11.482000] Found 0 issue(s)

Terminal output of same command
@ ~/D/Simulator> /Users/hans/.pyenv/shims/mypy simulator.py
simulator.py:107: error: Function is missing a return type annotation
simulator.py:107: note: Use "-> None" if function does not return a value
simulator.py:108: error: Name 'x' is not defined
Found 2 errors in 1 file (checked 1 source file)

I tried to dig into the source code but I could not quite find where the issue occurs as I am not too familiar with JS and the Nova API. I think somehow the capturing of stdout/stderr does not occur correctly.

Hey, thanks for letting me know.
I’ll look into it a bit later. Maybe the latest Nova updates changed something I let slip unnoticed. Although, it is the first such report since the last Nova update.
By the way, do you have a code example to verify this issue? A one where it reproduces accurately.

It does not work for me in general. None of the issues in this specific file get reported:
#!/usr/bin/env python3

def my_function():
    print(x)

my_function()

regular Mypy output is
test.py:4: error: Function is missing a return type annotation
test.py:4: note: Use "-> None" if function does not return a value
test.py:5: error: Name 'x' is not defined
Found 2 errors in 1 file (checked 1 source file)

I am not sure what this is related to. Maybe it is because I am using fish as a shell? Could this potentially influence the plugin?

Thanks. I doubt that fish is the reason here since I’m also a fellow fish user 😄 I’ll check it ASAP.

@Kamik423, I tried to reproduce this behavior, but strangely, Mypy gave me the same result in all cases I checked: VS Code, bare Mypy, and Nova. In all cases, I checked with and without a configuration file. And I don’t have a global configuration file for Mypy.
My project-level configuration usually looks like this (and should not affect results):
[mypy]
ignore_missing_imports = True
follow_imports = silent
show_column_numbers = True
warn_redundant_casts = True
sqlite_cache = True

The result always was “Success: no issues found in 1 source file”. But something similar to the behavior you have I was able to reproduce with the --strict option. It looks like the following:
playground-3.py:4:1: error: Function is missing a return type annotation
playground-3.py:4:1: note: Use "-> None" if function does not return a value
playground-3.py:5:11: error: Name 'x' is not defined
playground-3.py:8:1: error: Call to untyped function "my_function" in typed context
Found 3 errors in 1 file (checked 1 source file)

So, do you have a global configuration file for Mypy maybe somewhere, like $XDG_CONFIG_HOME/mypy/config or ~/.config/mypy/config or ~/.mypy.ini, by any chance? But beyond those, Mypy will always prioritize a project- or directory-level configuration file, like mypy.ini then .mypy.ini, and finally setup.cfg. Maybe there’s an option somewhere that works for bare use yet not visible for the extension.
Also, the version of Mypy I’m using is 0.812, just in case. Which one do you use?
For example, Flake8 always sees the undefined x error, the obvious and only real one here (since other errors exist only for the strict mode). Yet my Mypy version sees nothing in this case, and I’m not sure it has to, without some particular options.
To be precise (since the strict option is an alias for a set of flags), the following flags will produce a result like above:

The --disallow-untyped-calls for error: Call to untyped function "my_function" in typed context;
The --disallow-untyped-defs for error: Function is missing a return type annotation and note: Use "-> None" if function does not return a value;
And the --check-untyped-defs for error: Name 'x' is not defined.

By default, all of those are disabled (or ignored).
My assumption here is that you use an older Mypy version, where some of those options are possibly enabled, or it’s some inconsistencies between global and local configurations.

Unfortunately I was only using the trial version of Nova and have decided not to continue on to the paid one, so I cannot help you further. I hope no one else encounters the issue though.

@Kamik423, no worries, and thank you for the report anyway. Maybe it’ll help in the future.


dcp analyzer

I'd like to use the dcp analyzer but the dcp.stanford.edu website appears to be down. Will the site be back up or is there another way to access the source for the analyzer? Thanks!

This is sad news! I'll look into it.

Bumping this as well! Was trying to use it for a demonstration, but I get no response.
(base) guille-mbp:~ guille$ ping dcp.stanford.edu PING dcp.stanford.edu (<IP_ADDRESS>): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 Request timeout for icmp_seq 3 ^C --- dcp.stanford.edu ping statistics --- 5 packets transmitted, 0 packets received, 100.0% packet loss (base) guille-mbp:~ guille$

It should be up now. Try it!

Sounds great! Wanted to also bump, just in case :)

I spoke too soon. There's some kind of weird permissions error (example http://dcp.stanford.edu/analyzer?expr=1%2B1). I'm truly baffled about why this is happening. If anyone is familiar with django I'd appreciate help. Basically it's hosted using Apache and mod_wsgi, when you call the analyzer the parse view needs to write to a file. The file is writeable by all users, but somehow it throws an error to open it with write permissions.

Perhaps @sredmond can help?

Unfortunately I don't have any Django knowledge to drop here. The situation of a globally-writeable fail failing to be opened for writing is strange - there might be something weird if the file is writeable by all users but not readable (although who sets permissions like that), in which case some hidden library call that might be relying on reading file data could be crashing. Can you include the error that is generated when trying to open the file with write permissions?


v1.0.2

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/77651
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.2 -m "<description of version>" a4c4b18803ff594e566efa0ad27b26b85c0dd1fd
git push origin v1.0.2


Fix array indexing issue

Codecov Report
Patch and project coverage have no change.

Comparison is base (aa13e2a) 64.43% compared to head (ed48f5b) 64.43%.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop      #18   +/-   ##
========================================
  Coverage    64.43%   64.43%
========================================
  Files            8        8
  Lines          464      464
========================================
  Hits           299      299
  Misses         165      165

Flag
Coverage Δ

unittests
64.43% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Issue: overlap text

Steps:
Access kyber network > Exchange > Click advance button > input long gas price > Obs: overlap text between resolution:  1000x949  and 800x949

duplicate


(Suggestion) Javascript/PlaceholderAPI conditions

The current conditions are awesome, but it would be even better if you supported conditions that one could take from PlaceholderAPI. An example of what I imply would be the following:
http://pastebin.com/Q6xXmCbN
I don't know exactly how you would implement this, maybe separate nodes, or putting each expression in a separate file that you then refer to with a permission node like: cperms.expression.prison_level1 to indicate that expression. Anyways, I just thought it would expand the usefulness of the plugin. I would personally use it, I thought of it while looking at the LuckPerms documentation on default-assignments. :)

Sure.
So the placeholder just returns a list of permission nodes?

I don't really understand your question. If the conditions (expression) is true, then the player would have the permissions nodes under "true" applied to him, if it were false, a player would have other permission nodes applied.

So the config example you linked would be a part of ConditionalPerms?

I'm suggesting the idea of these conditions people can create (the
conditions described above, with the help of placeholder api). I don't know
how exactly you'd want to implement it, but yes, I was thinking it would be
part of conditional perms.
On Oct 27, 2016 9:50 AM, "Luck"<EMAIL_ADDRESS>wrote:

So the config example you linked would be a part of ConditionalPerms?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lucko/ConditionalPerms/issues/1#issuecomment-256703275,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL6K-RuW4tCfpFu7PAEBaNQl2eZ6DZGtks5q4NY6gaJpZM4Kh13E
.

Alright. LuckPerms is my priority right now, but I might get a chance to do this at some point. 🙂


Add src to absolute paths in browserify task

Fixes #9893
Unfortunately, I don't know why src is missing from the middle of the path, but adding it manually fixes the task.

:+1: Sure, do the thing


What is the meaning of pipeline status QUEUED and COMPLETE. why some pipeline keep stick at queued state?

When I am running certain instances, few of them stays stuck at queued state and not able to process further. What conditions trigger queued state?
Is it cpu or memory load? Or issue related to input camera stream?
@whbruce @nnshah1  please help me to understand this behaviour.

Do you see it being reproducible? Have you tried increasing debug-level to capture logs?
Do you use gstreamer in a shell, or programmatically (C/C++, Python)?

@divdaisymuffin
Pipelines will be in QUEUED state before it starts(RUNNING state).
In what case pipeline could be in  QUEUED state longer?

gstreamer is waiting on resources (CPU/GPU load)
MAX_RUNNING_PIPELINES environment variable is set to a number and those number of pipelines are already in RUNNING state, once one of them is COMPLETED, next pipeline will be picked up.


KAFKA-4593: Don't throw IllegalStateException and die on task migration

Call for review @bbejeck @guozhangwang @dguy

Triggered a system test for this: https://jenkins.confluent.io/job/system-test-kafka-branch-builder/1083/

Updated

@mjsax, i still think we need an interface to pass into the ChangelogReader rather than AssignedTasks - it doesn't need the whole AssignedTasks, just a single method.

Updated.

Updated.

@mjsax, can you please rebase?

Rebased.
Retriggered system test: https://jenkins.confluent.io/job/system-test-kafka-branch-builder/1087/
System test did fail above -- not sure why. Seems to be unrelated to this PR and we got no failing tests in night runs recently. Let's see.

@mjsax the failure in the previous run was the broker compatibility issue that was fixed by https://github.com/apache/kafka/pull/3944
The latest build passed.

merged to trunk


Generated records implement Serializable when serializableModel-configOption is enabled

Checklist

[x] Closes #71 and #61
[x] Documentation (README.md) has been updated
[ ] Version number updated in pom.xml and licenseInfo.mustache
[ ] Project has been compiled with mvn clean install
[ ] Updated generated-sources-files have been committed

Updated wiki

PATCH


⚠ Samsung has degraded performance

In 38c1d0f, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2322 ms

Resolved: Samsung performance has improved in f97062c.


Honor Priority Mode

Do not wake screen or vibrate,  even if checked, if user is in Priority or None mode.  For Lollipop only.

Can't disable the screen from waking without root (needed to see if user is in priority/none mode).  Also can't use lollipop notification APIs to wake screen like done with vibrate.


suggest allow custom default merge message template

Gitea version (or commit ref):
Git version:
Operating system:
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[ ] Not relevant

Log gist:

Description
Hello, I think it's usefull , if user can define merge message template, maybe we can allow user to do it by define .gitea/MERGE_MESSAGE_{merge_style}_TEMPLATE.md file in base branch. which is Similar to issue and pr template. thanks.
Screenshots

I think this is still valid

A relatively simple first solution would be to just provide per-instance templates - these could actually use gotemplates and have the models.Issue etc. passed in.
Per-repository templates would need to go into the .gitea/ folder on the $master branch using code from the issue templates and template repositories code. If we use gotemplates for this we cannot just pass in the models.Issue etc as it would not be too difficult to use methods on the Issue to then change the User etc. Therefore some kind of defined variable replacement would be needed - Again similar to that used in issue/repository templates.


feat: Use "casbin" command instead of "java -jar target/casbin-java-cli.jar" command

fix: #12

Replaced by: https://github.com/jcasbin/casbin-java-cli/pull/14


update resources name

follow https://github.com/kubernetes/kubernetes/pull/43303

This change is

LGTM

Should this be targeting the 1.6 as the base branch instead? It doesn't appear in kubectl get output for 1.5.x.

Should this be targeting the 1.6 as the base branch instead?

Yes. The release 1.6 is not out yet

@ymqytw , You can change the base branch to release-1.6. If you do that, I can merge this right away.

@devin-donnelly Unfortunately, I can't change the base branch. I'm not the owner of this PR and I don't have permission to change that.

I was able to change the base to release-1.6.

@chenopis Great! Thanks.


Temperature Presets for Probe

Added temperature presets (meat temps) to probe climate
Align variables referenced between probe climate and probe sensor entities
Fixed issue where probe alarm wasn't resetting
Updated min target probe temp to 80°F
Closes #44

Going to reopen from a different branch so I can submit multiple pull requests.


[Web Portal] disable appTrackingUrl button if returned url is nil

Coverage increased (+20.5%) to 73.81% when pulling 93d76d9994be3a501498fd9ffa5a5ec0c1a69e1d on qinsu/portal/atu into<PHONE_NUMBER>5345dabc2d9cdd8bca9d19481cef7d on master.


Is it normal that FID affected by the num_gen option?

Thanks for this great work.
I have reproduced the claimed FID 3.5 on cifar10. But the default FID computation is quite time consuming(about 40 minutes) since it requires generating 50,000 images.
When I reduce the num_gen option to 5,000 in compute_fid.py, the resulted FID increases a lot, e.g. increased from 5.12 to 9.75.
Is this normal? According FID's definition,   FID shall not affected by the num_gen.

Yes, it is normal. The FID is defined as the squared 2-Wasserstein distance between two approximated Gaussians. We first embed generated and real data within the deepest Inception layer (to compare features rather than pixels) and then, we compute Gaussian statistics of the generated and real samples. The more samples we have to compute the Gaussian statistics, the better the approximation is.
The process takes indeed ~35 min on 1 A100. Increasing the batch size and the number of GPUs can reduce this time accordingly.


Supplying a Class to a factory that overrides to_s no longer results in ...

...getting the wrong Class constructed
This patch allows factories to be constructed like this:
FactoryGirl::Factory.new(:name, :class => SomeConst)
even when SomeConst.to_s returns something other than "SomeConst"
Patch includes test.

Can you provide a real-world example where you'd override to_s on the class level? I've never seen this done before so I'm interested in why you'd do that in the first place. Subsequently, all you have to do to get around this is pass a string to :class =>.

Sure thing; in my case, we have a proxy class that forwards its method calls to one of two other classes, depending on if we're using an offline implementation or a web service backed implementation.
In testing we end up using both implementations at different times, and initially configured the factory to use the proxy class (after all, #new was proxied to the right spot). It appeared to work, except that when we ran all the tests together, the very first test to call the factory would lock the implementation in use by the factory. The confusion we suffered ended up costing us 1 to 2 developer working days where we weren't entirely certain why tests would fail sometimes but not others. (admittedly, most of that time was spent pouring over FactoryGirl's code)
Given that fixing the problem is relatively trivial (assuming no one overrides .to_a? ...) we thought it would be a good idea to submit a fix.
I admit that our use case is relatively rare. I'd still like to see this issue patched though, as it violates the principle of least surprise when your code (potentially needlessly) overrides to_s.

We're curre


sys:split/3 cause segmentation fault

I'm aware that sys:split/3 has renamed to sys:split_all/3. When runing old code before migration, I find that now sys:split/3 will cause segmentation fault. e.g.:
:- initialization(main).

main :- sys:split('a b', ' ', L), write(L), nl, halt.

Backtrace:
Core was generated by `tpl foo.pro'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000000000 in ?? ()
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x000000000043ddc6 in call (q=0x213bed0) at src/jela.c:421
#2  0x000000000043dfb7 in run_me (q=0x213bed0) at src/jela.c:471
#3  0x00000000004088bd in query_run (self=0x213bed0) at src/trealla.c:887
#4  0x000000000040a15e in trealla_run_query (self=0x212d010, src=0x2139530 "main.") at src/trealla.c:1376
#5  0x0000000000409cbf in trealla_consult_file (self=0x212d010, filename=0x7ffd088bb810 "foo.pro") at src/trealla.c:1277
#6  0x000000000040521b in main (ac=2, av=0x7ffd088ba868) at tpl.c:364
(gdb)

Not sure if it is related, now sys:split_all/3 will cause an error:
% tpl
Trealla v0.1alpha, Jun  6 2017
?- sys:split_all('a b', ' ', L).
ERROR: UNKNOWN -> 'split_all/3'
false.
?-

Yes, for some reason repl is messed up.
On 6 Jun 2017 16:41, "Xin Wang"<EMAIL_ADDRESS>wrote:

Not sure if it is related, now sys:split_all/3 will cause an error:
% tpl
Trealla v0.1alpha, Jun  6 2017
?- sys:split_all('a b', ' ', L).
ERROR: UNKNOWN -> 'split_all/3'
false.
?-
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/trealla-lang/trealla/issues/135#issuecomment-306396475,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVqpEjNUbCQJ3ZQIsVBWcs2SYy27Wnneks5sBPSbgaJpZM4NwvLA
.

This problem also exists if usage of initialization/1 directive and sys:split_all/3 are seperated into two source files.
I have added another test to trealla-tests repo.

Can be closed now, thanks.