Any way to access loaders with "inline code" (vm.Script, eval, etc.)

If you have serialized "content" of a specific loader format (say for example TypeScript, or whatever), it would be nice to be able to use the existing loader functionality to be able to evaluate it "inline". One might for example expect that vm.Script, given that it allows you specify a filename option, might automatically choose the right loader:
// Imagine this was run with --experimental-loader typescript-loader.mjs
vm.Script("const x: Number = 5;", { filename: "test.ts" });

As far as I'm aware though, there is no way to do this currently (please correct me if I am mistaken!). I tried seeing if I could call load() directly to go through the loading machinery and just passing in the source property, but I also couldn't find an API to do that:
doLoad({ source: "some typescript...", url: "blah.ts" });

I think the loader itself need to export some function, as the loaders API only deals with transforming URLs to a source string.

Right, but that forces one to have to replicate the entire machinery. The vm.Script example above displays why this would be frustrating, node already knows the right transpilation for ".ts" files, yet I'd have to hope the TypeScript loader provider took the care to provide a separate function, and then I'd have to apply it manually. The mime-type data URL you provided I think does a great job of highlighting the core problem and proposing an excellent solution. The current system currently couples two largely unrelated tasks:  fetching (as in "loading from storage") with evaluation (as in "loading into the runtime"). It is weird that it should be the TypeScript loader's job to itself handle data URLs. It would seem that there should be a composable system where a single data URL "fetching" loader merely worries about taking a data URL and turning it into a  { mimeType, source } structure that can then be handled by an unrelated TypeScript (or whatever else) source string "evaluating" loader.
As a thought experiment, imagine that instead of current resolve() and load(), we instead had fetch and evaluate. The job of the first is, given an import specifier, grab the contents and determine the mime type, and return the contents and a mimeType. It can also of course simply modify the specifier and pass it off to the nextFetch the way resolve can pass on to the nextResolve.
The evaluate loader then registers itself for a mime type (evaluate no longer needs to concern itself at all with determining if it itself should handle the content in question). It also is "storage type independent". At this phase, it makes no difference whether the contents came from a data URL, base64, filesystem, or network request. All the TypeScript transpiler needs to do is transpile, then pass off to the nextEvaluate with the mimeType changed to "text/javascript":
typescript-loader.js
import { compile } from "typescript-compiler";

// This module has no need for a `resolve` function at all. HTTP/HTTPS requests that return
// mime-type: text/typescript work out of the box, data URLs that specify text/typescript work
// out of the box, and files with the file extension .ts work out of the box. If anyone ever
// implements a different storage loader (like ftp:// or something), that will also just work.
export const MimeType = "text/typescript";
export const FileExtensions = ["ts"];

export default function evaluate({ mimeType, source }, nextEvaluate) {
    nextEvaluate({ mimeType:"text/javascript", source: compile(source) });
}

Similarly, the https loader example from the docs now makes more sense in my opinion:
const isHTTPS = specifier => specifier && .startsWith('https://');

export function fetch(specifier, context, nextFetch) {
  const { parentURL = null } = context;
  const HTTPSURL =
    isHTTPS(specifier) ? new URL(specifier) :
    isHTTPS(parentURL) ? new URL(specifier, parentURL) :
   false;

  if (!HTTPSURL)
    return nextFetch(specifier);

  // Normally Node.js would error on specifiers starting with 'https://', but here
  // we can load the data ourselves.
  return new Promise((resolve, reject) => {
      get(url, (res) => {
        let data = '';
        res.on('data', chunk => data += chunk);
        res.on('end', () => resolve({
          mimeType: res.getHeader("Content-Type"),
          shortCircuit: true,
          source: data,
        }));
      }).on('error', (err) => reject(err));
    });
  }
}

As you can see, the HTTPS loader now only needs one function, and doesn't have to make the assumption about the format of the returned code. Similarly, a future CoffeeScript transpiler doesn't have to do an extreneous early recursive call to nextLoad that relies on that incorrectly hinting that the code is module, just for you to ignore it and transpile afterward.
Just to demonstrate parity with the current API's abilities, a hypothetical "github:"
loader still only needs to modify the specifier and pass on to the next loader:
github-loader.js
export function fetch(specifier, context, nextFetch) {

  if (!specifier.startWith("github:"))
    return nextFetch(specifier, context);

  return nextFetch(`https://github.com/${specifier}`, context);
}

This now allows you to load from github:nodejs/node/some/file.ts, and will  compose fine with the typescript compiler, with neither needing to know anyting about eachother, and both only needing to implement one function.
Back to the original issue though, this now provides a good foundation to have "loader" support (which is a bit of a loaded term since loaders do everything from loading to transpiling) anywhere code might show up. Whether it be in vm.Script(), or even if you wish to parse markdown and compile code in code blocks that specify the language type in the code fence.

A quick note: I would not necessarily call the two functions fetch and evaluate, I just chose those names to not make it confusing if I reused load for example. The basic Idea is that there is something that "gets the data", and then something that "does stuff to the data".

The basic Idea is that there is something that “gets the data”, and then something that “does stuff to the data”.

An earlier version of the Loaders API had four hooks: resolve, getFormat, load and transform. These got collapsed into just resolve and load, with the responsibility for determining the format left ambiguous (it could be decided by either hook, so long as load returns it) and transformations, such as transpiling TypeScript, happening within load.
We did this to make chaining more practical. If there are separate load and transform hooks, for example, a transpilation loader could do its work in either one; and then all the other loaders in the chain would need to know what to expect from each hook. Collapsing them into one hook makes chaining simpler and less prone to error, and relying less on community-determined standards and expectations.
We’re approaching stable status for the API, so reevaluating the hooks is not something that I would welcome at this point. Refactoring them into fetch—really resolve plus load—and evaluate, which is really transform, would weight the API far in the direction that it’s geared toward the transpilation use case at the expense of all others. There are lots of use cases for loaders that just do resolution, like the example HTTPS loader in the docs, and it’s unnecessary for all of those loaders to need to handle data retrieval in addition to rewriting resolution strings.
All this said, your original question of having a way for loaders to apply to vm.Script and similar is a valid one. At the moment vm.Script means CommonJS and there’s a separate vm.Module for ESM code, so while loaders are ESM-only they would apply only to the latter. I think in the short term the easiest way to achieve this is if there were an API that exposed the possibly-loaders-enhanced resolve and load hooks for use anywhere; like import { resolve, load } from 'module' or somesuch, that would allow passing in input from user code to get output as it would have come from the loaders workflow. You could use such APIs to transform your strings before passing them into vm.Script or vm.Module. Some of the items under https://github.com/nodejs/loaders#milestone-2-usability-improvements point at an API such as this.

Hi @GeoffreyBooth, thanks for the response and the context! If the reasoning is around not wanting to change the API further, then I totally get that. However, I am wondering if you looked at all of the examples I provided -- the https loader in my system is (I think?) quite simpler and easier to follow than the one in the current docs (linked here again for comparison: https://nodejs.org/api/esm.html#https-loader).
I only bring this up because I don't think this system is weighted towards transpiling at all, and leaves resolution equally simple for specifier/url changes, and more ergonomic for "just download" cases. If you look at the https loader in my example, it is of course shorter than the one in the node docs, but more importantly, requires implementing only one function (which I think makes way more sense, vs. having to implement resolve just to early exit and then do the real work in load), and most importantly automatically composes with anyone else's transpiler loaders. In contract, the https example is the Node docs is forced to bring up the fact that it's not clear what to do if the downloaded data isn't an ESM module, probably because the solution is too complicated in an already 50 line example.
I provided the 3 line "github" resolver example in my post to show how you still get super simple resolution with the "resolve/load" system (to reiterate here, fetch doesn't force you to actually do the downloading if you just need to change the specifier/url, you can still send that off to the nextResolver).  This one is short enough to just paste back in here:
export function fetch(specifier, context, nextFetch) {
  if (!specifier.startWith("github:"))
    return nextFetch(specifier, context);

  return nextFetch(`https://github.com/${specifier}`, context);
}

I think the two big ideas are that 1) to your point, neither use case should be favored: and thus in most instanced they should both require implementing just one function. And 2) we should adopt the existing mime-type standard for handling data, that would we'd get for free from any sort of loader that interacts with the internet, as opposed to having an implicit system that relies on the code having to infer the type from the filesystem extension in both methods. Anyways, again, if the API is done then no worries, just wanted to make sure my concerns and explanation was clear, and also hopefully point out that this system isn't meant to in any way target transpilation at the expense of resolution -- I think both are simpler here, and their respective roles are clearler (as opposed to both handling identification for example).

@tolmasky resolution and fetching are separate though. You need to resolve a specifier into a URL which allows returning the same module binding in the case multiple modules import the same module using different specifiers. Imagine:
main.js
import "https://example.com/foo.js";
import "https://example.com/etc.js";

https://example.com/foo.js:
import "./etc.js";

In this case the specifiers "https://example.com/etc.js" and "./etc.js" resolve to the same URL. You wouldn't want to load two instances of etc.js.
I do 100% agree we need a way to programmatically access the loader API. I'm working on a hot reloadable loader right now. Since nodejs caches modules forever eventually we run out of memory. I was hoping to move to vm but then I don't have any way to access other loaders in the chain.

If REPL support is included in Milestone 3, I think it would also makes sense to include support for node --eval as well. Which ideally would also extend to eval() calls.

Do you want to open an issue to update the readme?
I don't think --print is feasible because we can't add the equivalent of a console.log wrapper around ESM code because import statements must be top level. But the rest should be doable.

Assuming you meant PR, I opened one in https://github.com/nodejs/loaders/pull/174
RE: ESM in --print
I'm not sure how --print works, but is it really as simple as wrapping console.log around the code? If so, how does it accept if-statements like this: node --print 'if (true) { 2 }'
Since it's seems to accept statements, I'm curious what's preventing ESM import statements from working?

Since it's seems to accept statements, I'm curious what's preventing ESM import statements from working?

I don't know, I've never looked into it. I assumed the current --print somehow took advantage of the CommonJS wrapper but you're right, it must be something else. I assumed there was a reason ESM has never been supported in --print but maybe there isn't. That would need to happen first before hooks could affect it. If you can figure it out, pull requests are welcome.


Create deployment in k8s for jungle and lacchain

I have to fix the build process. When copying .env.* to .env, the graphql endpoint is lost.


Make generated records transparent

Making the generated records transparent makes debugging easier.

Hey Jens,
I've got conflicting updates from you and Leif Andersen.  It looks like, Lief is making the the structs #:prefab and you are making them #:transparent.  Since #:prefab implies transparent, I'm inclined to take his pull request, but if there is a reason you'd prefer #:transparent to prefab, we should talk with Lief and make sure that will work for his purposes too.
-andy:)

