UHF-9458: Re-added default scopes

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (8c479c8) 71.71% compared to head (c9356b1) 72.95%.
 Consider uploading reports for the commit 386c5cc to get more accurate results

Additional details and impacted files
@@             Coverage Diff              @@
##               main      #29      +/-   ##
============================================
+ Coverage     71.71%   72.95%   +1.24%
+ Complexity       56       55       -1
============================================
  Files             4        4
  Lines           198      196       -2
============================================
+ Hits            142      143       +1
+ Misses           56       53       -3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Can you please share the dataset you used

Can you please share the dataset you used, the dataset I found so far is handled differently than yours and the code doesn't make sense!

I can give you my email, would you mind leaving me a contact form?

I can give you my email, would you mind leaving me a contact form?

ok

<EMAIL_ADDRESS>

I can give you my email, would you mind leaving me a contact form?我可以给你我的电子邮箱，你介意给我一张联系人表格吗？

ok 好的

My email is<EMAIL_ADDRESS>and I look forward to your reply!

My email is<EMAIL_ADDRESS>and I look forward to your reply too!

我也发了一封邮件，希望获取到您所用的数据集~
<EMAIL_ADDRESS>

<EMAIL_ADDRESS>

我不是作者，我只是在下面评论了一下。我也在询问作者要数据集
ゞ 有一种冷丶透心凉
@.***
Original Email
Sender:"wangly0276"< @.*** >;
Sent Time:2023/11/15 10:45
To:"cjymz886/GFNER"< @.*** >;
Cc recipient:"leaiijj"< @.*** >;"Comment"< @.*** >;
Subject:Re: [cjymz886/GFNER] Can you please share the dataset you used (Issue#1)
@.***
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

I can give you my email, would you mind leaving me a contact form?

ok

Hello, I have sent an email to you requesting your dataset. My email is<EMAIL_ADDRESS>and I look forward to your reply! Thank you very much.

Hello, I have sent an email to you requesting your dataset. My email is<EMAIL_ADDRESS>and I look forward to your reply! Thank you very much. @cjymz886

Hello, I have sent an email to you requesting your dataset. My email is<EMAIL_ADDRESS>and I am eagerly awaiting your response.Thank you！ @cjymz886

no ACE2005 dataset
| |
@.***
|
|
@.***
|
---- Replied Message ----
| From | @.> |
| Date | 5/22/2024 17:29 |
| To | @.> |
| Cc | @.> ,
@.> |
| Subject | Re: [cjymz886/GFNER] Can you please share the dataset you used (Issue #1) |
My email is @.*** and I look forward to your reply too,thank you very much!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

no ACE2005 dataset | | @.*** | | @.*** | ---- Replied Message ---- | From | @.> | | Date | 5/22/2024 17:29 | | To |<EMAIL_ADDRESS>| | Cc |<EMAIL_ADDRESS>, @._> | | Subject | Re: [cjymz886/GFNER] Can you please share the dataset you used (Issue #1) | My email is<EMAIL_ADDRESS>and I look forward to your reply too,thank you very much! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

Oh,thank you very much, I have received your email and replied to it. Please check it

hello, have u received the datasets?  can u send me one? Thank u very much. Looking for your reply!

It has been sent to you, please check it. if you don't receive it, please give me your email.
| |
songxing
|
|
@.***
|
---- Replied Message ----
| From | Mengying @.> |
| Date | 5/28/2024 20:39 |
| To | @.> |
| Cc | @.> ,
@.> |
| Subject | Re: [cjymz886/GFNER] Can you please share the dataset you used (Issue #1) |
no ACE2005 dataset | | @.*** | | @.*** | ---- Replied Message ---- | From | @.> | | Date | 5/22/2024 17:29 | | To | @**.> | | Cc | @.> , @._> | | Subject | Re: [cjymz886/GFNER] Can you please share the dataset you used (Issue #1) | My email is @. and I look forward to your reply too,thank you very much! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.*>
Oh,thank you very much, I have received your email and replied to it. Please check it
hello, have u received the datasets? can u send me one? Thank u very much. Looking for your reply!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

It has been sent to you, please check it. if you don't receive it, please give me your email. | | songxing | | @.*** | ---- Replied Message ---- | From | Mengying @.> | | Date | 5/28/2024 20:39 | | To | @.> | | Cc | @.> , @.> | | Subject | Re: [cjymz886/GFNER] Can you please share the dataset you used (Issue #1) | no ACE2005 dataset | | @.*** | | @.*** | ---- Replied Message ---- | From | @.> | | Date | 5/22/2024 17:29 | | To | @**.> | | Cc | @.> , @._> | | Subject | Re: [cjymz886/GFNER] Can you please share the dataset you used (Issue #1) | My email is @. and I look forward to your reply too,thank you very much! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.> Oh,thank you very much, I have received your email and replied to it. Please check it hello, have u received the datasets? can u send me one? Thank u very much. Looking for your reply! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.**>

hello！i didnt find it. Can u send me one again? Thank u very much! my email is<EMAIL_ADDRESS>


exceptions / disconnects

i am wondering if there is a way to handle device disconnects or other connection problems in home assistant / pyhomematic.
i'd like to be notified about any device disconnects or any problems with ccu <-> device and ccu <-> home assistant communication via an event that can be automated.
there might be infrastructure for this already, but i was not able to find any information.

With ccu <-> device you mean the communication between the CCU and a thermostat or whatever? If so, the CCU has the "Servicemeldungen". These aren't directly visible in HASS (yet, it would be possible though if someon would implement it), but the ccu-entity within HASS always has a numeric value, which corresponds to the total count of such service messages. So if it's always 0 and then turns to 1 you know, that at least some sort of error has occurred. That way you know you should have a look at the CCU and check which error has happened.
The ccu <-> hass connection is hard to monitor. A dropped connection usually results in your hass-devices not updating anymore, since the CCU stops sending the event-data to hass. But the CCU does not send a "we had a dropped connection"-message. And the CCU also lacks som sort of "ping"-method which we could use to check if the connection is still alive. So in that case you only have the workaround to have an automation that fires as soon as some sensor hasn't changed for time X. A brightness-sensor for example which is configured to periodically send the brightness. Such a sensor should change its value a few times across a whole if it's near a window. Or something similar, like a sensor measuring the power usage of the house, which never is 0W if you have a CCU running.


Disable pan gesture on front VC when showing VCs from side

Hi,
my situation is that in the left VC I have a menu, one of the menu items is controller with MKMapView inside. When the VC with map is shown in front with the left menu revealed, pan gestures in the visible part of the front VC are being caught by the map so it is not possible to go back to front VC by swiping from right to left.

Hi
Are you setting your recognizesPanningOnFrontView at YES ?


Interceptor policies are not working when added from the apk-conf

Description
When interceptors are added as API-level or resource level policies from apk-conf file, they do not work as intended when the backendURL points to a k8s service.
apiPolicies:
  request:
    - policyName: "Interceptor"
      policyVersion: v1
      parameters:
        backendUrl: "http://interceptor-service.test-apk.svc.cluster.local:8443"
        headersEnabled: true

In the backend CR generated for the interceptor base path is added as an empty string.
apiVersion: dp.wso2.com/v1alpha1
kind: Backend
metadata:
  name: backend-1dae10f7e7f06e5af130f489c3b4abcd9d920d51-interceptor
  namespace: apk
spec:
  basePath: ""
  protocol: http
  services:
  - host: interceptor-service.test-apk.svc.cluster.local
    port: 8443

When the basePath is removed, interceptors are working as expected.

In the backend CR generated for the interceptor base path is added as an empty string.
apiVersion: dp.wso2.com/v1alpha1
kind: Backend
metadata:
  name: backend-1dae10f7e7f06e5af130f489c3b4abcd9d920d51-interceptor
  namespace: apk
spec:
  basePath: ""
  protocol: http
  services:
  - host: interceptor-service.test-apk.svc.cluster.local
    port: 8443

When the basePath is removed, interceptors are working as expected.

Ignore this part as it was observed that this is not the fix for the bug.


⚠ Roblox TextFilter Api has degraded performance

In c6fa4bb, Roblox TextFilter Api (https://textfilter.roblox.com) experienced degraded performance:

HTTP code: 200
Response time: 1532 ms

Resolved: Roblox TextFilter Api performance has improved in 0e1df8a.


rxjs beta-3 bundle not working

Hi all,
I am using version 0.7.9 of typings, and am trying to create a bundled typing for @reactivex/rxjs beta 3.
I'm running typings bundle --out tmp and I get the following error:
Attempted to compile "@reactivex/rxjs" as a dependency, but it contains some ambient module declarations ("/code/rxjs/dist/cjs/Observable.d.ts").

I get this error if I try to run this in the es6 folder too.
For your reference (and to save you having to pull an npm version of rxjs), the files in question are (oh do let me know if you would like any other files referenced to be attached):
Rx.d.ts (the entry file):
export { Subject } from './Subject';
export { Observable } from './Observable';
import './add/observable/bindCallback';
import './add/observable/bindNodeCallback';
import './add/observable/combineLatest';
import './add/observable/concat';
import './add/observable/defer';
import './add/observable/empty';
import './add/observable/forkJoin';
import './add/observable/from';
import './add/observable/fromArray';
import './add/observable/fromEvent';
import './add/observable/fromEventPattern';
import './add/observable/fromPromise';
import './add/observable/interval';
import './add/observable/merge';
import './add/observable/race';
import './add/observable/never';
import './add/observable/of';
import './add/observable/range';
import './add/observable/throw';
import './add/observable/timer';
import './add/observable/zip';
import './add/operator/buffer';
import './add/operator/bufferCount';
import './add/operator/bufferTime';
import './add/operator/bufferToggle';
import './add/operator/bufferWhen';
import './add/operator/cache';
import './add/operator/catch';
import './add/operator/combineAll';
import './add/operator/combineLatest';
import './add/operator/concat';
import './add/operator/concatAll';
import './add/operator/concatMap';
import './add/operator/concatMapTo';
import './add/operator/count';
import './add/operator/dematerialize';
import './add/operator/debounce';
import './add/operator/debounceTime';
import './add/operator/defaultIfEmpty';
import './add/operator/delay';
import './add/operator/delayWhen';
import './add/operator/distinctUntilChanged';
import './add/operator/do';
import './add/operator/expand';
import './add/operator/filter';
import './add/operator/finally';
import './add/operator/first';
import './add/operator/groupBy';
import './add/operator/ignoreElements';
import './add/operator/inspect';
import './add/operator/inspectTime';
import './add/operator/last';
import './add/operator/let';
import './add/operator/every';
import './add/operator/map';
import './add/operator/mapTo';
import './add/operator/materialize';
import './add/operator/merge';
import './add/operator/mergeAll';
import './add/operator/mergeMap';
import './add/operator/mergeMapTo';
import './add/operator/multicast';
import './add/operator/observeOn';
import './add/operator/partition';
import './add/operator/pluck';
import './add/operator/publish';
import './add/operator/publishBehavior';
import './add/operator/publishReplay';
import './add/operator/publishLast';
import './add/operator/race';
import './add/operator/reduce';
import './add/operator/repeat';
import './add/operator/retry';
import './add/operator/retryWhen';
import './add/operator/sample';
import './add/operator/sampleTime';
import './add/operator/scan';
import './add/operator/share';
import './add/operator/single';
import './add/operator/skip';
import './add/operator/skipUntil';
import './add/operator/skipWhile';
import './add/operator/startWith';
import './add/operator/subscribeOn';
import './add/operator/switch';
import './add/operator/switchMap';
import './add/operator/switchMapTo';
import './add/operator/take';
import './add/operator/takeLast';
import './add/operator/takeUntil';
import './add/operator/takeWhile';
import './add/operator/throttle';
import './add/operator/throttleTime';
import './add/operator/timeout';
import './add/operator/timeoutWith';
import './add/operator/toArray';
import './add/operator/toPromise';
import './add/operator/window';
import './add/operator/windowCount';
import './add/operator/windowTime';
import './add/operator/windowToggle';
import './add/operator/windowWhen';
import './add/operator/withLatestFrom';
import './add/operator/zip';
import './add/operator/zipAll';
export { Operator } from './Operator';
export { Observer } from './Observer';
export { Subscription, UnsubscriptionError } from './Subscription';
export { Subscriber } from './Subscriber';
export { AsyncSubject } from './subject/AsyncSubject';
export { ReplaySubject } from './subject/ReplaySubject';
export { BehaviorSubject } from './subject/BehaviorSubject';
export { ConnectableObservable } from './observable/ConnectableObservable';
export { Notification } from './Notification';
export { EmptyError } from './util/EmptyError';
export { ArgumentOutOfRangeError } from './util/ArgumentOutOfRangeError';
export { ObjectUnsubscribedError } from './util/ObjectUnsubscribedError';
import { AsapScheduler } from './scheduler/AsapScheduler';
import { AsyncScheduler } from './scheduler/AsyncScheduler';
import { QueueScheduler } from './scheduler/QueueScheduler';
declare var Scheduler: {
    asap: AsapScheduler;
    async: AsyncScheduler;
    queue: QueueScheduler;
};
declare var Symbol: {
    rxSubscriber: any;
    observable: any;
    iterator: any;
};
export { Scheduler, Symbol };

Observable.d.ts:
import { PartialObserver, Observer } from './Observer';
import { Operator } from './Operator';
import { Subscriber } from './Subscriber';
import { Subscription } from './Subscription';
import { IfObservable } from './observable/IfObservable';
import { ErrorObservable } from './observable/ErrorObservable';
export interface Subscribable<T> {
    subscribe(observer: Observer<T>): Subscription;
}
export declare type SubscribableOrPromise<T> = Subscribable<T> | Promise<T>;
export declare type ArrayOrIterator<T> = Iterator<T> | ArrayLike<T>;
export declare type ObservableInput<T> = SubscribableOrPromise<T> | ArrayOrIterator<T>;
/**
 * A representation of any set of values over any amount of time. This the most basic building block
 * of RxJS.
 *
 * @class Observable<T>
 */
export declare class Observable<T> implements Subscribable<T> {
    _isScalar: boolean;
    protected source: Observable<any>;
    protected operator: Operator<any, T>;
    /**
     * @constructor
     * @param {Function} subscribe the function that is  called when the Observable is
     * initially subscribed to. This function is given a Subscriber, to which new values
     * can be `next`ed, or an `error` method can be called to raise an error, or
     * `complete` can be called to notify of a successful completion.
     */
    constructor(subscribe?: <R>(subscriber: Subscriber<R>) => Subscription | Function | void);
    /**
     * Creates a new cold Observable by calling the Observable constructor
     * @static true
     * @owner Observable
     * @method create
     * @param {Function} subscribe? the subscriber function to be passed to the Observable constructor
     * @return {Observable} a new cold observable
     */
    static create: Function;
    /**
     * Creates a new Observable, with this Observable as the source, and the passed
     * operator defined as the new observable's operator.
     * @method lift
     * @param {Operator} operator the operator defining the operation to take on the observable
     * @return {Observable} a new observable with the Operator applied
     */
    lift<R>(operator: Operator<T, R>): Observable<R>;
    /**
     * Registers handlers for handling emitted values, error and completions from the observable, and
     *  executes the observable's subscriber function, which will take action to set up the underlying data stream
     * @method subscribe
     * @param {PartialObserver|Function} observerOrNext (optional) either an observer defining all functions to be called,
     *  or the first of three possible handlers, which is the handler for each value emitted from the observable.
     * @param {Function} error (optional) a handler for a terminal event resulting from an error. If no error handler is provided,
     *  the error will be thrown as unhandled
     * @param {Function} complete (optional) a handler for a terminal event resulting from successful completion.
     * @return {Subscription} a subscription reference to the registered handlers
     */
    subscribe(observerOrNext?: PartialObserver<T> | ((value: T) => void), error?: (error: any) => void, complete?: () => void): Subscription;
    /**
     * @method forEach
     * @param {Function} next a handler for each value emitted by the observable
     * @param {PromiseConstructor} [PromiseCtor] a constructor function used to instantiate the Promise
     * @return {Promise} a promise that either resolves on observable completion or
     *  rejects with the handled error
     */
    forEach(next: (value: T) => void, PromiseCtor?: typeof Promise): Promise<void>;
    protected _subscribe(subscriber: Subscriber<any>): Subscription | Function | void;
    static if: typeof IfObservable.create;
    static throw: typeof ErrorObservable.create;
}

Thanks for the report, it may be the same issue as https://github.com/typings/typings/issues/340. Is there a file that does declare module '...' without a corresponding import?

There are a number of definition files that are imported (transitively) that look like this:
import { BufferSignature } from '../../operator/buffer';
declare module '../../Observable' {
    interface Observable<T> {
        buffer: BufferSignature<T>;
    }
}

Where the ../../Observable would be pointing to the Observable.d.ts file, which is the one the being complained about.
I can keep looking if that's not what you mean...

I think it's the same issue. I'll get a simple patch out and remove this restriction ASAP.

What does declare module '../../Observable' mean? Module augmentation based on relative path?
Why it is not just declare module 'Observable'?

@unional : This was a new feature added in version 1.8. It allows modules to extend other modules.
The primary reason is that I can export say an object from the observable.ts module, and in another module (buffer.ts) add a property to that object.
The reason you would want to do this is to prevent huge objects that not all consumers would want. In the case of RX, there are a lot of operators that could bloat say a web-app. So this way, a consumer can select which operators they want included.
The declare module '../../Observable mechanism is the corresponding type definition to support this use case.

@blakeembrey Thanks!

I understand module augmentation. Just don't understand the relative path part.
Because declare module "id" syntax declares a module (external module), therefore I try to understand what does the relative path means.
If your repo is ready I'll take a look to educate myself. :)

@unional An external module can still be a relative one. In this case the two modules are in the same package and relative to each other.
But it's probably easier to see the code for yourself. It's not my repo (I sadly can't take any credit for the excellent library). Its url is: https://github.com/ReactiveX/rxjs.
The github repo doesn't have the typings materialised, so to get to the typings, it's probably easier to install it as an npm dependency (npm install @reactivex/rxjs) and look in the dist folder

Ar.... I see. It is the output generated from typings bundle. It's also related to the module name pollution I discuss before https://github.com/typings/core/issues/1#issuecomment-192802609


How to set last post timestamp via LatestStamps("stampsfile").set_last_post_timestamp("myaccount", datetime)

I'm trying to write a Python bot that fetches the Instagram posts from an account and posts them on Twitter.
I want the bot to post just the newest post, therefore I thought I should make use of the LatestStamps Class.
I now have the problem that I don't fully understand how to get the post-timestamp of the post and how to set it in the stampsfile.
What kind of value does the datetime parameter need?

Nevermind...
for post in profile.get_post():
LatestStamps("stampsfile").set_last_post_timestamp("profile", post.date)

Nevermind...
for post in profile.get_post():
LatestStamps("stampsfile").set_last_post_timestamp("profile", post.date)


[backport v1.0.3] Cannot delete Template

This is a backport issue for https://github.com/harvester/harvester/issues/2376

Verified fixed on v1.0-9e056ebc-head (06/10). Close this issue.
Result

If the template is the default version, it will not display the delete button

If the template is not the default version, it will display the delete button

We can also delete the entire template from the config button

Test Information

Test Environment: 1 node1 harvester on local kvm machine
Harvester version: master-26bff4f1-head (06/10)

Verify Steps

Go to advanced -> tempaltes
Create a new template
Modify the template to create a new version
Click the config button of the default version template
Click the config button of the non default version template


DEM FRANCE 1 meter open licence

Hello,
Turns out that IGN brought since January 2021, an open access to its DEM 1M (RGE 1 m Alti)
See the list of Zip related to french metropolitan regions available at 1m.
https://geoservices.ign.fr/documentation/diffusion/telechargement-donnees-libres.html#rge-alti-1-m

Looks like great data source, thanks for sharing!

@nvkelso are you gonna add it at some point? There are a lot of issues in the current elevations in France.
On a side note  because of that i am trying to generate hgt files in the same format as in aws https://registry.opendata.aws/terrain-tiles/. Is there a script/doc explaining how you generate those from geotiff?

@nvkelso Do you know if AWS S3 public download has now integrated this ?


Checkaccess

Q
A

Is bugfix?
no

New feature?
no

Breaks BC?
no

Tests pass?
yes

Fixed issues
added a checkAccess example

Thank you!


Attempt at speeding up prisma-generator tests

In working on #1458 I noticed that some tests took me a while to execute. A lot of it seems to be centered around npm installs, so I picked out the prisma generator tests to experiment on.
As a baseline, current dev tests for that file took around 400 seconds on my system; with the npm installs taking up between 20 and 40 seconds.
With the --no-progress --no-audit --no-fund flags, total time for this file reduced to 300 seconds on my system.
I then looked at adding a test project directory, installing that in test-scaffold and copying from there each test. That reduced execution time to about 100 seconds on my system.
Given that this would seperate definition of the test context (which dependencies etc) from test execution, I wanted to try and avoid that if I could; so I looked at pnpm store. That is the version I finally submitted in this PR:

Generally, we define a gitignored directory as a custom pnpm-store directory only to be used in the test suite.
In beforeAll, we use a package.json and .npmrc written into a temp dir to load any missing dependencies into the store.
In beforeEach, we can then write that same package.json and .npmrc and execute pnpm install --offline to quickly install from the store.
On my system this executes at around 55 seconds with an empty store, and at around 45 seconds when I've already populated the store earlier.

To me, this approach seems like a nice middle ground:

These tests are slightly less isolated then they were before, as they rely on the pnpm store. While that's unfortunate, it isn't that different from what we already have with test-scaffold.
Given that the project already uses pnpm, I'd expect it shouldn't be a problem to use pnpm commands within tests. I am somewhat wondering whether pnpm-installed-via-npm setups might be an issue?
Using a pnpm store specific to the complete workspace test suite keeps it insulated from the rest of the system and the actual workings of the project
The pnpm store seems slighly beneficial to me over the test-scaffold-and-copy I had before, given that the context of the test (package.json) isn't as separated from the actual test.

Happy to hear your thoughts on this! Is this an approach worth taking? Do you see downsides I'm missing here? Are there other factors to consider? Do you see room for further improvement?

Hi @WimTibackx, I'm sorry for the late response. Thanks for working on improving test speed. I've been bothered by it for quite a while but have been procrastinating on it 😅.
I think using a shared pnpm store is a great idea, which should make the installation process significantly faster, especially for running locally. From another perspective, I'm also wondering if we need to scaffold a npm project for each test at all. The tests were made this way mainly because Prisma and ZenStack both do code generation into node_modules and using disposable projects is the simplest way to isolate. However, since both Prisma and ZenStack allow specifying where to output the generated code, we can probably only emit them into some temp dir while not having a full-scale npm project at all.
What do you think about this direction? It's gonna be a bigger change though.

Hi @ymc9! It's about time I respond to this. Sorry for the delayed reply, I got a bit wrapped up in work and life for a bit.

I think using a shared pnpm store is a great idea, which should make the installation process significantly faster, especially for running locally.

I've been looking into this last weekend, but it requires some further tinkering. My original proof of concept probably used the easiest set of dependencies, unfortunately :) . The bigger dependency trees and the post-install scripts require some further work for this PR. I'm taking another shot at it today, will keep you posted.

I'm also wondering if we need to scaffold a npm project for each test at all. (...) since both Prisma and ZenStack allow specifying where to output the generated code, we can probably only emit them into some temp dir while not having a full-scale npm project at all.

That's a fair point indeed. As long as there's one full-on npm project integration test per module / variant, having other test cases run based on results emitting to a temp dir could suffice indeed.
For now, I'll see if I can universally apply the pnpm store approach, as that should already help a fair bit.

Closing for now. Will pick it up again as necessary.


Error thrown when attempting to split panes on about screen

Open the About screen
Run a "Pane: Split (direction) And Copy Active Item" command

Atom Version: 1.7.4
System: Microsoft Windows 8.1 Enterprise
Thrown From: Atom Core
Stack Trace
Uncaught Error: The workspace can only contain one instance of item [object Object]
At ...\Atom\resources\app.asar\src\item-registry.js:11

Error: The workspace can only contain one instance of item [object Object]
    at ItemRegistry.module.exports.ItemRegistry.addItem (...\Atom\resources\app.asar\src\item-registry.js:11:15)
    at PaneContainer.module.exports.PaneContainer.addedPaneItem (...\Atom\resources\app.asar\src\pane-container.js:387:25)
    at ...\Atom\resources\app.asar\src\pane-container.js:366:19
    at ...\Atom\resources\app.asar\src\pane-container.js:97:16
    at Function.module.exports.Emitter.simpleDispatch (...\Atom\resources\app.asar\node_modules\event-kit\lib\emitter.js:25:14)
    at Emitter.module.exports.Emitter.emit (...\Atom\resources\app.asar\node_modules\event-kit\lib\emitter.js:125:28)
    at PaneContainer.module.exports.PaneContainer.didAddPane (...\Atom\resources\app.asar\src\pane-container.js:306:27)
    at Pane.module.exports.Pane.setContainer (...\Atom\resources\app.asar\src\pane.js:125:26)
    at PaneAxis.module.exports.PaneAxis.addChild (...\Atom\resources\app.asar\src\pane-axis.js:144:13)
    at PaneAxis.module.exports.PaneAxis.insertChildAfter (...\Atom\resources\app.asar\src\pane-axis.js:216:19)
    at Pane.module.exports.Pane.split (...\Atom\resources\app.asar\src\pane.js:895:23)
    at Pane.module.exports.Pane.splitRight (...\Atom\resources\app.asar\src\pane.js:856:19)
    at atom-pane.commandRegistry.add.pane:split-right-and-copy-active-item (...\Atom\resources\app.asar\src\register-default-commands.js:247:32)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (...\Atom\resources\app.asar\src\command-registry.js:260:29)
    at ...\Atom\resources\app.asar\src\command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (...\Atom\resources\app.asar\node_modules\atom-keymap\lib\keymap-manager.js:580:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (...\Atom\resources\app.asar\node_modules\atom-keymap\lib\keymap-manager.js:388:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeyEvent (...\Atom\resources\app.asar\src\window-event-handler.js:98:36)
    at HTMLDocument.<anonymous> (...\Atom\resources\app.asar\src\window-event-handler.js:3:61)

Confirmed on Windows 10 x64, Atom 1.9.0-dev-6991246.

Am not able to reproduce on master (1.11) on Windows 10.

Still happens to me on 1.11.0-dev-080f1d3.

Yeah, this is a weird one – this seems like an error the ItemRegistry should just silently handle, instead of putting the onus on API consumers to check whether an instance already exists in the workspace. 😕 Pretty much all of Atom's view packages are prone to this, although I think at least find-and-replace has a workaround.

I can't think of a scenario where two copies of about makes any sense. I'm more worried you can do this to settings-view and end up with two copies that immediately get out of sync as you make changes.
I think it would make most sense for items to opt-in to the copy behavior if they have been written to support it correctly.  I think by default we'd include our TextEditor and perhaps Image-View and Archive-View.

Fixed via https://github.com/atom/tabs/pull/522.


Allow Fortran field which changes size during the run

lxavier

Currently we get error when trying to write field which do not have a constant size (e.g. data assimilation):
Error: sizes of field i_prof passed with sizes (2658x1x1x1), but registered with sizes (2657x1x1x1)

MeteoSwiss-APN/serialbox#51

Re-open if still important.


how to change .exe thingie

Describe your problem here.
once you enter the psych engine folder it says like PsychEngine.exe I wanna change that to like AMOGUS.exe
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No

This is something you would most likely want to edit within the "Project.xml" file before compiling. This can be located on line 5 of the file.

i said lua

rename the file genius

Rename the .exe file

im an ide


bump resolver to lts-5.3

updates Aeson so it can parse plain strings, needed
for Week07 tests

@aztecrex - Merged. Thanks for the PR!


The action 'Open' is enabled for one soft deleted folder in the new ADLS Gen2 blob explorer

Storage Explorer Version: 1.32.0-dev (93)
Build Number: 20230904.1
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 20.04/MacOS Ventura 13.5 (Apple M1 Pro)
Architecture: x64/x64/x64
How Found: From running testing
Regression From: Previous release (1.31.1)
Bug Descriptions
Several actions are incorrectly enabled for one soft deleted folder in the new ADLS Gen2 blob explorer.

Steps to Reproduce

Expand one ADLS Gen2 storage account -> Blob Containers.
Right click one blob container -> Click 'Open Gen2 as Blob Explorer (test)'.
Create a folder -> Soft delete the folder.
Switch to 'Active and soft deleted blobs' -> Select the soft deleted folder.
Check whether the action 'Open' is disabled.

Expected Experience
The action 'Open' is disabled.
Actual Experience
The action 'Open' is enabled.

@JasonYeMSFT ,verified this issue on the build 20230906.5, the 'Propagate Access Control Lists...' action is still enabled for one soft deleted folder.

Verified this issue on the main build 20230908.4.
The 'Propagate Access Control Lists...' action is disabled for soft delete folder. So, we are going to close it.


Build problem on debian docker

When i build on a debian docker container i get the following errors
_Compiling cyclonedds-sys v0.1.2 (/workspaces/positiondetection/tmp/cyclonedds-sys)
Compiling cyclonedds-rs v0.3.1 (/workspaces/positiondetection/tmp/cyclonedds-rs)
error[E0560]: struct cyclonedds_sys::ddsi_sertype_ops has no field named typeid_hash
--> /workspaces/positiondetection/tmp/cyclonedds-rs/src/serdes.rs:777:9
|
777 |         typeid_hash: None,
|         ^^^^^^^^^^^ cyclonedds_sys::ddsi_sertype_ops does not have this field
|
= note: available fields are: version, arg, free, zero_samples, realloc_samples ... and 10 others
error[E0560]: struct cyclonedds_sys::ddsi_sertype_ops has no field named serialized_size
--> /workspaces/positiondetection/tmp/cyclonedds-rs/src/serdes.rs:778:9
|
778 |         serialized_size: None,
|         ^^^^^^^^^^^^^^^ help: a field with a similar name exists: get_serialized_size
error[E0560]: struct cyclonedds_sys::ddsi_sertype_ops has no field named serialize
--> /workspaces/positiondetection/tmp/cyclonedds-rs/src/serdes.rs:779:9
|
779 |         serialize: None,
|         ^^^^^^^^^ cyclonedds_sys::ddsi_sertype_ops does not have this field
|
= note: available fields are: version, arg, free, zero_samples, realloc_samples ... and 10 others
error[E0560]: struct cyclonedds_sys::ddsi_sertype_ops has no field named deserialize
--> /workspaces/positiondetection/tmp/cyclonedds-rs/src/serdes.rs:780:9
|
780 |         deserialize: None,
|         ^^^^^^^^^^^ cyclonedds_sys::ddsi_sertype_ops does not have this field
|
= note: available fields are: version, arg, free, zero_samples, realloc_samples ... and 10 others
When i do a small local fix of the 4 points above i get the following error:
Compiling cyclonedds-sys v0.1.2 (/workspaces/positiondetection/tmp/cyclonedds-sys)
Compiling cyclonedds-rs v0.3.1 (/workspaces/positiondetection/tmp/cyclonedds-rs)
error[E0063]: missing fields derive_sertype, get_serialized_size, serialize_into and 3 other fields in initializer of cyclonedds_sys::ddsi_sertype_ops
--> /workspaces/positiondetection/tmp/cyclonedds-rs/src/serdes.rs:768:14
|
768 |     Box::new(ddsi_sertype_ops {
|              ^^^^^^^^^^^^^^^^ missing derive_sertype, get_serialized_size, serialize_into and 3 other fields_

Thank you for raising the ticket.  May I know which version of Cyclonedds do you have installed on your system?

Hello,
Sorry for the late reply but cyclonedds version was 0.8.2 the date was Jan
20.
Best regards
Ad
Op ma 31 jan. 2022 12:26 schreef Sojan James @.***>:

Thank you for raising the ticket. May I know which version of Cyclonedds
do you have installed on your system?
—
Reply to this email directly, view it on GitHub
https://github.com/sjames/cyclonedds-rs/issues/2#issuecomment-1025639215,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOACPEEVXAH2AIGICZ6A3JDUYZWVNANCNFSM5M3QXCKQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

I finally got around to fixing this.  The CDDS serialization interface has changed.  This is not unexpected as this is undergoing a lot of changes.  I've pushed the fixes to use the new interface.  https://github.com/sjames/cyclonedds-rs/commit/bc64c4b6cec8c5ba0f3587ddb32474d0a9ce5df8
Also published on crates.io as version "0.4.0"

Hello,
I have tried to build the demo-vehicle-speed-publisher and i am sorry to
tell but i get the erorr
/usr/local/include/dds/ddsc/dds_basic_types.h fatal Error: stdbool.h file
not found
Best regards
Ad
Op ma 7 mrt. 2022 09:07 schreef Sojan James @.***>:

I finally got around to fixing this. The CDDS serialization interface has
changed. This is not unexpected as this is undergoing a lot of changes.
I've pushed the fixes to use the new interface. bc64c4b
https://github.com/sjames/cyclonedds-rs/commit/bc64c4b6cec8c5ba0f3587ddb32474d0a9ce5df8
Also published on crates.io as version "0.4.0"
—
Reply to this email directly, view it on GitHub
https://github.com/sjames/cyclonedds-rs/issues/2#issuecomment-1060295520,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOACPEHH45NWBKPYCFI6SG3U6W2MVANCNFSM5M3QXCKQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

Hmm,   I wonder why this is the case.  Have you installed clang-devel in the container?

Hello Sojan,
I have it working now.
Only libclang-dev was installed but not clang.
After apt-get install clang
It was fixed.
Thanks for  the help!!
Best regards,
Ad
Op zo 13 mrt. 2022 11:55 schreef Sojan James @.***>:

Hmm, I wonder why this is the case. Have you installed clang-devel in the
container?
—
Reply to this email directly, view it on GitHub
https://github.com/sjames/cyclonedds-rs/issues/2#issuecomment-1066075869,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOACPEDTDIK77OU6CUMBLEDU7XCSPANCNFSM5M3QXCKQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread. Message ID:
@.***>

Excellent!  Thank you for the feedback.  Closing this issue.

Hello Sojan,
Now i was compiling the subscriber example on github and i found the
following error on line 59.
Could you please help me out with an example on this?
Best regards,
Ad
Compiling cyclonedds-rs v0.4.4
Building [=======================> ] 147/149: vehicle-signals
Compiling vehicle_speed_subscriber v0.1.0
(/workspaces/cyclonedds/examples/demo-vehicle-speed-subscriber)
warning: unused imports: num, time
--> src/main.rs:1:12
|
1 | use core::{num, time};
|            ^^^  ^^^^
|
= note: #[warn(unused_imports)] on by default
warning: unused imports: sync::Arc, thread
--> src/main.rs:3:11
|
3 | use std::{sync::Arc, thread};
|           ^^^^^^^^^  ^^^^^^
warning: unused import: cyclonedds_rs::dds_topic::DdsEntity
--> src/main.rs:6:5
|
6 | use cyclonedds_rs::dds_topic::DdsEntity;
|     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
warning: unused import: Sample
--> src/main.rs:7:29
|
7 | use cyclonedds_rs::serdes::{Sample, SampleBuffer};
|                             ^^^^^^
warning: unused imports: FutureExt, select
--> src/main.rs:9:15
|
9 | use futures::{select, FutureExt};
|               ^^^^^^  ^^^^^^^^^
error[E0308]: mismatched types
--> src/main.rs:59:19
|
59 |         .with_qos(qos)
|                   ^^^ expected struct cyclonedds_rs::DdsQos, found
&mut cyclonedds_rs::DdsQos
warning: unused import: std::io::Read
--> src/main.rs:2:5
|
2 | use std::io::Read;
|     ^^^^^^^^^^^^^
For more information about this error, try rustc --explain E0308.
warning: vehicle_speed_subscriber (bin "vehicle_speed_subscriber")
generated 6 warnings
error: could not compile vehicle_speed_subscriber due to previous error;
6 warnings emitted
@.***:/workspaces/go_nla/go_lang/cyclonedds/examples/demo-vehicle-speed-subscriber$
Op di 15 mrt. 2022 om 04:54 schreef Sojan James @.***>:

Excellent! Thank you for the feedback. Closing this issue.
—
Reply to this email directly, view it on GitHub
https://github.com/sjames/cyclonedds-rs/issues/2#issuecomment-1067535077,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOACPEADZJVLC2D3HCM7L53VAACVXANCNFSM5M3QXCKQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Met vriendelijke groet,
Ad

The Qos interface had changed and I forgot to update the demo.  It is fixed now.  https://github.com/sjames/demo-vehicle-speed-subscriber/commit/e77a8e07510e4fd73234c910bc5c91f1a1be6ae0

Hello Sojan,
Thanks for your fast reaction.
Best regards
Ad
Op ma 4 apr. 2022 07:08 schreef Sojan James @.***>:

The Qos interface had changed and I forgot to update the demo. It is fixed
now. @.***
https://github.com/sjames/demo-vehicle-speed-subscriber/commit/e77a8e07510e4fd73234c910bc5c91f1a1be6ae0
—
Reply to this email directly, view it on GitHub
https://github.com/sjames/cyclonedds-rs/issues/2#issuecomment-1087121154,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOACPEAL3L7V7GBLLG24VNLVDJ2K7ANCNFSM5M3QXCKQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hello Sojan?
Unfortunatly i have to notify you that the cyclonedds-rs build is broken.
It nog reports that it can not find iceoryx helader files. Tommorow i Will
have a try-out instelling iceoryx.
Best regards
Ad
Op ma 4 apr. 2022 20:19 schreef Ad van den Langenberg <
@.***>:

Hello Sojan,
Thanks for your fast reaction.
Best regards
Ad
Op ma 4 apr. 2022 07:08 schreef Sojan James @.***>:

The Qos interface had changed and I forgot to update the demo. It is
fixed now. @.***
https://github.com/sjames/demo-vehicle-speed-subscriber/commit/e77a8e07510e4fd73234c910bc5c91f1a1be6ae0
—
Reply to this email directly, view it on GitHub
https://github.com/sjames/cyclonedds-rs/issues/2#issuecomment-1087121154,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOACPEAL3L7V7GBLLG24VNLVDJ2K7ANCNFSM5M3QXCKQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hello Sojan,
I had installed the libclan-dev.
I wil try it again.
Best regards
Ad
Op zo 13 mrt. 2022 11:55 schreef Sojan James @.***>:

Hmm, I wonder why this is the case. Have you installed clang-devel in the
container?
—
Reply to this email directly, view it on GitHub
https://github.com/sjames/cyclonedds-rs/issues/2#issuecomment-1066075869,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOACPEDTDIK77OU6CUMBLEDU7XCSPANCNFSM5M3QXCKQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>


docker: Error response from daemon

System Info
tensorRT-llm 0.8
Who can help?
No response
Information

[ ] The official example scripts
[ ] My own modified scripts

Tasks

[ ] An officially supported task in the examples folder (such as GLUE/SQuAD, ...)
[ ] My own task or dataset (give details below)

Reproduction
docker run --rm -it --ipc=host --ulimit memlock=-1 --ulimit stack=67108864
--gpus=all
--volume /home/wanghaikuan/code/TensorRT-LLM:/code/tensorrt_llm
--env "CCACHE_DIR=/code/tensorrt_llm/cpp/.ccache"
--env "CCACHE_BASEDIR=/code/tensorrt_llm"
--workdir /app/tensorrt_llm
--hostname nvidia-desktop-release
--name tensorrt_llm-release-wanghaikuan
--tmpfs /tmp:exec
tensorrt_llm/release:latest
Expected behavior
orin platform can enter docker successfully.

actual behavior
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'csv'
invoking the NVIDIA Container Runtime Hook directly (e.g. specifying the docker --gpus flag) is not supported. Please use the NVIDIA Container Runtime (e.g. specify the --runtime=nvidia flag) instead.: unknown.
additional notes
NONE

It may not be a bug related with the source code of TensorRT-LLM. Please refer to https://github.com/NVIDIA/nvidia-docker/issues/1225. Thanks!

please feel free to reopen this ticket if needed.


Tweak handling of aliases

Previously, execute_subcommand was called recursively, and each call
would .configure the config again. It worked, but seemed rather
fragile.
This commit handles aliases more explicitly, ensures that .configure
is called once and, as a bonus, adds a warning for when an alias is
shadowed by the built in.

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

r=me, nice!

@bors r=alexcrichton

:pushpin: Commit e4e3177 has been approved by alexcrichton

:hourglass: Testing commit e4e31776f56307a68962e85020386083e7bfc1e0 with merge d25fb85f77e29053b54d4d12782411f15b019845...

:broken_heart: Test failed - status-travis

@bors r=alexcrichton

:pushpin: Commit ecd1e5d has been approved by alexcrichton

:hourglass: Testing commit ecd1e5df0f9b84d95eeb013305dc43bdbd7e9bac with merge 151f37c2a7a797936ba755e52abee192dda8a1d3...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 151f37c2a7a797936ba755e52abee192dda8a1d3 to master...


input-group looks compressed and broken.

(Mac OS Mojave 10.14.4, Chrome 74.0.3729.157)
Looking at the following code for an input-group
https://github.com/twbs/bootstrap/blob/2d6e086342a93a59ae8abeb17460e9fab50ec267/scss/_input-group.scss#L7-L30
there are two interesting lines here: line 10 (flex-wrap: wrap) and line 22 (width: 1%) which seem to be the cause for the following rendering

And the code is

  <select class="custom-select" name="some-name">
    …
  </select>

    <button class="btn btn-outline-secondary dropdown-toggle" type="button" data-toggle="dropdown"></button>

    …

I’ve fixed this by adding flex-wrap: nowrap to the input group itself, and width: auto to the select element further down in the cascade. But I am curious about why these two values were chosen in the first place? Shouldn’t the flex-wrap be at least nowrap to ensure that an input group doesn’t break visually?

Please see https://getbootstrap.com/docs/4.3/components/input-group/#wrapping

@ysds, huh I missed that, thanks! Any recommendation on how to handle the width: 1% better?

Documented in the source, but I'm not sure this is still valid.
https://github.com/twbs/bootstrap/blob/master/scss/_input-group.scss#L19-L22


I can not able to select time picker by default.

I have created two butttons, one for date picker and one for time picker.I want to show time picker when opens the picker popup.

This would be a useful feature. I'll accept a PR to add it!


Can't get it to work with Yubikey

hello,
I found this appliation and it looked like a good way to use my yubikey for openssh on windows and WSL but i can't get it to work. I did have it working for openssh on windows with GPG however.
Can you give some more information on how this should be working? I am running the .exe and i have set the PATH variable like i should, but if i ssh i still get the prompt asking me for my password in stead of a popup for unlocking the yubikey.

just to be clear, i have removed GPG before trying this, as another issue (#1 )was also mentioning the inteference with gpg. #

could you run ssh -vvv YOURHOST and provide the log to me? (note: you should hide some sensitive information in the log)

I think you are interested in this bit:
debug3: unable to connect to pipe \\\\.\\pipe\\openssh-ssh-agent, error: 5 debug1: pubkey_prepare: ssh_get_authentication_socket: Permission denied
here is the full log:
' ssh -vvv root@firewall
OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
debug3: Failed to open file:C:/Users/username/.ssh/config error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_config error:2
debug2: resolving "firewall" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to firewall [<IP_ADDRESS>] port 22.
debug1: Connection established.
debug3: Failed to open file:C:/Users/username/.ssh/id_rsa error:2
debug3: Failed to open file:C:/Users/username/.ssh/id_rsa.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\Users\username/.ssh/id_rsa type -1
debug3: Failed to open file:C:/Users/username/.ssh/id_rsa-cert error:2
debug3: Failed to open file:C:/Users/username/.ssh/id_rsa-cert.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\Users\username/.ssh/id_rsa-cert type -1
debug3: Failed to open file:C:/Users/username/.ssh/id_dsa error:2
debug3: Failed to open file:C:/Users/username/.ssh/id_dsa.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\Users\username/.ssh/id_dsa type -1
debug3: Failed to open file:C:/Users/username/.ssh/id_dsa-cert error:2
debug3: Failed to open file:C:/Users/username/.ssh/id_dsa-cert.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\Users\username/.ssh/id_dsa-cert type -1
debug3: Failed to open file:C:/Users/username/.ssh/id_ecdsa error:2
debug3: Failed to open file:C:/Users/username/.ssh/id_ecdsa.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\Users\username/.ssh/id_ecdsa type -1
debug3: Failed to open file:C:/Users/username/.ssh/id_ecdsa-cert error:2
debug3: Failed to open file:C:/Users/username/.ssh/id_ecdsa-cert.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\Users\username/.ssh/id_ecdsa-cert type -1
debug3: Failed to open file:C:/Users/username/.ssh/id_ed25519 error:2
debug3: Failed to open file:C:/Users/username/.ssh/id_ed25519.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\Users\username/.ssh/id_ed25519 type -1
debug3: Failed to open file:C:/Users/username/.ssh/id_ed25519-cert error:2
debug3: Failed to open file:C:/Users/username/.ssh/id_ed25519-cert.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\Users\username/.ssh/id_ed25519-cert type -1
debug3: Failed to open file:C:/Users/username/.ssh/id_xmss error:2
debug3: Failed to open file:C:/Users/username/.ssh/id_xmss.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\Users\username/.ssh/id_xmss type -1
debug3: Failed to open file:C:/Users/username/.ssh/id_xmss-cert error:2
debug3: Failed to open file:C:/Users/username/.ssh/id_xmss-cert.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\Users\username/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_for_Windows_7.7
debug1: Remote protocol version 2.0, remote software version OpenSSH_8.2 FreeBSD-openssh-portable-8.2.p1_1,1
debug1: match: OpenSSH_8.2 FreeBSD-openssh-portable-8.2.p1_1,1 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to firewall:22 as 'root'
debug3: hostkeys_foreach: reading file "C:\Users\username/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file C:\Users\username/.ssh/known_hosts:6
debug3: load_hostkeys: loaded 1 keys from firewall
debug3: Failed to open file:C:/Users/username/.ssh/known_hosts2 error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts2 error:2
debug3: order_hostkeyalgs: prefer hostkeyalgs: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,ext-info-c
debug2: host key algorithms: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm<EMAIL_ADDRESS>debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm<EMAIL_ADDRESS>debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none
debug2: compression stoc: none
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256
debug2: host key algorithms: rsa-sha2-512,rsa-sha2-256,ssh-rsa,ecdsa-sha2-nistp256,ssh-ed25519
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm<EMAIL_ADDRESS>debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm<EMAIL_ADDRESS>debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos<EMAIL_ADDRESS>debug2: compression stoc<EMAIL_ADDRESS>debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher<EMAIL_ADDRESS>MAC:  compression: none
debug1: kex: client->server cipher<EMAIL_ADDRESS>MAC:  compression: none
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:zTRxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
debug3: hostkeys_foreach: reading file "C:\Users\username/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file C:\Users\username/.ssh/known_hosts:6
debug3: load_hostkeys: loaded 1 keys from firewall
debug3: Failed to open file:C:/Users/username/.ssh/known_hosts2 error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts2 error:2
debug3: hostkeys_foreach: reading file "C:\Users\username/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file C:\Users\username/.ssh/known_hosts:6
debug3: load_hostkeys: loaded 1 keys from <IP_ADDRESS>
debug3: Failed to open file:C:/Users/username/.ssh/known_hosts2 error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts2 error:2
debug1: Host 'firewall' is known and matches the ECDSA host key.
debug1: Found key in C:\Users\username/.ssh/known_hosts:6
debug3: send packet: type 21
debug2: set_newkeys: mode 1
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug1: SSH2_MSG_NEWKEYS received
debug2: set_newkeys: mode 0
debug1: rekey after 134217728 blocks
debug3: unable to connect to pipe \\.\pipe\openssh-ssh-agent, error: 5
debug1: pubkey_prepare: ssh_get_authentication_socket: Permission denied
debug2: key: C:\Users\username/.ssh/id_rsa<PHONE_NUMBER>000000)
debug2: key: C:\Users\username/.ssh/id_dsa<PHONE_NUMBER>000000)
debug2: key: C:\Users\username/.ssh/id_ecdsa<PHONE_NUMBER>000000)
debug2: key: C:\Users\username/.ssh/id_ed25519<PHONE_NUMBER>000000)
debug2: key: C:\Users\username/.ssh/id_xmss<PHONE_NUMBER>000000)
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,sk-ssh-ed25519<EMAIL_ADDRESS>debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug3: start over, passed a different list publickey,password,keyboard-interactive
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Trying private key: C:\Users\username/.ssh/id_rsa
debug3: no such identity: C:\Users\username/.ssh/id_rsa: No such file or directory
debug1: Trying private key: C:\Users\username/.ssh/id_dsa
debug3: no such identity: C:\Users\username/.ssh/id_dsa: No such file or directory
debug1: Trying private key: C:\Users\username/.ssh/id_ecdsa
debug3: no such identity: C:\Users\username/.ssh/id_ecdsa: No such file or directory
debug1: Trying private key: C:\Users\username/.ssh/id_ed25519
debug3: no such identity: C:\Users\username/.ssh/id_ed25519: No such file or directory
debug1: Trying private key: C:\Users\username/.ssh/id_xmss
debug3: no such identity: C:\Users\username/.ssh/id_xmss: No such file or directory
debug2: we did not send a packet, disable method
debug3: authmethod_lookup keyboard-interactive
debug3: remaining preferred: password
debug3: authmethod_is_enabled keyboard-interactive
debug1: Next authentication method: keyboard-interactive
debug2: userauth_kbdint
debug3: send packet: type 50
debug2: we sent a keyboard-interactive packet, wait for reply
debug3: receive packet: type 60
debug2: input_userauth_info_req
debug2: input_userauth_info_req: num_prompts 1
debug3: failed to open file:F:/dev/tty error:3
debug1: read_passphrase: can't open /dev/tty: No such file or directory`

It uses PIV interface. Have you generated a PIV certificate?

No, i have a GPG key. I'm in the process of creating a  PIV cert. If it works ill let you know, it looks like it's usererror then..

You should generate a self signed certificate in the yubico manager GUI with RSA ONLY
After generating a certificate, please re-plug your yubikey to make windows recognize your certificates

If it still doesn’t work, check if there is a valid user certificate in the windows certificate manager.

After some struggle i got it working. Thanks for your help and looking into it. The key was generating the PIV certificate and getting the ssh-rsa public key to the servers.
The option of right clicking and viewing the public keys were a great help of this, thanks!


Add many1Till to Combinators

Looks great, thanks!

Thanks.  I've just become a bit concerned by this, though:
  let
    target = (joinWith "" $ replicate 100000 "a") <> "b"
  assert' "manyTill should not blow the stack" $ canParse (manyTill (string "a") (string "b")) (target)

blows the call stack.

Yes, that's a general issue right now. It's not just this function.

Oh - that's good news.  It's just that I saw similar tests in place for many.

Well, many uses Data.List.manyRec, which is stack-safe, but that's a special case. We could try to write these two functions using MonadRec, it might be an interesting exercise.

Hmm - looks like I need to do some more learning.  Thanks again for all your help and advice.


doesn't find shows when running as a Python subprocess

From the command line, no problem:
/usr/local/bin/mtv_dl -v download topic='terra' channel='zdf' age-30d duration+30m --high --dir=/mnt/NAS/dvds/recordings
2019-10-15T21:04:47+0200 DEBUG    Using cache from PosixPath('/mnt/NAS/dvds/recordings/.Filmliste-akt.xz.cache').
2019-10-15T21:04:48+0200 DEBUG    Database age is 0:41:00.
2019-10-15T21:04:48+0200 DEBUG    Applying filter: topic=terra, channel=zdf, age-30d, duration+30m
2019-10-15T21:04:49+0200 DEBUG    Skipping 'Im Bann der Astrologie - Faszination Universum mit Harald Lesch' [ZDF, 'Terra X', 2019-09-29 19:30:00+02:00, e7da8281] (already loaded on 2019-10-01 09:11:00)
2019-10-15T21:04:49+0200 DEBUG    Downloading 'Unser kosmisches Schicksal - Faszination Universum mit Harald Lesch' [ZDF, 'Terra X', 2019-10-13 19:30:00+02:00, d944a6b8] from 'https://rodlzdf-a.akamaihd.net/none/zdf/19/10/191013_fu_schicksal_tex/3/191013_fu_schicksal_tex_3328k_p36v14.mp4'.

However, if I run the same command from within a sudo Python3.7 script using subprocess, I get this:
sudo python3.7 /mnt/NAS/dvds/recordings/pvr.py
2019-10-15 21:03:58.100566
running: /usr/local/bin/mtv_dl -v download topic='terra' channel='zdf' age-30d duration+30m --high --dir=/mnt/NAS/dvds/recordings
out: ''
err: '2019-10-15T21:03:58+0200 DEBUG    Using cache from PosixPath('/mnt/NAS/dvds/recordings/.Filmliste-akt.xz.cache').
2019-10-15T21:03:59+0200 DEBUG    Database age is 0:40:00.
2019-10-15T21:03:59+0200 DEBUG    Applying filter: topic='terra', channel='zdf', age-30d, duration+30m
'
exit: 0
2019-10-15 21:04:00.606802

This is the Python code I use to run an external command
def run(cmd):
    print(datetime.datetime.now())
    print("running:", " ".join(cmd))
    proc = subprocess.Popen(cmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE)
    stdout, stderr = proc.communicate()
    proc.stdout.close()
    proc.stderr.close()
    print("out: '{}'".format(stdout.decode("utf8")))
    print("err: '{}'".format(stderr.decode("utf8")))
    print("exit: {}".format(proc.returncode))
    print(datetime.datetime.now())
    print("-------------------")

run(["/usr/local/bin/mtv_dl", "-v", "download",  "topic='terra'",  "channel='zdf'",
                     "age-30d", "duration+30m", "--high", "--dir=/mnt/NAS/dvds/recordings"])

Do you have any idea what could cause this?

OK, when carefully studying my own bug report, it turns out the solution is to get of the quotes in topic and channel:
                     "age-30d", "duration+30m", "--high", "--dir=/mnt/NAS/dvds/recordings"])```

Great that you figured this out yourself :)
Did you consider to simply import mtv_dl and just run the functions instead?

Yes, that would even cleaner. The main reason I did it this way is that in the same python file I also call perl scripts, so I just used the same way of working for mtv_dl.


Passwordless use?

Hey,
Is it possible to use kanboard without authentication. I.e. upon going to the kanboard URL, you don't need to login.
(I use kanboard in a 1 user deployment, serving only on <IP_ADDRESS> on my laptop)

Nope it's not possible. You can probably trick the authentication with a .htaccess and reverse proxy auth...


Proposal: MSB based unsigned varint

MSB based unsigned varint
It is based on the varint of the Go standard library, with some modifications:

Dropping zig-zag encoding of signed ints. Multiformats use varints for indexing into tables. These are always positive indices.
There is no max. The Go implementation has a "64-bit integer" max (using 10 bytes for representation). Thankfully, the Go implementation leaves the door open to grow the integer if need be. Here, we explicitly state there is no maxmimum. There is always a continuation bit.
Implementations of each multiformat will give recommended maxes to avoid memory attacks, and varint implementations SHOULD either:

specify a soft max (a max in the implementation though not in the spec)
or require clients (like a mulithash implementation) to specify the max.

Spec
The encoding is:

unsigned integers are serialized 7 bits at a time, starting with the
least significant bits
the most significant bit (msb) in each output byte indicates if there
is a continuation byte (msb = 1)

We should probably do this one, as it's much simpler, and our varints are not expected to ever get beyond 32bits.
Group varints are more complicated and harder to implement. I'll give a week for people to voice counter opinion.

So its like the Uvarint in go's stdlib? I should be able to use that library interchangeably?

To clear up:
10 bit number: 0bJIHGFEDCBA would be encoded as: 0b1HGFEDCBA, 0b0000000JI

@whyrusleeping not sure, verify for yourself. the above protocol is the correct description.

I'm annoyed that these are little-endian. Network things should always be big-endian. Wonder why protobuf made this call (go varints come from protobuf) ....
https://play.golang.org/p/EV9uyPWUKM
dec   hex varint  varint buf
1     0x01        [1]
127   0x7f        [127]
128   0x8001      [128 1]
200   0xc801      [200 1]
256   0x8002      [128 2]
1024  0x8008      [128 8]
16384 0x808001    [128 128 1]

But i guess, because protobuf varints have well tested impls in tons of langs.

We're going with these. I'm probably going to regret the endianness in a few years, but i rather not argue why people can't use existing protobuf implementations...


Block state with makeWithCommands is wrong for vanilla commands

[x] The readme doesn't contain a resolution to my issue
[x] The example doesn't contain a resolution to my issue

Versions

node: 14.15
prismarine-template: ?

Detailed description of a problem
makeWithCommands should return an array with setBlock commands to build the schematic within a vanilla server. For blocks containing block states the commands returned contain a space between the blockname and the state:
/setblock -45 74 -212 grass_block [snowy="false"]
Expected behavior
The command should not have a space between the block name and the block state for servers running 1.16 (and earlier?) like this:
/setblock -45 74 -212 grass_block[snowy="false"]

Pr #28


Remove callback parameter

The functions in the library support two ways of getting the result of the request back. One of them is through a promise that is returned in the call, and the other one is a callback parameter that gets called with the data and eventual error.
The support for Promise is quite widespread at the moment and additions to the language like async/await, which allows a concise syntax around Promises, make this option the preferred one.
The idea is to get through some of the packages and projects that depend on the library and analyze how frequently they use the callback function before getting rid of it.

I'm currently working on a TypeScript rewrite with backwards compatibility in mind (I'll see how far I get). Would it be a good compromise to keep callbacks but implement Promise support using the standard API available in ES6 and TypeScript? I feel like quite a few people still use this library in an ES5 library, so requiring them to use a Promise polyfill and convert code might be a little overwhelming for some.

Thanks for your input @adamgrieger! Promises are widely supported these days and they are easy to polyfill for those projects targeting browsers like IE 11 and older. I tend to prefer having one way of doing something in the library instead of having 2 and then keep supporting the magic that assumes callback or options depending on the type of the parameter passed.


Unable to run tests on macOS

I tried to run the unit tests for Fether with yarn; yarn run build; yarn run test, but it gives the error shown below. I'm using macOS 10.14. I switched to Node.js v10.14.2. I'm using Yarn version 1.12.3.
scon @ ~/code/src/paritytech/fether - [master] $ nvm use v10.14.2
Now using node v10.14.2 (npm v6.4.1)
scon @ ~/code/src/paritytech/fether - [master] $ yarn; yarn run build; yarn run test
yarn install v1.12.3
[1/5] 🔍  Validating package.json...
[2/5] 🔍  Resolving packages...
success Already up-to-date.
✨  Done in 1.23s.
yarn run v1.12.3
$ lerna run build
lerna info version 2.11.0
$ rimraf lib
$ babel src --out-dir lib
🎉  Successfully compiled 35 files with Babel.
$ npm-run-all build-*
$ node-sass-chokidar src/ -o src/
$ react-app-rewired build
Creating an optimized production build...
Compiled successfully.

File sizes after gzip:

  400.53 KB (-37 B)  build/static/js/main.d6d9ed42.js
  45.51 KB           build/static/js/1.69905f60.chunk.js
  16.71 KB           build/static/js/0.2d7b1594.chunk.js
  7.04 KB            build/static/css/main.085abab8.css

The project was built assuming it is hosted at ./.
You can control this with the homepage field in your package.json.

The build folder is ready to be deployed.

Find out more about deployment here:

  http://bit.ly/2vY88Kr

$ copyfiles -u 2 "../fether-react/build/**/*" static/ && ./scripts/fixElectronBug.sh
$ electron-webpack
Hash: 7d4827e6b84c097663d4
Version: webpack 4.12.1
Child
    Hash: 7d4827e6b84c097663d4
    Time: 1390ms
    Built at: 12/15/2018 1:15:37 AM
          Asset      Size  Chunks             Chunk Names
        main.js   8.3 KiB       0  [emitted]  main
    main.js.map  9.65 KiB       0  [emitted]  main
     [0] external "electron" 42 bytes {0} [built]
     [1] external "@parity/electron" 42 bytes {0} [built]
     [2] ./package.json 1.56 KiB {0} [built]
     [3] external "fs" 42 bytes {0} [built]
     [4] ./electron-builder.json 346 bytes {0} [built]
     [5] external "pino" 42 bytes {0} [built]
     [6] external "commander" 42 bytes {0} [built]
     [7] external "pino-multi-stream" 42 bytes {0} [built]
     [8] external "url" 42 bytes {0} [built]
     [9] external "path" 42 bytes {0} [built]
    [10] external "commander-remaining-args" 42 bytes {0} [built]
    [11] ./src/main/index.js + 6 modules 11.9 KiB {0} [built]
         | ./src/main/index.js 4.05 KiB [built]
         | ./src/main/menu/index.js 2.09 KiB [built]
         | ./src/main/cli/index.js 1.54 KiB [built]
         | ./src/main/utils/pino.js 1.55 KiB [built]
         | ./src/main/utils/handleError.js 1.03 KiB [built]
         | ./src/main/messages/index.js 1.13 KiB [built]
         | ./src/main/utils/staticPath.js 434 bytes [built]
    [12] multi ./src/main/index.js 28 bytes {0} [built]
lerna success run Ran npm script 'build' in packages:
lerna success - fether
lerna success - fether-react
lerna success - fether-ui
✨  Done in 57.55s.
yarn run v1.12.3
$ semistandard '**/*.{js,ts}' --parser babel-eslint && CI=true lerna run test --parallel
lerna info version 2.11.0
lerna info run in 2 package(s): npm run test
fether: $ echo Skipped.
fether-react: $ react-app-rewired test --env=jsdom
fether: Skipped.
fether-react: /Users/scon/code/src/paritytech/fether/node_modules/react-scripts/scripts/test.js:20\n  throw err;\n  ^
fether-react: Error: No available storage method found.\n    at /Users/scon/code/src/paritytech/fether/node_modules/localforage/dist/localforage.js:2743:25\n    at process._tickCallback (internal/process/next_tick.js:68:7)
fether-react: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
fether-react: error Command failed with exit code 1.
lerna ERR! execute callback with error
lerna ERR! Error: Command failed: yarn run test
lerna ERR! /Users/scon/code/src/paritytech/fether/node_modules/react-scripts/scripts/test.js:20
lerna ERR!   throw err;
lerna ERR!   ^
lerna ERR!
lerna ERR! Error: No available storage method found.
lerna ERR!     at /Users/scon/code/src/paritytech/fether/node_modules/localforage/dist/localforage.js:2743:25
lerna ERR!     at process._tickCallback (internal/process/next_tick.js:68:7)
lerna ERR! error Command failed with exit code 1.
lerna ERR!
lerna ERR! $ react-app-rewired test --env=jsdom
lerna ERR! info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
lerna ERR!
lerna ERR!     at Promise.all.then.arr (/Users/scon/code/src/paritytech/fether/node_modules/lerna/node_modules/execa/index.js:236:11)
{ Error: Command failed: yarn run test
/Users/scon/code/src/paritytech/fether/node_modules/react-scripts/scripts/test.js:20
  throw err;
  ^

Error: No available storage method found.
    at /Users/scon/code/src/paritytech/fether/node_modules/localforage/dist/localforage.js:2743:25
    at process._tickCallback (internal/process/next_tick.js:68:7)
error Command failed with exit code 1.

$ react-app-rewired test --env=jsdom
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

    at Promise.all.then.arr (/Users/scon/code/src/paritytech/fether/node_modules/lerna/node_modules/execa/index.js:236:11)
    at process._tickCallback (internal/process/next_tick.js:68:7)
  code: 1,
  killed: false,
  stdout:
   '$ react-app-rewired test --env=jsdom\ninfo Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.\n',
  stderr:
   '/Users/scon/code/src/paritytech/fether/node_modules/react-scripts/scripts/test.js:20\n  throw err;\n  ^\n\nError: No available storage method found.\n    at /Users/scon/code/src/paritytech/fether/node_modules/localforage/dist/localforage.js:2743:25\n    at process._tickCallback (internal/process/next_tick.js:68:7)\nerror Command failed with exit code 1.\n',
  failed: true,
  signal: null,
  cmd: 'yarn run test',
  timedOut: false,
  exitCode: 1 }
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

it's working now, although i'm not sure what was originally wrong


USE-QA v3 to KerasLayer with trainable = True fail on fine-tune the model

(i) I define USE-QA for response and question encodes
USE_qa_response =  hub.KerasLayer('use-model/use-qa-model',                        input_shape=[],                        dtype=tf.string,                       output_key='outputs',                       signature='response_encoder',                        trainable=True)
USE_qa_question =  hub.KerasLayer('use-model/use-qa-model',                        input_shape=(),                        dtype=tf.string,                       output_key='outputs',                       signature='question_encoder',                        trainable=True)
(ii) Then, create a network for fine-tune the USE-QA
encode1 = USE_qa_response({'input': input1, 'context': context1})
  encode2 = USE_qa_question(questions)
(iii) After that, the error show
ValueError: Setting hub.KerasLayer.trainable = True is unsupported when calling a SavedModel signature.

Environment:
tensorflow == 2.4.1 tensorflow-hub == 0.11.0
If I change trainable = False it works! but the USE-QA won't fine-tune or change any parameter inside the model.
What should I do?

@mrpeerat,
The behavior seems to be expected as per the documentation of Arguments of Hub Keras Layer, mentioned below:

trainable | Optional. A boolean controlling whether this layer is trainable. Must not be set to True when using a signature (raises ValueError), including the use of legacy TF1 Hub format.

Since you are using signature='response_encoder', the argument, trainable should be set to False.

@mrpeerat,
The behavior seems to be expected as per the documentation of Arguments of Hub Keras Layer, mentioned below:

trainable | Optional. A boolean controlling whether this layer is trainable. Must not be set to True when using a signature (raises ValueError), including the use of legacy TF1 Hub format.

Since you are using signature='response_encoder', the argument, trainable should be set to False.

But if we set trainable = False the USE-QA will update the value or parameter inside the model?
Or what if we delete signature='response_encoder', I can't imagine how to implement fine-tune the USE-QA without the signature parameter, any suggestion?

Here is more information on why trainable = True is not supported when calling a SavedModel signature: https://github.com/tensorflow/hub/blob/a452309e69a9ec85641534a84016e92007785451/tensorflow_hub/keras_layer.py#L259
https://github.com/tensorflow/hub/issues/428#issuecomment-647191531 discusses a very similar problem and potential workarounds. Please reopen if you have further questions.


What model of AGN variability will we use for DC2?

In this comment, Eve notes that the galaxy catalogs produced by the CosmoSims code have black hole mass and accretion rate columns.  In the subsequent comment, Scott says it will take some work to incorporate those parameters into a model of variability for the AGNs that CatSim would serve up.  However, table 2 of the DC2 planning document (read-only) refers to a "damped random walk model" which must be something else.
@drphilmarshall Thoughts on what we should do for (presumably non-lensed) AGNs?

Also relevant for #59.

It's an old joke that whenever I meet someone new at a meeting, they introduce themselves by saying "I have a better AGN variability model than you do"....
Currently, CatSim models AGN using the damped random walk model from MacLeod et al (2010; ApJ 721, 1014), which Zeljko gave us (Zeljko being MacLeod's PhD advisor).  This model is parametrized in terms of the structure function of the random walk*.  We could certainly implement a different variability model that depends on the parameters in the DC2 catalog.  We could also find a mapping between blackhole accretion rate and the structure function.  I am not an expert in any of the underlying physics, but someone in this collaboration must be.
*For those who, like me did not know anything about damped random walks before having this conversation for the first time, the structure function is the asymptotic RMS variability of the AGN on long time scales.

  I don't claim to have a better model, but I can help sort out something that makes sense for DC2.

One thing that we may want to consider is that, if we have some model that
is not a random walk but is one that we think is OK, we may want to stick
in some sources with variability generated using that model.  I have no
idea if this is feasible, and it may make the complexity of the process too
high.  However, I worry when we are using the same model to generate things
(in this case light curves, eventually) that we might use to evaluate
them.  Maybe this isn't a big deal here, but the underlying unease that I
have is that if we tune our analysis code to produce the best results from
these simulations we may be losing some ability once we are confronted with
real data.  As I say, it's not clear to me that this is actually a worry,
but it would be nice to see if our codes deal well with data generated by
multiple models.
 I don't
claim to have a better model, but I can help sort out something that makes
sense for DC2.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/LSSTDESC/DC2_Repo/issues/55#issuecomment-352500146,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACCEUl3qUvWPt7bsCfhJb4gu3SYFh1gjks5tBqOYgaJpZM4RC1vA
.

--
Chris Fassnacht
Professor, Physics Dept.
UC Davis
1 Shields Ave.
Davis, CA 95616
+1-530-554-2600

Could we invert the problem?  That is, stick with data generated with one model, but then evaluate how well analysis codes that assume multiple models work?  Will that teach us as much as the process you described?   (or at least will it teach us enough for what we wanted to learn in DC2?)

Hi Rachel,
I'm not sure if your suggestion would address what worries me, since
presumably the codes that did better at handling the data generated by the
damped random walk model would be evaluated as "better".  However, all of
this may be moot for DC2.  Maybe it is fine to get something that does well
with damped random walk light curves now and then worry about whether that
paints us into a corner later on.
Chris
On Mon, Dec 18, 2017 at 11:59 AM, Rachel Mandelbaum <
<EMAIL_ADDRESS>wrote:

Could we invert the problem? That is, stick with data generated with one
model, but then evaluate how well analysis codes that assume multiple
models work? Will that teach us as much as the process you described? (or
at least will it teach us enough for what we wanted to learn in DC2?)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/LSSTDESC/DC2_Repo/issues/55#issuecomment-352541095,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACCEUmw8Hu6CX5b6g-7cQiGiYzL-U37yks5tBsQWgaJpZM4RC1vA
.

--
Chris Fassnacht
Professor, Physics Dept.
UC Davis
1 Shields Ave.
Davis, CA 95616
+1-530-554-2600

I'm not sure if your suggestion would address what worries me, since
presumably the codes that did better at handling the data generated by the
damped random walk model would be evaluated as "better".

That's true, they would be.  But that's not quite my point.  Consider two scenarios:

The codes that model the light curves as damped random walk do drastically better than the codes that model the light curves in some other way that we think is at least reasonably well-motivated.

The codes that model the light curves as damped random walk do only slightly better than the codes that model the light curves in some other way that we think is at least reasonably well-motivated.

In the first case, what we've learned is that our analyses depends sensitively on the match between the real and assumed AGN variability model, and so for DC3 we should spend some time/effort in getting the latest and greatest in the sims (and we also need to improve our modeling codes to avoid this sensitivity and marginalize over any unknown features in AGN variability).  In the second case, what we've learned is that multiple models that we think are physically plausible do nearly as well as each other, so we're not too sensitive to the AGN variability model in the sims -> we can focus on other things, both in DC3 sims and in developing modeling codes.
I admit I may be missing something, as I'm not an expert, but I feel this could still be informative.

Hi Rachel,
I hadn't thought about it that way.  What you say makes sense, so we
probably don't have to worry about multiple generative models at this point.
Ciao,
Chris
On Mon, Dec 18, 2017 at 4:23 PM, Rachel Mandelbaum<EMAIL_ADDRESS>
wrote:

I'm not sure if your suggestion would address what worries me, since
presumably the codes that did better at handling the data generated by the
damped random walk model would be evaluated as "better".
That's true, they would be. But that's not quite my point. Consider two
scenarios:

The codes that model the light curves as damped random walk do drastically
better than the codes that model the light curves in some other way
that we think is at least reasonably well-motivated.
2.
The codes that model the light curves as damped random walk do only
slightly better than the codes that model the light curves in some
other way that we think is at least reasonably well-motivated.
In the first case, what we've learned is that our analyses depends
sensitively on the match between the real and assumed AGN variability
model, and so for DC3 we should spend some time/effort in getting the
latest and greatest in the sims (and we also need to improve our modeling
codes to avoid this sensitivity and marginalize over any unknown features
in AGN variability). In the second case, what we've learned is that
multiple models that we think are physically plausible do nearly as well as
each other, so we're not too sensitive to the AGN variability model in the
sims -> we can focus on other things, both in DC3 sims and in developing
modeling codes.
I admit I may be missing something, as I'm not an expert, but I feel this
could still be informative.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/LSSTDESC/DC2_Repo/issues/55#issuecomment-352600421,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACCEUpwwElOtdxFedFvC7miRWE-Ue7Tdks5tBwHzgaJpZM4RC1vA
.

--
Chris Fassnacht
Professor, Physics Dept.
UC Davis
1 Shields Ave.
Davis, CA 95616
+1-530-554-2600

As discussed on Slack starting here
https://lsstc.slack.com/archives/C77DDKZHR/p1527991352000121
my somewhat naive application of the fitting formulae from MacLeod et al has led to an AGN that varies from a mean magnitude of about 28 all the way up to magnitude 4.5.  Probably we just need to impose a hard cut on the maximum allowable value of the structure function for the random walk driving AGN variability.  Does 4 magnitudes seem reasonable?  Summarizing from Slack, the mean, median, and standard deviations of the structure functions produced by the current code are
# band mean median stdev
u 1.317624e+00 1.183000e+00 6.879020e-01
g 1.159129e+00 1.041000e+00 6.057803e-01
r 1.024631e+00 9.198000e-01 5.369232e-01
i 9.325369e-01 8.375000e-01 4.874273e-01
z 8.717454e-01 7.825000e-01 4.563290e-01
y 8.265397e-01 7.417000e-01 4.336567e-01

How many sigma away from the relevant band mean structure function was this
object? Given that we are only modeling the distribution approximately,
seems something like a 3-sigma clip could be justified?

The offensive object had structure functions on the order of 10 to 20, so: 10 to 20 sigma

That is quite the random draw. We might think of permitting 5-sigma
outliers, just to make things interesting!

It wasn't a random draw that caused the structure functions to be so large.  The phenomenological fit that we are applying is only valid in a certain regime of parameter space and we applied it outside that regime.  More specifically, the structure function is calculated by this code
   AA = -0.56
    BB = -0.479
    CC = 0.111
    DD = 0.11

    if rng is not None:
        if isinstance(redshift, numbers.Number):
            n_obj = 1
        else:
            n_obj = len(redshift)
        AA += rng.normal(0.0, 0.01, size=n_obj)
        BB += rng.normal(0.0, 0.005, size=n_obj)
        CC += rng.normal(0.0, 0.005, size=n_obj)
        DD += rng.normal(0.0, 0.02, size=n_obj)

    eff_wavelen_rest = eff_wavelen/(1.0+redshift)

    log_sf = AA + BB*np.log10(eff_wavelen_rest/4000.0)
    log_sf += CC*(M_i+23.0) + DD*(np.log10(mbh)-9.0)

The offending AGN had an M_i (absolute i band magnitude) of about -3, which was low enough log_sf became very positive.

@danielsf  So a readiness test on the instance catalog would have caught this issue. Sorry, I haven't kept track, but since we have an instance catalog reader and the DESCQA readiness test is quite generic, I think it could be adapted fairly easily for these kinds of checks.

I have run the script assigning AGN magnitudes and variability parameters to 0.1 version of cosmoDC2.  Naively doing what we did for run 1.2 (only accepting galaxies with black hole masses > 10**7 solar masses; throwing out AGN with apparent i-band magnitudes greater than 30; limiting structure functions to 4 magnitudes), I get the following distributions:
1-D distribtions of tau (timescale of variation in days) and i-band structure function. Different colors correspond to different cuts in observed r-band magnitude

2-D densities of observed r-band magnitude versus redshift, black hole mass, and Eddington ratio

2-D densities of absolute i-band magnitude versus redshift black hole mass and Eddington ratio

The distribution of tau and SF_i found in the MacLeod et al reference that our model is based on looks like this:

This is taken from SDSS.  The white histogram is all sources out to observed r-band of 22.5; the filled histogram is sources with absolute i-band magnitude between -26 and -27.   MacLeod et al considered 290 square degrees and found 9,275 spectroscopically confirmed AGN.  Obviously there are orders of magnitude more than that in cosmoDC2.  I do not know if that is because of selection effects in MacLeod et al, or if we need to thin out our simulation.
How do AGN experts feel about these distributions?

For reference, the underlying black hole model that generates this mock catalog has black hole masses determined by the M_bulge-M_bh power law taken from Kormendy & Ho 2013, and AGN accretion rate distributions taken from Aird, Coil & Georgakakis (2017).

@danielsf @jchiang87 Obviously we did make a final decision in DC2 :-) Two questions: (i) Is the write-up in the current DC2 paper draft (https://www.overleaf.com/8574729384jttdkyjcbgyq) sufficient to capture what was done? (ii) Is something different needed for the future? If so, we should capture that somewhere. I think then we can close this issue? Thanks!

I gave the paragraph in the DC2 paper dealing with this a once-over.  It looks sufficient.  @jiwoncpark has been doing some validation on the AGN population in run 2.*.  Hopefully, we will turn that into a DESC note or paper.

There's a mention above of considering whether the accretion is efficient vs. inefficient.  How is that handled in the output catalogs / mapping to observables?  For quiescent galaxies, something like 90%-95% of the time, when the accretion rate is low there should be no detectable optical flux from the AGN (i.e. you can't detect emission lines at all, which will be much easier to detect than continuum).

I don't think anything ever came of that statement (efficient vs. inefficient accretion).

Could somebody (@evevkovacs maybe you can help with this?) put a final summary in here with maybe links to the description of the new AGN approach that we will use in the DDF? We also need to update the DC2 paper draft. And then close this issue? Thanks!


Validate data

💁♂ Problem/Context
Each customer that creates an account should only be able to do so once with a single email address
📖 User Story
Have validated data to ensure reliability.
🎨 Design
Provide a link to the prototype and/or screenshot

🉑 Acceptance Criteria
What needs to be done to move this to Done?

🙅♂ Out of scope
What is not part of the scope? Explicitly mention it

🙈 User Roles
How will it work with different user roles/permissions? (if applicable)

💵 Pricing
What plan will this be available on? (Plan 1, Plan 2 etc.)

🎯 Measuring Success
How do we know we are successful? Do we need new events to track or update existing ones?

🛳 Release Strategy
Are we doing A/B testing? Are we releasing it internally? Are we going straight to General Availability?

❓Other Questions to think about
Do we have experience with this? How it will work with Feature XYZ? Does it our onboarding experience? How long will it take us?

Link to feature: https://shopperettes.productboard.com/feature-board/planning/features/18248798


Undefined property: DOMComment::$wholeText

Hello, the DOMComment object has no wholeText property.
https://github.com/voku/HtmlMin/blob/0da9ff11be965bac32ffb867d5f2092a8e321f8a/src/voku/helper/HtmlMin.php#L836-L838
I added a test and applied a possible fix.

This change is

Thanks for the fix, merged.


\machine\c$\folder type locations do not work on Windows

When accessing network shares on windows, the paths have the structure \machine\share or \machine(drive-letter)$\folder.
It is currently not possible to open network shares directly using NERDTree - when you attempt to do so, NERDTree responds with:
NERDTree: No bookmark or directory found for X
This looks to be something to do with the plugin expecting a drive letter if s:running_windows is true.
Unfortunately I'm not able to mount the share I'm after as a network drive with a letter on the machine I'm working on :-(

Closing this off as the pull request was accepted.


Fix incorrect tls code

TLS connections, and elevating a connection with STARTTLS are mutually exclusive, and should be two different functions. This code Breaks out TLS, and STARTTLS with SendWithTLS, and SendWithStartTLS.

I've tested this with STARTTLS and it's working as expected. I don't have a SMTP server to test SendWithTLS against. This should resolve #71

+1 for this fix as I have the same issue as #71 which forces me to use commit 94ae17d.

Hi there!
My apologies for how long it took me to get back to this. I've unfortunately had very little time to do maintenance on this library.
This LGTM. I apologize for not catching the breaking change in 27742b011ce59bee8fe7b7f1383449193a8e2c9f. That's my fault.
Thanks for taking the time to diagnose and send this in! Since this modifies the external API, I'll tag a new major release version soon.


Having my own tables inside traccar database

hi,
I use MySQL with Traccar. Do you think it would be a bad (or good?) idea if I had couple of my own tables in traccar database? I'd be using these tables to store some additional information about the devices, users etc. I could have these tables in a different database too but it unnecessariy complicates things I guess - so thought of creating those tables in traccar db itself.
Cheers,
M.M

It should be fine.

cool thanks :+1:


⚠ Shadow Does Streams has degraded performance

In ab6504d, Shadow Does Streams (https://stream.everythingbagel.me) experienced degraded performance:

HTTP code: 200
Response time: 6498 ms

Resolved: Shadow Does Streams performance has improved in 1b85dad after 10 minutes.


Opening 2D/3D scene when no scene was previously open no longer switches to 2D/3D viewport

Tested versions

Reproducible in 4.3.stable and 4.4.dev (514c564a8c855d798ec6b5a52860e5bca8d57bc9)
Not reproducible in 4.2.2.stable

System information
Fedora Linux 40 (KDE Plasma) - Wayland - Vulkan (Forward+) - dedicated AMD Radeon RX 7600M XT (RADV NAVI33) - AMD Ryzen 7 7840HS w/ Radeon 780M Graphics (16 Threads)
Issue description
Godot has this nifty behavior that it can detect the type of a scene (2D or 3D) based on its root node, and infer the viewport (2D/3D) to open for that scene accordingly.
This seems to have regressed in 4.3.stable and later.
What works:

Open a 2D scene and make sure to be on the 2D viewport.
Open a 3D scene: it will switch to the 3D viewport.
Close the 2D scene, reopen it: it will switch to the 2D viewport.

What doesn't work:

Have no scene open, make sure to be on the 2D viewport.
Open a 3D scene: it stays on the 2D viewport.
Close the 3D scene, make sure to be on the 3D viewport.
Open a 2D scene: it stays on the 3D viewport.

CC @KoBeWi
Steps to reproduce
See above.
Minimal reproduction project (MRP)
Test2DAnd3DScenes.zip

Bisecting points to #91435 as the culprit, @ajreckof

Read the https://github.com/godotengine/godot/pull/91435 description seems like this was a bugfix, but I not sure how to restore it without breaking it.

So what happens here is that when opening a scene it was always selecting the root of the scene when loading in addition to whatever the selection was and this made a lot of problems. The fact that it was switching to the 2D/3D viewer was simply a consequence of this selection. One thing I suggested was to add back the selection in the cases where there is no prior selection. If the switch is always wanted whatever the selection and only depending on the root node then I could add a patch in this way too.

If the switch is always wanted whatever the selection and only depending on the root node then I could add a patch in this way too.

This seems to be the old behavior. #91411 is a regression between dev5 and dev6. In dev5 root node is not selected, but the editor switches correctly.


Make Azure Kubernetes LTS dates consistent

In #6123 an LTS date for Azure Kubernetes 1.30 was added. The fields used are inconsistent with the existing LTS dates for 1.27.
In 1.27 the eol field was used for the LTS EOL date, and the lts field was used for the original non-LTS eol date. In 1.30 these fields have been switched. The 1.27 data also has an eoas field with the same value as lts which gets rendered as a field called support which does not exist for 1.30.
It makes more sense to me to use the eol field for the original non-LTS EOL date, and the lts field for the extended LTS EOL date. So this PR updates the 1.27 data to be consistent with the 1.30 data.

cc @MathieuPuech @chenrui333 as author and reviewer of #6123

Could you make at least the dates of (releae ) 1.30 and 1.7's lts/eol dates same ?

Just for clarity:
lts is meant to hold the LTS status for a release (bool). In case an exact LTS start date is available (since many products promote a release to LTS after some time), we use the lts parameter as a date. This is the relevant explanation from https://endoflife.date/contribute:

# Whether this is a "LTS" release (optional, default = false).
# What LTS means may differ from product to product (see LTSLabel above).
# Only provide for a release that will get much longer support than usual.
# Alternatively, this can be set to a date when the product is not labeled
# as LTS when it is released (ex. Angular) or when normal versions are
# promoted LTS after their release (ex. Jenkins).

As such:

lts should be set to the midway mark for LTS release (releaseDate+1y)
eol should be set to releaseDate + 1y for non-LTS releases, and releaseDate + 2y for LTS releases.