Cannot Install By Angular CLI

Error occur as below, need help :
C:\xampp\htdocs\ANGULAR_PROJECT\vQr>npm i @zxing/ngx-scanner@latest --save

<EMAIL_ADDRESS>install C:\xampp\htdocs\ANGULAR_PROJECT\vQr\node_modules\sharp
node-gyp rebuild

C:\xampp\htdocs\ANGULAR_PROJECT\vQr\node_modules\sharp>if not defined npm_config_node_gyp (node "C:\Users\yen-yee.wong\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "C:\Users\yen-yee.wong\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! stack     at PythonFinder.failNoPython (C:\Users\yen-yee.wong\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\configure.js:483:19)
gyp ERR! stack     at PythonFinder. (C:\Users\yen-yee.wong\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\configure.js:508:16)
gyp ERR! stack     at C:\Users\yen-yee.wong\AppData\Roaming\npm\node_modules\npm\node_modules\graceful-fs\polyfills.js:284:29
gyp ERR! stack     at FSReqWrap.oncomplete (fs.js:152:21)
gyp ERR!  You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^4.0.0 but none is installed. You must install peer dependencies
yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

This is a problem with your environment, try to install:
npm install --global --production windows-build-tools

...and try again.

I have the same issue and the solution from @werthdavid  did not work.
I found out that the issue is in @zxing-web/library with sharp 0.19.1. With sharp 0.20.0 the issue does not appear. I created a PR https://github.com/zxing-web/library/pull/10

Just to share with you guys, this is what happens when npm install in zxing library:
~/Projects/zxing-web/library (master)
$ npm install
npm WARN deprecated<EMAIL_ADDRESS>All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
npm WARN deprecated<EMAIL_ADDRESS>Use uuid module instead
><EMAIL_ADDRESS>install C:\Users\67390\Projects\zxing-web\library\node_modules\uws
> node-gyp rebuild > build_log.txt 2>&1 || exit 0

><EMAIL_ADDRESS>install C:\Users\67390\Projects\zxing-web\library\node_modules\phantomjs-prebuilt
> node install.js

PhantomJS not found on PATH
Download already available at C:\Users\67390\AppData\Local\Temp\phantomjs\phantomjs-2.1.1-windows.zip
Verified checksum of previously downloaded file
Extracting zip contents
Removing C:\Users\67390\Projects\zxing-web\library\node_modules\phantomjs-prebuilt\lib\phantom
Copying extracted folder C:\Users\67390\AppData\Local\Temp\phantomjs\phantomjs-2.1.1-windows.zip-extract-1521118385189\phantomjs-2.1.1-windows -> C:\Users\67390\Projects\zxing-web\library\node_modules\phantomjs-prebuilt\lib\phantom
Writing location.js file
Done. Phantomjs binary available at C:\Users\67390\Projects\zxing-web\library\node_modules\phantomjs-prebuilt\lib\phantom\bin\phantomjs.exe

><EMAIL_ADDRESS>install C:\Users\67390\Projects\zxing-web\library\node_modules\sharp
> (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)

info sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.6.1/libvips-8.6.1-win32-x64.tar.gz
info sharp Creating C:\Users\67390\Projects\zxing-web\library\node_modules\sharp\build\Release
info sharp Copying DLLs from C:\Users\67390\Projects\zxing-web\library\node_modules\sharp\vendor\lib to C:\Users\67390\Projects\zxing-web\library\node_modules\sharp\build\Release
prebuild-install info begin Prebuild-install version 2.5.1
prebuild-install info looking for local prebuild @ prebuilds\sharp-v0.20.0-node-v57-win32-x64.tar.gz
prebuild-install info looking for cached prebuild @ C:\Users\67390\AppData\Roaming\npm-cache\_prebuilds\https-github.com-lovell-sharp-releases-download-v0.20.0-sharp-v0.20.0-node-v57-win32-x64.tar.gz
prebuild-install http request GET https://github.com/lovell/sharp/releases/download/v0.20.0/sharp-v0.20.0-node-v57-win32-x64.tar.gz
prebuild-install http 200 https://github.com/lovell/sharp/releases/download/v0.20.0/sharp-v0.20.0-node-v57-win32-x64.tar.gz
prebuild-install info downloading to @ C:\Users\67390\AppData\Roaming\npm-cache\_prebuilds\https-github.com-lovell-sharp-releases-download-v0.20.0-sharp-v0.20.0-node-v57-win32-x64.tar.gz.29084-ea6877ce66f2a.tmp
prebuild-install info renaming to @ C:\Users\67390\AppData\Roaming\npm-cache\_prebuilds\https-github.com-lovell-sharp-releases-download-v0.20.0-sharp-v0.20.0-node-v57-win32-x64.tar.gz
prebuild-install info unpacking @ C:\Users\67390\AppData\Roaming\npm-cache\_prebuilds\https-github.com-lovell-sharp-releases-download-v0.20.0-sharp-v0.20.0-node-v57-win32-x64.tar.gz
prebuild-install info unpack resolved to C:\Users\67390\Projects\zxing-web\library\node_modules\sharp\build\Release\sharp.node
prebuild-install info unpack required C:\Users\67390\Projects\zxing-web\library\node_modules\sharp\build\Release\sharp.node successfully
prebuild-install info install Successfully installed prebuilt binary!

><EMAIL_ADDRESS>postinstall C:\Users\67390\Projects\zxing-web\library\node_modules\webpack\node_modules\uglifyjs-webpack-plugin
> node lib/post_install.js

><EMAIL_ADDRESS>postinstall C:\Users\67390\Projects\zxing-web\library\node_modules\sinon
> node -e "console.log('\u001b[32mLove sinon? You can now support the project via the open collective:\u001b[22m\u001b[39m\n > \u001b[96m\u001b[1mhttps://opencollective.com/sinon/donate\u001b[0m\n')" || exit 0

Love sinon? You can now support the project via the open collective:
 > https://opencollective.com/sinon/donate

npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^3.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^2.1.0-beta.15 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

added 1076 packages from 1758 contributors in 107.087s

As you can see, that's a lot of things, especially for Windows environments.

Package updated and working: https://zxing-ngx-scanner.stackblitz.io/


[W6.2][T10-B1]Wu Qihao

W6.2

@qihao27
Accepting this PR with minimal review and I found no important issue.


DLL missing on windows

nvToolsExt64_1.dll is not present in the windows pacakge whereas libnvToolsExt.so is in the linux package.
This is probably because of the DLL is in a package called nsight_nvtx which is a windows only package. https://developer.download.nvidia.com/compute/cuda/redist/nsight_nvtx/windows-x86_64/nsight_nvtx-windows-x86_64-1.21018621-archive.zip

This is expected. nsight_nvtx was dropped in 12.0.0 and is header only for Windows now. I can't seem to find a release note reference other than the component table including it in 11.8 and dropping it in 12.0.
The nvtx github also mentions the dll as unneeded.

NOTE: Older versions of NVTX did require linking against a dynamic library. NVTX version 3 provides the same API, but removes the need to link with any library. Ensure you are including NVTX v3 by using the nvtx3 directory as a prefix in your #includes:

Thanks Isuru! 🙏
Appreciate you pointing this out to us. This is an ideal time to catch (and if needed fix these kinds of issues)
Even with libnvToolsExt.so, this is part of the older NVTX 2 on Linux. Similarly in that case, it would be preferable for users to upgrade to the header only NVTX 3.
Note that NVTX 3 has a compatibility mode with the NVTX 2 API. It comes down to some changes like this
-#include <nvToolsExt.h>
+#include <nvtx3/nvToolsExt.h>

Also potentially updating old CMake NVTX targets to use nvtx3 if CMake is used
If this is PyTorch related, have seen a few folks working on these changes


POD IP cannot ping success maybe since not proper route items are added?

Issue
My k8s cluster have  one master, and 3 nodes,  and I deployed nginx pod per node,  one of the node's pod IP cannot ping success
kubectl get pods -o wide
NAME             READY   STATUS    RESTARTS   AGE     IP               NODE            NOMINATED NODE   READINESS GATES
nginx-arm64      1/1     Running   0          5h22m   <IP_ADDRESS>      bcm-2xxx-rpi4
nginx-intel      1/1     Running   0          57m     <IP_ADDRESS>   intel-x86-64
nginx-worker-0   1/1     Running   0          2d4h    <IP_ADDRESS>      worker-0
ping <IP_ADDRESS>  on master node not success
Expected Behavior
ping <IP_ADDRESS> on master node success
Current Behavior
Below is some info:
tcpdump -i cali89835606d4a -nn icmp

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on cali89835606d4a, link-type EN10MB (Ethernet), capture size 262144 bytes
09:44:19.845193 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 13461, seq 1111, length 64
09:44:20.845379 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 13461, seq 1112, length 64

ICMP packets have received, but no response.
This is route table after pod nginx-intel is deployed on intel-x86-64:

Kernel IP routing table:
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
<IP_ADDRESS>         <IP_ADDRESS>   <IP_ADDRESS>         UG    0      0        0 eth0
<IP_ADDRESS>         <IP_ADDRESS>         <IP_ADDRESS>         U     10233  0        0 cali89835606d4a
<IP_ADDRESS>     <IP_ADDRESS>         <IP_ADDRESS>     U     233    0        0 cali89835606d4a
<IP_ADDRESS>     <IP_ADDRESS>   <IP_ADDRESS> UG    0      0        0 tunl0
<IP_ADDRESS>     <IP_ADDRESS>   <IP_ADDRESS> UG    0      0        0 tunl0
<IP_ADDRESS>  <IP_ADDRESS>   <IP_ADDRESS> UG    0      0        0 tunl0
<IP_ADDRESS>   <IP_ADDRESS>   <IP_ADDRESS> UG    0      0        0 tunl0
<IP_ADDRESS>  <IP_ADDRESS>         <IP_ADDRESS> U     0      0        0 *
<IP_ADDRESS>  <IP_ADDRESS>         <IP_ADDRESS> UH    0      0        0 cali89835606d4a
<IP_ADDRESS>      <IP_ADDRESS>         <IP_ADDRESS>     U     0      0        0 docker0
<IP_ADDRESS>   <IP_ADDRESS>         <IP_ADDRESS>   U     0      0        0 eth0
<IP_ADDRESS>   <IP_ADDRESS>         <IP_ADDRESS>   U     0      0        0 eth0

3  routes  items are added after pod is deployed,  and I think maybe the highlighted 2 items are not needed.
I don't know why it is added on this node.  the other 2 working nodes only add one route item.
ip addr show cali89835606d4a

33: cali89835606d4a@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1440 qdisc noqueue state UP group default
link/ether ee:ee:ee:ee:ee:ee brd ff:ff:ff:ff:ff:ff link-netnsid 0
>     inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global noprefixroute cali89835606d4a
valid_lft forever preferred_lft forever
inet6 fe80::ff87:16a7:c285:f239/64 scope link
valid_lft forever preferred_lft forever
inet6 fe80::ecee:eeff:feee:eeee/64 scope link
valid_lft forever preferred_lft forever

I don't understand why the highlighed part is added.  the working node don't have this part.
Your Environment

Calico version :  v3.12.0
Orchestrator version : k8s version:  v1.18.8-dirty
Operating System:  Linux

Does calico version and k8s version have  requirement to match each other? Where I can get this info? Thanks

I also tried nsenter -n -t $CONTAINER_PID ping <IP_ADDRESS>, cannot ping success.
so I add a route manully:
ip route add <IP_ADDRESS> dev eth0
after add this,   ping <IP_ADDRESS> can success.
This is route table of container:
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
<IP_ADDRESS>         <IP_ADDRESS>     <IP_ADDRESS>         UG    0      0        0 eth0
<IP_ADDRESS>     <IP_ADDRESS>         <IP_ADDRESS> UH    0      0        0 eth0
with the wrongly added route items,  package send to gateway which should goto eth0,  but goto cali89835606d4a again.

This one is similar to the bug I just opened here #4131

I reinstall the system of intel-x86-64, and deploy again with same steps.  and this time,  the 2 additional  wrong route item not added,  so I can ping susscess my pod ip.
so I guess this bug cannot reproduce every time,  it should be triggered by some condition,  which maybe cause not every clean enviroment， I just guess.

@sandy-lcq What is your pod CIDR and node CIDR? It seems they are both on <IP_ADDRESS>/16 network? Normally you would set your pod CIDR (e.g. <IP_ADDRESS>/24) on a different network with your node CIDR.

@song-jiang ,   my pod CIDR is <IP_ADDRESS>/16, and my node network is in subnet  <IP_ADDRESS>/24,  so my understanding they are in different network,  please help to check below config, thanks.
here is my config
kubectl cluster-info dump | grep cidr
"--allocate-node-cidrs=true",
"--cluster-cidr=<IP_ADDRESS>/16",
"--node-cidr-mask-size=24",
"--allocate-node-cidrs=true",
"--cluster-cidr=<IP_ADDRESS>/16",
"--node-cidr-mask-size=24",
kubeadm config view | grep Subnet
podSubnet: <IP_ADDRESS>/16
serviceSubnet: <IP_ADDRESS>/12
master node ip: <IP_ADDRESS>
intel-x86-64 node ip : <IP_ADDRESS>;eth0

In your issue description, you mentioned pinging from master node not working
09:44:19.845193 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 13461, seq 1111, length 64
09:44:20.845379 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 13461, seq 1112, length 64

So I am assuming <IP_ADDRESS> is your master node ip.

@song-jiang  <IP_ADDRESS> is ip of  tunl0 on master-node.  calico work in ipip mode.

@sandy-lcq I see. Yeah, two routes highlighted are very suspicious and definitely wrong. From local host, there should be one route pod-ip to calixxxx interface for each pod.
<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> U 10233 0 0 cali89835606d4a
<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> U 233 0 0 cali89835606d4a

I wonder if there are other processes programming routes on your host.

@sandy-lcq Please reopen this issue if you have more information.

@sandy-lcq Please reopen this issue if you have more information.

@song-jiang
Recently I have setup a self managed dual stack k8s cluster with calico networking by kubeadm on Linux, but right now I am facing some issues like I am unable to ping6 from master node to pod and at the same time I am able to ping6 from pods to master node
And ipv4 pinging both side from master to pods and pods to master node,
So can you give me some suggestions where I am missing some things


Retry signature validation if the schema changes

When a schema change occurs on the signatures table the prepared statement cache for the lock becomes invalid and the PostgreSQL adapter will raise PG::InFailedSqlTransaction. Because the transaction is already invalid any attempt to deallocate the statement fails - see rails/rails#12330.
Whilst any general approach that retries the transaction block after clearing the cache is not a workable solution it's one that can work in this instance. We only retry the once - if clearing the cache doesn't help then the cause of the transaction failure is somewhere else.

LGTM


Prepopulate Response.headers with values from headers_list()

This is offering slightly better control over headers possibly set by the environment or 3rd-party libraries. No test cases, I'm afraid: This would require a combination of @runInSeparateProcess and @preserveGlobalState disabled which I couldn't get to work with the bundled version of PHPUnit.

This is not correct. It will cause these headers to be sent again later in Response::send().


chore(tests): fix full_node_test

Purpose
Fix some of fails in a full_node_test including accidentally changed save_network_to_file test

prnet cleaned-up successfully


Fixed serious performance regression (revert 0f12a073af4486509dfd777da1854efb5dc571ee)

Revert commit that caused all non-zip files to be read entirely upon opening.
IsZipArchive() would read and process the entire file looking for a zip header.

Nice catch, just ran into this myself.

Finally did a release for this


Remove remaining list package code from the check command

Description of PR
Package list is a standalone command. This removes the final remnants of --list-package from the check command.
Signed-off-by: Brad P. Crochet<EMAIL_ADDRESS>
Fixes #255

Changes (required)

Remove extraneous code from check command

Checklist (required)

[X] I have reviewed and followed the contribution guidelines
[X] I have performed a self-review of my code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation if needed
[X] I have checked that my changes pass all tests

/lgtm


Use single source of truth for deployment tables

Instead of hard coding the table names, this change will look at the definitions in ethereum/deployments.ts for the table definitions.

I'm converting this to a draft until the pilot sessions table is available in ethereum/deployments.ts

I'm converting this to a draft until the pilot sessions table is available in ethereum/deployments.ts

I just merged the PR that adds it!

I just merged the PR that adds it!

@datadanne Excellent!  I'm rebasing onto that change and I'll force push here


Do you have a plan to support JavaScript or TypeScript?

I think SBE could used for web project by JavaScript or TypeScript,But I wonder if you implement it as your plan.

SBE would be really useful for web applications and particularly on mobile where it could save battery life with more efficient message parsing. We have no plans to provide this ourselves but would welcome contributions.


Fix data migration

A merged data migration that corrects the content IDs for several
Whitehall documents makes reference to a slug that doesn't exist in
staging or production. This change removes that slug and makes the code
in the data migration a little more robust to this kind of error.

:+1:


Add missing menu active item background back

Fix #30578

Not sure if this is a complete fix. I will check later. In v1.21, this style was provided by this rule:
.ui.menu .active.item,
.ui.menu .active.item:hover,
.ui.vertical.menu .active.item,
.ui.vertical.menu .active.item:hover {
  color: var(--color-text);
  background: var(--color-active);
}

Somehow this must have gotten lost during https://github.com/go-gitea/gitea/pull/30325 or another PR.

I have checked there is .ui.menu .active.item {  background: var(--color-active);
And I think current UI looks good enough so there is no need to add :hover.
Feel free to double check and edit this PR if necessary


Suggestion: Integrations should be able to provide it's own models for calculation

Hello,
 case TRANSPORTATION_MODE_PUBLIC_TRANSPORT:
      // Average of train and bus
      return (0.5 * carbonIntensity(TRANSPORTATION_MODE_TRAIN)
        + 0.5 * carbonIntensity(TRANSPORTATION_MODE_BUS));

The issue with this calculation is that every country and every public transportion system is not equal. It would be nice if by activities you could add your own method of calculation. For example, if a country has all it's public transports fuel from green sources it will be significantly lower than one that doesn't.
When you create an activity, it would be nice if you could provide a function that calculates the amount for that specific integration.

Hi @stonetwig ,
Thanks for the suggestion. In order to separate concerns, it makes more sense to have carbon models calculate emissions of activities instead of letting integrations provide their own calculation.
However, in principle, activities should have all the information needed to calculate their footprint (including the country of the activity if that's important in the carbon model).
This makes sure the carbon models are re-usable across integrations.
Is there any carbon model you wanted to improve?


Throw an error if an invalid platform is passed to the bundler

This pull request will have the React Native CLI throw an error if an invalid platform is passed to it, rather than the previous behavior where it would fail silently and give errors about missing files (like AccessibilityInfo)
> react-native bundle --entry-file index.js --bundle-output test.bundle --platform test
Invalid platform (test) selected.
Available platforms are:
  ios, android, windows, web, native
If you are trying to bundle for an out-of-tree platform, it may not be installed.

Test Plan:
I've tested passing a registered --platform to react-native bundle, and it builds without issue. I've also passed an invalid string and this error is thrown as expected.
Release Notes:
[CLI] [ENHANCEMENT] [local-cli/bundle/buildBundle.js] - Added a check to verify that the --platform passed to the bundler is valid
[CLI] [ENHANCEMENT] [local-cli/core/index.js] - Using lodash's uniq to get rid of duplicate entries in platforms and providesModuleNodeModules. Before, "ios" and "android" were in the list twice.

Thank you for your PR. We just moved this code to https://github.com/react-native-community/react-native-cli so please submit your PR there.

Hey @empyrical - that was a great PR. I don't recon you ended up submitting it again to CLI - I would love to see it because it helps with the developer experience which is our priority now!

Hey! I can remake this over in the RNCLI repo 😄

Let's do it!


Possible feature update: Only spawn from actual trees

This should be configurable with an on/off toggle, but somehow it feels wrong when I place a leaf block manually, that leaves begin falling from it. There should be some kind of check (similar to the leaf-decay check) which checks if the leaf block is in concact with a log (or within touching distance of other leaf blocks that touch a log). I'm sure there are already samples of code available that do this very check that we can slot in.

I just found state.get(LeavesBlock.PERSISTENT) which is true exactly if it was placed manually.
There's also state.get(LeavesBlock.DISTANCE), an integer between 1 and 7 telling the distance to an appropriate log.
Leaves despawn when state.get(DISTANCE) == 7 && !state.get(PERSISTENT).
So we could either use the distance or the persistence flag.
I guess it makes more sense to use the persistence flag, since most of the times, leaves are placed nearby logs anyways, so there wouldn't be an actual change.
How should we name the config option?
"Drop from manually placed leaves", defaulting to true?
It's the shortest description I can come up with and still kinda a mouthfull

I just found state.get(LeavesBlock.PERSISTENT) which is true exactly if it was placed manually.
There's also state.get(LeavesBlock.DISTANCE), an integer between 1 and 7 telling the distance to an appropriate log.
Leaves despawn when state.get(DISTANCE) == 7 && !state.get(PERSISTENT).
So we could either use the distance or the persistence flag.
I guess it makes more sense to use the persistence flag, since most of the times, leaves are placed nearby logs anyways, so there wouldn't be an actual change.
How should we name the config option?
"Drop from manually placed leaves", defaulting to true?
It's the shortest description I can come up with and still kinda a mouthfull

I think LeavesBlock.DISTANCE returns 0 if you've got a leaf block touching a stone block touching a log. It should only return the distance as it travels along other leaf blocks, making it a good way to check if a leaf block is part of an actual tree or part of something else. I haven't checked if it only works in straight lines and 90-degree angles or if it supports diagonal distances, as that would be required for some modded tree types.
As for the config option, I'd probably prefer something like "Only drop from actual trees" or similar, defaulting to false. Yours is good too, although I agree that "manually" might make it a bit wordy. Maybe "Drop from player-placed leaves"?

I think LeavesBlock.DISTANCE returns 0 if you've got a leaf block touching a stone block touching a log. It should only return the distance as it travels along other leaf blocks, making it a good way to check if a leaf block is part of an actual tree or part of something else. I haven't checked if it only works in straight lines and 90-degree angles or if it supports diagonal distances, as that would be required for some modded tree types.
As for the config option, I'd probably prefer something like "Only drop from actual trees" or similar, defaulting to false. Yours is good too, although I agree that "manually" might make it a bit wordy. Maybe "Drop from player-placed leaves"?

I believe this issue can be closed?

For me, the "player placed" option is enough, though it is different from what was originally suggested.
Implementing an actual tree check would be too expensive and basically impossible to get 100% right anyway.
There might be some merit of looking at LeavesBlock.DISTANCE but I'm not sure if it's worth getting into.
So I'd vote close until someone has a better suggestion.

Agreed, the "Player Placed" option should be enough. We can revisit this at a later date to see how leaf blocks placed as part of structures in Worldgen are handled.


Add show_diff parameter to postfix::hash and postfix::map

I suspect the goal of this feature is similar to that of #243, right?

I haven't used Sensitive yet but if that will suppress the diff content with puppet.conf has show_diff = true then #243 is a better approach.

Sensitive hides the content marked as sensitive from the outputs and reports.

I'll close this as I believe #243 fixes it.


Zebra Plugin

When i try to install the zebra plugin with pip install git+https://github.com/SergeoLacruz/inventree-zebra-plugin
I get asked for a username and password
any help
Pete

The repo os public. I can install it even withour beeing logged into github.
Perhaps a local password for  write access to your machine?
Anybody else having this issue?

No problem found


Fix for Chef 13 deprecation warning

Just got to review it. Passed kitchen?

Yes it passes but I'm wary that the output might not be quite as neat as you would like:
https://gist.github.com/equick/7f3e86b161727dc34f4108b2e07d4d5f
Basically the test is designed to throw an error when a bad port is passed and in this case ignore the failure. This counts as a pass.
If selinux_policy accepts the bad port value, it will notify the ruby block.

solves #45

I think it looks nice. The only shame is that it's a runtime issue rather than a compilation issue. But that's a future improvement thing. Rest of the kitchen runs OK?

Well ... not exactly :) See for yourself:
default-centos-6-chef-11 https://gist.github.com/equick/a21cb38e1f9e7fe79ad6375fbff5b825 (pass)
default-centos-67 https://gist.github.com/equick/c1fee501446a8912674393e88e8512cf (fail)
default-centos-72  https://gist.github.com/equick/605ecfe4b1da15e4694de68f59faa27d (fail)
broken-selinux-fedora-22 https://gist.github.com/equick/694ff094fe890bac50de2fecc54a157f (fail)
broken-selinux-fedora-23 https://gist.github.com/equick/bf4ce60c448b9b20e2ebb8baba873303 (fail)

Re-patched on my branch port-validate. Some tests are still failing, must be some regression I didn't test somewhere

They all pass if I comment out the fcontext.rb test.
From what I can make out, the stat test performed (like the one below) is run before the file context actually changes. Possible a timing issue or something related to the run order?
execute 'true' do
  not_if "stat -c %C #{dir_name} | grep #{context}"
  notifies :run, 'ruby_block[fail-mismatch]', :immediate
end

Maybe change it to echo BLA ; stat -c %C #{dir_name} | grep #{context} and see when it prints?

No difference - https://gist.github.com/equick/24c99af2148b1b3df3a4f75547e1f66e

I can't really figure out what's going on there.
Can you spare some time for it please? I'm afraid of keeping on releasing with something bad in it

No probs. I need some time to figure it out myself so bear with me on this one :)

Appears to already be in master via https://github.com/BackSlasher/chef-selinuxpolicy/commit/387225487e4a77568c70e005a4154068153f20c3

righto.


Migrate LGTM.com installation from OAuth to GitHub App

Hi There,
This project is still using an old implementation of LGTM's automated code review, which has now been disabled. To continue using automated code review, and receive checks on your Pull Requests, please install the GitHub App on this repository.
Thanks,
The LGTM Team

Deleted the old LGTM webhook. New LGTM GitHub App was already setup for this repo.


subscriber: remove trace event calls from the subscriber

It was noted that emitting a tracing event inside the subscriber could
trigger a deadlock, since std::sync::Once is not re-entrant. This
removes the tracing from the subscriber Layer methods.
If the capacity was full, sending the event was spawned into tokio, but
the event might not have been inside a runtime in the first place. And
it essentially turns it into an unbounded queue. So that is also
removed.
It also changes from using a constant FLUSH_AT_CAPACITY to a struct
field that is based on the configured event buffer capacity. A value of
half the buffer capacity was chosen, since hitting a full channel will
now mean the event is completely lost.
Fixes #27

Oh, I think rustfmt needs to be run?

Looks like there are also conflicts with main that need to be resolved?


I am curious about the difference between [Context] and [ScriptEngine] methods.

Hello, I'm Newbie who used nashorn and came over to the graal.
I checked that there are two ways to run the script while using Graal, and I wonder about the difference between the two.
First method similar to the existing nashorn grammar.
: ScriptEngine` newEngine = new ScriptEngineManager().getEngineByName("graal.js");
newEngine.eval(script);
The second method is using the Context grammar( Polyglot)
: Context newEngine = Context.newBuilder("js").build();
newEngine.eval("js", pdxScript);
I'm curious about the difference between these two methods and the better way.
And the following error occurs in the console.
I wonder what exactly the running time composition here means.
The polyglot context is using an implementation that does not support runtime compilation.

Hi,
Regarding ScriptEngine VS Context:

ScriptEngine is the JDK way to access script languages (like JavaScript: Rhino, Nashorn, etc.). This will work on any compatible JVM.
Context is GraalVM's way of accessing (script) languages. This will only work on GraalVM, or when you add the functionality explicitly by loading the respective libraries (when on a stock JVM).

ScriptEngine is great for easy tasks, but in GraalVM, our aspiration is to provide efficient and secure interoperability between languages - move data and code freely between Java and many more languages like JavaScript, Ruby, Python, R, LLVM, etc. While this is somewhat possible with the ScriptEngine interface, that interface has many shortcomings. This is the reason we provided our own org.graalvm.polyglot.* APIs. So if you want to benefit from true language interoperability on the GraalVM, use Context. If you have just a simple task (one helper script, that exchanges only limited data with the main Java app, and has only few interactions back and forth), and you need to be compatible with stock JVMs, ScriptEngine might solve your task. Our preference is clearly with Context.

The polyglot context is using an implementation that does not support runtime compilation.

That means that you are probably using a stock JVM and used our libraries to bring some GraalVM functionality there. But there are two different steps to that: first, make sure that the org.graalvm.polyglot.Context and other APIs are available, and start a language (e.g., Graal.js) based on it. That probably already works when you see that error message.
The second, missing (or misconfigured) step is to provide the GraalVM Compiler as well. That is not technically necessary - Graal.js is a Java application and will work on a stock JVM - but only with the GraalVM Compiler Graal.js will actually be fast. Only the GraalVM Compiler can help Graal.js to execute JavaScript code down to machine code. If you use
Solutions:

Use a GraalVM build instead of the current OpenJDK/OracleJDK/etc.
Have a look at e.g. https://docs.oracle.com/en/graalvm/enterprise/21/docs/reference-manual/js/RunOnJDK/ on how you can load the GraalVM Compiler on a stock JVM.

The third option is: ignore the error message and use Graal.js without GraalVM Compiler. This will technically work, but it will be slow. In the range of 10-100x slower than with GraalVM Compiler. You have been warned :-)
Best,
Christian

Thank you for your kind answer.
The project I am developing is being developed in the JAVA8 environment. Also, we plan to use Graal in the OpenJDK17 environment in the future.
Then, in such an environment as above, which one do you recommend more, [ScriptEngine] or [Context]?

Thank you for your kind answer.
The project I am developing is being developed in the JAVA8 environment. Also, we plan to use Graal in the OpenJDK17 environment in the future.
Then, in such an environment as above, which one do you recommend more, [ScriptEngine] or [Context]?

Thank you for your kind answer.
The project I am developing is being developed in the JAVA8 environment. Also, we plan to use Graal in the OpenJDK17 environment in the future.
Then, in such an environment as above, which one do you recommend more, [ScriptEngine] or [Context]?

Hi,
Regarding ScriptEngine VS Context:

ScriptEngine is the JDK way to access script languages (like JavaScript: Rhino, Nashorn, etc.). This will work on any compatible JVM.
Context is GraalVM's way of accessing (script) languages. This will only work on GraalVM, or when you add the functionality explicitly by loading the respective libraries (when on a stock JVM).

ScriptEngine is great for easy tasks, but in GraalVM, our aspiration is to provide efficient and secure interoperability between languages - move data and code freely between Java and many more languages like JavaScript, Ruby, Python, R, LLVM, etc. While this is somewhat possible with the ScriptEngine interface, that interface has many shortcomings. This is the reason we provided our own org.graalvm.polyglot.* APIs. So if you want to benefit from true language interoperability on the GraalVM, use Context. If you have just a simple task (one helper script, that exchanges only limited data with the main Java app, and has only few interactions back and forth), and you need to be compatible with stock JVMs, ScriptEngine might solve your task. Our preference is clearly with Context.

The polyglot context is using an implementation that does not support runtime compilation.

That means that you are probably using a stock JVM and used our libraries to bring some GraalVM functionality there. But there are two different steps to that: first, make sure that the org.graalvm.polyglot.Context and other APIs are available, and start a language (e.g., Graal.js) based on it. That probably already works when you see that error message.
The second, missing (or misconfigured) step is to provide the GraalVM Compiler as well. That is not technically necessary - Graal.js is a Java application and will work on a stock JVM - but only with the GraalVM Compiler Graal.js will actually be fast. Only the GraalVM Compiler can help Graal.js to execute JavaScript code down to machine code. If you use
Solutions:

Use a GraalVM build instead of the current OpenJDK/OracleJDK/etc.
Have a look at e.g. https://docs.oracle.com/en/graalvm/enterprise/21/docs/reference-manual/js/RunOnJDK/ on how you can load the GraalVM Compiler on a stock JVM.

The third option is: ignore the error message and use Graal.js without GraalVM Compiler. This will technically work, but it will be slow. In the range of 10-100x slower than with GraalVM Compiler. You have been warned :-)
Best, Christian

Thank you for your kind answer.
The project I am developing is being developed in the JAVA8 environment. Also, we plan to use Graal in the OpenJDK17 environment in the future.
Then, in such an environment as above, which one do you recommend more, [ScriptEngine] or [Context]?

If you want to use GraalVM features, language interoperability between e.g. JavaScript and Java, then then Context is the only thing I can suggest.
The only two reasons when you need to use ScriptEngine are:

you need to be backwards compatible to code already using ScriptEngine.
your cannot (always) use GraalVM

Best,
Christian


refactor(type): introduce Timestampz type

Signed-off-by: Runji Wang<EMAIL_ADDRESS>I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
This PR introduces Timestampz type as a wrapper over the original i64, as well as the corresponding TimestampzArray and TimestampzArrayBuilder. It makes a 1-1 mapping between SQL data types and Rust types, removes the ambiguity of i64 value -> int64 or timestampz. Thus ToText and ToBinary can be called without specifying the data type.
Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Refer to a related PR or issue link (optional)

Thus ToText and ToBinary can be called without specifying the data type.

This may not be the right direction to go, although a 1-1 mapping does feel cleaner at first glance.
There are basically 2 different designs:

Scalar/Datum contains enough sql-typing information, and can derive its corresponding DataType.
Scalar/Datum only contains arbitrary binary data, whose proper interpretation depends on its accompanying DataType.

In our current implementation, ScalarImpl is not [u8] but an enum. So it does feel closer to the former design than the latter. However, this may just be a side effect of rust tagged union (aka enum):

Matching against enum is easier to use than reinterpreting [u8].
The extra tagging bits inside enum ScalarImpl happen to contain enough information as enum DataType.

My concern is, as our DataType becomes complex later, the tagging bits inside ScalarImpl won't be enough, and we still need to take the latter design that passes ScalarImpl and DataType together.

Do beware of: https://github.com/risingwavelabs/risingwave/pull/7067 added to merge train.

@xiangjinwu Thanks for the explanation! I'll revert this part.

Closed as it will encourage ignoring data types that leads to misinterpretation. Will reopen it when we find a proper solution.


Git remote: either guess everything, or nothing.

We've had several tickets recently that came up due to customers not
realizing (and who could blame them) that even if they provide an app
handle and no environment, we're overriding their choice of environment
based on the current git remote.
This patch updates the aptible CLI to either guess both the app handle
and the environment handle from the current git remote (and explain what
it did), or guess neither if CLI arguments were provided.

This replaces #168.
Here's how this works in practice:

# Attempt to restart an app that doesn't exist fails
$ aptible restart --app test-app-ZZ
Could not find app test-app-ZZ in any environment (options provided via CLI arguments)

# Attempt to find an environment that doesn't exist
$ aptible restart --app test-app-ZZ --environment abc
Could not find environment abc (options provided via CLI arguments)

# Attempt to find an app that doesn't exist in an environment fails
$ aptible restart --app test-app-ZZ --environment v1
Could not find app test-app-ZZ in environment v1 (options provided via CLI arguments)

# No args uses current git working directory (restarts test-app in environment aptible)
$ aptible restart
INFO -- : Launching 2 containers for web on 2 AWS instances...
INFO -- : ...
INFO -- : Restart successful.

# No environment is guessed when (restarts test-app-v1 in environment v1)
$ aptible restart --app test-app-v1
Restarting app...
INFO -- : Restarting app...
INFO -- : ...
INFO -- : Restart successful.

cc @fancyremarker @blakepettersson

[Current coverage][cc-pull] is 86.44%

Merging [#170][cc-pull] into [master][cc-base-branch] will increase coverage by 2.87%

@@             master       #170   diff @@
==========================================
  Files            24         27     +3
  Lines           864       1010   +146
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            722        873   +151
+ Misses          142        137     -5
  Partials          0          0

Powered by Codecov. Last updated by [eba5020...17250c8][cc-compare]
[cc-base-branch]: https://codecov.io/gh/aptible/aptible-cli/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/aptible/aptible-cli/compare/eba50200f695e5397327899b30f4e6874849503e...17250c864858bc1247d8e653796f412972d63350
[cc-pull]: https://codecov.io/gh/aptible/aptible-cli/pull/170?src=pr

Much improved IMO. 👏

Closing and reopening with rebased commits on top of #174.


The pipeline always runs on the same node

I was testing the pipeline, but found that it was always scheduled to run on the same node.
Node affinity has been tried, but the result is the same.
Is there any way to schedule to different nodes.
apiVersion: argoproj.io/v1alpha1
kind: Workflow                  # new type of k8s spec
metadata:
  generateName: hello-world-    # name of the workflow spec
spec:
  entrypoint: whalesay          # invoke the whalesay template
  templates:
    - name: whalesay              # name of the template
      container:
        image: docker/whalesay
        command: [ cowsay ]
        args: [ "hello world" ]
        resources: # limit the resources
          limits:
            memory: 32Mi
            cpu: 100m

The scheduling is handled by the k8s scheduler just like any other pod, so you can use all the usual tricks, eg nodeSelector. Antiaffinity will be trickier unless you are being consistent with workflow pod labeling.
Maybe document what you tried and what failed?
It would be useful to know why you want to spread pods over multiple nodes too.

Mentoring requests are intended for people asking for a mentor to help them contribute to the project.
I think you want either the github discussion, or the argo-workflows slack channel for this type of question.


Links not working

Please update the URLs of this page.
Thanks.
Sandip

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

ID: 07e835b4-908e-4566-7420-b5f3cefffa91
Version Independent ID: 19a908fc-3526-eec2-85c6-d9c7a04e97db
Content: Hyper-V on Windows 10
Content Source: virtualization/hyper-v-on-windows/index.md
Service: windows-10-hyperv
Product: windows-10-hyperv
GitHub Login: @scooley

Thanks, fixed!


add check for isAuthCachingDisabled

fix for #18

Pull Request Test Coverage Report for Build 86

0 of 21 (0.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-3.2%) to 39.167%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

opentracing-elasticsearch-client-common/src/main/java/io/opentracing/contrib/elasticsearch/common/TracingHttpClientConfigCallback.java
0
21
0.0%

Files with Coverage Reduction
New Missed Lines
%

opentracing-elasticsearch-client-common/src/main/java/io/opentracing/contrib/elasticsearch/common/TracingHttpClientConfigCallback.java
1
0.0%

Totals

Change from base Build 84:
-3.2%

Covered Lines:
94

Relevant Lines:
240

💛  - Coveralls


Create distribution without using Route53

I am trying to use this module to create a Cloudfront distribution with S3 origin.
In my case we use cloudflare for DNS. We don't use Route53.
I am getting an error:
data.aws_route53_zone.default: Either name or zone_id must be set
How can I use this module without using Route53?
We do have a private hosted zone in Route53. Perhaps we can specify the name of that zone.

I have set this property
dns_aliases_enabled      = "false"
So this should have disabled dns records from being created so I don't understand why I am getting error shown above.


Add logic for global peers to be passive if the remote end is a Calico instance

Description

Configures global BGP peers to be passive if the remote end is another instance where Calico is running.
Related issues/PRs

Partially solves https://github.com/projectcalico/calico/issues/5461
Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

Add passive configuration for global BGP peers

I don't think we have any tests that set up a full mesh using BGP peers. The global peer tests get really close, but I think any tests we have for full mesh are under when node-to-node mesh is enabled.


Added some useful points in the readme file and updated th liscense

I am a beginner and i wanted to start my open source journey by contributing in your wonderful project , i have made some basic and useful changes in the readme and liscense file please consider them .

Thanks, but a few suggestions:

License files are auto-generated templates. We don't modify them.
Please focus on fixing the code bugs and request for enhancements on the provided project repositories. This is only a placeholder for project ideas targeting the GSoC.


Code using AccelerationStructureInstanceKHR does not compile

vk.zig:4902:5: error: packed structs cannot contain fields of type 'vk.TransformMatrixKHR'
    transform: TransformMatrixKHR,
vk.zig:4902:5: note: only packed structs layout are allowed in packed types
vk.zig:4897:39: note: struct declared here
pub const TransformMatrixKHR = extern struct {
                               ~~~~~~~^~~~~~
referenced by:
    AccelerationStructureInstanceKHR: vk.zig:4901:53

The issue appears to be that AccelerationStructureInstanceKHR is defined to be a packed struct, but it contains TransformMatrixKHR -- an extern struct, and doing so is now illegal in Zig. Not sure what the solution is here -- presumably, the only thing that actually works is to ensure all structs in packed structs are packed as well, but not sure if we can actually rely on this behaving as expected, as that would require replacing extern with packed in some scenarios, which the C ABI may not like.
Though a cursory glance makes me think only TransformMatrixKHR and SRTDataNV would need to undergo the extern -> packed transition, so at least for now it should be fine.
Also, since packed structs cannot be in extern structs, there's a couple places where that would need to be amended as well -- just the simple replacement solution as above seems even sketchier here.  There are more scenarios affected by this.

Also, unrelated, but this not being noticed before makes me think this project should have one of those things some Zig projects have where it just references every struct to ensure it typechecks.

Ah yes, this type has given some trouble before. It used to work before the packed struct overhaul, I think.

Also, unrelated, but this not being noticed earlier makes me think this project should have one of those things some Zig projects have where it just references every struct to ensure it typechecks (though this specific issue seems to need an initialization attempt to typecheck, not just a reference).

Yes, thats a good idea

Added this refAllDecls-like test also (even more elaborate than the STD one): https://github.com/Snektron/vulkan-zig/blob/master/test/ref_all_decls.zig
Of course it uncovered a bunch of issues, those are also all fixed now.

Thanks! Looks like vulkan-zig received a lot of improvements today! :smile:


ModDevTool - Add parent folder

Make it possible to define the structure of the exported zip file
Make it possible to select the Mod folder and describe it’s “surroundings”
I want to be able to select a specific mod folder and export it to a supported zip file structure looking for example something like this:

mods-unpacked/
mods-unpacked/.import
mods-unpacked/ModAuthor-ModName
mods-unpacked/ModAuthor-ModName/ModMain.gd
mods-unpacked/ModAuthor-ModName/_meta.json
mods-unpacked/ModAuthor-ModName/...

[x]  Add the possibility to define a parent folder
[x]  Create the parent folder before zipping
[x]  Put everything inside the parent folder

Done with - https://github.com/GodotModding/godot-mod-tools/commit/624571603c27ece02122c8fa9392659e3ebc9358


Migration update could potentially cause duplicate issues

This was added recently
class AddBlueprintToEntriesTable extends UpdateScript
{
    public function shouldUpdate($newVersion, $oldVersion)
    {
        return ! Schema::hasColumn(config('statamic.eloquent-driver.table_prefix', '').'entries', 'blueprint');
    }

Now if someone pulls our repo and composer update before running the migration, a new migration (duplicate) will be created because he does not yet have this column. This could lead to someone potentially pushing duplicate migrations to a server and making it crash on deploy...

Shouldn't the update check look for the migration file in the project instead of looking if the column already exists?

Would it not make more sense for you to just not git commit the migration?

@ryanmitchell
All of our migrations are source controlled, and we wouldn't want to start manually picking which should be source controlled and which should not, since all the other ones have always worked fine.

@ryanmitchell Probably the first time someone actually updates and pushes without migrating locally which created the duplicate.

wrapp it in a
if (!Schema::hasColumn('entries', 'blueprint')){ ?

}

@maxi032 yes that would work but again the issue is bigger. If migrations are being applied properly there would be no need to do that.
To ‘solve’ this we would need to apply similar to logic to all past and figure migrations which makes no sense to me.


Add Network Automation to Network section

[Insert URL to the list here]
https://github.com/networktocode/awesome-network-automation#readme
[Explain what this list is about and why it should be included here]
Massive list of network automation resources
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions.
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ add Swift
❌ Adding Swift
❌ Added Swift

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

Your entry should be added at the bottom of the appropriate category.
The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
The default branch should be named main, not master.
Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.
Must not feature Contributing or Footnotes sections.

Has an appropriate license.

We strongly recommend the CC0 license, but any Creative Commons license will work.

Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).

A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
Place a file named license or LICENSE in the repo root with the license text.
Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.
It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
The section should not appear in the Table of Contents.

All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't use hard-wrapping.
Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

Thanks for making an Awesome list! 🙌
It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

Hello,
there are 426 errors from lint:
$ npx awesome-lint https://github.com/networktocode/awesome-network-automation
✖ Linting
README.md:111:2
✖    1:1    Invalid URL: http:                                            remark-lint:double-link
✖    1:1    Forbidden license section found                               remark-lint:awesome-license
✖    1:1    Missing or invalid Table of Contents                          remark-lint:awesome-toc
✖    1:31   Invalid badge source                                          remark-lint:awesome-badge
✖    5:3    Invalid list item link URL                                    remark-lint:awesome-list-item
...
good luck !

Hey @ryanmerolle, according with the guideline, the default branch in your repo should be named main instead of master 🙂

Hi @ryanmerolle , according with the guideline,  I think you should add  unicorn comment and put your reviewed PRs in the description of the PR. Additionally, I think you need to remove the template text from there.

Closes #2036


Unable to GET media from GCS bucket and add folder in media library

Describe the bug
Uploading media is working fine, but will fetching images in the media library from the bucket gives 500
Error screenshot for fetching images from bucket

Error screenshot for adding folder

plugins.js file

middlewares.js file

Hello,
The problem describe has no relation with GCS.
GCS is working fine and your configuration looks good.
I suggest you to check the error details on your strapi instance, but your problem is related with filters set in URL with GET files routing.
Have you try to debug the GET /files route first ?
Thanks,

Hello Lith,
Yes tried debugging GET /files, and everything is the same as earlier, and no issues were found.
Is there anything else that I need to change ?
Thanks for your help


502 bad gateway when click "Force Refresh" when  query data from hive by presto

Make sure these boxes are checked before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if any
[ ] I have reproduced the issue with at least the latest released version of superset
[ ] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version
Expected results
Actual results
Steps to reproduce
url :   /superset/explore_json/table/105/?preselect_filters=%7B%7D&form_data=%7B%22datasource%22%3A%22105__table%22%2C%22viz_type%22%3A%22pivot_table%22%2C%22slice_id%22%3A48%2C%22granularity_sqla%22%3Anull%2C%22time_grain_sqla%22%3A%22Time+Column%22%2C%22since%22%3A%22100+years+ago%22%2C%22until%22%3A%22now%22%2C%22groupby%22%3A%5B%22acct_day%22%5D%2C%22columns%22%3A%5B%5D%2C%22metrics%22%3A%5B%22sum__tgt%22%2C%22sum__jszh%22%2C%22sum__total%22%5D%2C%22pandas_aggfunc%22%3A%22sum%22%2C%22pivot_margins%22%3Afalse%2C%22number_format%22%3A%22.4r%22%2C%22combine_metric%22%3Afalse%2C%22where%22%3A%22%22%2C%22having%22%3A%22%22%2C%22filters%22%3A%5B%5D%2C%22extra_filters%22%3A%5B%5D%7D&force=true

click one dashboard with 5 charts, the page loads successfully, however, when i click "Force Refresh" ,
return 502 bad gateway, the sever went down and restart.
we tested refresh 2 charts at the same time , it also loaded successfully. when refreshing more than 3 charts ,the program went down and retart.

in the config.py :   SUPERSET_WORKERS = 2
anyone can give a hint for debug?

this is because our web server was not deployed properly. it is suggested to use gunicorn with the following command:
gunicorn
-w 10
-k gevent
--timeout 120
-b  <IP_ADDRESS>:6666
--limit-request-line 0
--limit-request-field_size 0
--statsd-host localhost:8125
superset:app


Hali2/samples

Add README.md and update the code to upload/download report from/to the same local folder where the code is.

@HanLiMS,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Add: Circuit Breaker support for Routes

Purpose
Circuit Breaker configurations need to be done in the Backend Level in order to prevent downstream services from becoming overwhelmed due to failures or high latency.
Approach
Introduced new property circuitBreakers in Backend CRDs. A sample CRD looks as follows.
apiVersion: dp.wso2.com/v1alpha1
kind: Backend
metadata:
  name: insecure-backend
spec:
  circuitBreaker:
    thresholds:
    - maxConnections: 100
      maxPendingRequests: 100
      maxRequests: 100
      maxRetries: 3
  services:
  - host: backend
    port: 80

The cluster will consist of the CircuitBreaker configuration which can be found from the config dump.
        {
          "version_info": "772576675",
          "cluster": {
            "@type": "type.googleapis.com/envoy.config.cluster.v3.Cluster",
            "name": "a3b58ccf-6ecc-4557-b5bb-0a35cce38256__prod.gw.wso2.com_http-bin-api1.0.8_810833ca-0798-4aab-8530-8644182f26c20",
            "type": "STRICT_DNS",
            "connect_timeout": "20s",
            "circuit_breakers": {
              "thresholds": [
                {
                  "max_connections": 100,
                  "max_pending_requests": 100,
                  "max_requests": 100,
                  "max_retries": 3,
                  "max_connection_pools": 0
                }
              ]
            },
            "dns_refresh_rate": "5s",
            "dns_lookup_family": "V4_ONLY",
            "load_assignment": {
              "cluster_name": "a3b58ccf-6ecc-4557-b5bb-0a35cce38256__prod.gw.wso2.com_http-bin-api1.0.8_810833ca-0798-4aab-8530-8644182f26c20",
              "endpoints": [
                {
                  "lb_endpoints": [
                    {
                      "endpoint": {
                        "address": {
                          "socket_address": {
                            "address": "backend",
                            "port_value": 80
                          }
                        }
                      }
                    }
                  ]
                }
              ]
            },

Issue

https://github.com/wso2/apk/issues/1304

Codecov Report
Patch coverage has no change and project coverage change: -5.83 :warning:

Comparison is base (ca7e452) 30.51% compared to head (40d0cc5) 24.68%.

:exclamation: Current head 40d0cc5 differs from pull request most recent head d3f9e1f. Consider uploading reports for the commit d3f9e1f to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1327      +/-   ##
==========================================
- Coverage   30.51%   24.68%   -5.83%
==========================================
  Files         338       53     -285
  Lines       39196     9648   -29548
  Branches    11620        0   -11620
==========================================
- Hits        11962     2382    -9580
+ Misses      26976     7137   -19839
+ Partials      258      129     -129

Flag
Coverage Δ

adapter
24.68% <ø> (+0.04%)
:arrow_up:

admin-domain-service
?

backoffice-domain-service
?

config-deployer-service
?

devportal-domain-service
?

idp-domain-service
?

runtime-domain-service
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 265 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Run tool in Travis

Travis can now run all of the tool functionalities and the XTT handshake (with software DAA) using the default values.
Edit: client.c has been changed to return a value from util/util_errors.h. xtt.c returns 0 only when the chosen function returns a 0 and a 1 if any other value is returned--which fixes #101

Thanks for making the changes to the tool, to make sure it returns non-zero on error!
I force pushed, to rebase onto the recent changes on master.
I also moved your work from the travis.yml file into its own test script, so that we can run the same quick check locally (including on every invocation of ctest). Let me know what you think of those changes, and if you like them feel free to rebase them into your previous commits.
Otherwise, LGTM!

Those look great, thanks!


only external metadata files use conformsTo

Coverage remained the same at 100.0% when pulling 214877a9b42c3a727aec3e064903132de4b7a97c on conforms-to-doc-fix into ff39585c833fbf0f09fdfb444888ec4e48f119d8 on master.


Cap flag at end

1. Tell us something about your changes.
First commit will remove ge2d support from amlogic device as it is not needed anymore.
The second commit will fix the video slow down issue on amlogic devices. The amvideocap driver needs to support the CAP_FLAG_AT_END method.
2. If this changes affect the .conf file. Please provide the changed section
removed 2 settings as they are not needed anymore: amlogic_grabber & ge2d_mode
3. Reference an issue (optional)
The existing video slow down issue since hyperion got ported to arm/amlogic
Note: For further discussions use our forum: forum.hyperion-project.org
More infos about the video slow down:
https://discourse.coreelec.org/t/slow-down-of-hyperion-ng/341

Will merge once the conflicting file has been resolved 👍

something went wrong on my fork rebase - will do it again...


Rename tasks/ to benchmarks/

In order to fix conflicts in https://github.com/openproblems-bio/website/pull/13, we need to merge this change separately.

Since tasks/ doesn't currently factor in to the existing website at all, I'm going to go ahead and merge.


Don't match TOSDR on "device fingerprinting"

Reviewer: @jdorweiler
CC: @russellholt

Description:

Steps to test this PR:

Open e.g. https://wordpress.com/
Privacy practices should show as "unknown"

Automated tests:

[ ] Unit tests
[ ] Integration tests

Reviewer Checklist:

[ ] Ensure the PR solves the problem
[ ] Review every line of code
[ ] Ensure the PR does no harm by testing the changes thoroughly
[ ] Get help if you're uncomfortable with any of the above!
[ ] Determine if there are any quick wins that improve the implementation

PR Author Checklist:

[ ] Get advice or leverage existing code
[ ] Agree on technical approach with reviewer (if the changes are nuanced)
[ ] Ensure that there is a testing strategy (and documented non-automated tests)
[ ] Ensure there is a documented monitoring strategy (if necessary)
[ ] Consider systems implications

👍


RHTAPSRE-429: Disabling Sync Policy for Staging Public ArgoCD

This pull request will disable sync_policy for the Staging Public ArgoCD instance. We are migrating this ArgoCD instance to appsre managed OSD Cluster.

@manish-jangra Left a comment on the JIRA issue. PTAL

@manish-jangra Left a comment on the JIRA issue. PTAL

added description


[ENH] Operator overloading in BaseClasses

Is your feature request related to a problem? Please describe.
Operator overloading (apparently called magic or dunder methods by python people) was introduced across the toolkit last year.
https://github.com/sktime/sktime/pull/2164
I simply does see the need, for classification, clustering and regression at least. It seems like a contrivance for doing it just because you can. I can see no issues asking for it, no genuine use case and to me at least the high level logic of equating pipeline with multiplication is not at all intuitive. It is not, for example, transitive. It may be that other people like it, in which case no problem.
Describe the solution you'd like
In the push for a simpler toolkit, I would like to strip it out and focus instead on using sklearn pipelines, which are more familiar to users.
Describe alternatives you've considered
if these are popular we can leave them as is, I'm just looking to simplify are reduce the bloatiness of the base classes.
Additional context
I would like to do the same for clustering and regression

as with the delegates, having these overloaded operators causes no harm. No one has said anything here, so I think leave them for now, going to close this

reopening after discussion with @MatthewMiddlehurst

Closing after further discussion 🙂.


add webcomponents-lite.js in DEPS

Tests in html/custom need webcomponents.
These were removed recently, but are pulled in indirectly via observatory packages. Because those tests use it explicitly, the webcomponents package (or at least the webcomponents-lite.js file) need to be available in the repo.
3 options:

add the package in DEPS and pull it from https://github.com/dart-archive/web-components (this requires a mirror)
copy the .js file in the repo directly
use DEPS to pull the .js file directly from the polymer organization, rather than from our archive package.

The last idea seems more prone to be broken if changes happen upstream, so my inclination is for (1) or (2).
/cc @terrylucas @kevmoo @whesse

Option 2 seems the simplest, if the licence can be the same (If it is created by Google, and can be moved to the Dart licence).  It also seems appropriate, since we are using only one file, for legacy support, and will not be needing to update it. Option 1 is straightforward as well, I would mirror it to dart.googlesource.com.


specifying proxy path

userc can specify his proxy path too by jst using -x
eg : nws -x http://example.com

I like the idea and may implement it later, but there are a few problems (you may address them if you wish):

The -v option is already used.
Header of the README was clobbered.
Code style of the changes doesn't match the rest of the project.

Thanks for reviews, surely will look into it

I tried fixing above issues, hope this helps. please let me know your feedback on same.


error running snakeoil3_gym.py

Encountered error running this file. Error message below:
File "snakeoil3_gym.py", line 246
if 'identified' in sockdata:
^
IndentationError: expected an indented block

Also, when I try to run torcs, and type in "torcs" in terminal, the program will be stuck at a state where it is waiting for request on port 3101.


namespace in xml file must be identical to xsd file

btw I meant to say Hi again in my previous issue. I am been otherwise occupied for a while, but revisiting my xsd project.
I have an issue where namespaces in the xml file must be explicit and given the same name as in the xsd file.
For example, my file test.xsd defines a namespace "example" as "http://my.example.com":
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:example="http://my.example.com"
	targetNamespace="http://my.example.com"
	elementFormDefault="qualified">

	<xs:complexType name="MyType">
	<xs:sequence>
		<xs:element name="integerField" type="xs:integer"/>
	</xs:sequence>
	</xs:complexType>

	<xs:element name="myThing" type="example:MyType"/>

</xs:schema>

Then my xml file myTest.xml declares "xlmns="http://my.example.com" but this isn't sufficient: the value 1974 is not displayed in the generated form:
<myThing xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="test.xsd"
	xmlns="http://my.example.com">
		<integerField>1974</integerField>
</myThing>

If I define a namespace called "ex" instead of "example", it still isn't sufficient:
<ex:myThing xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="test.xsd"
	xmlns:ex="http://my.example.com">
		<ex:integerField>1974</ex:integerField>
</ex:myThing>

However if I define the namespace "example" as in the xsd file, the value 1974 is shown in the generated form:
<example:myThing xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="test.xsd"
	xmlns:example="http://my.example.com">
		<example:integerField>1974</example:integerField>
</example:myThing>

Yes, that's right. All namespaces and their prefixes are loaded into a root-namespaces variable and used throughout the stylesheets. So yes, (1) all namespaces should be declared in the root XSD, and (2) all prefixes (or lack thereof) should be the equal in all XSDs.
I realize it's an annoying limitation. I'll put it on the TODO-list for improvements... ;)

I understand. And it seems namespaces must be equal in the xml file too.

Hi Michiel,
This is not an "issue" so didn't want to open a new one. Just a question: is it possible to define an element in an xsd file as "readonly" in the sense that the html form will not allow editing (nor require a particular value) but the value can be set in an xml file and displayed (readonly) in a generated filled form?
Kevin.

Hi Kevin,
Yes, using 'fixed' attributes will make an element visible but not editable in a form.
Best, Michiel

However if the element is fixed to say 0, if I'm not mistaken this will override the value in a generated filled form instead of using the value in the xml file, which is what I need. So I need the ID to be unchangeable by the user through the form, but still be used as normal in every other way (i.e. have a value in xml file which is included in form submissions).

Ah, in that case, no. The value in the XML file wouldn't be valid according to the XSD with 'fixed=0' anyway.
I think your best bet is to disable the (and optionally hide) the input element through CSS.

ok thanks, will think about a workaround along those lines.

Hi Michiel,
I am enjoying using xsd2html2xml so thanks again. Another question, which may not be an "issue" so not opening a new one: is there a way to specify a string type that allows the empty string? I have tried a restriction on xs:string with a regexp that permits empties but the generated form still expects a non-empty value and complains that the field is not filled in. Let me know if you would prefer such questions in a new issue or simply by email.
cheers,
Kevin.

Hi Kevin,
I don't think an empty string is a valid xs:string type. Use minOccurs="0" for elements or use="optional" for attributes instead.
The issues board is fine for these kinds of questions.
Best regards,
Michiel

Hi,
This page indicates that an empty string is a valid xs:string value
https://www.oxygenxml.com/forum/topic1864.html
And this validator allows an empty string for an xs:string type
https://www.liquid-technologies.com/online-xsd-validator
So I’m inclined to think it’s legal. Perhaps try your favourite validator?
Kevin.

Hi Kevin,
I'm not yet convinved... ;) The XSD Datatypes documentation is not all that specific about it. But I'm inclined to think you're right, judging from the behavior of the validators.
However, I think that in 99% of the use cases people will expect those fields to be non-empty. So implementing it as default on text fields would not be a good solution. But making fields optional if the type definition contains an xs:pattern which allows for empty strings, or has an xs:minLength of 0, or is nillable, could work well.
In the meantime, either try changing the schema with minOccurs="0", or edit the XSLT directly to remove the required attribute for text fields.
Best regards,
Michiel

Yep, I think your proposed solutions (pattern with empty, or minLength=0) would solve the problem well. Please let me know if/when you implement one. In the meantime I'll use one of the workarounds.
Thanks,
Kevin.

Hi Kevin,
The latest commit has support for minLength="0" built-in for strings, normalized strings, and tokens. Both textfields and textareas with that property are generated as optional elements.
Best regards,
Michiel

Thanks! Will try it in the next few days.

Hey there,
I'm not sure if I'm doing something wrong but can't get minLength="0" to work for strings. I have this test file:
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
	<xs:simpleType name="stringType">
		<xs:restriction base="xs:string">
			<xs:minLength value="0"/>
		</xs:restriction>
	</xs:simpleType>

	<xs:complexType name="root">
		<xs:sequence>
			<xs:element name="el1" type="xs:string" minLength="0"/>
			<xs:element name="el2" type="stringType"/>
		</xs:sequence>
	</xs:complexType>

	<xs:element name="rootElement" type="root"/>
</xs:schema>

and the generated form insists I fill in both el1 and el2. I'm not even sure if using minLength in the way I use in el1 definition is legal but thought I'd try. Certainly in the restriction it's legal.
Let me know your thoughts.
Kevin.

Your code works for me. el2 is optional, el1 has incorrect syntax.
Are you sure you are using the latest commit, not the latest release?

doh! got the latest commit and works like a charm. Thanks!
On another matter, is there a way to specify the directory to look in for xsd files that are referenced by an xml file when doing xml to html (i.e. generating a filled form)?

Nice. You can point to an XSD schema from an XML file through an xsi:schemaLocation attribute.

yep, thanks. It looks for the xsd file in the directory in which the xml file resides. Which is fine for me.
K.

so i'm using the empty string fix, and have uncovered another issue. I completely understand if it takes some time to fix.
In the following example the element "el" is not optional (the form insists on a non-empty string). Its type is "stringExtension", which is an extension of an optional string type (i.e. of a restriction of string with minLength="0")
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
	<xs:simpleType name="stringType">
		<xs:restriction base="xs:string">
			<xs:minLength value="0"/>
		</xs:restriction>
	</xs:simpleType>

	<xs:complexType name="stringExtension">
		<xs:simpleContent>
			<xs:extension base="stringType">
				<xs:attribute name="myAtt" type="xs:string" fixed="val"/>
			</xs:extension>
		</xs:simpleContent>
	</xs:complexType>

	<xs:complexType name="root">
		<xs:sequence>
			<xs:element name="el" type="stringExtension"/>
		</xs:sequence>
	</xs:complexType>

	<xs:element name="rootElement" type="root"/>
</xs:schema>

Please check the latest commit, it should fix it.

It sure does, thanks Michiel.
A question: is there a way to have an attribute in the xml and xsd that is hidden in the html form?

Yes, you can use an annotation and hide the element with css.
This adds a class to your HTML element:
<xs:element type="xs:string" name="string" default="singleline string">
	<xs:annotation>
		<xs:appinfo source="https://github.com/MichielCM/xsd2html2xml">
			<class>hide</class>
		</xs:appinfo>
	</xs:annotation>
</xs:element>

And then hide it with CSS:
.hide { display: none; }
Use the config-style parameter to point to your custom CSS file.

thanks mate, will try this approach for attributes as well.

Hi,
This page indicates that an empty string is a valid xs:string value
https://www.oxygenxml.com/forum/topic1864.html
And this validator allows an empty string for an xs:string type
https://www.liquid-technologies.com/online-xsd-validator
So I’m inclined to think it’s legal. Perhaps try your favourite validator?
Kevin.

I'm experiencing this issue too. We have several xs:string elements in the schema with patterns that allow empty string and minOccurs="0" so it shouldn't be necessary to complete these fields on the form. However, they're generated with required="required" which causes validation to fail, preventing the form from being submitted without users attending to each of the affected fields.
This isn't actually a problem when a new set of data is entered as the field and tag are omitted by default, however after processing by another component we receive the XML data back with empty strings for each of these elements, which then become problematic string input fields when the data is edited in the HTML form. In order to make the form submit successfully, each one needs to be removed by clicking all the appropriate delete buttons.
I'm hoping that a simple XSLT change might prevent the required="required" attributes being generated for these fields when minOccurs="0"? We are currently using xsd2html2xml version 2 but unfortunately probably can't update to the latest very easily!

Hi,
This page indicates that an empty string is a valid xs:string value
https://www.oxygenxml.com/forum/topic1864.html
And this validator allows an empty string for an xs:string type
https://www.liquid-technologies.com/online-xsd-validator
So I’m inclined to think it’s legal. Perhaps try your favourite validator?
Kevin.

I'm experiencing this issue too. We have several xs:string elements in the schema with patterns that allow empty string and minOccurs="0" so it shouldn't be necessary to complete these fields on the form. However, they're generated with required="required" which causes validation to fail, preventing the form from being submitted without users attending to each of the affected fields.
This isn't actually a problem when a new set of data is entered as the field and tag are omitted by default, however after processing by another component we receive the XML data back with empty strings for each of these elements, which then become problematic string input fields when the data is edited in the HTML form. In order to make the form submit successfully, each one needs to be removed by clicking all the appropriate delete buttons.
I'm hoping that a simple XSLT change might prevent the required="required" attributes being generated for these fields when minOccurs="0"? We are currently using xsd2html2xml version 2 but unfortunately probably can't update to the latest very easily!

You can add a quick fix to the stylesheet: in the handle-simple-element template, wherever a 'required' attribute is added, add a check for the $min-occurs variable not being 0.

You can add a quick fix to the stylesheet: in the handle-simple-element template, wherever a 'required' attribute is added, add a check for the $min-occurs variable not being 0.

Thanks for the prompt reply. I was able to make the changes successfully by taking that approach!


Edit code indentation for correct alignment

[x] Added/updated documentation

Whoa…?! I guess at selecting the master branch, it did a whole diff between v2.2 and master. How can I correct that? I just changed some whitespace… 😬


punctuation.definition.string.begin/end

Suggestion: make the punctuation.definition.string.begin/end to "foreground": "#928374
This makes it easier to distinguish the quotation marks from the rest of the string.
greeting,
Liguma

I think it's not a good idea.
Say we have bash script code like this:
printf "%s %s" "date: ${var1}" "location: ${var2}"

It will be hard to distinguish between these strings, especially when there are spaces inside each string.


Add listObserved and listUnobserved callbacks

A friendly ping for code owner @matanlurey!
+cc @davidmorgan.

Feeling lonely in this PR, @matanlurey , @davidmorgan can you give me a clue?

I'm not really sure the status of this package ... maybe @kevmoo @nshahan

What use case/problem is this trying to solve? It feels like this might be for an application specific use case since it doesn't include similar functionality for the observable maps.
I'm reluctant to increase the size of the API without a strong justification.

@nshahan thanks for taking a look.
Some context on the problem this is trying to solve is in #78 (last point). Specifically, this would allow the list to dynamically populate only when there's at least one subscriber (to reduce the waste of resources when fetching from e.g. a remote database).
There's also a TODO comment that suggests that a similar interface was in plans:
https://github.com/dart-lang/observable/blob/04eae7a581f585fc9bafa9a36d2817e14c19c5aa/lib/src/observable_list.dart#L112-L114
Lastly, I don't see how this can be implemented for observable maps which do not have anything analogical to _listChanges. Let me know what you mean by similar functionality for maps and I'm happy to update this PR!

One alternative approach that I could try to implement is sending a notification (via notifyPropertyChange) that hasListObservers has changed.
https://github.com/dart-lang/observable/blob/04eae7a581f585fc9bafa9a36d2817e14c19c5aa/lib/src/observable_list.dart#L123-L125
I.e. something along these lines:
  _listChanges = new StreamController.broadcast(
    sync: true,
+   onListen: () => notifyPropertyChange(#hasListObservers, false, true),
    onCancel: () {
      _listChanges = null;
+     notifyPropertyChange(#hasListObservers, true, false);
    },

WDYT?

From my perspective, this package no longer offers anything that generally useful (the concept of observe-ability of collections stock has gone down quite a bit with the rise of immutability). I wouldn't want to add anything else to the API surface going forward.

@matanlurey thank you for your comment. I risk making a very specific example, but on a bright side it's realistic: I'd appreciate a hint on how list animations, in response to item addition / removal, can be implemented with immutable collections. Specifically the logic of detecting which items are inserted, removed or moved.

Unfortunately I am not prepared to do code reviews or advice here. StackOverflow is a better option.

@matanlurey okay.  I must have misunderstood the purpose your statement about this package no longer providing anything generally useful.

@nshahan, @matanlurey  can I get your comment on the solution I proposed above?
Sorry but I'm not buying an argument that "this package no longer offers anything that generally useful" and therefore "wouldn't want to add anything else to the API surface". This doesn't sound reasonable from an engineering perspective, given that I am offering to merge a PR with documentation and full coverage by tests (and if you disagree, I am happy to add more).
Even if UI moves forward to the world of immutable collections, which I appreciate, solutions like Firebase Database and Firestore operate on a concept of events modifying existing collections, not sending the whole dataset over and over.

@nshahan, @matanlurey -- a firndly ping.

@nshahan , @matanlurey -- a not so friendly friendly ping.

Socially awkward ping?

Sorry but I'm not buying an argument that "this package no longer offers anything that generally useful" and therefore "wouldn't want to add anything else to the API surface". This doesn't sound reasonable from an engineering perspective, given that I am offering to merge a PR with documentation and full coverage by tests (and if you disagree, I am happy to add more).

@dotdoom I appreciate your effort here and adding documentation and tests are helpful. 😄There are more engineering costs we have to consider though. Any new API needs to be evaluated in the design patterns of large applications and frameworks where the package is already or could be used in the future.
Once the new API is added and it gains uses there could be unintended consequences and cleaning it up later could be difficult and time consuming. For example, how does the API interact with Angular change detection and the component life cycle? Does it conflict with changes the Angular team might be wanting to make already? How does it interact with apps built in Flutter and its roadmap? I'm not asking for you to answer these questions, just posing them as hypothetical issues that could require additional design work and evaluation.
We currently don't have any of these evaluations planned for this package and can't justify adding more to the API without that type of work. I'm going to close the pull request for now, but we can refer back to this in the future if there is a proven use case that requires these types of changes and they are fully evaluated.


Multiple targets with same framework output name causes Xcode to build the wrong target

Describe the bug
Because of a bug with xcodebuild reported here and here, when RxBluetoothKit project is integrated directly as a source dependency inside another project (not via Carthage), Xcodebuild will incorrectly choose the wrong target (macOS, watchOS) when determining dependencies implicitly.
To Reproduce
Steps to reproduce the behavior:

Create a simple project with just iOS as platform/sdk
Make sure Implicit Dependency is checked in the scheme
Add RxBluetoothKit.xcodeproj to project
Drag the RxBluetoothKit.framework for iOS from RxBluetoothKit.xcodeproj Products folder to the Link Phase of the main project.
Make sure it's NOT explicitly specified in Target Dependency (xcodebuild will complain about multiple commands build the same output otherwise)
On the command line execute:
set -euo pipefail && xcodebuild -derivedDataPath 'build' -sdk 'iphonesimulator' -enableCodeCoverage YES  -scheme 'App' -configuration 'Debug' build

Notice that it will randomly pick ios, watchos or macos.
Expected behavior
It should pick iOS.
Solution
The way to solve it is to follow what other frameworks do like RxSwift, etc.. and have a single target RxBluetoothKit that supports all platforms.
Environment:

Macbook Pro 2018
OS: macOS 10.14.4
Library version: 5.2.1
Swift version: 5

same problem

same problem


Upgraded project settings, got rid of some trivial warnings.

Just upgraded per Xcode 7

Passes tests on Xcode 7.1.1


Global account settings popup modifications

After the related issues are implemented (#100 #141 #142), the account settings popup should be modified to explain user what's going on:

The "Reset your sensors to these defaults" should reset all custom sensor settings (the issue #142) to these defaults and because it can reset so many settings user has manually adjusted, we'll need another warning message popup:
"This will reset all custom sensor variable and order modifications you may have adjusted on your sensors to these account defaults. Custom names, background images, alerts and offsets are not affected."

Now I'm thinking that would be better to have more comprehensive selection of the settings here. Similar settings that we have on the sensor settings popup: https://github.com/ruuvi/com.ruuvi.station.webui/issues/142#issuecomment-1051864318
This way user could adjust the global account settings for newly added sensors as he/she likes and then start adding sensors without needing to go adjust all the sensors individually. The "Reset your sensors to these defaults" would then offer also all the same options than the individual sensor settings popups do.
So, let's discuss about this before implementing and let's update the spec if decided so.

Let's close this issue for now until we get feedback from users about possible need for these relatively complex configuration options. If not many would need these kinds of configuration options, it'll be better to keep things simple and not to offer them.


Feature request: Ajax loading of results / endless scroll

It would be nice to be able to switch from paginated results to a endless scroll list of items (automatically load on page scroll).

Hi @synonymous1984 thanks for taking the time to fill in this issue. Can you explain how it could work UX wise? What is the trigger of such switch of behavior?

Hi @bobylito! You can read a study about infinite scroll at smashing magazine. Maybe a hybrid version is also a good idea: https://www.smashingmagazine.com/2013/05/infinite-scrolling-lets-get-to-the-bottom-of-this/

Heads up! There's no an infinite hits widget: https://community.algolia.com/instantsearch.js/documentation/#infinite-hits


Add sample code for Custom Voice REST API

Purpose
Add sample code for Custom Voice REST API.
Pull Request Type
Add python sample code.

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

/azp run


clear all save states except latest for each platform

I like this one ;)

should go out next update


Marathon application schema changes.

taskKillGracePeriodSeconds field was added to marathon application struct.
Documentation about it can be found here - https://github.com/mesosphere/marathon/blob/master/docs/docs/rest-api/mesosphere/marathon/api/v2/AppsResource_create.md
Also secrets field was added, but i can't find any documentation about it right now, its only mentioned in schema - https://github.com/mesosphere/marathon/blob/master/docs/docs/rest-api/public/api/v2/schema/AppDefinition.json

Both fields are related to PRs assigned to milestone 1.3. Since Mesosphere has decided to skip 1.2, I think we can expect the next stable release to include proper documentation.
I'd rather wait to add support for either in go-marathon until the features truly end up in the next stable release. Happy to review any PRs of yours though once things have landed.

Support for the task kill grace period has been added by now.

#299 brought support for secrets. This issue is resolved.


Green LED after a successful glitch

There are two kinds of LED - GRB and RGB. Originally there was a special hardware switch by pin 25 that swapped colours when needed. Now it's moved to the different colour set, that works on both RGB / GRB diodes. That is why 2.7+ firmware uses only White, Blue and Yellow.  No more Red or Green because it can be inversed for somebody else.


Mbarba/patch pipeline

A whole new pipeline, but limited in scope: it's only to be used to update a core database after a patch build from VEuPathDB using the gene_diff script. It is using some older perl scripts, and some updated.
The pipeline goal is to do the following:

Replace the stable ids by the old ones if the genes have been updated. Do the same for transcripts/translations if an updated gene still has some of the older transcripts.
Transfer metadata from the previous database for those genes that have been updated, namely:

Description
Xrefs (excluding those from xref pipeline and protein features)
Version (incremented)

Allocate stable ids to new genes and new transcripts using the OSID service.
Load the events in the mapping_session and stable_id_event table (using the allocated IDs).
Create standard exon stable ids and set the version for all features.

I reviewed all 20 files commited. I haven't found any issues. Will there be example data to test the pipeline ? I guess testing would be tricky given it would also rely on new/old core_dbs ?

Yeah, it's too complicated as a whole pipeline to test (and its use will be pretty limited so no point spending too much time here).
Best way to do this is to should always make a mock run first, check that the changes make sense, and then reload the db and run with the OSID service for the production run.


Autocompletion does not work for complex object module outputs

Prerequisites

[x] Ensure you have latest version of plugin installed
[x] Search for possible issue duplicates

Installation details

[x] IDE version (Help->About->Copy to Clipboard)

IntelliJ IDEA 2019.2.3 (Community Edition)
Build #IC-192.6817.14, built on September 24, 2019
Runtime version: 11.0.4+10-b304.69 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.14.6
GC: ParNew, ConcurrentMarkSweep
Memory: 1981M
Cores: 8
Registry:
Non-Bundled Plugins: org.intellij.plugins.hcl, org.intellij.scala, org.jetbrains.plugins.hocon

[x] intellij-hcl plugin version (Settings->Plugins)

0.7.7

[x] Terraform version (terraform -v)

Terraform v0.12.6

Terraform Configuration Files
./child/main.tf
output "complex" {
  value = {
    top = {
      middle = {
        bottom = "nope"
      }
    }
  }
}

./main.tf
module "child" {
  source = "./child"
}

output "test" {
  value = module.child.complex.top.middle.bottom
}

Exception
Unresolved reference top

Expected Behavior
top, middle, and bottom should all resolve, as this is valid terraform code in version 0.12.*.
Actual Behavior
top (and thus all three) don't resolve
note: terraform validate succeeds
Steps to Reproduce

Place cursor after value = module.child.complex
Invoke completion.

Will be fixed in upcoming update