cdp freezes/hangs with no output

Console output:
spawned chrome task
spawned cdp
enabled page
navigated
page loaded
Code:
Gist here
Desciption of problem:
The "task" just hangs/freezes and doesnt give any output. Preferbly, you would also teach me how I enable logging so I can deal with any further issues. aswell as pointing out what I did wrong 😄

A Chrome instance exposes a number of targets which are not necessarily just tabs, for example there are service workers, background pages of extensions, etc. by default this module hooks to the first available target. Usually Chrome keeps this list (CDP.List()) ordered by usage frequency (most recently used first).
Now the chrome-launcher module doesn't work for me, but in my case (an probably yours) the first target is the background page of the CryptoTokenExtension. So apart from explicitly create a new tab for your purpose a possible solution might be to filter the targets and attach to proper pages only:
const target = (targets) => {
    return targets.find(target => target.type === 'page');
};

const client = await CDP({ port, target })

Preferbly, you would also teach me how I enable logging so I can deal with any further issues.

I'm afraid there's no such thing for what concerns this module, but in this case it helped to take a look at the available targets with chrome-remote-interface list.
Hope it help!

PS this won't work because close() is a proper method of the CDP class and you'll lose the reference to this:
const {close} = client();
close();

FYI the default behavior is now to prefer type === 'page' targets (014e3f06ec63ab39c3439f1727a7c431a0ef9223).

Silly me, apparently Windows doesn't get headless support until Chrome v60. I was using v59 😮 . I will get back to you once I can update to v60 if this is still an issue


WebcamActiveSensor Does Not Update (Logitech c930e, Win 10 19042.685)

WebcamActiveSensor does not update from "False" to "True" when webcam is in use.  Sensor fails to update using Zoom client, webcamtests.com, and integrated windows 10 camera app despite operating correctly in all applications.
Webcam: Logitech c930e (USB)
Drivers: v <IP_ADDRESS>, provided on 5/13/2020 by Logitech
OS: Windows 10 Pro, Version 20H2, OS build 19042.685

Thank you for creating an issue!
I actually had the same problem with my work laptop today so I can at least reproduce it. My guess it that is has something to do with where Windows saves the last accessed data. Sometimes it seems to be in HKEY_CURRENT_USER and sometimes in HKEY_LOCAL_MACHINE. I think this sensor should actually check both and so does the microphone sensor.

Thank you for creating an issue!
I actually had the same problem with my work laptop today so I can at least reproduce it. My guess it that is has something to do with where Windows saves the last accessed data. Sometimes it seems to be in HKEY_CURRENT_USER and sometimes in HKEY_LOCAL_MACHINE. I think this sensor should actually check both and so does the microphone sensor.

Have the same issue on a dell Latitude laptop
Windows 10 20H1 (updated to 20H2 and still the same).
The webcam (Integrated webcam) and microphone (Realtek Audio) sensors appear to do nothing.
Tried teams (taskbar shows that something is using my mic) and windows camera app

Have the same issue on a dell Latitude laptop
Windows 10 20H1 (updated to 20H2 and still the same).
The webcam (Integrated webcam) and microphone (Realtek Audio) sensors appear to do nothing.
Tried teams (taskbar shows that something is using my mic) and windows camera app

Webcam Registry Key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\webcam
Microphone Registry Key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\microphone

the page you linked in your feature request, mentions about tracking history of usage. mine doesnt appear too

Webcam Registry Key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\webcam
Microphone Registry Key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\microphone

the page you linked in your feature request, mentions about tracking history of usage. mine doesnt appear too

Hi @rEs-84!
If you scroll down to the bottom on that settings screen, do you see more entries there? Do they have a date and time for last accessed?

Hi @rEs-84!
If you scroll down to the bottom on that settings screen, do you see more entries there? Do they have a date and time for last accessed?

I think I fixed it. Could any of you try this standalone release?

I think I fixed it. Could any of you try this standalone release?

yeah that seems to have done the trick.
Out of interest how are you detecting the webcam and mic are in use, still registry (but somewhere else?)
i'm only interested in the mic monitoring, to mute my radio when on calls.
I did have a few issues getting the new version to actually connect to mqtt, but I think killing the previous app running in the background as an admin account, might of resolved it. So i assume two copies cant be ran on same machine (not issue for me).
Maybe enable a taskbar icon so the app can be closed / config got to easily etc?

yeah that seems to have done the trick.
Out of interest how are you detecting the webcam and mic are in use, still registry (but somewhere else?)
i'm only interested in the mic monitoring, to mute my radio when on calls.
I did have a few issues getting the new version to actually connect to mqtt, but I think killing the previous app running in the background as an admin account, might of resolved it. So i assume two copies cant be ran on same machine (not issue for me).
Maybe enable a taskbar icon so the app can be closed / config got to easily etc?

The standalone install seems to have worked for me too!  Nice work!

The standalone install seems to have worked for me too!  Nice work!

Thanks for testing this both of you! I'm going to mark this as closed and the fix will be in the next release. If anyone comes across this, you can use the file I linked a few comments up if you don;t want to wait for next release.
@rEs-84, yes, it's still registry. The following sub registries are available:

I was only checking HKEY_LOCAL_MACHINE while some entries appear in HKEY_CURRENT_USER. This may have something to do with how application are installed, either as user or for the whole machine but I'm not sure about that.

Thanks for testing this both of you! I'm going to mark this as closed and the fix will be in the next release. If anyone comes across this, you can use the file I linked a few comments up if you don;t want to wait for next release.
@rEs-84, yes, it's still registry. The following sub registries are available:

I was only checking HKEY_LOCAL_MACHINE while some entries appear in HKEY_CURRENT_USER. This may have something to do with how application are installed, either as user or for the whole machine but I'm not sure about that.


Proposal: index/suffixarray: added functionality via longest common prefix array

What version of Go are you using (go version)?

$ go version
go version go1.13.1 linux/amd64

I have added an LCP array to the suffix array to provide the following functionality
func (x *Index) DistinctSubsCount() int
func (x *Index) DistinctSubs() [][]byte
func (x *Index) LongestRepeatedSubs() [][]byte

The LCP array is being initialized by once.Do() inside these methods, so existing users that don't need the new functionality won't have to deal with the overhead.
If this is something of interest, i will create a PR.
Cheers.

CC @griesemer
I suspect that we're going to consider the index/suffixarray package as complete.  It might be better to provide your changes as a library available for anyone who wants it.  https://golang.org/doc/faq#x_in_std

Agreeing with @ianlancetaylor : It is not that we're not interested in having more functionality, the problem is that by adding more functionality to the std library we're adding maintenance burden (to the Go team) for a library that is not super-widely used but of significant complexity.
Marking NeedsDecision for input from the proposal committee.

@griesemer should we perhaps mark this as a proposal so that we can gain visibility from the proposal review committee? I ask because proposal have been reviewed periodically but no response on this one. Thank you.

Marked as Proposal for visibility, per @odeke-em 's suggestion.

@petar-dambovaliev, I've been doing some index/suffixarray uses recently (including the recent optimizations) and it's true that lots of algorithms start with "compute the suffix array and the LCP array". If the code were not much more to maintain, it might be worth having in the package proper instead of delegating to third-party packages. I'm less certain about the API, but we can figure that out.
You said you could make a PR. How much code is it? I'm just curious what level of complexity we're talking about taking on. Thanks.

@rsc, the associated CL that @petar-dambovaliev made is at
https://go-review.googlesource.com/c/go/+/213758
On Wed, Apr 1, 2020 at 10:54 AM Russ Cox<EMAIL_ADDRESS>wrote:

@petar-dambovaliev https://github.com/petar-dambovaliev, I've been
doing some index/suffixarray uses recently (including the recent
optimizations) and it's true that lots of algorithms start with "compute
the suffix array and the LCP array". If the code were not much more to
maintain, it might be worth having in the package proper instead of
delegating to third-party packages. I'm less certain about the API, but we
can figure that out.
You said you could make a PR. How much code is it? I'm just curious what
level of complexity we're talking about taking on. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/36450#issuecomment-607399963, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABFL3VZH2AIUTG25DVKUAETRKN5WLANCNFSM4KEHHZ2Q
.

@petar-dambovaliev, I've been doing some index/suffixarray uses recently (including the recent optimizations) and it's true that lots of algorithms start with "compute the suffix array and the LCP array". If the code were not much more to maintain, it might be worth having in the package proper instead of delegating to third-party packages. I'm less certain about the API, but we can figure that out.
You said you could make a PR. How much code is it? I'm just curious what level of complexity we're talking about taking on. Thanks.

I am sure that when reviewed, you will have good ideas to improve on it.
At the moment it is 264 lines, including some tests and the generated code for 32/64 int slices.
The actual implementation is less than a 100 lines.

