Cloudflare issues with token in config

What happened?
I'm having an issue with cloudflare:apiToken stored as a secret where it looks like it's being ignore however exporting the variable or passing into the call both work.
Steps to reproduce
Peforming
AWS_PROFILE=my_profile pulumi config set cloudflare:apiToken --secret rEdAcTeD
AWS_PROFILE=my_profile pulumi refresh

results in all my cloudflare resources errorring like
    error: Preview failed: could not validate provider configuration: 1 error occurred:
    	* Invalid combination of arguments: "api_key": one of `api_key,api_token` must be specified

If I provide the token via the command line like so, works
AWS_PROFILE=my_profile CLOUDFLARE_API_TOKEN=rEdAcTeD pulumi refresh

or
export CLOUDFLARE_API_TOKEN=rEdAcTeD
AWS_PROFILE=my_profile pulumi refresh

Expected Behavior
Refresh without errors
Actual Behavior
Errors for all cloudflare resources
Output of pulumi about
CLI
Version      3.38.0
Go Version   go1.19
Go Compiler  gc

Plugins
NAME        VERSION
aws         5.11.0
cloudflare  4.9.0
docker      3.4.1
nodejs      unknown
random      4.8.2
terraform   5.6.6

Host
OS       debian
Version  11.4
Arch     x86_64

This project is written in nodejs: executable='/usr/local/bin/node' version='v16.16.0'

Current Stack: global

--Removed 280 resources

Found no pending operations associated with global

Backend
Name           c94133a78fad
URL            s3://my-s3-state/path
User           root
Organizations

Dependencies:
NAME                VERSION
@pulumi/awsx        0.40.0
@pulumi/pulumi      3.38.0
@types/lodash       4.14.184
@types/node         14.18.26
lodash              4.17.21
@pulumi/aws         5.11.0
@pulumi/cloudflare  4.9.0
@pulumi/random      4.8.2
@pulumi/terraform   5.6.6

### Additional context

I've tried with the latest cloudflare and pulumi versions too

### Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

My understanding is that this provider doesn't really support the config option even though the installation guide says so here: https://www.pulumi.com/registry/packages/cloudflare/installation-configuration/#configuring-the-provider
@guineveresaenger sounds like with the addition of https://github.com/pulumi/pulumi-terraform-bridge/pull/606/ we should be able to make this sort of support a lot simpler to add?

To be precise there are two options - fix the documentation to remove the config option setting or add support for config options. The latter would be more desirable.

@stack72 to make sure my understanding is correct here.

https://github.com/pulumi/pulumi-terraform-bridge/pull/606 is really only a set of helper functions for warning - they won't affect configuration options at all. Let me look at what is happening here - my guess is that there's something going wring with the secret part.
@lilHermit what happens when you use pulumi config set cloudflare:apiToken <redacted> - but without the --secret flag?

Thanks @guineveresaenger - I had misunderstood a couple of things.
Guin and I looked through this together and I think we understand what is happening here.
@lilHermit  - it sounds like you have an existing cloudflare provider initialized using the api key. Can you post some details on how you are passing that to the provider? i.e. is through the config parameters, passed explicitly in the constructor or the environment variables?
Only one of api key and api token can be passed to the provider as specified but this is missing from the Pulumi provider's documentation. When you specify the api token through pulumi's config parameter, the terraform provider's validation is triggered and it fails with the error you saw. However, the validation is skipped when the token is specified through the environment variable. Moreover, the TF provider prefers the api token over the api key when specified using the environment variables. Overall this is expected behavior though I admit the documentation does not make this obvious which we will fix.
In summary, you want to only set one of the API key and API tokens as the error suggests.

@lilHermit what happens when you use pulumi config set cloudflare:apiToken <redacted> - but without the --secret flag?