#:prefab is fine.
Both #:prefab and #:transparent prints the contents in the REPL.
2015-07-01 23:23 GMT+02:00 Andy Keep<EMAIL_ADDRESS>
Hey Jens,
I've got conflicting updates from you and Leif Andersen. It looks like,
Lief is making the the structs #:prefab and you are making them
#:transparent. Since #:prefab implies transparent, I'm inclined to take his
pull request, but if there is a reason you'd prefer #:transparent to
prefab, we should talk with Lief and make sure that will work for his
purposes too.
-andy:)
—
Reply to this email directly or view it on GitHub
https://github.com/akeep/nanopass-framework-racket/pull/7#issuecomment-117828232
.

--
Jens Axel Søgaard

Okay, sounds good, I'll mark this pull request closed and merge Leif's.
Thanks,
-andy:)


Ability to close the reader from the outside

Hi guys @hrishikesh-kadam @mahavir155 !
First of all thank you for the great library!
Does folio reader has ability to close itself outside of the reader.
For example I start reading the book from MainActivity, start the timer, when it finishes I call to close the reader and save read position.
If Folio Reader has no this option - what is you suggestion, how to implement it?

@mahavir155 Awesome, good to know!
When it can be implemented, I hope it's not so hard for you?

@OlegTarashkevich Close API now live in v0.4.2

Greate, but how can I listen to "book close" event?
I posted a question here #463
I'm new to android.


Integration with kinesalite

Recommendation on setting endpoint (host:port) and credentials in options to use a local kinesalite?  This is a follow-up to mhart/kinesalite#39
For local integration tests event sourcing to a lambda function.  Would this project emulate similar to KCL?  I'm trying to avoid the DynamoDB issue discussed in mhart/kinesalite#11
Sorry for dragging in a separate repo into the discussion; just wanted to provide context.

This is from the kinesalite readme:
Or with the kinesis module (currently only works in https mode, when kinesalite is started with --ssl):

var kinesis = require('kinesis')

kinesis.listStreams({host: 'localhost', port: 4567}, console.log)

Unfortunate that it only works with SSL version though

Not sure if I went this route yet, but will give it a go here in a bit and follow-up by midday.  Thanks @RodH257!

Great - got this working but question remains how to invoke a lambda function (on local) emulating the KCL.  This all based on the assumption that my use case is common (if not, interested to know what folks are using these two projects for) - just not finding a lot of examples on making the integration realistic compared to AWS.

Not really getting anything practical out of this and will need to sideline it for now.  Will close to reduce noise and circle back in the near future.


Cow: Watch tru-path.org

Cow requests the watch of the watch_keyword tru-path\.org. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

tru-path\.org has been seen in 2 true positives, 0 false positives, and 0 NAAs.

Approved by Nick in Charcoal HQ


run.py and OpenCL issues

Hi, I tried to build the binary on my GNU/Linux Debian 9.3 with NVIDIA 970 graphics card (driver 375.82) and I encountered these issues:

the original install/run.py script does not work, but replacing in the cmake fuction, the line cmd = "cmake" + arg + "../" + src_dir with cmd = [" cmake ", arg," ../ "+ src_dir] everything works fine

after having successfully built the binary and then installed and configured the add-on in Blender (2.78a), I have decomposed the Suzanne monkey successfully, but in the log
Suzanne_log.txt
have resulted some OpenCL related errors.

bye

Hi after analyzing a bit I saw that the OpenCL issue is due to the int32_t type declarations in the kernel program oclProgramSource in src/VHACD_lib/src/VHACD.cpp.
I solved by changing them with the int standard scalar type as described here.
I attached a simple git diff master with latest commit.
opencl-correction.diff.txt
Bye

Hi Consultit, consider forking, applying the updates you've discussed above and issue a pullrequest against the original repo.
Best Regards Jens Edhammer

Hi Jens, That would be great. Please, do.


Change language label rdf:label of increase (OEO_00340005)

Description of the issue
The rdf:label of the class increase got in # 1644 a German language label (@de).
This leads Protégé to show only the class ID.

Ideas of solution

Change to @en, then Protégé shows it correctly.
Can potentially solved while touching the class increase in the large module restructuring of #1592

Workflow checklist

[ ] I discussed the issue with someone else than me before working on a solution
[ ] I already read the latest version of the workflow for this repository
[ ] The goal of this ontology is clear to me

I am aware that

[ ] every entry in the ontology should have a definition
[ ] classes should arise from concepts rather than from words

I fixed this in #1670


like per hashtag does not respect likeLimit and it's called even if not subscribed in main.py

Fixed problems:

if there are config.tags, media were liked even thought liked$.subscribe() was not explicitly called in main.ts.
if likeLimit was set to 0 or unsetted then like would continuously occur without any limit
each number of likes for each tag feed was equal to likeLimit

https://github.com/breuerfelix/jinsta/pull/55

Now likes in hashtag feeds is't not done if there is no liked.subscribe() in main.
if likeLimit is set to 0 it will not continue forever.
Now instead of having likeLimit number of likes per hashtag each hashtag will have is own like number. The sum of all the like of all the hashtags will be equal (or real close) to likeLimit.
example.
if like limit is 10 and hashtags are ['one', 'two', 'three']
then executing once we could get 3 likes on 'one', 4 likes on 'two', 3 likes on 'three'
executing a second time could lead to 5 likes on 'one', 2 on 'two' and 2 on three
Note that the second time the sum is equal to 11, this might happen due to the Math.round() on Math.random() done in likesForTags() in features/utils. This could be solved but more randomness of this kind it think that plays on our favor.
While writing this it just came to my mind that maybe we should also randomize the order in which tags will be visited and each time we should only select a subsets of all the tags. If you like the idea @breuerfelix i could create a separate task for this, but for now i would like to give more priority to other tasks (such as implementing new features)

since you perfectly implemented this, i will close the issue :)


added migration answers table

Description
This PR creates the migration for the answers table.
Fixes # (27)
How to test?
run this command to test!
knex migrate:latest
Checklist

[x ] I have performed a self-review of my own code
[ x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ x] This PR is ready to be merged and not breaking any other functionality

Good job @DlnyaMazhari

Good group :)


characterCounter() doesn't work after dynamically adding

Hi All
Question is about dinamically appending characterCounter part.
Yes I know that I should initialize after dynamically adding, but it doesn't work
my input parts adding dynamically like this
var clone = SMTHING.cloneNode(true);
clone.getElementsByClassName('sm-class')[0].innerHTML = 'smth';
.
.
SOMETHINGELSE.appendChild(clone);

good, but
before appending $(clone).find('#textarea1').characterCounter();
or after appending $('#textarea1').characterCounter();
it doesn't work
it works correctly when I doesn't add dynamically,
Also I can see the added span.character-counter  , but js part (on focus or on blur) doesn't work ,
thanks in advance

Hi @amovsisyan Can you share a code pen for this? May be i can help you

Hi @developeranirudhprabhu
thanks for response and sorry for delay
https://jsfiddle.net/vtzapt0g/4/
does this have the info you asked ?

Hi @amovsisyan let me check and get back

@amovsisyan I found the issue that was stopping dynamic initialisation of the plugin and have provided a pull request. Kindly have a look at the suggested changes

@amovsisyan i have checked that this issue is not seen in v1. So with the new release this should work flawlessly

hi @developeranirudhprabhu
thanks for update , will check woon and let you know


SCP1289 - Impaired local intrinsic immunity to SARS-CoV-2 infection in severe COVID-19

Project short name:
Shalek-Human-SeqWellS3
Primary Wrangler: @arschat
Secondary Wrangler: Ida

Associated files

Google Drive: folder

Published study links

Paper: Impaired local intrinsic immunity to SARS-CoV-2 infection in severe COVID-19

Accessioned data: https://singlecell.broadinstitute.org/single_cell/study/SCP1289

Ingest project

Key Events

[x] Convert published metadata to HCA spreadsheet
[x] Manually curate dataset to meet HCA metadata standard
[x] Collect any matrix and cell-type annotation files
[x] Are the analysis files suitable for CellxGene? If something is missing get in touch with the authors to request it
[x] Upload sheet to validate metadata
[x] Transfer raw files to ingest to validate data files
[x] Check linking using ingest graph validator
[x] Ask the Secondary Wrangler for an end-to-end review of the project. Ask the Expertise Wrangler to review specific tabs if needed
[x] Submit dataset to Production
[ ] Complete the Export SOP
[ ] Convert project data to SCEA format following the SCEA conversion SOP if appropriate

Will use 1 cell suspension for each specimen after this slack discussion.

After submitting, get the following error in ingest:
Project is Invalid. Please go back and edit the project.
* should NOT have additional properties at root of document
Investigating.

edit the project fields through API and to edit the template

New submission is now graph valid, and ready for secondary review.

Hi Arsenios! The dataset looks great I only have two comments:
Specimen

I'd suggest cryopreservation, other since the cells are not dead

Analysis protocol

you can add the derivation process

Analysis file

there is no good ontology label for UMAP in HCAO right now, maybe it would be worth it to open an ontology ticket and request a new term
I think you swapped the protocols for 20210220_NasalSwab_NormCounts.txt and 20210220_NasalSwab_RawCounts.txt

Applied sec review suggestions (thanks Ida), and submitted.
Input form to be filled when exported.

Input form sent

Error in R28 - Neither project nor supplementary file metadata have submission_date stablished (Value: null). This may have been a side effect of programmatic updates.
Actions:

[ ] Update staging area with submission date (Take from submission entity) for both project and supplementary file metadata
[ ] Update ingest with that same information for project

I believe we have a gap in our validation process. Our metadata validation should have caught this error. Please create a bug ticket.

yep - system fields are not validated because they are generated on the go

@ESapenaVentura to confirm if we need to do the changes in Ingest. Otherwise this ticket could move to close right?

Was this resolved by Amnon as part of the R28 errors remaining to be sorted in Ingest that Amnon did last week? @ESapenaVentura ? Trying to understand if we can close this

missing submissionDate was add back to ingest by Amnon - this ticket can be closed!


[feature-request] Vim plugin should provide option to search through all files in current project dir

As in #368, this is a clone of a feature existing in CtrlP. Imagine I'm working on a project with this structure:
├── .git
├── module1
│   ├── bang
├── module2
│   ├── boom
└── module3
   └── twang
