add category summary to blog page

The blog page has links on the left, but these are duplicates of the menu bar.
It would be more useful to have a category listing with counts in that spot.

Hi @kgorman - We're planning to address this in the site redesign that's currently underway.


[T2A4][W14-A1]Lim Jie

Ready for review

the inlining of processProgramArgs is from activity 3.
Accepting this PR without a review because another of your PRs for this tutorial was reviewed in detail.


[AERIE-2145] Gaps in external profiles

Tickets addressed: AERIE-2145
Review: By commit
Merge strategy: Merge (no squash)

Description
by commit:

The nullableP parser currently cannot unparse nulls because it throws a NoSuchElementException when unwrapping. The workaround is to throw a ClassCastException which the chooseP parser will catch try the next option. @Twisol was this the intended pattern? I don't see another way to do it, but throwing for control flow on the happy path seems iffy.
This allows the dynamics in ProfileSets to be Optional. This allows external dataset profiles to have gaps, but also requires all segments of simulated profiles to be wrapped in Optional.of(). Also, the Post/GetProfileSegmentsActions were updated to write to the new is_gap column of the profile_segment table.
Due to conversions between our many formats for representing profiles, the duration of the last segment is lost when storing and retrieving from the database. This isn't an issue for simulated profiles because they end at the plan horizon, but external profiles can end in the middle of the plan. So I've added an extra gap segment at the end of all profiles to keep the duration. This required a small change in the UI here.

Verification
I'm in progress writing an e2e test(s) for this.
Documentation
I'm in progress writing a docs tutorial for this.
Future work
we did it bois

@Twisol was this the intended pattern?

I'm not sure what you mean here. The develop implementation of nullableP invokes Optional::get, which will of course throw on empty. This doesn't seem to be a problem with the parser system itself.
Here is a custom parser (no combinators) that I think should work. I haven't tested this, and I'm not confident that my getSchema() uses the right JSON-Schema syntax, but it's the basic idea.
    return new JsonParser<>() {
      @Override
      public JsonObject getSchema(final SchemaCache anchors) {
        return Json.createObjectBuilder()
            .add("any", Json.createArrayBuilder()
                .add(JsonValue.NULL)
                .add(parser.getSchema()))
            .build();
      }

      @Override
      public JsonParseResult<Optional<T>> parse(final JsonValue json) {
        if (json.getValueType() == JsonValue.ValueType.NULL) return JsonParseResult.success(Optional.empty());

        return parser.parse(json).mapSuccess(Optional::of);
      }

      @Override
      public JsonValue unparse(final Optional<T> value) {
        return value.map(parser::unparse).orElse(JsonValue.NULL);
      }
    };

@Twisol When unparsing chooseP(A, B), choose's unparser will only check B's unparser if a ClassCastException is thrown. In cases where the Java types associated with A and B are different, this is fine because the exception will be caused by chooseP itself. But in this case, both A and N operate on Optional<T>, so the only way for A to tell  chooseP to try B when it encounters Optional.empty() is to manually throw a ClassCastException.

Right. Because chooseP depends on class casts to pick the right parser, it isn't appropriate for this case. Put another way, the individual parsers are supposed to convert to and from values of some type, but one of them only handles some of them (failing on the rest) and the other is lossy because it sends everything to null (and then back to empty).
The individual parsers ought to be total and lossless, so chooseP is not a good combinator to use to decompose this problem with.

I really want a proper sumP akin to productP but with Either instead of Pair. Unfortunately there are serious ergonomics issues with the design I've tried up to this point.

@Twisol just for the sake of getting something working, I reworked it to add chooseWithPredicateP with allows each variant to decide whether it can be unparsed from the given value. There's a wee bit of "Don't Repeat Yourself Except When You Need To" because for the life of me I can't figure out how to map a generic varargs to another varargs array without losing all the type information. Thoughts on that?

Did you have a chance to evaluate my alternative solution from before?

Wow. That there the whole time? I completely missed it. Please hold

That'll do it 🤦 . Thanks!

Glad to be of assistance :)

Turns out we already had a docs page for external datasets, and its better written! I'm going to update it and move it to the new directory instead of using my own.

Uncovered a problem while testing, somewhere along the way it makes an assumption that the external dataset starts at plan start. Will fix.

Fixed problem that was forcing datasets to start at the plan start.
Added e2e test

It doesn't test the full process of adding and querying an external dataset because the code for retrieving datasets is not exposed as a hasura action. So instead it uploads a dataset and queries it directly from hasura's autogenerated plan_dataset_by_pk query.
This tests that we correctly store datasets that don't start at the plan start and gaps in the middle of profiles.

Added tutorial docs


[MINOR] change project version to 0.5.1

What changes were proposed in this pull request?
change project version to 0.5.1
Why are the changes needed?
tag 0.5.1_rc0 based this commit
Does this PR introduce any user-facing change?
no
How was this patch tested?
build package with package name 0.5.1

@FANNG1 does it still require?


Creating an account for Jason Clark.

Build failed.

http://logs.bonnyci.org/check_github/BonnyCI/hoist/239/1489611506.0/bonnyci-run-check-multinode : FAILURE in 8m 11s

I'll just resubmit this....


how can i do like this in nlog?

in serilog:
using (LogContext.PushProperty("a", 1))
{
    log.Information("b={b} a={a}");
    using (LogContext.PushProperty("b", 2))
    {
        log.Information("c={c} b={b} a={a}", 3);
    }
}

output:
[16:51:37 inf] b={b} a=1
[16:51:37 inf] c=3 b=2 a=1

thanks!!!

NLog 4.1 introduced MDLC, so you can do this:
using (MappedDiagnosticsLogicalContext.SetScoped("a", "1")) {
    log.Info("Hello World");
    using (MappedDiagnosticsLogicalContext.SetScoped("b", "2")) {
         log.Info("Hello Again");
    }
}

And then you can have the following console-target:
<target type="console" layout="${time} ${level} ${message} ${all-event-properties} ${mdlc=a}  ${mdlc=b}" />

But where Serilog automatically merges LogContext-properties into the LogEvent-properties (using enricher), then NLog keeps them seperate. But yes it could be nice with a ${all-scope-properties}. Guess it should be added with NLog 5.0

Grateful！！😊

Closing the question as answered. I guess any feature-request / pull-request to be created separately.


Numeric separators are not transpiled in ECMAScript < 2021

Describe the bug
Numeric separators are not removed from the transpired code even if I set ES5 as a target.
Input code
const foo = 1_000;

Config
{
  "jsc": {
    "parser": {
      "syntax": "ecmascript",
      "jsx": false
    },
    "target": "es5",
    "loose": false,
    "minify": {
      "compress": false,
      "mangle": false
    }
  },
  "module": {
    "type": "es6"
  },
  "minify": false,
  "isModule": false
}

Playground link
https://play.swc.rs/?version=1.2.187&code=H4sIAAAAAAAAA0vOzysuUUjLz1ewVTCMNzAwsAYAekUtKRIAAAA%3D&config=H4sIAAAAAAAAA0WMTQrEIAxG75K1286id5hDBCctFv9IUhgR714tlu7C915ehUMsrBUyshCPS0pU%2FMMKZAOKZZcVTNf6tKEXagYUeScdiiyd%2BZSEJjUQXHRbGSWbQmYSeRHG3T9m66GQfucYKmjJdAc%2F0N7G%2FHPynaLySe0Cj9ke9LUAAAA%3D
Expected behavior
The input code should be transpiled into
var foo = 1000;

Actual behavior
Numeric separators stay unchanged, but the other syntax like const declaration gets traspiled:
var foo = 1_000;

Version
1.2.164+
Additional context
It seems like a regression issue, version 1.2.163 gives a correct result.
No response

Seems like a regression related to spans...


Enforce vocab

Hi,
Where in code is the best to enforce using an array of OWL/vocabs or stick to a SHACL?
Thanks very much!

Furthermore, using these vocabs and

an input JSON-ld RDF as context
a prompt Question,
can you recommend a way to generate Answer without hallucination?


Container does not consistently center content

Component or Package Name: Container
Component or Package Version: 1.10.11
@jsxp-email/cli Version?: N/A
Operating System (or Browser): Chrome on Windows, gmail on android
Node Version: 20
Link to reproduction (⚠ read below): https://stackblitz.com/edit/jsx-email-repro-yrfrwp?file=templates%2FReproduction.tsx

Expected Behavior
Content placed inside of a <Container/> is centered.
Actual Behavior
Content placed inside of a <Container/> is not automatically centered.
Additional Information
From https://jsx.email/docs/components/container:

Horizontally center child components and content

In testing, I found that the most consistent way to get this component to truly 'center' the child content is to set align="center" on the <td> inside of the container <table> rather than the table itself.
Alternatively, this might just be a documentation discrepancy, as the react-email maintainers think despite identical documentation and relatively similar component (it is a fork after all). The other way to make this work is just to set m-auto on the content, which is not terrible (though I don't know that the Container maintains much use).

@ganondev let's resurrect your react-email PR here. I did a deep dive on where this component comes from (it's something we inherited from forking) and it points back to mj-container in MJML v3, which was removed in MJML v4 because drum roll issues with confusing users. Basically this was a half-baked implementation by react-email.
So this presents an opportunity to improve and take another step forward in this project. What I think I'd like to do is offer a boolean prop named align and set that typed to 'center' | 'left' | 'right' and default to center. This will almost certainly be a breaking change for people relying on the errant behavior, so it's a great candidate for the next major version (which is soon).
That all begs the question: is Container the right name for this component?

Makes sense. I'm not sure about the name, but it never felt meaningful. In proper component libraries, when you have something with a vague name like container or box, the point is usually 'this is just a <div> with sensible defaults for the library', but that's not really what is happening here. It's a component for alignment, and I'd be a fan of a component that is named for what it's doing. Something like <Aligner/> but perhaps that's too narrow. It's hard to say whether this component has a lot of other use because it doesn't really do anything in its current form that Section doesn't do better.


Update to syntax section

The following is missing from the syntax section at the top of the page.
| expression [ NOT ] IN ('expression','expression',...)

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

ID: 9d95b977-1f78-9a1b-de56-e0d1cf4b1d40
Version Independent ID: 98dd5dfe-631c-5ff5-c1ee-516d3c68a195
Content: WHERE (Azure Stream Analytics) - Stream Analytics Query
Content Source: stream-analytics-docs/where-azure-stream-analytics.md
Service: stream-analytics
GitHub Login: @Fleid
Microsoft Alias: fleide

Good catch, thanks!
Fixing now.

It took its time but it's online now :)
Thanks again!
#please-close


Fails to connect

The future returned by lapin::client::Client::connect doesn't always complete.
In some instances when running something like the following code, the application will just stall.
core.run(
    TcpStream::connect(&addr, &handle).and_then(|stream| {
        lapin::client::Client::connect(stream, &ConnectionOptions::default())
    })
)

log file: https://www.dropbox.com/s/gti4kf327vfepib/log.html?dl=0