It errors because it believes it's a secret
error: config value for 'cloudflare:apiToken' looks like a secret; rerun with --secret to encrypt it, or --plaintext if you meant to store in plaintext```

Thanks @guineveresaenger - I had misunderstood a couple of things.
Guin and I looked through this together and I think we understand what is happening here. @lilHermit - it sounds like you have an existing cloudflare provider initialized using the api key. Can you post some details on how you are passing that to the provider? i.e. is through the config parameters, passed explicitly in the constructor or the environment variables?
Only one of api key and api token can be passed to the provider as specified but this is missing from the Pulumi provider's documentation. When you specify the api token through pulumi's config parameter, the terraform provider's validation is triggered and it fails with the error you saw. However, the validation is skipped when the token is specified through the environment variable. Moreover, the TF provider prefers the api token over the api key when specified using the environment variables. Overall this is expected behavior though I admit the documentation does not make this obvious which we will fix.
In summary, you want to only set one of the API key and API tokens as the error suggests.
I am not initialising the provider manually I'm letting the code do this as per the docs. It did work for sometime and then all of a sudden stopped. I'm only using API token not key. As I said using the ENV far the provider picks up the apiToken but not from the config. Whilst ENV works ok for local runs it's not something I want to do in CICD.

hi @lilHermit - here are a few ways to check your configuration settings to make sure you're not accidentally providing both api_key and api_token.

check in your Pulumi.<stackname>.yaml to see if api_key is hiding in there
run pulumi config get cloudflare:api_keyandpulumi config get cloudflare:api_token
check on pulumi.com on youraccount/yourproject/yourstack under "Configuration" for any discrepancies
You can also look for api_key and api_token in the output of pulumi stack export - it is possible you may have set them on individual resources, although that is really unlikely to be possible for these values - I'm not super familiar with Cloudflare though.

If the error message is correct (and it might not be; these OnlyOneOf settings have some interesting logic sometimes) then you have an api_key sitting around quietly somewhere.
At this point, we'd need to see a code sample to verify we can repro this behavior and look into it. 🙇♀

hi @lilHermit - here are a few ways to check your configuration settings to make sure you're not accidentally providing both api_key and api_token.
Ok strangely the documentation says apiKey and apiToken Cloudflare docs but the error implies api_key / api_token. I have changed my Pulumi.<stackname>.yaml to api_token to test but still the same

check in your Pulumi.<stackname>.yaml to see if api_key is hiding in there

There is an apiToken but this gets ignored, the only way to provide it is via CLOUDFLARE_API_TOKEN env variable

run pulumi config get cloudflare:api_keyand pulumi config get cloudflare:api_token

root@05eec48ecb07:/pulumi/projects# AWS_PROFILE=my-profile pulumi config get cloudflare:apiKey
error: configuration key 'cloudflare:apiKey' not found for stack 'global'

root@05eec48ecb07:/pulumi/projects# AWS_PROFILE=my-profile pulumi config get cloudflare:apiToken
<rEdAcTeDtOkEn>

check on pulumi.com on youraccount/yourproject/yourstack under "Configuration" for any discrepancies

We're not using pulumi.com for state (s3 bucket)

You can also look for api_key and api_token in the output of pulumi stack export - it is possible you may have set them on individual resources, although that is really unlikely to be possible for these values - I'm not super familiar with Cloudflare though.

root@05eec48ecb07:/pulumi/projects# AWS_PROFILE=my-profile pulumi stack export | grep apiToken
root@05eec48ecb07:/pulumi/projects# AWS_PROFILE=my-profile pulumi stack export | grep apiKey

If the error message is correct (and it might not be; these OnlyOneOf settings have some interesting logic sometimes) then you have an api_key sitting around quietly somewhere.
At this point, we'd need to see a code sample to verify we can repro this behavior and look into it. bowing_woman

I'll create  repo this morning

Ok on creating a "proof of issue" repo it works fine so there must be something somewhere in the stack/state
In my program
AWS_PROFILE=my-profile pulumi stack export | egrep -i "api_key|apiKey|api_token|apiToken"

Returns no matches
In the "proof of issue"
pulumi stack export | egrep -i "api_key|apiKey|api_token|apiToken"
                    "apiToken": {
                    "apiToken": {

I then found this thread
Running the following fixed the provider and now a refresh works without issues
AWS_PROFILE=my-profile pulumi up --target "urn:pulumi:global::my-program::pulumi:providers:cloudflare::default_4_10_0" --skip-preview

Confirmation of the token now in the state
AWS_PROFILE=my-profile pulumi stack export | egrep -i "api_key|apiKey|api_token|apiToken"
                    "apiToken": {
                    "apiToken": {

Summary
There was neither aplToken or apiKey in the state so the error message is misleading. I assume the provider had got out of sync with the config, I noticed the pulumi config refresh command which removed the apiToken from the config it might be worth haveing the opposite to sync state with the config?!

Hi @lilHermit - I am so sorry for all this back and forth. I believe the root cause here is  that you're correct, our documentation is wrong, and I have pushed a fix for that here.
Since it sounds like you've figured out a way forward, I'm going to close this issue once the registry PR merges.
Thank you for reporting and apologies for the misleading documentation.

Hi @lilHermit - apologies for the delay.
I tried this with the most recent version of Pulumi and could not reproduce this issue. Please re-open and ensure to add the "needs-triage" label if you're still having trouble!


Htmlcss branch

Hello! have checked my code again?
On Wed, Feb 15, 2023 at 12:43 AM Francis Ugorji @.***>
wrote:

@.**** commented on this pull request.
In README.md
https://github.com/BANCUNGUYE66/-Hello-Microverse-project/pull/1#discussion_r1106412014
:

+## ❓ FAQ (OPTIONAL)

+> Add at least 2 questions new developers would ask when they decide to use your project.

+- [Question_1]

[Answer_1]

+- [Question_2]

[Answer_2]

+(back to top)

@BANCUNGUYE66 https://github.com/BANCUNGUYE66 you welcome 👍
—
Reply to this email directly, view it on GitHub
https://github.com/BANCUNGUYE66/-Hello-Microverse-project/pull/1#discussion_r1106412014,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3Z4RYCMLL6AD7FUELXJVTTWXP4APANCNFSM6AAAAAAU3373SM
.
You are receiving this because you were mentioned.Message ID:
@.***
com>


Problem in Mac?

Hi Cheerfulstoic, I got a problem trying to install in Mac, do you have any report about it? Moreover I would like to add it on my website http://odlg.org , do you think I can do that?

Feel free to re-open if you still need help


New config implementation

TODO

[x] Document it + add mention about e.g. --config #375
[x] When no config file is provided should fall back to default configuration
[ ] Verbose safty-check for config builder.

Overview
This should come after https://github.com/callstack/haul/pull/339 🙏
I've introduced new config based on #323
Default config file is now haul.config.js
export default {
  // Haul specific options - currently none
  webpack: {}, // Webpack config
}

tldr;
type ConfigOptions = {
  root: string,
  platform: 'ios' | 'android',
  dev: boolean,
  minify?: boolean,
  bundle?: boolean,
};

function createWebpackConfig from Haul package is a helper to create a Webpack configuration. You can pass an argument as a function and the first argument will be ConfigOptions object, or just a plain object if you don't need configuration.
Examples
import { createWebpackConfig } from 'haul';

export default {
  webpack: createWebpackConfig(({ platform }) => {
    entry: `./index.${platform}.js`,
  }),
}

You can also provide whole Webpack config without merging it with ours.
import MyConfig from 'webpack.config.js'

export default {
  webpack: MyConfig,
}

or you can easily override ours
import { createWebpackConfig } from 'haul';

export default {
  webpack: env => {
    const config = createWebpackConfig({
      entry: `./index.js`,
    })(env);

    config.plugins.push(new CaseSensitivePathsPlugin());

    return config;
  },
}

Can you change the base to workers PR? It would be easier to review this way

@thymikee good point I've forgotten. 👍

I will reimplement this PR. Stay tuned. 👍

We will also need to support the old config format as well for now (with a deprecation warning).

@satya164 that actually make a sense. I will take a look on it.

@satya164 Please, re-check 👍

Are you handling the case where no config file is present? I couldn't find it in the PR. It should be something like this:

No, I wasn't aware that we are on "no-config" hype train. 🚂 I will fix it.

Documentation updated. This should be ready now. I just have to wait for CI fix coming from #339. 💪 @satya164

Hm. It looks that I have to resolve few conflicts.

@zamotany can you comment about avoiding mutating the resulting config which happens in your PR? it needs to be changed in this PR or yours.

Would you be open to opening up the configuration for the haste resolver plugin as well? We're currently forking it to allow for custom platforms to be added with haul but we would need a hook in the config to use this approach instead of forking the whole thing. I'd specifically like to allow a set of modules in addition to react-native to be added.

@jukben right now the providesModules equivalent in haul is injected with the HasteResolver plugin. You currently only get the choice of resolving react-native. It would be more convenient to have a configuration option that specifies this with [ 'react-native' ] as the default, but allow out of tree platforms like react-native-windows etc to inject their Haste modules.
This way if I wanted to add out of tree platforms to react-native I would only need to add:
providesModules: ['react-native', 'react-native-windows']

This is similar to the way that metro does it with rn-cli.
I guess what i'm asking for is, can we expose the HasteResolver plugin configuration in this new config object you are building?

can we expose the HasteResolver plugin configuration

We can add some parameters and export HasteResolverPlugin. Then you can use this plugin to add more haste stuff.

@satya164 i totally agree, that a babel-plugin re-writing the haste modules to relative paths is a better long term solution. I may undertake that myself when I have a chance. But perhaps we could use the configuration option to remove the HasteResolver when you don't give it providesModules in that case. Right now there isn't any way to opt out of haste. If you are on a project that has totally adopted Haul and webpack you don't need haste to fix the platform imports so it would be faster to skip (if we somehow had a version of react-native itself that was haste free). I was thinking of using this configuration as a means to help those migrating from metro, who currently rely on haste.

@jukben mind merging next branch and continue working on this?

You'll also need to address this comment: https://github.com/callstack/haul/pull/339#discussion_r171362226

BTW you prolly need to do a rebase so that @zamotany's commits appear in the diff.

Yea, I've tried to ease things by merging, but that's just too hard to get right, since I was not in the topic (sorry about that). I've already talked to @jukben and he's going to revert the stuff I did and merge/rebase once again.

Good to go, lint and test are passing @thymikee
@jukben Please fix flow errors.
There's also small problem, right now You using a deprecated style of the configuration [...] warning gets piped to <stdout.log. We need to change that.

This is ready to go. Finally! 🎉
Just wait for @thymikee. He will implement jest-diff to reduce size of snapshots. Which is a good idea. 🙏

I've left one complete snapshot inside getConfig and used diffs and asymmetric assertions for the rest

cc @satya164 one final review?

@jukben What about updating docs? https://github.com/callstack/haul/blob/master/docs/Configuration.md

@AleksandrZhukov Oh snap. Probably some flaw in the rebase. 😔 Can you bring it back in the PR? https://github.com/callstack/haul/blob/75bf51096909e8a7a3cd031060253240db3f3978/docs/Configuration.md

@jukben thx


Allow panic in fuzz test code

Add nolint comments.
ref: https://github.com/pion/turn/pull/112

Codecov Report

Merging #113 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #113   +/-   ##
=======================================
  Coverage   65.71%   65.71%
=======================================
  Files          36       36
  Lines        1823     1823
=======================================
  Hits         1198     1198
  Misses        496      496
  Partials      129      129

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 06a2f68...3da0901. Read the comment docs.


Make the homepage hero display a message when no open listings are available

I think for this one we need to introduce some kind of store/ actions. I don't know if there was already a discussion about it?

I think the goal was to avoid a store implementation until the next major phase of work, when we do the application form, so that we can consider the state management solution in the context of the form solution. Given that it's super unlikely for the state to switch during a user session, can we not just pass props?

Sure, we can use props, but in that case we need to load listings on home page and then when we get to listings. I was trying to avoid it. I can do it that way.

Totally good point. I don't think it's a big deal for the time being (especially since the static listings load should be super-fast), but I agree that it's not ideal longer term.


MenuItems are not fullWidth if TextField is fullWidth

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

If a TextField is set to fullWidth and used as a Select, the MenuItems should be as wide as the input (and Menu).
Current Behavior

The Menu is the same width as the TextField, but the MenuItems are not the correct size.

Steps to Reproduce (for bugs)

<TextField fullWidth select  label="Days and Stuff">
    <MenuItem value={0}>Today</MenuItem>
    <MenuItem value={1}>24 Hours</MenuItem>
    <MenuItem value={7}>7 Days</MenuItem>
    <MenuItem value={15'}>15 Days</MenuItem>
    <MenuItem value={30}>30 Days</MenuItem>
</TextField>

Context

This just looks wonky - its not critical but people think our app is broken. In the meantime, I've used the native prop to skirt around the issue.
Your Environment

Tech
Version

Material-UI
beta 33

React
15.x

browser
Chrome / FF

etc

This can be used as a workaround:
<TextField fullWidth select SelectProps={{ MenuProps: { MenuListProps: { style: { width: '100%' } } } }}>

Another alternative is to use an override on the List component, i.e:
MuiList: {
      root: {
        width: '100%',
      },
    },

Not sure if this was fixed already but could not reproduce with chrome / FF
https://codesandbox.io/s/nwy21nll

@oliviertassinari This seems to be fixed: https://codesandbox.io/s/zq7qj3p86x

@joshwooding do you happen to know which version included the fix?

@joshwooding Thank you for looking into it :).
@cvburgess You can try to change the version in the linked codesandbox. I have tried up to v1.0.0, it's working. If you want to stay on the beta, you can dive even further.
v1.0.0-beta.33 is 10 month old, wow, that's all?!

Actually, it's also working with beta.33 😮: https://codesandbox.io/s/zq8koqyxy4. If you guys have a reproduction witht the latest version of Material-UI, we can have a look. Otherwise, let's keep it close.

@oliviertassinari we're on 1.5.1 :/

@cvburgess Looks like it works for 1.5.1 too :/ https://codesandbox.io/s/oxzmqylj46
This is just a standalone component though, do you have an example of the outer component and its styling?


[test][IRGen] Split returnaddress related check into a separate file

llvm.returnaddress is unavailable on WebAssembly, so split the part from access_markers.sil to exclude it conditionally.

@swift-ci Please smoke test

Do anyone have any concern about merging this?


How can I draw canvas on cameraTextureView

I tried below but nothing happened:
val paint = Paint().apply {
             isAntiAlias = true
             style = Paint.Style.STROKE
             color = Color.RED
            strokeWidth = 10f
}

var canvas = Canvas(bitmap)
canvas.drawRect(
           rect.x.toFloat(),
           rect.y.toFloat(),
           rect.x.toFloat() + rect.width,
          rect.y.toFloat() + rect.height,
)

cameraTextureView.unlockCanvasAndPost(canvas)

What sample are you trying to do this with? Camera2 or CameraX? My first guess would be that you are drawing on the TextureView but the camera keeps outputting new frames and drawing on top of your code, which is why you are not seeing any changes. You need to do the drawing in a different layer or implement some synchronization mechanism.

mm, could be your statement is correct @owahltinez

the camera keeps outputting new frames and drawing on top of your code
You need to do the drawing in a different layer

Below what I did, appreciate your comments for optimization
I created an image view, with the same dimension, and location (constrains) of the cameeraX texture view, to act as overlay, and do all the drawings on it,  just need to be sure that this overlay is above not under the texture view, i.e. following it in the layout xml file.
<?xml version="1.0" encoding="utf-8"?>
<androidx.constraintlayout.widget.ConstraintLayout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    xmlns:tools="http://schemas.android.com/tools"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    tools:context=".MainActivity">

    <TextureView
        android:id="@+id/view_finder"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:layout_marginTop="24dp"
        android:visibility="visible" />

    <ImageView
        android:id="@+id/imageView"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:contentDescription="@string/pic_desc"
        android:visibility="visible" />

</androidx.constraintlayout.widget.ConstraintLayout>

And the drawing code is:
lateinit var overlay: Bitmap
private fun startCamera() {
        val analyzerConfig = ImageAnalysisConfig.Builder().apply {
            setImageReaderMode(
                ImageAnalysis.ImageReaderMode.ACQUIRE_LATEST_IMAGE)
        }.build()

        val analyzerUseCase = ImageAnalysis(analyzerConfig).apply {
            analyzer = ImageAnalysis.Analyzer { image, rotationDegrees ->
                val bitmap = view_finder.bitmap ?: return@Analyzer
                overlay = Bitmap.createBitmap(bitmap.width, bitmap.height, Bitmap.Config.ARGB_8888)

                scope.launch(Dispatchers.Unconfined) {
                    val mat = Mat()
                    Utils.bitmapToMat(bitmap!!, mat)

                    val detectedFaces = FaceDetection.detectFaces(bitmap!!)

                   if (detectedFaces.toArray().isNotEmpty()) {
                       val paint = Paint().apply {
                           isAntiAlias = true
                           style = Paint.Style.STROKE
                           color = Color.RED
                           strokeWidth = 10f
                       }

                       for (rect in detectedFaces.toArray()) {
                           var canvas = Canvas(overlay)
                           canvas.drawRect(
                               rect.x.toFloat(),
                               rect.y.toFloat(),
                               rect.x.toFloat() + rect.width,
                               rect.y.toFloat() + rect.height,
                               paint
                           )
                           overlay?.let { Canvas(it) }?.apply {
                               canvas
                           }
                       }
                   }
                }

                runOnUiThread {
                    imageView.setImageBitmap(overlay)
                }
            }
        }
   CameraX.bindToLifecycle(this, preview, imageCapture, analyzerUseCase)
}

Below is an output of my app as of now showing this drawing:


Hashing Implement

Implement hashing in any language but javascript. Try to include probing techniques.

Hi, @ephremdeme Can I be assigned this issue for Hacktoberfest PR ?
Also do you want this to be implemented only in any one language or more ?

It will be great if you will implement it in many language

Hi @ephremdeme, just one more question..
Should I put the code in a folder and then create a PR?

Hi @ephremdeme, Should I put all the code I will write on this issue in the folder named Hashing ?

Yeah, sure.

Hey @ephremdeme I can implement it in Java.Should I?

Ok, here you go.

I implemented it in Java .


Big gaps on outline with width > 1

Describe the bug
When using the Stylized Surface Shader with a width bigger than 1 I have big gaps between the outlines on my low poly model.
To Reproduce
Steps to reproduce the behavior:

Add Low Poly Model
Add Material if Stylized Surface Shader
Settings as image below

Expected behavior
I'd expect to have a clear outline, but it has gaps and looks bugged. Problem is even bigger on a higher distance
Screenshots

If applicable, add screenshots to help explain your problem.
Unity details:

Flat Kit version: 2.6.5
Unity version: 2020.2.3f1
Graphics Pipeline: URP
Development OS: [e.g. Windows]

Flat Kit has two ways of generating outlines: with the Stylized Surface shader and with the Outline Renderer Feature. The former is a quick one, and unlike Photoshop outline, it is a tool to work live with 3D objects, and It is best suited for the smooth rounded objects. The latter method gives precise outlines on the objects of any shape.
When you use the Stylized Surface outline, in the URP version of Flat Kit you can see the Scale parameter. It is designed to make the outlines appear nicer on such sharp-angled meshes like the cubes. Please, look at the difference it makes to the outlines as opposed to using only the Width parameter.

It is described in the documentation — Stylized Surface, Main Parameters chapter,
(please, scroll down to the 'Outline' paragraph).
This topic had been discussed earlier here in the Git Issues, for example this one.

thanks for the very fast support ! I missed that in the docs - sorry for that!


cursor not at input after auto-fill on an inline CSS property

hey, just wanted to report a small improvement that can be made in auto-fill of properties inside inline style elements.
upon auto-filling the property inside an inline style element the cursor is taken to after the ; - for all other elements VS code auto-fill takes the cursor automatically to the place where input is required which is very helpful, doing the same for inline style element will be great i.e, take the cursor to before ;
https://user-images.githubusercontent.com/25464742/198877265-7a88e56a-c2c4-4c22-b1c3-4cd60ff32f9c.mov

The problem is that after completing style, you are in snippet mode (visible by the line after "") :

When typing further, the css completions for background-color also comes back with a snippet. But code completion doesn't not allow nested snippet modes (I assume) and just applies it as a text.

When a snippet is active, IntelliSense as you type (aka quick suggestions) is disabled. That is because there is a conflict between the Tab-key which moves to the next placeholder but also accepts a completion. You wouldn't be able to type in a placeholder and then move to the next placeholder as you would accept a suggestion then. You have the following options

change the default via the editor.suggest.snippetsPreventQuickSuggestions-setting
in snippets trigger suggestions manually (via Ctrl+Space, Alt+ESC (macOS), or ctrl/cmd+i)

hey I did not fully get you but how is this working for height placeholder? (attaching below)
here the cursor did not move to after ; but instead at the place where input is required before ;
https://user-images.githubusercontent.com/25464742/199081775-898b002e-13c6-4501-829c-ee046a41d5e9.mov

@lavishsaluja To see the bug you must start typing style
@jrieken changingeditor.suggest.snippetsPreventQuickSuggestions` makes no difference. Note that the second suggestion window is triggered by the completion itself (it has am accept command), not by quick suggest
I think would be ok to end the first snippet mode when the second completion dialog is opened. Currently Tab accepts the proposal.