If I am editing module3/twang, and I use FZF, I cannot see any files outside of module3/. CtrlP will traverse up the directory tree until it finds a .git, .svn, .hv, etc. folder. This means that any project that is under version control can easily be traversed using only this one navigation tool. Would it be possible to add something similar to FZF? If not in the standard options, perhaps with some additional configuration by the users?

Are you using autochdir? If so I suggest not doing that, it's a legacy option that should not be used.

Something like this?
function! s:find_root()
  for vcs in ['.git', '.svn', '.hg']
    let dir = finddir(vcs.'/..', ';')
    if !empty(dir)
      execute 'FZF' dir
      return
    endif
  endfor
  FZF
endfunction

command! FZFR call s:find_root()

FZF -> Files if you have fzf.vim project
Using VCS-specific commands to find the root should give more accurate results

e.g. git rev-parse --show-toplevel

You can consider using the low-level fzf#run() directly if you need more control

Thanks guys.
Closed #369
On Wed, Oct 7, 2015 at 3:40 AM Junegunn Choi<EMAIL_ADDRESS>wrote:

Something like this?
function! s:find_root()
for vcs in ['.git', '.svn', '.hg']
let dir = finddir(vcs.'/..', ';')
if !empty(dir)
execute 'FZF' dir
return
endif
endfor
FZFendfunction
command! FZFR call s:find_root()

FZF -> Files if you have fzf.vim project
Using VCS-specific commands to find the root should give more
accurate results

e.g. git rev-parse --show-toplevel

You can consider using the low-level fzf#run() directly if you need
more control

—
Reply to this email directly or view it on GitHub
https://github.com/junegunn/fzf/issues/369#issuecomment-146053423.


Implement Send for all simple git types

This implements Send for all simple libgit2-sys types. According to https://github.com/libgit2/libgit2/blob/main/docs/threading.md this is fine - objects can be sent between threads.
Refs https://github.com/rust-lang/git2-rs/issues/194

Are there any plans on merging this any time soon ?

I’m not sure the best way to test this, but I’ve used this branch on an extensively multi-threaded application that opens, utilises and exchanges hundreds of repositories between threads without issue.
That’s definitely a bit “source: trust me bro” but it does seem perfectly fine.

I really wish this PR could be merged, or if in the docs was some clear documentation with workarounds

@orf did you find some issues with that, or just closed due to testing issues?

 It works fine

Any chance of this being reopened?

I did actually encounter one issue - multiple threads writing to a single odb instance in parallel using the odb writer interface seems to encounter race conditions and suffers from incomplete objects being written.
That’s one of the few objects explicitly and already marked as “safe to use from multiple threads”.

According to this PR https://github.com/libgit2/libgit2/pull/5595, I think odb of libgit2 should be "thread-safe".
If it doesn't, I think it's a bug in libgit2, not ours.
BTW, although we could use odb in multithread, it could still failed to call due to "locked" by another thread, have you check the returning error code?
I think we should mark them "Send" now and when we encounter some bug in the future, we could help open an issue in libgit2.

+1


source-git: document patch metadata

we have created a dedicated card for the complete documentation work, this should be good to merge, please approve


fix(datepicker): avoid accidental form submissions through calendar buttons

Sets all internal calendar buttons to be type="button" in order to avoid accidental submissions if the calendar is placed inside a form.
Fixes #10514.

@crisbeto please rebase

Rebased.


Misleading type error with implicit operator in generic type, from generic argument type to that generic type, when the generic argument is an interface

Fedora 31, dotnet 3.0.100
When using an implicit operator from a type variable T to a concrete type, if the type argument is an interface, a misleading error is shown: Cannot implicitly convert type 'SomeType' to 'SomeGeneric<SomeType>'. An explicit conversion exists (are you missing a cast?)
There is no explicit cast.
Here is a minimal example:
using System.Collections.Generic;
public class BadError<T> {
   public static implicit operator BadError<T>(T value) => new BadError<T>();
}
public class GoodError {
   // user-defined conversions to or from an interface are not allowed
   public static implicit operator GoodError(IReadOnlyList<int> value) => new GoodError();
}
public static class ObBoi {
   public static void Main()
   {
      IReadOnlyList<int> list = new List<int>();
      // Cannot implicitly convert type 'System.Collections.Generic.IReadOnlyList<int>' to 'BadError<System.Collections.Generic.IReadOnlyList<int>>'. An explicit conversion exists (are you missing a cast?)
      BadError<IReadOnlyList<int>> a = list;
   }
}

I believe what you're seeing is that implicit conversions to or from an interface is explicitly disallowed in C#. CC @jaredpar
From section 15.10.4 "Conversion operators" of the C# spec:

User-defined conversions are not allowed to convert from or to interface-types. In particular, this
restriction ensures that no user-defined transformations occur when converting to an interface-type, and
that a conversion to an interface-type succeeds only if the object being converted actually implements the
specified interface-type.

Correct. That's why I included the GoodError snippet of code. My problem is that the error message I get with the generic class is mislieading.

This issue was moved to dotnet/csharplang#3840


Python interoperability does not work: cannot call value of non-function type 'PyValue'

Running this code:
let np = Python.import("numpy")
let a = np.arange(15).reshape(3, 5)

throws
py.swift:5:18: error: cannot call value of non-function type 'PyValue'
var a = np.arange(15).reshape(3, 5)
        ~~~~~~~~~^

While np is <module 'numpy' from '/usr/local/lib/python2.7/dist-packages/numpy/__init__.pyc'>
Bu the way, how to link Swift to Python 3?

Currently, you have to call np.arange.call(with: 15).reshape.call(with: 3, 5).
The need to call .call(with) explicitly will go away with the Dynamic Callable proposal, but it is yet to be implemented.

Thanks very much! That helped.
How to pass named arguments then?
And what about Python 3?


Feat: replace input.live and input.recorded with input.visual

Upgraded repo to replace input.live and input.recorded nodes with the new input.visual node.
Main changes:

merge input.live and input.recorded capabilities into input.visual
attributes input_source and input_dir are now just source
files: add visual.yml, visual.py; remove live.yml, live.py, recorded.yml, recorded.py
add .gif and .m4v to supported input file types
if source is an empty directory, pipeline will gracefully end instead of crashing with FileNotFoundError
change "Approximately Processed: 10%" message to "Progress: 10%"; only display for inputs with known sizes beforehand
show "Frames Processed: 100" message for all inputs
remove filename from input.visual outputs; to set the filename in a output.media_writer instead
backward compatibility : add (temp) converter logic to DeclarativeLoader to convert existing input.live, input.recorded to input.visual
node converter displays deprecated warning for input.live, input.recorded; shows converted node contents for user verification
add input.visual unit test
update existing unit tests to work with input.visual
update docs: change all input.live, input.recorded references to use input.visual

Realised one problem with current implementation whereby filename is removed to the output node: when reading a directory of images/videos and outputting using media_writer, the list of input filenames are not available. Previously the media_writer would output a similar list of files, except they had been processed by PeekingDuck.

Updated based on above suggested changes for second review.

Replaced input.live/input.recorded -> input.visual where applicable.

Would be good to have a deprecation notice input.live and input.recorded where all the input nodes are listed, similar to the draw nodes. The notice can be added in the __init__.py, see example for draw.


Adding About Data Science beam article info to the Community page

fixes #21245
Adding information about and a link to the Beam content in Towards Data Science to the community page, collocated with the link to the Beam section on StackOverflow.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @sachinag

I'd suggest the broader Medium target instead of that specific publication, like so: https://medium.com/tag/apache-beam

@sachinag I agree. I updated the link to point to Medium, and I updated the title to say "Blog posts" instead of naming the publication.

LGTM, thank you Rebecca!
On Tue, Oct 11, 2022 at 10:47 AM Rebecca Szper @.***>
wrote:

@sachinag https://github.com/sachinag I agree. I updated the link to
point to Medium, and I updated the title to say "Blog posts" instead of
naming the publication.
—
Reply to this email directly, view it on GitHub
https://github.com/apache/beam/pull/23524#issuecomment-1275059447, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AOLR6K2AEILEH5Z6UROTBN3WCWR3BANCNFSM6AAAAAAQ66R5QA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Code Cell input/output display for latexpdf

At present, the basic pdf generated by myst-nb looks like this (ignore the missing contents) :-
python.pdf
The style is really basic at the moment and needs quite a bit of improvement.
We can address each one of them one by one in this thread.
I will start this off by pointing out a few

In and Out blocks are indistinguishable at the moment

We can have something like this

Alignment of text/latex outputs to left instead of center

Having packages to handle greek letters in code blocks

Would love to hear your thoughts on this, @mmcky @jstac @choldgraf @chrisjsewell
A reference implementation of styling of code-cells in quantecon lectures can be seen here:
python_programming_for_quantitative_economics.pdf
We can accumulate all of this in changes in a custom theme which we can load with latex_documents , or we can use latex_elements instead to specify it?

shifted this to cli https://github.com/ExecutableBookProject/cli/issues/114


chore(configParser): allow non-glob file pattern

re: the conversation at https://github.com/angular/protractor/pull/2445#issuecomment-159019360
Cucumber allows line numbers to be passed in the filename in the
form of features/some.feature:42. Glob expanding that results in
an empty array and nothing being passed to the framework runner.
This change checks for glob magic characters and only tries expanding
it if found. Otherwise it just passes the filename verbatim.
This was previously handled in #2445 by stripping the line number
first, but this is a more generic (non-cucumber) way to do it.

sighs
I'll try again when it works with npm 3

You don't have to close it.

wasn't sure if/when I could fix it


Please update the sailor version

Sailor version is too old, cannot be deployed into elastic.io

@khanzadyan fixed

Thanks @zubairov I will start deploring this into the tenants. Should I close this?

Deployment confirmed.

tested


Atlas Bulk upload with batch size throwing error

I am trying to upload excel with bulk upload functionality, for smaller size file its working fine , but having more data throws error from server side (504 time-out) , So I tried putting batch size parameter. But then its started throwing below error.
Any suggestion to resolve it?
client = AtlasClient(endpoint_url='http://xxxx.xxx.xx/api/atlas/v2',
                     authentication=auth)
result = client.upload_entities(batch=entities, batch_size=1000)

File "C:\Users\sbagal\PycharmProjects\pythonProject\venv\lib\site-packages\pyapacheatlas\core\client.py", line 1243, in upload_entities
payload["entities"], batch_size=batch_size)]
File "C:\Users\sbagal\PycharmProjects\pythonProject\venv\lib\site-packages\pyapacheatlas\core\util.py", line 274, in batch_dependent_entities
if len(candidate_set) > largest_candidate_size:
TypeError: object of type 'NoneType' has no len()