thanks, I'll look into it

I can see the issue, but I can rarely trigger it, what's your setup? How far is the amqp server?
I pushed a small fix in version 0.7.0, please try with this one, it might fix this issue.

Since I have a lot of integration tests, I'm hitting this bug pretty much all the time.
I'm running RabbitMQ 3.6.9 locally in a docker container.
I have tested it with version 0.7.0 but the bug persists. In fact I think I found another one but I'll open a separate issue for it.

I wasn't able to reproduce the output from #30 so here is another log for this issue but with a few more log statements (https://github.com/dfaust/lapin/blob/debug-log/futures/src/transport.rs#L192-L260), I hope it helps.
log file: https://www.dropbox.com/s/jfls4ikt5ci4hjs/conn_log_28.html?dl=0

@dfaust not sure that would change anything about this (Geal have some ideas on how to work around that) but could you give #31 a go?

I checked a few failed tests using #31, this time I couldn't find any ERRO did not get a frame? -> None, so I posted the log to #30.


Allow excluding the cluster security group from the list of additional security groups.

Is your request related to a problem? Please describe.
I am importing EKS clusters created with eksctl. In my existing clusters, the cluster security group is not on the list of additional security groups. I can't import my existing EKS cluster without it being forced to recreate because the module forces the cluster security group to be part of the additional security groups.
Describe the solution you'd like.
Adding a variable like cluster_additional_security_group_ids_include_cluster_sg_id which defaults to true to keep the current behavior, but allowing it to be set to false so that the cluster security group id is not added to the list of additional security group ids.
Describe alternatives you've considered.
The only alternatives are to not use the module, or recreate my cluster.
Additional context

Can you provide a reproduction? This doesn't quite make sense but seeing a repro will help clarify

I just opened https://github.com/terraform-aws-modules/terraform-aws-eks/pull/2752, maybe that will help it make more sense.
I'm using terraform import to import and existing EKS cluster. In my existing cluster, the Cluster Security Group is not in the list of Additional Security Groups:

As the module is currently, it adds the cluster security group to the list of additional security groups, but this change forces a replacement when running terraform apply. The submitted PR lets a variable cluster_additional_security_group_ids_exclude_cluster_sg_id be set to true, so the list of additional security groups will not have the cluster security group added.

which cluster security group - there is the primary security group which the EKS service creates automatically, and this module creates on additional security group which allows users to control the security groups rules
If you do not want to have this 2nd cluster security group created, you can set create_cluster_security_group = false

When my cluster was initially created with eksctl (eksctl create cluster --name <name>), it created two security groups. When viewing my cluster in the console, one of them is listed under Cluster Security Group, and one of them is under Additional Security Groups, as shown in the screenshot above.
I was hoping to be able to terraform import all my existing EKS resources using this module with module variables set such that when running terraform apply there would be few changes, and nothing replaced.
It seemed that I should import the security group shown under Cluster Security Group in the AWS console as module.eks.aws_security_group.cluster[0], and the security group listed under Additional Security Groups in the AWS console should be added with the variable cluster_additional_security_group_ids. But if I do that, the module tries to add the security group listed under Cluster Security Group to the list of Additional Security Groups, which forces replacement when running terraform apply.
I supposed I could set create_cluster_security_group = false, even though that security group does exist...or is the security group listed under Additional Security Groups the one that I should import into module.eks.aws_security_group.cluster[0]?

I haven't tried this but I don't think you should need to do anything with the Cluster Security Group in terms of Terraform import - that is not created nor controlled by Terraform, it was created by EKS. If anything, you may need to update the statefile manually after importing the cluster to specify the security group ID.
For the additional security group - you can import that into module.eks.aws_security_group.cluster[0]

Ah, that makes sense then. That get's me straightened out what to import where, it's looking like I can move forward now without any issues. Thanks!

awesome! sorry for any confusion - it can get complicated when resources that are created outside of Terraform are involved 😅
Closing for now but please feel free to open a new issue for any further issues/questions


Features

I threw something together real quick that does the absolute basics:

Takes a ViewModel and puts its properties on the element.
Renders to shadow dom with a template.

More things we need:

[ ] - Maybe the ability to render to the element's child instead of shadow DOM since shadow DOM doesn't let any global styles in.
[ ] - Make a real scope, figure out what to do there.
[ ] - Get the passed in props/attributes and pass those into the ViewModel when it is created

and probably a lot more.
@pYr0x @justinbmeyer
https://github.com/canjs/can-custom-elements/blob/master/test/test.js#L11

Awesome! I'm wondering if there should be a separate view model. I've been thinking we might use can-define directly on the element.
Sent from my iPhone

On Jan 20, 2017, at 4:46 PM, Matthew Phillips<EMAIL_ADDRESS>wrote:
I through something together real quick that does the absolute basics:
Takes a ViewModel and puts its properties on the element.
Renders to shadow dom with a template.
More things we need:

Maybe the ability to render to the element's child instead of shadow DOM since shadow DOM doesn't let any global styles in.
Make a real scope, figure out what to do there.
and probably a lot more.

@pYr0x @justinbmeyer
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I made it use can-define directly which comes out like this:
class MyApp extends CanElement {
	static get view() {
		return view;
	}
}

define(MyApp.prototype, {
	name: {
		value: "world"
	}
});

Since classes can be mixed in through function calls, it would be nice if can-define had a signature like this:
var defined = define.mixin({
	name: {
		value: "world"
	}
});

class MyApp extends defined(CanElement) {
	static get view() {
		return view;
	}
}

One issue to keep in mind is that standard elements don't have side-effects just by creating them and we should preserve them. Let's say we have a todo-list element that makes requests to fetch todos.  This:
var todoList = document.createElement("todo-list");

Should not start making requests.  This should:
document.body.appendChild("todoList");

You can trigger side-effects by setting setters though. Think about the img element which will start fetching as soon as you set the src property.

So I got scoping to work which means that bindings work in stache:
<some-child {foo}="bar"></some-child>

This will get bar from the parent scope and pass it in.
To make this template-language neutral this is how it currently works: https://github.com/canjs/can-custom-elements/blob/master/test/test.js#L10
This is ugly. We don't have a tagData kind of thing like with can-component so we can't pass a setupBindings function that way.  I think the setupBindings function should be on the renderer function so that if you do something like this:
var stache = require("can-stache");
require("can-stache-bindings");

var view = stache("{{foo}}");

view.setupBindings(el);

Open to a better way to have this function be available generically though.  cc @justinbmeyer

I want to make it so that you can bind attributes to properties. This should probably happen automatically for attributes -> properties but for the other direction that's not so clear. I think I might make a custom can-define behavior that works like so:
define(SomeElement.prototype, {
  foo: {
    value: "bar",
    attribute: true
  }
});

This means that if someone does this:
var el = document.querySelector("some-element");
el.foo = "something else";

The attribute would be updated to reflect that change.  Going to put it in can-custom-elements/attribute for now, might make it part of the base stuff later.

Closing this in favor of individual issues:
https://github.com/canjs/can-custom-elements/issues/3
https://github.com/canjs/can-custom-elements/issues/2

Value and value are only run when read, so they should work pretty well.
Sent from my iPhone

On Jan 21, 2017, at 9:29 AM, Matthew Phillips<EMAIL_ADDRESS>wrote:
So I got scoping to work which means that bindings work in stache:
<some-child {foo}="bar">
This will get bar from the parent scope and pass it in.
To make this template-language neutral this is how it currently works: https://github.com/canjs/can-custom-elements/blob/master/test/test.js#L10
This is ugly. We don't have a tagData kind of thing like with can-component so we can't pass a setupBindings function that way. I think the setupBindings function should be on the renderer function so that if you do something like this:
var stache = require("can-stache");
require("can-stache-bindings");
var view = stache("{{foo}}");
view.setupBindings(el);
Open to a better way to have this function be available generically though. cc @justinbmeyer
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


I need some help with this table. I want it to stretch horizonally accross the screen, and I feel like it's really obvious, what I'm doing wrong. Screenshot:

I've recreated that part which is visible in the screencap but it is behaving correctly.
Could you post the share link for this brew? Maybe there is a style tag elsewhere confusing things.

Sure thing. Uh.. if i can figure it out. should be as easy as that right?  https://homebrewery.naturalcrit.com/share/BkLr5AHqQ

OK, that's the link.
Hmm ... the table is showing as wide in my browser. What does the brew look like in your share link? (i.e. not editor tab)

It looks the same as the screenshot. The Spell slots are clipping through the barrier because it's too small. So from what youre saying it might be just my browser?

I'll try chrome instead

Seems to be solved. Closing.


update css variables for breakpoints and fix eslint errors

update css variables for breakpoints and fix eslint errors

Most of the changes seem to be present in the main branch through other PRs hence closing this. If still things that require to be merged, please resolve conflicts and reopen @aashishsingla567


Linux install calls for blues-utils which doesn't exist for Raspbian

The documentation claims that noble works for Raspberry Pi and the wiki says to install dependencies as follows:

sudo apt-get install bluetooth bluez-utils libbluetooth-dev

But bluez-utils doesn't exist for Raspbian. What should be the list of dependencies to get noble installed properly on Raspbian for Raspberry Pi?

The wiki is out of sync with the read me: https://github.com/sandeepmistry/noble#ubuntudebianraspbian
I've updated it with: sudo apt-get install bluetooth bluez libbluetooth-dev libudev-dev
@stasiana thanks for bringing this up.


[Design Spec] ESNext import()

import(specifier) is a newly proposed syntax for dynamically module loading. import(specifier) takes string as an input (Note: unlike ES6 static import which only allow string literal as module specifier) and returns a promise of module namespace object.
The full proposal can be found here
Original issue: #12364
This issue will discuss design proposal for implementing import(): parsing, type-checking, and emitting. The proposal will not include "module namespace object" type which will be separately discussed and implemented.
Parsing
import(specifier) will be parsed as CallExpression. and specifier will be parsed as AssignmentExpression
Error
It will be an error if the module flag is ES2015
Type-checking

specifier is type checked as string type. (Clarification: the only limitation for specifier in original proposal is that it can called toString())

The return of import(specifier) will be as following
-- if known module can be resolved from specifier, then we return Promise of module namespace object
-- if not known module, then we return Promise of any. This will give an error in noImplicitAny mode and import() is used as an expression

We will use existed module resolution logic to try to figure out the module of the dynamic import.

Emit
Emit for each different module kind emit is outlined below
import('blah');

Node

Promise.resolve().then(() => require('blah'));

AMD

define(["require", "exports", "blah"], function (require, exports) {
    "use strict";
    Object.defineProperty(exports, "__esModule", { value: true });
    new Promise(resolve => require(['blah'], resolve));
});

UMD