I believe what you are seeing is actually https://github.com/microsoft/vscode/issues/163808


Helm: Missing default value for postgresql.service.port

I am trying to deploy the Helm Chart with the default configuration exactly like described in https://backstage.io/docs/deployment/helm. But it fails, because Helm is unable to template the postgres-test.yaml, because postgresql.service.port is not set.
Expected Behavior
I expect the Helm chart to be deployable like described in the docs.
If I add the following lines to our values.yaml the deployment works like expected:
postgresql:
  service:
    port: 5432

Actual Behavior
Helm is unable to template the postgres-test.yaml, because postgresql.service.port is not set.
Steps to Reproduce
Deploy the Helm Chart like described here: https://backstage.io/docs/deployment/helm
Your Environment

Browser Information: -

Output of yarn backstage-cli info: -

Seems sensible, is it something you would like to contribute?

Hello @Rugvip ,
suddenly the issue was gone. I am closing the issue.

Issue is not fixed at all
git clone https://github.com/backstage/backstage.git
cd contrib/chart/backstage
helm dependency update

cat <<EOF > cfg.yml
appConfig:
  app:
    baseUrl: https://backstage.<IP_ADDRESS>.nip.io
    title: Backstage
  backend:
    baseUrl: https://backstage.<IP_ADDRESS>.nip.io
    cors:
      origin: https://backstage.<IP_ADDRESS>.nip.io
  lighthouse:
    baseUrl: https://backstage.<IP_ADDRESS>.nip.io/lighthouse-api
  techdocs:
    storageUrl: https://backstage.<IP_ADDRESS>.nip.io/api/techdocs/static/docs
    requestUrl: https://backstage.<IP_ADDRESS>.nip.io/api/techdocs
EOF

helm install -f cfg.yml backstage .
Error: INSTALLATION FAILED: template: backstage/templates/tests/test-postgresql.yaml:17:27: executing "backstage/templates/tests/test-postgresql.yaml" at <.Values.postgresql.service.port>: nil pointer evaluating interface {}.port

I run into the same issue as @alexweide adding the following to values.yaml indeed fixes the issue
postgresql:
  service:
    port: 5432

Issue still exists and should be reopened, adding the lines @JaapHaitsma notes solve the issue

Sorry, will close this again as the helm chart documentation has been removed and we do not plan support the particular chart in contrib going forward. There's a newer chart at https://github.com/vinzscam/backstage-chart/ which I recommend that you use instead.


Restrict unknown scheme of HTTP/2 request

Strictly following RFC 3986 Section 3.1
scheme      = ALPHA *( ALPHA / DIGIT / "+" / "-" / "." )

Cherry-picked to v9.2.x


[XTrending√VIDEOs!]* Oviya Viral Leaked Video 2024 FULL LINK On Social Media X Telegram [NOW√S.E.X.70K]

11 sec ago Oviya Leaked Video Viral On Social Media. ~[XTrending√VIDEOs!]* Oviya Viral Leaked Video 2024 FULL LINK On Social Media X Telegram [NOW√S.E.X.70K]

Oviya's latest video has taken the internet by storm, grabbing the attention of users and igniting widespread discussions on social media. This rising digital creator, renowned for her captivating content, particularly her recent Spiderman-themed video, has experienced a notable surge in interest from fans eager to discover where to view the full version. Many are flocking to platforms like Instagram, X (formerly known as Twitter), and Discord to access her work.
As excitement continues to build, fans are actively expressing their reactions online, demonstrating the significant impact of social media in propelling creators like Oviya into the limelight. With her distinct style and creative approach, she has quickly become a leading figure in the digital space, leaving many intrigued about her future projects and content.
[Trending√_S.E.X√NOW!] Oviya Viral Leaked Video 2024[FULL~HD]

thank you

xcvxcvxcv


Should use CharsetDecoder rather than new String(bytes, UTF_8)

Bad use here: https://github.com/javasync/AsyncFileRw/blob/master/src/main/java/org/javaync/io/AsyncFileReader.java#L81
We cannot assume that we have a valid number of bytes:  res.append(new String(bytes, UTF_8));
This can be wrong: new String(bytes, UTF_8)

Solve on Release 1.1.3.


[Todo] Version should be read from a consolidated location

E.g. in Makefile and then subprocesses use the env variable generated by the Makefile.

This file should also contain the versions of the client runtime and React, React DOM libraries we should with Retro.

This file should also contain the versions of the client runtime and React, React DOM libraries we should with Retro.


Compatibility with Voxelyze

Hi,
Does the new .vxa file have the same formatting as the one the original Voxelyze engine used? I have skimmed through and they look similar but I just wanted to confirm.
Many Thanks,
Minh Vu

Hi Minh Vu,
This project is now being developed as voxcraft-sim.
https://github.com/voxcraft/voxcraft-sim
In general the two VXA formats are similar but not identical. We have some documentation on the differences but it is not complete so if you have trouble finding things please feel free to submit an issue.
Best,
David


benchmark_app wrappers update for 2022.1

Output of benchmark_app changed in 2022.1. Some notebook use wrappers that parse benchmark_app output, either benchmark_model from notebook_utils or a wrapper in the notebook itself. This output is no longer correct, since the line with the string "Latency" is now empty.

@Debskij  can you work on this next week. We've recorded a few sessions where this is empty and I was asked about it the other day. Need to fix the empty latency part.


Fake setTimeout should "fail" on too large delays

Both browsers and Node.js handles timers with int32 and overflows on values above<PHONE_NUMBER>.  It would be good if lolex in some way fails in that case too.
Background:
I read about the maximum delay on setTimeout, and prepared a farTimeout to just recursively wrap the  setTimeout with max timeout multiple times.  But, using test first approach, I noticed that the setTimeout handled 90 days without problem, even though the docs said max ~25 days.  Digging deeper, I realized that the sinon.useFakeTimers gave me a setTimeout that handled larger numbers than Node.js setTimeout.
Suggested solution:
I think something like this in addTimer function would make it behave more like the actual setTimeout:
const maxTimeout =<PHONE_NUMBER>
if (timer.delay && timer.delay > maxTimeout) {
    timer.delay = (timer.delay + maxTimeout) % (maxTimeout * 2) - maxTimeout
}

…not making a pull request right now though since this was quite quickly thrown together; could make one if you think this is a good solution.

Seems reasonable. But the if is unneeded, so the math could be simplified to
// overflow if timer > maxTimeout
timer.delay = timer.delay % maxTimeout;
}

I placed it in addTimer rather than setTimeout since there are similar limitations to other timers, but in addTimer there isn't always a delay?
The + max … - max is to mimic the int32 overflow, that will sometimes render a negative value (making the timer trigger immediately).

There are "timers" like setImmediate and nextTick that does not take arguments, so that might be why.

Was there a PR coming?

I'm sorry, my vacation got in the way!  I'll get to it this week I hope!

New summer, new hopes :-)