@petar-dambovaliev, thanks for sending the CL, and apologies for not getting back to this sooner. The world went haywire a bit in April. :-(
As I look at this, it seems like (1) generating the LCP efficiently is more subtle than the code in the CL, and (2) it's unclear what exactly to do with the LCP afterward.
For (1), the code in the CL is O(N²) - if you have a text of N x's, each inner loop of newLcp_NN takes on average N/2 steps, for a total of N²/2 = O(N²). There are linear-time algorithms for constructing the LCP, though. The algorithm by Kasai et al. uses an extra temporary array of N ints but only requires O(N) computation. And there are variants too, described at https://en.wikipedia.org/wiki/LCP_array#Efficient_construction_algorithms. It also appears that the SA-IS implementation used for constructing the suffix array itself can be adapted to construct the LCP during suffixarray.New, provided you know you need it ahead of time.
For (2), we don't expose the actual suffix array directly in the current package API - and that turned out to be a good choice, since it let us use int32 or int64 internally based on the data size - so it wouldn't make much sense to expose the actual LCP directly either. That higher-level API makes the LCP less useful than I had thought.
I could see one option would be to have an alternate constructor - NewLCP maybe - that returns an LCP-enabled *Index. Using NewLCP would mean incurring an extra 4N memory overhead for the in-memory Index (or 8N for very large texts) but would let index.Lookup run in O(log(N) + len(s) + len(result)) instead of O(log(N)*len(s) + len(result)) (note the + vs * after log(N) in those two expressions). I'm not convinced it would be worth the added API overhead of a new constructor and all the new code to make Lookup faster this way. Possibly, but possibly not.
That raises the question of what other new high-level API an LCP-aware suffixarray could provide, beyond the faster Lookup. I don't see much honestly. I see that in the CL there are three new functions:

LongestRepeatedSubs returns the longest repeated substrings from data.
DistinctSubs returns all the distinct substrings from data.
DistinctSubsCount returns the number of distinct substrings in data.

At first glance these don't seem widely needed, nor do they seem to fit into the "index" theme (this is index/suffixarray), and they also seem impossible in the general case to implement particularly efficiently.
In the worst case, LongestRepeatedSubs could return O(N) results (well, O(N/log N) but the constant factor makes it more like O(N)), meaning that you end up with potentially 24*N bytes of slice headers for an N-byte text.
Similarly, in the worst case, nearly all of the N²/2 substrings in a text are distinct, meaning DistinctSubsCount has to return the value N²/2. That value might not fit in an int or even an int64 for a large enough text. We'd need some kind of int128 representation on a 64-bit system. We could maybe do that for DistinctSubsCount, but then DistinctSubs has to return a [][]byte with length equal to that count, which is both quite large (24*N²/2 bytes of slice headers) and potentially impossible - there are no int128-len slices.
Why did you choose these three operations? In what contexts do they arise?
Thanks very much.

Based on the discussion above, this seems like a likely decline.

No change in consensus, so declined.


Rename name of tab with user / service listing

Release Playbook

[ ] Rebase against master
[ ] Code review
[ ] Merge into master
[ ] Verify changes at http://site-staging.convox.com
[ ] Promote release on site-production in the convox/production Rack

Thanks!


TypeError: node.kids is undefined

I ran into this error when I tried to use the Time Traveling Debugger (clicking on the wrench)
Running without the Time Traveling Debugger is fine.
The code I was running was from elm-architecture-tutorial
(example 5)
Stack Trace:
addAllToDict() debug.js:12136
forEach() self-hosted:211
addAllToDict() debug.js:12136
forEach() self-hosted:211
addAllToDict() debug.js:12136
forEach() self-hosted:211
addAllToDict() debug.js:12136
forEach() self-hosted:211
flattenSignalGraph() debug.js:12138
initAndWrap() debug.js:12191
make() debug.js:11666
init() mainEffects.elm:1391
Elm.fullscreen() mainEffects.elm:1274
initModuleWithDebugState() debug.js:11672
Elm.fullscreenDebug() debug.js:11596
 mainEffects.elm:12324

This has been reported many times. No new ticket is required, so please close it as a duplicate.
Some existing open tickets about this are https://github.com/elm-lang/elm-reactor/issues/145 and https://github.com/elm-lang/elm-reactor/pull/149 (and there are various closed duplicates as well).

oops sorry


I presume this doesn't work on most COTS hardware?

I'm here exploring LLM's and while looking at T5 on their repo page, it said to come here.
I'm interested in Q/A systems, I know there are other model's available that do run on COTS, just asking for those who wish to run on premise equipment and/or if there will be a COTS available version of T5X that can run on COTS.

It will work on GPUs, they must have tensors though. I think all TI Nvidia GPUs have tensor processors. You cannot perform training for LLM on basic on premise hardware and expect it to finish this year.


Color picker: disable other hovers

Refs: #31457
I understand that currently there is some limiation and you can not stop the other hover from showing up, however this is confusing as the other hover seems to be a part of the color picker (in the example below: "color of an element's text")
Like debug, when you are showing the color picker you should disable the regular hover.
Assigning to July for discussion.

We can disable other hover messages to pop up but I think it is not fair to block other hovers just because we decided to show colour picker. I find it's quite useful to see other message to know what over what the color picker is opened against.

If you decide that the best experience for the user is to see both then we need a more clear seperation.
Currently due to the size of the color picker the small hover feels like it belongs to the color picker

That's the idea we stuck to when moved color picker to a hover. That's why I would say we keep it as-designed, but I can add more clear separation. Do you think bigger bottom border would be enough or you have a better idea?

If you can not hide it then maybe leave it as it is.
Let's also ping @joaomoreno and @jrieken to get their inpu

I can hide it, no problem, though we discussed not to with @joaomoreno. Lets leave it for a discussion and move to the next milestone.

Not going with this for now.


How to disable sorting and editable feature from the excel sheet

@paulhodel : How to disable sorting and editable feature from the excel sheet created on the browser ?

columSorting:false
editable:false

Its not working Paul ? should i need to replace my jquery,excel.js file again ?

Yes, you should update and get the most recent version.
On Tue, May 23, 2017 at 4:44 AM, gulshan-escalon<EMAIL_ADDRESS>wrote:

Its not working Paul ? should i need to replace my jquery,excel.js file
again ?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/paulhodel/jexcel/issues/11#issuecomment-303282529,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFvagapka1dJeroNkcudeo3l9p35DXbcks5r8lYMgaJpZM4Nh25V
.


Fix total file size on snackbar

This requires you to get file size data from watch.

adding total filesize to receiving files

completed with pull request #24


Can't use container blocks as nouns

"poka pi jan ante":

Yes, this has pained me for some time too; it occurs also in phrases like: "mi wile jo e tomo tawa sina", which the renderer now interprets as "I want to have a house, according to you.", because it renders tawa as the preposition-container, while sometimes you mean: "I want to have your car."
Your case seems quite simple to solve: before "pi" you always get the noun-glyph and not a container-glyph. Maybe there are more cases like that? Can you think of any?.. maybe the same before "en" or "anu".
For other cases, such as my example above it is more difficult, because the language is just ambiguous about what the noun-phrase is. I can imagine then to introduce a way to help the renderer by (optionally) stringing noun-phrases: "mi wile jo e tomo-tawa-sina."


Specify only partial config

Is it possible to use the default inspircd.conf file but then also load a custom config which specifes only a few settings (e.g. opers, permanent channels..) without the inspircd.conf file being present when the container first starts?
I've tried with an arbitrary file in the /conf directory but it isn't loaded. I've also tried with an existing file (opers.conf) but it is overwritten on first run.
Example: /ircd/conf/site.conf contains:
<permchannels channel="#help" modes="nt" topic="Help.">
Then run:
docker run -d -p 6667:6667 -v /ircd/conf/:/inspircd/conf/ inspircd/inspircd-docker

Currently it's not possible, but I'm working on an implementation.
Right now you can only get a copy of the config by provide the directory and then modify it as you need.
Pull requests are welcome :)

Great, thanks for letting me know. I can stop pulling my hair out thinking it should work.
Only idea I had now was to check for another environment variable which holds the name of additional config to load and check this in the config.sh - but I don't think it would work since config.sh runs before all the modules are loaded.

In general it's not a problem. The config for modules is loaded during the module initialization or later. And this is way after the whole config is read and parsed by InspIRCd.
So feel free to modify the config.sh. But in general as already mentioned: Simply load the mount the modified config is the easiest way.
If you want to run it in Swarm-mode or something, you can also build in your own config.

I appreciate your time, just wanted to mention that it seems to be  necessary to include the customised inspircd.conf file before the container is ran for the first time. What I was doing was running the image so that it would populate the volume, then modifying the files in the volume and restarting the container.
This would produce cryptic error messages like Syntax error - start of tag expected at /inspircd/conf/inspircd.conf:542:1 (last tag was on line 534) which made me think I had some problem with my changes.
So I'm now storing inspircd.conf, modules.conf et al modifed as required and usingCOPY conf/*.conf /conf/ in my Dockerfile so that the config files are pre-populated.

This is in general not a problem of the docker image. It's a InspIRCd "bug". Locateded here: https://github.com/inspircd/inspircd/blob/insp20/src/configparser.cpp#L268-L269
It's part of the config parser and as work around you can simply delete the last comment section or add a line break a the end (iirc this solves the problem). Maybe @Adam- can tell us more details.
In general the image is build to simply allow you to add your configs by extending it.
You can use a Dockerfile like this one:
FROM inspircd:latest
COPY conf/ /inspircd/conf/

Simply place this Dockerfile into a directory and your configs into a sub directory called conf. That's it :)

A fix is incoming: #48
I currently think about what's the perfect solution. Because right now loading modules possibly fails because m_md5 and other "required" modules are loaded afterwards.
Feel free to test it :)

Works for me!


[BUG possibly] loading & playing of samples in project spits errors

ive recently ran into this when on a xcode project, not playground. i can set up playgrounds. but was running into this just when 3.6 happened
the project, again, is super duper simple. just a loading of a sample to play [wav]. but even just before the 3.6 release, the sample would not even play, no sound. which i could not understand. but now it errors, on a clean new project
import Cocoa
import AudioKit

class ViewController: NSViewController {
  let sampler = AKSampler()
  override func viewDidLoad() {
    super.viewDidLoad()
    do {
      try sampler.loadWav("idle")
      sampler.amplitude = 0.5
      sampler.play()
    } catch {
      AKLog("NOT LOADED DAWG")
    }
    AudioKit.output = sampler
    AudioKit.start()
  }

  override var representedObject: Any? {
    didSet {
    // Update the view, if already loaded.
    }
  }
}

& this is the error that spits out in the console, no matter what
2017-04-08 13:20:51.705912+0100 SampleLayer[7795:82471] [central] 54:   ERROR:    >avae> AVAudioUnitMIDIInstrument.mm:105: -[AVAudioUnitMIDIInstrument startNote:withVelocity:onChannel:]: error -10867
2017-04-08 13:20:51.706105+0100 SampleLayer[7795:82471] Failed to set (contentViewController) user defined inspected property on (NSWindow): error -10867

as said before, the sample just didnt play, for some reason before 3.6. but now it doesnt play & errors in the console

i am using latest xcode 8.3.1. if that by chance may help. also this is a macOS app, not iOS

i have just tried in the same project, the oscillator. that worked perfectly. no errors popping up in the console when running. i did comment out the sampler code obviously, as it would not run properly with it in still

Trying to play before starting AudioKit... try this:
  override func viewDidLoad() {
    super.viewDidLoad()
    do {
      try sampler.loadWav("idle")
      sampler.amplitude = 0.5
    } catch {
      AKLog("NOT LOADED DAWG")
    }
    AudioKit.output = sampler
    AudioKit.start()
    sampler.play()
  }


Set up handlebars templates for display of items and prices.

when an item and price are displayed, store the id # of that item as a non-visible property in the template.

index is working

single search is in progress


url is truncatured when url contain querystring