(function (factory) {
    if (typeof module === "object" && typeof module.exports === "object") {
        var v = factory(require, exports);
        if (v !== undefined) module.exports = v;
    }
    else if (typeof define === "function" && define.amd) {
        define(["require", "exports"], factory);
    }
})(function (require, exports, useSyncRequire) {
    "use strict";
    Object.defineProperty(exports, "__esModule", { value: true });
    require.length === 1 ?
        /*CommonJs Require*/ Promise.resolve().then(() => require('blah'));
        /*Amd Require*/ new Promise(resolve => require(['blah'], resolve));
});

System

system.import('blah')

ES2018 new value

import('blah')

import should not be allowed if --module ES2015.. we have no way of emitting them correctly.

@mhegazy Maybe you should let import() passthrough when --module ES2015.
Likely scenario for me here is using a bundler like Webpack that will take care of it (as of webpack 2.2, import() is supported).
This behavior is useful and we need a way to generate output with import(). If you feel uncomfortable with labeling ES2015 something that really is an extension thereof, maybe we need a new ES201? target.
My interpretation is that ES2015 is the native, standard, ES module system and I'm not shocked to see the newly approved import() inside it, even if it was not strictly speaking in 2015.

Shouldn't the 'if not known module' reflect the possibility of missing module and do not expose any?
I'm proposing in this case return Promise<{} | undefined>. Then the caller would be responsible to properly check result of the promise.

Ah, sorry, forgot it would go to failure channel of the promise. Then it should be Promise<{}>.

@mhegazy Maybe you should let import() passthrough when --module ES2015.
Likely scenario for me here is using a bundler like Webpack that will take care of it (as of webpack 2.2, import() is supported).

this is not valid ES2015 code. even if the engine supports ES2015 modules, import is a keyword and it would be an error.
I guess what you are looking for is a --module ES2018.

Then it should be Promise<{}>.

{} is fairly useless.. it will force users to case. any is more forgiving, and will allow users to proceed without adding a cast. the --noImplicitAny error would help those users interested in stomping out anys.

The emit for Node is slightly incorrect. The require should only start after the stack has unwinded, but the example snippet does it synchronously. It should look like:
Promise.resolve().then(() => require('blah'))

@mhegazy the main (existing) implementer of import() is webpack, so it would be highly desirable to have a passthrough for it. Currently, TypeScript users are stuck with using the deprecated and, eventually, "worsly typed" System.import() method in webpack.

Would --module esNext do? this will pass through import(..) as well as import .. and export ..?

Yeah, that would definitely do.

If spec is scheduled for es2018 I thing module=es2018 is better than esNext. Next is relative 😀

@mhegazy I think whether you graft it to --module es2015 or you create a new --module es2018 doesn't matter much (I could argue for both), as long as we can use it. 👍

Note: import() needs to wait until the stack unwinds prior to doing any eval.
For node it is also important to note that CJS modules only produce a default export according to the rewritten proposal:
Promise.resolve().then(() => {
  return {default: require('blah')}
});

CJS modules returning a default is an orthogonal issue. it applies to all ES6 import forms as well. this is tracked under https://github.com/Microsoft/TypeScript/issues/8687, and should be done around the time the node ES6 module implementation is starting to solidify.

Thanks all for the feedback. I have updated the spec accordingly. I decided that to introduce new flag since the syntax is not ES2015 valid

@yuit, For UMD modules, function.length is an ES5 feature, so i do not think we can use that. so we will have to use the boolean flag instead, or come up with another alternative.

Just to mention here, the transform for System.register should be the following:
import x from 'x';
import('dynamic').then(...);
// ->
System.register(['x'], function (_export, _context) {
  var x;
  return {
    setters: [X => x = X.default],
    execute: () => {
      _context.import('dynamic').then(...);
    }
  };
});

This has been supported as of SystemJS 0.20 and is included in the Babel transformer.

@mhegazy If you consider that there never was a pre-ES5 implementation of commonjs, it should be safe to rely specifically on require.length === 1. If it's undefined or otherwise different than 1, you're either running on ES3 (for which there are no commonjs implementations) or on AMD.

@Kovensky you are correct. i was wrong. function.length should be fine to use.

Sorry for bringing this once again, but I didn't really get the reason why unresolved module will end up being any.
My understanding is that a dynamic module loading feature will be used in two major ways:

module specified explicitly as a string literal (in form of module specifier in import from) or string constant expression (or, I'm not sure, as a union of string literal types)

in that case module can be resolved statically and TS can reason about this and give more specific type of the module like it does this for static module binding now
it has very limited set of usage scenarios (I can think of just module splitting with lazy loading)

module specified as a dynamic expression which can be resulted in some string in runtime.

that case, to me, is going to be much common; it covers scenarios where modules are loaded as a result of some runtime module name calculation (plugins, configuration, use demand, ...)
it is common, that a module consumer expects a module with a specific contract and need to perform some duck-type checking to be sure that module is actually what was expected

My claim is that supplying unknown modules with type any would result in too permissive modules.
Moreover, with noImplicitAny there's no legal way to allow such unknown modules and not get "implicit any" error, isn't it? Having {} as a module type would allow type asserting in the way that module consumer needs without possibility to be poisoned by any.

this is already the behavior today, a module that does not exist, but a .js file for it existed is resolved as any. i do not see why this is any different.

I do see, actually. The behavior today assumes the static binding to done where the module specifier is known at compile time. With import, that is by design to have a module specifier to not be known at compile time.
So, to be more practical, it comes up to a question: how can I avoid "implicit any" error under noImplicitAny with a code like this:
const module = await import(dynamicallyReceivedPluginModule);

Ah, you should be able to cast to suppress the noImplicitAny error:
const module = await import(dynamic) as any;

Potentially we could allow import<T>(...) as sugar as well.
Another part of this change would be to enable some sort of syntactic form to express a module shape.. e.g. import (....) as moduleof "./blah". or import<moduleof "./blah">(...).

ok, got it. It may work. Thanks for clarification.

The following seems more natural?
const module: any = await import(dynamic);

That's how I fix "implicitely any" errors when they are intended: by adding the type declaration.

if we assume it is a contextual-type-able then sure.

@Igorbek Thanks for raise your concern. To be clear here, the PR addressing this issue will not involve way to express module shape.... I will open a separate issue where we can devote the entire discussion on how to express such concept

I don't think "blah" should be passed to define as a dependency in the AMD output.

@dasa thanks for catching this. You are correct.

I think using import('blah') with --outFile and --module systemjs should just emit System.import('blah') for migration like #12473. Is this already considered?
// older-namespace.ts
// namespace-based code which will eventually migrate to module-based code
namespace Foo {
  export async function foo() {
    const blah = await import('blah.js'); // should be System.import
  }
}

// blah.ts
// already migrated module
export function blah() {}

Hi guys,
I'm having problems using esnext as a replacement of commonjs that will preserve import for webpack.
This is the issue: https://github.com/Microsoft/TypeScript/issues/16820


Fix re-connect when the connector has an address already

Before, it would deadlock after you refreshed the page when connecting to rainbow. I'm not 100% sure this is the best solution, so input is welcome if you see a better approach.
This way, when you select a network, a previous connection is restored. Also when you disconnect, it immediately clears the connector. Before you had to click it twice for some reason.

Per our DM, I removed the disconnect state interaction, but keep the initialization state capture.


Time scale on workbench don't match up with CVS output

Today, Michael and I tried to use a CSV document of annotations to find where EEB calls were annotated by myself last week, as there is no easy way to search for them in the website without manually re-reviewing spectrograms, or to know what data has been reviewed already on the website. I found that it was quite difficult to use the CSV files to do this, with CVS headings being quite confusing (e.g.  event_start_time_utc and  event_start_datetime_utc appear to be identical), and wondered if there is a headings glossary that users can also download. One thing that might also help marry up the web and CSV times would be to include the hours in the annotation times (hh:mm:ss format rather than mm:ss).  @atruskie @cofiem @jwim1

This issue has been opened in the wrong repository. This is a public repo for programs that cut and convert segments of audio.
Other points:

Searching for annotations? The annotation library is being remade to deal with this
Navigating to them? See the listen_url column
We currently have no concept of reviewing or verification of annotations. This should be discussed as a separately.
RE event_start_time_utc and event_start_datetime_utc: Excel has difficulty reading dates and times in one column. Therefore we have to split them out into separate columns. The split format is annoying for other users so we keep all columns. Open the CSV in notepad++ and you can verify the differences yourself.
The point about hh:mm:ss - full and exact datetimes are included in the files. Excel does not format them properly.
Mark and I are automatically tagged in these issues. Jason does not need to be unless there is some architectural issue to discuss.
Issues are tracking system for bugs/features/work items. Support is still best sourced in an email/chat format.


Start Feature.onDragStart implementation

Following on https://github.com/alex3165/react-mapbox-gl/issues/412

This is a first implementation, to validate strategy.
It need reviews, and help.
Also, I couldn't find some tests about features, so I didn't implemented one (it would need whole bootstrapping and it's way over my knowledge).
I couldn't test it by hand, since I don't get anything to Typescript. Tried to npm run prepublishOnly and npm link it inside my project, but got errors.

Hey @cyrilchapon thanks for helping on this, what do you think about something like this? https://github.com/alex3165/react-mapbox-gl/pull/519/files

I reworked the entire file, cleaned up and implemented onDrag and onDragEnd. Gonna make another PR

(Because the actual implementation also suffered from a bug : when clicking on a feature (anywhere not at the center), it would trigger a onDragEnd (+others) event)


Feature request: Remove 'Spectator' column at battleroom

Spectator condition is already shown in [Status] column on users list, and floating description enhances help on mouse hover.

Also color name/code could be removed and only show the color itself.

Those table columns are for setting the status for players that might not be you. If you want a cleaner view, try the "grouped" players view type in settings.

Checkbox clicking has no effect (at least without admin permissions), and context menu has aleady a !spec option.
I believe it has no much sense this dedicated column.
"grouped" players view type is a very good feature.
Cleaner view for "table" players view can be an enhancement too.


Converting app name to valid PHP class name for compiled container

Codecov Report

Merging #5 (94127bd) into main (3646024) will increase coverage by 0.66%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##              main      #5      +/-   ##
==========================================
+ Coverage     7.78%   8.44%   +0.66%
  Complexity     125     125
==========================================
  Files           18      18
  Lines          411     367      -44
==========================================
- Hits            32      31       -1
+ Misses         379     336      -43

Flag
Coverage Δ

unittests
8.44% <0.00%> (+0.66%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

 Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


cursor following display of candidate words problem

Description of the problem or steps to reproduce
I use the Chinese input method under the win10 console to realize cursor following display of candidate words, but in micro, this window cannot follow the cursor. I've tried a lot of input methods that can't solve this problem, so I guess it needs to be micro.exe Support this feature itself.
Specifications

Commit hash:
OS: win 10
Terminal:cmd

This is difficult for me to try out, and it probably is an issue with the win10 console rather than micro. Do you see this same behavior when typing commands into the win10 console, or when using other text editors in the win10 console?


Introduction of trace_if_false

What are your opinions on introduction of trace_if_false? It's heavily inspired by Plutus but I think it's an important function.
In my opinion, it's important to have traces for each predicate in validator.
It could be an addition in the stdlib like the following:
fn trace_if_false(str: String, res: Bool) {
  if !res {
    trace str
    res
  } else {
    res
  }
}

But I think it adds unnecessary condition in the exported UPLC when having traces off? So maybe it would make more sense to have some keyword on the language level?
This proposal could also be seen in the same bucket for better developer experience https://github.com/aiken-lang/aiken/issues/489#issuecomment-1584305945

Aiken provides this as a built in operator already: https://aiken-lang.org/language-tour/troubleshooting#-operator

@KtorZ yes, I'm aware it's available, but I'm interested in providing custom trace messages, having a trace from the code is not that great IMHO.

@KristianBalaj
you can use aiken/builtin to make your own utility and publish it as a package on github. This then doesn't need to dependent on stdlib.
use aiken/builtin

fn trace_if_false(message: String, expr: Bool) -> Bool {
  if expr {
    expr
  } else {
    builtin.debug(message, expr)
  }
}


Cookies not being set after loginWIthEmailAndPassword

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
The issue is with signingWIthEmaillPassword, its intermittent. Sometimes the cookie is not set and therefore the other calls fail due to no uuid
To Reproduce
login, cookie set, SignOut, login , SignOut, Login, no cookie set
Steps to reproduce the behavior, please provide code snippets or a repository:

Go to '…'
Click on '…'
Scroll down to '…'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System information

OS: [e.g. macOS, Windows]
Browser (if applies) [e.g. chrome, safari]
Version of supabase-js: [e.g. 6.0.2]
Version of Node.js: [e.g. 10.10.0]

Additional context
Add any other context about the problem here.

hello! did you resolve it?

I’m experiencing the same issue. The login is authorized, but after the user is redirected to the home page and I try to fetch user details using auth.getUser, it doesn't return any information about the logged-in user. If you log into another account, sign out, and then log in with a different account, auth.getUser still returns information from the previous account.
Any solution for this?


RDK-30982: PWR MGR refactoring

RDK-30982: PWR MGR refactor changes
Reason for change: refactoring pwrmgr
Test Procedure: Refer to JIRA
Risks: Low

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: akhilsarada:x: rajnishdeyYou have signed the CLA already but the status is still pending? Let us recheck it.


webpack Error: Cannot resolve module 'jQuery'

I'm getting the following errors when running webpack.
ERROR in ./photos/static/js/main.js
Module not found: Error: Cannot resolve module 'jQuery' in /home/bernd/Downloads/django-react-djangocon2015-master/photos/static/js
@ ./photos/static/js/main.js 27:14-31
ERROR in ./photos/static/js/store.js
Module not found: Error: Cannot resolve module 'jQuery' in /home/bernd/Downloads/django-react-djangocon2015-master/photos/static/js
@ ./photos/static/js/store.js 29:14-31
Bernd
BTW: Have you looked into more modern alternatives to jquery ajax?

Hello. I'm not sure why you're getting this error.  Is jquery present in the resulting "node_modules" folder?
I haven't looked into alternatives for jquery to run ajax calls. Would you have some recommendations?
Thanks!

Yes, I did run npm install before attempting the webpack build. I have included the first few lines (truncated) of the output below.
(jphalip)bernd@bernd-freya:~/Downloads/django-react-djangocon2015-master$ npm install
npm WARN package.json @ No repository field.
npm WARN package.json @ No license field.
npm WARN peerDependencies The peer dependency babel-core@* included from babel-loader will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN optional dep failed, continuing<EMAIL_ADDRESS>npm WARN optional dep failed, continuing<EMAIL_ADDRESS><EMAIL_ADDRESS>node_modules/react-render
<EMAIL_ADDRESS>node_modules/uuid
<EMAIL_ADDRESS>node_modules/reflux
├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS>node_modules/jquery
<EMAIL_ADDRESS>node_modules/lodash
As far as ajax without jquery one could use a ployfill for the fetch API (https://github.com/github/fetch) or perhaps a much more powerful but lean library such as superagent (https://github.com/visionmedia/superagent). Both can be installed through npm and should work with webpack.

I noticed that the jQuery folder under node_modules is actually called "jquery" with lower case Q. I changed the import statements in question to this spelling in my local copy and it now works.

@berndca Oh, that's interesting. I suppose it might have worked for me because my OSX partition isn't case sensitive. I'll push a fix, thanks! Thank you also for the ajax tips, I'll look into those.

@berndca  you better
npm install jQuery

instead
npm install jquery

And no need to rename folder names in node_modules


[Win32] t_Co=16 until termguicolors, then t_Co=256

Steps to reproduce
In cmd, powershell, pwsh, or wt on Windows run vim --clean -c "echom 'Before tgc: '.&t_Co | set termguicolors | echom 'With tgc: '.&t_Co | set notermguicolors | echom 'After tgc: '.&t_Co"
:messages contains:
Before tgc: 16
With tgc: 256
After tgc: 256

Expected behaviour
:messages contains:
Before tgc: 256
With tgc: 256
After tgc: 256

Version of Vim
8.2.4014
Environment
OS: Windows 10 Version 10.0.19043.1415
Terminal: ConHost (cmd, powershell, pwsh) or Windows Terminal
$TERM: not set
Logs and stack traces
No response

Note:  A similar/same issue was reported in https://github.com/vim/vim/issues/3432 which appears to have introduced the behavior that t_Co changes when termguicolors is set.  If this behavior is intentional, perhaps it is not an issue.  However, it is surprising to me that t_Co is detected as 16 and more surprising that it changes (permanently) in response to termguicolors.

Also note that both 24-bit gui colors (with termguicolors) and 8-bit colors (with notermguicolors) appear to be displayed correctly.


ZQS-1334: Add COEF_k and PREP

Description

Preparation of the COEF_k and COEF_k_prime quantum states

Implementation of C-PREP unitaries

Please verify that you have completed the following steps

[ ] I have self-reviewed my code.
[ ] I have included test cases validating introduced feature/fix.
[ ] I have updated documentation.

Also, we typically let the reviewer resolve the comments once they see it has been addressed. 😅


convolution should use all image when image is masked

The final convolution leaves masked pixels untouched.
It should use unmasked pixels to calculate the convolution kernel but apply the convolution to all pixels regardless of mask.

The mistake is when dealing with masked arrays.
>>> img = np.array([[1, 2], [3, 4]])
>>> opt_img = np.array([[1, 1], [1, 1]])
>>> opt_imgm = np.ma.array(opt_img, mask=np.array([[True, False], [False, True]]))
>>> img - opt_img
array([[0, 1],
       [2, 3]])
>>> img - opt_imgm
masked_array(data =
 [[-- 1]
 [2 --]],
             mask =
 [[ True False]
 [False  True]],
       fill_value = 999999)
>>> (img - opt_imgm).data
array([[1, 1],
       [2, 4]])

The masked pixels are left untouched.


Open in windows terminal option gone

Windows Terminal version
1.11.3471.0
Windows build number
Microsoft Windows [Version 10.0.22000.556]
Other Software
No response
Steps to reproduce
I literally restored my lappy using the windows resort pc option and opted in for cloud restore. My PC was running slow before that's why. I had this option before when I install win 11 for 1st time. But now it's just plain gone. Went to the registry there was no blocked folder there also under shellextensions.
Expected Behavior
should be able to get the option of Open in windows terminal when I right-click anywhere.
Actual Behavior
the terminal is working fine when I launch from start menu and can add gitbash to the terminal also. But that option to open in windows terminal when we right click on desktop or anywhere is goneright-click.

Does this work if you right click on and actual folder within File Explorer? (not like, on the background of a directory, but on a folder itself)? If so, this might be #11839

Does this work if you right click on and actual folder within File Explorer? (not like, on the background of a directory, but on a folder itself)? If so, this might be #11839

No it was not coming even then. You can see the 1st screenshot I posted in the same issue. I was aware of that issue. I thought this is diff.
https://github.com/microsoft/terminal/issues/11839#issuecomment-1065856908

Hey we made some changes to the way the shell extension tries to find the active directory in the last couple builds - does this work on 1.16 / 1.17 for you/?

 This issue has been marked as requiring author feedback, but hasn't had any activity in the last week. We're gonna close it to tidy up. Feel free to continue the discssion in the comments - we can always reopen if new information comes to light. Thanks!


Update DLPack support

DO NOT MERGE until the upstream is tagged!
The new v0.4 has the following change:

Support complex numbers
Rename the struct DLContext to DLDevice

Prepare for Array API adoption (https://github.com/data-apis/array-api/pull/106).

Upstream is tagged.
Jenkins, test this please

Jenkins CI test (for commit fe4db97c0858099f88959458bff61f40b441244c, target branch master) failed with status FAILURE.

This is ready.

Jenkins, test this please

Jenkins CI test (for commit fe4db97c0858099f88959458bff61f40b441244c, target branch master) failed with status FAILURE.

Jenkins, test this please

Jenkins CI test (for commit fe4db97c0858099f88959458bff61f40b441244c, target branch master) succeeded!


[2.7.x] Backports

@jamesnetherton https://github.com/apache/camel-quarkus/pull/3880 can be backport?

@jamesnetherton #3880 can be backport?

Yeah, seems to be a harmless thing to add. I'll cherry-pick it over.


Horizontal space tidy

Removing the spacing() helper altogether.
We were generating all possible classes to account for 4 x 4 x 2 x 15 possibilities (480), but auditing how we use them revealed that we very rarely use the responsive element for horizontal cases, and the unit is almost always either 6px or 12px.
So replacing the 480 classes with just the 8 that we tend to use seemed to make sense.

After a quick chat with @GarethOrmerod, it looks like the intention is to bring the responsive behaviour that we've applied to the vertical space into the horizontal spacings as well. But this is a far cleaner starting point to work from than what we had before.


Update risk profile logic

Questions in profile seem to vary quite a bit from the security doc they originated from.  Noted the few where this causes issues with the answers for risk levels but could be more than what I saw.  These likely need to be updated to the wording directly from the security document.


Type instantiation is excessively deep and possibly infinite.

hello faced with such a problem with my nextjs13 project and experimental app directory.

Hey Andrew, thanks for reporting this issue. Could please share your whole I18N setup and keys that you pass to it?
Cause from this screen I can't really now what might be the problem and how to reproduce it.

Okay, here is my provider in custom component, where i get the error

here is setup i18n exactly as in the documentation

en keys

ru keys

usually error occurred in the hook "useTranslateBase"
or in the I18NProvider

Yeah, I was able to reproduce this error. I'll look into it more deeply and try to fix tomorrow.
Thanks you very much for reporting an issue!

Seems like with current API and parameters inferring that the library has, it's not possible to fix this issue. It most likely will require some changes not only in typings, but the API itself also.
I'll rollback latest inferring improvements and will try to come up with a better solution to this problem.

I just reverted inferParameterTypes option so that we avoid recursive type checking for now. Will try to think of a better solution, but for now no parameters inferring.


Confirm what happens when we click on the buttons on the Get Involved page

Requirement
Links and reference point to where the various links in the Get Involved page lead to. For example, where does the "Volunteer: tech support" button lead to?
Example Screenshot

Get involved links:
Download the app:  app store links
Volunteer tech support: https://github.com/mapswipe/
Volunteer translation: transifex page
Download tooklit button: link to a google folder (URL to come)
Submit query (for corporates): link to a google form (URL to come)
Tell us more (for orgs): link to a google form (URL to come)
Donate now: https://opencollective.com/mapswipe

Updating to include all links:
Get involved links:
Download the app: app store links
Volunteer tech support: https://github.com/mapswipe/
Volunteer translation: transifex page
Download tooklit button: https://drive.google.com/drive/folders/1j5XnyqI_LKYBCg9oJaaWIKbsBxwB8Cld?usp=drive_link
Submit query (for corporates):https://docs.google.com/forms/d/e/1FAIpQLSf_05ZvC4i7HfDgYqedvsPxG66o8SHMaKs1GpnLC9KVFa4FuQ/viewform?usp=sf_link
Tell us more (for orgs): https://docs.google.com/forms/d/e/1FAIpQLSetcSda6EyuvOXMUPe7Gw7wNNIdR9R9RlvOi1j9Zu-C3ZXtbg/viewform?usp=sf_link
Donate now: https://opencollective.com/mapswipe


[heimdall] Update Heimdall README URL

@radum I know it's super minor, but can you please bump the chart version in Chart.yaml to 1.0.1 for this change?

@billimek Actually this requires a subpath option also. Without it it becomes annoying. I would close this and make that update with this one also.


data-select event dispatched to parent

The chart now dispatches data-select event when clicked to any of the bar chart candles so this one can be handled in the parent

Not exactly sure I understand the value of this change, would mind elaborating a bit or providing some more specific use-cases? Is this something that is frappe-charts specific, or something more Svelte-specific?

Ping @djole87 -- I'm keen to move forward and merge this, I was just hoping to get some more understanding so that I could add proper documentation for this feature. Thanks!

This links to the https://frappe.io/charts/docs/update_state/navigation feature. It could probably used for drill-downs, linking to other pages or similar stuff. I don't really see a reason not to have it.

@JoelEllis thanks for point me to that (I was previously unaware).

@djole87 I've played around with your changes a bit, and it is a bit incomplete. There is no handler given to the on:data-select, and this handler should be a prop so that consumers can hook into this event. In addition, this should be documented in the README.md.
To make this PR complete, please make the following changes:

Add the new prop under the rest, defaulting to a noop: export let onDataSelect = () => {};
Pass that prop to the root element: on:data-select={onDataSelect}
Document how this works in the README.

This is a great change, thanks for finding this. I would love to help get this merged as soon as possible, so let me know if you need a hand, as if you don't respond I may just pick up where you left off.

Hi again! Thanks for looking at this again!
I think the reason no handler is given is an attempt to use the Event Forwarding feature (demo). As far as I'm aware, that should work by default, even with this, although I haven't tested it.
I do agree on adding it to the README though - it's easy to forget about things like that! If you want, I could open a separate PR to do that?
Thanks again!

@JoelEllis thank you for adding documentation. Normally I would request that documentation be added in the same PR as the feature, but that's not reasonable here as you are not the original PR author (sorry, I thought you were the same person as @djole87 when I wrote this comment).


Double click on a word

Hi!
With a Text field, I can't select a word by clicking twice on it as the normal field.
With the plugin:

Without:

Is there a way to enable double click?
Thanks!

Same behavior for me. unfortenetly i can't select any text or url by a double-click.
interestingly I can select everything by clicking on the label of i.e. a text, textarea or url - but only in ff.

Merged #9


how to import all widgets into thingsboard?

Hi
love your collection of widgets!
Any way to import all of them as a widget GROUP to thingsboard instead of manually one by one?
Regards

Added the Widget Bundle in the "Bundle" directory

when importing the Bundle, This error pops up for one of the widgets, not sure which
GET: /api/plugins/telemetry/DEVICE/13814000-1dd2-11b2-8080-808080808080/values/attributes/SERVER_SCOPE
404: OK


image tags do not match between ceph-ansible and cephadm deployments

Bug Report
What happened:
I have deployed a cluster with cephadm and had a look at the image tags deployed, then compared them to ceph-ansible-6.0.3 all.yml and it does not match
What you expected to happen:
matching tags/versions
How to reproduce it (minimal and precise):

Share your group_vars files, inventory and full ceph-ansibe log
$ git status
HEAD detached at v6.0.3
...
$ grep -iR container_image all.yml
#node_exporter_container_image: "docker.io/prom/node-exporter:v0.17.0"
#grafana_container_image: "docker.io/grafana/grafana:6.7.4"
#prometheus_container_image: "docker.io/prom/prometheus:v2.7.2"
#alertmanager_container_image: "docker.io/prom/alertmanager:v0.16.2"
From # ceph orch ps
VERSION NAME
0.20.0 alertmanager.node05
6.7.4 grafana.node04
0.18.1 node-exporter.node01
0.18.1 node-exporter.node02
0.18.1 node-exporter.node03
0.18.1 node-exporter.node04
0.18.1 node-exporter.node05
2.18.1 prometheus.node01
Environment:
ceph version
ceph version 16.2.0 (0c2054e95bcd9b30fdd908a79ac1d8bbc3394442) pacific (stable)
cat /etc/centos-release
CentOS Linux release 8.3.2011
cephadm version
Using recent ceph image docker.io/ceph/ceph@sha256:030e84addad8f3a7d26ea49b180660f1a9b33ef06d691759f320a58e892fb535
ceph version 15.2.10 (27917a557cca91e4da407489bbaa64ad4352cc02) octopus (stable)

That's expected.
ceph-ansible and cephadm aren't two different tools two with different default values.
If you want to use the same container image tag than cephadm then you can still override the ceph-ansible default values.


Wild-IR not working as expected

Hello. I just checked out the updated implementation of Wild-IR and test the output by running app.py  in universal-image-restoration/config/wild-ir, and I have made sure that I placed the pretrained models in right paths and no errors were thrown during the gradio app was running. However, the output images are all in the same size as the input images and the quality was remained unchanged. The related opt file  inference.yaml and code in models directory only supports denoising model rather than SR model.
According to all clues mentioned above, I wonder if the Wild-IR implementation in this repo is still not working as intended (not the same as the impressive results shown in the paper). I would appreciate more helpful information from you.

Hi! The current Wild-IR model only supports normal image restoration (denoising, deblurring, dejpeg...) where the LQ and HQ images have the same size. If you want to perform super-resolution you can try to resize the LQ image before feeding it to the model.


v0.17.0-alpha2 doesn't serve on 443

headscale serve does not serve anything on port 443 in version v0.17.0-alpha2
ss -tpln output only shows port :80 being used.
LISTEN 0      4096               *:80              *:*    users:(("headscale",pid=2234,fd=10))

If you use v0.17.0-alpha1 everything seems to be working as expected. At least I was able to register a new node with out issue.
ss -tpln output when running v0.17.0-apha1
LISTEN 0      4096       <IP_ADDRESS>:9090       <IP_ADDRESS>:*    users:(("headscale",pid=1830,fd=11))
LISTEN 0      4096               *:80               *:*    users:(("headscale",pid=1830,fd=14))
LISTEN 0      4096               *:443              *:*    users:(("headscale",pid=1830,fd=10))
LISTEN 0      4096               *:50443            *:*    users:(("headscale",pid=1830,fd=9))

Both server and client are Ubuntu 22.04.
I'm a new user of headscale so it's possible I don't have something configured properly. This seems unlikely though as v0.17.0-alpha1 works and alpha2 does not.

Can you paste here your config?

I don't change the config between switching versions:
grab example config from git repo and save as config.yaml and modify keys: server_url, tls_letsencrypt_hostname, acme_email
---
server_url: https://vpn2.example.com:443
listen_addr: <IP_ADDRESS>:8080
metrics_listen_addr: <IP_ADDRESS>:9090
grpc_listen_addr: <IP_ADDRESS>:50443
grpc_allow_insecure: false
private_key_path: /var/lib/headscale/private.key
noise:
  private_key_path: /var/lib/headscale/noise_private.key
ip_prefixes:
  - fd7a:115c:a1e0::/48
  - <IP_ADDRESS>/10
derp:
  server:
    enabled: false
    region_id: 999
    region_code: "headscale"
    region_name: "Headscale Embedded DERP"
    stun_listen_addr: "<IP_ADDRESS>:3478"
  urls:
    - https://controlplane.tailscale.com/derpmap/default
  paths: []
  auto_update_enabled: true
  update_frequency: 24h
disable_check_updates: false
ephemeral_node_inactivity_timeout: 30m
node_update_check_interval: 10s
db_type: sqlite3
db_path: /var/lib/headscale/db.sqlite
acme_url: https://acme-v02.api.letsencrypt.org/directory
acme_email<EMAIL_ADDRESS>tls_letsencrypt_hostname: "vpn2.example.com"
tls_client_auth_mode: relaxed
tls_letsencrypt_cache_dir: /var/lib/headscale/cache
tls_letsencrypt_challenge_type: HTTP-01
tls_letsencrypt_listen: ":http"
tls_cert_path: ""
tls_key_path: ""
log_level: info
acl_policy_path: ""
dns_config:
  nameservers:
    - <IP_ADDRESS>
  domains: []
  magic_dns: true
  base_domain: example.com
unix_socket: /var/run/headscale.sock
unix_socket_permission: "0770"
logtail:
  enabled: false
randomize_client_port: false

root@localhost:/etc/headscale# headscale serve
An updated version of Headscale has been found (0.17.0-alpha2 vs. your current v0.17.0-alpha1). Check it out https://github.com/juanfont/headscale/releases
2022-09-07T23:54:24Z INF No private key file at path, creating... path=/var/lib/headscale/private.key
2022-09-07T23:54:24Z INF No private key file at path, creating... path=/var/lib/headscale/noise_private.key
2022-09-07T23:54:24Z INF Enabling remote gRPC at <IP_ADDRESS>:50443
2022-09-07T23:54:24Z INF listening and serving gRPC on: <IP_ADDRESS>:50443
2022-09-07T23:54:24Z INF listening and serving HTTP on: <IP_ADDRESS>:8080
2022-09-07T23:54:24Z INF listening and serving metrics on: <IP_ADDRESS>:9090
2022-09-07T23:54:24Z INF Setting up a DERPMap update worker frequency=86400000
2022-09-07T23:55:11Z INF Received signal to stop, shutting down gracefully signal=interrupt
2022-09-07T23:55:11Z INF Headscale stopped

root@localhost:/etc/headscale# headscale version
v0.17.0-alpha2
root@localhost:/etc/headscale# rm -r /var/lib/headscale/* /var/run/headscale.sock
root@localhost:/etc/headscale# headscale serve
2022-09-07T23:58:06Z INF No private key file at path, creating... path=/var/lib/headscale/private.key
2022-09-07T23:58:06Z INF No private key file at path, creating... path=/var/lib/headscale/noise_private.key
2022-09-07T23:58:07Z INF Setting up a DERPMap update worker frequency=86400000

Hello, you need change tls_letsencrypt_challenge_type from HTTP-01 to TLS-ALPN-01, or use existing certificate with options tls_cert_path: "" and tls_key_path: "". It's a bug (

I was able to successfully start headscale using v0.17.0-alpha2 following your instructions.

Set tls_letsencrypt_challenge_type:  TLS-ALPN-01.
headscale version then complained about listen_addr needing to be set to :443
listen_addr: <IP_ADDRESS>:8080 -> listen_addr: <IP_ADDRESS>:443

root@localhost:/etc/headscale# headscale version
v0.17.0-alpha2
root@localhost:~# headscale serve
2022-09-08T11:28:06Z INF Enabling remote gRPC at <IP_ADDRESS>:50443
2022-09-08T11:28:06Z INF listening and serving gRPC on: <IP_ADDRESS>:50443
2022-09-08T11:28:06Z INF listening and serving HTTP on: <IP_ADDRESS>:443
2022-09-08T11:28:06Z INF listening and serving metrics on: <IP_ADDRESS>:9090
2022-09-08T11:28:06Z INF Setting up a DERPMap update worker frequency=86400000

It looks like there is no service running port 80. I assume that has to do with using TLS-ALPN-01.
root@localhost:~# ss -tpln|grep headscale
LISTEN 0      4096       <IP_ADDRESS>:9090       <IP_ADDRESS>:*    users:(("headscale",pid=4623,fd=14))
LISTEN 0      4096               *:443              *:*    users:(("headscale",pid=4623,fd=13))
LISTEN 0      4096               *:50443            *:*    users:(("headscale",pid=4623,fd=12))

I was then able to register two machines using the tailscale client who can ping each other. :)

Good to know that there is a workaround; too bad I cannot put Headscale on 443 here.

I possibly seem to be hitting this issue:
I've noticed what appears to be a regression between 0.17-alpha1 and 0.17-alpha2/alpha3.
Specifically - with 0.17-alpha1 - headscale is listening on the specified ports in the configuration file (e.g. 8080, 50443 etc.) as expected:
victorhooi@headscale-test:~$ sudo netstat -tunlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 <IP_ADDRESS>:22              <IP_ADDRESS>:*               LISTEN      475280/sshd: /usr/s
tcp        0      0 <IP_ADDRESS>:9090          <IP_ADDRESS>:*               LISTEN      721302/headscale
tcp6       0      0 :::80                   :::*                    LISTEN      721302/headscale
tcp6       0      0 :::8080                 :::*                    LISTEN      721302/headscale
tcp6       0      0 :::22                   :::*                    LISTEN      475280/sshd: /usr/s
tcp6       0      0 :::50443                :::*                    LISTEN      721302/headscale
udp        0      0 <IP_ADDRESS>:68              <IP_ADDRESS>:*                           383/dhclient
udp        0      0 <IP_ADDRESS>:323           <IP_ADDRESS>:*                           22697/chronyd
udp6       0      0 ::1:323                 :::*                                22697/chronyd
victorhooi@headscale-test:~$

Here is the startup console output as well:
An updated version of Headscale has been found (0.17.0-alpha3 vs. your current v0.17.0-alpha1). Check it out https://github.com/juanfont/headscale/releases
2022-09-22T07:40:15Z INF Setting up a DERPMap update worker frequency=86400000
2022-09-22T07:40:15Z INF Enabling remote gRPC at <IP_ADDRESS>:50443
2022-09-22T07:40:15Z INF listening and serving gRPC on: <IP_ADDRESS>:50443
2022-09-22T07:40:15Z INF listening and serving HTTP on: <IP_ADDRESS>:8080
2022-09-22T07:40:15Z INF listening and serving metrics on: <IP_ADDRESS>:9090
2022-09-22T07:40:18Z INF The HTTP2 server was closed error=EOF
2022-09-22T07:40:18Z INF ../runner/work/headscale/headscale/protocol_common.go:677 > Machine successfully refreshed machine=Victors-MacBook-Pro-2 node_key=[bQLA7] noise=true old_node_key=[PgiEl]
2022-09-22T07:40:18Z INF Client is starting up. Probably interested in a DERP map handler=PollNetMap machine=Victors-MacBook-Pro-3 noise=true
2022-09-22T07:40:18Z INF Client is starting up. Probably interested in a DERP map handler=PollNetMap machine=Victors-MacBook-Pro-3 noise=true

However, with 0.17-alpha2 and 0.17-alpha3 and the same configuration file - it does not appear to be listening on those ports anymore:
victorhooi@headscale-test:~$ sudo netstat -tunlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 <IP_ADDRESS>:22              <IP_ADDRESS>:*               LISTEN      475280/sshd: /usr/s
tcp6       0      0 :::80                   :::*                    LISTEN      721251/headscale
tcp6       0      0 :::22                   :::*                    LISTEN      475280/sshd: /usr/s
udp        0      0 <IP_ADDRESS>:68              <IP_ADDRESS>:*                           383/dhclient
udp        0      0 <IP_ADDRESS>:323           <IP_ADDRESS>:*                           22697/chronyd
udp6       0      0 ::1:323                 :::*                                22697/chronyd

and the startup console lines:
victorhooi@headscale-test:~$ sudo headscale serve
2022-09-22T07:28:51Z DBG Loading DERPMap from path func=GetDERPMap url=https://controlplane.tailscale.com/derpmap/default
2022-09-22T07:28:51Z INF Setting up a DERPMap update worker frequency=86400000

I'm just trying to understand the workaround - does this mean we need to change the configured port from 8080 to 443 as well?

I think this was a result of a refactoring, can some of you try https://github.com/juanfont/headscale/pull/831.

This fix is now in 0.17 alpha 4, please give it a go.


Fix typo: languaue => language

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@47b4bbe). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #38   +/-   ##
=========================================
  Coverage          ?   78.65%
=========================================
  Files             ?       11
  Lines             ?     1148
  Branches          ?        0
=========================================
  Hits              ?      903
  Misses            ?      181
  Partials          ?       64

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 47b4bbe...b2b2a24. Read the comment docs.


Wait till all helm release resources deleted when doing helm purge from werf

Autopurge installed failed release should wait till resources gone. Leads to error:

Error: release alo-alo failed: object is being deleted: persistentvolumeclaims "psql-data" already exists`!

werf dismiss command should also wait till all release resources (and optionally namespace) are gone.

Implemented.


Assertion Error: Coverage Attention Needs to be Set

We have tried training this model following all the instructions on the page, but are running into the following error at the training step. We hope you can give us some tips to fix this error (we have tried different ways to do so, but to no avail):
Traceback (most recent call last):
File "train.py", line 6, in
main()
File "/content/drive/My Drive/data-to-text-hierarchical-master/onmt/bin/train.py", line 204, in main
train(opt)
File "/content/drive/My Drive/data-to-text-hierarchical-master/onmt/bin/train.py", line 88, in train
single_main(opt, 0)
File "/content/drive/My Drive/data-to-text-hierarchical-master/onmt/train_single.py", line 98, in main
opt, device_id, model, fields, optim, model_saver=model_saver)
File "/content/drive/My Drive/data-to-text-hierarchical-master/onmt/trainer.py", line 35, in build_trainer
train_loss = onmt.utils.loss.build_loss_compute(model, tgt_field, opt)
File "/content/drive/My Drive/data-to-text-hierarchical-master/onmt/utils/loss.py", line 30, in build_loss_compute
assert opt.coverage_attn, "--coverage_attn needs to be set in "
AssertionError: --coverage_attn needs to be set in order to use --lambda_coverage != 0
Would really appreciate some help with this. Thank you

Hi,
I think setting --lambda_coverage 0 will fix this issue.
If you're using the config file provided at the root of the repo, change line 71 to lambda_coverage: 0 or simply remove it (default is 0).
I advise to use the training config file from Craig Thomson, where the correct hyperparameter is used (the file is named train_htransformer.cfg).
After closing this issue, I'll replace the root config file with this one, so a simple git pull should work.
Let me know if this doesn't solve your issue, in which case feel free to re open.


Update set-value to fix CVE-2019-10747

This PR fixes CVE-2019-10747
For future reference, I read about a way to make this process a lot easier: You can add a "resolutions" section to package.json with any minimum version requirements for transitive dependencies, in this case:
  "resolutions": {
    "set-value": ">= 2.0.1"
  },

and then run yarn install and yarn will update yarn.lock to honor those requirements for you, or warn you if it can't. The package doesn't need to be a direct dependency for this to work. ~And after yarn.lock has been updated, you might as well remove it from package.json again before you commit, to keep the amount of clutter down.~ 👈 that last bit didn't work, it allowed the 0.x version back in

@tdonohue I noticed that as well, but those missing scores seem to have come in now. Perhaps their servers couldn't cope?


conversion to tabix file sometimes failing

Issue:
Original summary stats file ( /project/farber_lab/will/echolocatoR/echo_bmd_FINAL.tsv.gz) gets overwritten with an empty file when running on HPC.
Potential source
Not being able to find bgzip and/or zcat executables during:
"( zgrep 'CHR' /project/farber_lab/will/echolocatoR/echo_bmd_FINAL.tsv.gz; zgrep -v ^'CHR' /project/farber_lab/will/echolocatoR/echo_bmd_FINAL.tsv.gz | sort -k1,1 -k2,2n ) | bgzip > /project/farber_lab/will/echolocatoR/echo_bmd_FINAL.tsv.gz"
Potential solution:
Explicitly call bgzip/zcat using full path to conda env executable.
Slurm error message:
Registered S3 method overwritten by 'GGally':
  method from
  +.gg   ggplot2
[1] "+ Assigning gene_col and locus_col independently"
       Locus      Gene CHR       POS         SNP           P       Effect
1:   5S_rRNA   5S_rRNA  23 150229408   rs5925496 0.036154500 -0.003934910
2:    61E3.4    61E3.4  16  21841448 rs181722413 0.100000000 -0.064257900
3:       7SK       7SK  23 137222166   rs1594214 0.000473012  0.008040440
4: A-575C2.4 A-575C2.4  16  28647605 rs574951226 0.100000000  0.038680500
5:      A1BG      A1BG  19  58863449   rs4801579 1.000000000  0.000358687
6:      A1CF      A1CF  10  52617099 rs531994296 0.100000000  0.024644900

)   )  ) ))))))}}}}}}}} {{{{{{{{{(((((( (  (   (
A1BG (1 / 2)
)   )  ) ))))))}}}}}}}} {{{{{{{{{(((((( (  (   (
[1] "+ Extracting relevant variants from fullSS..."
[1] "+ Query Method: tabix"
[1] "+ QUERY: Chromosome = 19 ; Min position = 57863449 ; Max position = 59863449"
[1] "TABIX:: Converting full summary stats file to tabix format for fast querying..."
[1] "( zgrep 'CHR' /project/farber_lab/will/echolocatoR/echo_bmd_FINAL.tsv.gz; zgrep -v ^'CHR' /project/farber_lab/will/echolocatoR/echo_bmd_FINAL.tsv.gz | sort -k1,1 -k2,2n ) | bgzip > /project/farber_lab/will/echolocatoR/echo_bmd_FINAL.tsv.gz"
[1] "+ CONDA:: Identified tabix executable in echoR env."
[1] "TABIX:: Indexing"
[1] "/sfs/qumulo/qhome/wr8yp/.conda/envs/echoR/bin/tabix -f -S 1 -s 1 -b 2 -e 2 /project/farber_lab/will/echolocatoR/echo_bmd_FINAL.tsv.gz"
Error in data.table::fread(file_path, nrows = 0, header = T) :
  File is empty: /tmp/Rtmp25KA9t/file6c8a19dc4c5b
Fine-mapping complete in:
Time difference of 14.3 secs

)   )  ) ))))))}}}}}}}} {{{{{{{{{(((((( (  (   (
A1CF (2 / 2)
)   )  ) ))))))}}}}}}}} {{{{{{{{{(((((( (  (   (
[1] "+ Extracting relevant variants from fullSS..."
[1] "+ Query Method: tabix"
[1] "+ QUERY: Chromosome = 10 ; Min position = 51617099 ; Max position = 53617099"
[1] "TABIX:: Existing indexed tabix file detected"
Error in data.table::fread(file_path, nrows = 0, header = T) :
  File is empty: /tmp/Rtmp25KA9t/file6c8a533e796c
Fine-mapping complete in:
Time difference of 0.1 secs
[1] "+ Identifying Consensus SNPs..."
[1] "++ support_thresh = 2"
[1] "++ top_CS_only=FALSE"
[1] "+ Calculating mean Posterior Probability (mean.PP)..."
Error in `[.data.table`(x, r, vars, with = FALSE) :
  column(s) not found: SNP
Calls: finemap_loci ... eval -> subset -> subset.data.table -> [ -> [.data.table
Execution halted

When running system from within Rstudio, it’s not always great at finding the package where bgzip is. I think I fixed this previously by making echolocatoR search for the bgzip executable withint the selected conda env, but there was likely still a residual empty file called “echo_head.tsv.gz”, which tricks echolocatoR into thinking the bgzipped file is good to go. I’ve added some new safeguards against this, including adding the “-f” flag to bgzip (which will overwrite any previous empty files), and detecting the file.size of the “.gz” file. If its size==0 then echolocatoR will delete it and then proceed.
I have also found out a weird trick where opening Rstudio via command line after activating the environment can help Rstudio to find paths to packages within that env. I’ve added this note to to the Readme documentation.


[@triniwiz/nativescript-image-cache-it] Build fails after updating XCode to 14.3 - could not build Objective-C module 'SDWebImage'

...
1 warning generated.
<module-includes>:1:9: note: in file included from <module-includes>:1:
#import "Headers/SDWebImage-umbrella.h"
        ^
/Users/dmytrovepretskyi/Desktop/seesnap-2/nativescript-app/platforms/ios/build/Debug-iphonesimulator/SDWebImage/SDWebImage.framework/Headers/SDWebImage-umbrella.h:57:9: note: in file included from /Users/dmytrovepretskyi/Desktop/seesnap-2/nativescript-app/platforms/ios/build/Debug-iphonesimulator/SDWebImage/SDWebImage.framework/Headers/SDWebImage-umbrella.h:57:
#import "SDWebImagePrefetcher.h"
        ^
/Users/dmytrovepretskyi/Desktop/seesnap-2/nativescript-app/platforms/ios/build/Debug-iphonesimulator/SDWebImage/SDWebImage.framework/Headers/SDWebImagePrefetcher.h:92:1: error: property with 'retain (or strong)' attribute must be of object type
@property (strong, nonatomic, nonnull) dispatch_queue_t delegateQueue;
^
/Users/dmytrovepretskyi/Desktop/seesnap-2/nativescript-app/node_modules/@triniwiz/nativescript-image-cache-it/platforms/ios/src/ImageCacheItUtils.swift:10:8: error: could not build Objective-C module 'SDWebImage'
import SDWebImage
       ^
...
** BUILD FAILED **

Unable to apply changes on device: 39EDFAD2-BE45-4EA6-BCC5-5AEA734A5DA6. Error is: Command xcodebuild failed with exit code 65.

Same thing if I try to build in XCode

I updated the "@triniwiz/nativescript-image-cache-it" plugin to the latest 7.3.0
ns doctor returns this:
No issues were detected.
✔ Your ANDROID_HOME environment variable is set and points to correct directory.
✔ Your adb from the Android SDK is correctly installed.
✔ The Android SDK is installed.
✔ A compatible Android SDK for compilation is found.
✔ Javac is installed and is configured properly.
✔ The Java Development Kit (JDK) is installed and is configured properly.
✔ Xcode is installed and is configured properly.
✔ xcodeproj is installed and is configured properly.
✔ CocoaPods are installed.
✔ CocoaPods update is not required.
✔ CocoaPods are configured properly.
✔ Your current CocoaPods version is newer than 1.0.0.
✔ Python installed and configured correctly.
✔ The Python 'six' package is found.
✔ Xcode version 14.3.0 satisfies minimum required version 10.
✔ Getting NativeScript components versions information...
⚠ Update available for component nativescript. Your current version is 8.4.0 and the latest available version is 8.5.2.
✔ Component @nativescript/core has 8.5.0 version and is up to date.
✔ Component @nativescript/ios has 8.5.1 version and is up to date.
✔ Component @nativescript/android has 8.5.0 version and is up to date.

Before the XCode update, everything was working perfectly fine

After updating the NativeScript CLI to 8.5.3 I was able to build for iOS. This issue can be closed. Thanks, @edusperoni !


Define library in EntryObject does not give the same output than define library in output

Bug report

What is the current behavior?
If I define the library in the EntryObject or  in the Output with JQuery in externals it does not give the same output. Indeed, Jquery is not define or require anymore when library is defined in EntryObject.
If the current behavior is a bug, please provide the steps to reproduce.

Find a reproductive example here and clone the repo.

Check the bundled file in the dist, you will have something like that:

(function webpackUniversalModuleDefinition(root, factory) {
	if(typeof exports === 'object' && typeof module === 'object')
		module.exports = factory(require("jQuery"));
	else if(typeof define === 'function' && define.amd)
		define("library/example", ["jQuery"], factory);
	else if(typeof exports === 'object')
		exports["library/example"] = factory(require("jQuery"));
	else
		root["library"] = root["library"] || {}, root["library"]["example"] = factory(root["jQuery"]);
})(self, function(__WEBPACK_EXTERNAL_MODULE_jquery__) {

Uncomment the library property in the entry.example and comment the library property in the output.
Run webpack.
Check the bundled file in the dist, you will have something like that:

(function webpackUniversalModuleDefinition(root, factory) {
	if(typeof exports === 'object' && typeof module === 'object')
		module.exports = factory();
	else if(typeof define === 'function' && define.amd)
		define("library/example", [], factory);
	else if(typeof exports === 'object')
		exports["library/example"] = factory();
	else
		root["library"] = root["library"] || {}, root["library"]["example"] = factory();
})(self, function() {

As you can see there is no more JQuery in the bundle file.

What is the expected behavior?
We should have the same bundle file.

Other relevant information:
webpack version:  5.64.4
Node.js version: 14.17.5
Operating System: Windows 10
Additional tools:

When externals do not explicitly specified a type of external, they will use the externalsType type, which defaults to output.library.type.
By not specifying output.library.type you are basically switching the externals to a different type. From amd to var. So they no longer appear in the amd library.
Either set externalsType: "amd" or externals: { jquery: "amd jQuery }`

Thanks it works !


strange error and debug info for the plugin?

I am using 5.1.1 ELK stack and using output_jdbc plugin to update Oracle 12c about the status of the ETL.
I have a strange error:
I have 10 Oracle inputs (input_jdbc plugin) and 1 output to the same Oracle server. The output updates 10 records in the status table. But if I use only 1 output, not all 10 records get updated. (I have outputs to ES and were all successful). Strange thing is that if I single out those not updated one and setup another output for it and it is successful.
Input{
jdbc 1{}
..
jdbc 10 {}
}
Output
{
if done {  -- condition when 1 input finishes
jdbc 1{}
}
}
This config fail for some say 4, 8,9,10
This config works:
input{
jdbc 1{}
..
jdbc 10 {}
}
Output
{
if done {
if [type] =~ "^?[4,8,9,0]{1}$" { --pick out those having problem and handle it separately
jdbc 1{}
} else {
jdbc 2 {}
}
}
}
How can this be happening? 1 and 2 are identical. Any setting that I need to add? (ojdbc6.jar or odjbc7.jar behave the same)  to make the first config works?
BTW, the plugin does not have any debug/info output. Like the SQL statement etc. Can this be added?
Thanks

I can't think of a reason why this would happen off the top of my head.. I'd guess either the plugin is retrying and failing - but it should eventually log that it failed after however many attempts you've configured it for (10 by default).
Is there any possibility you can run the problem configuration with the logstash --debug flag, and try and make the problem happen? That should put logstash-output-jdbc and HikariCP (a component the plugin uses) into a very spammy mode, and should give you some SQL errors. If you can copy the log into here, it would be very very helpful.
With regards to the debug info for the sql statement, the plugin runs a prepared statement of what you give it (unless you're using the unsafe_statement option, I suppose), meaning it would just output whats in the config, the event. I usually just use stdout { codec => rubydebug } if I absolutely have to.

I did turn on the debug and did not see any error.(Plugin did not show SQL, so I do not know if it got executed, I just know ES output got there.  That is why I want to you add SQL before execution as INFO so that I will know if the SQL got executed or not.)
I did not use unsafe-statement option.
Here is the entire log from start to shutdown, running 10(+2 start and stop) and 1 output(+1 concluding output). Updating 2 tabes. Table 2 is status table:(Result is append to the end of the log)
Notice that 4,8,9,10 status is still "P" but everything is completed.  Strange.
logstash-plain.txt

@theangryangel
The problem is because I am using aggregate filter and tried to detect the 1st and last record. When there is only one aggregate. My output detect it as 1st record and change the status to "P", but it also is the last record and tried to set it to "C". This caused conflict I guess. (But there are 2 jdbc outputs, one for 1st and one for last). Currently I detect 1st record using the original event and not the aggregate event and it works fine.
But the problem is still strange. Why there is such behavior? When I make a 3rd jdbc output for the last, it works fine also.
The output plugin seems to set the pool at full size and not incremental. Can this be changed? If I have 5 outputs, and the default pool size is 24. I am having 120 connections in the DB. Could this be set at say 2 and increment by say 4 till max?
One side question: How can I use Time.Now.strfmt(....) as Statemtment parameter?
statement =>["select * from tab where date=?",Time.now.strfmt(...)]
This syntax is ok with the config, but not work when executing in the plugin.

I'm sorry @iti888, but I've just not had the time yet to think about this problem, let alone try and actually figure it out.

But the problem is still strange. Why there is such behavior? When I make a 3rd jdbc output for the last, it works fine also.

I honestly don't really understand exactly what you're trying to do. Can you give me the exact, or very close configuration... I have the feeling this is more of a configuration error than a plugin problem.

One side question: How can I use Time.Now.strfmt(....) as Statemtment parameter?

You can't... Logstash doesn't execute the configuration as if it's ruby (except for one plugin). I'd personally suggest using something like CURRENT_TIMESTAMP, or sys_extract_utc(SYSTIMESTAMP) in your sql. i.e. statement =>["select * from tab where date=sys_extract_utc(SYSTIMESTAMP)"]
If you absolutely have to use Time.Now.strfmt, then your only option is to use the ruby filter to add a field to the event. Something like this might work (i've not tested this):
ruby { code => "event.set("new_timestamp", Time.Now.strfmt(...)" }

I tested again. It is scheduling/timing problem. There are 2 job trying to update the same record, but they are different connections, which caused the issue.
As for Time.Now.strfmt(....), I just figured out how to do it without adding a field. It is strange howthe plugin treated the Statement parameter:
UPDATE table  ts_field=to_timestamp(?,'yyyy-mm-dd HH24:MI:SS.ff3') will work with parameter "@timestamp" but not "%{@timestamp}".
"%{@timestamp}" has a format  'yyyy-mm-dd"T"HH24:MI:SS.ff3"Z"'
while "@timestamp" has a format of 'yyyy-mm-dd HH24:MI:SS.ff3'
also ["UPDATE table  ts_field=to_timestamp(?,'yyyy-mm-dd"T"HH24:MI:SS.ff3"Z"')...", "%{@timestamp}"] does not cause config or runtime error.
But from Oracle DB side. The Escape "" was in the formating string. So, it failed. How do you make this to work?

Welcome to the wonderful world of logstash.
https://logstash.jira.com/browse/LOGSTASH-1377 has been open since 2013 about quoting problems in configurations.
The problem is that JDBC drivers have given us issues in the past for timestamps, as drivers all seem to work differently for setting timestamps.
According to https://github.com/theangryangel/logstash-output-jdbc/blob/master/examples/oracle.md josemazo had success using CAST(? as timestamp), with @timestamp.
I'm afraid I don't use Oracle and I'm not going to have time to install and investigate myself for a while.

Looks like I just cannot use " to escape double quote. (but Oracle time formatting needs that:) )
As for @timestamp. My confusion is why "@timestamp" and "%{@timestamp}" is different. Isn't one is the field itself and the other is string of the field? How does the plugin passing the parameter to the SQL? (Convert to string and pass or JDBC is doing the conversion?)

When you use @timestamp the plugin converts it to a string. The reason is explained in https://github.com/theangryangel/logstash-output-jdbc/blob/master/lib/logstash/outputs/jdbc.rb#L277 - but basically some JDBC drivers correctly support setTimestamp whereas others dont.
The reason why %{@timestamp} is different is because that %{} is logstash itself converting the timestamp to a string, and using a slightly different format. The reason why I use a different formatting string is because a different SQL engine failed to support logstash's format.
Ways forward at this point:

I can add a configuration parameter that governs the format that the string gets converted to, allowing you to configure it differently
I can add a configuration parameter that tells the plugin to use setTimestamp instead of setString

I was just wondering the inconsistency of formatting. As long as there is somekind of documentation saying the @timestamp parameter is treating differently as "@timestamp" or "%{@timestamp}". That is enough. I have to go a long way to find this out. (Because I can not use double quote. I have to convert the Time.now using strfmt(..) to a new field in the EVENT and pass as a parameter. Then I found "@timestamp" works exactly the same as what I was formatting.)


core: make import_image_tags handle 504 errors

Fixes OSBS-8448
import_image_tags is encountering 504 errors on RHEL7 because urllib3 isn't retrying them properly. add a new retry_on_gateway_timeout function and wrap _check_import_image_response in it.
Also, unify some of the associated handling of _check_image_image_response and rename it
_get_import_image_response_tags
Signed-off-by: Mark Langsdorf<EMAIL_ADDRESS>Maintainers will complete the following section:

[x] Commit messages are descriptive enough
[x] "Signed-off-by:" line is present in each commit
[x] Code coverage from testing does not decrease and new code is covered
[x] JSON/YAML configuration changes are updated in the relevant schema
[x] Changes to metadata also update the documentation for the metadata
[x] Pull request includes link to an osbs-docs PR for user documentation updates

Commit message updated.

Added to release notes under Bug Fixes

import_image retries on 504 errors to work around a Python network library bug in RHEL7


Node PID limiting

Reference https://github.com/kubernetes/kubernetes/pull/73651

@RobertKrawitz it appears this doc is ready to review, can you confirm? Also, can I get a technical lgtm?

This is ready to review.  @derekwaynecarr @dashpole could you provide the lgtm?

/lgtm

Just a note: the generated docs will be overwritten, but it appears you updated the actual package in k/k so it will get pulled in next generation. Thanks!
/lgtm
/approve


Remove outdated link

Flannel combained RBAC info into main manifest [1].
[1] https://github.com/coreos/flannel/commit/a154d2f68edd511498c948e33c8cbde20a5901ee

This change is

FYI, one solution proposed in another PR (https://github.com/kubernetes/kubernetes.github.io/pull/5588) is to pin the links to a specific version.

This PR will be applicable when Kubernetes starts to use/test/install flannel 0.9.x, which is the current version in master.
https://github.com/kubernetes/kubernetes.github.io/pull/5588 should be most accurate for what ships in 1.8.

So, we should merge this PR into master now, and move #5588 into the release-1.8 branch?


Add CLI  for quick and easy feature extraction

I think a CLI would be a nice addition to the library for quickly extracting features without having to write a python script / making the library even easier to use.
E.g. just being able to do thingsvision extract --image_dir <path/to/images> --model_name <...> --source <...> --modules <module1> <...> --output_dir <path/to/out_dir> and thingsvision show_modules --model_name <...> --source <...> would be nice.

Have recently done similar, can add this to the library.


Improve ember-inspector integration

[ ] Add in-element case https://github.com/glimmerjs/glimmer-vm/pull/1560
[ ] Add `modifiers case https://github.com/glimmerjs/glimmer-vm/pull/1559 https://github.com/emberjs/ember-inspector/pull/2548/files
[ ] Add rendered slots
[ ] Add rendered helpers?
[ ] tracked deps https://github.com/emberjs/ember-inspector/pull/2546/files

https://discord.com/channels/480462759797063690/1204116134236790835/1204423436051677224

ember_debug.js:6054 failed to setup in element support Error: Module: '@glimmer/runtime' not found.
at requireModule (ember-inspector.ts:575:13)
at InElementSupportProvider.require (ember_debug.js:6028:39)
at new InElementSupportProvider (ember_debug.js:5907:27)
at new RenderTree (ember_debug.js:6052:33)
at _class.init (ember_debug.js:10517:42)
at new BaseObject (ember_debug.js:9660:12)
at new _default (ember_debug.js:813:7)
at new _class (ember_debug.js:10508:3)
at EmberDebug.startModule (ember_debug.js:7318:20)
at ember_debug.js:7347:14


Zen mode does not exit when leaving fullscreen after restart

Steps to Reproduce:

go fullscreen
enable zen mode
quit
leave fullscreen

=> 🐛 zen mode is not exit because zenModeExitInfo.transitionedToFullScreen is not remembered correctly between restarts

Hi @bpasero,
If I understand correctly, I presume this is a bug because zen mode should only be enabled in fullscreen. When attempting to reproduce the bug, I noticed that step 3, quit, was not necessary to cause the bug. When I went fullscreen, enabled zen mode, then left fullscreen, I was still left in zen mode despite fullscreen being disabled. If you can confirm my understanding of the bug, then my partner @ldaanish and I would be happy to begin addressing this issue.
Thank you!


dev: use only reth_primitives and reth_rpc_types types

Time spent on this PR:

Closes #87 and closes #73
Pull Request type
Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[x] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Testing
[ ] Other (please describe):

What is the current behavior?
Some types were imported from reth_primitives and others from reth_primitives::rpc.
reth_primitives::rpc are types imported from ethers-rs.
What is the new behavior?
We now use :
-reth_rpc_types module for rpc types

reth_primitives module for type dependencies

Does this introduce a breaking change?

[x] Yes
[ ] No

There were some differences between custom types from types.rs and reth_rpc_types
Other information
There is still an issue with Log. Currently Log imported from reth_rpc_types does not match Log from ethers-rs. An issue is open on reth repo. Due to this, in core/mod.rs we still need to use Bytes, H160 and H256 imported from reth_primitives::rpc.

one rebase away from greatness 🦾🥁


Modal dialog doesn't manage focus

After opening a modal, the focus remains on the button that opened the modal
After manually focusing an element that's inside the modal, elements outside the modal can still be focused by pressing the Tab key enough times
After closing the modal, the focus isn't returned to the button that opened the modal; the <body> gets focused instead. This is bad for accessibility.

@cvrebert those are all good points. Do you know how to focus on an element that is not a form element? I'll do som

hmm.. I'm not entirely sure how to prevent that. ideas?

Bootstrap's modal seems to do it somehow.

I'll check out their code. Thanks for the tip!


Implement restore capabilities

Currently, data can only be extracted from ZK/etcd and stored in a number of places but other than looking at it, you can't use burry to restore the state of an infra service.

With a8e417b216f93f12725722a0e6949c96adc186c9 this is basically addressed, modulo edge cases and more testing.


removes the .sql part of the asset entry

closes #750

Could you also remove the extension from the workspace?

@magorlick done


Coding ID 93, society 17557 - language of recording different from language assigned to society

Parlametrics coding 93 is spoken in Bahasa Indonesian (indo1316). However, it is currently assigned to society 17557, whose language is Javanese (java1254). There is no current GJB society that is a perfect match for this language, because Bahasa Indonesian is the national language and the GJB societies from Indonesia are all assigned to local languages.
Best solution I can think of right now is to keep assigned to society 17557 and make a note in the metadata that the society match is a bit of an approximation.

Actually, new solution now makes more sense: assign conversation 93 to new society Urban Jakarta, which is assigned language indo1316.


Fix for automergeTriggers.yml (resource management app)

Disable logic is conflicting with enable logic since the order is not guarantee.
Kaleb try to create another label to act specifically for disabling  the auto-merge
Microsoft Reviewers: Open in CodeFlow

@Trenly let me know when you want me to merge this.

@Trenly let me know when you want me to merge this.

Looks good to me!