There are a few edge cases:
Node does:

When delay is larger than<PHONE_NUMBER> or less than 1, the delay will be set to 1.

Timers API say:

If timeout is less than 0, then set timeout to 0.

We don't handle this case at the moment - can PR to handle. We do handle it not being passed.
The spec itself does not require that the timeout is under 2**32 nor does it require that the timers are overflown in a particular way.
MDN claims:

Browsers including Internet Explorer, Chrome, Safari, and Firefox store the delay as a 32-bit signed integer internally. This causes an integer overflow when using delays larger than<PHONE_NUMBER> (about 24.8 days), resulting in the timeout being executed immediately.

We can definitely do that.

Timers can be nested; after five such nested timers, however, the interval is forced to be at least four milliseconds.

We can likely handle this case, but it's not very interesting (since order is still guaranteed)

Turns out this is actually well defined in WebIDL https://heycam.github.io/webidl/#abstract-opdef-converttoint (thanks to @annavk for pointing me in the right direction!).

Set x to ! IntegerPart(x).
Set x to x modulo 2bitLength.
If signedness is "signed" and x ≥ 2bitLength − 1, then return x − 2bitLength.
Otherwise, return x.

cc @elad-nach (have you started working on it by the way?)

this is implemented as part of the V8, why do you want to write a javascript implementation to something which is already implemented in the underlying engine?

@elad-nach what do you mean? lolex runs in many engines (unless you're suggesting to lift some part from V8), and even in V8 it's just how numbers work - and not implemented - it was specced to behave consistently with two's complement number arithmetic.
Your current code sets the timer to 1ms no matter what - if you look at @fatso83's implementation it actually follows the spec I linked to above in https://github.com/sinonjs/lolex/issues/67#issuecomment-224914479 - but I don't think Chrome or any of the browsers do (overflow) - I think they all actually run the timer immediately.
An easy test for this would be to run with 2 ** 31 - 1 + 1000 and see that it runs immediately and not after 1000ms. @fatso83 - I'm leaning towards liking @elad-nach's current implementation better than the spec compliant one - what do you say?

NodeJS spec specifies that above delays above 2 ** 31 are set to 1. Also ones below 1.

@elad-nach yes, but the DOM spec suggests otherwise so we might want to if/else and set timers accordingly - although this is already an edge case and I think setting them to 1 is a reasonable default for web too.
(I would throw on timers that are too long, but meh)

Closed by #124


Update chatcommands.py

Hi! I'm Victor VosMottor from StackExchange. I wrote a command that is equivalent of whatis and man commands in bash. I think it will be useful ;)

I'm... a little curious why we need this when all commands are explicitly documented already on our site (https://github.com/Charcoal-SE/SmokeDetector/wiki/Commands#wiki-wrapper)

Also, you need to keep in line with the Python standards we uphold to with PEP8 guidelines.  These're your code linting failures:
./chatcommands.py:2324:1: W293 blank line contains whitespace
./chatcommands.py:2325:1: W293 blank line contains whitespace
./chatcommands.py:2332:121: E501 line too long (275 > 120 characters)
./chatcommands.py:2333:121: E501 line too long (272 > 120 characters)
./chatcommands.py:2344:121: E501 line too long (353 > 120 characters)
./chatcommands.py:2349:121: E501 line too long (195 > 120 characters)
./chatcommands.py:2351:121: E501 line too long (145 > 120 characters)
./chatcommands.py:2352:121: E501 line too long (160 > 120 characters)
./chatcommands.py:2353:121: E501 line too long (147 > 120 characters)
./chatcommands.py:2355:121: E501 line too long (155 > 120 characters)
./chatcommands.py:2356:121: E501 line too long (125 > 120 characters)
./chatcommands.py:2357:121: E501 line too long (582 > 120 characters)
./chatcommands.py:2364:1: W391 blank line at end of file

If we do this, I think it would be better to have the documentation be a parameter to the @command decorator — that way we keep the command and the documentation together, and we don’t have to repeat all the aliases. Then the whatis command can just pull the command from the dictionary and return its documentation property.
However, I’m with Thomas on this one: although I have occasionally wished for a command like this, I think the harm outweighs the benefits. We already have thorough documentation on our wiki, and it’s easy enough to just run !!/help, click the link, and Ctrl+F for the command you need. I’d rather not have to maintain two independent copies of the same documentation, because people will update one and forget to update the other.
Also, just for future reference, please use more helpful commit messages than “Update chatcommands.py”. I know that’s GitHub’s default, but that’s a really unhelpful message — if I’m going through a blame, I don’t need to be reminded about the name of the file I’m already looking at. Rather, a commit message should summarize exactly what was changed and why. See How to Write a Git Commit Message. Thanks :)


Feature Request: Make all primitive variables a stack

Ok, I had this thought. What if the all the variables could be a stack. The := operator could push the stack or behave normally. Ie, := will create a new variable or will push a stack on an existing variable. = assigns positition 0 on the stack. Subsequent reads pops the stack, unless it is the last element which is persistent across reads.
Just a thought.

This is an interesting idea, but unfortunately the time for language changes has long passed. Also, note that your feature would make it rather difficult to reason about code: Let's say your := is inside a "for" loop
var x T
for ... {
   x := foo()
   ...
}

Is the stack popped after the for loop or is it as tall as the number of iterations? If it's popped, when is it popped (after each iteration, or at the end of the loop)? And so "Forth"... :-)
In short, I think such a feature would have a hard time in a structured language such as Go.

What are the use cases for this?
I think this is very confusing as the same identifier can have dramatically
different meaning without assignment.


azure-static-sites-client: init at 1.0.021731

Description of changes
Binary for Azure static web apps. More information here.
In theory, should work for x86_64-darwin as well but this PR only introduces support for x86-64-linux.
Tested deployment with ./StaticSitesClient upload.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Updated latest from 1.0.021671 to 1.0.021731.

@SuperSandro2000 Could you take another look, please?

Removed the code required for old versions which would require additional wrapping as the oldest version is now 1.0.021671 (the backup flavor).
https://github.com/NixOS/nixpkgs/blob/de1cee756881e5a09d061cbc89ecc106b0448702/pkgs/development/tools/azure-static-sites-client/default.nix#L27

Result of nixpkgs-review pr 204145 run on x86_64-linux 1

1 package built:

azure-static-sites-client

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1594


how to use tmux as default shell

Hello @0xMrR0b0t 👋
I don't use tmux as the default shell myself. Please ask on the usual tmux support channels 😊

Dupe of #587

@gpakosz, Can i get only the "Copy to OS clipboard" part of the tmux.conf file, I like to keep things in default style.


Improve text colors in dark theme

Fixes #18. I'm super unfamiliar with fluentui so let me know if it's not the right approach!
I couldn't figure out what changes the caret color for the theme picker :cry:
Examples light/dark themes:

Hey Aram! Thanks for the help. Code seems fine, and I tried it out here https://62030091d307bf0007bf3cfb--retrospective-notes.netlify.app/
I think the caret looks fine the way it is.
One thing I'd like your opinion on is if the header of the note should be of a different color than the body of the note (like in light mode)

I have no preference between the 2 tbh!


Bump cpp_demangle to 0.4.

Poke.

Looks fine. I still need to find a way to fix #256 before CI will pass. I normally do this sort of change as part of the release.


Adds Hyperlinks to taskSearch and converts TaskList and Ranking to smart table

#58
There was a conflict because I was merging searchTask.

Few errors occurring
Error: [$parse:syntax] Syntax Error: Token 'Name' is an unexpected token at column 11 of the expression [Requester Name] starting at [Name].
could you check this and push again, thanks

Done.
Should I raise a new PR?
On May 27, 2015 at 1:44:19 PM, Durim Morina<EMAIL_ADDRESS>wrote:
Few errors occurring
Error: [$parse:syntax] Syntax Error: Token 'Name' is an unexpected token at column 11 of the expression [Requester Name] starting at [Name].
could you check this and push again, thanks
—
Reply to this email directly or view it on GitHub.


Captcha

Find a way to avoid Captcha because bots only last 5 minutes before it stops

eso es verdad

Reportbot doesnt work bro

solve captcha

solve captcha

the bots dont even work and most of the time you cant even complete the captcha


Design System > Version 8.3 > Charts > Area Chart > Show error message.

Describe the bug
Show error message.
Steps to reproduce bug
1.Go to 'https://dev-react.raaghu.ai/'
2. Navigate to 'Design System > Version 8.3 > Charts > Area Chart > Controls'
Actual result-
Show error message.
Screenshots

Expected result-
Show gradient proper.
Desktop (please complete the following information):
-OS: [Windows 10 Enterprise]
-Browser [ edge]
-Version [ 125.0.2535.92]

Verified Pass


 When running the following snippet:
var phantom = require('node-phantom-simple');
var app = require('express')();

app.listen(0);

The node process stops handling SIGINT (i.e. Ctrl+C) and must manually be killed with SIGQUIT in order to exit. Removing the first line reverts back to the usual behavior.
Any hints ?
Env:
$ node -v
v4.1.1
$ npm -v
3.3.4
$ cat node_modules/node-phantom-simple/package.json | grep version
  "version": "2.0.5"
$ cat node_modules/express/package.json | grep version
  "version": "4.13.3"
$ uname -a
Linux lgce-arch3 4.2.1-1-ARCH #1 SMP PREEMPT Tue Sep 22 06:57:07 CEST 2015 x86_64 GNU/Linux

https://github.com/baudehlo/node-phantom-simple/blob/master/node-phantom-simple.js#L24
I guess, your app worked before, because you had no signal handlers at all, and some defaults were used. But you can't rely that nobody will use those handlers. Add your own with required behaviour.

Hmm, I would assume that would allow the default SIGINT handler to still
run though. If not, that's incorrect behaviour.
On Fri, Oct 9, 2015 at 9:06 AM, Vitaly Puzrin<EMAIL_ADDRESS>wrote:

https://github.com/baudehlo/node-phantom-simple/blob/master/node-phantom-simple.js#L24
I guess, your app worked before, because you had no signal handlers at
all, and some defaults were used. But you can't rely that nobody will use
those handlers. Add your own with required behaviour.
—
Reply to this email directly or view it on GitHub
https://github.com/baudehlo/node-phantom-simple/issues/81#issuecomment-146866350
.

I don't know why node works such way, but I think that's not driver issue.
https://github.com/baudehlo/node-phantom-simple/commit/f1859a07948b06f87fa5270c72318f9587f7d1e4 - here i removed some legacy handlers, but i'm 100% sure those were dirty kludges and should not be in this module.