@wjohnson Any suggestion on this. I have excel with around 20K entities. But its not able to process complete at once .. so tried loading with specifying batch_size=1000 ,
Also one question on same line , do we need all required relationship entities to be available in same batch? for ex. if I create table in first batch , can I use it in second batch for column relationship or it again require to have in second batch ?

Hi, @sbbagal13  Thank you for using PyApacheAtlas!
Can you share which version of PyApaceAtlas you're on?  The traceback is in a surprising spot. It's like it couldn't find any of the assets to be grouped together.
Your second question makes we wonder how deeply connected are you assets?  For example, are all 20,000 related to each other?  The batching algorithm looks for relationships and will create batches that include all related entities together.  If you have a group of related entities that exceed your batch size, it should throw an exception.

Hi @wjohnson , Thank you for responding. I have tried with latest version 0.13 and get same exception. As you said it might be issue with how the data in organized in excel.
Here is how we have data in excel:
1: Instance (first/single row)
2: rdbms_db (Second row till 1050 rows)
3: rdbms_db (Second row till 55 rows)
4: rdbms_columns (56 row to ~20k rows)
How can I load this data using batches ? what would be the best approach to making batches and batch size as well
Do each batch need to maintain the hierarchy (instance => rdbms_db => rdbms_tables => rdbms_colums ) ?

Oh yikes, @sbbagal13  - I might batch this up into a few things and take advantage of the AtlasObjectId feature.  You can see more about this feature here
I'd follow this order of operations:

Upload the rdbms_instance by itself, collect it's guid
Upload the rdbms_db by themselves and...

Add a column called [Relationship] instance
Fill that column with AtlasObjectId(guid:123-abc-456) where 123-abc-456 is the guid of the rdbms_instance
Perform an upload with a batch size of 100 or 200 - They should all now be independent.
Note the guids

Upload the rdbms_table and columns and...

Add a column called [Relationship] db and [Relationship] table
Fill the db column for each table row with AtlasObjectId(guid:123-abc-456) where 123-abc-456 is the guid of the rdbms_db
Fill the table column for each rdbms_column row with the FQN of the table that is being uploaded with it.
Perform an upload with a batch size of 1000 or 2000 - They should all now be independent.
This assumes that no one table has more than 1,000 columns

That SHOULD solve the problem of everything being related to the one root rdbms instance.  Please let me know if you give it a try!

Closing this for now (due to > 1 month since last update) but @sbbagal13 please feel free to reopen if you are still having an issue.


Is it possible to specify iteration id?

Is it possible to specify iteration id?

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

ID: 021ecbd2-8976-64a4-ca95-0009a1c02692
Version Independent ID: 47011e64-0198-6fac-cd07-0334f350f59c
Content: Example: Use prediction endpoint to programmatically test images with classifier - Custom Vision
Content Source: articles/cognitive-services/Custom-Vision-Service/use-prediction-api.md
Service: cognitive-services
Sub-service: custom-vision
GitHub Login: @anrothMSFT
Microsoft Alias: anroth

@guhuajun Thanks for the feedback. We are investigating into the issue and will update you shortly.

@guhuajun I believe you are referring to using the prediction API with the iteration id. In the previous version v2 the iteration id was used in the URL where the URL was similar to the one below.
https://southcentralus.api.cognitive.microsoft.com/customvision/v2.0/Prediction/<prediction_id>/url?iterationId=<iteration_id>
For version v3 the name of the iteration is used in the URL.
https://southcentralus.api.cognitive.microsoft.com/customvision/v3.0/Prediction/<prediction_id>/classify/iterations/<iteration_name>/url
Please use the new version of the same for using the prediction service.

Thanks for your answer. I will try.


Test async_star_await_for_test is flaky on dart2js-win-chrome

It looks like async_star_await_for_test on the dart2js-win-chrome bot oscillates between flaky -> RuntimeError and RuntimeError -> flaky on unrelated cls.

/cc @athomas - in case this is something to address with the flakiness detection at the infra level.

This test is now consistently failing on dart2js (as well as the VM). We may need to check this test for correctness.

This test is also oscillating between flaky <--> RuntimeError for the dart2js-linux-chrome bot.


:bug: Fix apm shell script reference in Windows

Requirements

[✓] Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
[✗] All new code requires tests to ensure against regressions (It's not new.)

Description of the Change
Change the Windows apm CLI shell reference to the correct path.
Applicable Issues
Fixes #13874.

Is there a specific reason you dropped the .sh extension?
Thanks for catching this, by the way.

@50Wliu I looked in atom/apm, and there's no .sh extension on the shell scripts in the /bin folder anymore.
Glad to help. :smiley:

Wow, that was obvious.  I really messed this up, didn't I.  Thanks for fixing this!


Add specs to this repo

Steven and I agreed that it's a bit cumbersome, and confusing, to have web-components requirements/specs housed in a different repo. So I said I'd move them here. This is just a copy of the gene-search spec, which I wanted to get over here before the meeting tomorrow.
But if you don't like this idea, @alancleary we can keep specs over in component-search-ui-srs  (and probably rename it since presumably not EVERY component is a search).

Closing since we need to think about UI specs at a higher level than web components.


Feature: MonitorWake should use F15 by default to trigger and also allow a configurable trigger key

Please make sure your feature isn't already listed on HASS.Agent's issue tracker:
https://lab02research.youtrack.cloud/
There's a list of open bugs & features on the right. On the left you can see what's being worked on, what's planned and what's ready for the next release.
If you're not sure, don't worry, just go ahead and we'll discuss :)

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

MonitorWakeCommand uses up arrow key which may inadvertently create problems. This key should be configurable.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Use F15 as a default trigger key instead, it works and is not a key found on most keyboards, thus, likely ignored by most programs.
In the unlikely event some program does use F15, user can configure it to be something else.

Interesting, good point and good idea :)

That's what I did for my custom monitor on/off prior to finding HASS.Agent, but I'm fully migrated to your project now. Thank you! :)

when i implemented my own NirCMD workaround before the beta, I had it press "scroll lock" twice to turn on the monitor.

NirCmd was also part of my custom solution :)

Hi, possible to implement this? My CLI often receives the up arrow and shows the previous command.


Build error

@sharma-shray I did not look into the detail of the program. But a quick solution has been updated and the program should be able to compile with the newer version of CMake.
Please feel free to reopen this issue if it does not work for you.


Websocket Mapping Returning 403

Ambassador is throwing a 403 while trying to access a websocket endpoint within the cluster. Here are the steps to recreate the issue:
[Kube Environment: Docker for Desktop on Mac]
Install Ambassador and the Echo Service

Deploy Ambassador with Helm

helm repo add datawire https://getambassador.io
helm install ambassador datawire/ambassador

Deploy the websocket echo deployment/service/mapping

---
apiVersion: v1
kind: Service
metadata:
  name: websocket-echo
  namespace: default
spec:
  ports:
    - name: http
      port: 80
      targetPort: 8080
  selector:
    app: websocket-echo
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: websocket-echo
  namespace: default
spec:
  replicas: 1
  selector:
    matchLabels:
      app: websocket-echo
  template:
    metadata:
      labels:
        app: websocket-echo
    spec:
      containers:
        - name: backend
          image: jmalloc/echo-server
          ports:
            - name: http
              containerPort: 8080
---
apiVersion: getambassador.io/v2
kind: Mapping
metadata:
  name: websocket-echo
  namespace: default
spec:
  prefix: /websocket/
  service: websocket-echo
  allow_upgrade:
  - websocket

✅ Verify the echo server can be reached from a pod within the cluster

Create a node shell on the cluster

kubectl run my-shell --rm -i --tty --image node:12 -- bash

In the shell, download wscat

npm i -g wscat

In the shell, connect to the service via the cluster service endpoint

wscat -c websocket-echo.default.svc.cluster.local

Verify the connection is established and messages can be echoed back

❌ Verify the echo server cannot be reach from outside the cluster

Install wscat on you local machine

npm i -g wscat

Using wscat, connect to the service using the mapping

wscat -c localhost/websocket-echo/

Verify that the error returned is error: Unexpected server response: 403

Am I missing something simple?

I am experiencing this same issue

We believe this issue has been addressed in more recent releases.  Feel free to reopen if issues persist with Websockets mappings on 2.x or higher.

Is there any way to debug this issue properly? I'm currently not able to access my webservice inside my kuberentes. If i portforward the service directly everything works fine.


Remove code deprecated in 0.22 (released on October 13, 2022) [transpiler and providers]

There is code released 9 month ago that needs to be removed.

qiskit/transpiler/passes/calibration/rzx_builder.py:68
qiskit/providers/basicaer/qasm_simulator.py:375

This includes:

[ ] Remove deprecated code and tests (if they only check the deprecation raise)
[ ] tag the PR as Changelog: Removal
[ ] create a release note in the category upgrade:. If you can include an example with an alternative for user to migrate to the new code, as this change might break users code.

Related:

https://github.com/Qiskit/qiskit/issues/10812
https://github.com/Qiskit/qiskit/issues/10811
https://github.com/Qiskit/qiskit/issues/10810

Hello @1ucian0 !
Can you please assign this issue to me !

Done! Thanks

yes! all the issues on this epic are closed and, therefore, it can be closed. Thanks!


Improve config formatting

@kevgo @charlierudolph

I found the old formatting difficult to read.

Nice!  :ship:

Looks good


[4.0][Bug fix] Do not publish elfinder files when chosen not to install file manager

A bug in the installation process made the elfinder files get published EVEN IF the user chose NOT to install the file manager. That's because the elfinder_files were included in the minimum stack.
This PR fixes it.

A new inspection was created.

The inspection completed: No new issues


Add Engine::precompile_compatibility_key

Draft for #5802 for naming / impl feedback while working on tests.
After writing the implementation I landed on precompile_compatibility_key to show the relationship with precompile_{module,component}, but can revert to the discussed cache_key if desired.

Finally getting back around to this, I realized that the cache system already generates a key like this, and sure enough this has exactly what I was looking for: https://github.com/bytecodealliance/wasmtime/blob/83d00fea4a881ab1160bf0a609ac463643bc0821/crates/wasmtime/src/module.rs#L1141-L1151
Reusing this code as-is would require changing the function signature a bit, e.g.:
pub fn precompile_compatibility_hash(&self) -> impl std::hash::Hash {
    crate::module::HashedEngineCompileEnv(self)
}

Sounds reasonable to me!


Autogenerate contract interacts using typechain.

Use typechain to generate the contract interacts.
Add post install script to generate the contract interacts

Upgrade web3 version to 1.0.0-beta.37 to be in sync with mosaic.js web version


