Allow the embedding of charts on other websites

Chart embedding [New Feature] 💅
This will entail that CB will have separate pages for each chart that can be used to embed them in <iframe/>. So basically, chartbrew.com/chart/6546/embed can be embedded into another site with <iframe src="above_url"></iframe>.
The API can serve this data if the chart is public, so that will need to be specific in the front-end.
Getting the embedded code can be done through the menu of each of the charts on the dashboard.

[x] New API route to get the data for embedding
[x] Front-end changes - new embedded page and menu option

This seems to be done now. Needs some testing before merging.


hyprexpo: Invalid dispatcher, requested "hyprexpo:expo" does not exist

hyprpm list shows that the plugin is loaded.
Hyprland version: 0.41.0

hyprctl plugin list says no plugins are loaded.

then hyprexpo failed to load

It is now fixed (for some reason)


test: unify how --entrypoint= is used

The usage of --entrypoint was a bit all over the place. This commit unifies it so that if the entrypoint is not "build" we always pass --entrypoint=/usr/bin/bootc-image-builder and the the arguments to bib are passed after the container.
This makes test (hopefully) more readable.

https://github.com/osbuild/bootc-image-builder/actions/runs/9790396974/job/27031918742?pr=513#step:12:113

:thinking:

https://github.com/osbuild/bootc-image-builder/actions/runs/9790396974/job/27031918742?pr=513#step:12:113
>       with pytest.raises(subprocess.CalledProcessError) as exc:
E       Failed: DID NOT RAISE <class 'subprocess.CalledProcessError'>

test/test_manifest.py:324: Failed

🤔

A silly copy/paste mistake, I fixed that now and double checked the others, should be okay now.


Passage / Frame Additions

The Passage and Frame classes need some reworking to ensure we can do everything we want to do with them. Right now it is not clear how multiple instruments might be implemented, nor is it clear how Passages might be overlaid, excerpted, etc. etc.

Putting this on hold for a little while.


Missing Docs for releases after 0.12

Check CONTRIBUTING guideline first and here is the list to help us investigate the problem.
Describe the bug
The documentation for all releases after 0.12 are missing from https://docs.fluentd.org/.
To Reproduce
Go to https://docs.fluentd.org/, click on 1.0, see only the introduction, no other docs.
Expected behavior
Go to the site and see all docs.


HBASE-26969:Eliminate MOB renames when SFT is enabled

Get rid of renames in the MOB compaction and flush.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
2m 31s
master passed

+1 :green_heart:
compile
2m 20s
master passed

+1 :green_heart:
checkstyle
0m 30s
master passed

-1 :x:
spotless
0m 35s
branch has 22 errors when running spotless:check, run spotless:apply to fix.

+1 :green_heart:
spotbugs
1m 17s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m  8s
the patch passed

+1 :green_heart:
compile
2m 17s
the patch passed

+1 :green_heart:
javac
2m 17s
the patch passed

-0 :warning:
checkstyle
0m 28s
hbase-server: The patch generated 13 new + 19 unchanged - 0 fixed = 32 total (was 19)

-0 :warning:
whitespace
0m  0s
The patch has 1 line(s) that end in whitespace. Use git apply --whitespace=fix <<patch_file>>.

The reported test failures seems unrelated.


"Splicer EU" should be labeled "EU SPC"

"Splicer EU" should be labeled "EU SPC" - the current name confuses users because SPLICER can only be ran on US labeling.

done!


Vulkan: StandardMaterial3D with refraction is opaque and doesn't refract anything

Godot version: Git 89a43d9c2
OS/device including version: Fedora 33, GeForce GTX 1080 (NVIDIA 460.39)
Issue description:
StandardMaterial3D with Refraction enabled is opaque and doesn't refract anything:

It's still considered transparent by the graphics pipeline, which means it won't cast shadows and will have transparency sorting issues with gizmos.
Steps to reproduce: Add a StandardMaterial3D, decrease the alpha component in the Albedo color, enable Refraction and set a normal map texture in the refraction texture slot.
Minimal reproduction project: test_refraction.zip

I can't reproduce this anymore as of https://github.com/godotengine/godot/commit/efc87481e45c66b3a18dfe1db82c3289fe2a370d, closing.


[Bug]: Pylance type error in Python samples

Language
Python
Version
latest
Description
Pylance will report following error in Python samples. May need to fix the error as user will see the errors when try the samples.
Mypy does not report the error after test.

"Application" is not exported from module "teams" Import from "teams.app" instead
"ApplicationOptions" is not exported from module "teams" Import from "teams.app_options" instead

Reproduction Steps
N/A

Hey @blackchoey, is this in the samples or in our SDK logic?

@lilyydu I remember this is resolved after one of Alex's PR. Will close this one. Thank you!


Added Rackspace & ETH Polymesse event demos

Description
Updated community.md with the 2 events which I will be presenting the faas project.

LGTM


Add nn.hlu (hyperbolic linear unit)

Add the hyperbolic linear unit (HLU) activation function, as described in Hyperbolic linear units for deep convolutional neural networks. It resembles ELU, but requires only elementary arithmetic operations, and is therefore faster:
import timeit

import jax
from jax import lax, nn, numpy as jnp, random

def hlu(x):
    # Naive version:
    # return jnp.where(x > 0, x, x / (1 - x))
    # Fixing nan gradient at x = 1:
    return x / jnp.maximum(1 - x, 1)

def main():
    key = random.PRNGKey(0)
    x = random.normal(key, [10**7])

    for f in [nn.elu, hlu]:

        def g(x, _):
            return f(x), None

        start = timeit.default_timer()
        jax.block_until_ready(lax.scan(g, x, None, length=10**3))
        end = timeit.default_timer()
        print(end - start)

if __name__ == "__main__":
    main()

6.881290550008998
1.9667128750006668

I can submit a PR.

Hi - thanks for the request. We don't have a hard-and-fast policy about what activation functions to include in jax.nn, but we lean toward being conservative about what we include: each new API entrypoint adds a small ongoing maintenance burden to the JAX package, and if the new activation can be implemented in a handful of lines, it's probably clearer for users to define it themselves.
We do include some well-known activations in the module, but I don't think HLU would qualify (it looks like the paper only has about 10 citations: https://scholar.google.com/scholar?cites=12756044201569621807).


question: how to dynamically show/hide items in Sidebar

Hi,
When asking general "how to" questions:
- Please do not open an issue here

Where should one ask instead?
Question is, how to make each Sidebar item here
https://github.com/coreui/coreui-free-vue-admin-template/blob/0d2b619677ba170898ec19ae9ad0a99db22b5d51/src/containers/_nav.js
be shown only if a condition is met, depending on Vue store?
Use case: show an item only if user permissions allow access to that item.
eg
 {
        _name: 'CSidebarNavItem',
        name: 'Colors',
        to: '/theme/colors',
        icon: 'cil-drop',
        showIf: "store.user.permissions.includes('Colors')"
      },

For store to work, how should it be declared in this file?
Thanks!

Where should one ask instead?

Documentation is answering 'how-to' questions. If documentation is not sufficient, the issue is about a lack of documentation.
CRenderFunction docs:
https://coreui.io/vue/docs/components/render-function.html
Backend integration docs:
https://coreui.io/vue/docs/introduction/template.html#backend-integration
Generally in your case, you have access to store only in Vue components. So the best way is to compute your items as shown in the 'backend integration' section based on your store state.


can also not run with history at all

https://github.com/ldoge/LDOGE/wiki/LiteDoge-full-node-copy-paste-installation-guide#clear-history
for bash in particular, this can be achieved at the beginning, not only at the end
https://www.gnu.org/software/bash/manual/bash.html#index-HISTFILE
used like:
$ HISTFILE=/dev/null bash
$ _

added the command thank you i checked out the website

you killed the format dude

how DId I kill the format?

you copy pasted the lines before your
cat /dev/null > ~/.bash_history ...
instead of after it,
and the preformatted block turned normal text
killing the line break between "$ HISTFILE=/dev/null bash" and "$ _"
On Sat, Jan 8, 2022 at 12:54 PM Shawn M. @.***> wrote:

how DId I kill the format?
—
Reply to this email directly, view it on GitHub
https://github.com/ldoge/LDOGE/issues/35#issuecomment-1007969653, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AMRS4W47ZEFOHWT5DGZEEVTUVAQY3ANCNFSM5C7SJ27Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

used like $ HISTFILE=/dev/null
that makes bash stop recording new history
history -c
that erases any previous history


Make it possible to score on Table_Clean

Currently there are no goals setup on Table_Clean.

I'd found it super valuable like this for testing (hadn't taken any goals out - I just don't think we ever put any in). That said, if people want this table to be a functional table, I don't think that that should stand in the way.
It's worth noting that Table_Clean (currently named "Empty") is no longer the default/first item in the level list, so its prominence is much lower than it has previously been.


DataTable - Add a new (form) action button

• It’s easy to add a new action buttun
    ◦ Just add it in the file : resources/views/your_models/datatables_actions.blade.php

• The only problem is if you add a new « form button » like the « Delete one » the new button will not be aligned with the 3 previous ones.

To align it your have to add the style « display: inline; » and to do this you have to modify the file :
    ◦ vendor/laravelcollective/html/src/FormBuilder.php
        ▪ protected $reserved = ['method', 'url', 'route', 'action', 'files', 'style'];
        ▪ and in open function
            • $attributes['style'] = $options['style'] ?? '';

@Dri372 can you share some screenshots of before style and after style?

Hi @mitulgolakiya
Of course, thanks for your package.
Before

After

@Dri372 as long as I know, the generator is not adding that button, I think that button is manually added by you. I will say, instead of modifying  vendor/laravelcollective/html/src/FormBuilder.php, either you should fix it by writing some global css or you can publish the laravel generator stub files and then do modification there.


Check for updates

Check GitHub release for updated binaries and prompt the users about the newer version

This already happens, actually. See here: https://github.com/matt1484/bl3_auto_vip/blob/master/cmd/main.go#L272

It’s not exactly the best way to check. I plan on changing it a bit at some point

This would actually be a really simple change:

GET JSON from https://api.github.com/repos/matt1484/bl3_auto_vip/releases/latest
Compare .tag_name to your version constant

You'd just need to make sure that your version constant matches your tag name.


'black' linter

The code currently is written with somewhat weird tabbing/ missing of string concating, ' instead of ", may I recommend using black to just look more readable?
Here is a PR that will show you the difference (I just ran 'black' on the root folder)
https://github.com/hansmach1ne/LFImap/pull/53

Another thing worth working on is f-string from this:
print(
                    "\n"
                    + colors.lightblue("[i]")
                    + " Parsing URL ["
                    + str(iteration + 1)
                    + "/"
                    + str(len(config.parsedUrls))
                    + "]: '"
                    + url
                    + "'"
                )

To:
print(f"\n{colors.lightblue('[i]')} Parsing URL [{str(iteration + 1)}/{str(len(config.parsedUrls))}]: '{url}'")

https://github.com/hansmach1ne/LFImap/commit/98d3d974f062a11a715f7c7556ed84533e6600a7


Python (standard library) implementation of update pileup object script

Fixes https://github.com/dmwm/WMCore/issues/11867
Status
ready
Description
A new replacement of Alan's WMCore/pycurl based Python script introduced in https://github.com/dmwm/WMCore/pull/11868
This script is based on Python standard library and does not require any third party or WMCore dependencies. It uses the MSPileup REST API to fetch all of the pileup documents, update each of them with data provided via a JSON file, then update those documents back in MSPileup (through a PUT http call).
Is it backward compatible (if not, which system it affects?)
YES
Related PRs
https://github.com/dmwm/WMCore/pull/11868
External dependencies / deployment changes