OK, I guess Node runs process.exit() (or equivalent) when no SIGINT handler is present, but there's nothing on the doc about that. You have to admit that unexpectedly changing signal handling of a program is quite confusing for a library, even though there doesn't seem to be a way to work around this...
I suspect that this "signal proxy" is there to kill the phantom process when the main process is killed right ? In that case, why rely on signals rather than hooking to process.on('exit', handler)?

why rely on signals rather than hooking to process.on('exit', handler)?

See https://github.com/baudehlo/node-phantom-simple/commit/bf04f4dd2f8d795b239eb93c964a9a33d842bd6c and #72

I was more refering to this

It's fired too late, program will exit before it transfer command to phantom.

That's right, my bad... So I guess there is no way in node to perform asynchronous cleanup without making proactive assumptions about the execution environment

Closing?

Well I think maybe the SIGINT handler should also do process.exit(-1), no?
On Fri, Oct 9, 2015 at 10:24 AM, Vitaly Puzrin<EMAIL_ADDRESS>wrote:

Closing?
—
Reply to this email directly or view it on GitHub
https://github.com/baudehlo/node-phantom-simple/issues/81#issuecomment-146886062
.

@baudehlo since this module is not standalone app, it should not force any behaviour to upper level. For example, if i don't wish to react at SIGINT...
It's not cool that package now change default CTRL+C action, but IMHO nobody rely on node defaults in real world (except beginners :smile:). It's more safe to define SIGTERM / SIGINT / unhandledException handlers to have predictable behaviour.