Different number of classes (bins) for angles error

When trying different number of classes (bins) for angles, I get
/opt/conda/conda-bld/pytorch_1550802451070/work/aten/src/THCUNN/ClassNLLCriterion.cu:105: void cunn_ClassNLLCriterion_updateOutput_kernel(Dtype *, Dtype *, Dtype *, long *, Dtype *, int, int, int, int, long) [with Dtype = float, Acctype = float]: block: [0,0,0], thread: [14,0,0] Assertion `t >= 0 && t < n_classes` failed.
Traceback (most recent call last):
  File "training.py", line 278, in <module>
    main()
  File "training.py", line 230, in main
    criterion_azi, criterion_ele, criterion_inp, criterion_reg, optimizer)
  File "training.py", line 187, in train
    loss_reg = criterion_reg(out[3], out[4], out[5], label.float())
  File "/opt/conda/lib/python3.6/site-packages/torch/nn/modules/module.py", line 489, in __call__
    result = self.forward(*input, **kwargs)
  File "/code/auxiliary/loss.py", line 42, in forward
    return delta_loss(pred_azi, pred_ele, pred_rol, target, self.__bin__)
  File "/code/auxiliary/loss.py", line 28, in delta_loss
    delta_azi = pred_azi[torch.arange(pred_azi.size(0)), target_label[:, 0]].tanh() / 2
RuntimeError: CUDA error: device-side assert triggered

The error happens inside the DeltaLoss class in the delta_loss method in the line:
delta_azi = pred_azi[torch.arange(pred_azi.size(0)), target_label[:, 0]].tanh() / 2

(link to line: https://github.com/YoungXIAO13/PoseFromShape/blob/master/auxiliary/loss.py#L29)
I tried debugging, but wasn't successful. I mostly use TF, so maybe I'm missing something very common in Pytorch?
When I use default number of classes (azimuth=24, elevation=12, in-plane=24), training runs normally and completes.

I found out the problem.
Number 180 is not divisible with 24 - the elevation angle has range set to 180: https://github.com/YoungXIAO13/PoseFromShape/blob/master/training.py#L124
So the solution is to set these two numbers (range and number of classes) to be divisible.
Anyway, pytorch error should have been more informative ...

Thanks for your notice, I've made a new commit to change all xxx_classes as a function of bin_size which is  used to define the classification bin size for all Euler angles, where you only need to change the bin_size to conduct an ablation study.


[Zotero] Show author (and other information) in search result

Extension – Zotero

Author: @sadanand-singh

The Zotero extension now searches for author, but it would also be great if the search result screen could display the author name. This is the most relevant information missing, with other information such as Volume, Issue Number and Pages potentially also a nice addition.
Moreover, the publication date field often shows multiple dates (or rather the date in multiple formats), which could be fixed.
Finally, I was wondering if the shortcuts for the commands can be made customisable (e.g. make "Copy the Bibtex Citation Key" the default enter key option)?
These could be useful improvements to an already great extension!

Next PR will add authors in the main view. Other issues like Volume etc, are not that easily reliable and would need quite a lot of development time, hence personally I have not found adding them worth my time.
Same goes for date format. Zotero really sucks at how it parses dates and it would really need a lot of coding to try to standardize it.
Shortcuts customization is a limitation of Raycast. Please file a feature request for the Raycast core feature separately.

Next PR will add authors in the main view. Other issues like Volume etc, are not that easily reliable and would need quite a lot of development time, hence personally I have not found adding them worth my time.
Same goes for date format. Zotero really sucks at how it parses dates and it would really need a lot of coding to try to standardize it.
Shortcuts customization is a limitation of Raycast. Please file a feature request for the Raycast core feature separately.

Sounds great, thank you for your work

Next PR will add authors in the main view. Other issues like Volume etc, are not that easily reliable and would need quite a lot of development time, hence personally I have not found adding them worth my time.
Same goes for date format. Zotero really sucks at how it parses dates and it would really need a lot of coding to try to standardize it.
Shortcuts customization is a limitation of Raycast. Please file a feature request for the Raycast core feature separately.

A small bug is that when I select "Open PDF", Raycast will always also open Zotero window and highlight that item, although it did open PDF at the same time. A little bit annoying, can you fix it if you have time? 😃

If I can add something, it would be useful to also have an option "Past Bibtex Citation Key to App" akin to Reference and Bibtex Entry.

If I can add something, it would be useful to also have an option "Past Bibtex Citation Key to App" akin to Reference and Bibtex Entry.

old request, but any update on getting the citation key to show up?


Error using Text component for production.

When using the Text component and creating a production build, it causes the error:
Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.

https://reactjs.org/docs/error-decoder.html?invariant=130&args[]=object&args[]=

This sometimes happen if the Text component isn't imported in the module and React is receiving the global Text instead. Do you have import { Text } from 'rebass' in scope in your module?

Sorry about that, I made a mistake in my initial attempt to recreate the problem. What's really happening is when I pass Text into a styled HOC, it gets rendered in development but not in production. It appears to lose all stylings in production. This has actually forced us to run production builds with Webpack set to NODE_ENV=development for the time being and has caused other unusual issues.
Here's some example code:
import React, { Component } from 'react';
import { Text } from 'rebass';
import styled from 'styled-components';

const ColorText = styled(Text) `
  color: pink;
`;

class App extends Component {
  render() {
    return (
      <div className="App">
        <ColorText>Hello</ColorText>
      </div>
    );
  }
}

export default App;

If you also want an example repo, I can create a create-react-app showing the issue.

check the link below, I had similar problem whit grid-styled. In my case grid-styled had different version of styled-components than the styled-components itself. And as a result the styles were not applied in production but worked in development. It almost drove me crazy before I solved it
https://www.styled-components.com/docs/faqs#why-am-i-getting-a-warning-about-several-instances-of-module-on-the-page

Closing this out since I suspect this is an issue with styled-components as mentioned above

The problem is beyond styled-components. Getting it on a fresh create-react-app,  just modified the fresh app.js like so:
`import React, { Component } from 'react';
import { Button } from '@rebass/grid';
import './App.css';
class App extends Component {
render() {
return (

Hi

);
}
}
export default App;
`
Then getting this error:

I have a suspicion that there is no named export "Button" in @rebass/grid. Try import {Button} from "rebass"

Thanks @trabek that solved it!


Align NSDateComponents selectors with OSX

NSDateComponents does not have a public "week" property, but it does have deprecated week and setWeek: methods, which do not interact with other values in NSDateComponents.

:shipit:

Having a week property is the same as having setWeek: and week. Perhaps we just need an explicit @synthesize week = _week; at the top of the implementation?

I worry somewhat that legacy code will be relying on week to actually do something; I don't think that it was always deprecated, and I don't think it always did nothing.
Are there facets that consumer NSDateComponents that could rely on the week property?

This is merely to not be flagged by our analysis tools as a mismatch.  week never worked on our platform, there is no expectation that it should work at this point.  Given that it is deprecated we could consider it if someone really needs it.

In reply to: 239017245 [](ancestors = 239017245)

:shipit:

NSDateComponents* dateComponents = [[NSDateComponents alloc] init];

needs to be released.

Refers to: tests/unittests/Foundation/NSDateComponentsTests.m:26 in 8f72d34. [](commit_id = 8f72d3464940b334b6066f0654aaff1c7e82e2d3, deletion_comment = False)

#include "gtest-api.h"

nit: replace it by TestFramework.h

Refers to: tests/unittests/Foundation/NSDateComponentsTests.m:17 in 8f72d34. [](commit_id = 8f72d3464940b334b6066f0654aaff1c7e82e2d3, deletion_comment = False)

:clock1:

That's not true, week works fine on our platform. I have some tests in NSCalendar verifying so, not as many as the other calendar units since it is deprecated however. If the concern is our analysis tools, a better solution may be to flag this in some way so the analyzer doesn't mark it as invalid.

In reply to: 239018515 [](ancestors = 239018515,239017245)

:shipit:


remove the empty branch in VariableAssignmentList

What problem does this PR solve?
Fix pingcap/tidb#17750.
What is changed and how it works?
Remove the empty branch in VariableAssignmentList.
Check List
Tests

Unit test
Integration test

Code changes
Side effects
Related changes

Need to cherry-pick to the release branch

Please add a test case showing that SET doesn't parse.
Rest LGTM.

/run-cherry-picker


added param to bind a key for "clear_screen"

so people can still avoid to use ESC to close inventories, whilst using SPACE for something else. yaaay!

Selfishly, I don't think this is necessary with the PR to auto-detect hotkeys. PR-905 loads the key file which has an OpenMenu keybind which the PR already leverages in a few spaces.
I can work to ensure that all explicit send calls for "esc" or "space" are updated within the PR.


Create a docker image for redshift_console

I've created on based on the python:2.7 base image: https://github.com/EverythingMe/redshift_console/commit/f5b522d2d45aed6e5f1f03283240974eff7e9e66
It's my first docker container, so feedback is appreciated.
To run it use:
docker run -e REDSHIFT_CONNECTION_STRING="user= password= host= port=5439 dbname=" -p 5000:5000 arikfr/redshift-console

The container works great, very easy to run this way thanks !
Although there are some issues with the app itself:
1.The Schemas page doesn't show any data (besides the upper tool bar)
2. On the Chrome I have to hit the restart button in order to see data (Loads, Status) . in Safari no refresh is needed.

Re. schemas page -- I'll check why this happens & fix.
Re. the need to refresh - what version of Chrome are you using? What OS? Are there any other errors in the console on those pages?

Chrome - I go to one of the tabs (status,loads) - there is an error and the page doesn't load, I hit refresh - no error and the page loads.

I couldn't reproduce it locally, but I just put a "safe guard" around the toFixed calls that might fail. I'll push the fix and release an updated version of the pip package and docker container tomorrow.

Great

@michaelloewenstein can you try pulling new version of the docker image and see if this resolved for you?

@michaelloewenstein if you didn't pull it already, please pull everythingme/redshift_console -- I'm going to deprecate the arikfr one.

Looking good, thanks! I'll try to use it a bit before we close this issue.
Michael Loewenstein
http://www.facebook.com/LoenMichael
http://il.linkedin.com/pub/michael-loewenstein/22/9a5/713/ | Blog
http://blogs.microsoft.co.il/miziel |w: i-collect.info | m:+972544503551 |
<EMAIL_ADDRESS>On Thu, Jul 16, 2015 at 11:12 AM, Arik Fraimovich<EMAIL_ADDRESS>wrote:

@michaelloewenstein https://github.com/michaelloewenstein if you didn't
pull it already, please pull everythingme/redshift_console -- I'm going
to deprecate the arikfr one.
—
Reply to this email directly or view it on GitHub
https://github.com/EverythingMe/redshift_console/issues/13#issuecomment-121872657
.

Actually this one is already closed ;-) But feel free to open new issues if you stumble at anything.