when my url is https://velivole.b-cdn.net/maptiler-osm-2017-07-03-v3.6.1-europe.mbtiles?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=SU4RTA768YPOWD1Q4GTP%2F20240129%2Fus-east-1%2Fs3%2Faws4_request&Signature=0d7a3d8a439e9f0d4e0d3941bd50c14fc716a37e44ac45f0c0ffcfa320c79e89
the request url is changed to https://velivole.b-cdn.net/maptiler-osm-2017-07-03-v3.6.1-europe.mbtiles

You should use encodeURIComponent on your URL:
import { createSQLiteThread, createHttpBackend } from 'sqlite-wasm-http';

const httpBackend = createHttpBackend({
  maxPageSize: 1024,
  backendType: 'sync' || undefined,  // <- select one
  timeout: 45000
});
const msg = await createSQLiteThread({ http: httpBackend })
  .then((db) => db('open', {
    filename: 'file:' + encodeURIComponent(remoteURL),
    vfs: 'http'
  }));
assert.equal(msg.type, 'open');
assert.strictEqual(decodeURIComponent(msg.result.filename), 'file:' + remoteURL);

? has special meaning in SQLite, do not forget that SQLite does not have any notion of HTTP - for SQLite you simply pass a filename that SQLite passes to a VFS driver that expects an URL.

As you may have seen from my profile, I have been living on social welfare for the last 3 years - eating with a few euros per day - and I expect to lose my home in the coming months. This is because of an extortion involving the French police and judiciary which included people simultaneously posting messages with content related to my sex life at my previous two employers. Currently, I am being offered a new job only if I accept that people around me continue to do this - without me saying anything - and only if accept a job at an employer chosen by the organizers of the extortion - because most companies refuse to do this. In order to further intimidate me, people are posting simultaneously issues and pull requests in all of the projects that I work in.
You have posted this issue simultaneously with @sifat-at-work. Is it because you are taking part in the extortion?

thank you for your help.
i don't know about this matter, i am just an ordinary software developer.

thank you for your help.
i don't know about this matter, i am just an ordinary software developer.

thank you for your help.
i don't know about this matter, i am just an ordinary software developer.


export 'default' (imported as 'core_1') was not found in '@angular/core'

Type of Issue
[x] Bug Report
[ ] Feature Request

Versions
ng-packagr: v1.5.0-rc.1
node: v6.11.0
@angular: v4.4.6
rxjs: 5.5.0
zone.js: 0.8.18

Description
When packaging my library i get the following warning:
'default' is not exported by 'node_modules\redux\es\index.js'
'default' is imported from external module 'rxjs/add/operator/let' but never used
'default' is imported from external module 'rxjs/add/operator/distinctUntilChanged' but n
'default' is imported from external module 'rxjs/add/operator/map' but never used
'default' is imported from external module 'rxjs/add/operator/filter' but never used
'default' is imported from external module 'rxjs/add/operator/switchMap' but never used

and when using my library in an application, i get the following warnings:
"export 'default' (imported as 'core_1') was not found in '@angular/core'

Here's my setup:
ng-package.json
{
  "$schema": "./node_modules/ng-packagr/ng-package.schema.json",
  "src": "lib",
  "dest": "dist/lib",
  "workingDirectory": ".ng_build",
  "lib": {
    "entryFile": "public_api.ts",
    "externals": {
      "oidc-client": "./node_modules/oidc-client/dist/oidc-client.min.js",
      "rxjs/add/operator/let": "Rx.Observable.prototype"
    }
  }
}

public_api.ts_
export * from './my-lib/my-lib.module'
tsconfig:
{
  "compileOnSave": false,
  "compilerOptions": {
    "outDir": "./dist/src",
    "baseUrl": "src",
    "paths": {
      "my-lib": [
        "dist/lib"
      ]
    },
    "sourceMap": true,
    "declaration": false,
    "moduleResolution": "node",
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "target": "es5",
    "typeRoots": [
      "node_modules/@types"
    ],
    "lib": [
      "es2017",
      "dom"
    ]
  }
}

I haven't been able to reproduce the issue in an example app
and I cannot make any sense of this but I hope you might.
Thanks

Hi there,
I have the same issues.
If any help is available, it will be greatly appreciated.
Regards

try changing your externals to
"externals": {
   "oidc-client": "oidc-client",
   "rxjs/add/operator/let": "Rx.Observable.prototype"
}

Hi @DavidParks8 . I tried what you suggested, unfortunately it didn't have any effect.

@IThordGray have you been able to reproduce the issue in an example app? Or do you have any idea what it might be ?

Hi @ams-itm . Did you got a solution ?

Hi @andrepesi. No, I have not.  If somebody could reproduce the issue it would be great.
Perhaps @dherges could pitch in?

@ams-itm I has created a new project, without "rxjs" dependencies and the error not happened. I am sure that error is about external dependencies references .

@andrepesi I agree. Could you provide this example project? It would help a lot!

@ams-itm Experiencing the same problem, its related to angular-redux on how its is bundled i believe. seems it fails to import angular/core

Thanks for the response @Gandii. I solved it by packaging it using this guide (without ng-packagr) https://www.usefuldev.com/blog/post/publishing-a-library-from-an-angular-cli-project

I'm having the same problem, unfortunately the useful dev link is not working for our implementation. Any ideas of potential fixes/ places to look for fixes would be appreciated.

Hi everyone,
do you have a GitHub repo so that I can reproduce the error?
Is it that an export default ... from TypeScript causes an error in rollup?

Hi everyone,
do you have a GitHub repo so that I can reproduce the error?
Is it that an export default ... from TypeScript causes an error in rollup?

@dherges I have not been been able to replicate the issue.

I got the same issue
WARNING in ./node_modules/ng-sp-lib/ng-sp-lib.js
29091:32-38 "export 'default' (imported as 'core_1') was not found in '@angular/core'
    at HarmonyImportSpecifierDependency._getErrors (C:\Projects\app\node_modules\webpack\lib\dependencies\HarmonyImportSpecifierDependency.js:65:15)
    at HarmonyImportSpecifierDependency.getWarnings (C:\Projects\app\node_modules\webpack\lib\dependencies\HarmonyImportSpecifierDependency.js:39:15)

the top of lib
import core_1, { ApplicationRef, ChangeDetectionStrategy, ChangeDetectorRef, Component, ComponentFactoryResolver, Directive, ElementRef, EventEmitter, Host, HostBinding, HostListener, Inject, Injectable, Injector, Input, NgModule, NgZone, Output, ReflectiveInjector, Renderer, TemplateRef, ViewChild, ViewContainerRef, ViewEncapsulation, forwardRef, isDevMode } from '@angular/core';

@ams-itm Sorry for replying only now. I changed gears completely and moved away from ng-packagr and followed some articles online, where I created my own packager seed. I didn't quite follow any of the threads there after.

Experiencing same issue here, not sure why exactly, we'll try to set up a repro repository as soon as we find the exact reason.

Ok I managed to prepro and pinpoint the exact use case for this error. I'll have the repro repository ready tomorrow at the latest. This thing wasn't easy to chase down very obscure error.

Sorry, I was able to reproduce this on two projects at work, the problem was with interface imports from VideoGular2 library, but when I tried to repro on a simplified open source version (here: https://github.com/avatsaev/ng-packagr-issue210-repro), everything was compiling fine, I think it happens due to combination with some other third party libs, I'm not sure which one(s) yet, I'll keep trying them one by one and I'll update here when I find it.

I think it's due to some third party libraries not respecting the Angular Library Format, so the imports you use from the lib, screws with the angular compiler (or webpack).
Here a solution I've found to debug, find out which lib breaks the transpilation, and fix the problem.
Suppose I have my-lib project that compiles with ng-packagr into dist/lib folder
After compilation in dist/lib/my-lib.js there is a problem with imports (core is not imported correctly):

Fist step is to figure out which lib is breaking everything so just control+F and look where core is used:

So one of the imports from TimeAgoPipe library is breaking the compilation

Project wide search (ctrl+shif+f 'time-ago-pipe') I only import from time-ago-pipe lib once:

So the solution in this case is to add the entire import path into externals in ng-package.json (if you have other imports from this lib add them too):

After which everything compiles fine:

The most confusing part of this bug is not knowing where the error comes from, because the ng-packagr packages the lib just fine, without warnings and spitting out an error.

Hi @avatsaev,
cool you figured out more! Is it possible for you to publish a repro on GitHub?
Does it originate from a import * as core from '@angular/core'?

@avatsaev hit the spot. I followed his instructions and was able to solve it.

For me this happened because I didn't have my compilerOptions.module set in tsconfig.json, which resulted in commonjs being used as default (for targets es3 or es5).
Setting it to es6 fixed it for me.
Relevant part:
{
  "compilerOptions": {
    "module": "es6"
  }
}

Thanks @markus-wa Your solution worked for me. 'es2015' worked for me.
Angular Version: 8.2.14
{   "compilerOptions": {     "module": "es2015"   } }

Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent ng-packagr version.
If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.


Requesting details or documentation about adding images to android game so that their size will adjust according to screen size

Issue details
I am creating an android game using libgdx and I use some images in some of the windows. I am placing my images in the window like following.
          screenWidth = Gdx.graphics.getWidth();
          screenHeight = Gdx.graphics.getHeight();
          batch.draw(playImage, screenWidth / 2 - texture.getWidth() / 2, screenHeight / 4 - texture
                   .getHeight() / 2);
           font.draw(batch, message, screenWidth / 2 - layout.width / 2, 5 * screenHeight / 8 -
                   layout.height / 2);

Will this give any issues when I use a different screen size? If so how should I handle this kind of scenario? Is there any documentation or tutorial on how to do this?
Please select the affected platforms

[x ] Android
[ ] iOS (robovm)
[ ] iOS (MOE)
[ ] HTML/GWT
[ ] Windows
[ ] Linux
[ ] MacOS

Please use the forums or the irc channel. https://github.com/libgdx/libgdx/wiki/Issue-Tracker


Moving FIRAnalyticsConfiguration calls to Analytics.

These APIS are specific to the Analytics SDK and have been moved there.
The instance methods have become static methods on the FIRAnalytics
class.
Should not be submitted until the internal Analytics changes land.

This is the first half of #1785 - the second half is removing it entirely.

Submitting since Travis is just running on the CHANGELOG change.


Editing growthBoost

No longer boost coin production, now makes plant older by pushing planted at time earlier
Limit between when you can water should be about a minute


A few things that stop an import

numberOfEditions is a Number field, when the value was -1 the code logged:
2017/03/12 23:19:56 [error] [plugin] [Forced] Books lists: {"numberOfEditions":["Number of editions is too small (minimum is 0)."]}

bookImages was an Asset field, when the import value was an array containing 2 identical URLs the task would get stale.
"bookImages": [
  "https://domain.com/path/to/image_1.jpg",
  "https://domain.com/path/to/image_1.jpg"
]

What version of Feed Me are you on? No validation errors come up for the Number field with a minimum value set. Can you confirm if you were uploading these URLs into your Asset field?

version 2.0.1 (Pro)
On the Number field, was a minimum value set to "0".
For the Asset field I use: "Upload files from urls (replace existing)"

And when you mention stop an import, how are you running the feed - using Run Feed, or using the direct link? Errors like these are supposed to show at the end of feed processing, and shouldn't stop an import from running mid-import. I'll try to replicate again.

I run imports using "Run Feed".
I've just ran a 200 product import and the task gets stale:
[20-Mar-2017 12:41:47 UTC] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 1462272 bytes) in /../craft/app/vendor/lsolesen/pel/src/PelJpeg.php on line 584

