BUG: JSDocs in wrong place with vue-tsc --declaration --emitDeclarationOnly

If I execute:

vue-tsc --declaration --emitDeclarationOnly

The JSDocs from my props don't show up based on the generated MyComponent.d.ts file.
I figured out the correct place for the JSDocs to work properly, so my request is that you duplicate them twice and add them to the correct place as well in the .d.ts file.
input Vue file
<template>
  <div class="pepicon" />
</template>

<script setup lang="ts">
import { defineProps, PropType } from 'vue'
import { Pepicon } from 'pepicons'

defineProps({
  /**
   * The icon name as per the reference at https://pepicons.com
   * @type {'airplane' | 'angle-down'}
   * @example 'airplane'
   */
  name: {
    type: String as PropType<Pepicon>,
    required: true,
  },
})
</script>

current output .d.ts file
With this output the JSDocs don't show up in Vite Vue 3 project
import { PropType } from 'vue';
import { Pepicon } from 'pepicons';
declare const _default: import("vue").DefineComponent<{
    /**
     * The icon name as per the reference at https://pepicons.com
     * @type {'airplane' | 'angle-down'}
     * @example 'airplane'
     */
    name: {
        type: PropType<Pepicon>;
        required: true;
    };
}, () => void, unknown, {}, {}, import("vue").ComponentOptionsMixin, import("vue").ComponentOptionsMixin, Record<string, any>, string, import("vue").VNodeProps & import("vue").AllowedComponentProps & import("vue").ComponentCustomProps, Readonly<{
    name?: unknown;
} & {
    name: Pepicon;
} & {}>, {}>;
export default _default;

desired output .d.ts file
With this output the JSDocs show up correctly in Vite Vue 3 project
import { PropType } from 'vue';
import { Pepicon } from 'pepicons';
declare const _default: import("vue").DefineComponent<{
    /**
     * The icon name as per the reference at https://pepicons.com
     * @type {'airplane' | 'angle-down'}
     * @example 'airplane'
     */
    name: {
        type: PropType<Pepicon>;
        required: true;
    };
}, () => void, unknown, {}, {}, import("vue").ComponentOptionsMixin, import("vue").ComponentOptionsMixin, Record<string, any>, string, import("vue").VNodeProps & import("vue").AllowedComponentProps & import("vue").ComponentCustomProps, Readonly<{
    /**
     * The icon name as per the reference at https://pepicons.com
     * @type {'airplane' | 'angle-down'}
     * @example 'airplane'
     */
    name?: unknown;
} & {
    /**
     * The icon name as per the reference at https://pepicons.com
     * @type {'airplane' | 'angle-down'}
     * @example 'airplane'
     */
    name: Pepicon;
} & {}>, {}>;
export default _default;

PS, I already am a monthly supporter, but I just made a one time sponsor of 50 usd  : )

@johnsoncodehk  PS, I already am a monthly supporter, but I just made a one time donation of 50 usd  : )

@mesqueeb Thanks! But I think this problem should be resolve in vue-next repo, I will research on it.

@johnsoncodehk thank you very much. This is a key issue for Volar to be able to have JSDocs show up together with the current VSCode autocomplete.
A key feature for components hosted on NPM. : )
Do you have any issue you can link here in the vue-next repo so I can track of any updates related to this?
Thank you very much.

@mesqueeb It should be a DefineComponent type issue, so I will just send a PR if I can resolve.

See https://github.com/vuejs/vue-next/pull/5166.

@johnsoncodehk I saw that the PR was merged. Any idea when it will be live on vue-tsc ?

@mesqueeb I can't say, the timing of the release of vue is decided by Evan.

You can use https://github.com/knightlyjs/knightly

@johnsoncodehk interesting!! I will check it out. However since the issue is upstream, do I need to make sure that both Vue and Vue-Tsc are on knightly? Seems a bit complex! 😅
Btw, I will post more details later, but it seems with script setup, defining props only in TypeScript, all JSDocs are shipped out as well.

@mesqueeb vue-tsc is not relevant to this, you just need to update vue.

@johnsoncodehk knightly-bot seems to not function right now, so I couldn't test.
Can you check this case as well? Currently it strips out JSDocs completely which is not desired:
input
const props = withDefaults(
  defineProps<{
    /**
     * The icon name as per the reference at https://pepicons.com
     * @example 'airplane'
     */
    name: Pepicon
  }>(),
  {
    name: 'airplane',
  },
)

expected output
import { Pepicon } from 'pepicons';
declare const _default: import("vue").DefineComponent<{
    /**
     * The icon name as per the reference at https://pepicons.com
     * @example 'airplane'
     */
    name: {
        type: import("vue").PropType<Pepicon>;
        required: true;
    } & {
        default: string;
    };
}, {}, unknown, {}, {}, import("vue").ComponentOptionsMixin, import("vue").ComponentOptionsMixin, Record<string, any>, string, import("vue").VNodeProps & import("vue").AllowedComponentProps & import("vue").ComponentCustomProps, Readonly<{
    /**
     * The icon name as per the reference at https://pepicons.com
     * @example 'airplane'
     */
    name?: unknown;
} & {
    /**
     * The icon name as per the reference at https://pepicons.com
     * @example 'airplane'
     */
    name: Pepicon;
} & {}>, {
    /**
     * The icon name as per the reference at https://pepicons.com
     * @example 'airplane'
     */
    name: Pepicon;
}>;
export default _default;

current output
import { Pepicon } from 'pepicons';
declare const _default: import("vue").DefineComponent<{
    name: {
        type: import("vue").PropType<Pepicon>;
        required: true;
    } & {
        default: string;
    };
}, {}, unknown, {}, {}, import("vue").ComponentOptionsMixin, import("vue").ComponentOptionsMixin, Record<string, any>, string, import("vue").VNodeProps & import("vue").AllowedComponentProps & import("vue").ComponentCustomProps, Readonly<{
    name?: unknown;
} & {
    name: Pepicon;
} & {}>, {
    name: Pepicon;
}>;
export default _default;

I'd love to test this on the new version of Vue! can you help me test it or show me how/where I can do so myself? 😊

@mesqueeb Under some conditions TS will precompute the output type, vue-tsc cannot avoid it. But you can avoid it by using defineProps<{ ... }>() instead of defineProps({ ... }).
const props = defineProps({
  /**
   * The icon name as per the reference at https://pepicons.com
   * @example 'airplane'
   */
  name: {
    type: Object as PropType<Pepicon>,
    default: 'airplane',
  }
})

@johnsoncodehk I am using defineProps<{ ... }>() already, yet it will strip out the JSDocs.
I was really excited that I could finally just define purely TS interfaces that represent the props of a component.
But if you're saying that there is no way to keep JSDocs when defining props purely in TS interfaces like so:  defineProps<{ ... }>() then I'd love to open a FR somewhere to request this.
In my mind vue-tsc is the library that creates the TS declaration files for component-libraries, so should I open the FR here? If not, could you help guide me where/how I best request this?
I think it will benefit the whole ecosystem when: (1) Vue component libraries can have their props defined in pure TS interfaces and (2) any JSDocs added to these actually show up in VSCode for devs who use those component libraries.
Interested to hear your thoughts on this! : )

Sorry I made a typo, it should be use defineProps({ ... }) instead of defineProps<{ ... }>(), just like my sample. With defineProps({ ... }) + next version, it should have completely support.

But if you're saying that there is no way to keep JSDocs when defining props purely in TS interfaces like so: defineProps<{ ... }>() then I'd love to open a FR somewhere to request this.

The right place is https://github.com/microsoft/TypeScript/issues, but I don't think they have much chance of supporting that.

Sorry I just found that this problem can actually simplify the virutal code to avoid! Please try<EMAIL_ADDRESS>

@johnsoncodehk the issue is gone on latest vue-tsc version!
the JSDoc is now correctly shown on hover:

(sorry I meant to get back to you sooner)


Use fields from servers table to substitute in the config.

We need to replace here the values of ca, crt, and key with corresponding values from server model.
https://github.com/Mehonoshin/smartvpn-billing/blob/master/config/sample.server.ovpn.erb
Also we'd like to display them at server's page.

Solved!


fix: Add missing export for Ec2Runner

fixes #161

I can't get push working locally right now. Can you run npm run build and push the new API.md? Or I can try some more later.


Alphabetize makefile targets

Sorts the makefile targets alphabetically
I didn't see a reason why they weren't and there didn't seem to be any cohesion between them, so sort them alphabetically (except default) to make it easier to find things.
Signed-off-by: Christopher Jones<EMAIL_ADDRESS>

LGTM

LGTM

@mavenugo Looks like #20398 in experimental

@tonistiigi Sorry. I dont understand the context of your comment in this PR ?

@mavenugo Just fyi that the experimental CI for this PR failed with the same error that is in #20398 https://jenkins.dockerproject.org/job/Docker-PRs-experimental/22905/console


Support Chart Labels

Detailed Description

It would be better if the chart displays a generated scale from the given data on the Y Axis or both
Context
It can be beneficial for improving the chart overall display

I would also like this to become a feature - it would allow for much more detailed charts.
+1


parallel downloads with librepo

Note:
we will unvendor the indicators library once there is a conda package for it!

Remaining issues with this code:

Python needs to be cleaned up, and FastSubdirData needs to be removed for good.
We might have to use cURL directly because conda set's some headers, and also adds some header data to the metadata:

It is adding these:
    headers = {}
    if etag:
        headers["If-None-Match"] = etag
    if mod_stamp:
        headers["If-Modified-Since"] = mod_stamp

    headers['Accept-Encoding'] = 'gzip, deflate, compress, identity'
    headers['Content-Type'] = 'application/json'

and saving these with the metadata:
    add_http_value_to_dict(resp, 'Etag', saved_fields, '_etag')
    add_http_value_to_dict(resp, 'Last-Modified', saved_fields, '_mod')
    add_http_value_to_dict(resp, 'Cache-Control', saved_fields, '_cache_control')

We could also ignore this and save the mamba metadata in a different place, disregarding these headers and just using a timeout set through the setting (which is how linux is usually doing it I guess).