Out of the 6 tables I got in some schema, 2 of them appears to be empty
while they are not empty in reality !  ever ran into something like that?
In the attached image you can see the redshift-console above and the sql
client below providing different insights.
[image: Inline image 1]
Michael Loewenstein
http://www.facebook.com/LoenMichael
http://il.linkedin.com/pub/michael-loewenstein/22/9a5/713/ | Blog
http://blogs.microsoft.co.il/miziel |w: i-collect.info | m:+972544503551 |
<EMAIL_ADDRESS>On Thu, Jul 16, 2015 at 11:30 AM, Arik Fraimovich<EMAIL_ADDRESS>wrote:

Actually this one is already closed ;-) But feel free to open new issues
if you stumble at anything.
—
Reply to this email directly or view it on GitHub
https://github.com/EverythingMe/redshift_console/issues/13#issuecomment-121876854
.

It doesn't show the image, can you attach it through GitHub's interface, or just send me directly (arik@everything.me)? thanks.

In addition, there is a table that exists but doesn't appear at all!
Michael Loewenstein
http://www.facebook.com/LoenMichael
http://il.linkedin.com/pub/michael-loewenstein/22/9a5/713/ | Blog
http://blogs.microsoft.co.il/miziel |w: i-collect.info | m:+972544503551 |
<EMAIL_ADDRESS>On Thu, Jul 16, 2015 at 12:02 PM, Loewenstien Michael <
<EMAIL_ADDRESS>wrote:

Out of the 6 tables I got in some schema, 2 of them appears to be empty
while they are not empty in reality !  ever ran into something like that?
In the attached image you can see the redshift-console above and the sql
client below providing different insights.
[image: Inline image 1]
Michael Loewenstein
http://www.facebook.com/LoenMichael
http://il.linkedin.com/pub/michael-loewenstein/22/9a5/713/ | Blog
http://blogs.microsoft.co.il/miziel |w: i-collect.info | m:+972544503551
|<EMAIL_ADDRESS>On Thu, Jul 16, 2015 at 11:30 AM, Arik Fraimovich <
<EMAIL_ADDRESS>wrote:

Actually this one is already closed ;-) But feel free to open new issues
if you stumble at anything.
—
Reply to this email directly or view it on GitHub
https://github.com/EverythingMe/redshift_console/issues/13#issuecomment-121876854
.

The missing table: is it on the same DB you used in the connection string? Maybe permissions problem? (or you've used a superuser?)


Change opacity of components on dragging

How would you go about changing opacity of all the components while one is being dragged (and kept at 100% opacity).
I wonder if there is an event listener I can work with to get:

start Drag (with the target element)
stop Drag (with the target element)

Thank you

Hi, this is not a bug report, you are asking for general programming support. That is not what this issue reporting system is for.
Please try stackoverflow for this type of question.


Offset is expected to be a string

Encoding to bytes causes and error.

Sorry for not reviewing, I ended up adding a test and including your fix in #40.

Sorry for not reviewing, I ended up adding a test and including your fix in #40.


re-enable git-annex in stackage

Now that esqueleto, aws, etc are fixed to work with ghc 8.x, git-annex builds again.

This still has some upper bounds issues:
QuickCheck-2.9.2 is out of bounds for:

[ ] chell-quickcheck-0.2.5 (>=2.3 && < 2.9). No maintainer.. Used by: library

http-client-<IP_ADDRESS> is out of bounds for:

[ ] aws-0.16 (>=0.3 && < 0.5). No maintainer. @aristidb. Used by: test-suite

vector-<IP_ADDRESS> is out of bounds for:

[ ] dbus-0.10.12 (>=0.7 && < 0.12). No maintainer.. Used by: library, test-suite

Kindly open a new PR once the bounds issues for chell-quickcheck, aws, and dbus have been addressed.


HOG Profile

Hi Guys, i have experience in nodejs but unfortunately newbie to bluetooth.
I want to implement  a keyboard/gamepad peripheral to automate some keystroks to ps4.
I absolutely have no idea how to start with bleno, my fist issue is how implement the HID device, what would be the structure of services/characteristics etc.
Any kind of help/docs/resources/code (hello world code for hogp) would be appreciated.

Just found https://github.com/kshoji/BLE-HID-Peripheral-for-Android it might be helpful. Will put some time to study it.

have you been able to implement a HID device using bleno ?


hosted: Update version for Mender client 4.0.4 release

Similar to #2423.

Pre-approved, with one minor comment to be clarified.

Thank you for the review :eyes:


Traffic from inside the cluster to external LB not working if IPSec is enabled

Bug report
I've ran into issues with IPSec enabled and trying to reach a service inside the cluster via it's external LB IP. As far as I understand kube-proxy inserts rules which rewrite the destination from external IP to internal pod IP to avoid hitting the loadbalancer as the traffic could flow within the cluster only. I've gathered that these rules are inserted and the traffic arrives at the destination pod. On the return path it looks like the connection tracking is not working as the traffic hits the lxc interface of the pod with source ip beeing the from pod instead of the service. Internal traffic with is directly addressed to the service ip from within the cluster works like expected: Pod->SVC(ClusterIP)->Pod.
For more information see below about configuration and sysdump.
General Information

Cilium version (run cilium version)

1.8.2

Kernel version (run uname -a)

Linux node1 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Orchestration system version in use (e.g. kubectl version, Mesos, ...)

1.19

How to reproduce the issue

Create cluster and install cilium with settings from cilium.values.yaml.
Observe traffic flowing between pods via SVC(ClusterIP) is working like expected hitting the external load balancer via it's global ip is not working.
Disabling IPSec from the helm chart and redeploying the cluster  fixes this issue.

If you need more information or I should try a dev build let me know.
cilium.values.yaml
config:
  enabled: true
  blacklistConflictingRoutes: false
  ipam: "kubernetes"
  bpfMasquerade: false

global:
  tunnel: "disabled"
  kubeProxyReplacement: disabled

  encryption:
    enabled: true
    nodeEncryption: false
    interface: enp7s0

  nodePort:
    directRoutingDevice: enp7s0

  masquerade: true

  endpointRoutes:
    enabled: true

  nativeRoutingCIDR: "<IP_ADDRESS>/9"
  autoDirectNodeRoutes: false

cilium-ipsec-disabled.zip
cilium-ipsec-enabled.zip
(Sysdumps where taken from completly different clusters to avoid having leftovers from other settings)

Could you try without nodePort.directRoutingDevice: enp7s0? It shouldn't be needed given that kubeProxyReplacement is disabled.

I've ran the same tests with the setting removed and the issue still exists.

cc @jrfastab

This looks very similar to https://github.com/cilium/cilium/issues/14646 except tunneling is disabled.
@tobiaskohlbau Could you check if disabling endpointRoutes solves the issue?

This looks very similar to https://github.com/cilium/cilium/issues/14646 except tunneling is disabled.
@tobiaskohlbau Could you check if disabling endpointRoutes solves the issue?

Sorry for the late response. I will try to test your solution if I find some time to recreate a cluster with above settings.

Sorry for the late response. I will try to test your solution if I find some time to recreate a cluster with above settings.


Please iterate patch number and deploy alongside #448

Please iterate patch number and deploy alongside #448

Thanks, 1.3.130 from master and<EMAIL_ADDRESS>were released.
Please take a look at here:
https://github.com/fuse-box/preview-1.4.1/tree/master/examples/react-code-splitting
It's not documented yet, but it's terrific ;-)

@nchanged gorgeous!


Legacy PiP displays non-toggleable second subtitles.

For some reason when I use Legacy PiP there's subtitles which I can't turn off, if I try to toggle it, it displays another set of subtitles on top of the first ones, which are also smaller. Interestingly, non-toggleable subtitles also carry over to PiP.
https://imgur.com/a/X9A2PNO/
I have iPhone 12 mini on iOS 14.3 and currently use the latest versions of the app and YouPiP, although this bug persisted for me for several months before. I used non-legacy PiP without this issue but grew tired of speed bug, so I switched back and remembered about the subtitles issue.

@Insaneous Any examples videos with that issue?

Closed due to inactivity.


Image Analysis TypeSpec changes to support Python SDK updates for beta.2

Work in progress...

/azp run


Changing Risk Configuration form

The form to change a risk configuration should:

Show the current models checked
Having a Cancel button

Added ~54 label

Added ~56 label


ExpressTransport.transport is exposed

In current codes, ExpressTransport.transport is exposed to end users such that a task could send messages to any task and evade flow control

fixed by #423
close this.


linux-20 is dead due to SSD disk drive pickup errors and inode corrupted.

Type of Request
bug
Infrastructure Environment
LUCI, Github, Cocoon scheduler, Autosubmit, etc...
What is happening?
linux-20 is dead due to SSD disk drive pickup errors and inode corrupted.

Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

2/14 - linux-20 is dead again after rebuild and reinstall OS second times.

Reformat the SSD disk drive then reinstall OS Ubuntu and rebuild machine again. Linux-20 is back online and running fine now.


POST request failure when connected with a database having hyphen in the db name

{
"error": "unable to find table name"
}
I'm getting this response when making POST request to a db having hyphen in the db name. eg db name: "my-db".
GET, PUT, PATCH and DELETE are working fine.