I've allocated more memory and I get the same error, current memory memory_limit => 1024M => 1024M.
Below is an example product item. I'm under NDA can't share the exact image / URL, it's a 1.5mb image.
{
  "status": "publish",
  "id": "42715",
  "title": "Dodger",
  "bookAuthor": "Terry Pratchett",
  "bookCategories": [
    "Childrens & YA"
  ],
  "bookDescription": "...",
  "bookEditionType": [],
  "bookNumberOfEditions": 0,
  "bookFeatures": [],
  "bookFormat": "hardcover",
  "bookImages": [
    "https://UNDERNDA/wp-content/uploads/2017/02/IMG_6967.jpg"
  ],
  "isBookRecommended": false,
  "bookIsbn": "9780385619271",
  "bookPrintingType": "ukFirstEditionFirstPrinting",
  "bookPublicationDate": "Thu, 13 Sep 2012 03:00:00 +0300",
  "bookPublisher": "Doubleday",
  "bookSignatureType": "unsigned",
  "bookTags": [
    "Fantasy"
  ],
  "bookOfTheMonthDate": "",
  "bookOfTheMonthDescription": "",
  "isBookOfTheMonth": false,
  "bookRareDescription": "",
  "permalink": "https://UNDERNDA/product/dodger-2/",
  "price": "25",
  "regularPrice": "25",
  "stock": 1,
  "gallery": "",
  "createdAt": "1424100303",
  "productImageGallery": "",
  "featured": "no",
  "slug": "dodger-2",
  "availabilityDatetime": "",
  "whenToCharge": "",
  "postDate": "Mon, 16 Feb 2015 17:25:03 +0200",
  "sku": "WS7XMMHA",
  "isEnabled": true,
  "bookAuthors": [
    "Terry Pratchett"
  ]
}

Have you looked at the Performance FAQ?
Having said that, I've never seen the reference to /../craft/app/vendor/lsolesen/pel/src/PelJpeg.php, so thats new. Have you tried this import with your image field un-mapped?

😆 sorry, I removed sensitive data from the path -> /../craft/app/vendor/lsolesen/pel/src/PelJpeg.php.
If I remove the image URL from bookImages, it imports the product.

I just meant if you select "Don't Import" for the Asset field you're importing bookImages into - and it sounds like thats the issue. Images are actually downloaded without loading them into memory first, so it shouldn't raise errors.
I bit tricky to debug without seeing your environment and data, but understand thats under a NDA. I'll see if I can come up with anything after some more testing.

I think is a memory related issue.
When I try to import a 200 product list, the import task gets stale at item number 126. I ran the same task 4 times and it gets stuck importing item 126. If I remove the first 125 products, the tasks finishes without problems.
So is not a FeedMe issue, what I don't know is how the image import works, maybe it loads all the images in memory and doesn't free it, somehow. The images I have imported are ~2mb.

Its Feed Me that does the image importing from a remote url, so I believe it still might be a Feed Me issue. I can do some further testing to identify memory leaks, but for the time-being, if you can limit your items to 100-125 that might work in the interim.


Trigger connection sweeping

Reenables connection sweeping, fixes #1844. Additionally log messages have been added as well.

bors r+


Svg relative

Updating all SVG urls as relative.

Resolves: MWPW-126739
Test URLs:

Before: https://main--dc--adobecom.hlx.page/acrobat/online/pdf-to-ppt?martech=off
After: https://main--dc--adobecom.hlx.page/acrobat/online/pdf-to-ppt?martech=off&milolibs=svg-relative

QA note: Before URL also won't show the issue until you change it as .live or production URL.
Since milolibs will not work for .live nor production, this is tricky to test. When I tested locally, it seems solid.

Closing this due to https://github.com/adobecom/milo/pull/508 from Chris M.


jpeg-js updated

Hi, jpeg-js is available as version 0.1.1 which fixes at least a annoying bug with jpeg files that store the quantization tables not before the actual frames.
Is there a chance that you update the package.json of jump to let it depend on the newer jpeg-js?
Thanks, Anton

Done and made a new release.


fix: spec.yaml wasn't always being skipped

Background: there's a special case in abc where the spec.yaml file isn't included in the template output, even if there's an include for path .. It turns out this was buggy, and is being fixed here.
Since we were comparing unnormalized paths to normalized paths, we'd sometimes overlook that ./spec.yaml and spec.yaml were the same file. The visitor function provided to copyRecursive was being called with the output of filepath.Rel(), which calls filepath.Clean() implicitly. But the blocklist was being initialized with un-Clean()ed paths. So the fix is just to Clean() the path before adding it to the blocklist.
cc @kevya-google who noticed and reported this.

This is obsolete and unnecessary since #141, closing.


Added multirobot test

Added multirobot test
If you want to see GZ gui: export SHOW_GZ_GUI=1
Try this new test with:
colcon test --merge-install --event-handlers console_direct+ --packages-select vehicle_gateway_integration_test --ctest-args -R test_takeoff_land_multirobot_x500

@codebot I have the same issue the other day, I recompiled everything and now it's working. I think it's related with a message type which is different for some reason, the message was updated but the code was not recompiled.


Slugs for translations

Hi I would like to use this package but I have a question. I have a project here at work were we Properties which will need to be translated and therefore the Title of a property is in another table like so:

properties Table
    id
    address
    featured_image_id
    ...

property_translations Table
    id
    property_id
    language_id
    title
    slug
    ...

How can I use this package to create the slugs since the slugs are in a pivot table?

I'll be honest, I've never tried this myself.  I know there were some previous issues regarding doing this, so I feel it's possible.
If you use a custom pivot model, you can always apply Sluggable to it instead of the Properties model.

i used dimsav plugin.You must add to 'property_translation' class.

protected $sluggable = [
        'build_from' => 'slugsomewhere',
        'save_to'    => 'slug',
    ];

public function getSlugsomewhereAttribute(){
        //implement your code, choose the var you wanna use as slug
       //query pivot tables and find it
       $res = your_implementation;
        return $res;
    }

it works with relationships too.

Version 4.0 of the package supports slugging to multiple fields on the same model.  This is likely what you could use.