Alan, I made an additional change to properly encode passed json data, please review last commit https://github.com/dmwm/WMCore/pull/11872/commits/f846361f4b34056ad3a4e7de980c2377eea9768d
All other commits are squashed. And, with my last fix I was able to update testbed docs. For that I used the following document located at /tmp/update.json
{"lastUpdateTime":<PHONE_NUMBER>}

and I call the script as following:
bin/adhoc-scripts/updatePileupObjects.py --fin=/tmp/update.json --url https://cmsweb-testbed.cern.ch

I inspected the logger output and it dumped that all documents were updated. I fetched new docs from testbed via curl call to https://cmsweb-testbed.cern.ch/ms-pileup/data/pileup and saw that all lastUpdateTime values were updated. Doing this I didn't modified any other fields in docs and only triggered update whose update time was set by MSPileyp code.
Said that, I can squash last commit after your additional review. It was required since otherwise we were passing dict objects rather the actual json. It it caused http error which I posted in this gist.
Moreover, I realized that this script can be used used ONLY for static change applied to all documents. In other words, if we want to add transition records this script will not be helpful as transition record need a customName equal to pileup name according to your gist section 2. In order to use this script we'll need to add additional code to read record, take its pileup name, and create transition record with it.

Looks good to me. Please squash the last 2 commits into a single one.
For the transition record, we can update this script once it becomes necessary. Potentially we don't even need to push upstream the transition logic.

squashing is done

Thanks Valentin.


Update old version links

Hi all,
please update always the version links like changelog and the link to the software in the readme.
Otherwise it is just wasted time for others to look into it..
Thanks, Best
Klim
edit: Pls update the FAQ section as well. There is no use in having the old SSH things in there if they are not working...

thanks, good catch!


[Icon Suggestion] Percent icon

As an indicator of sales

➡ https://github.com/tailwindlabs/heroicons/issues/173


LZ4 decoding is not working over hadoop