I agree, doing process.exit() also a strong assumption. For instance, If the lib is used in a program that only terminates upon receiving two Ctrl+C in 500ms, you'll kill the phantom process on the first one... Or maybe the program choses not to exit on SIGINT, in that case node-phantom-simple would also exit too soon.
Basically you lack a way to perform async cleanup in the exit event (that would be the best option IMO). A decent workaround could be to exit the node process if there is no other event handler for SIGINT (using [EventEmitter#listenerCount()](https://nodejs.org/api/events.html#events_emitter_listenercount_type)). Or just expect the dev to explicitly perform the closing action, that wouldn't be a shocking expectation.
“Beginners” issues aside, breaking defaults by defaults is not really acceptable if you ask me.

+1 @swordofpain

I don't like magic in code. I would add SIGINT note to known issues in doc https://github.com/baudehlo/node-phantom-simple#known-issues.

Well, If you don't like magic, maybe the auto-quit should just go then ?

Maybe use this instead:
https://nodejs.org/docs/latest-v0.12.x/api/process.html#process_event_beforeexit
On Fri, Oct 9, 2015 at 10:47 AM, Simon Wachter<EMAIL_ADDRESS>wrote:

I agree, doing process.exit() also a strong assumption. For instance, If
the lib is used in a program that only terminates upon receiving two Ctrl+C
in 500ms, you'll kill the phantom process on the first one... Or maybe the
program choses not to exit on SIGINT, in that case node-phantom-simple
would also exit too soon.
Basically you lack a way to perform async cleanup in the exit event (that
would be the best option IMO). A decent workaround could be to exit the
node process if there is no other event handler for SIGINT (using
EventEmitter#listenerCount()).
Or just expect the dev to explicitly perform the closing action, that
wouldn't be a shocking expectation.
“Beginners” issues aside, breaking defaults by defaults is not really
acceptable if you ask me.
—
Reply to this email directly or view it on GitHub
https://github.com/baudehlo/node-phantom-simple/issues/81#issuecomment-146892968
.

Or, as you said, add it to the known issues list and give a way to the dev to disable the magic feature.  May be it's better to just add SINGINT handler instead of improving the world :) ?

I'm not talking about reverting to old code, just to accept an option to not bind to SIGINT/SIGTERM (as the default would be to preserve compatibility if you wish to retain that feature), and let to the user the full responsibility of (explicitly) closing the processes. This approach would allow for:

less magic (you don't like it)
less assumptions (you don't like them)
less defaults silently broken (nobody likes them)

Best of both worlds ! I don't think it's node-phantom-simple's responsibility to take care of process exits, since it's not a standalone app as you correctly pointed out.

But we still have to do something with forked childs. It's not good to leave those after parent close.

Nor is it to close them if the parent doesn't indeed close (inc case of swallowed SIGINT for instance)

What about using .on('beforeExit') ?
On Fri, Oct 9, 2015 at 11:29 AM, Simon Wachter<EMAIL_ADDRESS>wrote:

Nor is it to close them if the parent doesn't indeed close (inc case of
swallowed SIGINT for instance)
—
Reply to this email directly or view it on GitHub
https://github.com/baudehlo/node-phantom-simple/issues/81#issuecomment-146903983
.

I think, we should care about closing phantom instances on process exit. That's important.
Can we use pings or monitor stdin/stdout state at bridge side? So, if bridge detects, that it's no longer mastered, it should kill itself.

Is my suggestion being ignored?

On Oct 9, 2015, at 6:17 PM, Vitaly Puzrin<EMAIL_ADDRESS>wrote:
I think, we should care about closing phantom instances on process exit. That's important.
Can we use pings or monitor stdin/stdout state at bridge side? So, if bridge detects, that it's no longer mastered, it should kill itself.
—
Reply to this email directly or view it on GitHub.

@baudehlo i did not investigated it deep. But according to docs, this event is not guaranteed, for example on direct process.exit() calls.

Turning the problem around. I like the way you think. That solves the issue that beforeExit may not be called in certain circumstances, and the case of the master process being SIGKILLed. We can still use it to do a close clean when we can. I can take a look at it tomorrow if you wish.
On Sat, Oct 10, 2015 at 12:17 AM, Vitaly Puzrin<EMAIL_ADDRESS>wrote:

I think, we should care about closing phantom instances on process exit. That's important.
Can we use pings or monitor stdin/stdout state at bridge side? So, if bridge detects, that it's no longer mastered, it should kill itself.
Reply to this email directly or view it on GitHub:
https://github.com/baudehlo/node-phantom-simple/issues/81#issuecomment-146998545

@swordofpain That will help. I'd like to participate as minimum as possible - busy with other project. As you can see in history, after 2.0.0 i touch only simple cases and noticeable fuckups.

Alright, I'll keep you posted here. Cheers.

I think I've got something decent. One question though: can I count on the longpoll to perform a request every 500ms to the child process ? Or are there cases when it doesn't happen ? I don't want to perform an extra PING request at regular interval if it's done already.

My bad, it's not the case. We only poll if there's pending work.

See PR #87 for a working implementation.

May I suggest removing the question tag?


Uncaught ReferenceError: module is not defined  while trying to import laravel-echo

I'm submitting a ...

[ ] support request

Provide information & explanation
I started a laravel-echo-server on my server and included laravel-echo into gulpfile.

As what I learned from laravel documentation:
Import Echo from 'laravel-echo'; is all I need to do.
It works fine since I can console.log(Echo) in the browser except there is an "Uncaught ReferenceError: module is not defined" in console.
I looked up the echo.js file and found module.exports = Echo, which cause the error.
Am I doing anything wrong?

Laravel & Angular version: 3.4.0

Hi @cran208
There isn't any module setup in this repository which is why your import statement is not working


Arc-enabled AKSengine cluster

Is your feature request related to a new Jumpstart scenario you would like to contribute?
Yes
Is your feature request related to a problem? Please describe.
No existing scenario covering AKS engine
Describe the solution you'd like
Arc-enabled aks-engine cluster with monitor/defender/policy instructions using Azure CLI
Describe alternatives you've considered
New cluster with kube-admin, but IMHO aksengine is easier for Azure admins
Additional context
Add any other context or screenshots about the feature request here.

Closing due to lack of response


Export structs

exporting the structs makes it easier to work with the package, if you want to mock etc

LGTM, thanks for your contribution.


Can I upload the audio file to server with FormData?

2016-11-02 21:29 I have the answer: Yes, I can.
I used this way upload image success, but upload audio fail, the server has received the audio file, but size is 0, I have no idea, please help!

I used react-native-fileupload upload audio file success, but react-native-fileupload can not run on Android, and it seems that no one to maintain.

I noticed this: https://github.com/jsierles/react-native-audio/issues/97
@RakanNimer said: If you want to upload and download voice files then using react-native-fs would be a great idea.

  uploadAudio = async () => {
    const path = `file://${AudioUtils.DocumentDirectoryPath}/test.aac`
    const formData = new FormData()
    formData.append('file', {
      uri: path,
      name: 'test.aac',
      type: 'audio/aac',
    })
    try {
      const res = await fetch(API_UPLOAD_MSG_FILE, {
        method: 'POST',
        headers: {
          'Content-Type': 'multipart/form-data',
        },
        body: formData,
      })
      const json = await res.json()
    } catch (err) {
      alert(err)
    }
  }

Hi，man
do you fix it？

@Sumrocks Yes, use const path = 'file://' + AudioUtils.DocumentDirectoryPath + 'test.aac'. On Android, you must add file://.

TKS soooooo much !!! it work

Hi there, thanks for this question.
And @zhiquan-yu thanks for your answer. However it is required by the endpoint I am hitting, for me to set 'Content-Type': 'audio/acc'. If I do this, react-native gives me this error:
I tried with 'Content-Type':'multipart/form-data' however my end point returns errors.
This is my code:
    const data = new FormData();
    const ext = 'acc';
    data.append('file', {
        uri:`file://${file_path}`,
        name:`recording.${ext}`,
        type:`audio/${ext}`
    }, `recording.${ext}`);

    const response = await fetch('https://stream.watsonplatform.net/speech-to-text/api/v1/recognize?continuous=true', {
        method: 'POST',
        headers: {
            // 'Content-Type': `audio/${ext}`,
            'Content-Type': 'multipart/form-data',
            'X-Watson-Authorization-Token': token
        },
        body: data
    });

    console.log('watson-stt::getResults - response:', response);

    if (response.status !== 200) {
        const error = await response.text();
        throw new Error(`Got bad response "status" (${response.status}) from Watson Speach to Text server, error: "${error}"`);
    }

+1

_upload = async () => {
let apiUrl = 'http://<IP_ADDRESS>/api_for_solutions/upload_recording';
       const path = 'file://' + AudioUtils.DocumentDirectoryPath + 'test.aac';

        const formData = new FormData();
        formData.append('file', {
            uri: path,
            name: 'test.aac',
            type: 'audio/aac',
        })
        fetch(apiUrl, {
            method: 'POST',
            headers: {
                'Content-Type': 'multipart/form-data',

            },
            body: formData
        }).then(response => {
            console.error(response)
        }).catch(err => {
            console.error(err)
        })

}
#######################
output:-network request failed
plzz solve my error,i am new in react.
thanks in advance

@Biplovkumar copy paste this https://github.com/expo/expo/issues/214#issuecomment-316950941

@gregbenner I have copied you code as well, still I am getting the same network request error.. Is it related to fetch? I mean should I use third party plugin like axios or fetch-blob ?

hey @ShooterArk @Biplovkumar did you find a solution to this?

@SumRocks Yes, use const path = 'file://' + AudioUtils.DocumentDirectoryPath + 'test.aac'. On Android, you must add file://.

not working
any help please


Update vendir to 0.21.1

Vendir 0.21.1 was released yesterday, but homebrew was not updated
Fixes: https://github.com/vmware-tanzu/homebrew-carvel/issues/13

Thanks for the PR @jorgemoralespou!


LiteDatabase.Checkpoint() method causes a deadlock

Version
<IP_ADDRESS>/Windows 7/.NET framework 4.5
Describe the bug
Affter called ILiteCollection.Insert(),calling LiteDatabase.Checkpoint().LiteDatabase.Checkpoint() method causes a deadlock.
Code to Reproduce
var t = 0;
while (true)
{
if (testDb == null) testDb = new LiteDatabase("datas\test.ldb");
for (var i = 0; i < 5; i++)
testDb.GetCollection().Insert(new TestData { Name = "name" + (t++) });
            testDb.Checkpoint();
        }

Screenshots/Stacktrace

@sqlite-me I could not reproduce the issue with the code you provided. Could you provide us more info or perhaps another piece of code that could be used to reproduce the issue?

This is a finished example. I reproduced the problem when I tested it.Let the program run longer, with a certain probability.
Code
class TestData
{
public int Id { get; set; }
public string Name { get; set; }
}
class Program
{
static void Main(string[] args)
{
var testDb = new LiteDatabase("test.ldb");
var count = 0;
while (true)
{
for (var i = 0; i < 5; i++)
{
testDb.GetCollection().Insert(new TestData { Name = "name" + (count++) });
}
testDb.Checkpoint();
            Console.WriteLine(count);
        }

    }
}

in class  "LiteDB.Engine.DiskWriterQueue"
When method Wait() executes to waiter.Set();, and method CreateThread() executes to _while(running).
Next,method Wait() executes to _writing.Wait();, and method CreateThread() executes to waiter.Wait(), both threads may  wait forever.

Hi @sqlite-me, I remove this waits and use a simple task re-creating. Will be avaiable in next minor release

Hi @mbdavid has this bug already been released?

@zandam-xrn Yes, this has been fixed. We forgot to close the issue somehow.


Remap Shortcuts not working properly

Microsoft PowerToys version
0.43.0
Running as admin

[X] Yes

Area(s) with issue?
Keyboard Manager
Steps to reproduce
I use Sharpkeys to exchange L_ctrl and L_alt,
Then use PowerTOys Remap
L_Alt+Tab→L_Ctrl+Tab=All App
L_ctrl + Tab → L_ctrl + L_alt + Tab.
Finally, this hotkey is mapped to the Logi G903 button.
But remap is not working properly, not work from time to time.
✔ Expected Behavior
L_Alt+Tab→L_Ctrl+Tab=All App
L_Ctrl+Tab→L_Ctrl+L_Alt+Tab=All App
❌ Actual Behavior
L_Ctrl+Tab=L_Ctrl+Tab
Other Software
Logitech G Hub 2021.8.792

Hi @mw0225,
I've given it a try and it seems to be working well enough.
Might it be that this is a conflict with SharpKeys?
What happens when you don't use Sharpkeys?
Also regarding the Logitech keyboard button. Does this only fail on the button, or does it fail when you press L_Ctrl+Tab directly as well?

Hi Jaime,
This problem is actually a little complex.
Because even use Sharpkeys to exchange Ctrl with Alt, and written in registry.
However, when setting Logi g hub and Powertoys, the keystroke still keep the original (unswed).
So I set the macro on the mouse button, the Left Tab is Alt + Shit + Tab.
This usually executes Left Tab, but often turning to task switch, and the reason is not clear.
After restarting PowerToys, it will work properly, but use a while back to task switch again.
[https://res.spikenow.com/c/?id=8gojwazws3wshh7c&s=48&m=c&_ts=16seap]           Marcus W - Chat @ Spikehttps://spikenow.com/r/a/?ref=spike-organic-signature&_ts=16seap       [16seap]
On September 1, 2021 at 10:13 GMT, Jaime Bernardo<EMAIL_ADDRESS>wrote:
Hi @mw0225https://github.com/mw0225,
I've given it a try and it seems to be working well enough.
Might it be that this is a conflict with SharpKeys?
What happens when you don't use Sharpkeys?
Also regarding the Logitech keyboard button. Does this only fail on the button, or does it fail when you press L_Ctrl+Tab directly as well?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerToys/issues/12975#issuecomment-910140522, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHSDG6OI42YIB33ITMJGDL3T7X4EPANCNFSM5DFQPB3A.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
[https://bolt.im/t/?pzlSLDGoORJ98VaJuxDC77dxhodJ-L-Pip9_aeYVqgZgX_hAfiQYKW9luSP1Lo-74t0dI2TrRRSdjziA1Ke-iw]

Finally, this hotkey is mapped to the Logi G903 button.

What do you mean by 'this hotkey' here?

Right-click on the PowerToys icon in the tray menu and select Report Bug

Drag and drop report into a GitHub comment.


support metrics integration with prometheus

I believe prometheus metrics has been integrated to the repository from this fork: https://github.com/thomaschangsf/acdc/tree/master

fixed in #37


Grid option

Is there a way to have a grid option with this dnd library?
<Sortable sensitivity={0} key={this.state.data.length} onSort={this.handleSort.bind(this)}>         {items}       </Sortable>

I'm sorry but no feature will be added at this time, I'd recommend you to check out react-dnd.


Feature/issue 35 add redis streams implementation

These changes can be functionally verified with unit test and integration tests with a running Redis server (Version 5+ is needed for Redis Streams functionality). To run integration tests add the redisIntegration tag when executing go test for example:
 $ go test ./... -tags redisIntegration

Addressed code review comments

Please document use of Mockery. None of the other code uses it and there is nothing in the Makefile to regenerate the RedisClient.go file.
Please document the Redis information architecture being used. One of the challenges I've faced in working across the different repos is simply trying to figure out how the pieces come together.
Please add the copyright and license header to the files that are missing it

Please document use of Mockery. None of the other code uses it and there is nothing in the Makefile to regenerate the RedisClient.go file.
Please document the Redis information architecture being used. One of the challenges I've faced in working across the different repos is simply trying to figure out how the pieces come together.
Please add the copyright and license header to the files that are missing it

I will add work on adding this now. Ignore my previous re-request for a review. I will re-request once these issues are addressed.

Addressed code review comments. Ready for re-review

Merging based on Lenny's approval and Andre's LGTM.


Add make rule for running goimports

What happened:
Running make fmt does not address linter formatting concerns.
What you expected to happen:
There should be a make fmt or make goimports rule that brings files to a state where hack/verify-golint.sh will pass.
How to reproduce it (as minimally and precisely as possible):
Alter line spacing on imports then run make fmt; make verify.

Hey @briantkennedy, I couldn't reproduce the issue, I added line spaces on imports in the file cmd/admission/main.go like this
import (
	"context"
	"crypto/tls"
	"errors"

	"flag"
	"fmt"
	"net/http"
	"os"
	"os/signal"
	"sync"

	"syscall"

then after running make verify hack/verify-golint.sh script passed.
Could you please add more details on what is missing here.

/assign

@akankshakumari393 it's been a while since we heard back from you on this one, are you still interested in this one? Do you need any help moving it forward?

I might not be able to work on the issue, feel free to reassign it.👍

Ok thanks for the heads up!


Code snippet for Luminosity in-App Acrylic is wrong

The bug is that the code snippet in Acrylic section for Luminosity In-App Acrylic refers to a resource by a different non-existing name than what it is. Custom resource is created with key CustomAcrylicBrush but the code tries to refer CustomAcrylicInAppLuminosity which doesn't exist.

I think this issue should be closed now since it was fixed with PR #123

Good catch, thanks.


Re-arrange wysiwym code

Re-organise folder structure for wysiwym to make it more meaningful.

What do you suggest?

To start with I want to re-organise files and folders, to a structure like this:
- schema
   -- nodes
   -- marks
- components
   -- menu and related components
- plugins
   -- image
       -- prosemirror-plugin
       -- nodeView
       -- editingModal
   -- table
       -- prosemirror-plugin
       -- nodeView
       -- editingModal
   -- link
       -- prosemirror-plugin
       -- nodeView
       -- editingModal
   -- code-block
       -- prosemirror-plugin
       -- nodeView
       -- editingModal
....

New folder structure I would propose:
- context
    - editorState.tsx
- components
    - Editor
       - index..tsx
       - styles
           - CodeMirror.tsx
           - ProseMirror.tsx
    - Menu
    - InlineMenu
- plugins
    - block
    - inline
    - image
    - link
    - common
    - table
- schema
    - nodes
    - marks
    - index.ts
- Translator

Hey @ncphillips : Above is details of new folder structure I would propose.
On high level intent is we have folders for prosemirror schema, react components, context, etc.
Each prosemirror feature like table, image, inline styles, lists... will be a folder in plugin. It will club its related prosemirror plugin, menu components, commands, etc.
This will make architecture pluggable, adding removing any of these plugins will add remove the feature. We can go ahead to dynamically add plugins to editor like schema.

Looks good to me!


faux::methods bug on recognizing types

Hi! Ive been implementing faux to mock some structs but I'm stuck in an error that i can not work it out. Hope you can help me out with this. The issue is that the compiler is throwing an error due to the return type. The error is below:
the return type refers to the mocked struct in a way that faux cannot handle. Split this function into an impl block not marked by #[faux::methods]. If you believe this is a mistake or it's a case that should be handled by faux please file an issue
Here below is the code. The issue is on Redis::run function but this function doesn't return a type that refers to the mocked struct, it just returns ():
#[cfg_attr(test, faux::create)]
#[derive(Clone)]
pub struct Redis {
    redis_host: String,
    pub pool: Option<Pool>,
}

impl std::fmt::Debug for Redis {
    fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {
        f.debug_struct("Redis")
            .field("redis_host", &self.redis_host)
            .field("pool", &self.pool.is_some())
            .finish()
    }
}

#[cfg_attr(test, faux::methods)]
impl Redis {
    pub fn new(config: &RedisConfig) -> Self {
        Self {
            redis_host: config.host.clone(),
            pool: None,
        }
    }
    async fn stop(&mut self) {
        self.pool.as_mut().unwrap().close()
    }

    async fn run(&mut self) -> Result<(), RedisError> {
        if self.pool.is_none() {
            let url = format!("redis://{}", self.redis_host);
            log::debug!("Redis URL: {}", url);

            match Config::from_url(url).create_pool(Some(Runtime::Tokio1)) {
                Ok(pool) => {
                    self.pool = Some(pool);
                }
                Err(err) => {
                    log::debug!("Error on connecting to redis: {:?}", err);
                    panic!("Unable to connect to redis {:?}", err)
                }
            };

            Ok("".to_string())
        } else {
            log::debug!("Redis Connection is already set.");
            Ok("".to_string())
        }
    }

    async fn get_async_connection(&mut self) -> Option<Connection> {
        match self.pool.as_mut().unwrap().get().await {
            Ok(connection) => Some(connection),
            Err(err) => {
                log::error!("Error getting connection from redis: {:?}", err);
                None
            }
        }
    }
}

That's all, hope you can help me.

Same behavior with an Option<> return type

Great! Thx for the quick response. I've implemented another workaround and combined two methods in one, but your workaround is much better.
I don't close the issue so that you can close it when submitting the fix! Thx again!

@nrxus Any news reagrding the fix?

Fixed in https://github.com/nrxus/faux/commit/6aa254acc217fc73feb19630a47c3f16e1efd824 which I just released as v0.1.10.
Hopefully this addresses the issues but please let me know if something is still wonky.


Visual studio intellisense is not using the specified TS version.

TypeScript Version:  2.1 - 2.6
We work on multiple solutions with different Typescript versions. This means I have Typescript 2.1 and 2.6.1 installed in Visual Studio 2017.
For the project that is using TS 2.1, we selected the correct Typescript version in the project properties.
In the msbuild output, i can see it's using tsc.exe in the Typescript 2.1 directory and that the build succeeded. But We still get TS errors for the Intellisense.
When I set the project to use Typescript 2.6, I get the same errors in both msbuild en Intellisense.
So I think Intellisense is ignoring the selected Typescript version and is always using the latest version installed.
Updating the project to use TS 2.6 is not a solution since it is an older angular 1.3 project. Most of the errors come from the angular 1.3 *.d.ts files.
Expected behavior:
Intellisense uses the version of typescript specified in the project properties. (same as msbuild)
Actual behavior:
Msbuild is using the correct Typescript version specified in the project properties. Intellisense on the other hand is using the latest Typescript version installed.
I'm not sure if this is a Visual Studio issue or Typescript issue, but they advised me to post this here.

What version of VS are you using? 2015 or 2017?

@mhegazy  We are using Visual Studio 2017 with all the latest updates. (Currently version 15.4.5)

we also have the same problem in VS 2017

Any updates?
This is kind of a difficult issue for us, since we have to install/uninstall Typescript 2.6 when we switch solutions.

Exact same problem here. Am using ts 2.1 but the intellisense with VS2017 <IP_ADDRESS> is using ts 2.5

@DieterDS1983 @christianarg
I can think of two reasons
1. Do you have multiple projects open in your solution?
Take a look at the warning here: https://github.com/Microsoft/TypeScript/wiki/Updating-TypeScript-in-Visual-Studio-2017#setting-typescript-versions-in-visual-studio-2017-version-153

Note! If multiple projects are loaded with different TypeScript versions set in the properties page, the latest TypeScript version of all versions specified will take precedence.

Does this sound like what you're seeing?
2. Do you have the tsserver.js for TypeScript 2.1?
Make sure %ProgramFiles(x86)%\Microsoft SDKs\TypeScript\2.1\tsserver.js exists on your disk.
If it doesn't, you might have an out of date version of TS 2.1 (there have been revision updates). Easiest way to ensure you have the latest is to go to your Visual Studio 2017 installer, click Modify, and make sure TypeScript SDK 2.1 is selected under "Individual Components" section.

Strange, I did an update to Visual Studio 15.5.1 yesterday and the problem has disappeared since.
@minestarks :
1. No, my solution has just 1 web project and 18 Class library projects. As far as I know the class library projects should not have any Typescript version in the project file. Also, in this case the ordinary build and intellisense build should both use the wrong version. My ordinary build is using the correct version (2.1), but intellisense is generating errors related to TS 2.6.
2. I have Typescript 2.1, 2.2 and 2.3 installed from the Visual Studio installer and tsserver.js is present.
Typescript 2.6 was downloaded from the typescript website. currently version <IP_ADDRESS>

@DieterDS1983 I think you must have been hitting a known bug in 15.4 that caused non-TypeScript projects to be counted as TypeScript projects, forcing every other project to use the latest version of TypeScript. I'm glad you upgraded and it got fixed now!

Also, in this case the ordinary build and intellisense build should both use the wrong version.

It's a nonissue now, but I'd like to correct this expectation. No, the behavior where the latest TS version is selected when you have multiple projects open, only affects Intellisense. We will always always respect the version you selected for the build, unless we really can't (i.e. it's not installed on the machine).
We should clarify this in the docs.

@minestarks

My solution has only 1 web project and 6 class Libraries
I do have tsserver on the specified path.

@DieterDS1983 what was your VS Version before you updated to 15.5.1. It's weird because in my case the problem STARTED with 15.5.1, before that (15.4.x I didn't have this issue.
Updated to 15.5.2 just now and the problem persist.

@minestarks  Ok, thanks for the explanation. It all makes sense to me now.
I think we can say this is solved for me now.
@christianarg I came from version 15.4.5. But the problems started in 15.3 for me.
Actually as soon as the added the typescript version to the project properties.

@christianarg I've read multiple reports of this problem starting after an upgrade to 15.5, so I think there's something there. Can you confirm your build is fine and this is just Intellisense that doesn't respect the TS version?

@minestarks can confirm, build is fine with, it's just the Intellisense.

@christianarg Thanks. One more question. If you enable the TypeScript/JavaScript Virtual Projects UI by going into Tools->Options->Text Editor->JavaScript/TypeScript->Project->General (shown below)...

...then if you check Solution Explorer, how many virtual projects do you see?

Chances are one of your Class Library projects are being incorrectly detected as a TypeScript project and forcing VS to load a newer version of TS for Intellisense. If this is the case, you may try temporarily removing that project from the solution and seeing if the situation improves.

@minestarks I indeed had multiple virtual projects. although deleting the from the solution had no effect on the issue: I've deleted the projects that also appeared as TS virtual projects; the VS virtual projects dissapeared, but the issue of intellisense using a wrong (newer) version of TSC is still there.
After removing the projects, I've tried close/ open the solution, close / open VS, Clean, Rebuild... still have the issue.

@minestarks Any update on this? am starting to consider Harakiri

After VS2017 upgrade to v15.5.2 I had similar issue. MSBuild was using correct version of TS and Intellisense  wasn't. I tried that what you wrote @minestarks and indeed one of my other website projects (where we don't have any .ts files) was identified as TypeScript project with insane ES6 lib with some Directories without name labels:

When I unloaded that project, intellisense errors disappeared. Is there any better solution for that instead of temporary one? Or we should wait for an update?

@christianarg I hope you're doing well. I'd like to take a closer look at your project because this has me stumped. Would you mind sharing the following with me? You can e-mail me directly if you don't want to post here (e-mail in my profile).
msbuild.exe yourproject.csproj /pp:out.xml
msbuild.exe yourproject.csproj /bl

Collect output files: msbuild.binlog and out.xml

@jgasiorowski I'm glad that workaround helped. That's what I would have suggested.
Would you mind telling me a bit more about the offending project? I found that any of these file types: .js .ts .jsx .tsx .ascx .aspx .cshtml .htm .html .master .vbhtml .vue can cause the project to be pegged as a "JavaScript project" and start forcing the language service to the latest version. Do you have any of these types in that project?
This is somewhat by design --we do want to load the latest language service if there's any JavaScript to be analyzed in the project--, but we're probably being overly aggressive when identifying whether a project contains JavaScript.

@minestarks So that is normal WebApplication project with WebForms in it. So it found the project correctly.
I don't mind that VS will push to use newest standards - the problem is that it caused that TS compiler for intellisense ignored TS version setting in another WebApp project in the same solution (and buried us with 200 errors :) )
to sum up our solution contains:

WebApplication MVC project with Typescript 2.1
WebApplication WebForms without Typescript (pure js only)

I thought that we should be able to use different TS, JS versions in projects which sits in one common solution

@jgasiorowski Unfortunately, that's a limitation we have today... I wish we didn't, but it boils down to these constraints:

We want to use the latest version of the language service for JavaScript, because it tends to contain a lot of bugfixes and perf improvements
We want to respect your TypeScript version if you've set it explicitly
We cannot run two different versions of the TypeScript language service at once. Among other drawbacks, it would use enormous amounts of memory we can't afford. We have to choose one or the other, so we make a judgment call and use the higher version. Note that your build will be unaffected (it will use the version you explicitly set).

Are there major issues preventing you from switching your project over to compile with TypeScript 2.5 or later? The newer compiler errors really do tend to point out legitimate issues. If they don't, we'd like to know.

@minestarks but that was setting was working before just fine. New update bring that new constraints?
I didn't really looked deeply into that 200 errors stack but for now what will prevent us from moving to 2.5 is the time we would need to spend on fixing those ;). Thank you for help!

@jgasiorowski VS 15.5 brought TypeScript 2.5. Earlier versions of VS only had 2.3.
My best guess is that before you upgraded VS, TypeScript 2.3 was being used, but wasn't showing as many compiler errors as 2.5. There were a lot more breaking changes between 2.3 and 2.5 than there were between 2.1 and 2.3.

What's worth it, I had some related issue raised on StackOverflow: https://stackoverflow.com/questions/47928191/how-to-install-typescript-2-2-onto-visual-studio-2017
This was fixed by installing the required SDK through the Visual Studio installer itself instead of a separate download.

@minestarks I'll answer the mail here so it may help other people.
First of all, I should had told you I was using the Typescript nuget package (my bad).
I did what you suggested:
Try adding these two lines to your .csproj:

At the top of your project, right after the  statement that brings in Microsoft.TypeScript.MSBuild.props from the NuGet package, add:

At the bottom of your project, right after the  statement that brings in Microsoft.TypeScript.MSBuild.targets from the NuGet package, add:

And still got the same problem, BUT!! ,now I AM able to do the workarround of unloading the projects that had been incorrectly detected as TS Virtual projects, and finally now it works.
It's still a bit ugly to have to unload those libreries (I actually need them) but I can live with this for a while (we are devs anyway, we were born to suffer xD).
Thanks a lot for the help. I can still provide any assistance you need to fix the issue without needing the workarround


No Data in Grafana Dashboards

Dont see data in Grafana Dashboards after local install.
After local install in dockers I dont see any data in Grafana Dashboards. Message: Tzdata has updated the release from 2019c to 2020a. cursor kept blinking. I can access both Teslamate and Grafana.

How to reproduce it (as minimally and precisely as possible):

Relevant entries from the logs

paste logs here

**Screenshots

**

Data

Environment

TeslaMate version: latest
Docker
OS TeslaMate is installed on: Windows linux docker
User OS & Browser: Chrome
Others:

After driving around / charging the dashboards should be populated. Any changes since this issue was created?


Use string comparison for BUILD_WITH_BORING_SSL_ASM

@jtattermusch @lidizheng
Relates to #24498

Also not that the sanity check is failing (yapf code formatting):
https://source.cloud.google.com/results/invocations/2c0a0875-171c-4b32-bba1-35b38964b206/targets/github%2Fgrpc%2Frun_tests%2Fsanity_linux_dbg_native%2Ftools%2Fdistrib%2Fyapf_code.sh/tests

@jtattermusch I tried to address you comments.  Would you mind taking another look?  Also how can I run lint/formatting locally (I can't seem to find the instructions, which I feel like I had at one point).

Needed to rebase.


Group events into an Observable Sequence

I have a mutation that takes lists of several different DjangoObjectTypes and calls .save() on each of them inside of an atomic transaction. I'm currently Queueing up their event.send() calls inside of transaction.on_commit() so that the subscription events corresponding to the models' on_save() events only kick off if the entire transaction is successful.
My problem now is this:
I want to create a subscription that can send the same payload as what was received in the initial mutation, assuming the mutation commit is successful (as opposed to a single subscription event per change). One way I can see this being done is by keeping my current configuration (one event per django model updated) and the grouping the events that came from the same transaction together with rxpy.
If I could make the events sent inside of a single on_commit become an Observable sequence, I could simply read each sequence of events into the subscription payload. But it seems that currently, each event becomes its own observable, so there's no notion of a "start" and "end" to the sequence of related events. The best I can do is create a buffer that collects different observables together, but this isn't really a viable solution to my problem.
Is it possible to combine multiple django events into an rxpy observable sequence? Or should I be instead creating a custom event, not tied to my django models' .save() but rather tied directly to the mutation (something like putting .on_commit(custom_event(payload)) inside of the .mutate's transaction.atomic block)

To work around this issue, I've created a custom event that takes a dictionary of lists of django models so that I can send a single event on Django Channels that contains the entire change payload. I'm kicking this off from the mutation itself (with the mutation's validated payload) now instead of via .post_save hooks.
Here's an example of that custom event (note, this code doesn't confirm that the objects in the lists are django models):
`class DictListModelSubscriptionEvent(SubscriptionEvent):
def init(self, operation=None, instance=None):
super(DictListModelSubscriptionEvent, self).init(operation, instance)
    if type(self.instance) == str:
        # deserialize django object
        self.instance = self.deserialize_dict()

def to_dict(self):
    _dict = super(DictListModelSubscriptionEvent, self).to_dict()

    _dict["instance"] = self.serialize_dict()

    return _dict

def serialize_dict(self):
    result = {}
    for key in self.instance:
        result[key] = serializers.serialize("json", self.instance[key])
    return json.dumps(result)

def deserialize_dict(self):
    result = {}
    serialized_dict = json.loads(self.instance)
    for key in serialized_dict:
        result[key] = [
            deserialized_object.object
            for deserialized_object in list(
                serializers.deserialize("json", serialized_dict[key])
            )
        ]
    return result`

However, I'd still really appreciate a response to the initial question if ya'll happen to have more insight


Make Add-Type open source files with FileAccess.Read explicitly (#7914)

Fix #7914
Omitting the FileAccess attribute when constructing a FileStream with FileMode.Open makes the constructor default to FileAccess.ReadWrite, which is completely unecessary and inappropriate for Add-Type when compiling from source
PR Summary
This PR ensures that Add-Type explicitly opens source code files with only Read access
PR Checklist

[X] PR has a meaningful title
[X] Summarized changes
[X] Change is not breaking
[X] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[X] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[X] Not Applicable
OR
[ ] User-facing Documentation needed

[ ] Issue filed - Issue link:

Testing - New and feature

[X] Not Applicable or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

@daxian-dbw @iSazonov does is make sense to include a test for this (to avoid another regression in the future?)

Looks like I opened this against @iSazonov fork lol, will re-submit


Support NUnit test properties

Implements https://github.com/nunit/teamcity-event-listener/issues/87

@NikolayPianikov, I came back with a new pull request.
The tricky part was to send the properties from [TestFixture] and [TestCase] attributes. In both cases, the properties were saved inside <test-suite ... event, meaning we have to send the test metadata only when the test suite is finished (it means that all tests inside the suite are finished too, and the corresponding flows are closed). To send the test metadata after the test is finished, I need to send it with the .dll name, so now I have to collect a .dll name for each test as well as the test events inside each test suite to be able to send the service messages to TC when the test suite finishes.
Thank you!


Improve OSX installation and directions.

Add truncate functionality.
Add Socket_timeout to scan options
Prvent issue caused by user logging in ZTS during cluster disruption

Hey, I still have permissions to merge your pull request. Ha.


Request for ADMIN featured application

Hi Arjun,
Is there any plans for admin application for this implementation?
Thanks & Regards,
-Anil Katta

Yes it will be released in near future.
On Dec 9, 2017 2:48 AM, "Anil Kumar Katta"<EMAIL_ADDRESS>wrote:

Hi Arjun,
Is there any plans for admin application for this implementation?
Thanks & Regards,
-Anil Katta
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/arjunsk/ionic-firebase-shopping-cart/issues/8, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJMRqg_DfVGAKYemDJ4nOuwXqdV-qhQ-ks5s-ae_gaJpZM4Q7qK5
.


Camera permission is not requested

Describe the bug
The CAMERA permission is not requested, and thus cannot be granted either. This makes it impossible to scan the Ehrenamtskarte, for example.
To Reproduce
Steps to reproduce the behavior:

Go to 'Ausweisen'
Click on 'Jetzt Aktivierungscode einscannen'
See the camera view open
Window stays black, no camera.

Expected behavior
Camera view is shown so the card can be scanned (question remains what the activation code is; I do not remember having received any with my card).
Screenshots
From a black screen? :wink:
Desktop (please complete the following information):

OS: [e.g. iOS] n/a
Browser [e.g. chrome, safari] n/a
Version [e.g. 22] n/a

Smartphone (please complete the following information):

Device: Fairphone 2
OS: Android 10 (LineageOS)
Browser n/a
Version 2.0.2

Additional context
None so far.

Thanks for opening this bug. Right now this is intentional, because we do not yet have build flavors.
The currently released version in the Play Store should not have this permission.
We can use this issue to re-add the camera permission as soon as we have build flavors.

I see. But if that's intentional, shouldn't that tab be hidden entirely? It's a bit confusing if I'm asked to scan a code and there's no camera to do it :wink:

Closing because it will be fixed by  #524.

Afaik, this is not done yet although the linked issue is closed. Let's put this as a technical task.

Yes we basically need to enable the camera permission based on the build config

Closing as soon all flavors of this app will have the camera perm. enabled.


[Pure K8S] API compatiblity

To ensure that pai's web portal and clients (vscode, sdk) will work on both YARN based and pure K8S based backend, we need to check the compatibility of current used APIs and implement some new Rest API wrappers for operations based on YARN or HDFS.
New API requests

[x] PAI's info API

[x] Current version
[ ] Endpoints
[x] Auth method
[x] Launcher type
[ ] Driver version

[x] Job's stdout / stderr / system log API wrapper
[ ] Storage API wrapper (HDFS / NFS)

Compatibility

[ ] Prometheus

[x] [Home] Job's gpu usage (abnormal jobs)
[x] [Admin - Hardware] hardware utilization queries
[x] Alert manager
[ ] Home page's yarn_node_gpu_available query

[x] Grafana

[x] [Dashboard] Dashboard
[x] [Job Detail] Job level metrics
[x] [Admin - Hardware] Hardware utilization grafana chart

[x] K8S API

[x] [Admin - Service] Pod status
[x] [Job Submission] Storage config

[ ] Exporter API
[ ] Rest API

[ ] User, Group

[x] [Home, Job Submission] Get user info
[x] [Job List] List users
[ ] 🕒 User management
[ ] 🕒 Group management

[ ] Virtual Cluster

[x] [Home, Job List] List virtual clusters

[x] [Home] Wrong total resources

[x] [Home] List node resources
[x] 🔧 [Admin - Virtual Cluster] Virtual clusters management #3574

[ ] Auth

[ ] 🕒 basic
[x] OIDC

[x] login
[x] logout

[ ] Job

[x] [Home, Job List] list jobs

[ ] [Home] list specific user's job (username query)

[x] [Job Submission] Submit v2 job

[ ] ❓ Can not submit a cpu only job

[x] [Home, Job Detail, Job List] Stop job
[x] [Job Detail] Get job info
[x] [Job Submission, Job Detail] Get job config
[ ] ❓ [Job Detail] Get job ssh info
[ ] v1 compatibility

[ ] ❗ [Job Clone, Extension] Submit v1 job

[ ] ❗ Exit diagnostics

[ ] Misc

[x] [Job Detail] stdout/stderr log

[ ] ❗ Mixed content issue

[x] 🔧 [Job Detail] Job attempts page link #3574
[x] 🔧 [Job Detail] Application tracking page #3574
[x] 🔧 [Admin - Virtual Cluster] Virtual cluster status link #3574

closed.


Reservoir constraints & "nil" syntax element

[x] reservoir constraints
[ ] "nil" syntax element

Once ready, this PR closes #14.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 95.65217% with 2 lines in your changes missing coverage. Please review.

Project coverage is 99.12%. Comparing base (ae4fb98) to head (3d096ea).

Files
Patch %
Lines

massaction/constraint.py
86.66%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##              main      #17      +/-   ##
===========================================
- Coverage   100.00%   99.12%   -0.88%
===========================================
  Files            5        5
  Lines          196      229      +33
===========================================
+ Hits           196      227      +31
- Misses           0        2       +2

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


Add prop-types peer dependency to remove deprecation warnings

This change removes deprecation warnings when running in a non-production environment with React 15.5

Hi, thank you for your input! I believe that peerDependencies is deprecated now and prop-types should just land in dependencies.
Also I'm worried how that would work for folks on React versions older than 15.5. I think we should fix that for React 16 release, bumping minimal React version required to 15.5... Although I'd still wait for the community to adapt to still fresh updates.
What's your stand?

Ah, I wasn't aware of the peerDependencies deprecation. I could update that to use dependencies.
I just tested using React 15 and double checked the documentation for the new PropTypes, and users on React >=15.0 and <15.3 will see a worse error message than 15.5 users see right now. So you're probably right to hold off on this change until at least bumping the minimum React version.
Thanks for looking at this!

Hey,
once again thank you for your input. Development is now planned and React-PDF will require React 15.5+ from version 1.7.