Slugging to multiple fields on the same model will produce something like this:
test-en (for locale en), test-hr (for locale hr), ...
But that's not an option for me.
I would like to get (if it's possible with current package):
test (for locale en), test (for locale hr), ...
Is there a way to create uniqueness to multiple fields? (in case that names for 2 different locales are the same, but that won't be always the case)
For example: 'unique' => ['name', 'locale']

I’m on vacation so don’t have access to anything but my phone right now. However, I think the section in the docs about modifying the unique scope constraint is probably what you need.


Add target URL to details.txt file

https://github.com/microbit-foundation/DAPLink/tree/details_url

Implemented by the Mbed team and in master already.


fix arm system panic

What type of this PR
Add one of the following kinds:
/kind bug
What this PR does / why we need it:
func-routine.goid don't support arm system
Which issue(s) this PR fixes:
Fixes #
Specified Reivewers:
/assign @your-reviewer

/approve


Will Apple reject the app if I use fishhook in app?

I have to use fishhook do some work,  Will Apple reject the app if I used fishhook in my app?    may I have a answer, many thanks.

Hi @GangWang
Unfortunately, you can expect that an app submission including fishhook will be rejected.

It's impossible to know for sure, but as @kastiglione said, we wouldn't suggest it.

;)  thanks,    well,   I guess there is no other way to hook c function in my app, is there?

Hi @GangWang
did you commit your app to appstore with including fishhook?
is that rejected by appstore?


My app doesn't work on a server

I have created a chat-app with your tutorial. It works just fine on a local host, but it doesn't work after deployment. The app - https://my-chat-26e48.firebaseapp.com/

It doesn't seem anything was deployed. Could you paste the output from the firebase deploy command?

I've tried to resolve the situation myself and something went wrong )) Yet, I've made a new project and used the code from the "web" folder - it works just fine. So it's my mistake, I'll try to figure out what I did wrong. Thanks for answering in such a short notice.

I'm glad to hear this. Cheers!


Set nginx to support redirection from http to https

Example use case:
apps:

server_name: www.test.com default_server
http_port: 443
docroot: /var/www/test.com/current
server_name: www.test.com
http_port: 80 default_server
redirect_to_https: true

We already have this feature in sslterminator role.
See https://github.com/wunderkraut/WunderMachina/blob/master/playbook/roles/sslterminator/defaults/main.yml#L15 for examples.
That might however need some better examples / explanation as it is not indeed clear that it would do that :D


Android Support

Hi,
I want to use this inside Android, is it supported?
Thanks

I used it inside Android，but when Compile，there is a erro message ：
Error:Error converting bytecode to dex:
Cause: Dex cannot parse version 52 byte code.
This is caused by library dependencies that have been compiled using Java 8 or above.
If you are using the 'java' gradle plugin in a library submodule add
targetCompatibility = '1.7'
sourceCompatibility = '1.7'
to that submodule's build.gradle file.

@dzx1994 which version have you used?

I used the lastes version，and i used JDK 1.8。

@dzx1994 Please try to use 2.7.3 version for Android, because only 2.x.x line Android compatible.

OK，thanks，i will try it next tomorrow。


v86 for 64-bit

Consider we do know it's possible to do 64-bit architectures as JSLinux has done, I think it's natural progression we also provide 64-bit support as well - which could be toggleable at the native side that handles the emulation.

https://github.com/copy/v86/issues/133


SOLR-16641 - Generate gradle.properties from template

This is a duplicate of #1320 atm, I just want to test the crave.io check

Sorry for adding the review here instead of #1320, it was a mistake. I can add it there if you want, or I'll wait a few days to see how that PR evolves and review again.

Sorry, I'll close this one but I'll remember the comments on it


Release build both Android and iOS crash the app

Describe the bug
Locally both the Android and iOS apps work perfectly but when moving to a release build when joining the room both apps (Android and iOS) crash the app.
The error is the same on both platforms:
2023-06-18 18:42:46.665396+0300 uHubs Dev[8610:509463] [javascript] TypeError: undefined is not an object (evaluating 'r(d[8]).Room')

and
CTFatalException: Unhandled JS Exception: TypeError: this.methodFactory is not a function. (In 'this.methodFactory(a,t,n)', 'this.methodFactory' is undefined)', reason: 'Unhandled JS Exception: TypeError: this.methodFactory is not a function. (In 'this.methodFactory(a,t,n)', 'this.methodFactory' is undefined),

To Reproduce
Steps to reproduce the behavior:

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

(4) #Logcat ERROR
2023-06-18 18:24:42.067 27745-27813/? E/ReactNativeJS: TypeError: undefined is not an object (evaluating 'r(d[8]).Room')

    This error is located at:
        in Unknown
        in Unknown
        in Unknown
        in Unknown
        in RCTView
        in Unknown
        in RCTView
        in Unknown
        in RCTView
        in Unknown
        in Unknown
        in RCTView
        in Unknown
        in f
        in Unknown
        in PanGestureHandler
        in Unknown
        in RCTView
        in Unknown
        in f
        in Unknown
        in RCTView
        in Unknown
        in G
        in Unknown
        in RNSScreen
        in f
        in Unknown
        in M
        in P
        in Unknown
        in RNSScreenContainer
        in ScreenContainer
        in Unknown
        in D
        in T
        in Unknown
        in RCTView
        in Unknown
        in Unknown
        in H
        in Unknown
        in Unknown
        in Unknown
        in Unknown
        in Unknown
        in RCTView
        in Unknown
        in RCTView
        in Unknown
        in RCTView
        in Unknown
        in Unknown
        in RCTView
        in Unknown
        in f
        in Unknown
        in PanGestureHandler
        in Unknown
        in RCTView
        in Unknown
        in f
        in Unknown
        in RCTView
        in Unknown
        in G
        in Unknown
        in RNSScreen
        in f
        in Unknown
        in M
        in P
        in Unknown
        in RNSScreenContainer
        in ScreenContainer
        in Unknown
        in D
        in T
        in Unknown
        in RCTView
        in Unknown
        in Unknown
        in H
        in Unknown
        in Unknown
        in Unknown
        in Unknown
        in Unknown
        in Unknown
        in RCTView
        in Unknown
        in k
        in RNSScreen
        in f
        in Unknown
        in M
        in P
        in Unknown
        in RNSScreenContainer
        in ScreenContainer
        in Unknown
        in H
        in Unknown
        in Unknown
        in Unknown
        in Unknown
        in Unknown
        in RCTView
        in Unknown
        in RCTView
        in Unknown
        in RCTView
        in Unknown
        in Unknown
        in RCTView
        in Unknown
        in f
        in Unknown
        in PanGestureHandler
        in Unknown
        in RCTView
        in Unknown
        in f
        in Unknown
        in RCTView
        in Unknown
        in G
        in Unknown
        in RNSScreen
        in f
        in Unknown
        in M
        in P
        in Unknown
        in RNSScreenContainer
        in ScreenContainer
        in Unknown
        in D
        in T
        in Unknown
        in GestureHandlerRootView
        in Unknown
        in H
        in Unknown
        in Unknown
        in Unknown
        in Unknown
        in Unknown
        in Unknown
        in c
        in RNCSafeAreaProvider
        in Unknown
        in s
        in C
        in n
        in Unknown
        in RCTView
        in Unknown
        in RCTView
        in Unknown
        in C
2023-06-18 18:24:42.070 27745-27813/? I/ReactNativeJS: { error:
       { [TypeError: undefined is not an object (evaluating 'r(d[8]).Room')]
         componentStack: '\n    in Unknown\n    in Unknown\n    in Unknown\n    in Unknown\n    in RCTView\n    in Unknown\n    in RCTView\n    in Unknown\n    in RCTView\n    in Unknown\n    in Unknown\n    in RCTView\n    in Unknown\n    in f\n    in Unknown\n    in PanGestureHandler\n    in Unknown\n    in RCTView\n    in Unknown\n    in f\n    in Unknown\n    in RCTView\n    in Unknown\n    in G\n    in Unknown\n    in RNSScreen\n    in f\n    in Unknown\n    in M\n    in P\n    in Unknown\n    in RNSScreenContainer\n    in ScreenContainer\n    in Unknown\n    in D\n    in T\n    in Unknown\n    in RCTView\n    in Unknown\n    in Unknown\n    in H\n    in Unknown\n    in Unknown\n    in Unknown\n    in Unknown\n    in Unknown\n    in RCTView\n    in Unknown\n    in RCTView\n    in Unknown\n    in RCTView\n    in Unknown\n    in Unknown\n    in RCTView\n    in Unknown\n    in f\n    in Unknown\n    in PanGestureHandler\n    in Unknown\n    in RCTView\n    in Unknown\n    in f\n    in Unknown\n    in RCTView\n    in Unknown\n    in G\n    in Unknown\n    in RNSScreen\n    in f\n    in Unknown\n    in M\n    in P\n    in Unknown\n    in RNSScreenContainer\n    in ScreenContainer\n    in Unknown\n    in D\n    in T\n    in Unknown\n    in RCTView\n    in Unknown\n    in Unknown\n    in H\n    in Unknown\n    in Unknown\n    in Unknown\n    in Unknown\n    in Unknown\n    in Unknown\n    in RCTView\n    in Unknown\n    in k\n    in RNSScreen\n    in f\n    in Unknown\n    in M\n    in P\n    in Unknown\n    in RNSScreenContainer\n    in ScreenContainer\n    in Unknown\n    in H\n    in Unknown\n    in Unknown\n    in Unknown\n    in Unknown\n    in Unknown\n    in RCTView\n    in Unknown\n    in RCTView\n    in Unknown\n    in RCTView\n    in Unknown\n    in Unknown\n    in RCTView\n    in Unknown\n    in f\n    in Unknown\n    in PanGestureHandler\n    in Unknown\n    in RCTView\n    in Unknown\n    in f\n    in Unknown\n    in RCTView\n    in Unknown\n    in G\n    in Unknown\n    in RNSScreen\n    in f\n    in Unknown\n    in M\n    in P\n    in Unknown\n    in RNSScreenContainer\n    in ScreenContainer\n    in Unknown\n    in D\n    in T\n    in Unknown\n    in GestureHandlerRootView\n    in Unknown\n    in H\n    in Unknown\n    in Unknown\n    in Unknown\n    in Unknown\n    in Unknown\n    in Unknown\n    in c\n    in RNCSafeAreaProvider\n    in Unknown\n    in s\n    in C\n    in n\n    in Unknown\n    in RCTView\n    in Unknown\n    in RCTView\n    in Unknown\n    in C',
         isComponentError: true,
         line: 2257,
         column: 1065,
         sourceURL: 'index.android.bundle' } }

2023-06-18 18:24:42.840 27745-27813/? E/ReactNativeJS: TypeError: this.methodFactory is not a function. (In 'this.methodFactory(a,t,n)', 'this.methodFactory' is undefined)

    --------- beginning of crash
2023-06-18 18:24:42.850 27745-27814/? E/AndroidRuntime: FATAL EXCEPTION: mqt_native_modules
    Process: io.uhubs.development, PID: 27745
    com.facebook.react.common.JavascriptException: TypeError: this.methodFactory is not a function. (In 'this.methodFactory(a,t,n)', 'this.methodFactory' is undefined), stack:
    n@2258:1061
    setLevel@2258:2040
    r@2258:2577
    i@2258:2595
    <unknown>@2258:3019
    d@2258:3033
    <unknown>@2258:395714
    h@2:1585
    d@2:958
    <unknown>@2257:1058
    Nr@81:45962
    RoomPage@2257:1034
    wr@81:42144
    Hl@81:89901
    Ba@81:79143
    Oa@81:79045
    ja@81:78810
    Ia@81:75972
    Ia@-1
    <unknown>@81:26350
    unstable_runWithPriority@144:3806
    ht@81:26297
    pt@81:26232
    Pa@81:73345
    Vr@81:47944
    Vr@-1
    <unknown>@903:465
    <unknown>@914:548
    <unknown>@914:548
    <unknown>@914:548
    <unknown>@920:747
    t@918:289
    k@916:477
    <unknown>@916:611
    <unknown>@2113:2520
    generatorResume@-1
    n@281:68
    v@281:279
    f@92:154
    <unknown>@92:863
    p@98:497
    b@98:895
    callImmediates@98:2990
    value@48:2779
    <unknown>@48:937
    value@48:2459
    value@48:907
    value@-1
    value@-1

        at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(ExceptionsManagerModule.java:83)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)
        at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:151)
        at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
        at android.os.Handler.handleCallback(Handler.java:942)
        at android.os.Handler.dispatchMessage(Handler.java:99)
        at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
        at android.os.Looper.loopOnce(Looper.java:226)
        at android.os.Looper.loop(Looper.java:313)
        at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:226)
        at java.lang.Thread.run(Thread.java:1012)

Expected behavior
To be able to start the room w/o any issue
Screenshots
If applicable, could you add screenshots to help explain your problem?
Device Info:

Product name: Samsung Galaxy S20 5G
Model name: SM-G981U1