Hello , we just tried latest apache-arrow version 3.0.0 and the write example included in low level api example, but lz4 still seems not compatible with Hadoop . we got this error reading over hadoop file parquet produced with 3.0.0 library  :
[leal@sulu parquet]$ ./hadoop-3.2.2/bin/hadoop jar apache-parquet-1.11.1/parquet-tools/target/parquet-tools-1.11.1.jar head --debug parquet_2_0_example2.parquet
2021-02-04 21:24:36,354 INFO hadoop.InternalParquetRecordReader: RecordReader initialized will read a total of 1500001 records.
2021-02-04 21:24:36,355 INFO hadoop.InternalParquetRecordReader: at row 0. reading next block
2021-02-04 21:24:36,397 INFO compress.CodecPool: Got brand-new decompressor [.lz4]
2021-02-04 21:24:36,410 INFO hadoop.InternalParquetRecordReader: block read in memory in 55 ms. row count = 434436
org.apache.parquet.io.ParquetDecodingException: Can not read value at 0 in block -1 in file [file:/home/leal/parquet/parquet_2_0_example2.parquet|file://home/leal/parquet/parquet_2_0_example2.parquet]
at org.apache.parquet.hadoop.InternalParquetRecordReader.nextKeyValue(InternalParquetRecordReader.java:255)
at org.apache.parquet.hadoop.ParquetReader.read(ParquetReader.java:132)
at org.apache.parquet.hadoop.ParquetReader.read(ParquetReader.java:136)
at org.apache.parquet.tools.command.HeadCommand.execute(HeadCommand.java:87)
at org.apache.parquet.tools.Main.main(Main.java:223)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.hadoop.util.RunJar.run(RunJar.java:323)
at org.apache.hadoop.util.RunJar.main(RunJar.java:236)
Caused by: java.lang.IllegalArgumentException
at java.nio.Buffer.limit(Buffer.java:275)
at org.apache.hadoop.io.compress.lz4.Lz4Decompressor.decompress(Lz4Decompressor.java:232)
at org.apache.hadoop.io.compress.BlockDecompressorStream.decompress(BlockDecompressorStream.java:88)
at org.apache.hadoop.io.compress.DecompressorStream.read(DecompressorStream.java:105)
at java.io.DataInputStream.readFully(DataInputStream.java:195)

any advice ? we need to write Lz4 files by C++ and read oover Hadoop jobs but still stuck on this problem .
Reporter: mario luzi
Related issues:

Support LZ4_RAW codec (is related to)

Original Issue Attachments:

parquet_3_0_example2.parquet

Note: This issue was originally created as PARQUET-1974. Please see the migration documentation for further details.

mario luzi:
@pitrou  attached file produced with 3.0.0 parquet-cpp version ...

Antoine Pitrou / @pitrou:
@gszadovszky The status is that the Parquet-C++ developers did all they could to try and achieve compatibility.
Now it's up to parquet-mr to pick up the ball. [~mario.luzi] Can you post the Parquet file so that they can take a look?
If there is no resolution on the Java side I will ask for LZ4 to be dropped from the Parquet spec. Right now Parquet is partly a proprietary standard due to under-specification.

Gabor Szadovszky / @gszadovszky:
I'm afraid I've lost track of this LZ4 compatibility issue. I can see a couple of resolved (e.g. ARROW-9177, PARQUET-1878) and a couple of still open (e.g. PARQUET-1241, PARQUET-1515) issues. All are for parquet-cpp/arrow. This is the first one for created for parquet-mr.
@wesm, @pitrou, what is the status of LZ4 compatibility between parquet-cpp and parquet-mr? There were discussions to extend parquet-format to properly specify LZ4 and maybe to add another compression option for framed LZ4. I did not find any jiras about these. I am also not sure about the parquet-mr LZ4 implementation if it is considered correct or we want to update something in that side as well.


Revisit Auth types expansion / Mapping types from Factory to Construct

Description
See the discussion here: https://github.com/aws-amplify/amplify-backend/pull/638#discussion_r1391807879
We should revisit ways in which to reduce type algebra in our Types for non-IDE users.
There are concerns that type algebra may confuse users, and we should check if customers provide feedback about this.
see https://github.com/aws-amplify/amplify-backend/pull/638

Closing this because we have not had any customer complaints around this subject.


Can't type special characters into TextInput

In kivy version 1.9.0 (latest stable), when I type a special character that requires two keystrokes in a standard TextInput, for example, á (´ then 'a'), the result is ´a instead of the proper á. The same happens to all characters that requires two keystrokes like é í ö ü.
Also, normally the accent keys can also work alternatively as a modifier key, so you can either hold ´ and type 'a' or you can type ´, release it, and type 'a' (the classical/standard way).
I don't really need that atm because my app is for mobile and mobile on-screen keyboards works differently (hopefully properly), but it is surely something worth mentioning, specially because physical keyboards for mobile also have the two-keystroke combination for some locales.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/22883799-can-t-type-special-characters-into-textinput?utm_campaign=plugin&utm_content=tracker%2F42681&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F42681&utm_medium=issues&utm_source=github).

Hey guys, any update on this? Can you at least confirm it?

Seems like it might be related to this SDL2 bug:
https://hg.libsdl.org/SDL/rev/02273530b7bf
Someone will need to compile the SDL2 dev source, or wait for the next release, and test it using one of these keymaps.

@kived: I can test it, just lemme know when it's ready. I don't actually need that atm so I'm not in a hurry, and it's no big deal because if someone really needs that it's just a matter of using a newer SDL2 which has the fix. Should be easy enough imho.
Perhaps you could let this issue open so I'll receive an email notification when the updated version is ready. I'm also on the IRC channel (nick 9-9) sometimes. I'm pretty sure the update will fix the problem though.
Thank you.


[vite] Internal server error: Cannot read property 'length' of null

Describe the bug
使用 Vite 构建Vue 项目，安装好依赖，运行 npm run dev 报相关错误  [vite] Internal server error: Cannot read property 'length' of null
System Info

vite version: 2.0.0-beta.52
Operating System:win10
Node version: 14.8.0
Package manager (npm/yarn/pnpm) and version:npm  6.14.7

Logs (Optional if provided reproduction)

@ailaiwuyou  I tried vite in your same environment and it performed well.
  ⚡Vite dev server running at:

  > Network:  http://<IP_ADDRESS>:3000/
  > Local:    http://localhost:3000/

  ready in 532ms.

^C^C
86166@DESKTOP-Q5AFI5E MINGW64 /c/web/lessons (main)
$ vue info

Environment Info:

  System:
    OS: Windows 10 10.0.18363
    CPU: (8) x64 Intel(R) Core(TM) i5-1035G4 CPU @ 1.10GHz
  Binaries:
    Node: 14.8.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.7 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Not Found
  npmPackages:
    @vitejs/plugin-vue: ^1.0.4 => 1.1.0
    @vue/compiler-core:  3.0.5
    @vue/compiler-dom:  3.0.5
    @vue/compiler-sfc: ^3.0.5 => 3.0.5
    @vue/compiler-ssr:  3.0.5
    @vue/reactivity:  3.0.5
    @vue/runtime-core:  3.0.5
    @vue/runtime-dom:  3.0.5
    @vue/shared:  3.0.5
    vue: ^3.0.5 => 3.0.5
    vue-router: ^4.0.3 => 4.0.3
    vue3-markdown-it: ^1.0.7 => 1.0.7
    vuex: ^4.0.0-rc.2 => 4.0.0-rc.2
  npmGlobalPackages:
    @vue/cli: Not Found

it seems like a problem occured in your code that caused vite hmr failed.

@ailaiwuyou  I tried vite in your same environment and it performed well.
  ⚡Vite dev server running at:

  > Network:  http://<IP_ADDRESS>:3000/
  > Local:    http://localhost:3000/

  ready in 532ms.

^C^C
86166@DESKTOP-Q5AFI5E MINGW64 /c/web/lessons (main)
$ vue info

Environment Info:

  System:
    OS: Windows 10 10.0.18363
    CPU: (8) x64 Intel(R) Core(TM) i5-1035G4 CPU @ 1.10GHz
  Binaries:
    Node: 14.8.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.7 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Not Found
  npmPackages:
    @vitejs/plugin-vue: ^1.0.4 => 1.1.0
    @vue/compiler-core:  3.0.5
    @vue/compiler-dom:  3.0.5
    @vue/compiler-sfc: ^3.0.5 => 3.0.5
    @vue/compiler-ssr:  3.0.5
    @vue/reactivity:  3.0.5
    @vue/runtime-core:  3.0.5
    @vue/runtime-dom:  3.0.5
    @vue/shared:  3.0.5
    vue: ^3.0.5 => 3.0.5
    vue-router: ^4.0.3 => 4.0.3
    vue3-markdown-it: ^1.0.7 => 1.0.7
    vuex: ^4.0.0-rc.2 => 4.0.0-rc.2
  npmGlobalPackages:
    @vue/cli: Not Found

it seems like a problem occured in your code that caused vite hmr failed.

@ailaiwuyou  I tried vite in your same environment and it performed well.
  ⚡Vite dev server running at:

  > Network:  http://<IP_ADDRESS>:3000/
  > Local:    http://localhost:3000/

  ready in 532ms.

^C^C
86166@DESKTOP-Q5AFI5E MINGW64 /c/web/lessons (main)
$ vue info

Environment Info:

  System:
    OS: Windows 10 10.0.18363
    CPU: (8) x64 Intel(R) Core(TM) i5-1035G4 CPU @ 1.10GHz
  Binaries:
    Node: 14.8.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.7 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Not Found
  npmPackages:
    @vitejs/plugin-vue: ^1.0.4 => 1.1.0
    @vue/compiler-core:  3.0.5
    @vue/compiler-dom:  3.0.5
    @vue/compiler-sfc: ^3.0.5 => 3.0.5
    @vue/compiler-ssr:  3.0.5
    @vue/reactivity:  3.0.5
    @vue/runtime-core:  3.0.5
    @vue/runtime-dom:  3.0.5
    @vue/shared:  3.0.5
    vue: ^3.0.5 => 3.0.5
    vue-router: ^4.0.3 => 4.0.3
    vue3-markdown-it: ^1.0.7 => 1.0.7
    vuex: ^4.0.0-rc.2 => 4.0.0-rc.2
  npmGlobalPackages:
    @vue/cli: Not Found

it seems like a problem occured in your code that caused vite hmr failed.

@ailaiwuyou  I tried vite in your same environment and it performed well.
  ⚡Vite dev server running at:

  > Network:  http://<IP_ADDRESS>:3000/
  > Local:    http://localhost:3000/

  ready in 532ms.

^C^C
86166@DESKTOP-Q5AFI5E MINGW64 /c/web/lessons (main)
$ vue info

Environment Info:

  System:
    OS: Windows 10 10.0.18363
    CPU: (8) x64 Intel(R) Core(TM) i5-1035G4 CPU @ 1.10GHz
  Binaries:
    Node: 14.8.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.7 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Not Found
  npmPackages:
    @vitejs/plugin-vue: ^1.0.4 => 1.1.0
    @vue/compiler-core:  3.0.5
    @vue/compiler-dom:  3.0.5
    @vue/compiler-sfc: ^3.0.5 => 3.0.5
    @vue/compiler-ssr:  3.0.5
    @vue/reactivity:  3.0.5
    @vue/runtime-core:  3.0.5
    @vue/runtime-dom:  3.0.5
    @vue/shared:  3.0.5
    vue: ^3.0.5 => 3.0.5
    vue-router: ^4.0.3 => 4.0.3
    vue3-markdown-it: ^1.0.7 => 1.0.7
    vuex: ^4.0.0-rc.2 => 4.0.0-rc.2
  npmGlobalPackages:
    @vue/cli: Not Found

it seems like a problem occured in your code that caused vite hmr failed.

I will

@ailaiwuyou I tried vite in your same environment and it performed well.
  ⚡Vite dev server running at:

  > Network:  http://<IP_ADDRESS>:3000/
  > Local:    http://localhost:3000/

  ready in 532ms.

^C^C
86166@DESKTOP-Q5AFI5E MINGW64 /c/web/lessons (main)
$ vue info

Environment Info:

  System:
    OS: Windows 10 10.0.18363
    CPU: (8) x64 Intel(R) Core(TM) i5-1035G4 CPU @ 1.10GHz
  Binaries:
    Node: 14.8.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.7 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Not Found
  npmPackages:
    @vitejs/plugin-vue: ^1.0.4 => 1.1.0
    @vue/compiler-core:  3.0.5
    @vue/compiler-dom:  3.0.5
    @vue/compiler-sfc: ^3.0.5 => 3.0.5
    @vue/compiler-ssr:  3.0.5
    @vue/reactivity:  3.0.5
    @vue/runtime-core:  3.0.5
    @vue/runtime-dom:  3.0.5
    @vue/shared:  3.0.5
    vue: ^3.0.5 => 3.0.5
    vue-router: ^4.0.3 => 4.0.3
    vue3-markdown-it: ^1.0.7 => 1.0.7
    vuex: ^4.0.0-rc.2 => 4.0.0-rc.2
  npmGlobalPackages:
    @vue/cli: Not Found

it seems like a problem occured in your code that caused vite hmr failed.

@ailaiwuyou I tried vite in your same environment and it performed well.
  ⚡Vite dev server running at:

  > Network:  http://<IP_ADDRESS>:3000/
  > Local:    http://localhost:3000/

  ready in 532ms.

^C^C
86166@DESKTOP-Q5AFI5E MINGW64 /c/web/lessons (main)
$ vue info

Environment Info:

  System:
    OS: Windows 10 10.0.18363
    CPU: (8) x64 Intel(R) Core(TM) i5-1035G4 CPU @ 1.10GHz
  Binaries:
    Node: 14.8.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.7 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Not Found
  npmPackages:
    @vitejs/plugin-vue: ^1.0.4 => 1.1.0
    @vue/compiler-core:  3.0.5
    @vue/compiler-dom:  3.0.5
    @vue/compiler-sfc: ^3.0.5 => 3.0.5
    @vue/compiler-ssr:  3.0.5
    @vue/reactivity:  3.0.5
    @vue/runtime-core:  3.0.5
    @vue/runtime-dom:  3.0.5
    @vue/shared:  3.0.5
    vue: ^3.0.5 => 3.0.5
    vue-router: ^4.0.3 => 4.0.3
    vue3-markdown-it: ^1.0.7 => 1.0.7
    vuex: ^4.0.0-rc.2 => 4.0.0-rc.2
  npmGlobalPackages:
    @vue/cli: Not Found

it seems like a problem occured in your code that caused vite hmr failed.

I will try again

I will

@ailaiwuyou I tried vite in your same environment and it performed well.
  ⚡Vite dev server running at:

  > Network:  http://<IP_ADDRESS>:3000/
  > Local:    http://localhost:3000/

  ready in 532ms.

^C^C
86166@DESKTOP-Q5AFI5E MINGW64 /c/web/lessons (main)
$ vue info

Environment Info:

  System:
    OS: Windows 10 10.0.18363
    CPU: (8) x64 Intel(R) Core(TM) i5-1035G4 CPU @ 1.10GHz
  Binaries:
    Node: 14.8.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.7 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Not Found
  npmPackages:
    @vitejs/plugin-vue: ^1.0.4 => 1.1.0
    @vue/compiler-core:  3.0.5
    @vue/compiler-dom:  3.0.5
    @vue/compiler-sfc: ^3.0.5 => 3.0.5
    @vue/compiler-ssr:  3.0.5
    @vue/reactivity:  3.0.5
    @vue/runtime-core:  3.0.5
    @vue/runtime-dom:  3.0.5
    @vue/shared:  3.0.5
    vue: ^3.0.5 => 3.0.5
    vue-router: ^4.0.3 => 4.0.3
    vue3-markdown-it: ^1.0.7 => 1.0.7
    vuex: ^4.0.0-rc.2 => 4.0.0-rc.2
  npmGlobalPackages:
    @vue/cli: Not Found

it seems like a problem occured in your code that caused vite hmr failed.

@ailaiwuyou I tried vite in your same environment and it performed well.
  ⚡Vite dev server running at:

  > Network:  http://<IP_ADDRESS>:3000/
  > Local:    http://localhost:3000/

  ready in 532ms.

^C^C
86166@DESKTOP-Q5AFI5E MINGW64 /c/web/lessons (main)
$ vue info

Environment Info:

  System:
    OS: Windows 10 10.0.18363
    CPU: (8) x64 Intel(R) Core(TM) i5-1035G4 CPU @ 1.10GHz
  Binaries:
    Node: 14.8.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.7 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Not Found
  npmPackages:
    @vitejs/plugin-vue: ^1.0.4 => 1.1.0
    @vue/compiler-core:  3.0.5
    @vue/compiler-dom:  3.0.5
    @vue/compiler-sfc: ^3.0.5 => 3.0.5
    @vue/compiler-ssr:  3.0.5
    @vue/reactivity:  3.0.5
    @vue/runtime-core:  3.0.5
    @vue/runtime-dom:  3.0.5
    @vue/shared:  3.0.5
    vue: ^3.0.5 => 3.0.5
    vue-router: ^4.0.3 => 4.0.3
    vue3-markdown-it: ^1.0.7 => 1.0.7
    vuex: ^4.0.0-rc.2 => 4.0.0-rc.2
  npmGlobalPackages:
    @vue/cli: Not Found

it seems like a problem occured in your code that caused vite hmr failed.

I will try again

@ailaiwuyou I tried vite in your same environment and it performed well.
  ⚡Vite dev server running at:

  > Network:  http://<IP_ADDRESS>:3000/
  > Local:    http://localhost:3000/

  ready in 532ms.

^C^C
86166@DESKTOP-Q5AFI5E MINGW64 /c/web/lessons (main)
$ vue info

Environment Info:

  System:
    OS: Windows 10 10.0.18363
    CPU: (8) x64 Intel(R) Core(TM) i5-1035G4 CPU @ 1.10GHz
  Binaries:
    Node: 14.8.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.7 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Not Found
  npmPackages:
    @vitejs/plugin-vue: ^1.0.4 => 1.1.0
    @vue/compiler-core:  3.0.5
    @vue/compiler-dom:  3.0.5
    @vue/compiler-sfc: ^3.0.5 => 3.0.5
    @vue/compiler-ssr:  3.0.5
    @vue/reactivity:  3.0.5
    @vue/runtime-core:  3.0.5
    @vue/runtime-dom:  3.0.5
    @vue/shared:  3.0.5
    vue: ^3.0.5 => 3.0.5
    vue-router: ^4.0.3 => 4.0.3
    vue3-markdown-it: ^1.0.7 => 1.0.7
    vuex: ^4.0.0-rc.2 => 4.0.0-rc.2
  npmGlobalPackages:
    @vue/cli: Not Found

it seems like a problem occured in your code that caused vite hmr failed.

Did you open the url in the browser? When I open the url in the browser it can be  reproduced

@ailaiwuyou I tried vite in your same environment and it performed well.
  ⚡Vite dev server running at:

  > Network:  http://<IP_ADDRESS>:3000/
  > Local:    http://localhost:3000/

  ready in 532ms.

^C^C
86166@DESKTOP-Q5AFI5E MINGW64 /c/web/lessons (main)
$ vue info

Environment Info:

  System:
    OS: Windows 10 10.0.18363
    CPU: (8) x64 Intel(R) Core(TM) i5-1035G4 CPU @ 1.10GHz
  Binaries:
    Node: 14.8.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.7 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Not Found
  npmPackages:
    @vitejs/plugin-vue: ^1.0.4 => 1.1.0
    @vue/compiler-core:  3.0.5
    @vue/compiler-dom:  3.0.5
    @vue/compiler-sfc: ^3.0.5 => 3.0.5
    @vue/compiler-ssr:  3.0.5
    @vue/reactivity:  3.0.5
    @vue/runtime-core:  3.0.5
    @vue/runtime-dom:  3.0.5
    @vue/shared:  3.0.5
    vue: ^3.0.5 => 3.0.5
    vue-router: ^4.0.3 => 4.0.3
    vue3-markdown-it: ^1.0.7 => 1.0.7
    vuex: ^4.0.0-rc.2 => 4.0.0-rc.2
  npmGlobalPackages:
    @vue/cli: Not Found

it seems like a problem occured in your code that caused vite hmr failed.

Did you open the url in the browser? When I open the url in the browser it can be  reproduced

@ailaiwuyou  Yes, I did.  I suggest you to check whether your code is clean or not.

@ailaiwuyou  Yes, I did.  I suggest you to check whether your code is clean or not.

Duplicate of #1384

Duplicate of #1384


Add apis/server dir to lint

This PR is part of #236 endeavor.

Please review and merge if you approve.

One problem I just realized about this approach, is that now my IDE won't lint the files in .eslintignore. I understand this is by design, but we need to make sure all developers are on the same page about how to lint the project going forward.

@bajiat we need to let all developers know about this PR. Going forward, whenever we touch an existing JavaScript file in our project, we need to make sure it is removed from the .eslintignore file and passes lint. We are going to work through our project to 100% passing lint.


🤔 [ISSUE] eazychart-[react & vue] - Add proper storybook controls

Description
Many of the props being passed to the charts are object (for example "xAxis" for BarChart).  When someone opens Storybook, he needs to update the object with a JSON input in order to visualize the effect of the prop update. Would be convenient to have form inputs in order to tweak the props for each story in Storybook.
Reproduction steps
Run yarn storybook and select a chart.

Hey @marrouchi,
Upon reading the document of the storybook, object and array can be edited
only using the json editor (Which is just like we have right now in eazychart)

We can have such text field/ form field like you are mentioning in the simple data type like
single text field, color, dropdown.
Let me know if you know any other way around, i will be happy to implement that.
Thanks.

Here is the document: https://storybook.js.org/docs/react/essentials/controls

Hello @RoshanShrestha123 ! Yes indeed, seems there's a workaround about this : https://github.com/storybookjs/storybook/issues/16089#issuecomment-944659255
The idea is to declare flat controls following storybook docs and then assembling back the object in the story.
Here is example how to make it generic :  https://github.com/storybookjs/storybook/issues/16089#issuecomment-923117303

Hey @marrouchi, sorry for the late reply.
If its okay, Can i work on this one? Will try to implement this one.
Thanks 🙏

Hello @RoshanShrestha123, yes of course :)
I just assigned the issue to you.