@JohanMabille @davidbrochart
I have written down some C++ stuff to tackle :)
Most of this concerns the subdirdata.hpp file.
librepo:
for metadata download we can't set or retrieve custom headers, but this would be needed for full compatibility of the downloaded metadata with conda.
the alternative is be to use cURL (libCURL) directly through C++.
currently there is a setting in librepo to manage the maximum number of parallel downloads.
we should figure out if we can limit the maximum number of downloads with taskflow as well. If yes, that would be great.
Maybe we should have one job with N connection sub-threads where each thread has a connection for downloading data.
Other C++ stuff:
figure out how we can use  with C++...
better wrapper around libarchive (https://github.com/wolfv/mamba/blob/79f98d4b48c6effaff04a8c2ab2d2ea083e3ecd0/include/subdirdata.hpp#L33-L75)
Make sure that local URL's work
Make sure that cache directory exists from within C++. E.g. this line fails if the ~/miniconda3/pkgs/cache/ folder does not exist. Some functions for filesystem path creation etc. are in the experimental branch here https://github.com/wolfv/mamba/blob/c7fdd67572ff568b107f43fe7b9e6c58d897fff3/experiments/path.hpp#L116-L143
https://github.com/wolfv/mamba/blob/79f98d4b48c6effaff04a8c2ab2d2ea083e3ecd0/include/subdirdata.hpp#L258

librepo:
for metadata download we can't set or retrieve custom headers, but this would be needed for full compatibility of the downloaded metadata with conda.

I think that adding the ability to do this in the librepo API would be a welcome addition. There are many cases where this makes sense, even for rpm ecosystem repodata fetching.


Explicit check for leaf parent element presence for updates_for

In certain scenarios, the call to recursive updates associated with updates_for may fail if the leaf's parent Element is null.
This results in an error similar to the following:
Uncaught TypeError: e2.parentElement is null
To prevent the error we'll perform an explicit check on the presence of the parent element before attempting to call closest().

Would you mind running yarn run prettier-standard:format and commiting again, please?

Thanks for the review @leastbad! Command run, commit amended.


there is a bug about train_loss

when training, the avg_loss = train_loss / log_interval, while train_loss is always 0

fixed


fix: remove rn 72 hack  (PR: 3)

RN 72 is entering EOL, and now that Lottie-iOS requires iOS 13 and above, we can safely discard the old hack that we had here
https://github.com/reactwg/react-native-releases/blob/main/docs/support.md

Let's add a compatibility table to the readme later.


Newvers2

Removed unneeded deps and tests ( Julia 1.3 <)

Codecov Report

Merging #3 into master will increase coverage by 11.01%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master       #3       +/-   ##
===========================================
+ Coverage   77.96%   88.98%   +11.01%
===========================================
  Files           5        5
  Lines         118      118
===========================================
+ Hits           92      105       +13
+ Misses         26       13       -13

Impacted Files
Coverage Δ

src/analysis_recipes.jl
85.50% <0.00%> (+14.49%)
:arrow_up:

src/trigger_keys.jl
75.00% <0.00%> (+75.00%)
:arrow_up:

Continue to review full report at Codecov.

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


SMP Data: first fragments are truncated

The first L2CAP fragments of SMP packets are truncated when capturing HCI logs using WPR or BTVS.
Log 1 (btvs) = DellLatitudeE7240.zip
Captured with Windows 11 on a Dell Latitude E7240 laptop with intel 7260 Bluetooth chip (see report_2021-7-12_19-2-48.txt)
See red and green markers in the HCI overview (Note: because of a sniffer issue they only appear in the Instant Timing view, then one can double click from there on the packet to make them appear in the HCI Injection Overview) : first fragments are truncated, others are not.
Here the air log was captured at the same time and we can map those HCI packets to the L2CAP packets exchanged over the air (yellow markers). Pairing was successful, what was exchanged on HCI was correct, it must be just btvs that truncates the data.
Log 2 (etl) = etl: BthTracing.zip and extracted cfa: BthTracing.btt.zip
Captured with Windows 10 PRO 21H1 on a Dell Vostro 3591 with Qualcomm 11ac QCA 9377 Bluetooth chip, driver version <IP_ADDRESS>3
Here we don't have the air logs and this is the problem: we cannot see what the SMP problem was :-(
Note: this is somewhat similar to https://github.com/microsoft/busiotools/issues/85.

I left a comment on #85. This should be the same issue.

Thank you @erikpe-msft, clicking "Full Packet Logging" indeed fixed the issue.
Leaving this issue open still for now, as a reminder for you to document this feature.
Also, how can you enable this directly in WPR?

@XavierBoniface : btvs is currently the only way to enable full packet logging. In order to capture sensitive data with wpr, you'll need to run btvs and click Full Packet Logging, once, on that test system. Then you can close btvs. After that, wpr should capture the sensitive data just like btvs.

Thank you. Yes, I had inferred that method already. It's just a bit cumbersome for a user that will only use wpr to have to install and run another tool (btvs) to change a configuration that affects also wpr. I had expected that there was an option in wpr to achieve the same.


Fix Traceflow e2e test to work on a 2-Node cluster

workerNodeName(2) implies that the cluster has 3 Nodes
Also include a 30m timeout value in the README instructions for running
e2e tests locally, since we now largely exceed the default 10m value.

/test-e2e

skipping unrelated tests
/skip-conformance
/skip-networkpolicy
/skip-windows-conformance
/skip-windows-networkpolicy


Prometheus unable to scrape node-exporter after upgrade 1.7.6 -> 1.8.4

(NOTE: This is used to report product bugs:
To report a security vulnerability, please visit https://istio.io/about/security-vulnerabilities
To ask questions about how to use Istio, please visit https://discuss.istio.io)
Bug description
We are running an istio sidecar proxy on our prometheus server which is scraping pods in our cluster. When upgrading from istio 1.7.6 to istio 1.8.4 prometheus is unable to scrape the node exporter. Logging level set to verbose gives the following message from the sidecar proxy.
2021-04-08T08:57:24.589761Z     debug   envoy http      [C149][S17405316898299644747] Sending local reply with details route_not_found
What we thought could be the issue is that the node-exporter is running as a headless service so we tried enabling the setting on pilot with PILOT_ENABLE_EDS_FOR_HEADLESS_SERVICES by setting it to true but no change.
Affected product area (please put an X in all that apply)
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[x] Upgrade
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
Expected behavior
The prometheus pod is able to scrape the node-exporter
Steps to reproduce the bug
Install istio 1.7.6 via operator
Install prometheus with node-exporter via this helm chart: https://github.com/helm/charts/tree/master/stable/prometheus with version 10.5.1. Prometheus running with sidecar, node-exporter without.
Upgrade istio to 1.8.4, prometheus is unable to scrape
Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
istioctl
client version: 1.8.4 control plane version: 1.8.4 data plane version: 1.8.4 (x proxies)
kubctl
Client Version: v1.20.2 Server Version: v1.18.9-eks-d1db3c
How was Istio installed?
Istioctl using operator init.
IstioOperator CustomResource installed through helm.
Environment where the bug was observed (cloud vendor, OS, etc)
Amazon EKS.
Additionally, please consider running istioctl bug-report and attach the generated cluster-state tarball to this issue.
Refer cluster state archive for more details.

do you have a config dump (https://github.com/istio/istio/wiki/Troubleshooting-Istio) and some more context in the debug logs (it should show the request that failed)?

Sure, so I have identified the issue. When I switch it to not being a headless service it works.
Providing config dump with and without the headless service. So it is the node-exporter parts
config_dump_headless.json.zip
config_dump_clusterIP.json.zip


Santa Clara County (and others) Daily Data Disappeared

Hello,
The tab containing # of cases per day for many counties, such as Santa Clara county, has disappeared. Is this intentional?
I really liked that feature personally! Curious about its disappearance. Thank you for your time and work!

hi, is this what you are looking for?

Or are you referring to the previous "Daily" chart? I removed it because I thought no one is using it. lol.

this is the one that I disabled (and can be brought back easiy)

this is largely duplicative with the previous one.

Is there a way on the main graph to hide the total # confirmed and auto scale around just the daily data?
I liked the simpler looking graph for easy to read screencaps, but can understand that behavior is largely redundant from a functional standpoint.
This looks like plot.ly Dash - there was an option to make the series hideable IIRC - maybe that would do it?

sorry, didn't see the comment until today. You can click on the label to enable/disable the data series.
for instance, the Confirmed (total) is disabled here.


It doesn't respect vim colorscheme

Hi there, here's couple screenshots with upterm (left) and iterm (right):
Solarized dark:

Solarized light:

I found a couple already closed issues: #1116 and #962, but I don't know if they are really about the same stuff. I use upterm 0.4.3, so the last one from release pages. I've installed it through homebrew.

Btw, on GNU/Linux it works great though. I've checked on Arch Linux with i3wm.


Error when extending null

    class C extends null {
        constructor() {
            return Object.create(null);
        }
    }

generates error:

error TS2377: Constructors for derived classes must contain a 'super' call.

in this case, a call to super is guaranteed to fail.

Isn't it a valid ES6 in the sense that you can extend null?

Yes - the problem is the compiler is saying you need to call super, which will cause your code to crash. Does the spec need to account for this as well?

So it is not error when extending null but do not give an error from super when extending null ?

talk with @mhegazy  we will error when users use super but not vice versa

We also want to give an error in this case
class B extends null {}

because of the following, in section [14.5.14] (https://people.mozilla.org/~jorendorff/es6-draft.html#sec-runtime-semantics-classdefinitionevaluation)

If constructor is empty, then,

If ClassHeritageopt is present, then
Let constructor be the result of parsing the String "constructor(... args){ super (...args);}" using the syntactic grammar with the goal symbol MethodDefinition.

Can you check with @bterlson that this applies to the extends null case.

I don't think that is an error. It's very clear from the below semantics.

Else
5.  If superclass is null, then
2.  Let constructorParent be the intrinsic object %FunctionPrototype%.

Let constructorInfo be the result of performing DefineMethod for constructor with arguments proto and constructorParent as the optional functionPrototype argument.

Then in DefineMethod

Let closure be FunctionCreate(kind, StrictFormalParameters, FunctionBody, scope, strict). If functionPrototype was passed as a parameter then pass its value as the functionPrototype optional argument of FunctionCreate.

Then in FunctionCreate

Let F be FunctionAllocate(prototype, Strict, allocKind).

Then in FunctionAllocate

Set the [[Prototype]] internal slot of F to functionPrototype.

Then of course, you need to understand you the runtime semantics for super calls:

Let func be GetSuperConstructor().

And, GetSuperConstructor will

Let superConstructor be activeFunction.[[GetPrototypeOf]]().

And obviously, [[GetPrototypeOf]]() invoked on activeFunction (known generally as "O") will

Return the value of the [[Prototype]] internal slot of O.

God.

I see your point @DanielRosenwasser . However, the default constructor will call super. this will be an error except it is different  super we are talking about here.

I see what you mean now @yuit - maybe we should change our emit for super calls to be something like
// No constructor defined:
_super && _super(this, arguments);

// In the presence of an explicit 'super(arg1, arg2, ..., argN)' call
_super && _super.call(this, arg1, arg2, ... argN);

Note: following code fails at execution time in io.js
class N extends null {}
var n = new N();  ->  function Empty() {} is not a constructor

class A extends null { } will indeed get the default constructor that includes super. This is not an error because ClassDefinitionEvaluation sets the [[prototype]] of the constructor to Function.prototype, which itself is a function. In other words, Object.getPrototypeOf(A) === Function.prototype.
Super property references should fail at runtime in methods as the [[prototype]] of the home object (A.prototype) is null.

Super property references should fail at runtime in methods as the [[prototype]] of the home object (A.prototype) is null.

so calling super will cause an error? (i.e so calling new A() will give runtime error)

@bterlson, @yuit found the following:

<IP_ADDRESS> Runtime Semantics: Evaluation

SuperCall : super Arguments

Let newTarget be GetNewTarget().

If newTarget is undefined, throw a ReferenceError exception.
Let func be GetSuperConstructor().
[...]

<IP_ADDRESS> Runtime Semantics: GetSuperConstructor ( )

The abstract operation GetSuperConstructor performs the following steps:

Let envRec be GetThisEnvironment( ).

Assert: envRec is a function Environment Record.
Let activeFunction be envRec.[[FunctionObject]].
Let superConstructor be activeFunction.[[GetPrototypeOf]]().
ReturnIfAbrupt(superConstructor).
If IsConstructor(superConstructor) is false, throw a TypeError exception.
Return superConstructor.

19.2.3 Properties of the Function Prototype Object

The Function prototype object is the intrinsic object %FunctionPrototype%. The Function prototype object is itself a built-in function object. When invoked, it accepts any arguments and returns undefined. It does not have a [[Construct]] internal method so it is not a constructor.

So what it seems like is that activeFunction.[[GetPrototypeOf]](). in GetSuperConstructor() will return Function.prototype which itself is not constructible, meaning that this will indeed error. Any idea whether this is the case, or whether we're missing something?

I missed the isConstructor check! You're right that's what the spec says, but this is an error. Spec will be fixed. Intention is for this not to throw via not installing a default constructor with a super call in this case.

Well, maybe. See bug here: https://bugs.ecmascript.org/show_bug.cgi.

@bterlson can you fix that link?

So for TypeScript, it seems like there are two things to fix:

The error we give is actually wrong for extends null. In that case, the user should not have a super call. And also, the fact that we require a super call could be bad for extending an expression where the runtime value could be null.
We need to change our pre-ES6 emit for default constructors if you extend null. Again, this will not work for extending an arbitrary expression. The alternative here is to make a helper that actually checks the value of _super, and only calls it if it's not null. That might be better.

@JsonFreeman : you are right. I believe we will need to fix our emit default constructor for below es5 to be able to handle extends null

Gah, edited. Sorry.

I think SameValue(protoParent, null) is a better check, that way it doesn't change the behavior for extends Function.protoype. But maybe that will break extends { prototype: null }.

I open separate issue to track what our decision is for default constructor


Custom Notification and Footer Tabs BUG

I am use custom notification and footer tabs at same page(wether default page or not get same bug).
And then tab buttons have no response for change tab (but swipe work fine).
After debug with Chrome Inspect, I find out even notification was hide,
It still keep some height from bottom and cover on footer tabs.
After tried z-index to notification , nav , tab-items , tab-item
My final solution is
deviceReady{
    document.querySelector('#notification_id').style.height="0px";
}

document.querySelector('#notification_id').style.height="";
phonon.notif('#notification_id').show();

document.querySelector('#notification_id').style.height="0px";
phonon.notif('#notification_id').hide();

Dirty but it works fine.

Hi @ckhsu3926,
Thank you for opening this issue.
I can't reproduce your bug..
Is your custom notification outside your page wrapper?
Example:
...

...

    <home data-page="true">...</home>
    ...
</body

@Qathom thanks for reply.
In my case,
I've tried

...

    ...
    <home data-page="true">...</home>
    ...

    <home data-page="true">
        ...

...

    </home>
    ...

Both of these style make this issue.
Totally Strange haha.
"Maybe" I bind mapsplugin/cordova-plugin-googlemaps(Ver.2.0) at same page is the reason why this happen,
although I did recheck every px are not overlap each other,
but I haven't give a shot to set map unclickable and figure out is this the reason of this issue.


💡 [REQUEST] - adding hover effect in login button

[x] I am from GSSoC'23.
[x] I would like to be assigned this task.

Section
Description

Concise Description
I notice that the login button does not have any hover effect

Solution Proposed
adding hover effect similar to home, about us, and contact us page

Screenshots

Code of Conduct
By submitting this issue, you agree to follow our Code of Conduct.

[x] I follow the Contributing Guidelines of this project.
[x] I have checked the current issues for duplicate problems.
[x] I have read the readme of this repository.

Hey @Iamdivyak  you may work on this. All the best! Please mention the issue no while raising the pr.

@AKD-01
Check pr #334

@AKD-01
Check pr #321

@Iamdivyak I am interrupting in your pull request, I am just reminding @AKD-01 that merge my PR ✨


Update generic object property method normalization

Currently, when custom buttons are added to a generic object, they show up in property methods as an array. This is causing an ["invalid method name: [[\"button1\"]]"] error during property method name validation. By flattening the array, calling custom actions can proceed as normal.
I discovered this while working on custom action button calling in the API. It was returning them just fine, but causing problems when trying to call the custom action.
@miq-bot add_label bug, gaprindashvili/yes
@miq-bot assign @gmcculloug

@bzwei Is this true, do custom buttons belong in property methods?

@gmcculloug maybe something fishy is just going on.
@bzwei the failure is happening here: https://github.com/ManageIQ/manageiq/blob/master/app/models/resource_action.rb#L72
[1] pry(#<ResourceAction>)> target.try(:my_zone)
NoMethodError: undefined method `key?' for ["invalid method name: [[\"gobutton\"]]"]:Array
from /Users/jilliantullo/code/manageiq/app/models/generic_object_definition.rb:49:in `block (2 levels) in <class:GenericObjectDefinition>'

You can also see the failure in the specs for this PR: https://github.com/ManageIQ/manageiq-api/pull/194

@jntullo it makes no sense to me. Custom buttons should not appear in property methods.

Closing as it appears to be an API-specific issue. Was able to resolve it by calling reload on the object (see https://github.com/ManageIQ/manageiq-api/pull/194/files#diff-57ac4c07fba9a7071def6b2f73bd1134R35) . Still have not been able to figure out the root cause, though.


Change registry to dependency initializer

Rather than children polling for objects, objects are provided to the children by an overseer.
This PR is created for potential discussion of pros and cons, improvements, or alternate solutions (and/or to merge if we like it.)

What's the state of this PR?

I believe Razcore mentioned he'd revisit the states, but he hasn't mentioned anything about it. I'd be ready to work with it as-is, though, and I can't think of any other major change.

Razcore has informed me that the PR is ready. The only thing is separating the gun from the movement states, but that will be folded as a minor enhancement into milestone 3.

Thanks!


Start of a fix for #1154

Signed-off-by: Scott Kurz<EMAIL_ADDRESS>Fixes #1154.

There's a flaw with this fix... in dev mode we're going to ignore the looseApp=false config ..so we need to make sure we update that path to handle classifiers as well.
The flaw is only in the case in which you have explicit config in server.xml.. in which case it won't align with the LMP expectation which will generate its own.

I manually tested most of the following matrix:
Project packaging:  war, ear
liberty-maven-plugin stripVersion:  true, false
loose app:  true (dev mode override), false (liberty:run)
classifier set (on war, ear plugin config), vs. not set.
And it all passed


Fixed logic for delegate call for transfer, create, write_log

I'll add a hardfork as a separate commit here


Observing 500 internal error when notification received on API:/v1/regard-device-object-deletion

When Object delete notification is received on API:/v1/regard-device-object-deletion, observing error 500 in MWDI.
{"notification-proxy-1-0:object-deletion-notification":{"counter":8,"timestamp":"2024-01-29T08:25:23.0+00:00","object-path":"/core-model-1-4:network-control-domain=live/control-construct=513250009/forwarding-domain=VLAN-FD/fc=VLAN-3301"}}

Tested with Test_v1.1.2 , Issue is no longer observed .
For object delete notification observing 204 response.
{"notification-proxy-1-0:object-deletion-notification":{
"counter":6,
"timestamp":"2024-02-09T06:02:07.0+00:00",
"object-path":"/core-model-1-4:network-control-domain=live/control-construct=513250009/forwarding-domain=VLAN-FD/fc=VLAN-3301"
}
}

Same issue observing in tag:1.1.3, hence re-opened this issue.

Issue still observed with test_1.1.4
{"notification-proxy-1-0:object-deletion-notification":{"counter":1,"timestamp":"2024-03-18T06:44:16.0+00:00","object-path":"/core-model-1-4:network-control-domain=live/control-construct=513250009/forwarding-domain=VLAN-FD/fc=VLAN-3319"}}
2024-03-18T06:48:39.572573455Z [18.03.2024 06:48.39.572] [ERROR] TypeError: Cannot read properties of null (reading 'uuid')
2024-03-18T06:48:39.572606325Z     at /home/openbackhaul/microWaveDeviceInventory/service/individualServices/cacheUpdateBuilder.js:31:17
2024-03-18T06:48:39.572611435Z     at Array.findIndex ()
2024-03-18T06:48:39.572614825Z     at Object.exports.cacheUpdateBuilder (/home/openbackhaul/microWaveDeviceInventory/service/individualServices/cacheUpdateBuilder.js:30:52)
2024-03-18T06:48:39.572617815Z     at /home/openbackhaul/microWaveDeviceInventory/service/IndividualServicesService.js:9844:35
2024-03-18T06:48:39.572626275Z     at runMicrotasks ()
2024-03-18T06:48:39.572629205Z     at processTicksAndRejections (node:internal/process/task_queues:96:5)
2024-03-18T06:48:39.577491044Z POST /v1/regard-device-object-deletion 500 31.747 ms - 55
2024-03-18T06:48:39.651709293Z [18.03.2024 06:48.39.651] [LOG]
2024-03-18T06:48:39.651731773Z  callback : POST http://xxx:xxx/v1/record-service-request header :{"user":"User Name","originator":"MicroWaveDeviceInventory","x-correlator":"Eee34c6E-5768-0951-5864-6272A3fF8ef0","trace-indicator":1,"customer-journey":"unknown","operation-key":"Operation key not yet provided.","Content-Type":"application/json"}body :{"x-correlator":"550e8400-e29b-11d4-a716-446655440000","trace-indicator":"1.3.1","user":"User Name","originator":"Resolver","application-name":"MicroWaveDeviceInventory","release-number":"1.1.0","operation-name":"/v1/regard-device-object-deletion","response-code":500}response code:204
2024-03-18T06:49:51.870939436Z [18.03.2024 06:49.51.870] [LOG]

Still seeing this issue in 1.1.2.f_impl
logs:
[12.07.2024 08:45.36.658] [ERROR] NotFoundError: Field "fc"="VLAN-1004" not found in cache
at Object.exports.cacheUpdateBuilder (/home/openbackhaul/microWaveDeviceInventory/service/individualServices/cacheUpdateBuilder.js:53:17)
at /home/openbackhaul/microWaveDeviceInventory/service/IndividualServicesService.js:10373:35
at processTicksAndRejections (node:internal/process/task_queues:96:5)
POST /v1/regard-device-object-deletion 404 59.649 ms - 79
[12.07.2024 08:45.36.724] [LOG]
callback : POST http://<IP_ADDRESS>:3003/v1/record-service-request header :{"user":"NotificationProxy","originator":"MicroWaveDeviceInventory","x-correlator":"f0776C42-FEeb-0A3b-7ACe-51edaEF20CCa","trace-indicator":1,"customer-journey":"unknown","operation-key":"Operation key not yet provided.","Content-Type":"application/json"}body :{"x-correlator":"21B1bdaa-D69B-70f5-4C7f-2c01aF476fBd","trace-indicator":"1","user":"NotificationProxy","originator":"NotificationProxy","application-name":"MicroWaveDeviceInventory","release-number":"1.1.0","operation-name":"/v1/regard-device-object-deletion","response-code":404}response code:204

Tested with latest  MWDI version 1.1.2.g_impl, Issue is no longer observed.
Object Deletion:
http://XXXXX:XXXX/v1/regard-device-object-deletion

{"notification-proxy-1-0:object-deletion-notification":{"counter":1,"timestamp":"2024-10-14T07:17:22.0+00:00","object-path":"/core-model-1-4:network-control-domain=live/control-construct=513250009/forwarding-domain=VLAN-FD/fc=VLAN-3387"}}

Response : 204 OK


Revert lockfile after tests

This pull request introduces a new util function that is used in the first step of rugged to store a copy of the lockfile for a project before we do anything, and in the last step to restore it after all testing is completed.
Closes #71

Also, are you also reverting any changes to the node_modules/ directory? Because if the lockfile gets updated, just reverting the changes to that file won’t actually change what’s in the the node_modules/ directory.

Also, are you also reverting any changes to the node_modules/ directory? Because if the lockfile gets updated, just reverting the changes to that file won’t actually change what’s in the the node_modules/ directory.

I am running the install command after reverting the lockfile with the frozen lockfile flag, in npm's case I'm running npm ci, you can see that in action on the following and subsequent lines: https://github.com/sparksuite/rugged/pull/72/files#diff-a2a171449d862fe29692ce031981047d7ab755ae7f84c707aef80701b3ea0c80R90
I thought that seemed sufficient to be confident I was restoring the previous state of the node modules.

Also, are you also reverting any changes to the node_modules/ directory? Because if the lockfile gets updated, just reverting the changes to that file won’t actually change what’s in the the node_modules/ directory.

I am running the install command after reverting the lockfile with the frozen lockfile flag, in npm's case I'm running npm ci, you can see that in action on the following and subsequent lines: https://github.com/sparksuite/rugged/pull/72/files#diff-a2a171449d862fe29692ce031981047d7ab755ae7f84c707aef80701b3ea0c80R90
I thought that seemed sufficient to be confident I was restoring the previous state of the node modules.

I think that should be sufficient. Though you may want to do some tests to be sure. One way to test it would be to not ignore the node_modules/ directory and see if Rugged first introduces changes and then eliminates those.


How to get my self-written module included in the Standard features of https://caddyserver.com/download?

I've created a plugin that automatically trusted_proxies from AWS CloudFront EDGE servers:
https://github.com/xcaddyplugins/caddy-trusted-cloudfront
trusted_proxies cloudfront module for Caddy
The module auto trusted_proxies AWS CloudFront EDGE servers from https://d7uri8nf7uskq.cloudfront.net/tools/list-cloudfront-ips
Requirements

Go installed
xcaddy

Build
$ xcaddy build --with github.com/xcaddyplugins/caddy-trusted-cloudfront

Caddyfile Syntax
trusted_proxies cloudfront {
    interval <duration>
}

interval How often to fetch the latest IP list. format is caddy.Duration. For example 12h represents 12 hours, and "1d" represents one day. default value 1d.

Caddyfile Example
trusted_proxies cloudfront {
    interval 1d
}

You register/login on the website by clicking on Account. Once you're logged in, you'll find a Register Package button.


trying again

Since this is going to make the file large, consider updating the script tag in the html to include:
 from
 <script src="./assets/index.js"></script>

to
 <script type="module" src="./assets/index.js"></script>


Invalid TransmogrifAI license

Hello,
We have noticed that your project uses TransmogrifAI code but has invalid license on it (Apache 2.0).
TransmogrifAI is open sourced under BSD-3 license so please keep the original license header.
Thank you.

OK  i will fix this as soon as possible
On Friday, March 1, 2019, Matthew Tovbin<EMAIL_ADDRESS>wrote:

Hello,
We have noticed that your project uses TransmogrifAI code but has invalid
license on it
https://github.com/allwefantasy/streamingpro/blob/fe77b7ffa511928e17ad7c1f38d17d64a9823e23/contri/streamingpro-automl/src/main/java/com/salesforce/op/WowOpWorkflow.scala
(Apache 2.0).
TransmogrifAI is open sourced under BSD-3 license
https://github.com/salesforce/TransmogrifAI/blob/master/LICENSE so
please keep the original license header.
Thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/allwefantasy/streamingpro/issues/956, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAwsPivwAbnXLGFugG0rXK1sNzdi6Pbnks5vSC3WgaJpZM4bXkNW
.

@tovbinm  I have created a new PR  to fix this issue. Can you review it and check is there something I have missed?

Thanks. LGTM.


OSGi plugin causes unnecessary build cache misses

I'm having an issue I think similar to https://issues.gradle.org/browse/GRADLE-1227.
Incremental task execution seems to work properly, but the task caching does not work properly.

I have subprojects api and core
core depends on api
both have the osgi plugin applied

When I execute the build two times in a row, every actionable task is properly UP-TO-DATE.
But when I do clean build with build cache enabled, then only 9 of the 11 cacheable tasks are taken from cache.
core:test is reexecuted (and due to that or due to the same reason core:jacocoTestReport).
The reason is, that the api JAR has s different hash when calculating the cache key.
The only difference inside the api JARs is the Bnd-LastModified header in the manifest.
To validate it is the reason for the cache miss, I tried to exclude the header, but I also wasn't successfull in trying to do so.
I tried
jar { manifest { instruction '-removeheaders', 'Bnd-LastModified' } }

this did not remove the header but only moved it down to be the last one while before it was near the top.
I tried
jar { manifest { instruction 'Bnd-LastModified', '0' } }

this had no effect whats-o-ever.
I tried
jar { manifest { instruction '-noextraheaders', 'true' } }

this removed the Created-By header and the Tool header and moved the Bnd-LastModified header down to the bottom of the manifest again.
Is the inability to remove the Bnd-LastModified header a separate issue I should report separately, or is this expected?
Should Gradle for improvement of binary build reproducability always suppress this header like it made the WriteProperties task that does not output a timestamp to generated properties files?
To validate my assumption I then resorted back to not apply the osgi plugin and then the JARs were identical and the cache was used properly for all 11 cacheable tasks.
If you want to have an example at hand, you can use the v_3 branch of https://github.com/Javacord/Javacord where I struggle with this issue.

The caching issue is clearly caused by the Bnd-LastModified attribute being added. I tried to remove it in the past, but gave up after similar results. Are you sure the code that adds it is on the Gradle side?

Well, either Gradle or something Gradle uses like the bnd tool.
I found a post on the bnd list by Luke from 2012 or so where he asked whether you can remove that attribute safely to get binary reproducible builds.
He didn't mention Gradle explicitly, but sounded like he talks about Gradle.
It was also at some point "fixed" that incremental build is ignoring that property as you can see in the linked issue.
Also if you Google for it, you find the recommendation to use the -removeheaders instruction to remove the header which seemed to partly work as it was not where the bnd tool usually had put it, but in the end of the attributes list, just as when I used the -noextraheaders instruction which made the other bnd-specific headers vanish and have the last modified header in the end again and the Bnd-LastModified instruction which should set it to a fixed value (you even do this in one of your tests) had no effect at all.

The OSGi plugin has been deprecated and will be removed in 6.0: #9433
Does the external plugin already solve your issues?

I don't know, I didn't use the external plugin in that project yet.
But as you said, as the bundled osgi plugin is deprecated, let's just close this issue here.


Jsoup new version,emptyTag : img overTag is not append! But i need append with

String htmlstr = "";
Document document = Jsoup.parse(htmlstr);
String html = document.body().html();
System.out.println(html);
// resutl :
//notice :  is missing, but i hope it end with !!! so what can i do it?

HTML doesn’t need close tags for img tags or other self closing tags. I would suggest reviewing why you. We’d it. You can use the XML output syntax if you want to output xml.


Add support for service instance sharing

A new feature allowing service instances to be shared across orgs and spaces was released in cf-deployment version 1.10.0. This doc explains the very simple step required to enable this feature for your service (adding a shareable field to your service-level metadata in the catalog). Have you thought about enabling this for your service?

@jenspinney : We will check this option and get back to you .


Fix the Handcoach/rigged hand model to handle pinch animations correctly

Currently the rigged hand meshes we use for visualization have issues matching the user's animations. Though the hand looks fine when doing pointing motions, the fingers do not close completely when doing pinching motions.

This issue is mostly here to track the work for fixing up the model/getting a new one working.

Leaving comment to keep track


EXT_meshopt_compression broke a lot of gltf files

@daemyung it looks like the support for EXT_meshopt_compression broke all gltf exported from sketchfab.
e.g. that's "ship in a bottle"

it should look like this:

Not sure if I can attach the models here. But it seems to me you can take any model from sketchfab and export as gltf and you'll have this issue.

@pixelflinger Thanks I will also look into this issue.


saving the notebook file replaces the content of notebook with the last cells content

now this is weird also dangerous lol, good thing i had my notebooks in a git repo
config: require("nvim-jupyter-client").setup({})
this is with all my plugins disabled so definitively the plugin is causing it
https://github.com/user-attachments/assets/f6db5fb8-ab6a-4e5f-84ad-5033d9bc5c56

I see, it's a bug in the markdown rendering. Let me take a look. What it is meant to do is enclose markdown in triple quotes when rendering then removing them for saving.


Fix misspell of type of Pod condition at init container explanation (fr)

In explanation of init container, doc says 'Initializing' pod condition. However according to doc of pod condition, it should be 'Initialized'.
This commit fixes this misspell of French doc.
This misspell is verified by PR #17329 which fixes English doc.

/lgtm
/approve


Homepage, Suggested feature: search box

Likely worth waiting for #10, contribute upstream
Suggested feature: Add a search box to the homepage to match old OpenDataPhilly site. On submit, forward to Datasets page and populate search there.

Suggested design:


[Port] fix load publish profile not working (#17851)

Fixes https://github.com/microsoft/azuredatastudio/issues/17850

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.001%) to 41.695%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/sql-database-projects/src/dialogs/publishDatabaseDialog.ts
0
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.001%

Covered Lines:
27272

Relevant Lines:
59355

💛  - Coveralls


FaceMesh is not detected properly when device is in landscape or portrait upside-down.

System information (Please provide as much relevant information as possible)

Have I written custom code (as opposed to using a stock example script provided in Mediapipe): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04, Android 11, iOS 14.4): Android
MediaPipe version: 8.10.0
Bazel version:
Solution (e.g. FaceMesh, Pose, Holistic): FaceMesh
Programming Language and version ( e.g. C++, Python, Java): Java

Describe the expected behavior:
I am developing a camera app using Mediapipe FaceMesh solution and saw that facemesh is not properly detected when the device is in landscape or portrait upside-down.
So I tried Android FaceMesh example app you provide, and checked that face mesh is not detected properly.

Works perfectly in portrait, but:

When in landscape or upside down, face mesh is also kinda upside down.
Is there any way we can resolve this problem?
Thank you in advance :)

Hi @carat-hansol, Have you looked at similar closed issue #3028  and comment. Thank you!


New version: pnpm.pnpm version 9.5.0

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: Open in CodeFlow

/azp run


Sources of invalidations

I was analyzing sources of invalidations (maybe you are already familiar with it, but some context can be found here and here) and it seems that one of the most important is caused by this definition:
Int(::Infinity) = ∞

which is understandable given how it breaks a lot of the assumptions from inference in Base, where Int(n) isa Int, but now it can also be ::Infinity.
I can see how eliminating that line would make supporting the whole array interface really cumbersome, but maybe it is worth trying to see if it can be restructured to improve precompilation and loading times.

Really I should do a PR into Base to make this hack unnecessary: I don't remember the offending code but there really isn't a good reason to convert to Int in the first place

All of our indexing is done with Int, so there's a pretty strong argument that size should return an Int.

It doesn't for BigInt(1):10 so that would be a breaking change to require that


Relations are now bidirectional, unlike at parse.com

Environment Setup
I'm running Node 4.3, Mongo 3.0.9 in DigitalOcean
Steps to reproduce
If a user has a like relation of type User and user A likes user B and you query user B's like relation for user A it returns true, which it's supposed to return false, since user B hasn't liked user A.
This is the way relations worked for my app in parse.com. Am I doing something wrong?
Logs/Trace

That would help to have more informations about that problem a test case, example etc...

I've added a test that checks for this in #1283, which passes. If you are doing something differently in your code and is not behaving how you expect, please open a new issue and include your code that is failing.


Add good first issue project board workflow to repository

This pr adds the project board workflow from the Vapor repository to this repository

Codecov Report

Merging #112 (da53ab1) into main (93c169e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #112   +/-   ##
=======================================
  Coverage   84.17%   84.17%
=======================================
  Files           4        4
  Lines         278      278
=======================================
  Hits          234      234
  Misses         44       44

Flag
Coverage Δ

unittests
84.17% <ø> (ø)

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


Fix loading named styles

Style files is loaded, but no settings are changed.

I approve this

https://www.artofunittesting.com/definition-of-a-unit-test
A good unit test is:

Able to be fully automated
Has full control over all the pieces running (Use mocks or stubs to achieve this isolation when needed)
Can be run in any order  if part of many other tests
Runs in memory (no DB or File access, for example)
Consistently returns the same result (You always run the same test, so no random numbers, for example. save those for integration or range tests)
Runs fast
Tests a single logical concept in the system
Readable
Maintainable
Trustworthy (when you see its result, you don’t need to debug the code just to be sure)

Not sure we score 100% on this checklist, but setting options is modifying global state and needs to be reset before we can run another test.

@daniel-caichac-DHI If you check that this PR is what you need, then I will publish a new alpha version on modelskill to PyPI.


Callback on timeout

Could you add a feature to allow for a callback function to be passed into the set() method, and this callback would be fired when the ttl is reached?
Thanks
Justin

yes that is possible, we could allow callbacks to be optional. we will try to include this in our next minor release.


Make aggregation time zone configurable

Description:
The incremental aggregations happen in GMT time zone. Making it configurable to user preferred time zone will enhance usefulness
Affected Siddhi Version:
all on or before 5.1.12

Fixed in https://github.com/siddhi-io/siddhi/pull/1637


DateTime logged as 'null' in Doctrine query log

It seems that a DateTime in the query is logged as null. Is this expected behaviour?
Log:
WHERE t0.requested_date = ?   AND ((t0.deleted_at IS NULL)) --> 'query params': [null]
I would expect something like:
WHERE t0.requested_date = ?   AND ((t0.deleted_at IS NULL)) --> 'query params': [2016-07-24 07:55:56]
![screen shot 2016-08-26 at 08 48 27]
(https://cloud.githubusercontent.com/assets/3961971/17996554/f2b1f63e-6b69-11e6-9530-b00ef2b44c43.png)

This is certainly strange. We transform variables into strings using Yaml::dump() so the datetime should be dumped as expected.

Well I tried the following:
EaseLogFormatter:
dump($record);  $contextAsString = Yaml::dump($context, $this->getInlineLevel($record), $this->prefixLength);  die(dump($contextAsString));
Outcome:
array:7 [   "message" => "SELECT COUNT(a0_.id) AS sclr_0 FROM apps_absence a0_ WHERE (a0_.user_id = ? AND a0_.is_bookable = ? AND a0_.requested_date = ?) AND (a0_.deleted_at IS NULL)"   "context" => array:1 [     "query params" => array:3 [       0 => 2       1 => false       2 => DateTime {#1015         +"date": "2016-07-24 00:00:00"         +"timezone_type": 3         +"timezone": "UTC"       }     ]   ]   "level" => 100   "level_name" => "DEBUG"   "channel" => "doctrine"   "datetime" => DateTime {#1027     +"date": "2016-08-24 08:29:37"     +"timezone_type": 3     +"timezone": "UTC"   }   "extra" => [] ] "'query params': [2, false, null]\n"

I've just tested in a Symfony app and the DateTime object seems to be dumped as expected, including the timezone:
___ DOCTRINE ___________________________________________________________________________________
SELECT DISTINCT ... WHERE ... GROUP BY ... ASC LIMIT 10 OFFSET 0
--> 'query params': [true, 2016-08-26T07:10:45+02:00]
___ DOCTRINE ___________________________________________________________________________________
SELECT ... WHERE ... ORDER BY ... DESC
--> 'query params': [true, 2016-08-26T07:10:45+02:00, [40, 39, 38, 37, 36, 35, 34, 33, 32, 31]]

If you need any more information (php version, bundle version, etc...) to investigate this ticket please let me know.

Dunno if this is relevant, but the a0_.requested_date field is a DATE field, not a DATETIME field.

If it can further help you: it returns null in the
Symfony\Component\Yaml\Inline

case is_object($value):
                if ($objectSupport) {
                    return '!php/object:'.serialize($value);
                }

                if ($exceptionOnInvalidType) {
                    throw new DumpException('Object support when dumping a YAML file has been disabled.');
                }

                return 'null';

Is there an update about this issue?

@NoScopie it should be fixed by #6. Could you please test it? Thanks!

@javiereguiluz Jep this seems to fix it. Thanks!
___ DOCTRINE ___________________________________________________________________
SELECT COUNT(a0_.id) AS sclr_0 FROM apps_absence a0_ WHERE (a0_.user_id = ? AND a0_.requested_date
  = ?) AND (a0_.deleted_at IS NULL)
--> 'query params': [4, '2017-06-03T00:00:00+00:00']


Installation instructions fix

Fixes composer reference as mentioned in issue #20 , fixes read me heading markup and removes duplicate installation instructions.

Thanks!


Large integers fail to parse

module ReproLargeInt where

thresholdIntWorks :: Int
thresholdIntWorks =<PHONE_NUMBER>

-- thresholdIntFails :: Int
-- thresholdIntFails =<PHONE_NUMBER>

-- ourLargeIntFails :: Int
-- ourLargeIntFails =<PHONE_NUMBER>740991

ourLargeFloatWorks :: Number
ourLargeFloatWorks =<PHONE_NUMBER>740991.0

These will fail with the compiler as well:
 Error 1 of 1

  Integer value<PHONE_NUMBER> is out of range for the JavaScript backend.
  Acceptable values fall within the range -2147483648 to<PHONE_NUMBER> (inclusive).

Int is a 32bit integer in PureScript, so you can't write literals larger than that.

These will fail with the compiler as well:
 Error 1 of 1

  Integer value<PHONE_NUMBER> is out of range for the JavaScript backend.
  Acceptable values fall within the range -2147483648 to<PHONE_NUMBER> (inclusive).

Int is a 32bit integer in PureScript, so you can't write literals larger than that.

Not in Erlang world

Sorry - should have said that code is from a Purerl project, so we have the luxury of supporting arbitrary sized integers...  The same happens with and without the type declaration.  Maybe it should read
thresholdIntFails :: MyErlangInt
thresholdIntFails =<PHONE_NUMBER>

but you get the idea :). As Rob suggested, any questions of that nature to Nick!
And as in my post in Discord, huge huge thanks to all involved - the tool is wonderful and had almost no issues with 50k lines of our code.

Not in Erlang world*

Right, if we wanted to support this we'd have to parameterize purescript-language-cst-parser, to allow larger(unbounded) literals.
I've checked and the Haskell CST implementation uses Haskell's Integer which is also unbounded.
I think it would be reasonable to support this in the PureScript implementation as well, though it'll be a little bit of a pain because JS BigInt's are less widely available than one might like.


Unexpected token 'export' for >v3

Hi, I tried to understand for a very long time, but I ran out of ideas. After updating to version 3, tests began to fall with this error, in the place where I call the Api class. The project includes a dependency that was generated using swagger-typescript-api, everything was fine on version 2. Any idea why this is happening? Thanks
Test suite failed to run

    Jest encountered an unexpected token

    This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.

    By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/en/ecmascript-modules for how to enable it.
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/en/configuration.html

    Details:

    /Users/r/project/specifications/lib/index.js:16
    export class HttpClient {
    ^^^^^^

    SyntaxError: Unexpected token 'export'

Hello @navyfox!
What version of TypeScript do you have on your machine?

Hello @navyfox!
What version of TypeScript do you have on your machine?

"typescript": "^4.1.3"
I updated all the dependencies, found only the relationship between version 2 and version 3

"typescript": "^4.1.3"
I updated all the dependencies, found only the relationship between version 2 and version 3

@navyfox can you share code\script how do you call swagger-typescript-api ?
Mmm, is it error returned from test scripts? (jest?)

@navyfox can you share code\script how do you call swagger-typescript-api ?
Mmm, is it error returned from test scripts? (jest?)

Yes for some reason only in tests(jest)

Yes for some reason only in tests(jest)

It can be happend because of jest runs all tests in NodeJS environment, do you attach some plugins (typescript for jest) to jest?

It can be happend because of jest runs all tests in NodeJS environment, do you attach some plugins (typescript for jest) to jest?

jest.config.json
{
  "name": "front",

  "collectCoverageFrom": [
    "**/*.{ts,vue}",

    "!**/node_modules/**",
    "!**/jest/**",
    "!**/coverage/**",
    "!**/mock/**",
    "!**/nuxt.config.ts",
    "!**/*.stories.ts",
    "!**/*.d.ts"
  ],

  "globals": {
    "vue-jest": {
      "hideStyleWarn": true
    }
  },

  "moduleFileExtensions": [
    "js",
    "json",
    "ts",
    "vue"
  ],

  "moduleNameMapper": {
    "~/(.*)": "<rootDir>/src/$1",
    "@/(.*)": "<rootDir>/src/$1"
  },

  "preset": "ts-jest",
  "testMatch": ["<rootDir>/**/*.test.ts"],

  "transform": {
    "^.+\\.svg$": "<rootDir>/test/transform/svg.js",
    "^.+\\.ts$": "babel-jest",
    ".*\\.(vue)$": "vue-jest"
  },

  "setupFiles": [
    "<rootDir>/test/jest.setup.ts"
  ],

  "verbose": true
}

.babelrc
{
  "plugins": [
    [
      "@babel/plugin-proposal-decorators",
      {
        "legacy": true
      }
    ],
    [
      "@babel/plugin-proposal-class-properties",
      {
        "loose": true
      }
    ],
    [
      "@babel/plugin-transform-runtime",
      {
        "regenerator": true
      }
    ]
  ],
  "presets": [
    "@babel/preset-env",
    "@babel/preset-typescript"
  ]
}

tsconfig.json
{
  "compilerOptions": {
    "allowJs": true,
    "baseUrl": ".",

    "esModuleInterop": true,
    "experimentalDecorators": true,

    "lib": [
      "esnext",
      "esnext.asynciterable",
      "dom"
    ],

    "module": "esnext",
    "moduleResolution": "node",

    "paths": {
      "~/*": [
        "src/*"
      ],

      "@/*": [
        "src/*"
      ]
    },

    "strict": true,
    "sourceMap": true,

    "target": "es2019",
    "types": [
      "@nuxt/types",
      "@nuxtjs/device",
      "@types/jest",
      "@types/node"
    ]
  },

  "include": [
    "src",
    "test"
  ],

  "exclude": [
    "node_modules",
    "**/*.js"
  ]
}

jest.config.json
{
  "name": "front",

  "collectCoverageFrom": [
    "**/*.{ts,vue}",

    "!**/node_modules/**",
    "!**/jest/**",
    "!**/coverage/**",
    "!**/mock/**",
    "!**/nuxt.config.ts",
    "!**/*.stories.ts",
    "!**/*.d.ts"
  ],

  "globals": {
    "vue-jest": {
      "hideStyleWarn": true
    }
  },

  "moduleFileExtensions": [
    "js",
    "json",
    "ts",
    "vue"
  ],

  "moduleNameMapper": {
    "~/(.*)": "<rootDir>/src/$1",
    "@/(.*)": "<rootDir>/src/$1"
  },

  "preset": "ts-jest",
  "testMatch": ["<rootDir>/**/*.test.ts"],

  "transform": {
    "^.+\\.svg$": "<rootDir>/test/transform/svg.js",
    "^.+\\.ts$": "babel-jest",
    ".*\\.(vue)$": "vue-jest"
  },

  "setupFiles": [
    "<rootDir>/test/jest.setup.ts"
  ],

  "verbose": true
}

.babelrc
{
  "plugins": [
    [
      "@babel/plugin-proposal-decorators",
      {
        "legacy": true
      }
    ],
    [
      "@babel/plugin-proposal-class-properties",
      {
        "loose": true
      }
    ],
    [
      "@babel/plugin-transform-runtime",
      {
        "regenerator": true
      }
    ]
  ],
  "presets": [
    "@babel/preset-env",
    "@babel/preset-typescript"
  ]
}

tsconfig.json
{
  "compilerOptions": {
    "allowJs": true,
    "baseUrl": ".",

    "esModuleInterop": true,
    "experimentalDecorators": true,

    "lib": [
      "esnext",
      "esnext.asynciterable",
      "dom"
    ],

    "module": "esnext",
    "moduleResolution": "node",

    "paths": {
      "~/*": [
        "src/*"
      ],

      "@/*": [
        "src/*"
      ]
    },

    "strict": true,
    "sourceMap": true,

    "target": "es2019",
    "types": [
      "@nuxt/types",
      "@nuxtjs/device",
      "@types/jest",
      "@types/node"
    ]
  },

  "include": [
    "src",
    "test"
  ],

  "exclude": [
    "node_modules",
    "**/*.js"
  ]
}

It is problem based on jest I think
swagger-typescript-api generates TS file and TypeScript support EcmaScript2015 features like export keyword
I see that you use babel-jest transform for *.ts scripts
 "transform": {
    "^.+\\.svg$": "<rootDir>/test/transform/svg.js",
    "^.+\\.ts$": "babel-jest", //here
    ".*\\.(vue)$": "vue-jest"
  },

Did you try to change it to ts-jest  ?

It is problem based on jest I think
swagger-typescript-api generates TS file and TypeScript support EcmaScript2015 features like export keyword
I see that you use babel-jest transform for *.ts scripts
 "transform": {
    "^.+\\.svg$": "<rootDir>/test/transform/svg.js",
    "^.+\\.ts$": "babel-jest", //here
    ".*\\.(vue)$": "vue-jest"
  },

Did you try to change it to ts-jest  ?

Maybe not only based on jest
With using<EMAIL_ADDRESS>you said that everything was fine?
That's interesting because in v2 already has keyword export
https://github.com/acacode/swagger-typescript-api/blob/93295596487bf23b95b179cebe038b7628ac8cbe/tests/generated/v3.0/personal-api-example.ts#L258

Maybe not only based on jest
With using<EMAIL_ADDRESS>you said that everything was fine?
That's interesting because in v2 already has keyword export
https://github.com/acacode/swagger-typescript-api/blob/93295596487bf23b95b179cebe038b7628ac8cbe/tests/generated/v3.0/personal-api-example.ts#L258

ts-jest Yes, I tried three days ago, the error line changes, but everything is the same. With the second version, everything works great)

ts-jest Yes, I tried three days ago, the error line changes, but everything is the same. With the second version, everything works great)

Sorry, really, from 1.8 to 2

Sorry, really, from 1.8 to 2

@js2me Thanks for the help. You pushed me in the right way.
jest.config.json
"transform": {
    "^.+\\.svg$": "<rootDir>/test/transform/svg.js",
    "^.+\\.ts$": "babel-jest",
    "\\.js$": "ts-jest",
    ".*\\.(vue)$": "vue-jest"
  },
"transformIgnorePatterns": [
    "node_modules/(?!@myApi)"
  ],

these lines are needed
"\\.js$": "ts-jest",
"transformIgnorePatterns": [
    "node_modules/(?!@myApi)"
  ],

@js2me Thanks for the help.


Export review comments as part of the PDF

We have the suggestion from a client "to save one Pdf version with comments still there"
This probably should include comments in an annotation style display as in Word/GDoc.
This would require versioning of plans first, potentially also a way to version comments and a complete rework of the PDF exporter.
Comments could be exposed via the API - will need to check with the wider community if that would be desired.

It wouldn't necessarily even be in a pdf format or for every user-type. I would at least like it to be available for admins. Right now there is no trace-back possible what kind of comments and recommendations were made. When a researcher has described practices in a DMP that are not the best practices or are just not allowed, we currently have to specify those comments again in an email so that we have traceability of our advice (seems double the work). If at some point research gets into 'trouble' for adhering to bad practices and say that nobody ever advised them otherwise, it becomes a difficult matter to determine where it went wrong. Of course our starting point is all based on mutual trust, but in case of an audit within the university (especially with sensitive data), it would be good to have trace-back. Concerning FAIR data, it would be good to have the DMP be traceable and verifiable as well.


ViewModel init call

Hi, I get your sample code for ViewModel
class BackpackViewModel : ViewModel() {
    val backpack: Backpack by inject()
}

and add an initialization block like here
class BackpackViewModel : ViewModel() {
    val backpack: Backpack by inject()
    init {
        backpack.doSomething()
    }
}

But I got this exception
java.lang.IllegalStateException: The dependency has not be injected yet.
If i call backpack.doSomething() after init call everything is working.
How I fix it?

The injection is done in the activity. So, when the vm init happened, the injection by the activity is not yet done.
Either 1/ you have to inject dependencies in the vm init before using the dependency, either 2/ request the action from the activity, when it is ready.
I prefer the 1/, and even from a general purpose, I prefer handing domain work from vm w/o dependency from view, to respect separation of concern !

@afaucogney is right (thx for the answer!), creation happens before injection. The process is divided into 2 steps:

When you use installViewModelBinding on your scope, we create the viewmodel using the right APIs under the hood.
When you start the injection, for example calling KTP...inject() inside your activity, it's when we inject the dependencies of the viewmodel.

The issue is that you are trying to access to those dependencies on the first step, when they are not ready yet. This is similar to when you wanna access injected fields inside a constructor. If you are curious, I could explain more about the reasons why we designed it that way.
Nevertheless, there is a way to solve it: using a ViewModel Factory to create the viewmodel using Toothpick.
val scope = KTP.openScopes(xxx)
scope.installViewModelBinding<MyViewModel>(activity, InjectedViewModelProvider(scope))
...

// This provider can be reused for any ViewModel
class InjectedViewModelProvider(private val scope: Scope) : ViewModelProvider.Factory {
    override fun <T : ViewModel?> create(modelClass: Class<T>): T {
        return scope.getInstance(modelClass)
    }
}

class BackpackViewModel(private val backpack: Backpack) : ViewModel() {
    init {
        backpack.doSomething()
    }
}

By doing so, you can use constructor and field injection within your viewmodel.
Same, if you are curious, I can provide more info about why we don't provide that functionality out-of-the-box.

@mrgaric If it works for you, plz feel free to close the issue.

thx for the answer. Yes, I am interested, why don't you provide this functionality out of the box?

So, we provide 2 ways of binding view models to your scope: with and without factory. If we use that constructor injection factory by default for the cases when you don't provide one (as you cannot have 2), then the behavior would not be consistent:

If you dont provide a factory for your viewmodel, we use our own and we perform constructor injection as well.
If you provide a factory for your viewmodel, we cannot use our own, so we do not perform constructor injection.

As I said, we considered that it would be inconsistent and in order to understand it, you would need to go deep on how TP does VM injection.
Maybe we should provide the Factory within TP anyway so people can use it if they want to? Or at least provide the example on the WIKI? What do you think?

I think an example will be enough. thx.


Unmount hook

The function returned by 'effect' callback should be called when component unmounted, as in builtin useEffect hook

I think this is an interesting idea. Would you mind opening a PR that adds this?


Cleanup

Cleans up directories, files and more. Thanks!
Changes

Use standard in favor of custom rules.
Move files into directories to clear room in root.

1.4.1


Update first-steps.md

According to RFC 9110, the current HTTP specification says:
"The POST method requests that the target resource process the representation enclosed in the request according to the resource's own specific semantics."
... and:
"The PUT method requests that the state of the target resource be created or replaced with the state defined by the representation enclosed in the request message content."
So, the tutorial is patently incorrect about PUT (updating has never been it's function, as far as I remember), and, I think, it unnecessarily over-simplifies POST.
This patch increases the accuracy of the doc, while only trivially increasing the complexity.
If this patch is controversial, I suggest simply removing PUT from this tutorial, since the new definition of POST makes PUT unnecessary for very many web applications. (Which have been using POSt and ignoring PUT for many years before the new standard anyway...)

📝 Docs preview for commit 10b84710cbeabe57b64caa87a0abb0aa1747f59a at: https://dce198f3.fastapitiangolo.pages.dev

I completely agree that the current statement simplifies what POST or PUT are.
But we need to remember it is the First Steps doc.  What we normally see in tutorials for beginners is precisely this simplification to make it easier to understand the basic operations of a CRUD when we are building an API.
So following this thought, we cannot say that the document is wrong.
But what was added didn't complicate the concept much.

I would argue that it is worse to give a beginner false information, and the doc's current definition of PUT is patently false, with respect to the RFC. If the language in this patch isn't sufficiently simple for the expected reader, then please just remove the reference to PUT. A beginner who needs more than POST can then look up better guidance elsewhere.

Yep, as @ceb10n says, this is introductory content, I don't intend to copy the RFC as is, just to give "good enough" guidelines for newcomers.
That's also why I say "Normally you use", instead of "As per the spec" or something similar.
Under my point of view, the docs are fine as they are, and are a "good enough" tradeoff for the objective I have for them, so I'll pass on this one, but thanks for the interest. :coffee:


Reorganize amplitude building functions and make public

For the documentation (but arguably also for the design), it would be more transparent to build the amplitude model through functions. In particular, the _generate_partial_decay methods can be reformulated so that they just produce a product of terms that are relevant to the helicity kinematics only (no dynamics).
This issue was motivated by https://github.com/ComPWA/qrules/pull/57, where it would have been nice to explain how the InteractionProperties are used to create Clebsch-Gordan coefficients in the canonical basis by pointing to the functions responsible for this in AmpForm:
https://github.com/ComPWA/ampform/blob/cdec30b9fa759cc4b418c693d4928d545d460a58/src/ampform/helicity.py#L584-L589
https://github.com/ComPWA/ampform/blob/cdec30b9fa759cc4b418c693d4928d545d460a58/src/ampform/helicity.py#L671-L673

We may also have to write some tests for the Clebsch-Gordan coefficients. These arguments j1 through to m3 are rather error-prone:
https://github.com/ComPWA/ampform/blob/cdec30b9fa759cc4b418c693d4928d545d460a58/src/ampform/helicity.py#L707-L723

Largely addressed through #87, which introduced formulate_clebsch_gordan_coefficients() and formulate_wigner_d(). With #245, however, the HelicityAmplitudeBuilder has again acquired a lot of implementation methods that are note well documented.


Fix exceptions/failures showing up as multiple log lines in Datadog

This should be a setting in structlog or at least easily handleable

@RobertKeyser do you have an easy way to test this? This'll take a bit of tinkering so I'm trying to figure out the best way for me to tackle it

https://ethyca.atlassian.net/browse/PROD-1224


Add overlay handling to base component (#24571)

Manual cherrypick of https://github.com/istio/istio/pull/24571.

Add overlay handling to base component

Refresh goldens

Update go.sum

@ostromart: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio_release-1.6
1782681ba145cc79a588355af7e720489790560f
link
/test gencheck_istio_release-1.6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ostromart: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio_release-1.6
1782681ba145cc79a588355af7e720489790560f
link
/test gencheck_istio_release-1.6

unit-tests_istio_release-1.6
1782681ba145cc79a588355af7e720489790560f
link
/test unit-tests_istio_release-1.6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@ostromart: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.6
1782681ba145cc79a588355af7e720489790560f
link
/test unit-tests_istio_release-1.6

gencheck_istio_release-1.6
1782681ba145cc79a588355af7e720489790560f
link
/test gencheck_istio_release-1.6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ostromart: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio_release-1.6
1782681ba145cc79a588355af7e720489790560f
link
/test gencheck_istio_release-1.6

unit-tests_istio_release-1.6
1782681ba145cc79a588355af7e720489790560f
link
/test unit-tests_istio_release-1.6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@ostromart: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.6
1782681ba145cc79a588355af7e720489790560f
link
/test unit-tests_istio_release-1.6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@ostromart: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio_release-1.6
1782681ba145cc79a588355af7e720489790560f
link
/test integ-distroless-k8s-tests_istio_release-1.6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Like Stagnant Doki

What feature do you want to get added on the base engine?
Add extra stages like in the json, there is a pixel stage section, I thought is there a way I can add a happy stage section
To test your sight, and reliability, please select the option of what should NOT be requested.
Stage Editor, 6K+ support, and winning icons.

You can already do this

Wait, how?!

With lua

Make both stages in one script, keep one invisible until the switch is supposed to happen
It works exactly like it does on source

Can it go from normal to pixel by this script:
function onCreate()
function onStepHit()
if curStep == number of steps
“isPixelStage”: true
end
end
end

Is there a script for that if it is wrong

Pls, tell me if there is a script, I might need it soon

https://github.com/ShadowMario/FNF-PsychEngine/wiki/Lua-Script-API:-Value-Setting-and-Getting-Functions#general-setters

I still don’t get it

Can you give me an example for changing ui

Example, pls

Is it like setProperty(‘isPixelStage’, true)

you can change isPixelStage on the json file of the stage

In middle of song


Copied files on Linux don't preserve permissions

I have some shell scripts I want to distribute along with my app (I run the NW.js app through a shell script to pass certain command-line flags that it is too late to do inside the app). When I build the app with nwjs-builder-phoenix, the shell scripts no longer have the executable flag when copied into the dist directory. File permissions should be preserved.

Will look into it.

@evshiron
Issue happens on macOS as well.
I have a secondary app (built with Swift using Xcode) and I package it inside my nw.js app.
The secondary app will not launch (after using nwjs-builder-phoenix) because permissions are not preserved.
After using nwjs-builder-phoenix I have to run the command:
chmod +x SecondaryApp.app/Contents/MacOS/* and everything will be fine.


task-provider-sample: how to read custom task attribute value?

According to the task-provider guide:

The task definition has two attributes task and file. task is the name of the Rake task and file points to the Rakefile that contains the task. The task property is required, the file property is optional. If the file attribute is omitted, the Rakefile in the root of the workspace folder is used.

It does not seem the file attribute value from tasks.json is actually being used in extension.ts code.
How do I read custom task attribute values defined in tasks.json?
Where/how are they available?
Do I need to parse tasks.json file?

task and file are defined for VS Code in the package.json of the extension and are used for identifying a task. They are not for modifying a task, they are instead provided by the the extension.
If you want to pass stuff from tasks.json into an extension, that's this issue: https://github.com/microsoft/vscode/issues/58836


Added Temperature convertor GUI python script

Description-Added Temperature convertor GUI python script
Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.
Fixes #2046

Type of change-Added Temperature convertor GUI python script
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[X] This change requires a documentation update
[X] Documentation Update

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[x] My documentation follows Template for README.md
[x] I have added the project meta data in the PR template.
[x] I have created the requirements.txt file if needed.

Project Metadata
If there is no-file/nothing to fill the below fields with, then type: none
Example: If no requirements.txt needed/present, then type none in Requirments.
Category:

[ ] Calculators
[x] AI/ML
[x] Scrappers
[ ] Social_Media
[ ] PDF
[ ] Image_Processing
[ ] Video_Processing
[ ] Games
[ ] Networking
[ ] OS_Utilities
[x] Automation
[ ] Cryptography
[ ] Computer_Vision
[ ] Fun
[x] Others

Title: <write script title here>
Folder: <type the folder name that contains your script>
Requirements: <type the name of text file containing the required to install python packages, type None if no file required>
Script: <Enter the name of the .py file (The main entry point of the program)>
Arguments: <enter any arguments that the script needs but - separeted like: h-c-m>
Contributor: <Enter your Github handle/username without url>
Description: <Enter a one line description that describes your script. Also, explain the arguments usage here>

Convert this into python Script and add a README file
readme.md

@avinashkranjan I have Converted this into python Script and added a README file also

@avinashkranjan  I have Converted this into python Script and added a README file also.
Done the task

@avinashkranjan I have done requested changes


_posts/0000-01-02-cbenakis.md

layout: slide
title: “Welcome to our second slide!”
Your test
Use the left arrow to go back!

How do I merge pull request?


font weight not being applied using dripsy's

hey! using dripsy with solito - I've followed the guide in the docs to get custom fonts setup, and it's (mostly) working really nicely. I've got one instance where it's not working though, and I can't work out why...
in my theme file I've got:
const rootFontName = 'Work Sans'
const headingFontName = 'TT Norms Pro'

export const Fonts = ({ children }: { children: React.ReactNode }) => {
  const [loaded] = useFonts({
    [rootFontName]: require('../../../apps/next/public/fonts/WorkSans-Regular.ttf'),
    ['Work Sans Medium']: require('../../../apps/next/public/fonts/WorkSans-Medium.ttf'),
    ['Work Sans SemiBold']: require('../../../apps/next/public/fonts/WorkSans-SemiBold.ttf'),
    [headingFontName]: require('../../../apps/next/public/fonts/TT-Norms-Pro-Bold.ttf'),
  })
  if (!loaded) return null
  return <>{children}</>
}

const webFont = (
  font: string,
  modifier?: string // used by native only as we need to specify different font weights
) =>
  Platform.select({
    // e.g... change me!
    web: `${font}, -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Helvetica, Arial, Inter-serif`,
    default: `${font}${modifier ? ' ' + modifier : ''}`,
  })

const theme = makeTheme({
  // https://www.dripsy.xyz/usage/theming/create
  customFonts: {
    [rootFontName]: {
      bold: webFont(rootFontName, 'SemiBold'),
      default: webFont(rootFontName),
      normal: webFont(rootFontName),
      '400': webFont(rootFontName),
      '500': webFont(rootFontName, 'Medium'),
      '600': webFont(rootFontName, 'SemiBold'),
      '700': webFont(rootFontName, 'SemiBold'),
      '800': webFont(rootFontName, 'SemiBold'),
      '900': webFont(rootFontName, 'SemiBold'),
    },
  },
  fonts: {
    root: rootFontName,
  }
....

The reason for these modifiers is because I couldn't work out another way of defining each fontface via CSS in the next app with the same name (Work Sans) but then being able to get the native app to pick up these different font files based on the weight. anyway, this is all groovy, and I've got e.g.
 h3: {
    color: (theme) => theme.colors.$black,
    fontSize: [16, 18],
    fontWeight: '600',
    lineHeight: [24, 24],
  },
...

working perfectly with H3s -> it renders Work Sans SemiBold both on the web and native app. however, defining a text variant like this:
text: {
  button: {
      fontSize: [16, 18],
      fontWeight: '500',
      lineHeight: [24, 24],
   },
},
...

and using it like this
 <Text
          variant="button"
          sx={{
            textAlign: 'center',
          }}
        >
          Should be Work Sans Medium!
        </Text>

it renders Work Sans Medium on native, but it renders Work Sans Regular on web...in the inspector the font family is Work Sans and the font weight is 400.
I even tried this:
 <Text
          variant="button"
          sx={{
            fontWeight: '500',
            textAlign: 'center',
          }}
        >
          Should be Work Sans Medium!
        </Text>

which had no effect. the only thing i could do to get it to render the medium font was this
 <Text
          variant="button"
          // not working without this and i have no idea why...
          style={{ fontWeight: '500' }}
          sx={{
            textAlign: 'center',
          }}
        >
        Should be Work Sans Medium!
        </Text>

have you seen this before / do you have any idea why this might be? thanks so much in advance!

yeah I think we’re missing the font-face code on Web. I’ll try to add that when I get the chance. You just have to use font face CSS in _document, make every font normal weight and name it after its font file.

Just today I've noticed +/- the same issue in a different context... on web, when fallback fonts are used before loading the custom font.
Missing the css style font-weight (especially 900) made it look very different and the moment the proper font loaded, it was quite a "bold blink" 😅  ... so transforming fontWeight into font-face should not remove it, but have both.
Anyway, thank you for adding this on your todo-list 👍

closing in favor of #193


45614 : Add ${OriginalSourcePath} replacement into pipeline job

Rationale
Currently, if a custom script pipeline job is started via the filebrowser import button the ${OriginalSourcePath} token is not available but if run from a file watcher that token is available. In the former case, while the input file is available, it is relative from the temp working directory and would need to be normalized if they needed the full path.
From a convenience and consistency standpoint we want to support the token in both scenarios. Docs seem to suggest that the replacement is also available.
Related issue

@labkey-jeckels, agreed that it's probably not the best way to handle multiple input files, but as you mentioned it's not likely for this particular scenario. One thing I did consider for the multiple input case is to add replacements like : ${OriginalSourcePath[0]}, ${OriginalSourcePath[1]} etc.


Current Readme is not reflecting the state of the repository

⚠ Is your feature request related to a problem? Please describe

💡 Describe the solution you'd like
Currently the readme file of the project doesn't reflect the actuall state.
🤚 Do you want to develop this feature yourself?

[X] Yes
[ ] No

#5 is solving this issue.


Sysdig does not work

Basic info
To make sure that we are on the same page:

Kernel: Linux nixos 4.4.6 #1-NixOS SMP Wed Mar 16 15:43:17 UTC 2016 x86_64 GNU/Linux
System: 16.09pre79453.32b7b00 (Flounder)
Nix version: nix-env (Nix) 1.11.2
Nixpkgs version: "16.09pre79453.32b7b00"

Describe your issue here
When installing sysdig and trying to run it, it does not find the sysdig driver.
Expected result
sysdig starts and captures events.
Actual result
sysdig fails with
Unable to load the driver
error opening device /dev/sysdig0. Make sure you have root credentials and that the sysdig-probe module is loaded.

Steps to reproduce

install sysdig (I did it via environment.systemPackages and sudo nixos-rebuild switch)
try to run sysdig:

~ > sudo sysdig
Unable to load the driver
error opening device /dev/sysdig0. Make sure you have root credentials and that the sysdig-probe module is loaded.

pinging @7c6f434c because I guess that I am just doing something wrong ;)

sounds like either the sysdig package providing the module has to be added, or sysdig enabled in the kernel

any idea on how to do that? I must admit I don't have one ;)

Ah I found the required config.  Add this to your configuration.nix
boot.extraModulePackages = [ pkgs.linuxPackages.sysdig ];


Create segwit transactions

Beyond using compressed keys (issue #1), further transaction cost reductions are possible using SegWit.
I investigated this but found some issues. Bitcoin Core (as of 0.15.1) uses 'addwitnessaddress' to create a SegWit-compatible address, but this RPC command does not work on an offline node:
error code: -4
error message:
Segregated witness not enabled on network

Which isn't true, but since it doesn't have a network connection, it doesn't realize that.
It also seems that the API is in flux and will be changing in a near-future release of Bitcoin Core.
So this issue is a placeholder for future work. When the Bitcoin Core API stabilizes and is usable offline, let's add SegWit support to Glacier to reduce the transaction costs.
We will want to make sure that the future SegWit-enabled Glacier can still withdraw bitcoins from addresses created using older Glacier versions without any additional hassle. Ideally the user will not have to know or care whether a given address is SegWit or not, except that transaction costs will be lower.

I'm working on this using a pre-release build of Bitcoin Core v0.16 but hit a hiccup: #12418 signrawtransaction unable to sign p2sh-segwit multisig transaction

I worked around the above issue and have a working implementation of p2wsh-in-p2sh segwit addresses. Two nice things about it: (1) no changes to the Glacier Protocol document are required; (2) withdrawing from addresses created by earlier Glacier versions still work seamlessly.
A typical withdrawal transaction dropped from a vsize of 407 to 225. At today's fee rate of 90 sat/B and a price of $8686, that's a savings of $1.42 per withdrawal. (More precisely, per UTXO spent.) That doesn't sound like much, but keep in mind the savings will come at withdrawal time, and who knows what the fee rate and price will be at that time. At January 7's fee rate of 510 sat/B and price of $16585, this change would have saved you $15.39 per withdrawal. That's on top of the $10.91 savings from #10.
The change is ready for a PR, but merging will have to wait until Bitcoin Core v0.16 is released to the Ubuntu PPA. I'm going to wait for the Glacier maintainers to come out of hibernation so I can rebase this onto the other changes I've sent recently.

This was released in v0.93.


Compiling static libs?

Hello,
When compiling static libs using mbed-cli, any lib the references mbed-os, or the static version of mbed-os (i.e pre-compiled), copies in all of the headers, linker script, etc. from mbed-os into the build directory of the static library.
This creates a problem when you have multiple libs that reference  mbed-os in your project and you want to use static builds of them vs re-compiling them every time.
I address this currently by building my static libs in a temporary location, and then just copy over the .h files and archive into LIBRARIES/NAME/ folder within the root of my project.  I delete the temporary build location.  I can then just compile the code I am working on instead of mbed-os, awesomelib1, awesomelib2,... etc. while working on the new code.
I am doing something wrong?  Does my question need more explanation?  My mbed-cli workspace structure follows;
mbed_cli_wkspc
---->libs
-------->mbed-os
-------->lib1
---->programs
--------->blinky
------------>BUILD
------------>LIBRARIES(static)
--------->blinky2
I even tried keeping the static copies in another location, without deleting the extra stuff that causes the issue, and still, same issue.  I might change to have my static builds in one location, so that I don't have multiple copies, one for each program, but that is a separate thought from this.
Eventually I want to look into adding mbed-cli to Sublime text using there build system features, but I need to learn that still.
Any suggestions, constructive comments on my workflow, etc. would be appreciated.
Thanks,

I can then just compile the code I am working on instead of mbed-os, awesomelib1, awesomelib2,... etc. while working on the new code.

This will happen anyway, assuming that you do not request a clean build. the build tools keep track of what has changed (including headers) and recompile only what is needed.
If you don't have a copy of mbed OS in a project, mbed CLI will download the mbed 2 tools and place them in a hidden .temp directory inside each project. This is probably not what you want.

There is a big disadvantage of using static libraries with mbed OS projects: You can't change the configuration.

This is probably not what you want.

Correct, I want my libs in a separate location that I maintain a single copy of.  I don't want new copies of libs I use frequently every time I create a new program, so I use --creat-only.

Let me try something based on your comment and get back to you.

Let me try something based on your comment and get back to you.

Let me know how it goes. 😄 Maybe we can document how to work around this better as a result of your findings.

@theotherjimmy
So, I couldn't recall if I had tried building the first time with all the required --source paths, and then just trying, mbed compile on the next build, to see if the BUILD directory had everything I needed.  It doesn't.
What you said above is true if you have the libs in the root of your project, but not if you keep them separate.  So, if you keep them separate you must reference them every time, or build a static copy that you keep locally, which is what I do.
It would be cool if there was a flag that told mbed-cli to do the operation of just keeping the required .h files and archive in the library build directory when done building a library.  It isn't a big deal now that I am experimenting with scripting the process, but it took a bit to figure out.
Is my workflow irregular?  Isn't it common to just have one copy of your libraries source, under version control, that you can build static copies of and use?
For documentation purposes I can do a better job of writting up my process and share it with you if you think it would be helpful.  But if my process is irregular and not the norm, would it be helpful?
Thanks,

Maybe I am making things harder on myself than need be.
If I think about it, having my libs in a remote location on my machine (that is under version control and available to others on a server) vs a remote location on a server that I pull from and place in the root of my project, isn't much different than if I compile static copies of the ones locally on my machine and then move the headers and archive over.
The differences are;

If I add a library from the server using mbed-cli, it pulls in the source and additional stuff to work with hg/git.  Once compiled, its compiled and doesn't get recompiled unless I change it, or do a clean build.  The pro is, the lib is in the root of my project and I don't have to add its path when compiling every time.  The con is, I have multiple copies of the lib all over my workspace, all under version control.  Not sure if this is a con, or a personal problem.

If I stay with my current set up, it is basically the same thing, I have my libs under version control and available to others through hg/mbed or GitHub, but I have to manage moving the required files from the static build into the root of my project if I don't want to add the path every time, which is the current con.  The pro, I have one copy of the src under version control, on my machine.

I will have to think about this more...

@j3270 Did you find answer to your question? Are you happy to close this issue if resolved for you?

ARM Internal Ref: MBOTRIAGE-456


Clarify instructions in Acme Controller Workshop

Closes #1477.

Sorry, I seem unable to make the DCO test pass. Would appreciate your help.

Sorry, I seem unable to make the DCO test pass. Would appreciate your help.

To DCO signoff your commits you use the git commit -s or git commit --signoff option, it's tough to fix if you do it wrong.  You can try the instructions linked on the DCO details link, or sometimes I just create a new branch and start over.

Sorry, I seem unable to make the DCO test pass. Would appreciate your help.

To DCO signoff your commits you use the git commit -s or git commit --signoff option, it's tough to fix if you do it wrong. You can try the instructions linked on the DCO details link, or sometimes I just create a new branch and start over.

Thanks! I made a new PR: #1484.