Dependencies Info (please reference your package-lock.json or yarn.lock file):
"dependencies": {
        "@codler/react-native-keyboard-aware-scroll-view": "^1.0.1",
        "@fingerprintjs/fingerprintjs": "^3.0.6",
        "@flyerhq/react-native-link-preview": "^1.6.0",
        "@fortawesome/fontawesome-svg-core": "^1.2.32",
        "@fortawesome/free-brands-svg-icons": "^5.15.1",
        "@fortawesome/free-regular-svg-icons": "^5.15.1",
        "@fortawesome/free-solid-svg-icons": "^5.15.1",
        "@fortawesome/react-native-fontawesome": "^0.2.6",
        "@gorhom/bottom-sheet": "^2",
        "@livekit/react-native": "^1.1.2",
        "@livekit/react-native-webrtc": "^104.0.1",
        "@react-native-async-storage/async-storage": "^1.14.1",
        "@react-native-community/art": "^1.2.0",
        "@react-native-community/cli": "^5.0.1",
        "@react-native-community/cli-debugger-ui": "5.0.1",
        "@react-native-community/clipboard": "^1.5.1",
        "@react-native-community/datetimepicker": "^3.4.6",
        "@react-native-community/masked-view": "^0.1.10",
        "@react-native-community/netinfo": "^6.0.0",
        "@react-native-community/picker": "^1.8.1",
        "@react-native-community/push-notification-ios": "^1.10.1",
        "@react-navigation/bottom-tabs": "^5.11.11",
        "@react-navigation/compat": "^5.3.15",
        "@react-navigation/material-bottom-tabs": "^5.3.15",
        "@react-navigation/native": "^5.9.4",
        "@react-navigation/stack": "^5.14.5",
        "@stripe/stripe-react-native": "^0.22.0",
        "@voximplant/react-native-foreground-service": "^3.0.1",
        "add": "^2.0.6",
        "axios": "^0.21.0",
        "babel-plugin-module-resolver": "^4.0.0",
        "buffer": "^6.0.3",
        "date-fns": "^2.28.0",
        "device-uuid": "^1.0.4",
        "final-form": "^4.20.2",
        "final-form-arrays": "^3.0.2",
        "jetifier": "^2.0.0",
        "js-base64": "^3.6.0",
        "json5": "^2.2.0",
        "lodash": "^4.17.20",
        "metro-config": "^0.66.1",
        "moment": "^2.29.1",
        "public-ip": "^4.0.3",
        "qs": "^6.9.3",
        "query-string": "^7.0.1",
        "react": "17.0.2",
        "react-devtools": "^4.14.0",
        "react-devtools-core": "^4.14.0",
        "react-final-form": "^6.5.3",
        "react-native": "^0.64.1",
        "react-native-add-calendar-event": "^4.0.0",
        "react-native-autocomplete-input": "^5.0.2",
        "react-native-autolink": "^4.0.0",
        "react-native-calendars": "^1.1249.0",
        "react-native-chip-view": "^0.0.12",
        "react-native-complete-mentions": "^1.0.9",
        "react-native-config": "^1.4.1",
        "react-native-controlled-mentions": "^2.2.5",
        "react-native-datepicker": "^1.7.2",
        "react-native-device-info": "^8.0.1",
        "react-native-dialog": "^9.3.0",
        "react-native-document-picker": "^5.0.3",
        "react-native-drawer": "^2.5.1",
        "react-native-elements": "3.4.2",
        "react-native-email-link": "^1.10.0",
        "react-native-fast-image": "^8.3.6",
        "react-native-file-viewer": "^2.1.4",
        "react-native-fs": "^2.20.0",
        "react-native-gesture-handler": "^1.10.0",
        "react-native-gifted-chat": "^0.16.3",
        "react-native-image-crop-picker": "^0.36.0",
        "react-native-image-picker": "^4.10.2",
        "react-native-image-progress": "^1.1.1",
        "react-native-image-slider": "^2.0.3",
        "react-native-image-slider-box": "^1.0.12",
        "react-native-image-slider-show": "^1.0.3",
        "react-native-keyboard-aware-scroll-view": "^0.9.3",
        "react-native-keychain": "^7.0.0",
        "react-native-linear-gradient": "^2.5.6",
        "react-native-maps": "^0.28.0",
        "react-native-onesignal": "^4.3.1",
        "react-native-paper": "^4.7.2",
        "react-native-permissions": "^3.1.0",
        "react-native-picker-select": "^8.0.2",
        "react-native-popup-dialog": "^0.18.3",
        "react-native-reanimated": "^1.13.2",
        "react-native-render-html": "^5.0.1",
        "react-native-safe-area-context": "^3.1.9",
        "react-native-screens": "3.10.2",
        "react-native-shared-element": "^0.8.2",
        "react-native-shortcut-badge": "^0.1.0-beta.2",
        "react-native-simple-toast": "^1.1.3",
        "react-native-skeleton-placeholder": "^4.0.0",
        "react-native-snap-carousel": "^4.0.0-beta.5",
        "react-native-splash-screen": "^3.2.0",
        "react-native-status-bar-height": "^2.6.0",
        "react-native-svg": "^12.1.0",
        "react-native-svg-transformer": "^0.14.3",
        "react-native-swipe-list-view": "^3.2.5",
        "react-native-toast-message": "2.1.5",
        "react-native-url-polyfill": "^1.3.0",
        "react-native-url-preview": "^1.1.9",
        "react-native-vector-icons": "^8.0.0",
        "react-native-video": "^5.1.0-alpha8",
        "react-native-webview": "^11.18.1",
        "react-navigation-slide-from-right-transition": "^1.0.4",
        "react-redux": "^7.2.2",
        "react-tiny-link": "^3.6.1",
        "redux": "^4.0.5",
        "redux-actions": "^2.6.5",
        "redux-enhancer-react-native-appstate": "^0.3.1",
        "redux-logger": "^3.0.6",
        "redux-persist": "^6.0.0",
        "redux-persist-transform-filter": "^0.0.20",
        "redux-saga": "^1.1.3",
        "redux-thunk": "^2.3.0",
        "reselect": "^4.0.0",
        "rn-fetch-blob": "^0.12.0",
        "rollbar-react-native": "^0.9.2",
        "sync-storage": "^0.4.2",
        "url-parse": "^1.5.3",
        "xregexp": "^5.0.1",
        "yarn": "^1.22.10"
    },
    "devDependencies": {
        "@babel/core": "^7.17.9",
        "@babel/runtime": "^7.17.9",
        "@react-native-community/eslint-config": "3.0.1",
        "@types/jest": "^27.4.1",
        "@types/lodash": "^4.14.181",
        "@types/qs": "^6.9.7",
        "@types/react": "^18.0.5",
        "@types/react-native": "0.67.4",
        "@types/react-native-autocomplete-input": "^5.0.0",
        "@types/react-native-datepicker": "^1.7.1",
        "@types/react-native-popup-dialog": "^0.16.3",
        "@types/react-native-snap-carousel": "^3.8.4",
        "@types/react-native-video": "^5.0.13",
        "@types/react-native-webrtc": "^1.75.5",
        "@types/react-redux": "^7.1.24",
        "@types/react-test-renderer": "^18.0.0",
        "@types/redux-actions": "^2.6.2",
        "@types/redux-immutable-state-invariant": "^2.1.2",
        "@types/redux-logger": "^3.0.9",
        "@types/url-parse": "^1.4.8",
        "babel-jest": "^27.5.1",
        "eslint": "8.13.0",
        "jest": "^27.5.1",
        "metro-react-native-babel-preset": "^0.70.1",
        "react-native-iap": "8.0.8",
        "react-test-renderer": "18.0.0",
        "redux-immutable-state-invariant": "^2.1.0",
        "redux-promise-middleware": "^6.1.2",
        "typescript": "^4.1.4"
    },

Additional context
Please feel free to add any other context about the problem here.

Update:
After trying to comment out everything line by line I see the error somehow on the release version is coming from this initialization:
const [room] = useState(
    () =>
      new Room({
        adaptiveStream: { pixelDensity: 'screen' },
      })
  );

I don't know why since locally in debug mode works fine but maybe this helps somehow if someone can help me out

Hmm, building the release version of the example app doesn't seem to run into this issue. Can you try seeing if there's any differences between your app and the example app?
It'd also help if you could symbolicate your error logs.
Finally, could you provide the specific version of livekit-client seen in your package-lock.json or yarn.lock file?

Hey, @davidliu I've tried to look over the example app and compare but nothing looks really out of the ordinary.
What's weird is in debug there's no issue but once I make the release build the error appears which I've tried to check by turning the release build locally on my device and removing everything except the:
const [room] = useState(
    () =>
      new Room()
  );

About the symbolicate the error logs, @davidliu, will check and try to provide the output.
My yarn.lock file:
/Users/admin/Work/ugenie/ugenie-screens/yarn.lock

@davidliu Symbolicating a stack trace is not supposed to be used while when generating a release build an error, appear.
If that's the case for me there is no error in the sense that my build works the app is functional but crashes when I want to test the functionality for calling on a release build and I open the screen where the livekit logic is placed ... otherwise the app works fine w/o any issue expect the one mentioned.

I'm sorry, not sure what you mean. Symbolicating is specifically for release builds, since those symbols are obfuscated; symbolicating lets us see where the actual code is.

Yap, my bad, but I tried to do that but I get nothing while running the line command... do you have any idea why?

Hey, @davidliu, I've tried to build for you a demo app with RN v0.64. (thinking maybe the RN version I use is too low?) but after installing everything in the @livekit/react-native package I'm stuck now with this error:
Build file<EMAIL_ADDRESS>line: 29

A problem occurred evaluating project ':livekit_react-native'.
> No signature of method: build_cnj2ja3g84zne9ohoyuvmflwu.android() is applicable for argument types: (build_cnj2ja3g84zne9ohoyuvmflwu$_run_closure1) values: [build_cnj2ja3g84zne9ohoyuvmflwu$_run_closure1@2abb6cb9]