Hey @RoshanShrestha123, thank you for your input it was very helpful :smile:. Sadly because it's been a while since you last communicated with us I'll be taking over this issue.


feat(lit): add router example

Me again!
Felt it looked a bit incomplete without a routing example so, even if it's not an "official" solution, I added an example with @vaadin/router which is a quite popular solution (and the most "kitchen sink" kind of solution I've found). I personally have used this library as well. The example itself I took out of the Getting started from its docs.
Other alternatives I've seen are either handling it as a multi-page app (multiple HTML files with the built-in browser navigation), or manually hooking into the popstate event to handle navigation events yourself. But this one is concise enough for a snippet, I feel.

Of course we always can do it manually with vanilla JS but in reality, we always use libraries like @vaadin/router to handle routing. So this is perfect for Component Party.
However the example submitted is not matching with other frameworks

@matschik makes sense. Modified it to match better with the other frameworks.


Remove os.cpu_count for choosing number of workers for LocalCluster

Removed os.cpu_count() while creating dask LocalCluster, letting it choose the number of workers. Addresses #5.

Could you clarify your comment @clyne a bit more - I am not sure I understand which comment you're referring to that needs to be adjusted?
If you're referring to the description of this PR, I had included a brief description of what changes were made in this PR. Should I add some more context to this comment?

Could you clarify your comment @clyne a bit more - I am not sure I understand which comment you're referring to that needs to be adjusted? If you're referring to the description of this PR, I had included a brief description of what changes were made in this PR. Should I add some more context to this comment?

Sorry for the confusion, I was referring to the comment in the cell here that says the next cell creates a cluster with the number of workers equal to the number of CPUs. Probably should say something like, we let Dask figure how how many workers to create.

Thanks for pointing out the error - I have made changes to the text accordingly.


It is impossible to create a Windows Forms class without loading the assembly before parsing the file containing the class

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce

Create a simple Windows Forms class in a .ps1 :

using namespace System.Windows.Forms
Add-Type -Assembly System.Windows.Forms

class MyForm : Form {
    MyForm() {
        [Application]::EnableVisualStyles()

        $this.Text = 'My Form'
        $this.Size = New-Object System.Drawing.Size(300, 200)
        $this.StartPosition = 'CenterScreen'
    }
}

$myForm = [MyForm]::new()
$myForm.ShowDialog()

Try to run it :
PS> .\myform.ps1

Expected behavior
Empty form opens up