If  "insertTableNameQuotesRegex" is updated, it should work.
Currently its not accepting db name or table name with hyphen
(?i)INTO\s+([\w|\.|"]*\.)*"(\w+)"\s*\(

Hi @sarath16933 thanks for reporting this issue.
Since you have found how to fix the bug, you are very welcome to send a PR to fix this.
What do you think? Can you do that?
Thank you.

Thanks @tiaguinho. I shall raise a PR for the fix.

When  will be this issue fixed?

When will be this issue fixed?

@saqwel unfortunately no, correction was sent, but be written test


PV enable timer starts only after car is connected

Describe the bug
When running evcc in "pv" mode and plugging the cable in, the timer starts:
[lp-1  ] DEBUG 2021/02/28 12:13:21 start pv enable timer: 30s
even though the exported power was above the enable.threshold already long ago , before plugging in.
It seems like the timers are reset or only taken into account, as soon as the car is connected.
P.S. With the default of 1 minute, I had multiple times the problem, that the charging did not start at all or went into an error state, as the car seemed to wait for a signal from the charging station, but it didn't happen. Currently I reduced my delay to 30 secs to workaround.
Expected behavior
Start charging immediately, if the enable settings have been fulfilled already before connecting the car.
Perform the "PV enable timer" logic also when car is not connected.

It seems like the timers are reset or only taken into account, as soon as the car is connected.

i haven‘t checked, but is that a problem?

i haven‘t checked, but is that a problem?

For me it was. Of course you can argue how "big" the issue is, but generally I would prefer to have a certain enable delay to prevent the charging to start on a short sunny moment. On the other hand, it should start charging on a sunny day, as soon as I connect the cable.

I would support to do monitoring of the available energy independently from a connected vehicle, so that charging can start immediately after plugging in. For me, this has low priority, but would improve the user experience as you would get "expected behaviour".
If a user, who is not familar with how EVCC works internally, plugs in the vehicle on a sunny day, she/he would expect that charging starts right now. Took me a while to understand where the delay comes from.

I would support to do monitoring of the available energy independently from a connected vehicle,

Off-topic. Please don't spam.

/reopen

Keep

Vorschlag: wir behandeln vehicle connected wie auch eine manuelle Auswahl des Modus über das UI oder Api so, als wären alle Timer abgelaufen und Schaltvorgänge könnten sofort stattfinden.
Passt?

Test wäre gut, sonst schieb ichs durch.

[x] Sofortiger Ladebeginn bei genügend PV-Strom: funktioniert


Should not use the nvme disk for the local fuse cache.

The bootstrap logic should use the following order to find a blockdevice on which it can configure its fuse cache filesystem:

ssd
hdd
nvme

SV
Version: master @Revision: 57bb56d5dccf9ff3c57ab01154f95cfaf5791688


Sphinx mapping: add reference to local object database shipped by pyt…

…hon3-doc
In Debian/Ubuntu, python3-doc ships a local sphinx documentation object
database that can be used to do offline documentation builds.
Add a reference to it, so that the network is only used if it is not
present, as a fallback.
Necessary to make the build reproducible (note that as other dependencies
do not ship these files yet, we have to patch them out downstream to
make the build fully reproducible).

Can one of the admins verify this patch?

Reference: https://wiki.debian.org/ReproducibleBuilds/SphinxIssues

Thanks @bluca for the contribution! That makes a lot of sense :)


error: external filter git-lfs smudge %f failed

Hi,
I am getting an error when check-outing a previous revision (see below).
Could you please point me out where the problem is?

LocalGitDir=.git
LocalGitStorageDir=.git
LocalMediaDir=.git/lfs/objects
TempDir=.git/lfs/tmp
ConcurrentTransfers=3
BatchTransfer=true
GIT_DIR=.git
GIT_WORK_TREE=.
GIT_PREFIX=

The message, "relation does not exist", means the file doesn't exist on the server. Did you push the file successfully?

I see.
Not yet. I have a local copy since I just experiment with the lfs.
Does that mean I cannot go back to a previous commit until I push the changes to the remote server?

Does that mean I cannot go back to a previous commit until I push the changes to the remote server?

Not necessarily. The smudge command will look in your .git/lfs/objects directory before checking the remote server. In your case, the file should be .git/lfs/objects/d9/b0/d9b006aa779cad15195d0d248a65550fa68ed372819d42ad444832633f241941.

Ok.
I have committed the changes and now it is working.
It looks like a bug but I cannot reproduce it now, so, I am closing the issue.
Thanks,
David.


onActivityResult called twice in Plugin class.

I am creating plugin to retrieve Phone Number and implementation is based on this Phone Retriever. My code for showing hint picker is fragmentActivity.startIntentSenderForResult(intent.getIntentSender(), RC_HINT, null, 0, 0, 0); and implemented PluginRegistry.ActivityResultListener in my PhoneRetrieverPlugin class. I am getting onActivityResult call twice. Below is code for onActivityResult
 @Override
    public boolean onActivityResult(int requestCode, int resultCode, Intent data) {
        if (requestCode == RC_HINT) {
            if (resultCode == Activity.RESULT_OK) {
                Credential cred = data.getParcelableExtra(Credential.EXTRA_KEY);
                Log.d(TAG, cred.getId());
                result.success(cred.getId());
                return true;
            } else {
                return false;
            }
        } else {
            return false;
        }
    }

where result is initialized in onMethodCall.  As this method is called twice, result is found to be null in second call.  How to avoid this method call twice?

Hi @MangeshKadam
can you please provide your flutter doctor -v
and  a reproducible minimal code sample
or the steps to reproduce the problem.
Thank you

@iapicca https://github.com/flutter/flutter/issues/48239 this is exact same code having above issue. I am getting result variable null in second onActivityResult call

I can reproduce the same issue with my plugin https://github.com/kineapps/flutter_file_dialog if I make small changes to example app's MainActivity.kt
This code works (current code in repo):
// OPTION A
import io.flutter.embedding.android.FlutterActivity

class MainActivity: FlutterActivity()

With this code the onActivityResult gets called twice (causing the issue https://github.com/kineapps/flutter_file_dialog/issues/1 in my plugin):
// OPTION B
import androidx.annotation.NonNull
import io.flutter.embedding.android.FlutterActivity
import io.flutter.embedding.engine.FlutterEngine
import io.flutter.plugins.GeneratedPluginRegistrant

class MainActivity: FlutterActivity() {
    override fun configureFlutterEngine(@NonNull flutterEngine: FlutterEngine) {
        GeneratedPluginRegistrant.registerWith(flutterEngine);
    }
}

The problem is that instructions here Upgrading pre 1.12 Android projects tell to use the OPTION B (which does not wok). You will get the same code with flutter create (Flutter 1.12.13+hotfix.8).
But instructions here Supporting the new Android plugins APIs tell you to use the OPTION A which does not cause the issue. But it is unclear if this OPTION A is safe to use in an app where I have tens of plugins some of which probably not migrated to V2 yet.
So in my opinion those two referenced documents give conflicting and/or confusing instructions. I don't know now how this should be implemented. Documents should cover also the case that an app depends on both V1 and V2 plugins which is probably the most common scenario currently.

The actual reason for this issue at least in my case is that ActivityAware.onAttachedToActivity is called twice (plugin instance is created twice?) on app startup with OPTION B. ActivityAware.onDetachedFromActivity is not called inbetween as you could expect. Not sure if this is a known feature, Flutter issue or an issue in my plugin. Anyway, it seems to be a mistake to perform initialization like addActivityResultListener in the ActivityAware.onAttachedToActivity because it will cause double registration for a listener. I refactored my plugin to prevent this by only saving the binding reference in ActivityAware.onAttachedToActivity and perform the actual initialization later in onMethodCall.

I can confirm this bug, just create a new project with flutter create with version 1.12.13+hotfix.8
and the bug is already there simply implementing PluginRegistry.ActivityResultListener and onActivityResult(..)
Proposed workaround by @kinex is working, simply commenting those lines:
class MainActivity: FlutterActivity() {
//    override fun configureFlutterEngine(@NonNull flutterEngine: FlutterEngine) {
//        GeneratedPluginRegistrant.registerWith(flutterEngine);
//    }
}

Is this safe to do or can we expect more bugs without registering the engine here?

Hi @MangeshKadam
Can't reproduce this issue on the latest master channel the issue even with configureFlutterEngine MainAcitivtydoesn't needconfigureFlutterEngine` anymore in V2 Embedding,

flutter doctor -v
[✓] Flutter (Channel master, 1.25.0-5.0.pre.64, on macOS 11.0.1 20B29
    darwin-x64, locale en-GB)
    • Flutter version 1.25.0-5.0.pre.64 at /Users/tahatesser/Code/flutter_master
    • Framework revision 4d4d017aa5 (6 hours ago), 2020-12-03 21:38:10 -0800
    • Engine revision 20caf54969
    • Dart version 2.12.0 (build 2.12.0-76.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.2)
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.2, Build version 12B45b
    • CocoaPods version 1.10.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.51.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.16.0

[✓] Connected device (4 available)
    • RMX2001 (mobile)     • EUYTFEUSQSRGDA6D          • android-arm64  •
      Android 10 (API 29)
    • Taha’s iPad (mobile) • 00008020-000255113EE8402E • ios            • iOS
      14.2
    • macOS (desktop)      • macos                     • darwin-x64     • macOS
      11.0.1 20B29 darwin-x64
    • Chrome (web)         • chrome                    • web-javascript • Google
      Chrome 87.0.4280.88

• No issues found!


Not able to use MtApi EA with investor password

Problem:
The EA get unhappy if you use a non-tradable account for MT login credentials.
This presumably prevent further use of the EA & API.
Expected
We should be able to do all normal operations , apart opening a trade, even when using investor credentials.  :)

@vdemydiuk
Is there a way you can modify the EA to allow using it also with an investor password?

This is probably related to #78.

Easy fix:
    if (IsTradeAllowed() == FALSE) {
        MessageBox("Trading is Disabled.", "MT4 API EA", MB_OK);
        //isCrashed = TRUE;
        //return (1);
    }

@eabase  Yes, you are right.
This checking prevents using MtApi with non-tradable accounts. It was added on the begining of the project and it is not actual for now.
I will remove code that stops experts if trade is not allowed (for both versions, MT4 and MT5).
User always can check this mode in runtime by calling function:
IsTradeAllowed() - MT4
TerminalInfoInteger(property TERMINAL_TRADE_ALLOWED) - MT5.


specify dplyr namespace

Not sure what's going on with the merge commit, but I think we can just squash it when we merge.

Thanks @davharris. That kind of merge commit typically results when you update a local branch to match upstream after you've already made changes. I squashed it out as suggested.


NuGet package has a leading zero

package id="CompareNETObjects" version="<IP_ADDRESS>" targetFramework="net45" />

This is non-standard and is causing problems in NuGet in VS2015, upgrades of packages sometimes fail.

@PhilipDaniels this is going to take a very long time to fix as it affects the base build process.

Hi @GregFinzer,
You might just need to update your version of NuGet. It looks like they made some changes in this area. Haven't dug in detail, but this thread implies later versions trim zeros: https://github.com/NuGet/Home/issues/3050

It is not just that.  It is a change of the base build logic, then manually modifying over 25 different projects with the associated installers.  Then performing a build and deploy of each.

For reference, the specific message that is being generated:
One or more unresolved package dependency constraints detected in the existing
packages.config file. All dependency constraints must be resolved to add or update
packages. If these packages are being updated this message may be ignored, if not
the following error(s) may be blocking the current package operation:
'FluentAssertions 4.19.4', 'XYZ 1.9.18057.70 constraint: CompareNETObjects (>= 4.3.0)'

Here XYZ is one of my libraries that uses CompareNETObjects.

Ok, thanks.


Set vim.g.loaded_leap = 1 when plugin loaded

I'm trying to determine whether or not leap has been loaded (because I'm setting up remotions for its mappings iff it is loaded).
Currently, I'm adding my own vim.g.loaded_leap = 1 in my lazy.nvim config() after loading leap.
This variable follows the vim convention for plugins:
https://vimhelp.org/usr_51.txt.html#:~:text=Then the user,are added twice.
Is there a better way to determine if leap is currently loaded?  Would you consider setting this variable yourself to follow convention?

For Lua plugins, there's no need for that, it's just: if package.loaded['leap'] then ... end (require checks this very table too before loading modules). https://www.lua.org/manual/5.1/manual.html#pdf-require

Thanks!  The not-yet-loaded version is:
---@param plugin string
function has_lazy_nvim_plugin(plugin)
  return require("lazy.core.config").spec.plugins[plugin] ~= nil
end

Shamelessly borrowed from LazyVim :)


No complaint buton

Describe the bug
After submission and grading of an UML, I couldnt find the complaint button or even the reviews/assessments on the graph.
To Reproduce

Go to UML excercise
Click on View result

Expected behavior
Find Complaint button and see the assessment
Screenshots

Which version of Artemis are you seeing the problem on?
7.6.5
What browsers are you seeing the problem on?
Chrome, Microsoft Edge
Additional context
No response
Relevant log output
No response

In your screenshots, you do not have a graded result. Therefore, you also can not complain about the result.


Typings - ChartDataset type is missing offset property

Workaround
using chart.data.datasets[0]['offset']
Environment

Chart.js version: 3.6.0

@GabrielMancik just to confirm, this is for the doughnut chart offset option?

yes


Docker Hub Automated Build

RELEASE NOTES

Ignore PHPSorm IDE configuration files.
Improved formatting in README.md.
Created configuration for docker-compose for more convenient development of Dockerfiles.
Use Pinba2 sources from current context instead of cloning latest master.
Planned next iteration of improvements for Dockerfile.

ADDITIONAL INFORMATION
The goal of this change is to clean up existing Dockerfile so ready-to-use docker images could be provided by using existing Docker Hub infrastructure. You can see a configured example of Docker Hub repository at https://hub.docker.com/r/alexanderilyin/pinba2/

Here are build settings I would recommend:

BTW I have a question why MariaDB was used and not a Percona?

Mariadb and not Percona is not a requirement, just something i had easy access to at the time.
Will happily test with Percona (and generally mysql api versions 5.7/8.0+).

Thing is - as pinba is a plugin - it depends on mysql/mariadb/percona internals that tend to change between versions.
So need to adapt the codebase as new versions are released.

Using multi-stage Dockerfile will allow removing cleanup which does not work as expected because of nature of layers

could you please elaborate on that, hate the cleanup code, will happily use any mechanism to get rid of it.

@anton-povarov I will update PR to use multi-stage Dockerfile as soon as I will be able to build it successfully. I thing I will have update in next few days on this.

@anton-povarov I've updated PR, unfortunately, to make Automated Builds work on Docker Hub I had to move Dockerfile to the root directory. Here are the main instructions you have to looks at to get the idea:
FROM fedora:25 as builder
...
FROM fedora:25
...
COPY --from=builder /_src/pinba2/mysql_engine/.libs/libpinba_engine2.so /usr/lib64/mysql/plugin/libpinba_engine2.so
...

You can read about it more here:

https://docs.docker.com/develop/develop-images/multistage-build/

Docker image from this PR is available on Docker Hub:

https://hub.docker.com/r/alexanderilyin/pinba2/tags/

Problem is it still fails with error from #2:
AF6469:~ ailyin$ docker run  alexanderilyin/pinba2:fedora-25-docker_hub
...
ERROR 1126 (HY000) at line 1: Can't open shared library '/usr/lib64/mysql/plugin/libpinba_engine2.so' (errno: 13, undefined symbol: my_print_error_service)

I found out that Docker Cloud allows to set build context, so it will allow keeping Dockerfile in a directory other than root, I will research it later this week:

https://cloud.docker.com/repository/docker/alexanderilyin/pinba2

Another option is to use CircleCI for building from multiple base images, but it makes sense only after #2 is fixed.

@mkevac please take a look on this PR one more time. Docker Image should be available in 25 minutes here:

https://hub.docker.com/r/alexanderilyin/pinba2/

It's building right now:

Locally you can build & start image like this:
docker-compose build
docker-compose up

P. S.
If you can share your Docker Hub username I can add you to collaborators so you can take a look on configuration inside.

@alexanderilyin it's working great
thank you!

@mkevac sweet. I just checked and the image was built automatically:
docker pull alexanderilyin/pinba2:fedora-25-docker_hub

The only problem that Docker Hub is extremely slow and it took 60+ minutes to build it remotely versus 25 minutes on MBP.

@mkevac any chances that image could be available here?

https://hub.docker.com/u/badoo/

@alexanderilyin we'll try

unsuccessful in finding owner as of now :(
@mkevac - found anybody ?

@anton-povarov nope, but I've just contacted my friend in Docker.


az ad sp create-for-rbac: --years not working

looks like a parsing issue.
az ad sp create-for-rbac --years 2
ERROR: Non-integer years and months are ambiguous and not currently supported.
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/site-packages/azure/cli/main.py", line 55, in main
    cmd_result = APPLICATION.execute(args)
  File "/usr/local/lib/python3.5/site-packages/azure/cli/application.py", line 117, in execute
    result = expanded_arg.func(params)
  File "/usr/local/lib/python3.5/site-packages/azure/cli/commands/__init__.py", line 216, in _execute_command
    result = operation(client, **kwargs) if client else operation(**kwargs)
  File "/usr/local/lib/python3.5/site-packages/azure/cli/command_modules/role/custom.py", line 464, in create_service_principal_for_rbac
    end_date = start_date + relativedelta(years=years)
  File "/usr/local/lib/python3.5/site-packages/dateutil/relativedelta.py", line 127, in __init__
    raise ValueError("Non-integer years and months are "
ValueError: Non-integer years and months are ambiguous and not currently supported.

Seeing this issue again
az ad sp create-for-rbac -n test-group --years 99
The command failed with an unexpected error. Here is the traceback:
Non-integer years and months are ambiguous and not currently supported.
Traceback (most recent call last):
File "/opt/az/lib/python3.6/site-packages/knack/cli.py", line 206, in invoke
cmd_result = self.invocation.execute(args)
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/init.py", line 351, in execute
raise ex
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/init.py", line 409, in _run_jobs_serially
results.append(self._run_job(expanded_arg, cmd_copy))
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/init.py", line 400, in _run_job
cmd_copy.exception_handler(ex)
File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/role/commands.py", line 69, in graph_err_handler
raise ex
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/init.py", line 379, in _run_job
result = cmd_copy(params)
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/init.py", line 171, in call
return self.handler(*args, **kwargs)
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/init.py", line 451, in default_command_handler
return op(**command_args)
File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/role/custom.py", line 1211, in create_service_principal_for_rbac
app_end_date = app_start_date + relativedelta(years=years or 1)
File "/opt/az/lib/python3.6/site-packages/dateutil/relativedelta.py", line 173, in init
raise ValueError("Non-integer years and months are "
ValueError: Non-integer years and months are ambiguous and not currently supported.

Same issue within the Azure Cloud Shell!

I think I see similar issue with Blob Storage, showing me tracebacks on az storage blob download
The command failed with an unexpected error. Here is the traceback:

The specified blob does not exist. ErrorCode: BlobNotFound
<?xml version="1.0" encoding="utf-8"?><Error>BlobNotFound<Message>The specified blob does not exist.
RequestId:6f266c99-701e-0014-4547-1d5e4b000000
Time:2020-04-28T10:29:09.2191258Z</Message></Error>
Traceback (most recent call last):
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-qdpilz60\knack\knack\cli.py", line 206, in invoke
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-qdpilz60\azure-cli-core\azure\cli\core\commands\__init__.py", line 578, in execute
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-qdpilz60\azure-cli-core\azure\cli\core\commands\__init__.py", line 636, in _run_jobs_serially
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-qdpilz60\azure-cli-core\azure\cli\core\commands\__init__.py", line 627, in _run_job
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-qdpilz60\azure-cli\azure\cli\command_modules\storage\__init__.py", line 240, in new_handler
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-qdpilz60\azure-cli\azure\cli\command_modules\storage\__init__.py", line 183, in handler
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-qdpilz60\azure-cli-core\azure\cli\core\commands\__init__.py", line 606, in _run_job
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-qdpilz60\azure-cli-core\azure\cli\core\commands\__init__.py", line 305, in __call__
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-qdpilz60\azure-cli-core\azure\cli\core\__init__.py", line 485, in default_command_handler
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-qdpilz60\azure-multiapi-storage\azure\multiapi\storage\v2018_11_09\blob\baseblobservice.py", line 1984, in
get_blob_to_path
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-qdpilz60\azure-multiapi-storage\azure\multiapi\storage\v2018_11_09\blob\baseblobservice.py", line 2156, in
get_blob_to_stream
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-qdpilz60\azure-multiapi-storage\azure\multiapi\storage\v2018_11_09\blob\baseblobservice.py", line 2124, in
get_blob_to_stream
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-qdpilz60\azure-multiapi-storage\azure\multiapi\storage\v2018_11_09\blob\baseblobservice.py", line 1862, in
_get_blob
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-qdpilz60\azure-multiapi-storage\azure\multiapi\storage\v2018_11_09\common\storageclient.py", line 430, in _perform_request
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-qdpilz60\azure-multiapi-storage\azure\multiapi\storage\v2018_11_09\common\storageclient.py", line 358, in _perform_request
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-qdpilz60\azure-multiapi-storage\azure\multiapi\storage\v2018_11_09\common\storageclient.py", line 344, in _perform_request
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-qdpilz60\azure-multiapi-storage\azure\multiapi\storage\v2018_11_09\common\_error.py", line 115, in _http_error_handler
azure.common.AzureMissingResourceHttpError: The specified blob does not exist. ErrorCode: BlobNotFound
<?xml version="1.0" encoding="utf-8"?><Error>BlobNotFound<Message>The specified blob does not exist.
RequestId:6f266c99-701e-0014-4547-1d5e4b000000
Time:2020-04-28T10:29:09.2191258Z</Message></Error>

Blob missing is actually sort of expected behavior in our case, I think it should be handled with regular error and nice message.

@Eragra3, this doesn't seem to be related to az sd. Please submit a new issue and share the necessary information.