* Try:
Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Exception is:
org.gradle.api.GradleScriptException: A problem occurred evaluating project ':livekit_react-native'.
	at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:93)
	at org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.lambda$apply$0(DefaultScriptPluginFactory.java:133)
	at org.gradle.configuration.ProjectScriptTarget.addConfiguration(ProjectScriptTarget.java:77)
	at org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:136)
	at org.gradle.configuration.BuildOperationScriptPlugin$1.run(BuildOperationScriptPlugin.java:65)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:56)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$run$1(DefaultBuildOperationExecutor.java:71)
	at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.runWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:45)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:71)
	at org.gradle.configuration.BuildOperationScriptPlugin.lambda$apply$0(BuildOperationScriptPlugin.java:62)
	at org.gradle.configuration.internal.DefaultUserCodeApplicationContext.apply(DefaultUserCodeApplicationContext.java:43)
	at org.gradle.configuration.BuildOperationScriptPlugin.apply(BuildOperationScriptPlugin.java:62)
	at org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.lambda$applyToMutableState$0(DefaultProjectStateRegistry.java:248)
	at org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.fromMutableState(DefaultProjectStateRegistry.java:275)
	at org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.applyToMutableState(DefaultProjectStateRegistry.java:247)
	at org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:42)
	at org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:26)
	at org.gradle.configuration.project.ConfigureActionsProjectEvaluator.evaluate(ConfigureActionsProjectEvaluator.java:35)
	at org.gradle.configuration.project.LifecycleProjectEvaluator$EvaluateProject.lambda$run$0(LifecycleProjectEvaluator.java:100)
	at org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.lambda$applyToMutableState$0(DefaultProjectStateRegistry.java:248)
	at org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.lambda$withProjectLock$3(DefaultProjectStateRegistry.java:308)
	at org.gradle.internal.work.DefaultWorkerLeaseService.withLocks(DefaultWorkerLeaseService.java:178)
	at org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.withProjectLock(DefaultProjectStateRegistry.java:308)
	at org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.fromMutableState(DefaultProjectStateRegistry.java:289)
	at org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.applyToMutableState(DefaultProjectStateRegistry.java:247)
	at org.gradle.configuration.project.LifecycleProjectEvaluator$EvaluateProject.run(LifecycleProjectEvaluator.java:91)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:56)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$run$1(DefaultBuildOperationExecutor.java:71)
	at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.runWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:45)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:71)
	at org.gradle.configuration.project.LifecycleProjectEvaluator.evaluate(LifecycleProjectEvaluator.java:63)
	at org.gradle.api.internal.project.DefaultProject.evaluate(DefaultProject.java:710)
	at org.gradle.api.internal.project.DefaultProject.evaluate(DefaultProject.java:145)
	at org.gradle.execution.TaskPathProjectEvaluator.configure(TaskPathProjectEvaluator.java:36)
	at org.gradle.execution.TaskPathProjectEvaluator.configureHierarchy(TaskPathProjectEvaluator.java:64)
	at org.gradle.configuration.DefaultProjectsPreparer.prepareProjects(DefaultProjectsPreparer.java:46)
	at org.gradle.configuration.BuildTreePreparingProjectsPreparer.prepareProjects(BuildTreePreparingProjectsPreparer.java:57)
	at org.gradle.configuration.BuildOperationFiringProjectsPreparer$ConfigureBuild.run(BuildOperationFiringProjectsPreparer.java:52)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:56)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$run$1(DefaultBuildOperationExecutor.java:71)
	at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.runWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:45)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:71)
	at org.gradle.configuration.BuildOperationFiringProjectsPreparer.prepareProjects(BuildOperationFiringProjectsPreparer.java:40)
	at org.gradle.initialization.DefaultGradleLauncher.prepareProjects(DefaultGradleLauncher.java:228)
	at org.gradle.initialization.DefaultGradleLauncher.doClassicBuildStages(DefaultGradleLauncher.java:165)
	at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:150)
	at org.gradle.initialization.DefaultGradleLauncher.executeTasks(DefaultGradleLauncher.java:126)
	at org.gradle.internal.invocation.GradleBuildController$1.create(GradleBuildController.java:72)
	at org.gradle.internal.invocation.GradleBuildController$1.create(GradleBuildController.java:67)
	at org.gradle.internal.work.DefaultWorkerLeaseService.withLocks(DefaultWorkerLeaseService.java:178)
	at org.gradle.internal.invocation.GradleBuildController.doBuild(GradleBuildController.java:67)
	at org.gradle.internal.invocation.GradleBuildController.run(GradleBuildController.java:56)
	at org.gradle.tooling.internal.provider.runner.ClientProvidedPhasedActionRunner.run(ClientProvidedPhasedActionRunner.java:60)
	at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
	at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
	at org.gradle.launcher.exec.BuildOutcomeReportingBuildActionRunner.run(BuildOutcomeReportingBuildActionRunner.java:63)
	at org.gradle.tooling.internal.provider.ValidatingBuildActionRunner.run(ValidatingBuildActionRunner.java:32)
	at org.gradle.tooling.internal.provider.FileSystemWatchingBuildActionRunner.run(FileSystemWatchingBuildActionRunner.java:67)
	at org.gradle.launcher.exec.BuildCompletionNotifyingBuildActionRunner.run(BuildCompletionNotifyingBuildActionRunner.java:41)
	at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner$3.call(RunAsBuildOperationBuildActionRunner.java:49)
	at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner$3.call(RunAsBuildOperationBuildActionRunner.java:44)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:200)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:195)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:62)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$call$2(DefaultBuildOperationExecutor.java:76)
	at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.callWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:54)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:76)
	at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner.run(RunAsBuildOperationBuildActionRunner.java:44)
	at org.gradle.launcher.exec.InProcessBuildActionExecuter.lambda$execute$0(InProcessBuildActionExecuter.java:54)
	at org.gradle.composite.internal.DefaultRootBuildState.run(DefaultRootBuildState.java:87)
	at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:53)
	at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:29)
	at org.gradle.launcher.exec.BuildTreeScopeLifecycleBuildActionExecuter.lambda$execute$0(BuildTreeScopeLifecycleBuildActionExecuter.java:33)
	at org.gradle.internal.buildtree.BuildTreeState.run(BuildTreeState.java:49)
	at org.gradle.launcher.exec.BuildTreeScopeLifecycleBuildActionExecuter.execute(BuildTreeScopeLifecycleBuildActionExecuter.java:32)
	at org.gradle.launcher.exec.BuildTreeScopeLifecycleBuildActionExecuter.execute(BuildTreeScopeLifecycleBuildActionExecuter.java:27)
	at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:104)
	at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:55)
	at org.gradle.tooling.internal.provider.SubscribableBuildActionExecuter.execute(SubscribableBuildActionExecuter.java:64)
	at org.gradle.tooling.internal.provider.SubscribableBuildActionExecuter.execute(SubscribableBuildActionExecuter.java:37)
	at org.gradle.tooling.internal.provider.SessionScopeLifecycleBuildActionExecuter.lambda$execute$0(SessionScopeLifecycleBuildActionExecuter.java:54)
	at org.gradle.internal.session.BuildSessionState.run(BuildSessionState.java:67)
	at org.gradle.tooling.internal.provider.SessionScopeLifecycleBuildActionExecuter.execute(SessionScopeLifecycleBuildActionExecuter.java:50)
	at org.gradle.tooling.internal.provider.SessionScopeLifecycleBuildActionExecuter.execute(SessionScopeLifecycleBuildActionExecuter.java:36)
	at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:36)
	at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:25)
	at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:59)
	at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:31)
	at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:55)
	at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:41)
	at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:47)
	at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:31)
	at org.gradle.launcher.daemon.server.exec.ExecuteBuild.doBuild(ExecuteBuild.java:65)
	at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:37)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.WatchForDisconnection.execute(WatchForDisconnection.java:39)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute(ResetDeprecationLogger.java:29)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon.execute(RequestStopIfSingleUsedDaemon.java:35)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.create(ForwardClientInput.java:78)
	at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.create(ForwardClientInput.java:75)
	at org.gradle.util.Swapper.swap(Swapper.java:38)
	at org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute(ForwardClientInput.java:75)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.LogAndCheckHealth.execute(LogAndCheckHealth.java:55)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.LogToClient.doBuild(LogToClient.java:63)
	at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:37)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:84)
	at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:37)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy$1.run(StartBuildOrRespondWithBusy.java:52)
	at org.gradle.launcher.daemon.server.DaemonStateCoordinator$1.run(DaemonStateCoordinator.java:297)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
Caused by: groovy.lang.MissingMethodException: No signature of method: build_cnj2ja3g84zne9ohoyuvmflwu.android() is applicable for argument types: (build_cnj2ja3g84zne9ohoyuvmflwu$_run_closure1) values: [build_cnj2ja3g84zne9ohoyuvmflwu$_run_closure1@2abb6cb9]
	at build_cnj2ja3g84zne9ohoyuvmflwu.run(/Users/admin/Work/rn641/node_modules/@livekit/react-native/android/build.gradle:29)
	at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:91)
	... 140 more

Looks like I've managed to fix the debug version but on release, I keep getting this error, maybe you have an idea why?
{path}.gradle/caches/modules-2/files-2.1/androidx.annotation/annotation/1.4.0/77e7b6bbe9803d890343716dd824dfdbc0f6fe77/annotation-1.4.0.jar!/META-INF/annotation.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.4.0.

Hmm, v0.64 is pretty old (over two years at this point), can you try upgrading to a newer version? I know v0.67 should work, though newer should be better.

After finishing the version with v0.64.1 will try yes. The idea is the project I am trying to implement livekit SDK for mobile is pretty huge so upgrading the version to something like v.0.67 can bring many changes in many places sadly

@davidliu I am unable to make a release build because of this error ... I tried several ways to provide the kotlin version, but nothing changes ..
{path}.gradle/caches/modules-2/files-2.1/androidx.annotation/annotation/1.4.0/77e7b6bbe9803d890343716dd824dfdbc0f6fe77/annotation-1.4.0.jar!/META-INF/annotation

### UPDATE:
Solved by upgrading to React Native version 0.67.5.
Leaving this here for others that may sustain older projects and get this issue.


grid: loadWatcher and showWatcher

This ensures the grid will load images with a 2000px offset instead of 500px and also have a dedicated watcher for the animation that is independent from the loading.
General discussion can be found here:
https://basecamp.com/1760900/projects/5735396/todos/153554645#comment_248036593

LGTM


texlive: bump for latest ctan, texlive.info archive

Motivation for this change
For some context, this was previously and recently discussed:
https://github.com/NixOS/nixpkgs/pull/61469#issuecomment-549477615
https://github.com/NixOS/nixpkgs/pull/71419#issuecomment-545867115
Fortunately it appears, due to developments since those discussion,
that there is now a versioned mirror for ctan contents!!
Naturally this commit is about moving to that mirror:
updating the package lists and regenerating the hashes.
This has two huge advantages:

Updating the pinned ctan packages can be done more frequently
than the current "once a year".
We don't have to rely on community members to create a snapshot
and mirror it indefinitely and at their own cost.

Minor "advantage":

I should be writing but instead I was working on this :P

It appears new, I stumbled upon a mention of it here[1]:

Native TL updates ultimately come from a directory named tlnet (on CTAN).
An archive for tlnet is available, with daily updates since
September 2019, and the final yearly release going back about ten years.

[1] https://www.tug.org/texlive/pkginstall.html

Concerns and theirs status:

Package integrity:
There may be concerns about ensuring the package hashes are obtained
from a trusted source-- I haven't looked into this at all "yet".

Mirror reliability and not-abusing-nice-things-from-good-people
If the mirror is a small operation it may be hostile to point
the network request fury of the Nixpkgs texlive community ;).
This doesn't appear to be the case and there's no mention of it,
and presumably wouldn't be linked from tug.org if wasn't to be used?
Would be good to chase down an announcement or otherwise ensure
this is expected usage.
Time will tell re:mirror reliability (or speed?),
so far it seems like a solid service meant to be used
and unlikely to be problematic.

Is the archive only updated once a day?
The archive is organized by date, which is wonderful (!)
but might mean the contents may see changes during the day.
I suspect this is not the case but just a thought.
Regardless, any problems seem easily avoided by simply
not updating to the current day and use yesterday instead.

If this is the way we move forward,
there are changes/fixes/improvements to be made
in terms of documentation as well as (possibly)
putting together some update automation tooling.

I have only tested this with a single project so far,
and it doesn't have any especially esoteric or demanding
needs.  Help testing by checking your projects to see
that they build and produce expected results.
Building against the before/after set and using diffpdf
is how I usually vet these updates, if that's useful.
The diffpdf especially helps identify the minor
appearance changes I usually miss visually-- tweaks
to microtype behavior or slightly different layout/placement
of figures or handling of beamer slides, etc.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @veprbl @vcunat @veprbl @lovek323 @raskin @jwiegley
(texlive maintainers, thanks!)
Discussion, testing, and help wrapping this up requested and
appreciated.

Did you see #74305?

@dtzWill  I merged my PR as it updates documentation comments. I propose we have some test period first to make sure users can use the new mirror. I'm a bit concerned with its speed also. From your motivation section, I assume that you don't have a specific problem that you are trying to address with the version bump. We can, of course, do the bump now if we really need to.

Ha! No I didn't see that PR, that is great.  Sorry for the dup, looking through that PR now.

From your motivation section, I assume that you don't have a specific problem that you are trying to address with the version bump. We can, of course, do the bump now if we really need to.

That's correct, and if we want to be careful about this I'm in favor of testing the mirror switch by itself (as we're now doing) and we can bump later as deemed useful or desirable.
The update was for only minor ctan package updates, nothing critical or likely to be of importance beyond my own projects.


Language support for generic type parameters

I wrote the following while investigating how cursorless deals with types and classes in Typescript.
interface IBasicPerson{
  Name : string,
  Age : number
}

const HairColorMap = {
  Blond : "Blond",
  Mouse : "Mouse",
} as const

type HairColor = keyof typeof HairColorMap

interface IExtendedPersion extends IBasicPerson{
  HairColor : HairColor
}

function NamesMatch<TPerson extends IBasicPerson, THasAName extends {Name:string}>( person:TPerson, namedThing:THasAName): boolean{
{
  const override:string= "badger";
  return namedThing.Name === person.Name || person.Name == override;
}

const personInstance:IExtendedPersion = {
  Age : 10,
  HairColor: "Blond",
  Name:"John"
};

console.log("Names match", NamesMatch(person, {Name:"Tony"}));

To select TPerson extends IBasicPerson I would need to use past as in 'take _ past _'. I think that the generic types should be dealt with in the same way as function parameters. This more of a an issue for Typescript where generic parameters may have an extends part to the generic type, but would be useful for other languages as even in C# you may have List<List> where you would want to select the inner List as an argument. This does raise the question what should happen if I say "Take type (mark in TPerson)" would it take the type argument IBasicPerson (at the moment it selects the boolean which is the type of the function)?

I believe in Rust we call generic type parameters argumentOrParameter, do we do the same in TypeScript?

Yeah I'd argue those type parameters could be argumentOrParameter.  Fwiw collectionItem (ie `"item") should work today
I think the "type" behaviour is reasonable, as "type" is supposed to be type annotations or type declarations


Arteria runfolder handlers

@Aratz Thank you so much for the review. I have learnt a lot while making the corrections.
I have now updated the code:

Thanks for addressing my comments :) Unfortunately I found some corner cases that would break the current version of the service. I've updated the tests accordingly.
There are also some comments from previous reviews that were not addressed.
If you want we could schedule a pair-programming sessions to fix this.

Hi @Aratz , thank you so much for the review.
Sorry for the previous comments I missed, I might have missed seeing them and need to look keenly (not intentional at all, hehe))
And I think it would be a good idea to pair program to implement the changes suggested

Great pair programming session to solve the comments... Thanks


Depend on ProjectivePoint: ToEncodedPoint

This reverts the unfortunate changes that had to be made in #91.
It was fixed in https://github.com/RustCrypto/elliptic-curves/pull/722.
This will actually require downstream users to update their primeorder dependency to v0.12.1, personally I don't think it is a problem, but the gain is also very minor.

CI fails because of Clippy, see #96.

Rebased on #96.


Hugo renders orgmode files (content/*.org) as if markdown

What version of Hugo are you using (hugo version)?

$ hugo version
Hugo Static Site Generator v0.64.1-C327E75D linux/amd64 BuildDate: 2020-02-09T20:47:32Z

Does this issue reproduce with the latest release?
Yes
Description of problem
In have a orgmode file (content/Org Test.org) which contains:
#+title: Org Test
#+date: 2020-02-08
#+draft: false

* This should be a header and not a list item

* This should be a header and not a list item renders as a list item rather than a header (* represents a list item in markdown but a header in orgmode).
The orgmode formating of the front-matter however seems to work fine, e.g. if I change #+draft: false to #+draft: true it actually becomes a draft item (isn't shown on the site). #+title: Org Test also works.
So it seems to recognize orgmode front-matter, but not orgmode content.

I couldn't reproduce this bug. I get h1 as expected. Anything org-relevant in your config? Can you run hugo and share the contents of public/org-test/index.html?
(also completely unrelated, since you're using emacs and hugo, can you reproduce #6773?)


How Disable drag on right menu but not the left menu?

I have 2 menus, left and right. On the start view I want both menus to be swipe/draggable. But on all other views I don't want the right menu to be draggable. Using $ionicSideMenuDelegate Im only able to disable both menus with canDragContent(false);
What's the Ionic way to accomplish this?
If I use this:
$ionicSideMenuDelegate.$getByHandle('right-menu').canDragContent(false);
I get this message:
Delegate for handle "right-menu" could not find a corresponding element with delegate-handle="right-menu"! canDragContent() was not called!
Possible cause: If you are calling canDragContent() immediately, and your element with delegate-handle="right-menu" is a child of your controller, then your element may not be compiled yet. Put a $timeout around your call to canDragContent() and try again.

Greetings @YaroslavG!
My sensors indicate that you need to update your issue through our custom issue form. We are now requiring all issues to be submitted this way, to ensure that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
I will have no choice but to close this issue if it is not resubmitted through the form. Please fill out the rest of the form, so that I may use my friendly robot powers to assist you.
Thank you!

Greetings @YaroslavG!
I've closed this issue because my sensors indicated it was old and inactive, and may have already been fixed in recent versions of Ionic. However, if you are still experiencing this issue, please feel free to reopen this issue by creating a new one, and include any examples and other necessary information, so that we can look into it further.
Thank you for allowing me to assist you.


Create components and logic for initial game flow without styling.

Add logic to create/join lobbies, play the game, get points, play again
Add minimal styles for the sake of testing the game

Reviewed with @lucasgreenwell

Reviewed with @lucasgreenwell


Kirstie's To Do list - Week starting 19th September 2017

URGENT

[x] Letters of recommendation for SRA application deadline 26th July
[x] Reviews for D&S fundings deadlines 18th September
[x] Review applications for student postdoc SIG deadline 24th September
[ ] Visa for China

To Do
Emails/Online

[ ] Email NCH re inclusivity call
[ ] Add ICON2017 slides to whitakerlab.github.io
[ ] Reply to PB email about outreach
[ ] Introduce HQ to CSAP folk & Inga
[ ] Schedule call w Wellcome Trust
[ ] Invoice to British Library
[ ] Invoice to Fuel
[ ] Newsletter - September #78
[x] Write RA job description

Waiting on admin response

[ ] Survey for research fellows office hours -- see #81

Next step (after 8th September) - write summary report

[ ] Add CamNeuro Data Blitz & NNHD to whitaker lab blog
[ ] DBS check with STEM Ambassadors
[x] Email TN re PhD
[ ] Email MB re DAT project
[ ] Email CH re FA
[ ] Email SV re TFL data study group/hackathon
[ ] Email psychiatry dude from CamNeuro NNHD
[ ] Add talk for Online Brain Intensive to website
[ ] Add ECNP talk to website
[ ] Email FV & MOR re: building interactive version of r code
[ ] Outreach prep for teaching in Peterborough

NSPN Analyses

[ ] Run longitudinal pipeline on HPHI

[ ] Need to be able to actually run code on HPHI first! See #39 😕
[ ] Need to copy over the data from HPC
[ ] Also need to check that everything looks good

[ ] Incorporate von Economo atlas in NSPN code
[ ] Send HCP parcellation data to JS deadline 1st August
[ ] Email to SW & PV re analysis update

NSPN Data Management (issue list)

[ ] Update data management team on Cambridge repository -- see NSPN-DM-#1
[x] Arrange date for next data management meeting

👉 Email sent 31st August

[ ] Add replies to email questions w GP & LV to repo
[ ] Add to issues in DataManagement repo
[ ] Create agenda for next meeting

Blogs/interviews/writing

[ ] Edit story engine for Mozilla

Invited talks/teaching

[ ] Presentation for Turing grad students deadline 4th September 2017
[ ] Abstract & bio for talk in Leeds
[ ] Talk for Warsaw brainhack -- see #80

BrainAge

[ ] Get code installed & running
[ ] Send questions to FL

OpenAdvice

[ ] Migrate to organisation ProjectOpenAdvice & build website there: https://projectopenadvice.github.io/
[ ] Merge jekyll pull request

OpenConCam

[ ] Rearrange meeting & make to do list
[ ] Reply to emails & update

Peer Reviews

[ ] A0030 deadline August 30th

MozFest

[ ] Create schedule
[x] Follow up on missing facilitator emails

OHBM

[ ] OpenScience github repo
[ ] Guide for rotating curation of slack

Closing w billions of things left undone, as is the way of things 😉


Fix broken link in readme TOC

The Respecting .gitignore link pointed to a section of the readme which no longer exists.

Thanks!