Actual behavior
PS> .\myform.ps1
ParserError: C:\myform.ps1:5
Line |
   5 |  class MyForm : Form {
     |                 ~~~~
     | Unable to find type [Form].

Note that this class works correctly if i instead do this :
PS> Add-Type -Assembly System.Windows.Forms
PS> .\myform.ps1

Removing "using namespace" and specifying "System.Windows.Forms" on each type does not change anything to this behavior, nor does adding a "using assembly" statement (which is supposedly made for this if i understand the documentation about it correctly).
using assembly 'C:\Program Files\PowerShell\7\System.Windows.Forms.dll'
Add-Type -Assembly System.Windows.Forms

class MyForm : System.Windows.Forms.Form {
    MyForm() {
        [System.Windows.Forms.Application]::EnableVisualStyles()

        $this.Text = 'My Form'
        $this.Size = New-Object System.Drawing.Size(300, 200)
        $this.StartPosition = 'CenterScreen'
    }
}

$myForm = [MyForm]::new()
$myForm.ShowDialog()

PS> .\myform.ps1
ParserError: C:\myform.ps1:4
Line |
   4 |  class MyForm : System.Windows.Forms.Form {
     |                 ~~~~~~~~~~~~~~~~~~~~~~~~~
     | Unable to find type [System.Windows.Forms.Form].

Error details
Exception             :
    Type        : System.Management.Automation.ParseException
    Errors      :
        Extent  : Form
        ErrorId : TypeNotFound
        Message : Unable to find type [Form].

        Extent  : Application
        ErrorId : TypeNotFound
        Message : Unable to find type [Application].
    Message     : At C:\myform.ps1:5 char:16
                  + class MyForm : Form {
                  +                ~~~~
                  Unable to find type [Form].

                  At C:\myform.ps1:7 char:10
                  +         [Application]::EnableVisualStyles()
                  +          ~~~~~~~~~~~
                  Unable to find type [Application].
    ErrorRecord :
        Exception             :
            Type    : System.Management.Automation.ParentContainsErrorRecordException
            Message : At C:\myform.ps1:5 char:16
                      + class MyForm : Form {
                      +                ~~~~
                      Unable to find type [Form].

                      At C:\myform.ps1:7 char:10
                      +         [Application]::EnableVisualStyles()
                      +          ~~~~~~~~~~~
                      Unable to find type [Application].
            HResult : -2146233087
        CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
        FullyQualifiedErrorId : TypeNotFound
        InvocationInfo        :
            ScriptLineNumber : 5
            OffsetInLine     : 16
            HistoryId        : 2
            ScriptName       : C:\myform.ps1
            Line             : class MyForm : Form {

            Statement        : Form
            PositionMessage  : At C:\myform.ps1:5 char:16
                               + class MyForm : Form {
                               +                ~~~~
            PSScriptRoot     : C:\
            PSCommandPath    : C:\myform.ps1
            CommandOrigin    : Internal
        ScriptStackTrace      : at <ScriptBlock>, <No file>: line 1
    TargetSite  :
        Name          : Create
        DeclaringType : scriptblock
        MemberType    : Method
        Module        : System.Management.Automation.dll
    Data        : System.Collections.ListDictionaryInternal
    Source      : System.Management.Automation
    HResult     : -2146233087
    StackTrace  :
   at System.Management.Automation.ScriptBlock.Create(Parser parser, String fileName, String fileContents)
   at System.Management.Automation.ExternalScriptInfo.ParseScriptContents(Parser parser, String fileName, String
fileContents, Nullable`1 definingLanguageMode)
   at System.Management.Automation.ExternalScriptInfo.get_ScriptBlock()
   at System.Management.Automation.CommandDiscovery.CreateCommandProcessorForScript(ExternalScriptInfo scriptInfo,
ExecutionContext context, Boolean useNewScope, SessionStateInternal sessionState)
   at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(CommandInfo commandInfo, CommandOrigin
commandOrigin, Nullable`1 useLocalScope, SessionStateInternal sessionState)
   at System.Management.Automation.ExecutionContext.CreateCommand(String command, Boolean dotSource)
   at System.Management.Automation.PipelineOps.AddCommand(PipelineProcessor pipe, CommandParameterInternal[]
commandElements, CommandBaseAst commandBaseAst, CommandRedirection[] redirections, ExecutionContext context)
   at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput,
CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][]
commandRedirections, FunctionContext funcContext)
   at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
CategoryInfo          : ParserError: (:) [], ParseException
FullyQualifiedErrorId : TypeNotFound
InvocationInfo        :
    ScriptLineNumber : 5
    OffsetInLine     : 16
    HistoryId        : 2
    ScriptName       : C:\myform.ps1
    Line             : class MyForm : Form {

    Statement        : Form
    PositionMessage  : At C:\myform.ps1:5 char:16
                       + class MyForm : Form {
                       +                ~~~~
    PSScriptRoot     : C:\
    PSCommandPath    : C:\myform.ps1
    CommandOrigin    : Internal
ScriptStackTrace      : at <ScriptBlock>, <No file>: line 1

Environment data
PSVersion                      7.4.1
PSEdition                      Core
GitCommitId                    7.4.1
OS                             Microsoft Windows 10.0.23619
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

This is expected behavior - type definitions and using ... directives in PowerShell source code are parsed and compiled ahead of script execution, and therefore prior to the execution of Add-Type -Assembly System.Windows.Forms.
The solution to this specific scenario is to use a using assembly directive:
using assembly System.Windows.Forms
using namespace System.Windows.Forms

class MyForm : Form {
    MyForm() {
        [Application]::EnableVisualStyles()

        $this.Text = 'My Form'
        $this.Size = New-Object System.Drawing.Size(300, 200)
        $this.StartPosition = 'CenterScreen'
    }
}

$myForm = [MyForm]::new()
$myForm.ShowDialog()

It will have the same effect as Add-Type -Assembly System.Windows.Forms, but since the using directive is parsed and applied by the time the class is compiled you'll no longer see the type resolution error.

@IISResetMe As specified in my longer explanation in Actual behavior, "using assembly" does not change anything to the problem, either by putting the absolute path or, like you just the name.
Absolute path (using assembly 'C:\Program Files\PowerShell\7\System.Windows.Forms.dll') :
PS> .\myform.ps1
ParserError: C:\myform.ps1:4
Line |
   4 |  class MyForm : System.Windows.Forms.Form {
     |                 ~~~~~~~~~~~~~~~~~~~~~~~~~
     | Unable to find type [System.Windows.Forms.Form].

Just the name (using assembly System.Windows.Forms) :
PS> .\myform.ps1
ParserError: C:\myform.ps1:1
Line |
   1 |  using assembly System.Windows.Forms
     |                 ~~~~~~~~~~~~~~~~~~~~
     | Cannot load assembly 'System.Windows.Forms'.

Remove spaces around :
using assembly "C:\Program Files\PowerShell\7\System.Windows.Forms.dll"
using namespace System.Windows.Forms

class MyForm:Form {
....

@237dmitry This does not seem to work for me.
PS> .\myform.ps1
ParserError: C:\myform.ps1:4
Line |
   4 |  class MyForm:Form {
     |               ~~~~
     | Unable to find type [Form].

I should mention that this issue is exactly the same in Windows PowerShell 5.1

Sorry, apparently while I was testing the assembly was loaded in advance.

I misspoke earlier about using a module with a RequiredAssemblies manifest entry being a viable workaround - it isn't, for the same reason that using assembly doesn't work. I've updated the previous comment accordingly.


Usage of {% extends %} in storefront

Should be {% sw_extends<EMAIL_ADDRESS>%}, so that the theme inheritance works correctly and we can extend the file in our plugins.
storefront/page/product-detail/review/review-login.html.twig

Hello,
thank you for creating this issue.
I have opened a ticket on our Issue Tracker for you. See the ticket link: https://issues.shopware.com/issues/NEXT-7080
Please use this ticket to track the state of your issue.


No documentation for setting up metadata.json file.

The Readme describes how to setup a Puppetfile but not metadata.json

That's because the metadata.json is part of a puppet module. See here:
https://docs.puppet.com/puppet/latest/reference/modules_metadata.html

this question seems to be answered. the issue should be closed.
@ekohl are you the one maintaining this repository? I saw you merged some pull requests almost a year ago (and you were the last one to do it)

Thanks for bringing this to my attention. I do have some interest but lack time to properly maintain it. If there are people who would like to contribute then Voxpupuli we welcome new contributors.


How to override variables in custom theme?

I can't figure out how to override variables in my custom theme. Could you provide me with an example or guide me in the right direction, please?
I want to change the width of the NavDrawer and from my understanding of components/layout/theme.css, the NavDrawer gets its width from --drawer-desktop-width located in components/drawer/config.css.
I tried implementing RTDrawer in my theme with the following CSS:
:root {
  --drawer-desktop-width: 100px;
  --drawer-mobile-width: 80px;
}

But without luck. Whats the correct way of achieving this?

I think it would be great with some guidance on how this is supposed to work. I'd be happy to write some documentation, when I figure out how?

Is the only option to provide a JS object to css-next features.customProperties.variables? Can't this be done using CSS?

As far as I know, that's the only option

@thj-dk Overriding variables can be done without preprocessing only if your browser supports it so it's not recommended at all. For this you just have to redefine variables after the originals. Of course they shouldn't be processed. To override variables with your customs you need to process with css next and provide your overrides. If you are using react toolbox configured with css modules in webpack it's pretty easy to define a module with all of your overrides and pass it to the customProperties option from css-next.
If you use react-toolbox-themr you can add your overrides in the package configuration or in a custom file as specified in the README.
Another option could be to override them as you were doing in your example but in that case you also need to import the original CSS file. Take into account that the variable scope is only applied per file!
At the end you need to either rely on the browser or process with css next. In the later you must use react toolbox themr or css next directly consuming their api to provide overrides.
@thj-dk Overriding variables can be done without preprocessing only if your browser supports it so it's not recommended at all. For this you just have to redefine variables after the originals. Of course they shouldn't be processed. To override variables with your customs you need to process with css next and provide your overrides. If you are using react toolbox configured with css modules in webpack it's pretty easy to define a module with all of your overrides and pass it to the customProperties option from css-next.
If you use react-toolbox-themr you can add your overrides in the package configuration or in a custom file as specified in the README.
Another option could be to override them as you were doing but in that case you also need to import the CSS file
If you have further questions please ask! I'll be happy to help.


How to disable the titles?

It it possible to have menu with icons only?
Like a .showOnlyIconsMode()

@roughike Could you please add this feature?


Non-Caching "Parse" method

While I love the new caching features you've introduced there are times where I want to run a template without caching against a service that contains cached templates (areas).

PS: Check out Cake you're build process will never be the same :smile:

Thanks, the problem I see with this is that the assembly is basically still cached in memory its just that you remove the possibility to access it (easily at least). This is basically a hidden memory leak.
Cake looks nice (thanks for the hint!), but it actually looks pretty much like a FAKE copy (which it what we are using currently) so I don't really see the reason to switch (for this project at least). And FAKE seems to be better integrated in a lot of tools we are currently using for building (Paket, FSharp.Formatting,... ). And Cake looks (from my first impression) quite limited (load custom assemblies?, open custom namespaces?, define custom types?) compared to FAKE.

Can point me in the right direction of where to look for the cached assembly as I really need this feature?

The problem is a CLR limitation, you can not unload a single assembly. You can only unload complete AppDomains. The assembly is loaded here: https://github.com/Antaris/RazorEngine/blob/master/src/source/RazorEngine.Core/Compilation/DirectCompilerServiceBase.cs#L264
WIthout loading the assembly you cannot run the template...

If you need this and are fine with increasing memory usage you can manually delete the cache entries (use the InvalidatingCachingProvider and a custom TemplateManger without internal caching, like https://github.com/Antaris/RazorEngine/blob/master/src/source/RazorEngine.Core/Templating/ResolvePathTemplateManager.cs)
On the other hand of you are fine with weak performance but don't want memory leaks you can spin up a new IsolatedRazorEngineService instance and destroy the new AppDomain when you are finished


Docker image for quicker builds

Feature request
Hi ! As building cargo-make can take a really long and unneeded time on Travis, it could be interesting to have a docker image available, as Travis (and Gitlab-CI, too) support Docker. I don't know the state of Docker/Rust compatibility however, but I could try preparing an image myself and making a PR afterwards.
This way, the actual binary would only be built once per version, and then downloaded from the Docker hub or another repository, instead of rebuilding it during every build.
Code Example
This .travis.yml
before_install:
- cargo install --debug cargo-make

script:
- cargo make ci-flow

would be replaced by:
services:
- docker

before_install:
- docker pull sagiegurari/cargo-make

script:
- docker run sagiegurari/cargo-make ci-flow

Thanks for the suggestion.
I also use docker in few travis builds, but usually to run services that I can't run on travis directly, for example an oracle database or specific go version + nodejs in same build.
Anyhow, while it is really great and allows me to do things I can't do normally in travis, the issue is that it takes a long time to download and startup.
I think that building cargo-make is a lot faster (it takes around 1 minute in travis build), while docker takes around twice as much.
Regardless, I'll look at it and try to setup such an image.

I setup a simple docker image: https://hub.docker.com/r/sagiegurari/cargo-make/
And I'm not expert in docker, but you won't be able to use it exactly as you wrote because docker is its own linux machine in a way.
So the rust version won't come from travis but from the image and so are the sources that are going to be used for the cargo make process unless you setup some data volume that would enable access from the docker container to the travis machine.
When I use docker in builds, I usually extend the relevant docer file with my own to add the library and test sources + setup the test script to run it all.
Maybe i'm missing something basic here, so suggestions are welcome.

Thinking of a faster solution.
Maybe I'll publish prebuilt versions to bintray so travis builds can just download it and use it without compiling.
That would allow to use any rust version and not limited to the specific version in the docker image and allow you to setup the build in travis and not in docker.
I uploaded the latest version at:
https://bintray.com/sagiegurari/cargo-make/download_file?file_path=cargo-make
But haven't tested this approach yet.
would probably test it tomorrow or day afterwards and if works i'll work on automatically deploying to bintray the latest version after each cargo-make build.
Can't think of any faster solution than this.

If you want to try something, you can do the following the travis.yml
script:
  - wget -O ~/.cargo/bin/cargo-make https://bintray.com/sagiegurari/cargo-make/download_file?file_path=cargo-make
  - chmod 777 ~/.cargo/bin/cargo-make
  - cargo-make make ci-flow

Tell me if it works good for you and i'll make it more official and part of the publishing flow and document it.

published and updated the docs: https://github.com/sagiegurari/cargo-make#usage-ci-travis
see example
script:
  - wget -O ~/.cargo/bin/cargo-make https://bintray.com/sagiegurari/cargo-make/download_file?file_path=cargo-make_v0.3.47
  - chmod 777 ~/.cargo/bin/cargo-make
  - cargo-make make ci-flow

See that the version of cargo-make is part of the url so you can decide which version  you want to work with.
It really speeds things up but I currently only support linux with this solution so travis is ok, but appveyor will have to do cargo install.

The bintray deployment is really working well for me: compiling cargo-make, even in debug mode, took 58s, and this is now down to a 3s single download !
I used some bash-ninja-skills to make sure the latest available cargo-make version is used, I'm sharing it below:
env:
  global:
  - CARGO_MAKE_URL="https://bintray.com/sagiegurari/cargo-make/download_file?file_path=cargo-make_v"

before_install:
  - curl -SsL $CARGO_MAKE_URL$(cargo search cargo-make | grep cargo-make | cut -d\" -f2) > $HOME/.cargo/bin/cargo-make
  - chmod 777 $HOME/.cargo/bin/cargo-make

That's a cool script.
I'll add it to the docs 👍

Updated docs. I think we can close this issue.


feat: Include knative webhooks in readiness probes

Fixes #3867
Description
Buddy PR to https://github.com/aws/karpenter-core/pull/334
Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[ ] No

Release Note

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Is there a way to ensure in testing that we are using these readiness/liveness probes on our webhooks?

I could write an e2e test that tries out a single replica install + immediately install a provisioner afterwards. Seems like a lot, though. If anything, WDYT catching this w/ a followon as part of the increased test coverage work?

WDYT catching this w/ a followon as part of the increased test coverage work

Sounds good. As long as we are documenting it somewhere. Maybe we should create a mega-issue that captures test coverage in the Karpenter project?


Docker-Compose Redis check failing with message "Authentication required."

I'm trying to integrate Redis with Datadog in my docker compose application.
Per your instructions, I am using this compose file for my Datadog instance:
version: "3"
services:
  datadog:
    container_name: datadog
    build:
      context: [directory where Dockerfile is and my conf.d folder is stored]
      dockerfile: ./Dockerfile
      args:
        - DD_API_KEY
        - DD_SITE
    restart: on-failure
    volumes:
     - /var/run/docker.sock:/var/run/docker.sock
     - /proc/:/host/proc/:ro
     - /sys/fs/cgroup:/host/sys/fs/cgroup:ro
    links:
     - redis

And this is the Dockerfile for my Datadog service:
FROM datadog/agent:latest

# Resolve the runtime arguments:
ARG DD_API_KEY
ARG DD_SITE

# Set the environment variables:
ENV DD_API_KEY ${DD_API_KEY}
ENV DD_SITE ${DD_SITE}

ADD conf.d/redisdb.d/conf.yaml /etc/datadog-agent/conf.d/redisdb.d/conf.yaml
ADD conf.d/redisdb.d/conf.yaml /etc/datadog-agent/conf.d/redisdb.yaml

(I have seen conflicting information about whether the configuration file should be in conf.d/redisdb.yaml or conf.d/redisdb.d/conf.yaml. I tried both but neither worked.)
My Redis conf.yaml is:
init_config:

instances:
  - host: redis
    port: 6379
    password: [password to my Redis instance]

I have verified that the Redis instance is working and I can connect with that password. I have also ssh'd into the container and verified that the yaml files copied over correctly.
However when I pull the logs from the Datadog container I see this:
2021-01-09 01:14:19 UTC | CORE | INFO | (cmd/agent/app/run.go:218 in StartAgent) | Starting Datadog Agent v7.24.1
2021-01-09 01:14:19 UTC | PROCESS | INFO | (pkg/util/log/log.go:526 in func1) | Collector docker successfully detected
2021-01-09 01:14:19 UTC | PROCESS | INFO | (pkg/util/log/log.go:526 in func1) | Using collector docker
2021-01-09 01:14:19 UTC | PROCESS | WARN | (pkg/util/log/log.go:541 in func1) | failed to get configuration value for key "process_agent_config.host_ips": unable to cast <nil> of type <nil> to []string
2021-01-09 01:14:19 UTC | PROCESS | INFO | (pkg/util/log/log.go:526 in func1) | could not deduce host IP from source config: no hostIPs were configured
2021-01-09 01:14:19 UTC | PROCESS | INFO | (pkg/util/log/log.go:526 in func1) | could not deduce host IP from source ec2 metadata endpoint: unable to fetch EC2 API, status code 404 trying to fetch http://<IP_ADDRESS>/latest/meta-data/local-ipv4
2021-01-09 01:14:19 UTC | PROCESS | INFO | (pkg/util/log/log.go:526 in func1) | overriding API key from env DD_API_KEY value
2021-01-09 01:14:19 UTC | PROCESS | INFO | (pkg/process/config/config.go:297 in mergeConfigIfExists) | no config exists at /etc/datadog-agent/system-probe.yaml, ignoring...
2021-01-09 01:14:19 UTC | PROCESS | INFO | (pkg/process/config/config.go:456 in loadEnvVariables) | overriding API key from env DD_API_KEY value
2021-01-09 01:14:19 UTC | SYS-PROBE | INFO | (pkg/util/log/log.go:526 in func1) | no config exists at /etc/datadog-agent/system-probe.yaml, ignoring...
2021-01-09 01:14:19 UTC | SYS-PROBE | INFO | (pkg/util/log/log.go:526 in func1) | overriding API key from env DD_API_KEY value
2021-01-09 01:14:19 UTC | SYS-PROBE | INFO | (cmd/system-probe/main.go:84 in runAgent) | system probe not enabled. exiting.
2021-01-09 01:14:19 UTC | SECURITY | INFO | (app/app.go:168 in start) | All security-agent components are deactivated, exiting
2021-01-09 01:14:20 UTC | TRACE | INFO | (pkg/util/log/log.go:526 in func1) | Loaded configuration: /etc/datadog-agent/datadog.yaml
2021-01-09 01:14:20 UTC | TRACE | INFO | (pkg/tagger/tagger.go:156 in tryCollectors) | docker tag collector successfully started
2021-01-09 01:14:20 UTC | CORE | INFO | (cmd/agent/app/run.go:262 in StartAgent) | Hostname is: production
2021-01-09 01:14:20 UTC | CORE | INFO | (pkg/api/security/security.go:145 in fetchAuthToken) | Saved a new authentication token to /etc/datadog-agent/auth_token
2021-01-09 01:14:20 UTC | CORE | INFO | (cmd/agent/app/run.go:289 in StartAgent) | GUI server port -1 specified: not starting the GUI.
2021-01-09 01:14:20 UTC | CORE | INFO | (pkg/forwarder/forwarder.go:266 in Start) | Forwarder started, sending to 1 endpoint(s) with 1 worker(s) each: "https://7-24-1-app.agent.datadoghq.com" (1 api key(s))
2021-01-09 01:14:20 UTC | CORE | INFO | (cmd/agent/app/run.go:343 in StartAgent) | logs-agent disabled
2021-01-09 01:14:20 UTC | CORE | INFO | (cmd/agent/app/run.go:347 in StartAgent) | System probe config not found, disabling pulling system probe info in the status page: open /etc/datadog-agent/system-probe.yaml: no such file or directory
2021-01-09 01:14:20 UTC | CORE | INFO | (pkg/util/version_history.go:43 in logVersionHistoryToFile) | Cannot read file: /opt/datadog-agent/run/version-history.json, will create a new one. open /opt/datadog-agent/run/version-history.json: no such file or directory
2021-01-09 01:14:20 UTC | CORE | INFO | (pkg/tagger/tagger.go:156 in tryCollectors) | docker tag collector successfully started
2021-01-09 01:14:20 UTC | CORE | INFO | (pkg/dogstatsd/listeners/udp.go:97 in Listen) | dogstatsd-udp: starting to listen on <IP_ADDRESS>:8125
2021-01-09 01:14:20 UTC | CORE | INFO | (pkg/collector/runner/runner.go:92 in NewRunner) | Runner started with 4 workers.
2021-01-09 01:14:20 UTC | CORE | INFO | (pkg/collector/python/init.go:311 in Initialize) | Initializing rtloader with python3 /opt/datadog-agent/embedded
2021-01-09 01:14:20 UTC | PROCESS | INFO | (main_common.go:108 in runAgent) | running on platform: linux-4.4.0-169-generic-x86_64-with-glibc2.2.5
2021-01-09 01:14:20 UTC | PROCESS | INFO | (main_common.go:111 in runAgent) | running version: Version: 7.24.1, Git hash: cf2a7e6, Git branch: HEAD, Build date: 2020-12-11T15:10:53, Go Version: go version go1.14.7 linux/amd64,
2021-01-09 01:14:20 UTC | PROCESS | INFO | (pkg/tagger/tagger.go:156 in tryCollectors) | docker tag collector successfully started
2021-01-09 01:14:20 UTC | CORE | INFO | (pkg/util/cloudprovider.go:54 in DetectCloudProvider) | No cloud provider detected
2021-01-09 01:14:21 UTC | TRACE | INFO | (pkg/trace/agent/run.go:131 in Run) | Trace agent running on host production
2021-01-09 01:14:21 UTC | TRACE | INFO | (pkg/trace/api/api.go:125 in Start) | Listening for traces at http://<IP_ADDRESS>:8126

...

2021-01-09 01:14:24 UTC | CORE | INFO | (pkg/collector/runner/runner.go:261 in work) | check:redisdb | Running check
2021-01-09 01:14:24 UTC | CORE | INFO | (pkg/collector/runner/runner.go:261 in work) | check:ntp | Running check
2021-01-09 01:14:24 UTC | CORE | ERROR | (pkg/collector/runner/runner.go:292 in work) | Error running check redisdb: [{"message": "Authentication required.", "traceback": "Traceback (most recent call last):\n  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/base.py\", line 863, in run\n    self.check(instance)\n  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/redisdb/redisdb.py\", line 500, in check\n    self._check_db()\n  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/redisdb/redisdb.py\", line 194, in _check_db\n    info = conn.info()\n  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/redis/client.py\", line 1304, in info\n    return self.execute_command('INFO')\n  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/redis/client.py\", line 901, in execute_command\n    return self.parse_response(conn, command_name, **options)\n  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/redis/client.py\", line 915, in parse_response\n    response = connection.read_response()\n  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/redis/connection.py\", line 730, in read_response\n    response = self._parser.read_response()\n  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/redis/connection.py\", line 337, in read_response\n    raise error\nredis.exceptions.AuthenticationError: Authentication required.\n"}]
2021-01-09 01:14:24 UTC | CORE | INFO | (pkg/collector/runner/runner.go:327 in work) | check:redisdb | Done running check

I'm not really sure where I can go from here? Are my services configured correctly? Is there anything else I can try?

Hey @AttilaTheFun ,

(I have seen conflicting information about whether the configuration file should be in conf.d/redisdb.yaml or conf.d/redisdb.d/conf.yaml. I tried both but neither worked.)

Either of these will work with the agent. As long as the config directory or the config file is named the same as the integration (redisdb in this case). It looks like the config file is fine since the check is being run. I believe the main issue is authentication.
The error is occurring when the redis integration attempts to try connecting to your instance: https://github.com/DataDog/integrations-core/blob/6e5779072c333bcacaa47575810f8b8a6967212b/redisdb/datadog_checks/redisdb/redisdb.py#L194
Does your redis instance require a username by any chance?

Hey @AttilaTheFun ,

(I have seen conflicting information about whether the configuration file should be in conf.d/redisdb.yaml or conf.d/redisdb.d/conf.yaml. I tried both but neither worked.)

Either of these will work with the agent. As long as the config directory or the config file is named the same as the integration (redisdb in this case). It looks like the config file is fine since the check is being run. I believe the main issue is authentication.
The error is occurring when the redis integration attempts to try connecting to your instance: https://github.com/DataDog/integrations-core/blob/6e5779072c333bcacaa47575810f8b8a6967212b/redisdb/datadog_checks/redisdb/redisdb.py#L194
Does your redis instance require a username by any chance?

It shouldn't - I'm using Redis 5.0.
Since I posted this I managed to get the Autodiscovery approach working with this docker-compose file:
version: "3"
services:
  datadog:
    container_name: datadog
    build:
      context: ~/Developer/Go/github.com/attilathefun/datadog
      dockerfile: ./Dockerfile
      args:
        - DD_API_KEY
        - DD_SITE
        - REDIS_PASSWORD
        - DD_MYSQL_PASSWORD
    restart: on-failure
    volumes:
     - /var/run/docker.sock:/var/run/docker.sock
     - /proc/:/host/proc/:ro
     - /sys/fs/cgroup:/host/sys/fs/cgroup:ro
    links:
     - redis

And the Redis file:
version: "3"
services:
  redis:
    container_name: redis
    build:
      context: ~/Developer/Go/github.com/attilathefun/redis
      dockerfile: ./Dockerfile
      args:
        - REDIS_PASSWORD
    restart: on-failure
    volumes:
      - redis:/var/lib/redis
    ports:
      - "6379:6379"
    labels:
      com.datadoghq.ad.check_names: '["redisdb"]'
      com.datadoghq.ad.init_configs: '[{}]'
      com.datadoghq.ad.instances: '[{"host": "%%hostname%%","port":"6379","password":"%%env_REDIS_PASSWORD%%"}]'
volumes:
  redis:

I'm not sure why the manual config wasn't working though :/

It shouldn't - I'm using Redis 5.0.
Since I posted this I managed to get the Autodiscovery approach working with this docker-compose file:
version: "3"
services:
  datadog:
    container_name: datadog
    build:
      context: ~/Developer/Go/github.com/attilathefun/datadog
      dockerfile: ./Dockerfile
      args:
        - DD_API_KEY
        - DD_SITE
        - REDIS_PASSWORD
        - DD_MYSQL_PASSWORD
    restart: on-failure
    volumes:
     - /var/run/docker.sock:/var/run/docker.sock
     - /proc/:/host/proc/:ro
     - /sys/fs/cgroup:/host/sys/fs/cgroup:ro
    links:
     - redis

And the Redis file:
version: "3"
services:
  redis:
    container_name: redis
    build:
      context: ~/Developer/Go/github.com/attilathefun/redis
      dockerfile: ./Dockerfile
      args:
        - REDIS_PASSWORD
    restart: on-failure
    volumes:
      - redis:/var/lib/redis
    ports:
      - "6379:6379"
    labels:
      com.datadoghq.ad.check_names: '["redisdb"]'
      com.datadoghq.ad.init_configs: '[{}]'
      com.datadoghq.ad.instances: '[{"host": "%%hostname%%","port":"6379","password":"%%env_REDIS_PASSWORD%%"}]'
volumes:
  redis:

I'm not sure why the manual config wasn't working though :/

With the manual approach, could you verify that there is a conf.yaml for redis in the /etc/datadog-agent/conf.d path of the container?
The recommended method to include a config is to mount the directory: https://docs.datadoghq.com/agent/docker/integrations/?tab=file
The main difference between using ADD vs VOLUME would be that volume is accessible at run-time.

With the manual approach, could you verify that there is a conf.yaml for redis in the /etc/datadog-agent/conf.d path of the container?
The recommended method to include a config is to mount the directory: https://docs.datadoghq.com/agent/docker/integrations/?tab=file
The main difference between using ADD vs VOLUME would be that volume is accessible at run-time.

I'm facing the same issue, even though I'm using volume to attach the config file and I'm sure that config file is seen by the datadog redis checker - as I've changed port in redis config file to 8888 and see in datadog agent logs that it tries to use that port and fails.
I've started with latest redis image, then downgraded to 5.0.10, that did not helped.
Docker compose file:
version: '3.4'

services:
  redis:
    container_name: redis_cache2
    image: 'bitnami/redis:5.0.10'
    environment:
      - REDIS_PASSWORD=Qwerty@123
    ports:
      - "6379:6379"

  datadog-agent:
    container_name: datadog-agent2
    image: gcr.io/datadoghq/agent:latest
    environment:
      - DD_API_KEY=mykey
      - DD_ENV=local
      - DD_SITE=datadoghq.com
      - DD_TAGS=datadog.agent
      - DD_APM_ENABLED=true
      - DD_LOGS_ENABLED=true
      - DD_PROCESS_AGENT_ENABLED=true
      - DD_APM_NON_LOCAL_TRAFFIC=true
      - DD_LOGS_CONFIG_CONTAINER_COLLECT_ALL=true
      - DD_CONTAINER_EXCLUDE=true

    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /proc/:/host/proc/:ro
      - /sys/fs/cgroup:/host/sys/fs/cgroup:ro
      - ./conf.d:/conf.d

    links:
     - redis

Redis config file, sitting in relative path to docker compose file ./conf.d/redisdb.d/conf.yaml
init_config:

instances:
  - host: redis
    port: 6379
    password: Qwerty@123

I'm facing the same issue, even though I'm using volume to attach the config file and I'm sure that config file is seen by the datadog redis checker - as I've changed port in redis config file to 8888 and see in datadog agent logs that it tries to use that port and fails.
I've started with latest redis image, then downgraded to 5.0.10, that did not helped.
Docker compose file:
version: '3.4'

services:
  redis:
    container_name: redis_cache2
    image: 'bitnami/redis:5.0.10'
    environment:
      - REDIS_PASSWORD=Qwerty@123
    ports:
      - "6379:6379"

  datadog-agent:
    container_name: datadog-agent2
    image: gcr.io/datadoghq/agent:latest
    environment:
      - DD_API_KEY=mykey
      - DD_ENV=local
      - DD_SITE=datadoghq.com
      - DD_TAGS=datadog.agent
      - DD_APM_ENABLED=true
      - DD_LOGS_ENABLED=true
      - DD_PROCESS_AGENT_ENABLED=true
      - DD_APM_NON_LOCAL_TRAFFIC=true
      - DD_LOGS_CONFIG_CONTAINER_COLLECT_ALL=true
      - DD_CONTAINER_EXCLUDE=true

    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /proc/:/host/proc/:ro
      - /sys/fs/cgroup:/host/sys/fs/cgroup:ro
      - ./conf.d:/conf.d

    links:
     - redis

Redis config file, sitting in relative path to docker compose file ./conf.d/redisdb.d/conf.yaml
init_config:

instances:
  - host: redis
    port: 6379
    password: Qwerty@123

+1 to this, as I'm running into the exact same issue using helm. I'm putting the output of the redis helm chart user/pass into the datadog helm file via terraform, but no matter what configuration I try, it either says Authentication Required or invalid username-password pair or user is disabled.
I've tried setting the username to default, the output from the redis helm chart, and even root. None of which work, and I have no idea why.
My other services who use the redis service for access have zero issues connecting within my Kubernetes cluster, for context. I've even put Datadog in the same namespace as my redis service no dice.


Standalone mode

Hi,
how to use telegram-bot-dialogs in standalone mode without Laravel? Is it possible?
2017-02-04T12:09:03.112966+00:00 app[web.1]: [04-Feb-2017 12:09:03 UTC] PHP Fatal error:  Uncaught ArgumentCountError: Too few arguments to function HelloCommand::__construct(), 0 passed in /app/vendor/irazasyed/telegram-bot-sdk/src/Commands/CommandBus.php on line 86 and exactly 1 expected in /app/HelloCommand.php:20
so that I can add command in this way:
$telegram->addCommands([
   HelloCommand::class
]);
$update = $telegram->commandsHandler(true);

Thanks in advance,
Alex

Sorry I think it's duplicated

@typhoon1978 In last few commits I reduced Laravel dependencies. But it still depends on Redis facade. Also, compatibility with Laravel could be broken. I'll test it and fix if needed.

You could test the latest version (master branch) for standalone usage. Dependencies was deleted (replaced for Redis to use predis package directly).
Also I pushed simple example (just for tests): https://github.com/zarincheg/example-bot


major refactor: create standalone rpc directory w/ bitcoin-s-core jar file, …

…all tests pass

ACK


Unnecessary code

To shutdown the VMs we can simply use " $VMIDs | Stop-AzVM " there is not need for looping. Can also add -NoWait to do it in parallel

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

ID: 7c823b1f-688f-e1b9-1590-92d12c28b138
Version Independent ID: ac483660-9046-51b6-b678-4e6f5cd15e74
Content: Resize a Windows VM in Azure - Azure Windows Virtual Machines
Content Source: articles/virtual-machines/windows/resize-vm.md
Service: virtual-machines-windows
GitHub Login: @cynthn
Microsoft Alias: cynthn

$VMIDs | Get-AzResource | Stop-AzVM -Force -NoWait

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

Thanks for the suggestion here.  We have simplified the code as you suggested and a bit of the other code around it.  #please-close


修复了在中文输入的时候hintText不消失的问题

Coverage decreased (-0.2%) to 82.973% when pulling 9b9d119d8e7ab64cb3a9c4954235496479a25840 on develop into 657ef3f9c175c57c333f2b14b181555dcc8ce4e4 on master.


Missing Header File

freefloating_gazebo/BodySetpoint.h is missing.  Cannot compile the demo

improper workspace settings

BodySetpoint.h is created from BodySetpoint.msg in freefloating-gazebo/freefloating_gazebo
If you don't do a system install of the freefloating_gazebo package, then catkin_make won't find the file when you try to compile this demo.
Instructions for people who want to have this as a local install in their ROS workplace and/or don't want to have to go searching for a "fix" (this assumes you already have a catkin workspace set up):
$ cd catkin_ws/src
$ git clone https://github.com/freefloating-gazebo/freefloating_gazebo
$ git clone https://github.com/freefloating-gazebo/freefloating_gazebo_demo
$ cd ..
$ gedit src/freefloating_gazebo_demo/src/freefloating_gazebo_demo.cpp
Now change line 1 to read this:
#include "../../../devel/include/freefloating_gazebo/BodySetpoint.h"
$ catkin_make
This may fail out the first time, so run catkin_make again:
$ catkin_make
Once the message has been made at least once, it will exist in the catkin_ws/devel directory to be found.
Have fun! :)


PR: Fix an error with the Python path manager widget

Description of Changes
This is simply to fixed a minor bug that was introduced by PR #10623.
Issue(s) Resolved
Fixes the following error :
  File "C:\Users\User\spyder\spyder\app\mainwindow.py", line 3016, in show_path_manager
    """Update dockwidgets features settings"""
  File "C:\Users\User\spyder\spyder\widgets\pathmanager.py", line 98, in __init__
    text=_("Move to top"),
  File "C:\Users\User\spyder\spyder\widgets\pathmanager.py", line 197, in setup
    if path not in self.not_active_pathlist:
TypeError: can only concatenate tuple (not "list") to tuple

Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: Jean-Sébastien Gosselin

Python 2... 😡

@goanpeca I'm curious, why did you choose to use tuples instead of lists to store the various python paths?

@goanpeca I'm curious, why did you choose to use tuples instead of lists to store the various python paths?

The former logic was updating lists and modifying them. I felt that the secondary effects of that resulted in more difficult bugs, that is why I cleaned the whole process.
Using tuples was a way to ensure this.

Ok, thanks for the explanation, that makes sense.


Input value UI of FAQ page

@rahulbamnuya , the UI is already in good shape, and another issue for the same exists. You’ve spammed 5 issues related to the UI of different sections, but none of them have any information on how you actually plan to improve it.
Please explain the changes you wish to make in the open issues. This isn’t the right way to open issues—each one should provide a full explanation of the problem and how you intend to solve it.
Also, since I’ve already assigned one issue to you, kindly focus on that, make a PR, and only then consider opening additional issues.


PHP 7.4

The bundle doesn't seem to work with PHP 7.4 (anymore?) due to some dependency:
  Problem 1
    - symfony/http-client-contracts 2.5.x-dev requires php >=8.0.2 -> your PHP version (7.4.8) does not satisfy that requirement.
    - Installation request for stogon/unleash-bundle ^0.3.3 -> satisfiable by stogon/unleash-bundle[v0.3.3].
    - Conclusion: remove symfony/http-client-contracts v2.3.1
    - Conclusion: don't install symfony/http-client-contracts v2.3.1
    - stogon/unleash-bundle v0.3.3 requires symfony/http-client-contracts ^2.4 -> satisfiable by symfony/http-client-contracts[2.4.x-dev, 2.5.x-dev].
    - Can only install one of: symfony/http-client-contracts[2.4.x-dev, v2.3.1].
    - Can only install one of: symfony/http-client-contracts[2.5.x-dev, v2.3.1].
    - Installation request for symfony/http-client-contracts (locked at v2.3.1, required as 2.3.*) -> satisfiable by symfony/http-client-contracts[v2.3.1].

@lostfocus i tried with an fresh Symfony installation in a PHP 7.4 Docker container and it works on my side.

What have you defined for minimum-stability in your composer.json ? as i can see, you have dev but if you replace it with stable it should work
What is your Symfony version ?

In the end it was symfony/http-client-contracts - we use another bundle that requires 2.3.* on PHP7.4 and only goes to 2.4.* on PHP8.


no such file or directory, open 'F:\angular2\gpscheck\node_modules\ng2-google-place-autocomplete\index.js'

From @nizampatnamnagaraju on June 17, 2017 5:0
Copied from original issue: psykolm22/ng2-google-place-autocomplete#22

From @varunsaikodumuri on September 13, 2017 11:5
I am having same issue too. Any solution please?

From @amanarya99 on September 3, 2017 5:11
did you get any solution ?? I am currently having the same issue

Fix with angular-google-place


bug: all tasks mark as complete after completing any one

after the most recent update, whenever one task is completed, all task highlighting is removed and the arrow to the owner is applied, despite other tasks still needing to be done. removing a piece of furnature will reapply all remaining highlights, but building the replacement will again cause this.

.

I am not able to replicate this, can you tell me what version of the plugin you are using? You should see the version in the plugin-hub panel.

i am on 1.5

I can't replicate this so I can't fix it, I don't know what to tell you.
I'm doing an expert contract at the same location as you and I don't see it.

The only other thing I can think of is maybe it's dependent on your config options for the plugin?

well i feel a little the fool, restarting fixed it. sorry for the wasted time, should definitely have done that first.

No worries, no idea how or why this would have happened to you though.


Document Apache configuration in more detail

The Apache configuration needs more details on how to correctly set the WSGI and the .cfg file. This made it the testing of issue #137 more difficult.

All contents already in docs


Feature/azuresearch vector support

Added Support for Azure AI Search as a Vector Store
Summary
This update introduces a Python module (azuresearch_vector.py) for interacting with Azure’s search services.
Key features include

Utilization of fastembed for embedding.
Leveraging Azure AI Search to manage metadata by setting a single vector database with a metadata type that can be ddl, documentation, or sql. This approach maintains interaction consistency and easily adapts to the existing logic.

Example with Documentation
def add_documentation(self, doc: str) -> str:
    id = deterministic_uuid(doc) + "-doc"
    document = {
        "id": id,
        "document": doc,
        "type": "doc",
        "document_vector": self.generate_embedding(doc)
    }
    self.search_client.upload_documents(documents=[document])
    return id

def get_related_documentation(self, text: str) -> List[str]:
    result = []
    vector_query = VectorizedQuery(vector=self.generate_embedding(text), fields="document_vector")

    df = pd.DataFrame(
        self.search_client.search(
            top=self.n_results_documentation,
            vector_queries=[vector_query],
            select=["id", "document", "type"],
            filter=f"type eq 'doc'",
            vector_filter_mode=VectorFilterMode.PRE_FILTER
        )
    )

    if len(df):
        result = df["document"].tolist()
    return result

Pre-PR Actions

Tests conducted in test_vanna.py.
Pre-commit checks completed.

Thank you @lucaordronneau ! I had to comment out the integration test until we can set up Azure AI Search on our Azure account.


el-table实现多行合计功能

Please make sure these boxes are checked before submitting your PR, thank you!

[ ] Make sure you follow Element's contributing guide (中文 | English | Español | Français).
[ ] Make sure you are merging your commits to dev branch.
[ ] Add some descriptions and refer relative issues for you PR.

用插槽实现了类似的功能，感觉插槽实现更灵活一些


Logs on log file

Add a functionality that we can add the logs directly to a text file that can be store in documents directory or cache directory. This file can be used to send report to the developer in case of any issues

Whats wrong with google docs?

I any crashes occur in x user, then hee can report issue to me. While reporting, programmatically, I can attach his/her device Log file to the attachment of the mail. That way it can be easier for me to fetch the issue after the App goes live

I think there are other loggers that do this?


Prevent publication of module with same variant name or equivalent variants

When publishing Gradle metadata, making it illegal to produce the following would help build and plugin authors in getting it right:

Prevent publication of two variants with the same name
Prevent publication of two equivalent variants, that is with the same attributes and capabilities

While technically a breaking change, this sounds like earlier error detection during publication.

Should we also fail (or warn?) if there is no variant in the publication?

Can more likely happen with #10510 in place
Related to #7888 (fail when resolving GMM module without variants)


BUG: Portable Windows version not loading properly on Windows 11

I installed Bussin_Napture-portable.paf.exe and ran it, you can see it below:
So it shows a text bar(assumed, because when I hover my mouse over, it triggers mouse entry text icon) , I think it may be the search box, anyway it stay like that and doesn't "load"(invisible wall, so loads technically, but doesn't show up) the rest of the UI.
My laptop is running Windows 11 Pro 22H2 10.0.22621 64bit

Duplicate of #50

Duplicate of #50

Oh, thank you!


Merge Language 2022-10-01-preview back to main:dev/ creating 2023-05-01

Choose a PR Template
Switch to "Preview" on this description then select one of the choices below.
Click here to open a PR for a Data Plane API.
Click here to open a PR for a Control Plane (ARM) API.

@akning-ms can someone look at all the LRO errors? Are these new? They do return an Operation-Location header.
@kayousef as for the other errors about mismatching host templates, I made a recent change to the swagger in dev/ such that all the host templates are just "/language" which means all the authoring endpoints need to start with "/authoring". IIRC, TA used a host template of "/language/authoring" to avoid repeating it (my suggestion) but turns out validation doesn't like that. That should fix most of the errors besides the LRO ones.

@akning-ms can someone look at all the LRO errors? Are these new? They do return an Operation-Location header.
@kayousef as for the other errors about mismatching host templates, I made a recent change to the swagger in dev/ such that all the host templates are just "/language" which means all the authoring endpoints need to start with "/authoring". IIRC, TA used a host template of "/language/authoring" to avoid repeating it (my suggestion) but turns out validation doesn't like that. That should fix most of the errors besides the LRO ones.

@heaths done

@kayousef the samples also need to be updated to have the right api-version. Click on the Details links above to see what needs to be fixed. I'll ping @akning-ms about all these seemingly new LRO errors I've never seen before.

@akning-ms can someone look at all the LRO errors? Are these new? They do return an Operation-Location header.

the rule is enabled on Jun 2022. @raych1 to confirm whether it is something we should support in dataplane for Operation-Location

@heaths , you could add approved-modelvalidation label if the errors are confirmed as false alarm. Let me know if dataplane has another requirement for LRO instead of following ARM RPC.

Let's get this merged and try to fix all these in the dev/ folder once and for all so we don't keep getting blocked on validation errors (legit or faulty).


fix:improve PictorialBarSeriesOption

Brief Information
This pull request is in the type of:

[ ] bug fixing
[ ] new feature
[x] others

What does this PR do?

Let the interface PictorialBarSeriesOption extends the interface SeriesEncodeOptionMixin .
Fixed issues
No issues.

Details
Before: What was the problem?

The interface PictorialBarSeriesOption don't extends interface SeriesEncodeOptionMixin.
But PictorialBar supports the config encode  as document describled.
So,this PR was produced to improve the definition of PictorialBar.

After: How is it fixed in this PR?

Let the interface PictorialBarSeriesOption  extends interface SeriesEncodeOptionMixin .

Misc

[ ] The API has been changed (apache/echarts-doc#xxx).
[ ] This PR depends on ZRender changes (ecomfe/zrender#xxx).

Related test cases or examples to use the new APIs
N.A.
Others
Merging options

[x] Please squash the commits into a single one when merging.

Other information

Please update PR description to let us know what this PR does and why it's necessar

Please update PR description to let us know what this PR does and why it's necessary.

The PR description is completed

I check the code and the following series don't have SeriesEncodeOptionMixin. @100pah Can you confirm if there are any missing by mistake?

Treemap
Tree
Sunburst
Lines
Graph
Sankey
ThemeRiver
Pictorial (the only one that has encode in the doc)

@Ovilia

I check the code and the following series don't have SeriesEncodeOptionMixin. @100pah Can you confirm if there are any missing by mistake?

Treemap
Tree
Sunburst
Lines
Graph
Sankey
ThemeRiver
Pictorial (the only one that has encode in the doc)

This series theoretically can use encode, but seams rarely used? We can probably add encode
Tree based data source (Treemap, Tree, Sunburst)  and graph based data source (Graph, Sankey ) theoretically can use encode, but we might not ready to use it (e.g.,  no test case yet).
Lines and ThemeRiver  have special data source, which we are not sure whether it is suitable to use encode yet.


lodash: changed _.parseInt() method

https://lodash.com/docs#parseInt
https://lodash.com/docs#_ (description of the chainable wrapper)

@chrootsu thanks mate!


Removed redundant code from build.sh

Specifically, it looks like a merge conflict or something back
in a3b11c4 caused the directory variables to be set and mkdir'd
twice.

Thanks for the contribution! Please ensure your commits follow our style guide. This code will be tested once a Deis maintainer reviews it.

good catch. I also noticed this and removed it in #86 though separating it out into another PR is better. Thanks @ess!

Wow. Nice catch

LGTM2 (mobile)


SharpHook Issue

I really love the addon, it has helped me so much with making my Desktop Pet widget, but the addon seems windows exclusive only, which is fine, by all means.
A quick question came to mind, wouldn't using a library like https://github.com/TolikPylypchuk/SharpHook help make it easier to make the addon cross platform and help add the listed missing features?
I sadly don't have much C# experience, but I still felt like mentioning the library could help you at some point if you were wanted to make the addon not strictly for windows only!

I do have a branch for sharphook.. if you want to take a look. Lmk if you can see it.

Ah, I see it now, didn't notice it earlier. Sorry for the confusion ^^;
Thanks for letting me know btw!

Hey, sorry for reopening the issue, but I am having a bit of a problem with the SharpHook addon ^^;
In my app, you can have "States" that you can rebind keys to. However, this seems to not work with the addon for some reason.

rebinding code :

the part where it detects the input :

so from what im seeing on my side of trying to reproduce this issue is that when new action/inputs are added, they aren't being added to the "ActionDictionary" within the globalinput. I'll let you know once i've fixed this issue

Okay I know that the issue is. So when I created this pluggin, I assumed that the inputs were gunna be static. And so what's happening is that when you put in a new keybind, it doesn't update the GlobalInput's internal InputMap called ActionDictionary. This is what's causing the null returns. I've solved it on my end, through some janky code just need to think of a way to make it neater.

those should fix ur issues for now... until i find a more permanent solution

Thanks for your answer, I guess the issue should still be open since it isn't 100% fixed?

alright I pushed an update. Let me know if you run into other issues. (also do you think I should just make sharphook the main branch?)

Thanks for the quick fix, for the main branch thing, it is up to you. I say if you feel like it could give wider support and ease of use, go for it!


✨ feat(VSecM Safe): Delete safe-managed assoc k8s secrets

Delete safe-managed k8s secrets #511
Description
This PR introduces a new feature of deleting the associated kubernetes secrets if it's a safe-managed one. User can enable this feature by setting the “VSECM_SAFE_REMOVE_LINKED_K8S_SECRETS” env variable to true.
Changes
List the major changes you have made in bullet points:

app/safe/cmd/main.go: to print new env variable
app/safe/internal/state/secret-queue-k8s-delete.go: to implement deletion process.

Each queue job handled in a new goroutine.
Each deletion process uses fixed backoff strategy.
If the k8s secret not found for deletion process is no-op and it does not return an error.

core/env/safe.go: to get the VSECM_SAFE_REMOVE_LINKED_K8S_SECRETS env variable

Test Policy Compliance

[x] I have added or updated unit tests for my changes.
[x] I have included integration tests where applicable.
[x] All new and existing tests pass successfully.

Code Quality

[x] I have followed the coding standards for this project.
[x] I have performed a self-review of my code.
[x] My code is well-commented, particularly in areas that may be difficult
to understand.

Documentation

[x] I have made corresponding changes to the documentation (if applicable).
[x] I have updated any relevant READMEs or wiki pages.

Checklist
Before you submit this PR, please make sure:

[x] You have read the contributing guidelines and
especially the test policy.
[x] You have thoroughly tested your changes.
[x] You have followed all the contributing guidelines for this project.
[x] You understand and agree that your contributions will be publicly available
under the project’s license.

By submitting this pull request, you confirm that my contribution is made under
the terms of the project’s license and that you have the authority to grant
these rights.

Thank you for your contribution to VMware Secrets Manager
🐢⚡!

Thanks for your contribution @gurkanguray — I’ll check it out… within a few days.


Can not launch window from render process

Same problem as this: https://github.com/TamkeenLMS/electron-window-manager/issues/9
Should re-open that issue until fixed.
var myWindow = windowManager.createNew('myWindow', 'Stuff', false, false, false, false)
myWindow.loadURL('/login')
myWindow.open()

Uncaught Error: Could not call remote function ''. Check that the function signature is correct.
Is the documentation outdated? Because nothing I try works.

Hi there
I am not sure, it's been awhile since I last updated (or used) this library, or Electron for that matter. Try to debug more and If you find a solution please make PR.
Good luck

Hey I got the same issue,
Started a clean electron-quick-start-master on windows 10, and added the following code to to the index.html:
`    var remote = require('electron').remote;
var windowManager = remote.require('electron-window-manager');
// Create a new window
var win2 = windowManager.createNew('win23', 'Windows #2');
win2.loadURL('/test.html');
win2.open();`

This gives the same error as above mentioned. (used different urls, like direct file,  http and https)
I tried to find where the index.js of the electron-window-manager crashes, this happens on line 303:
instance.content().loadURL(url, options);
Before this line everything runs, after that line it doesn't.

Code works when you define the url in the createNew function:
`    var win2 = windowManager.createNew('win2', 'Windows #2', "https://github.com/TamkeenLMS/electron-window-manager/", false, {}, false);
win2.open();`

I cant debug further because I cant find something that has to do with content().
Instance just returns the saved window data.